User equipment, base stations, and methods for priority rules used in channel state information reporting

Abstract

This invention describes a User Equipment (UE). The UE includes a receiving circuit configured to receive downlink control information (DCI) in a format used for scheduling a physical downlink shared channel (PDSCH) on a physical downlink control channel (PDCCH). The DCI includes a priority indicator. The UE also includes a transmission circuit configured to perform channel state information (CSI) reporting on the first physical uplink channel based on the priority indicator, in the event that a first physical uplink channel overlaps with a second physical uplink channel.

Description

Technical Field

[0001] This disclosure relates generally to communication systems. More specifically, this disclosure relates to user equipment (UE), base stations, and methods for priority rules for channel state information reporting. 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 downlink control information (DCI) format for scheduling / activating a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical uplink control channel (PUCCH) on a physical downlink control channel (PDCCH), the DCI including a priority indicator; and a transmission circuit configured to perform channel state information (CSI) reporting on the first physical uplink channel based on the priority indicator if the first physical uplink channel overlaps with the second physical uplink channel.

[0006] In one example, a base station apparatus includes: a transmission circuit configured to transmit downlink control information (DCI) format for scheduling / activating a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical uplink control channel (PUCCH) on a physical downlink control channel (PDCCH), the DCI including a priority indicator; and a receiving circuit configured to receive a channel state information (CSI) report on the first physical uplink channel based on the priority indicator, in the case where a first physical uplink channel overlaps with a second physical uplink channel.

[0007] In one example, a communication method for a user equipment includes: receiving a downlink control information (DCI) format for scheduling / activating a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical uplink control channel (PUCCH) on a physical downlink control channel (PDCCH), the DCI including a priority indicator; and, in the case where a first physical uplink channel overlaps with a second physical uplink channel, performing a channel state information (CSI) report on the first physical uplink channel based on the priority indicator.

[0008] In one example, a communication method of a base station apparatus includes: transmitting downlink control information (DCI) format for scheduling / activating a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical uplink control channel (PUCCH) on a physical downlink control channel (PDCCH), the DCI including a priority indicator; and receiving a channel state information (CSI) report on the first physical uplink channel based on the priority indicator when a first physical uplink channel overlaps with a second physical uplink channel. 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 Examples of multiple parameter sets are 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 An example of uplink transmission is shown.

[0014] [ Figure 6 ] Figure 6 An example of uplink transmission priority is shown.

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

[0016] [ Figure 8 ] Figure 8 The various components that can be used in gNB are shown.

[0017] [ Figure 9 ] Figure 9 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.

[0018] [ Figure 10 ] Figure 10 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.

[0019] [ Figure 11 ] Figure 11 This is a block diagram illustrating a specific implementation of gNB.

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

[0021] This invention describes a User Equipment (UE). The UE includes a receiving circuit configured to receive downlink control information (DCI) in a format used for scheduling a physical downlink shared channel (PDSCH) on a physical downlink control channel (PDCCH). The DCI includes a priority indicator. The UE also includes a transmission circuit configured to perform channel state information (CSI) reporting on the first physical uplink channel based on the priority indicator, in the event that a first physical uplink channel overlaps with a second physical uplink channel.

[0022] The present invention also describes a base station apparatus. The base station apparatus includes a transmission circuit configured to transmit a DCI format for scheduling PDSCH on a PDCCH, the DCI including a priority indicator. The base station apparatus also includes a receiving circuit configured to receive a CSI report on the first physical uplink channel based on the priority indicator, in the event that a first physical uplink channel overlaps with a second physical uplink channel.

[0023] The present invention also describes a communication method for user equipment. The method includes receiving a DCI format for scheduling a PDSCH on a PDCCH, the DCI including a priority indicator. The method further includes, in the event that a first physical uplink channel overlaps with a second physical uplink channel, performing a CSI report on the first physical uplink channel based on the priority indicator.

[0024] The present invention also describes a communication method for a base station apparatus, the method comprising transmitting a DCI format for scheduling a PDSCH on a PDCCH, the DCI including a priority indicator. The method further comprises, in the case that a first physical uplink channel overlaps with a second physical uplink channel, receiving a CSI report on the first physical uplink channel based on the priority indicator.

[0025] 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.

[0026] 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).

[0027] 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.

[0028] 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.

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 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.

[0033] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, wherein the same reference numerals indicate elements with similar functions. The systems and methods generally described and illustrated in the accompanying drawings 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.

[0034] 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 one or more physical antennas 122a-n to transmit electromagnetic signals to and receive electromagnetic signals from gNB 160. gNB 160 communicates with 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 gNB 160 can be a TRP.

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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.

[0039] 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.

[0040] The UE scheduling module 126 can perform downlink reception and uplink transmission. Downlink reception includes receiving data, receiving downlink control information, and / or receiving downlink reference signals. Uplink transmission includes transmitting data, transmitting uplink control information, and / or transmitting uplink reference signals.

[0041] In radio communication systems, 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.

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

[0043] In another example, a Physical Uplink Control Channel (PUCCH) can be defined. The PUCCH can be used to transmit Uplink Control Information (UCI). UCI may include Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK), Channel State Information (CSI), and / or Scheduling Request (SR). HARQ-ACK is used to indicate a positive acknowledgment (ACK) or negative acknowledgment (NACK) for downlink data (e.g., transport blocks, Media Access Control Protocol Data Units (MAC PDUs), and / or Downlink Shared Channel (DL-SCH)). CSI is used to indicate the state of the downlink channel (e.g., downlink signaling). CSI may include aperiodic CSI (e.g., transmitted on the PUSCH), semi-persistent CSI (e.g., transmitted on the PUSCH and / or PUCCH), and / or periodic CSI (e.g., transmitted on the PUSCH and / or PUCCH). Additionally, SR is used to request resources for uplink data (e.g., transport blocks, MAC PDUs, and / or Uplink Shared Channel (UL-SCH)).

[0044] 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.

[0045] 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).

[0046] For example, DCI format 1_0 used for scheduling PDSCH in a cell can be defined as a DCI format for the downlink. Additionally, as described herein, one or more radio network temporary identifiers (e.g., cell RNTI (C-RNTI), configured scheduling RNTI (CS-RNTI), system information RNTI (SI-RNTI), random access RNTI (RA-RNTI), MCS-C-RNTI (modulation and coding scheme-C-RNTI), and / or first RNTI) can be used to transmit DCI format 1_0. Furthermore, DCI format 1_0 can be monitored (e.g., transmitted, mapped) in the common search space (CSS) and / or the UE-specific search space (USS). Alternatively, DCI format 1_0 can be monitored (e.g., transmitted, mapped) only in the CSS.

[0047] For example, the DCI included in DCI format 1_0 may be a frequency domain resource allocation (e.g., for PDSCH). Alternatively, the DCI included in DCI format 1_0 may be a time domain resource allocation (e.g., for PDSCH). Alternatively, the DCI included in DCI format 1_0 may be a modulation and coding scheme (e.g., for PDSCH). Alternatively, the DCI included in DCI format 1_0 may be a new data indicator. Alternatively, the DCI included in DCI format 1_0 may be a TPC (e.g., transmission power control) command for scheduling PUCCH. Alternatively, the DCI included in DCI format 1_0 may be a PUCCH resource indicator. Alternatively, the DCI included in DCI format 1_0 may be a PDSCH-to-HARQ feedback timing indicator. Alternatively, the DCI included in DCI format 1_0 may be a priority indicator.

[0048] Alternatively or additionally, the DCI format 1_1 used for scheduling PDSCH in a cell may be defined as a DCI format for the downlink. Alternatively or additionally, C-RNTI, CS-RNTI, MCS-C-RNTI, and / or the first RNTI may be used to transmit DCI format 1_1. Alternatively or additionally, DCI format 1_1 may be monitored (e.g., transmitted and / or mapped) in the CSS and / or USS.

[0049] For example, the DCI included in DCI format 1_1 may be a BWP indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a frequency domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a time domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_1 may be a TPC command for scheduling a PUCCH. Additionally or alternatively, the DCI included in DCI format 1_1 may be a CSI request for requesting (e.g., triggering) the transmission of CSI (e.g., a CSI report (e.g., an aperiodic CSI report)). Alternatively or additionally, the DCI included in DCI format 1_1 may be a PUCCH resource indicator. Alternatively or additionally, the DCI included in DCI format 1_1 may be a PDSCH-to-HARQ feedback timing indicator. Alternatively or additionally, the DCI included in DCI format 1_1 may be a priority indicator.

[0050] Additionally or alternatively, the DCI format 1_X (e.g., DCI format 1_2) used for scheduling PDSCH in a cell can be defined as a DCI format for the downlink. Additionally or alternatively, C-RNTI, CS-RNTI, MCS-C-RNTI, and / or the first RNTI can be used to transmit DCI format 1_X. Additionally or alternatively, DCI format 1_X can be monitored (e.g., transmitted and / or mapped) in the CSS and / or USS.

[0051] For example, the DCI included in DCI format 1_X may be a BWP indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_X may be a frequency domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_X may be a time domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_X may be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_X may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_X may be a TPC command for scheduling a PUCCH. Additionally or alternatively, the DCI included in DCI format 1_X may be a CSI request for requesting (e.g., triggering) the transmission of CSI (e.g., a CSI report (e.g., an aperiodic CSI report)). Alternatively or additionally, the DCI included in DCI format 1_X may be a PUCCH resource indicator. Alternatively or additionally, the DCI included in DCI format 1_X may be a PDSCH-to-HARQ feedback timing indicator. Alternatively or additionally, the DCI included in DCI format 1_X may be a priority indicator.

[0052] Alternatively or additionally, the DCI format 0_0 used for scheduling PUSCH in a cell may be defined as the DCI format used for the uplink. Alternatively or additionally, C-RNTI, CS-RNTI, temporary C-RNTI, MCS-C-RNTI, and / or the first RNTI may be used to transmit DCI format 0_0. Alternatively or additionally, DCI format 0_0 may be monitored (e.g., transmitted, mapped) in the CSS and / or USS. Alternatively, DCI format 0_0 may be monitored (e.g., transmitted, mapped) only in the CSS.

[0053] For example, the DCI included in DCI format 0_0 can be a frequency domain resource allocation (e.g., for PUSCH). Alternatively, the DCI included in DCI format 0_0 can be a time domain resource allocation (e.g., for PUSCH). Alternatively, the DCI included in DCI format 0_0 can be a modulation and coding scheme (e.g., for PUSCH). Alternatively, the DCI included in DCI format 0_0 can be a new data indicator. Alternatively, the DCI included in DCI format 0_0 can be a redundant version. Alternatively, the DCI included in DCI format 0_0 can be a TPC command for scheduling PUSCH. Alternatively, the DCI included in DCI format 0_0 can be a priority indicator.

[0054] Additionally or alternatively, the DCI format 0_1 ​​used for scheduling PUSCH in a cell can be defined as a DCI format for the uplink. Here, DCI format 0_1 ​​can be described as a first DCI format 601. Additionally or alternatively, C-RNTI, CS-RNTI, and / or MCS-C-RNTI can be used to transmit DCI format 0_1 ​​(i.e., the first DCI format 601). That is, the first DCI format 601 can be DCI format 0_1 ​​with a CRC scrambled by C-RNTI, CS-RNTI, and / or MCS-C-RNTI. Here, as described below, DCI format 0_1 ​​with a CRC scrambled by MCS-C-RNTI and / or the first RNTI can be a second DCI format 603. Additionally or alternatively, DCI format 0_1 ​​(i.e., the first DCI format 601) can be monitored (e.g., transmitted, mapped) in CSS and / or USS.

[0055] For example, the DCI included in DCI format 0_1 ​​may be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a frequency domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a time domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a TPC command for scheduling PUSCH. Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a CSI request for requesting a CSI report. Additionally or alternatively, the DCI included in DCI format 0_1 ​​may be a priority indicator. If no higher-level parameter is configured for enabling priority indication (e.g., PriorityIndicator-ForDCIFormat0_1), the priority indicator can be 0 bits. If a higher-level parameter is configured for enabling priority indication (e.g., PriorityIndicator-ForDCIFormat0_1), the priority indicator can be 1 bit.

[0056] Alternatively or additionally, the DCI format 0_Y (e.g., DCI format 0_2) used for scheduling PUSCH in the cell may be defined as the DCI format used for the uplink. Alternatively or additionally, C-RNTI, CS-RNTI, MCS-C-RNTI, and / or the first RNTI may be used to transmit DCI format 0_Y. Alternatively or additionally, DCI format 0_Y may be monitored (e.g., transmitted, mapped) in the CSS and / or USS.

[0057] For example, the DCI included in DCI format 0_Y may be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_Y may be a frequency domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_Y may be a time domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_Y may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_Y may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_Y may be a TPC command for scheduling PUSCH. Additionally or alternatively, the DCI included in DCI format 0_Y may be a CSI request for requesting a CSI report. Additionally or alternatively, the DCI included in DCI format 0_Y may be a priority indicator. If no higher-level parameter for enabling priority indication is configured (e.g., PriorityIndicator-ForDCIFormat0_2), the priority indicator can be 0 bits. If a higher-level parameter for enabling priority indication is configured (e.g., PriorityIndicator-ForDCIFormat0_2), the priority indicator can be 1 bit.

[0058] Here, as described above, the RNTI (e.g., Radio Network Temporary Identifier) ​​assigned to UE 102 can be used for the transmission of DCI (e.g., one or more DCI formats, one or more DL control channels (e.g., one or more PDCCHs)). That is, gNB 160 can (e.g., by using RRC messages) transmit information to UE 102 for configuring (e.g., assigning) the RNTI.

[0059] For example, a CRC (Cyclic Redundancy Check) parity bit (also simply CRC) generated based on the DCI is appended to the DCI, and after appending, the CRC parity bit is scrambled by RNTI. UE 102 can attempt to decode (e.g., blind decoding, monitoring, detecting) the DCI appended with the RNTI-scrambled CRC parity bit. For example, UE 102 detects the DL control channel (e.g., PDCCH, DCI, DCI format) based on blind decoding. That is, UE 102 can use the CRC scrambled by RNTI to decode the DL control channel. In other words, UE 102 can use RNTI to monitor the DL control channel. For example, UE 102 can use RNTI to detect the DCI format.

[0060] Here, RNTI may include C-RNTI (cell-RNTI), CS-RNTI (configured scheduling C-RNTI), SI-RNTI (system information RNTI), RA-RNTI (random access RNTI), temporary C-RNTI, MCS-C-RNTI (modulation and coding scheme-C-RNTI), and / or the first RNTI.

[0061] For example, C-RNTI can be a unique identifier for identifying RRC connections and / or scheduling. Additionally or alternatively, CS-RNTI can be a unique identifier for configuration-based authorized scheduling transports. Additionally or alternatively, SI-RNTI can be used to identify system messages (SIs) mapped on the BCCH and dynamically carried on the DL-SCH (e.g., SI messages). Additionally or alternatively, SI-RNTI can be used for broadcasting SIs. Additionally or alternatively, RA-RNTI can be an identifier for random access procedures (e.g., Msg.2 transport). Additionally or alternatively, temporary C-RNTI can be used for scheduling random access procedures (e.g., Msg.3 (re)transports (e.g., Msg.3PUSCH (re)transports)). Additionally or alternatively, MCS-C-RNTI can be a unique identifier for an MCS table (e.g., an alternative MCS table) indicating PDSCH and / or PUSCH. The first RNTI may differ from C-RNTI, CS-RNTI, SI-RNTI, RA-RNTI, temporary C-RNTI, and / or MCS-C-RNTI.

[0062] Here, in a random access procedure (e.g., a contention-based random access procedure), the Msg.3 PUSCH transmission (e.g., the initial transmission) can be scheduled using the random access response grant. For example, in a random access procedure, the random access response grant can be included in the PDSCH (e.g., the Msg.2 transmission). Additionally, in a random access procedure, the random access response grant can be used to schedule the PUSCH for the Msg.3 transmission. Furthermore, as mentioned above, a PDCCH with a CRC scrambled by a temporary C-RNTI (i.e., DCI format 0_0) can be used to schedule the PUSCH for the Msg.3 transmission (e.g., Msg.3 retransmission).

[0063] Alternatively or additionally, 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 additionally, 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 additionally, the PUSCH may be used to transmit uplink data (e.g., UL-SCH, uplink transport block, MAC PDU).

[0064] 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). Additionally or alternatively, 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.

[0065] 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, a MIB can be used to carry minimal system information. Additionally or alternatively, SIBs can be used to carry system information messages.

[0066] 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. Additionally or alternatively, the SS can be used to detect the physical layer cell ID of the cell.

[0067] In radio communications used for uplink, UL RS can be used as the uplink physical signal. Additionally or 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 rather are used by the physical layer.

[0068] 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). Additionally or 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).

[0069] 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).

[0070] Additionally or alternatively, dual connectivity operation may be supported. For example, in dual connectivity operation, special cells may be defined. For example, a special cell may include a primary cell (e.g., the primary cell of a primary cell group (e.g., MSG)) and / or a primary / secondary cell (e.g., the primary and secondary cells of a secondary cell group (e.g., SCG)). Here, the primary and secondary cells may be referred to as cells of the primary / secondary cell group (e.g., the primary SCG cell). That is, the term "special cell" refers to a primary cell (e.g., the primary cell of an MCG) and / or a primary / secondary cell (e.g., the primary and secondary cells of an SCG).

[0071] For example, the primary cell can be a serving cell operating on the primary frequency (e.g., an MCG cell), where UE 102 can perform an initial connection establishment procedure and / or initiate a connection re-establishment procedure. Alternatively, the secondary cell can be a serving cell (e.g., an SCG cell), where UE 102 can perform a random access procedure (e.g., in the case of UE 102 performing a reconfiguration (e.g., a reconfiguration with a synchronization procedure)).

[0072] Alternatively or additionally, a special cell may always be activated (e.g., the special cell may not be deactivated). That is, secondary cells may be activated and deactivated. Additionally, PUCCH transmission may be performed (e.g., supported) only on the special cell. That is, PUCCH transmission may always be performed on the special cell. For example, resources (e.g., resource sets) for PUCCH transmission may be configured and / or indicated only on the special cell (e.g., by gNB 160 for UE 102 (e.g., by using RRC messages and / or DCI formats)). Alternatively or additionally, resources (e.g., resource sets) for PUCCH transmission may be configured and / or indicated only on each UL BWP of the special cell (e.g., by gNB 160 for UE 102 (e.g., by using RRC messages and / or DCI formats)) (e.g., only on each UL BWP in the UL BWP set of the special cell). Alternatively or additionally, a contention-based random access procedure may be performed (e.g., supported) only on the special cell.

[0073] That is, the serving cell may include a primary cell (e.g., the primary cell of MCG), a primary-secondary cell (e.g., the primary-secondary cell of SCG) and / or a secondary cell (e.g., the secondary cell of MCG and / or SCG).

[0074] For example, gNB 160 can transmit information for configuring the index of the serving cell (e.g., the index of the primary and secondary cells and / or the index of the secondary cell) using RRC messages. That is, the index of the serving cell can be used to identify the serving cell. UE 102 can identify the serving cell based on the index of the serving cell. Here, the index of the primary cell can be defined as "0". That is, the index of the primary cell can always be "0". For example, gNB 160 can transmit information for configuring the index of the secondary cell using RRC messages. And UE 102 can identify the index of the serving cell (e.g., the secondary cell) based on this information.

[0075] Additionally or alternatively, gNB 160 may transmit information for configuring cell groups (e.g., cell groups associated with dual connectivity operations (e.g., MCG and / or SCG)) using RRC messages. As described above, an MCG may include a primary cell and / or a secondary cell. Additionally, an SCG may include a primary-secondary cell and / or a secondary cell. For example, in dual connectivity operations, if UE 102 is configured with a cell group (e.g., MCG and / or SCG), UE 102 is configured with two MAC entities (e.g., one MAC entity for the MCG and one MAC entity for the SCG). For example, if UE 102 is not configured with a cell group (e.g., MCG and / or SCG), UE 102 is configured with one MAC entity (e.g., one MAC entity for the MCG). That is, for dual connectivity operations, the term "special cell" may refer to the primary cell of the MCG or the primary-secondary cell of the SCG, depending on whether the MAC entity is associated with the MCG or SCG respectively.

[0076] 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.

[0077] 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.

[0078] 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.

[0079] 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.

[0080] 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.

[0081] 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.

[0082] 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, the one or more transmitters 158 may transmit during a UL subframe. The one or more transmitters 158 may upsample and modulate a signal 156 and transmit the modulated signal to one or more gNBs 160.

[0083] 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.

[0084] 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.

[0085] 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.

[0086] 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.

[0087] 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.

[0088] 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.

[0089] 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.

[0090] 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.

[0091] 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.

[0092] 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 signals 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.

[0093] 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.

[0094] 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.

[0095] Figure 2 Examples of multiple parameter sets 201 are shown. For example... Figure 2 As shown, multiple parameter sets 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 set 201. For example, the RE of the reference parameter set 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.

[0096] Alternatively or additionally, the number of OFDM symbols per slot may be determined based on p (e.g., subcarrier spatial configuration).203 Here, for example, a slot configuration of 0 (e.g., the number of OFDM symbols 203 per slot may be 14) and / or a slot configuration (e.g., the number of OFDM symbols 203 per slot may be 7).

[0097] 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.

[0098] Figure 3 A subframe 369 may include Symbol 387. Additionally or alternatively, 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) 891, 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. Additionally or alternatively, 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.

[0099] Alternatively or concurrently, 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), may be employed. 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.

[0100] 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 pair (k,l), where `k` is the index in the frequency domain, and `l` refers to the symbol position in the time domain. The resource element (k,l)389 on antenna port p and the subcarrier spacing configuration p are represented as (k,l). p,μ Physical resource block 391 is limited to the frequency domain. A continuous subcarrier. Physical resource block 391 in the frequency domain from 0 to... Numbering. 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.

[0101] 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).

[0102] UE 102 can monitor a candidate set of PDCCHs (e.g., PDCCH candidates) in one or more control resource sets (e.g., CORESET) on the active DL bandwidth portion (BWP) of each active serving cell, based on the corresponding search space set. Here, the term "monitor" may imply that UE 102 attempts to decode each PDCCH (e.g., the candidate set of PDCCHs) according to the monitored DCI format. Additionally, the PDCCH candidates may be candidates for DL ​​control channels that may be mapped, allocated, and / or transmitted.

[0103] The candidate set of PDCCHs that UE 102 needs to monitor can be defined based on a search space set (e.g., also simply referred to as the search space). UE 102 can monitor the candidate set of PDCCHs in the search space. The search space set may include a common search space (CSS, UE common search space) and / or a user equipment-specific search space (USS, UE-specific search space).

[0104] That is, CSS and / or USS can be defined (e.g., configured) in the region of the DL control channel. For example, CSS can be used to transmit DCI to multiple UEs 102. For example, a Type0-PDCCH common search space can be defined for one or more DCI formats having a CRC scrambled by SI-RNTI. Additionally or alternatively, a Type1-PDCCH common search space can be defined for DCI formats having a CRC scrambled by RA-RNTI, temporary C-RNTI, and / or C-RNTI. Additionally or alternatively, a Type3-PDCCH common search space can be defined for DCI formats having a CRC scrambled by C-RNTI and / or CS-RNTI.

[0105] The USS can be used to transmit DCI to a specific UE 102. For example, the USS can be determined based on a Radio Network Temporary Identifier (RNTI) (e.g., C-RNTI). For example, the USS can be defined for a DCI format with a CRC scrambled by C-RNTI and / or CS-RNTI.

[0106] Here, gNB 160 can transmit first information for configuring (e.g., determining) one or more CORESETs using RRC messages. For example, for each DL BWP in a DL BWP (e.g., each DL BWP in the serving cell), gNB 106 can transmit first information for configuring that one or more CORESETs using RRC messages. For example, the first information may include information for configuring the index of the CORESET. Additionally, the first information may include information for configuring multiple consecutive symbols of the CORESET. Furthermore, the first information may include information for configuring the resource block set of the CORESET.

[0107] Here, the index "0" of the CORESET (i.e., the value "0" of the CORESET, CORESET#0) can be configured using the MIB and / or SIB. For example, the index "0" of the CORESET can be used to identify a common CORESET configured in the MIB and / or SIB. That is, the index of a CORESET other than the value "0" can be configured as the index of the CORESET. Additionally, the index of a CORESET with the value "0" can be configured using CORESET-zero information. Furthermore, the index "0" of the CORESET can be configured using dedicated RRC messages (i.e., UE-specific RRC messages and / or serving cell-specific RRC messages). That is, the gNB 160 can transmit information for configuring a CORESET with index "0" (i.e., CORESET#0) using the MIB. Additionally or alternatively, the gNB 160 can transmit information for configuring CORESET#0 using the SIB. Alternatively, the gNB 160 may transmit information for configuring CORESET#0 by using a dedicated RRC message.

[0108] Here, CORESET#0 can be configured for the initial BWP (e.g., the initial DL BWP). Here, the gNB 160 can transmit information for the initial BWP (e.g., the initial BWP) using RRC messages (e.g., MIB, SIB, and / or dedicated RRC messages). Additionally, the index of the initial BWP (e.g., the initial DL BWP) can be "0". That is, index "0" (e.g., value "0") can be applied (e.g., defined) for the initial BWP (e.g., the initial DLBWP). For example, (e.g., for a primary cell), the initial BWP (i.e., the BWP with index "0") can be the BWP used for initial access. Additionally or alternatively, (e.g., for a secondary cell), the initial BWP (i.e., the BWP with index "0") can be the BWP configured for the UE to first operate at the secondary cell activation point.

[0109] Here, gNB 160 can transmit information about the index used to configure the DL BWP (e.g., an index other than index "0") by using RRC messages (e.g., MIB, SIB, and / or dedicated RRC messages). Additionally, gNB 160 can transmit information about the index used to configure the UL BWP (e.g., an index other than index "0") by using RRC messages (e.g., MIB, SIB, and / or dedicated RRC messages). That is, the index of the DL BWP can be used to identify the DL BWP. Additionally, the index of the UL BWP can be used to identify the ULBWP. UE 102 can identify the DL BWP based on its index. Additionally, UE 102 can identify the UL BWP based on its index.

[0110] As mentioned above, CORESET#0 can be referred to as a public CORESET. Additionally, CORESETs other than CORESET#0 can be referred to as UE-specific CORESETs. That is, a CORESET with an index "X" other than index "0" (e.g., X = 1, 2, 3, ...) can be referred to as a UE-specific CORESET. For example, gNB 160 can transmit information for configuring UE-specific CORESETs (e.g., the index of the UE-specific CORESET) using dedicated RRC messages.

[0111] Additionally or alternatively, a search space set (e.g., a set of CSSs and / or USSs) may be configured for each of the one or more CORESETs. That is, the search space set may be associated with a CORESET. For example, UE 102 may monitor PDCCHs (e.g., PDCCH candidates) in the CSS set associated with CORESET#0. Additionally, UE 102 may monitor PDCCHs (e.g., PDCCH candidates) in CSS sets not associated with CORESET#0. Additionally, the UE may monitor PDCCHs (e.g., PDCCH candidates) in USSs (e.g., USS not associated with a USS). Furthermore, for example, a search space set may be configured for each DL BWP. That is, a search space set may be configured for each DL BWP in the serving cell.

[0112] Additionally or alternatively, gNB 160 may transmit second information for configuring search space sets using RRC messages. For example, the second information may be configured for each search space set. For example, the second information may include information for configuring the index of the search space set. Additionally or alternatively, the second information may include information for configuring the index of the CORESET associated with the search space set. Additionally or alternatively, the second information may include information for indicating the PDCCH monitoring period and / or PDCCH monitoring offset in which UE 102 monitors PDCCHs in the search space set. Additionally or alternatively, the second information may include information for indicating the PDCCH monitoring mode within a time slot. For example, information indicating the PDCCH monitoring mode may be used to indicate a first symbol within the time slot for PDCCH monitoring. For example, UE 102 may determine the PDCCH monitoring timing based on the PDCCH monitoring periodicity, PDCCH monitoring offset, and / or PDCCH monitoring mode within the time slot.

[0113] Additionally or alternatively, the second information may include information indicating the type of search space set (e.g., information indicating whether the search space set is a CSS or a USS). Additionally or alternatively, the second information may include information instructing UE 102 to monitor one or more DCI formats of the PDCCH in the search space set accordingly. For example, if the search space set is a CSS (e.g., if the search space set is configured as CSS), DCI format 0_0 and / or DCI format 1_0 may be configured to monitor the PDCCH (e.g., a PDCCH candidate). Here, the DCI format used to monitor the PDCCH in the CSS may be scrambled by C-RNTI, CS-RNTI, RA-RNTI, temporary C-RNTI, SI-RNTI, and / or a first RNTI.

[0114] Additionally or alternatively, if the search space set is a USS (e.g., if the search space set is configured as a USS), then DCI formats 0_0, 1_0, 0_Y, and / or 1_X can be configured to monitor PDCCHs (e.g., PDCCH candidates). Additionally or alternatively, if the search space set is a USS, then DCI formats 0_1, 1_1, 0_Y, and / or 1_X can be configured to monitor PDCCHs (e.g., PDCCH candidates). For example, if the search space set is a USS, either the first set of DCI formats (e.g., DCI formats 0_0, 1_0, and / or 0_Y and / or 1_X) or the second set of DCI formats (e.g., DCI formats 0_1, 1_1, 0_Y, and / or 1_X) can be configured to monitor PDCCHs (e.g., PDCCH candidates). For example, if the search space set is a USS, either the third set of DCI formats (e.g., DCI format 0_Y and / or DCI format 1_X) or the fourth set of DCI formats (e.g., DCI format 0_1 ​​and / or DCI format 1_1) can be configured to monitor the PDCCH. Alternatively, if the search space set is a USS, either the fifth set of DCI formats (e.g., DCI format 0_Y and / or DCI format 1_X) or the sixth set of DCI formats (e.g., DCI format 0_0 and / or DCI format 1_0) can be configured to monitor the PDCCH. Here, the DCI format used for monitoring the PDCCH in the USS can be scrambled by C-RNTI, CS-RNTI, and / or the first RNTI. For example, second information can be configured for each search space set. That is, second information can be configured for each search space set within the search space set.

[0115] Here, the index "0" of the search space set (i.e., the value "0" of the search space set) can be configured using the MIB and / or SIB. For example, the index "0" of the search space set can be used to identify a common search space set configured in the MIB and / or SIB. That is, the index of a search space set other than the value "0" can be configured as the index of the search space. Additionally, the index of a search space set with the value "0" can be configured using information about search space - zero. Furthermore, the index "0" of the search space set can be configured using dedicated RRC messages (i.e., UE-specific RRC messages and / or serving cell-specific RRC messages). That is, the gNB 160 can transmit information for configuring a search space set with index "0" (i.e., search space set #0) using the MIB. Alternatively or additionally, the gNB 160 can transmit information for configuring search space set #0 using the SIB. Alternatively or additionally, the gNB 160 can transmit information for configuring search space set #0 using dedicated RRC messages. Here, the search space set #0 can be configured for the initial BWP (e.g., the initial DL BWP).

[0116] As described above, search space set #0 can be referred to as the common search space set. Additionally, search space sets other than search space set #0 can be referred to as UE-specific search space sets. That is, a search space set with an index "X" other than index "0" (e.g., X = 1, 2, 3, ...) can be referred to as a UE-specific search space set. For example, gNB 160 can transmit information for configuring UE-specific search space sets (e.g., the index of the UE-specific search space set) using dedicated RRC messages.

[0117] Here, for example, for the serving cell, gNB 160 can configure four DL BWP sets (e.g., up to four DL BWPs, one DL BWP set) using RRC messages (e.g., for reception by UE 102). Additionally or alternatively, gNB 160 can indicate active DL BWPs using the DCI format for downlink. For example, for each DL BWP in the DL BWP set, gNB 160 can configure the subcarrier spacing, cyclic prefix, number of consecutive PRB491s (e.g., PRB bandwidth), and / or index (e.g., DL BWP index) in that DL BWP set using RRC messages.

[0118] Alternatively, for the serving cell, the gNB 160 can configure four UL BWP sets (e.g., up to four UL BWPs, one UL BWP set) using RRC messages (e.g., for transmission by UE 102). Alternatively, the gNB 160 can indicate active UL BWPs using the DCI format for uplink. Alternatively, for each UL BWP in the ULBWP set, the gNB 160 can configure the subcarrier spacing, cyclic prefix, number of consecutive PRB 491s (e.g., PRB bandwidth), and index (e.g., UL BWP index) in that UL BWP set using RRC messages.

[0119] Alternatively or additionally, UE 102 may perform reception on the PDCCH and / or PDSCH in the DL BWP based on the configuration used for the DL BWP. Alternatively or additionally, UE 102 may perform this based on the configuration used for the UL BWP.

[0120] Figure 5 An example of uplink transmission is shown. For example... Figure 5 As shown, simultaneous transmission of PUCCH and PUSCH for UL signal transmission can be supported. As mentioned above, the UL signal may include an uplink physical channel and / or uplink physical signals. Additionally or alternatively, the UL signal may include uplink data (e.g., UL-SCH) and / or UCI (e.g., HARQ-ACK, CSI (e.g., non-periodic CSI, semi-persistent CSI, and / or periodic CSI) and / or SR).

[0121] That is, UE 102 can perform simultaneous transmission of PUCCH and PUSCH in time slots and / or symbols (e.g., at the same timing, in the same time context, when the occupancy of UL signals (e.g., each of the UL signals) overlaps in at least one symbol and / or at least one time slot). For example, UE 102 can perform simultaneous transmission of UCI on PUCCH and uplink data (e.g., and / or UCI) on PUSCH. Here, simultaneous transmission of PUCCH and PUSCH on the same serving cell can be supported. Additionally or alternatively, simultaneous transmission of PUCCH and PUSCH on different serving cells can be supported. That is, simultaneous transmission of PUCCH and PUSCH on the same serving cell may not be supported.

[0122] Additionally or alternatively, the gNB 160 may transmit third information indicating (e.g., configuring) the simultaneous transmission of PUCCH and PUSCH configured (e.g., indicating and / or allowing). For example, the gNB 160 may configure the simultaneous transmission of PUCCH and PUSCH for the serving cell. For example, the gNB 160 may transmit information for configuring the index of the serving cell (e.g., along with the third information) using RRC messages. Additionally or alternatively, the gNB 160 may transmit information for configuring the index of the UL BWP (e.g., along with the third information) using RRC messages.

[0123] That is, the gNB 160 can be configured with the serving cell (e.g., the index of the serving cell) associated with the simultaneous transmission of PUCCH and PUSCH. For example, the gNB 160 can be configured with the serving cell on which the simultaneous transmission of PUCCH and PUSCH is performed.

[0124] Alternatively or additionally, UE 102 may perform simultaneous transmission of PUCCH and PUSCH on a serving cell (e.g., a serving cell configured with third information). For example, UE 102 may perform simultaneous transmission of PUCCH and PUSCH only on a serving cell (e.g., a serving cell configured with third information). Alternatively or additionally, UE 102 may perform (e.g., may not be allowed to perform) simultaneous transmission of PUCCH and PUSCH on a non-serving cell (e.g., a serving cell not associated with third information (e.g., no third information configured)).

[0125] Additionally, the gNB 160 can be configured with UL BWPs (e.g., indexes of ULBWPs) associated with the simultaneous transmission of PUCCH and PUSCH. For example, the gNB 160 can be configured with UL BWPs executed on the simultaneous transmission of PUCCH and PUSCH.

[0126] Alternatively or additionally, UE 102 may perform simultaneous transmission of PUCCH and PUSCH on a UL BWP (e.g., a UL BWP configured with third information). For example, UE 102 may perform simultaneous transmission of PUCCH and PUSCH only on a UL BWP (e.g., a UL BWP configured with third information). Alternatively or additionally, UE 102 may not perform (e.g., may not be allowed to perform) simultaneous transmission of PUCCH and PUSCH on a UL BWP (e.g., a UL BWP not associated with third information (e.g., not configured with third information)).

[0127] That is, gNB 160 can be configured with a serving cell and / or UL BWP associated with the transmission of PUCCH and PUSCH. For example, gNB 160 can be configured with a serving cell and / or UL BWP on which the transmission of PUCCH and PUSCH is performed. Furthermore, UE 102 can perform simultaneous transmission of PUCCH and PUSCH only on the serving cell (e.g., a serving cell configured with third information) and / or the UL BWP (e.g., a UL BWP configured with third information). Additionally or alternatively, UE 102 can perform (e.g., may not be allowed to perform) simultaneous transmission of PUCCH and PUSCH not on the serving cell (e.g., a serving cell not associated with third information) and / or the UL BWP (e.g., a UL BWP not associated with third information).

[0128] Additionally or alternatively, gNB 160 can configure third information for a special cell. For example, gNB 160 can configure third information for a special cell along with (e.g., together with) the index of a secondary cell. That is, gNB 160 can configure a secondary cell associated with the transmission of PUCCH and PUSCH. For example, gNB 160 can configure a secondary cell on which PUCCH transmission and PUSCH transmission on the special cell are performed simultaneously. That is, UE 102 can perform simultaneous transmission of PUCCH on the special cell and PUSCH on the secondary cell. Furthermore, the special cell can be the serving cell for which the third information is configured. In addition, the secondary cell can be the serving cell associated with the third information (e.g., the serving cell configured with (e.g., together with) the third information).

[0129] Additionally or alternatively, gNB 160 can configure third information for a specific cell along with (e.g., together with) the index of the UL BWP (e.g., the index of the UL BWP of the specific cell and / or the index of the UL BWP of the secondary cell). That is, gNB 160 can configure the UL BWP associated with the transmission of PUCCH and PUSCH. For example, gNB 160 can configure the UL BWP (e.g., the UL BWP of the secondary cell) on which PUSCH transmission is performed simultaneously with the PUCCH transmission on the UL BWP (e.g., the UL BWP of the specific cell). That is, UE 102 can perform simultaneous transmission of PUCCH (e.g., the UL BWP of the specific cell) and PUSCH (e.g., the UL BWP of the secondary cell) on the UL BWP. And, the UL BWP (e.g., the UL BWP of the specific cell) can be the UL BWP for which third information is configured. Additionally, a UL BWP (e.g., a UL BWP for a secondary cell) can be a UL BWP associated with third information (e.g., a UL BWP configured with (e.g., together with) third information).

[0130] Additionally or alternatively, gNB 160 may configure third information for each serving cell. For example, gNB 160 may configure third information for each of a special cell (e.g., a primary cell and / or a primary-secondary cell) and / or a secondary cell. Furthermore, gNB 160 may configure serving cells associated with PUCCH and PUSCH transmissions (e.g., performing simultaneous PUCCH and PUSCH transmissions). That is, UE 102 may perform simultaneous PUCCH and PUSCH transmissions on serving cells (e.g., serving cells associated with third information (e.g., serving cells configured with third information)). Additionally or alternatively, UE 102 may not perform (e.g., may not be allowed) PUCCH and PUSCH transmissions on serving cells (e.g., serving cells not associated with third information (e.g., serving cells not configured with third information)).

[0131] Additionally or alternatively, gNB 160 may configure third information for each UL BWP. For example, gNB 160 may configure third information for each of the UL BWPs (e.g., the UL BWP of the primary cell and / or the UL BWPs of the primary and secondary cells) and / or the UL BWPs of the secondary cell. Furthermore, gNB 160 may configure UL BWPs associated with PUCCH and PUSCH transmissions (e.g., performing simultaneous PUCCH and PUSCH transmissions). That is, UE 102 may perform simultaneous PUCCH and PUSCH transmissions on UL BWPs (e.g., UL BWPs associated with third information (e.g., UL BWPs configured with third information)). Additionally or alternatively, UE 102 may not perform (e.g., may not be allowed) PUCCH and PUSCH transmissions on UL BWPs (e.g., UL BWPs not associated with third information (e.g., UL BWPs without third information)).

[0132] As described above, the serving cell associated with the simultaneous transmission of PUCCH and PUSCH (e.g., third information) can be a special cell (e.g., a primary cell and / or a primary-secondary cell) and / or a secondary cell. Additionally, the serving cell configured for the simultaneous transmission of PUCCH and PUSCH (e.g., third information) can be a special cell (e.g., a primary cell and / or a primary-secondary cell) and / or a secondary cell. Alternatively or additionally, the UL BWP associated with the simultaneous transmission of PUCCH and PUSCH (e.g., third information) can be the UL BWP of the special cell (e.g., the primary cell and / or the primary-secondary cell) and / or the UL BWP of the secondary cell. Alternatively or additionally, the UL BWP configured for the simultaneous transmission of PUCCH and PUSCH (e.g., third information) can be the UL BWP of the special cell (e.g., the primary cell and / or the primary-secondary cell) and / or the UL BWP of the secondary cell.

[0133] In some specific implementations, for the sake of simplicity, it can be assumed that the serving cell associated with the simultaneous transmission of PUCCH and PUSCH (e.g., third information) described herein is included in serving cells configured with the simultaneous transmission of PUCCH and PUSCH (e.g., third information). Additionally, it can be assumed that the UL BWP associated with the simultaneous transmission of PUCCH and PUSCH (e.g., third information) described herein is included in UL BWPs configured with the simultaneous transmission of PUCCH and PUSCH (e.g., third information).

[0134] Additionally, it can be assumed that the serving cells described herein that are not associated with simultaneous transmission of PUCCH and PUSCH (e.g., third information) are included in serving cells where simultaneous transmission of PUCCH and PUSCH (e.g., third information) is not configured. Furthermore, it can be assumed that the ULBWPs described herein that are not associated with simultaneous transmission of PUCCH and PUSCH (e.g., third information) are included in UL BWPs where simultaneous transmission of PUCCH and PUSCH (e.g., third information) is not configured.

[0135] That is, as described above, gNB 160 can be configured with third information and (e.g., together with, associated with) the index of the serving cell and / or the index of the UL BWP. Furthermore, UE 102 can transmit PUCCH and PUSCH simultaneously on the serving cell and / or UL BWP where the third information is configured. Alternatively, UE 102 may not transmit PUCCH and PUSCH simultaneously on the serving cell and / or UL BWP where the third information is not configured (e.g., execution may be disallowed).

[0136] Figure 6 An example of uplink transmission priority is shown. For example... Figure 6As shown, the priority of UL signals can be defined (e.g., configured, indicated, and / or specified). As described above, UL signals may include uplink physical channels and / or uplink physical signals. Additionally or alternatively, UL signals may be uplink data (e.g., UL-SCH) and UCIs (e.g., HARQ-ACK, CSIs (e.g., aperiodic CSI, semi-persistent CSI, and / or periodic CSI) and / or SR). Here, the identification (e.g., definition, specification) of the priority of aperiodic CSI can be considered the same as that of uplink data (e.g., UL-SCH). For example, priorities for uplink data (e.g., and / or aperiodic CSI) and / or UCIs (e.g., HARQ-ACK, CSIs (e.g., semi-persistent CSI, and / or periodic CSI) and / or SR) can be defined (e.g., configured, indicated, and / or specified).

[0137] For example, for uplink data transmission (e.g., UL-SCH transmission), priority can be identified based on indications (e.g., priority indicators) included in the DCI format used for uplink (e.g., the DCI format used for scheduling PUSCH). For example, if UE 102 detects (e.g., decodes, receives) a DCI format including an indication set to a value "0", UE 102 can identify the corresponding PUSCH transmission (e.g., the corresponding uplink data transmission, the corresponding UL-SCH transmission) as low priority. Additionally or alternatively, if UE 102 detects a DCI format including an indication set to a value "1", UE 102 can identify the corresponding PUSCH transmission as high priority.

[0138] Here, aperiodic CSI reports on the PUSCH (e.g., aperiodic CSI reports (e.g., aperiodic CSI reports along with uplink data transmission on the PUSCH)) can be considered the same as uplink data transmission on the PUSCH (e.g., UL-SCH transmission). For example, gNB 106 can transmit a DCI format that triggers a trigger state (e.g., aperiodic CSI trigger state, aperiodic CSI report). Furthermore, UE 102 can perform aperiodic CSI reporting on the PUSCH based on decoding (e.g., detecting, receiving) the DCI format that triggers the trigger state. Here, the trigger state is initiated (e.g., indicated) by using the CSI request field in the DCI format. That is, gNB 106 can transmit a DCI format including a CSI request field set to trigger aperiodic CSI reporting. Furthermore, UE 102 can perform aperiodic CSI reporting on the PUSCH based on decoding the DCI format including a CSI request field set to trigger aperiodic CSI reporting.

[0139] Alternatively or additionally, for uplink data transmission, priority can be identified based on the RNTI used to scramble the CRC (e.g., CRC parity bit) attached to the DCI format used for uplink (e.g., the DCI format used for scheduling PUSCH). For example, if UE 102 detects (e.g., decodes, receives) a DCI format with a CRC scrambled by C-RNTI, UE 102 can identify the corresponding PUSCH transmission (e.g., the corresponding uplink data transmission, the corresponding UL-SCH transmission) as low priority. Alternatively or additionally, if UE 102 detects a DCI format with a CRC scrambled by MCS-C-RNTI and / or a first RNTI, UE 102 can identify the corresponding PUSCH transmission (e.g., the corresponding uplink data transmission, the corresponding UL-SCH transmission) as high priority.

[0140] Alternatively or additionally, for uplink data transmission, priority can be identified based on the DCI format used for the uplink (e.g., the DCI format used for scheduling PUSCH). For example, if UE 102 detects (e.g., decodes, receives) DCI format 0_0 and / or DCI format 0_1, UE 102 can identify the corresponding PUSCH transmission (e.g., the corresponding uplink data transmission, the corresponding UL-SCH transmission) as low priority. Alternatively or additionally, if UE 102 detects DCI format 0_Y, UE 102 can identify the corresponding PUSCH transmission as high priority.

[0141] Here, it can be assumed that PUSCH transmissions identified as low priority (e.g., uplink data (e.g., UL-SCH) and / or aperiodic CSI) described herein are included in low-priority PUSCH transmissions (e.g., low-priority uplink data (e.g., UL-SCH) and / or low-priority aperiodic CSI). Additionally, it can be assumed that PUSCH transmissions identified as high priority (e.g., uplink data (e.g., UL-SCH) and / or aperiodic CSI) described herein are included in high-priority PUSCH transmissions (e.g., high-priority uplink data (e.g., UL-SCH) and / or high-priority aperiodic CSI).

[0142] Additionally or alternatively, for HARQ-ACK transmissions (e.g., on PUSCH and / or PUCCH), priority (e.g., the DCI format for scheduling PDSCH) can be identified based on indications (e.g., priority indicators) included in the DCI format used for the downlink. For example, if UE 102 detects (e.g., decodes, receives) a DCI format including an indication set to a value "0", UE 102 can identify the HARQ-ACK (e.g., HARQ-ACK transmission) for the corresponding PDSCH transmission (e.g., the corresponding PDSCH transmission scheduled using a DCI format including an indication set to a value "0") as low priority. Alternatively or alternatively, if UE 102 detects a DCI format including an indication set to a value "1", UE 102 can identify the HARQ-ACK (e.g., HARQ-ACK transmission) for the corresponding PDSCH transmission as high priority.

[0143] Additionally or alternatively, for HARQ-ACK transmissions, priority can be identified based on the RNTI used to scramble the CRC (e.g., CRC parity bit) attached to the DCI format used for downlink (e.g., the DCI format used for scheduling PDSCH). For example, if UE 102 detects (e.g., decodes, receives) a DCI format with a CRC scrambled by C-RNTI, UE 102 can identify the HARQ-ACK (e.g., HARQ-ACK transmission) used for the corresponding PDSCH transmission (e.g., the corresponding PDSCH transmission scheduled using a DCI format with a CRC scrambled by C-RNTI) as having low priority. Additionally or alternatively, when UE 102 detects a DCI format having a CRC scrambled by MCS-C-RNTI and / or a first RNTI, UE 102 may identify that the HARQ-ACK (e.g., HARQ-ACK transmission) used for the corresponding PDSCH transmission (e.g., the corresponding PDSCH transmission scheduled by using a DCI format having a CRC scrambled by MCS-C-RNTI and / or a first RNTI) is of high priority.

[0144] Alternatively or additionally, for HARQ-ACK transmissions, priority can be identified based on the DCI format used for the downlink (e.g., the DCI format used for scheduling PDSCH). For example, if UE 102 detects (e.g., decodes, receives) DCI format 1_0 and / or DCI format 1_1, UE 102 can identify the HARQ-ACK (e.g., HARQ-ACK transmission) used for the corresponding PDSCH transmission (e.g., the corresponding PDSCH transmission scheduled using DCI format 1_0 and / or DCI format 1_1) as having low priority. Alternatively or additionally, if UE 102 detects DCI format 1_X, UE 102 can identify the HARQ-ACK (e.g., HARQ-ACK transmission) used for the corresponding PDSCH transmission (e.g., the corresponding PDSCH transmission scheduled using DCI format 1_X) as having high priority.

[0145] Here, it can be assumed that HARQ-ACK transmissions identified as low priority (e.g., HARQ-ACK) described herein are included in low-priority HARQ-ACK transmissions (e.g., low-priority HARQ-ACK). Additionally, it can be assumed that HARQ-ACK transmissions identified as high priority (e.g., HARQ-ACK) described herein are included in high-priority HARQ-ACK transmissions (e.g., high-priority HARQ-ACK).

[0146] Additionally or alternatively, gNB 160 may transmit information regarding the configuration for semi-persistent CSI reporting (e.g., and / or the configuration for semi-persistent CSI-RS) using RRC messages. Furthermore, gNB 160 may transmit a DCI format activating the semi-persistent CSI trigger state. For example, the DCI format for uplink may include a CSI request field indicating a semi-persistent CSI trigger state to be activated or deactivated. And, based on decoding the DCI format activating the semi-persistent CSI trigger state (e.g., the DCI format for uplink), UE 102 may perform semi-persistent CSI reporting on the PUSCH based on the semi-persistent CSI reporting configuration. That is, gNB 160 may transmit a DCI format including a CSI request set to activate semi-persistent reporting (e.g., the DCI format for uplink). Furthermore, based on decoding the DCI format (e.g., DCI format) including the CSI request field set to activate semi-persistent CSI reporting, UE 102 can execute semi-persistent CSI reporting on PUSCH according to the configuration of semi-persistent scheduling.

[0147] Additionally or alternatively, gNB 160 may transmit information regarding the configuration for periodic CSI reporting (e.g., and / or the configuration for periodic CSI-RS) using RRC messages. Furthermore, UE 102 may perform periodic CSI reporting on the PUCCH based on the periodic CSI reporting configuration. Here, UE 102 may perform periodic CSI reporting on the PUSCH if it will transmit a PUSCH that overlaps with the PUCCH containing periodic CSI reporting. That is, UE 102 may perform periodic CSI reporting on the PUSCH if it will transmit a PUSCH that overlaps with the periodic CSI reporting on the PUCCH.

[0148] Here, it can be assumed that the configuration for semi-persistent CSI reporting, the configuration for semi-persistent CSI-RS, the configuration for periodic CSI reporting, and / or the configuration for periodic CSI-RS are included in the configuration for CSI reporting.

[0149] Additionally or alternatively, priority for CSI reports (e.g., periodic CSI reports on PUSCH and / or PUCCH, semi-persistent CSI reports on PUSCH) can be identified based on indications (e.g., priority indicators). For example, the gNB 160 can transmit indications of the priority of the configuration for identifying CSI reports by using RRC messages. That is, the gNB 160 can transmit information with configuration information about CSI reports (i.e., information for identifying the priority of CSI reports) by using RRC messages.

[0150] For example, gNB 160 can configure information set to "0" for the first configuration of the CSI report (e.g., CSI configuration-1, the corresponding configuration of the CSI report) (i.e., information used to identify the priority of the CSI report). Furthermore, UE 102 can identify that the CSI report corresponding to the first configuration with information set to "0" is of low priority. Alternatively, gNB 160 can configure information set to "1" for the second configuration of the CSI report (e.g., CSI configuration-2, the corresponding configuration of the CSI report) (i.e., information used to identify the priority of the CSI report). Furthermore, UE 102 can identify that the CSI report corresponding to the second configuration with information set to "1" is of high priority.

[0151] As stated above, the identification (e.g., definition, specification) of priorities used for semi-persistent CSI can be considered the same as that for periodic CSI (e.g., periodic CSI reports on PUCCH). Additionally or alternatively, the identification (e.g., definition, specification) of priorities used for semi-persistent CSI can be considered the same as that for uplink data (e.g., uplink data transmission on PUSCH).

[0152] Here, it can be assumed that CSI reports identified as low priority (e.g., CSI) described herein are included in the low-priority CSI reports (e.g., low-priority CSI). Additionally, it can be assumed that CSI reports identified as high priority (e.g., CSI) described herein are included in the high-priority CSI reports (e.g., high-priority CSI). Here, CSI reports may include only semi-persistent CSI reports and / or periodic CSI reports. That is, CSI reports may exclude non-periodic CSI reports.

[0153] Additionally or alternatively, gNB 160 may transmit information about the configuration for SR transmissions using RRC messages. Furthermore, UE 102 may perform SR transmissions on the PUCCH based on the SR transmission configuration.

[0154] Additionally or alternatively, for SR transmissions (e.g., SR, SR transmission on PUCCH), priority can be identified based on indications (e.g., priority indicators). For example, the gNB 160 can transmit an indication for identifying the priority of an SR transmission using RRC messages. That is, the gNB 160 can transmit information containing configuration information about the SR transmission (i.e., information for identifying the priority of the SR transmission) using RRC messages.

[0155] For example, gNB 160 can configure information set to "0" for a first configuration for SR transmission (e.g., SR configuration-1, the corresponding configuration for SR transmission) (i.e., information used to identify the priority of SR transmission). Furthermore, UE 102 can identify that an SR transmission corresponding to the first configuration with information set to "0" is of low priority. Alternatively, gNB 160 can configure information set to "1" for a second configuration for SR transmission (e.g., SR configuration-2, the corresponding configuration for SR transmission) (i.e., information used to identify the priority of SR transmission). Furthermore, UE 102 can identify that an SR transmission corresponding to the second configuration with information set to "1" is of high priority.

[0156] Here, it can be assumed that SR transmissions identified as low priority (e.g., SR) described herein are included in low-priority SR transmissions (e.g., low-priority SR). Additionally, it can be assumed that SR transmissions identified as high priority (e.g., SR) described herein are included in high-priority SR transmissions (e.g., high-priority SR).

[0157] That is, high-priority PUSCH transmissions (e.g., high-priority uplink data (e.g., UL-SCH) and / or high-priority aperiodic CSI) and / or high-priority UCI transmissions (e.g., high-priority UCI, high-priority PUCCH transmissions) can be defined. Here, high-priority UCI transmissions may include high-priority HARQ-ACK transmissions (e.g., higher-priority HARQ-ACK), high-priority CSI transmissions (e.g., high-priority CSI), and / or high-priority SR transmissions (e.g., high-priority SR). Additionally, low-priority PUSCH transmissions (e.g., low-priority uplink data (e.g., UL-SCH) and / or low-priority aperiodic CSI) and / or low-priority UCI transmissions (e.g., low-priority UCI, low-priority PUCCH transmissions) can be defined. Here, low-priority UCI transmissions may include low-priority HARQ-ACK transmissions (e.g., low-priority HARQ-ACK), low-priority CSI transmissions (e.g., low-priority CSI), and / or low-priority SR transmissions (e.g., low-priority SR).

[0158] Additionally or alternatively, where simultaneous transmission of PUCCH and PUSCH is configured for the serving cell (e.g., and / or UL BWP) and UE 102 will transmit a high-priority PUSCH on the serving cell (and / or UL BWP) that overlaps with the PUCCH used for high-priority UCI on the serving cell (and / or UL BWP), UE 102 may perform simultaneous transmission of high-priority PUSCH and high-priority UCI (e.g., high-priority PUCCH) on the serving cell (and / or UL BWP). That is, UE 102 may perform high-priority uplink data transmission on PUSCH and high-priority UCI transmission on PUCCH on the serving cell (and / or UL BWP). For example, UE 102 may perform high-priority uplink data transmission on PUSCH in a secondary cell and high-priority UCI transmission on PUCCH in a special cell.

[0159] Additionally or alternatively, when simultaneous transmission of PUCCH and PUSCH is configured for the serving cell (e.g., and / or UL BWP) and UE 102 will transmit a high-priority PUSCH on the serving cell (and / or UL BWP) that overlaps with the PUCCH used for low-priority UCI on the serving cell (and / or UL BWP), UE 102 may perform simultaneous transmission of high-priority PUSCH and low-priority UCI (e.g., low-priority PUCCH) on the serving cell (and / or UL BWP). That is, UE 102 may perform high-priority uplink data transmission on PUSCH and low-priority UCI transmission on PUCCH on the serving cell (and / or UL BWP). For example, UE 102 may perform high-priority uplink data transmission on PUSCH in a secondary cell and low-priority UCI transmission on PUCCH in a special cell.

[0160] Additionally or alternatively, where simultaneous transmission of PUCCH and PUSCH is configured for the serving cell (e.g., and / or UL BWP) and UE 102 will transmit low-priority PUSCH on the serving cell (and / or UL BWP) that overlaps with the PUCCH used for high-priority UCI on the serving cell (and / or UL BWP), UE 102 may perform simultaneous transmission of low-priority PUSCH and high-priority UCI (e.g., high-priority PUCCH) on the serving cell (and / or UL BWP). That is, UE 102 may perform low-priority uplink data transmission on PUSCH and high-priority UCI transmission on PUCCH on the serving cell (and / or UL BWP). For example, UE 102 may perform low-priority uplink data transmission on PUSCH in a secondary cell and high-priority UCI transmission on PUCCH in a special cell.

[0161] Additionally or alternatively, where simultaneous transmission of PUCCH and PUSCH is configured for the serving cell (e.g., and / or UL BWP) and UE 102 will transmit low-priority PUSCH on the serving cell (and / or UL BWP) that overlaps with the PUCCH used for low-priority UCI on the serving cell (and / or UL BWP), UE 102 may perform simultaneous transmission of low-priority PUSCH and low-priority UCI (e.g., low-priority PUCCH) on the serving cell (and / or UL BWP). That is, UE 102 may perform low-priority uplink data transmission on PUSCH and low-priority UCI transmission on PUCCH on the serving cell (and / or UL BWP). For example, UE 102 may perform low-priority uplink data transmission on PUSCH in a secondary cell and low-priority UCI transmission on PUCCH in a special cell.

[0162] Additionally or alternatively, in cases where simultaneous transmission of PUCCH and PUSCH is not configured for the serving cell (e.g., and / or UL BWP) and UE 102 will transmit a high-priority PUSCH on the serving cell (and / or UL BWP) that overlaps with the PUCCH used for high-priority UCI on the serving cell (and / or UL BWP), UE 102 may perform the transmission of high-priority PUSCH and high-priority UCI on the PUSCH on the serving cell (and / or UL BWP). That is, UE 102 may perform multiplexing of high-priority UCI and high-priority uplink data on the PUSCH. Specifically, UE 102 may perform the transmission of high-priority uplink data and high-priority UCI on the PUSCH on the serving cell (and / or UL BWP). For example, UE 102 may perform the transmission of high-priority uplink data and high-priority UCI on the PUSCH in the serving cell (e.g., a special cell and / or a secondary cell).

[0163] Additionally or alternatively, in cases where simultaneous transmission of PUCCH and PUSCH is not configured for the serving cell (e.g., and / or UL BWP) and UE 102 will transmit a high-priority PUSCH on the serving cell (and / or UL BWP) that overlaps with a PUCCH used for low-priority UCI on the serving cell (and / or UL BWP), UE 102 may perform high-priority PUSCH transmission on the serving cell (and / or UL BWP). Additionally or alternatively, UE 102 may discard low-priority UCI (e.g., low-priority UCI transmission, low-priority PUCCH transmission). That is, UE 102 may perform high-priority uplink data transmission on PUSCH on the serving cell (and / or UL BWP) and discard low-priority UCI transmission on PUCCH. For example, UE 102 may perform high-priority uplink data transmission on PUSCH in a secondary cell. Furthermore, UE 102 may discard low-priority UCI transmission on PUCCH in a special cell.

[0164] Additionally or alternatively, in cases where simultaneous transmission of PUCCH and PUSCH is not configured for the serving cell (e.g., and / or UL BWP) and UE 102 will transmit low-priority PUSCH on the serving cell (and / or UL BWP) that overlaps with the PUCCH used for high-priority UCI on the serving cell (and / or UL BWP), UE 102 may perform high-priority UCI (e.g., high-priority PUCCH) transmission on the serving cell (and / or UL BWP). Additionally or alternatively, UE 102 may discard low-priority uplink data (e.g., low-priority uplink data transmission, low-priority PUSCH transmission). That is, UE 102 may perform high-priority UCI transmission on PUCCH and low-priority uplink data transmission on PUSCH on the serving cell (and / or UL BWP). For example, UE 102 may perform high-priority UCI transmission on PUCCH in a special cell. Additionally, UE 102 may discard low-priority uplink data transmission on PUSCH in a secondary cell.

[0165] Additionally or alternatively, in cases where simultaneous transmission of PUCCH and PUSCH is not configured for the serving cell (e.g., and / or UL BWP) and UE 102 will transmit a low-priority PUSCH on the serving cell (and / or UL BWP) that overlaps with the PUCCH used for low-priority UCI on the serving cell (and / or UL BWP), UE 102 may perform the transmission of low-priority PUSCH and low-priority UCI on the PUSCH on the serving cell (and / or UL BWP). That is, UE 102 may perform multiplexing of low-priority UCI and low-priority uplink data on the PUSCH. Specifically, UE 102 may perform the transmission of low-priority uplink data and low-priority UCI on the PUSCH on the serving cell (and / or UL BWP). For example, UE 102 may perform the transmission of low-priority uplink data and low-priority UCI on the PUSCH in the serving cell (e.g., a special cell and / or a secondary cell).

[0166] Additionally or alternatively, when simultaneous transmission of PUCCH and PUSCH is configured for the serving cell (e.g., and / or UL BWP) and UE 102 will transmit high-priority PUSCH on the serving cell (and / or UL BWP) that overlaps with the PUCCH for high-priority UCI and the PUCCH for low-priority UCI on the serving cell (and / or UL BWP), UE 102 can perform simultaneous transmission of high-priority PUSCH (e.g., and / or low-priority UCI) and high-priority UCI (e.g., high-priority PUCCH) on the serving cell (and / or UL BWP). That is, UE 102 can perform multiplexing of low-priority UCI with high-priority uplink data on PUSCH. In other words, UE 102 can perform transmission of high-priority uplink data (e.g., and / or low-priority UCI) on PUSCH and high-priority UCI on PUCCH on the serving cell (and / or UL BWP). For example, UE 102 can perform the transmission of high-priority uplink data (e.g., and / or low-priority UCI) on the PUSCH in a secondary cell and high-priority UCI on the PUCCH in a special cell.

[0167] Additionally or alternatively, when simultaneous transmission of PUCCH and PUSCH is configured for the serving cell (e.g., and / or UL BWP) and UE 102 will transmit low-priority PUSCH overlapping with the PUCCH for high-priority HARQ-ACK and the PUCCH for low-priority UCI on the serving cell (and / or UL BWP), UE 102 can perform simultaneous transmission of low-priority PUSCH (e.g., and / or low-priority UCI) and high-priority UCI (e.g., high-priority PUCCH) on the serving cell (and / or UL BWP). That is, UE 102 can perform multiplexing of low-priority UCI with low-priority uplink data on PUSCH. In other words, UE 102 can perform transmission of low-priority uplink data (e.g., and / or low-priority UCI) on PUSCH and high-priority UCI on PUCCH on the serving cell (and / or UL BWP). For example, UE 102 can perform the transmission of low-priority uplink data (e.g., and / or low-priority UCI) on the PUSCH in a secondary cell and high-priority UCI on the PUCCH in a special cell.

[0168] Additionally or alternatively, in cases where simultaneous transmission of PUCCH and PUSCH is not configured for the serving cell (e.g., and / or UL BWP) and UE 102 will transmit high-priority PUSCH on the serving cell (and / or UL BWP) that overlaps with the PUCCH for high-priority UCI and the PUCCH for low-priority UCI on the serving cell (and / or UL BWP), UE 102 may perform high-priority PUSCH and high-priority UCI transmission on the PUSCH on the serving cell (and / or UL BWP). That is, UE 102 may perform multiplexing of high-priority UCI and high-priority uplink data on the PUSCH. Additionally or alternatively, UE 102 may discard low-priority UCI (e.g., low-priority UCI transmission). That is, UE 102 may perform high-priority uplink data and high-priority UCI transmission on the PUSCH on the serving cell (and / or UL BWP) and discard low-priority UCI transmission on the PUCCH. For example, UE 102 can perform the transmission of high-priority uplink data and high-priority UCI on the PUSCH in a secondary cell. Additionally, UE 102 can discard low-priority UCI on the PUCCH in a special cell.

[0169] Additionally or alternatively, in cases where simultaneous transmission of PUCCH and PUSCH is not configured for the serving cell (e.g., and / or UL BWP) and UE 102 will transmit low-priority PUSCH on the serving cell (and / or UL BWP) that overlaps with the PUCCH for high-priority HARQ-ACK and the PUCCH for low-priority UCI on the serving cell (and / or UL BWP), UE 102 may perform high-priority UCI transmission on the PUCCH on the serving cell (and / or UL BWP). Additionally or alternatively, UE 102 may discard low-priority uplink data (e.g., low-priority PUSCH transmission) and low-priority UCI (e.g., low-priority UCI transmission). That is, UE 102 may perform high-priority UCI transmission on the PUCCH on the serving cell (and / or UL BWP) and discard low-priority PUSCH and low-priority UCI transmissions on the PUCCH. For example, UE 102 may perform high-priority UCI transmission on the PUCCH in a specific cell. Additionally, UE 102 can discard low-priority uplink data transmissions on the PUSCH in secondary cells. Furthermore, UE 102 can discard low-priority UCI transmissions on the PUCCH in special cells.

[0170] As described above, UE 102 can be configured to switch (e.g., change) the behavior of UL signal transmission for the serving cell (e.g., and / or UL BWP) based on the priority of the UL signal and / or the simultaneous transmission of PUCCH and PUSCH (e.g., third information). Here, as described above, the priority of the UL signal can be identified based on an indication (e.g., configuration and / or indication). Additionally, the priority of the UL signal can be identified based on an RNTI used to scramble the CRC attached to the DCI format (e.g., the DCI format corresponding to the UL signal). Additionally, the priority of the UL signal can be identified based on the DCI format (e.g., the DCI format corresponding to the UL signal). Furthermore, the simultaneous transmission of PUCCH and PUSCH (e.g., third information) is configured for (e.g., associated with) the serving cell (e.g., and / or UL BWP).

[0171] As described above, UE 102 can monitor the PDCCH (e.g., the DCI format for downlink and / or the DCI format for uplink) in the CSS. For example, UE 102 can monitor the PDCCH in the CSS associated with CORESET#0. Additionally, UE 102 can monitor the PDCCH in CSSs not associated with CORESET#0. Furthermore, UE 102 can monitor the PDCCH (e.g., the DCI format for downlink and / or the DCI format for uplink) in the USS. For example, UE 102 can monitor the PDCCH in the USS (e.g., the USS not associated with CORESET#0). Here, the priority of the UL signal may not apply to the UL signal corresponding to the PDCCH detected in the CSS (e.g., the DCI format for downlink and / or the DCI format for uplink). That is, the priority of the UL signal may only apply to the UL signal corresponding to the PDCCH detected in the USS (e.g., the DCI format for downlink and / or the DCI format for uplink). That is, the description related to the priority of the UL signal mentioned above can only be applied to the UL signal corresponding to the PDCCH detected in the USS (e.g., the DCI format for the downlink and / or the DCI format for the uplink).

[0172] That is, regardless of the configuration for simultaneous transmission of PUCCH and PUSCH (e.g., third information) (i.e., whether third information is configured and / or not configured), in the case of PDCCH detected in CSS (e.g., DCI format for downlink and / or DCI format for uplink), UE 102 can perform UL signal transmission corresponding to the PDCCH detected in CSS (e.g., DCI format for downlink and / or DCI format for uplink).

[0173] Additionally or alternatively, the priority of UL signals may not apply to UL signals corresponding to PDCCHs detected in the CSS associated with CORESET#0 (e.g., DCI format for downlink and / or DCI format for uplink). That is, the priority of UL signals may only apply to UL signals corresponding to PDCCHs not associated with CORESET#0 in the USS and / or CSS (e.g., DCI format for downlink and / or DCI format for uplink). In other words, the description relating to the priority of UL signals described above may only apply to UL signals corresponding to PDCCHs not associated with CORESET#0 in the USS and / or CSS (e.g., DCI format for downlink and / or DCI format for uplink).

[0174] That is, regardless of the configuration for simultaneous transmission of PUCCH and PUSCH (e.g., third information) (i.e., whether third information is configured and / or not configured), in the case of a PDCCH (e.g., DCI format for downlink and / or DCI format for uplink) detected in the CSS associated with CORESET#0, UE 102 may perform UL signal transmission (e.g., DCI format for downlink and / or DCI format for uplink) corresponding to the PDCCH detected in the CSS associated with CORESET#0.

[0175] Here, it can be assumed that the UL signal (e.g., UL signal transmission) corresponding to the PDCCH (e.g., DCI format for downlink and / or DCI format for uplink) detected in the CSS is included in the first UL signal. Additionally or alternatively, it can be assumed that the UL signal (e.g., UL signal transmission) corresponding to the PDCCH (e.g., DCI format for downlink and / or DCI format for uplink) detected in the CSS associated with CORESET#0 is included in the first UL signal.

[0176] That is, it can be assumed that uplink data transmission and / or aperiodic CSI reports (e.g., PUSCH transmissions) corresponding to PDCCHs detected in the CSS (e.g., scheduled using a DCI format for uplink) are included in the first PUSCH transmission. Additionally or alternatively, it can be assumed that uplink data transmission and / or aperiodic CSI reports (e.g., PUSCH transmissions) corresponding to PDCCHs detected in the CSS associated with CORESET#0 (e.g., scheduled using a DCI format for uplink) are included in the first PUSCH transmission.

[0177] Additionally, it can be assumed that HARQ-ACK transmissions corresponding to PDSCH (e.g., PDSCH transmissions) scheduled using a PDCCH (e.g., a DCI format for downlink) detected in the CSS are included in the first HARQ-ACK transmission. Alternatively or additionally, it can be assumed that HARQ-ACK transmissions corresponding to PDSCH (e.g., PDSCH transmissions) scheduled using a PDCCH (e.g., a DCI format for downlink) detected in the CSS associated with CORESET#0 are included in the first HARQ-ACK transmission. That is, it can be assumed that PDSCH transmissions (e.g., HARQ-ACK transmissions) corresponding to PDSCH (e.g., PDSCH transmissions) scheduled using a PDCCH (e.g., a DCI format for downlink) detected in the CSS are included in the first PUCCH transmission. Additionally or alternatively, it may be assumed that a PDSCH transmission (e.g., a HARQ-ACK transmission) corresponding to a PDSCH (e.g., a PDSCH transmission) scheduled by using a PDSCH (e.g., a DCI format for the downlink) detected in the CSS associated with CORESET#0 is included in the first PUCCH transmission.

[0178] For example, if UE 102 will transmit a high-priority PUSCH (e.g., a high-priority PUSCH transmission) on the serving cell (and / or UL BWP) that overlaps with the first PUSCH (e.g., the first PUSCH transmission) on the serving cell, UE 102 may perform the first PUSCH transmission. Additionally or alternatively, UE 102 may discard the high-priority PUSCH (e.g., the high-priority PUSCH transmission). That is, UE 102 may perform the first PUSCH transmission on the serving cell (and / or UL BWP) and discard the high-priority PUSCH transmission.

[0179] Additionally or alternatively, if UE 102 will transmit a low-priority PUSCH (e.g., a low-priority PUSCH transmission) on the serving cell (and / or UL BWP) that overlaps with the first PUSCH (e.g., the first PUSCH transmission) on the serving cell, UE 102 may perform the first PUSCH transmission. Additionally or alternatively, UE 102 may discard the low-priority PUSCH (e.g., the low-priority PUSCH transmission). That is, UE 102 may perform the first PUSCH transmission on the serving cell (and / or UL BWP) and discard the low-priority PUSCH transmission.

[0180] Additionally or alternatively, if UE 102 will transmit a first PUSCH (e.g., a first PUSCH transmission) on the serving cell (and / or UL BWP) that overlaps with a high-priority PUSCH (e.g., a high-priority PUSCH transmission) and a low-priority PUSCH (e.g., a low-priority PUSCH transmission) on the serving cell, UE 102 may perform the first PUSCH transmission on the serving cell. Additionally or alternatively, UE 102 may discard both the high-priority PUSCH (e.g., a high-priority PUSCH transmission) and the low-priority PUSCH (e.g., a low-priority PUSCH transmission). That is, UE 102 may perform the first PUSCH transmission on the serving cell (and / or UL BWP) and discard both the high-priority PUSCH transmission and the low-priority PUSCH transmission.

[0181] Additionally or alternatively, if UE 102 will transmit a high-priority HARQ-ACK (e.g., a high-priority PUCCH transmission) on the serving cell (and / or UL BWP) that overlaps with the first HARQ-ACK (e.g., the first PUCCH transmission) on the serving cell, UE 102 may perform the first HARQ-ACK transmission (e.g., the first PUCCH transmission). Additionally or alternatively, UE 102 may discard the high-priority HARQ-ACK transmission (e.g., the high-priority PUCCH transmission). That is, UE 102 may perform the first HARQ-ACK transmission (e.g., the first PUCCH transmission) on the serving cell (and / or UL BWP) and discard the high-priority HARQ-ACK transmission (e.g., the high-priority PUCCH transmission).

[0182] Additionally or alternatively, if UE 102 will transmit a low-priority HARQ-ACK (e.g., a low-priority PUCCH transmission) on the serving cell (and / or UL BWP) that overlaps with the first HARQ-ACK (e.g., the first PUCCH transmission) on the serving cell, UE 102 may perform the first HARQ-ACK transmission. Additionally or alternatively, UE 102 may discard the low-priority HARQ-ACK (e.g., the low-priority PUCCH transmission). That is, UE 102 may perform the first HARQ-ACK transmission (e.g., the first PUCCH transmission) on the serving cell (and / or UL BWP) and discard the low-priority HARQ-ACK transmission (e.g., the low-priority PUCCH transmission).

[0183] Additionally or alternatively, if UE 102 will transmit a first HARQ-ACK (e.g., a first PUCCH transmission) on the serving cell (and / or UL BWP) that overlaps with high-priority HARQ-ACK (e.g., high-priority PUCCH transmission) and low-priority HARQ-ACK (e.g., low-priority PUCCH transmission) on the serving cell, UE 102 may perform the first HARQ-ACK transmission (e.g., the first PUCCH transmission) on the serving cell. Additionally or alternatively, UE 102 may discard both the high-priority HARQ-ACK (e.g., high-priority PUCCH transmission) and the low-priority HARQ-ACK (e.g., low-priority PUCCH transmission). That is, UE 102 may perform the first HARQ-ACK transmission (e.g., the first PUCCH transmission) on the serving cell (and / or UL BWP) and discard both the high-priority HARQ-ACK (e.g., high-priority PUCCH transmission) and the low-priority HARQ-ACK (e.g., low-priority PUCCH transmission).

[0184] That is, if UE 102 will transmit a first PUSCH on the serving cell (and / or UL BWP) that overlaps with a high-priority PUSCH on the serving cell, UE 102 may perform the first PUSCH transmission on the serving cell and discard the high-priority PUSCH transmission. Alternatively or additionally, if UE 102 will transmit a first PUSCH on the serving cell (and / or UL BWP) that overlaps with a low-priority PUSCH on the serving cell, UE 102 may perform the first PUSCH transmission on the serving cell and discard the low-priority PUSCH transmission. Alternatively or additionally, if UE 102 will transmit a first PUSCH on the serving cell (and / or UL BWP) that overlaps with both high-priority and low-priority PUSCH on the serving cell, UE 102 may perform the first PUSCH transmission on the serving cell and discard both high-priority and low-priority PUSCH transmissions.

[0185] Additionally or alternatively, if UE 102 will transmit a PUCCH for first HARQ-ACK on the serving cell (and / or UL BWP) that overlaps with the PUCCH for high-priority HARQ-ACK on the serving cell, UE 102 may perform (e.g., the serving cell) first HARQ-ACK transmission on the PUCCH and discard the high-priority HARQ-ACK transmission. Additionally or alternatively, if UE 102 will transmit a PUCCH for first HARQ-ACK on the serving cell (and / or UL BWP) that overlaps with the PUCCH for low-priority HARQ-ACK on the serving cell, UE 102 may perform (e.g., the serving cell) first HARQ-ACK transmission on the PUCCH and discard the low-priority HARQ-ACK transmission. Additionally or alternatively, if UE 102 will transmit a PUCCH for first HARQ-ACK on the serving cell (and / or UL BWP) that overlaps with the PUCCH for high-priority HARQ-ACK and the PUCCH for low-priority HARQ-ACK on the serving cell, UE 102 may perform (e.g., serving cell) first HARQ-ACK transmission on the PUCCH and discard the high-priority HARQ-ACK transmission and the low-priority HARQ-ACK transmission.

[0186] PUSCH (which may or may not include CSI reports using PUSCH, such as A-CSI on PUSCH, SP-CSI on PUSCH) or PUCCH (including duplicates, if any)) may have a priority index of 0 or a priority index of 1. If no priority index is provided for PUSCH or PUCCH, the priority index is 0. If, in an active DL BWP, the UE monitors PDCCH to detect DCI formats 0_1 and 1_1 or DCI formats 0_2 and 1_2, the priority index may be provided by the priority indicator field. If the UE indicates the ability to monitor PDCCH in an active DL BWP to detect DCI formats 0_1 and 1_1 and to detect DCI formats 0_2 and 1_2, then DCI format 0_1 ​​or DCI format 0_2 may schedule PUSCH transmissions with any priority, and DCI format 1_1 or DCI format 1_2 may schedule PDSCH reception and trigger PUCCH transmissions with corresponding HARQ-ACK information with any priority. If, after resolving the overlap of PUCCH and / or PUSCH transmissions with the same priority index, the UE determines to transmit a first PUCCH with a higher priority index, a PUSCH with a lower priority index, or a second PUCCH, and the transmission of the first PUCCH will overlap with the transmission of the PUSCH or the second PUCCH in time, then the UE will not transmit the PUSCH or the second PUCCH. If, after resolving the overlap of PUCCH and / or PUSCH transmissions with the same priority index, the UE determines to transmit a PUSCH with a higher priority index, a PUCCH with a lower priority index, and the transmission of the PUSCH will overlap with the transmission of the PUCCH in time, then the UE will not transmit the PUCCH. If, after resolving the overlap of PUCCH and / or PUSCH transmissions with the same priority index, the UE determines that it will transmit a first PUSCH with a higher priority index on the serving cell and a second PUSCH with a lower priority index on the same serving cell, and the transmission of the first PUSCH will overlap with the transmission of the second PUSCH in time, then the UE will not transmit the second PUSCH, wherein at least one of the two PUSCHs is not scheduled by DCI format.

[0187] If the UE will transmit CSI reports on overlapping physical channels, the UE can multiplex CSI reports by applying priority rules, taking into account priority indicators (or priority indexes).

[0188] After successfully decoding either DCI format 0_1 ​​or DCI format 0_2, which triggers the aperiodic CSI trigger state, the UE can perform an aperiodic CSI (A-CSI) report using the PUSCH on the serving cell. When two PUSCH allocations are scheduled using DCI format 0_1, the aperiodic CSI report is carried on the second scheduled PUSCH. When more than two PUSCH allocations are scheduled using DCI format 0_1, the aperiodic CSI report is carried on the penultimate scheduled PUSCH. Aperiodic CSI reports carried on PUSCH support both wideband and subband frequency granularity. Aperiodic CSI reports carried on PUSCH support Type I, Type II, and Enhanced Type II CSI.

[0189] After successfully decoding either DCI format 0_1 ​​or DCI format 0_2 to activate the semi-persistent CSI trigger state, the UE can perform a semi-persistent CSI (SP-CSI) report on the PUSCH. DCI format 0_1 ​​and DCI format 0_2 contain a CSI request field indicating whether the semi-persistent CSI trigger state should be activated or deactivated. Semi-persistent CSI reporting on the PUSCH supports Type I, Type II with wideband and subband frequency granularity, and Enhanced Type II CSI. PUSCH resources and MCS can be allocated semi-persistently via uplink DCI.

[0190] CSI reports on the PUSCH can be multiplexed with uplink data on the PUSCH. CSI reports on the PUSCH can also be performed without any multiplexing with uplink data from the UE. Type I CSI feedback is supported for CSI reports on the PUSCH. Type I wideband and subband CSI are supported for CSI reports on the PUSCH. Type II CSI is also supported for CSI reports on the PUSCH.

[0191] This article describes priority handling between A-CSI and SP-CSI based on priority indicators or priority indices.

[0192] In specific implementations, SP-CSI (i.e., activated by a DCI format including a priority indicator (priority index) set to "1") takes precedence over A-CSI (i.e., scheduled by a DCI format including a priority indicator (priority index) set to "0"), based on the value of the priority indicator or priority index. For example, after successfully decoding DCI format 0_1 ​​or DCI format 0_2 that activates the semi-persistent CSI trigger state, the UE can perform a semi-persistent CSI (SP-CSI) report on the PUSCH, and the priority index provided by the priority indicator field in DCI format 0_1 ​​or DCI format 0_2 is set to "1" (referred to in this disclosure as an SP-CSI report with priority index 1). The UE can also perform an aperiodic CSI (A-CSI) report using the PUSCH on the serving cell after successfully decoding DCI format 0_1 ​​or DCI format 0_2 that triggers the aperiodic CSI trigger state, and the priority index provided by the priority indicator field in DCI format 0_1 ​​or DCI format 0_2 is set to "0" (referred to in this disclosure as an A-CSI report with priority index 0). An SP-CSI report with priority index 1 can have a higher priority than an A-CSI report with priority index 0. If an SP-CSI report with priority index 1 and an A-CSI report with priority index 0 conflict, and if the time occupancy of the physical channel scheduled to carry the CSI report overlaps in at least one OFDM symbol and is transmitted on the same carrier, the UE may not send an A-CSI report with priority index 0. The priority handling behavior described herein can be configured by RRC. For example, if an RRC parameter (e.g., SP-CSI_priority_enabler) is configured and / or set to a value indicating that priority processing behavior is enabled, an SP-CSI report with priority index 1 can have a higher priority than an A-CSI report with priority index 0.

[0193] In another specific implementation, A-CSI (i.e., scheduled by a DCI format including a priority indicator set to "0") takes precedence over SP-CSI (i.e., activated by a DCI format including a priority indicator set to "1"), regardless of the value of the priority indicator or priority index. For example, an aperiodic CSI (A-CSI) report using PUSCH can be scheduled by DCI format 0_1 ​​or DCI format 0_2 that triggers the aperiodic CSI trigger state, regardless of whether the priority index is provided in a DCI format and / or whatever value the priority index is set to. If an SP-CSI report activated by a DCI format with or without a priority index (regardless of the priority index value, if provided) conflicts with an A-CSI report, and if the time occupancy of the physical channel scheduled to carry the CSI report overlaps in at least one OFDM symbol and is transmitted on the same carrier, the UE may not send an SP-CSI report. The priority handling behavior described herein can be configured by RRC. For example, if an RRC parameter (e.g., A-CSI_priority_enabler) is configured and / or set to a value indicating that priority processing behavior is enabled, an A-CSI report can have a higher priority than an SP-CSI report, regardless of the value of the priority indicator or priority index.

[0194] In yet another specific implementation, a new factor (e.g., p) considering the value of the priority indicator is added to the equation of the priority rule in the CSI report. That is, the new function / equation Pri iCSI (p, y, k, c, s) can be used for the priority rules of CSI reports, where y = 0 for semi-persistent CSI reports to be carried on PUSCH, y = 1 for non-periodic CSI reports to be carried on PUSCH, y = 2 for semi-persistent CSI reports to be carried on PUCCH, and y = 3 for periodic CSI reports to be carried on PUCCH; k = 0 for CSI reports carrying L1-RSRP or L1-SINR, and k = 1 for CSI reports not carrying L1-RSRP or L1-SINR; c is the serving cell index and N cells It is the value of the high-level parameter maxNro / ServingCells; s is reportConfigID and M sThis is the value of the high-level parameter maxNrofCSI-ReportConfigurations; p is determined by the priority index provided by the DCI format (e.g., DCI format 0_1 ​​and / or DCI format 0_2) for scheduling A-CSI reports and / or activating SP-CSI (e.g., p = 1 if the priority index is 1 (or p = 0); p = 0 if the priority index is 0 (or p = 1); p - 0 if no priority index is provided (or p = 1)). If the associated Priority Index of the first report is... iCSI If the (pykc,s) value is lower (or higher) than the second report, the first CSI report can have a higher priority than the second CSI report. Two CSI reports are considered conflicting if the time occupancy of the physical channel scheduled to carry the CSI report overlaps in at least one OFDM symbol and is transmitted on the same carrier. When the UE is configured to transmit two conflicting CSI reports, the UE may not send a report with a higher (or lower) priority. iCSI CSI reports for (pykc,s) values. This article describes the new function / equation Pri. iCSI Details of (pykc,s).

[0195] For example,

[0196] Pri iCSI (p, y, k, c, s) = 2·N cells ·M s ·y+N cells ·M s ·k+M s ·c+s+p·scale,

[0197] The scale can be indicated, configured, and / or a fixed value in the specification and / or determined by other parameters, and the scale can be any value (e.g., positive values ​​such as 1, 2, 3, negative values ​​-1, -2, -3, -3.6, etc.). For example,

[0198] Pri iCSI (p, y, k, c, s) = 2, N cells ·M s ·(y+p·scale)+N cells ·M s ·k+M s ·c+s,

[0199] The scale can be indicated, configured, is a fixed value in the specification, and / or determined by other parameters, and the scale can be any value (e.g., positive values ​​such as 1, 2, 3, negative values ​​such as -1, -2, -3, -3.6, etc.).

[0200] In cases where A-CSI and SP-CSI have the same priority index or where no priority index is provided, A-CSI may take precedence over SP-CSI. For example, if an SP-CSI report with priority index 1 (or 0) conflicts with an A-CSI report with the same priority index 1 (or 0), and if the time occupancy of the physical channel scheduled to carry the CSI report overlaps in at least one OFDM symbol and is transmitted on the same carrier, the UE may not send the SP-CSI report.

[0201] This article also describes priority handling between SP-CSI and UL-SCH based on priority indicator considerations.

[0202] In specific implementations, based on the value of the priority indicator, SP-CSI (i.e., activated by a DCI format including a priority indicator set to "1") can take precedence over UL-SCH (i.e., scheduled by a DCI format including a priority indicator set to "0"). For example, after successfully decoding DCI format 0_1 ​​or DCI format 0_2 that activates the semi-persistent CSI trigger state, the UE can perform a semi-persistent CSI (SP-CSI) report on the PUSCH, and the priority index provided by the priority indicator field in DCI format 0_1 ​​or DCI format 0_2 is set to "1" (referred to in this disclosure as an SP-CSI report with priority index 1). The UE can also perform UL-SCH using the PUSCH (referred to in this disclosure as UL-SCH with priority index 0) after successfully decoding DCI format 0_1 ​​or DCI format 0_2 that includes a priority indicator field set to "0". An SP-CSI report with priority index 1 can have a higher priority than a UL-SCH with priority index 0. If an SP-CSI report with priority index 1 and a UL-SCH with priority index 0 conflict, and if the time occupancy of physical channels scheduled to carry one or more CSI reports and / or UL-SCH overlaps in at least one OFDM symbol and is transmitted on the same carrier, the UE may not transmit the UL-SCH with priority index 0. The priority handling behavior described herein can be configured by RRC. For example, if an RRC parameter (e.g., SP-CSI_priority_enabler) is configured and / or set to a value indicating that priority handling behavior is enabled, then an SP-CSI report with priority index 1 is considered to have a higher priority than a UL-SCH with priority index 0.

[0203] In another specific implementation, regardless of the priority indicator value, UL-SCH (i.e., scheduled by a DCI format including a priority indicator set to "0") can take precedence over SP-CSI (i.e., activated by a DCI format including a priority indicator set to "1"). For example, UL-SCH using PUSCH can be scheduled by DCI format 0_1 ​​or DCI format 0_2, regardless of whether the priority index is provided in DCI format and / or whatever value the priority index is set to. If an SP-CSI report activated by a DCI format with or without a priority index (regardless of the priority index value, if provided) conflicts with UL-SCH, and if the time occupancy of the physical channel scheduled to carry CSI reports and / or UL-SCH overlaps in at least one OFDM symbol and is transmitted on the same carrier, the UE may not send an SP-CSI report. The priority handling behavior described herein can be configured by RRC. For example, if an RRC parameter (e.g., UL-SCH_priority_enabler) is configured and / or set to a value indicating that priority processing behavior is enabled, then UL-SCH can have a higher priority than the SP-CSI report, regardless of the value of the priority indicator or priority index.

[0204] For cases with the same priority or no priority, UL-SCH takes precedence over SP-CSI. For example, if an SP-CSI report with priority index 1 (or 0) is considered to conflict with a UL-SCH report with the same priority index 1 (or 0), and if the time occupancy of the physical channel scheduled to carry CSI reports and / or UL-SCH overlaps in at least one OFDM symbol and is transmitted on the same carrier, the UE may not send an SP-CSI report.

[0205] For SP-CSI transmissions without UL-SCH, the first actual repeat can be used.

[0206] Any combination of priority processing between A-CSI and SP-CSI and between SP-CSI and UL-SCH as described above can be applied.

[0207] For example, SP-CSI can take precedence over A-CSI as described above, and SP-CSI can take precedence over UL-SCH as described above. In this case, A-CSI can take precedence over UL-SCH. That is, SP-CSI takes precedence over A-CSI, and A-CSI takes precedence over UL-SCH.

[0208] Additionally or alternatively, SP-CSI may take precedence over A-CSI as described above, and UL-SCH may take precedence over SP-CSI as described above. In this case, A-CSI may take precedence over UL-SCH. That is, SP-CSI takes precedence over A-CSI, and A-CSI takes precedence over UL-SCH.

[0209] Alternatively or additionally, A-CSI may take precedence over SP-CSI as described above, and SP-CSI may take precedence over UL-SCH as described above. That is, A-CSI takes precedence over SP-CSI, and SP-CSI takes precedence over UL-SCH. Alternatively or additionally, A-CSI may take precedence over SP-CSI as described above, and UL-SCH may take precedence over SP-CSI as described above. That is, A-CSI takes precedence over UL-SCH, and UL-SCH takes precedence over SP-CSI.

[0210] For example, regardless of the value of the priority indicator, A-CSI can always take precedence over SP-CSI as described above. Similarly, A-CSI can always take precedence over UL-SCH as described above. Furthermore, priority processing between SP-CSI and UL-SCH can be applied (e.g., determined) based on the value of the priority indicator as described above. That is, SP-CSI can take precedence over UL-SCH based on the value of the priority indicator (i.e., A-CSI can take precedence over SP-CSI, and SP-CSI takes precedence over UL-SCH). Additionally, UL-SCH can take precedence over SP-CSI based on the value of the priority indicator (i.e., A-CSI can take precedence over UL-SCH, and UL-SCH takes precedence over SP-CSI). In other words, A-CSI can always take precedence over both SP-CSI and UL-SCH. That is, regardless of the value of the priority indicator, A-CSI can always take precedence over both SP-CSI and UL-SCH. Furthermore, priority processing can be applied between SP-CSI and UL-SCH based on the value of the priority indicator. That is, a priority indicator (e.g., the value of the priority indicator) may not be applied to A-CSI (i.e., A-CSI report). Specifically, UE 102 may not apply a priority indicator (e.g., the value of the priority indicator) to A-CSI (i.e., A-CSI report).

[0211] If the UE is provided with RRC parameters for uplink cancellation (e.g., UplinkCancellation), a search space set and a CI-RNTI provided by ci-RNTI are provided to the UE in one or more serving cells for monitoring PDCCH candidates and detecting DCI format 2_4 using the CI-RNTI provided by ci-RNTI. If a set of symbols indicated by DCI format 2_4 (e.g., having at least one bit value "1" in the corresponding set of bits in DCI format 2_4) includes a symbol of a PUSCH transmission (which repeats) or a symbol of an SRS transmission, and a set of PRBs indicated by DCI format 2_4 (having a corresponding bit value "1" in the corresponding set of bits in DCI format 2_4) includes a symbol of a PUSCH transmission (which repeats) or a PRB of an SRS transmission, then UE cancellation of a PUSCH transmission or a repeat of a PUSCH transmission (if the PUSCH transmission has a repeat) or an SRS transmission on the serving cell is detected for DCI format 2_4 of the serving cell. If the UE is provided with an RRC parameter (e.g., applicabilityforCI) that indicates that the priority index should be considered, a PUSCH with priority index 0 can be cancelled based on the detection of DCI 2_4 as described above, but a PUSCH with priority index 1 can ignore DCI 2_4 and be transmitted as normal.

[0212] If the UE is provided with RRC parameters for uplink cancellation (e.g., UplinkCancellation), a search space set is provided to the UE in one or more serving cells, a CI-RNTI provided by ci-RNTI is used to monitor PDCCH candidates, and DCI format 2_4 is detected using the CI-RNTI provided by ci-RNTI, then SP-CSI reports using PUSCH and / or A-CSI reports using PUSCH can also be cancelled. If a set of symbols indicated by DCI format 2_4 (e.g., having at least one bit value "1" in the corresponding set of bits in DCI format 2_4) includes symbols of SP-CSI transmissions (which are repeated) or symbols of A-CSI transmissions, and a set of PRBs indicated by DCI format 2_4 (having a corresponding bit value "1" in the corresponding set of bits in DCI format 2_4) includes symbols of SP-CSI transmissions (which are repeated) or PRBs of A-CSI transmissions, then the UE that detected DCI format 2_4 for the serving cell cancelled the SP-CSI report or A-CSI report.

[0213] This article describes considerations for canceling SP-CSI reporting using PUSCH and / or using A-CSI reporting using PUSCH, based on priority indicators or priority indexes.

[0214] In specific implementations, RRC parameters (e.g., the same parameter `applicabilityforCI` as described above, and a different parameter `applicabilityforCSICI` specifically for CSI reporting) can be configured to indicate whether a priority index and / or indicator should be considered for canceling SP-CSI reports using PUSCH and / or A-CSI reports using PUSCH. If the UE is provided with an RRC parameter indicating that a priority index should be considered, SP-CSI reports with priority index 0 and / or A-CSI reports with priority index 0 can be canceled based on the detection of DCI2_4 as described above. However, SP-CSI reports with priority index 1 and / or A-CSI reports with priority index 1 can ignore DCI2_4 and be transmitted as normal.

[0215] In yet another specific implementation, regardless of whether a priority index is provided and regardless of the value of the priority index, SP-CSI reports and / or A-CSI reports can be cancelled based on the detection of DCI 2_4 as described above.

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

[0217] UE 702 may also include a housing that accommodates one or more transmitters 758 and one or more receivers 720 to allow for the transmission and reception of data. The transmitters 758 and receivers 720 may be combined into one or more transceivers 718. One or more antennas 722a-n are attached to the housing and electrically coupled to the transceivers 718.

[0218] The various components of UE 702 are coupled together via a bus system 711 (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 7 The UE 702 is shown as a bus system 711. The UE 702 may also include a digital signal processor (DSP) 713 for processing signals. The UE 702 may also include a communication interface 715 that provides users with access to the functions of the UE 702. Figure 7 The UE 702 shown is a functional block diagram, not a list of specific components.

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

[0220] The gNB 860 may also include a housing that accommodates one or more transmitters 817 and one or more receivers 878 to allow for data transmission and reception. The transmitters 817 and receivers 878 may be combined into one or more transceivers 876. One or more antennas 880a-n are attached to the housing and electrically coupled to the transceivers 876.

[0221] The various components of the gNB 860 are coupled together via a bus system 811 (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 8 The bus system is shown as 811. The gNB 860 may also include a digital signal processor (DSP) 813 for processing signals. The gNB 860 may also include a communication interface 815 that provides users with access to the functions of the gNB 860. Figure 8The gNB 860 shown is a functional block diagram, not a list of specific components.

[0222] Figure 9 This is a block diagram illustrating a specific implementation of a UE 902 in which one or more of the systems and / or methods described herein may be implemented. The UE 902 includes a transmitting device 958, a receiving device 920, and a control device 924. The transmitting device 958, the receiving device 920, and the control device 924 can be configured to perform combined... Figure 1 One or more of the aforementioned functions. (Above) Figure 7 It shows Figure 9 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.

[0223] Figure 10 This is a block diagram illustrating a specific implementation of a gNB 1060 in which one or more of the systems and / or methods described herein may be implemented. The gNB 1060 includes a transmitter 1017, a receiver 1078, and a control unit 1082. The transmitter 1017, receiver 1078, and control unit 1082 can be configured to perform combined... Figure 1 One or more of the aforementioned functions. (Above) Figure 8 It shows Figure 10 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.

[0224] Figure 11 This is a block diagram illustrating a specific implementation of gNB 1160. gNB 1160 can be combined with... Figure 1 An example of the described gNB 1160. The gNB 1160 may include a high-level processor 1123, a DL transmitter 1125, a UL receiver 1133, and one or more antennas 1131. The DL transmitter 1125 may include a PDCCH transmitter 1127 and a PDSCH transmitter 1129. The UL receiver 1133 may include a PUCCH receiver 1135 and a PUSCH receiver 1137.

[0225] The higher-layer processor 1123 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 1123 can obtain transport blocks from the physical layer. The higher-layer processor 1123 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 1123 can provide transport blocks to the PDSCH transmitter and provide transport parameters related to the transport blocks to the PDCCH transmitter.

[0226] DL transmitter 1125 can multiplex downlink physical channels and downlink physical signals (including reserved signals) and transmit them via transmit antenna 1131. UL receiver 1133 can receive and demultiplex the multiplexed uplink physical channels and uplink physical signals via receive antenna 1131. PUCCH receiver 1135 can provide UCI to higher-layer processor 1123. PUSCH receiver 1137 can provide received transport blocks to higher-layer processor 1123.

[0227] Figure 12 This is a block diagram illustrating a specific implementation of UE 1202. UE 1202 can be combined with... Figure 1 An example of UE102 is described. UE 1202 may include a higher-level processor 1223, a UL transmitter 1251, a DL receiver 1243, and one or more antennas 1231. The UL transmitter 1251 may include a PUCCH transmitter 1253 and a PUSCH transmitter 1255. The DL receiver 1243 may include a PDCCH receiver 1245 and a PDSCH receiver 1247.

[0228] The higher-layer processor 1223 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 1223 can obtain transport blocks from the physical layer. The higher-layer processor 1223 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 1223 can provide transport blocks to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1253.

[0229] DL receiver 1243 can receive and demultiplexed downlink physical channels and downlink physical signals via receiving antenna 1231. PDCCH receiver 1245 can provide DCI to higher-layer processor 1223. PDSCH receiver 1247 can provide received transport blocks to higher-layer processor 1223.

[0230] 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.

[0231] 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.

[0232] 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... Disks typically copy data magnetically, while optical discs use lasers to copy data optically.

[0233] 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.

[0234] 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.

[0235] 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.

[0236] 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.

[0237] Furthermore, if the program is commercially available, it can be distributed on a portable recording medium or transferred 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.

[0238] 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 can 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 can be a microprocessor, or alternatively, it can be a conventional processor, controller, microcontroller, or state machine. Each general-purpose processor or each circuitry described herein can be configured by digital circuitry or by analog circuitry. Furthermore, when advancements in semiconductor technology lead to the development of technologies for manufacturing integrated circuits that replace current integrated circuits, integrated circuits produced using such technologies can also be used.

[0239] In one example, a user equipment (UE) includes: a receiving circuit configured to receive downlink control information (DCI) format for scheduling a physical downlink shared channel (PDSCH) on a physical downlink control channel (PDCCH), the DCI including a priority indicator; and a transmission circuit configured to perform channel state information (CSI) reporting on the first physical uplink channel based on the priority indicator if the first physical uplink channel overlaps with the second physical uplink channel.

[0240] In one example, a base station apparatus includes: a transmission circuit configured to transmit downlink control information (DCI) format for scheduling a physical downlink shared channel (PDSCH) on a physical downlink control channel (PDCCH), the DCI including a priority indicator; and a receiving circuit configured to receive a channel state information (CSI) report on the first physical uplink channel based on the priority indicator, in the case that a first physical uplink channel overlaps with a second physical uplink channel.

[0241] In one example, a communication method for a user equipment includes: receiving downlink control information (DCI) format for scheduling a physical downlink shared channel (PDSCH) on a physical downlink control channel (PDCCH), the DCI including a priority indicator; and, in the case where a first physical uplink channel overlaps with a second physical uplink channel, performing a channel state information (CSI) report on the first physical uplink channel based on the priority indicator.

[0242] In one example, a communication method of a base station apparatus includes: transmitting downlink control information (DCI) format for scheduling a physical downlink shared channel (PDSCH) on a physical downlink control channel (PDCCH), the DCI including a priority indicator; and receiving a channel state information (CSI) report on the first physical uplink channel based on the priority indicator when a first physical uplink channel overlaps with a second physical uplink channel.

[0243] In one example, a user equipment (UE) includes: a receiving circuit configured to receive downlink control information (DCI) format for scheduling / activating a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical uplink control channel (PUCCH) on a physical downlink control channel (PDCCH), the DCI including a priority indicator; and a transmission circuit configured to perform channel state information (CSI) reporting on the first physical uplink channel based on the priority indicator if the first physical uplink channel overlaps with the second physical uplink channel.

[0244] In one example, a base station apparatus includes: a transmission circuit configured to transmit downlink control information (DCI) format for scheduling / activating a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical uplink control channel (PUCCH) on a physical downlink control channel (PDCCH), the DCI including a priority indicator; and a receiving circuit configured to receive a channel state information (CSI) report on the first physical uplink channel based on the priority indicator, in the case where a first physical uplink channel overlaps with a second physical uplink channel.

[0245] In one example, a communication method for a user equipment includes: receiving a downlink control information (DCI) format for scheduling / activating a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical uplink control channel (PUCCH) on a physical downlink control channel (PDCCH), the DCI including a priority indicator; and, in the case where a first physical uplink channel overlaps with a second physical uplink channel, performing a channel state information (CSI) report on the first physical uplink channel based on the priority indicator.

[0246] In one example, a communication method of a base station apparatus includes: transmitting downlink control information (DCI) format for scheduling / activating a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical uplink control channel (PUCCH) on a physical downlink control channel (PDCCH), the DCI including a priority indicator; and receiving a channel state information (CSI) report on the first physical uplink channel based on the priority indicator when a first physical uplink channel overlaps with a second physical uplink channel.

[0247] <Cross-reference>

[0248] This non-provisional application claims priority to provisional application 63 / 024,950, filed May 14, 2020, pursuant to section 119 of title 35 of the United States Code, the entire contents of which are incorporated herein by reference.

Claims

1. A user equipment (UE), the UE comprising: The receiver is configured to receive downlink control information (DCI) format for activating semi-persistent channel state information (SP-CSI) reporting on a first physical uplink shared channel (PUSCH), the DCI format including a priority indicator, and the receiver is configured to receive a second DCI format for triggering aperiodic channel state information (A-CSI) reporting on a second PUSCH. and The transmitter is configured to execute the A-CSI report on the second PUSCH after successfully decoding the second DCI format, wherein If the time occupancy of the first PUSCH and the second PUSCH overlaps in at least one OFDM symbol and they are transmitted on the same carrier, the A-CSI takes precedence over the SP-CSI regardless of the value of the priority indicator, and neither of them sends the SP-CSI report on the first PUSCH.

2. A base station apparatus, the base station apparatus comprising: A transmitter configured to transmit downlink control information (DCI) format for activating semi-persistent channel state information (SP-CSI) reporting on a first physical uplink shared channel (PUSCH), the DCI format including a priority indicator, and the transmitter configured to transmit a second DCI format for triggering aperiodic channel state information (A-CSI) reporting on a second PUSCH. and A receiver, configured to receive the A-CSI report on the second PUSCH, wherein, When the time occupancy of the first PUSCH and the second PUSCH overlaps in at least one OFDM symbol and is transmitted on the same carrier, the A-CSI takes precedence over the SP-CSI regardless of the value of the priority indicator, and the SP-CSI report on the first PUSCH is not received by the receiver.

3. A communication method for user equipment, the communication method comprising: On the first physical uplink shared channel PUSCH, a downlink control information (DCI) format for activating semi-persistent channel state information (SP-CSI) reporting is received, the DCI format including a priority indicator. Receive the second DCI format on the second PUSCH to trigger an aperiodic Channel State Information (A-CSI) report; as well as After successfully decoding the second DCI format, the A-CSI report is executed on the second PUSCH, wherein... If the time occupancy of the first PUSCH and the second PUSCH overlaps in at least one OFDM symbol and they are transmitted on the same carrier, the A-CSI takes precedence over the SP-CSI regardless of the value of the priority indicator, and neither of them sends the SP-CSI report on the first PUSCH.

Images