User equipment, base stations, and methods for CSI requests

Abstract

The UE includes a receiving circuit configured to receive first information, second information, first downlink control information (DCI) on the physical downlink control channel (PDCCH), and a second DCI on the PDCCH. The UE also includes a transmission circuit configured to transmit channel state information (CSI) reports on the physical uplink shared channel (PUSCH). A CSI request field in the first DCI is configured by the first information. A CSI request field in the second DCI is configured by the second information. The first information includes a trigger state for aperiodic CSI reporting for the first DCI. The CSI request field in the second DCI is configured by the second information.

Description

Technical Field

[0001] This disclosure relates generally to communication systems. More specifically, this disclosure relates to novel signaling, procedures, user equipment, and base stations for configuring uplink control information on a micro-slotted physical uplink shared channel (PUSCH). 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 includes a receiving circuit and a transmitting circuit. The receiving circuit is configured to receive first information, second information, first downlink control information (DCI) on a physical downlink control channel (PDCCH), and a second DCI on the PDCCH. The transmitting circuit is configured to transmit channel state information (CSI) reports on a physical uplink shared channel (PUSCH), wherein a CSI request field in the first DCI is configured by the first information, and a CSI request field in the second DCI is configured by the second information. The first information includes a triggering state for aperiodic CSI reporting of the first DCI, and the CSI request field in the second DCI is configured by the second information.

[0006] In one example, a base station apparatus includes a transmission circuit and a receiving circuit. The transmission circuit is configured to transmit first information, second information, first downlink control information (DCI) on a physical downlink control channel (PDCCH), and a second DCI on the PDCCH. The receiving circuit is configured to receive channel state information (CSI) reports on a physical uplink shared channel (PUSCH), wherein a CSI request field in the first DCI is configured by the first information, and a CSI request field in the second DCI is configured by the second information. The first information includes a triggering state for aperiodic CSI reporting of the first DCI, and the CSI request field in the second DCI is configured by the second information.

[0007] In one example, a communication method for a user equipment includes: receiving first information, second information, first downlink control information (DCI) and second DCI on a physical downlink control channel (PDCCH), and transmitting channel state information (CSI) reports on a physical uplink shared channel (PUSCH), wherein a CSI request field in the first DCI is configured by the first information, a CSI request field in the second DCI is configured by the second information, the first information includes a triggering state for aperiodic CSI reporting of the first DCI, and the CSI request field in the second DCI is configured by the second information.

[0008] In one example, a communication method of a base station apparatus includes: transmitting first information, second information, first downlink control information (DCI) and second DCI on a physical downlink control channel (PDCCH), and receiving channel state information (CSI) reports on a physical uplink shared channel (PUSCH), wherein a CSI request field in the first DCI is configured by the first information, a CSI request field in the second DCI is configured by the second information, the first information includes a triggering state for aperiodic CSI reporting of the first DCI, and the CSI request field in the second DCI is configured by the second information. Attached Figure Description

[0009] [ Figure 1 ] Figure 1 This is a block diagram illustrating one or more base station devices (gNBs) and one or more user equipment (UEs) in which systems and methods for signaling can be implemented.

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

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

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

[0013] [ Figure 5 ] Figure 5 This is a diagram showing the CSI trigger state in CSI-AperiodicTriggerStateList and the CSI request fields in DCI format 0_1 ​​and DCI format 0_2.

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

[0015] [ Figure 7 ] Figure 7 The various components that can be used in gNB are shown.

[0016] [ Figure 8 ] Figure 8 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.

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

[0018] [ Figure 10 ] Figure 10 This is a block diagram illustrating a specific implementation of gNB.

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

[0020] [ Figure 12 ] Figure 12 This is a flowchart illustrating the communication method performed by the UE.

[0021] [ Figure 13 ] Figure 13 This is a flowchart illustrating the communication method performed by the gNB. Detailed Implementation

[0022] The UE includes a receiving circuit configured to receive first information, second information, first downlink control information (DCI) on the physical downlink control channel (PDCCH), and a second DCI on the PDCCH. The UE also includes a transmission circuit configured to transmit channel state information (CSI) reports on the physical uplink shared channel (PUSCH). A CSI request field in the first DCI is configured by the first information. A CSI request field in the second DCI is configured by the second information. The first information includes a trigger state for aperiodic CSI reporting for the first DCI. The CSI request field in the second DCI is configured by the second information.

[0023] This invention describes a User Equipment (UE). The UE includes a receiving circuit configured to receive a Radio Resource Control (RRC) message including information for configuring a priority indication present in a Downlink Control Information (DCI) format. This DCI format is used for scheduling the Physical Downlink Shared Channel (PDSCH). The priority indication is used to indicate the priority of Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) transmissions for the PDSCH. The UE also includes a transmission circuit configured to perform HARQ-ACK transmissions for the PDSCH based on this priority. This information is configured for each Control Resource Set (CORESET), except for CORESETs with index "0".

[0024] The present invention also describes a base station apparatus. The base station apparatus includes a transmission circuit configured to transmit an RRC message, the RRC message including information for configuring a priority indication present in a DCI format. The DCI format is used for scheduling PUSCH. The priority indication is used to indicate the priority of HARQ-ACK transmission for PDSCH. The base station apparatus also includes a receiving circuit configured to perform HARQ-ACK reception for PDSCH based on the priority. This information is configured for each CORESET, except for CORESETs with index "0".

[0025] The present invention also describes a communication method for a UE. The communication method includes receiving an RRC message, the RRC message including information for configuring a priority indication present in a DCI format. The DCI format is used for scheduling PUSCH. The priority indication is used to indicate the priority of HARQ-ACK transmissions for PDSCH. The communication method further includes performing HARQ-ACK transmissions for PDSCH based on this priority. This information is configured for each CORESET, except for CORESETs with index "0".

[0026] The present invention also describes a communication method for a base station apparatus. The communication method includes transmitting an RRC message, the RRC message including information for configuring a priority indicator present in a DCI format. The DCI format is used for scheduling PUSCH. The priority indicator is used to indicate the priority of HARQ-ACK transmission for PDSCH. The communication method further includes performing HARQ-ACK reception for PDSCH based on the priority. This information is configured for each CORESET, except for CORESETs with index "0".

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

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

[0029] At least some aspects of the systems and methods disclosed herein can be described in conjunction with 3GPP LTE, LTE-A Advanced (LTE-A), 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.

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

[0031] In 3GPP specifications, base stations are commonly referred to as Node B, Evolved Node B (eNB), Home Enhanced or Evolved Node B (HeNB), or some 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.

[0032] It should be noted that, as used herein, a “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” 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.

[0033] 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 receive downlink signals and / or transmit uplink signals in the BWPs of one and / or more serving cells.

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

[0035] 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 drawings below is not intended to limit the scope of the claims, but merely to represent the systems and methods described.

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

[0037] 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, the one or more gNBs 160 can also use one or more downlink channels 119 to transmit information or data to the 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0050] Here, the priority indicator can be used to indicate the priority of PDSCH transmission and / or PDSCH reception (e.g., 2 bits, 00: lowest priority, 01: lower priority, 10: higher priority, and / or 11: highest priority). For example, when UE 102 detects (e.g., decodes, receives) a DCI format including the priority indicator for downlink, UE 102 can identify that PDSCH transmission and / or PDSCH reception are prioritized (e.g., PDSCH transmission and / or PDSCH reception have higher priority, highest priority, lower priority, and / or lowest priority).

[0051] Additionally or alternatively, a priority indicator may be used to indicate the priority of HARQ-ACK transmission and / or HARQ-ACK reception for PDSCH (e.g., 2-bit information, 00: lowest priority, 01: lower priority, 10: higher priority, and / or 11: highest priority). For example, when UE 102 detects a DCI format including a priority indicator for downlink, UE 102 may identify that HARQ-ACK transmission and / or HARQ-ACK reception for PDSCH are prioritized (e.g., HARQ-ACK transmission and / or HARQ-ACK reception for PDSCH have higher priority, highest priority, lower priority, and / or lowest priority).

[0052] 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, 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.

[0053] 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 (e.g., for PDSCH transmission and / or for PDSCH reception). Alternatively or additionally, the DCI included in DCI format 1_1 may be a priority indicator (e.g., for PDSCH HARQ-ACK transmission and / or for PDSCH HARQ-ACK reception).

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

[0055] 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 (e.g., for PDSCH transmission and / or for PDSCH reception). Alternatively or additionally, the DCI included in DCI format 1_X may be a priority indicator (e.g., for PDSCH HARQ-ACK transmission and / or for PDSCH HARQ-ACK reception).

[0056] Here, DCI format 1_X (and / or DCI format 1_X including priority indication) can be used to indicate the priority of PDSCH transmission and / or PDSCH reception (e.g., higher priority, highest priority, lower priority, and / or lowest priority). For example, when UE 102 detects DCI format 1_X (and / or DCI format 1_X including priority indication), UE 102 can recognize that PDSCH transmission and / or PDSCH reception are prioritized (e.g., PDSCH transmission and / or PDSCH reception have higher priority, highest priority, lower priority, and / or lowest priority).

[0057] Additionally or alternatively, DCI format 1_X (and / or DCI format 1_X including priority indication, and / or DCI format 1_X having a CRC scrambled by a first RNTI, and / or DCI format 1_X having a CRC scrambled by a first RNTI including priority indication) may be used to indicate the priority (e.g., higher priority, highest priority, lower priority, and / or lowest priority) for HARQ-ACK transmission for PDSCH and / or HARQ-ACK reception for PDSCH. For example, when UE 102 detects DCI format 1_X (and / or DCI format 1_X including priority indication, and / or DCI format 1_X with CRC scrambled by a first RNTI, and / or DCI format 1_X with CRC scrambled by a first RNTI including priority indication), UE 102 can identify that HARQ-ACK transmission for PDSCH and / or HARQ-ACK reception for PDSCH are prioritized (e.g., HARQ-ACK transmission for PDSCH and / or HARQ-ACK reception for PDSCH have higher priority, highest priority, lower priority, and / or lowest priority).

[0058] 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, 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.

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

[0060] Here, the priority indicator can be used to indicate the priority of PUSCH transmission and / or PUSCH reception (e.g., 2 bits, 00: lowest priority, 01: lower priority, 10: higher priority, and / or 11: highest priority). For example, when UE 102 detects a DCI format including a priority indicator for uplink, UE 102 can identify that PUSCH transmission and / or PUSCH reception are prioritized (e.g., PUSCH transmission and / or PUSCH reception have higher priority, highest priority, lower priority, and / or lowest priority).

[0061] Alternatively or additionally, the DCI format 0_1 ​​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, and / or the first RNTI may be used to transmit DCI format 0_1. Alternatively or additionally, DCI format 0_1 ​​may be monitored (e.g., transmitted, mapped) in the CSS and / or USS.

[0062] 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, as described below, the DCI included in DCI format 0_1 ​​may be information indicating an index of a configured authorized configuration. Additionally or alternatively, the DCI included in DCI format 0_0 may be a priority indicator (e.g., for PUSCH transmission and / or for PUSCH reception).

[0063] 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, 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.

[0064] 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, as described below, the DCI included in DCI format 0_Y may be information indicating an index of a configured authorized configuration. Additionally or alternatively, the DCI included in DCI format 0_Y may be a priority indicator (e.g., for PUSCH transmission and / or for PUSCH reception).

[0065] Here, DCI format 0_Y (and / or DCI format 0_Y including priority indication, and / or DCI format 0_Y with CRC scrambled by the first RNTI, and / or DCI format 0_Y with CRC scrambled by the first RNTI including priority indication) can be used to indicate the priority (e.g., higher priority, highest priority, lower priority, and / or lowest priority) for PUSCH transmission and / or PUSCH reception. For example, when UE 102 detects DCI format 0_Y (and / or DCI format 0_Y including priority indication, and / or DCI format 0_Y with CRC scrambled by the first RNTI, and / or DCI format 0_Y with CRC scrambled by the first RNTI including priority indication), UE 102 can recognize that PUSCH transmission and / or PUSCH reception are prioritized (e.g., PUSCH transmission and / or PUSCH reception have higher priority, highest priority, lower priority, and / or lowest priority).

[0066] Additionally or alternatively, upon receiving DCI format 1_0, DCI format 1_1, and / or DCI format 1_X (e.g., based on the detection of DCI format 1_0, DCI format 1_1, and DCI format 1_X), UE 102 may perform PDSCH reception. Additionally or alternatively, upon receiving DCI format 0_0, DCI format 0_1, and / or DCI format 0_Y (e.g., based on the detection of DCI format 0_0, DCI format 0_1, and DCI format 0_Y), UE 102 may perform PUSCH transmission.

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

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

[0069] 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 and / or first RNTI.

[0070] For example, a C-RNTI can be a unique identifier for identifying an RRC connection and / or scheduling. Additionally or alternatively, a CS-RNTI can be a unique identifier for configuration-based authorized scheduling transmissions. Additionally or alternatively, an 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, an SI-RNTI can be used for broadcasting SIs. Additionally or alternatively, a RA-RNTI can be an identifier for random access procedures (e.g., Msg.2 transmissions). Additionally or alternatively, a temporary C-RNTI can be used for scheduling random access procedures (e.g., Msg.3(re)transmissions (e.g., Msg.3PUSCH(re)transmissions)).

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

[0072] Additionally or alternatively, the first RNTI may be an identifier used to indicate the priority (e.g., higher priority, highest priority, lower priority, and / or lowest priority) of PDSCH transmission and / or PDSCH reception. For example, if UE 102 detects a PDSCH with a CRC scrambled by the first RNTI, UE 102 may identify that the corresponding PDSCH is prioritized (e.g., the corresponding PDSCH transmission / reception has higher priority, highest priority, lower priority, and / or lowest priority).

[0073] Additionally or alternatively, the first RNTI may be an identifier used to indicate the priority (e.g., higher priority, highest priority, lower priority, and / or lowest priority) of HARQ-ACK transmission and / or HARQ-ACK reception of PDSCH. For example, if UE 102 detects a PDCCH with a CRC scrambled by the first RNTI, UE 102 may identify that the HARQ-ACK of the corresponding PDSCH is prioritized (e.g., the HARQ-ACK transmission / reception of the corresponding PDSCH has a higher priority, highest priority, lower priority, and / or lowest priority).

[0074] Additionally or alternatively, the first RNTI may be an identifier used to indicate the priority (e.g., higher priority, highest priority, lower priority, and / or lowest priority) of PUSCH transmission and / or PUSCH reception. For example, if UE 102 detects a PDCCH with a CRC scrambled by the first RNTI, UE 102 may identify that the corresponding PUSCH is prioritized (e.g., the corresponding PUSCH transmission / reception has higher priority, highest priority, lower priority, and / or lowest priority).

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

[0076] In addition, PDSCH and / or PUSCH can be used to transmit information from higher layers (e.g., the Radio Resource Control (RRC) layer and / or the 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 CEs). Here, RRC messages and / or MAC CEs are also referred to as higher layer signals.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0092] 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 of gNB scheduling modules 194. gNB scheduling module 194 can perform scheduling of downlink and / or uplink transmissions as described herein.

[0093] gNB operation module 182 may provide information 188 to demodulator 172. For example, gNB operation module 182 may inform demodulator 172 of the expected modulation pattern for transmissions from one or more UEs 102.

[0094] 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 transmissions from one or more UEs 102.

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

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

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

[0098] 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 one or more UEs 102. One or more transmitters 117 may upconvert one or more modulated signals 115 and transmit those modulated signals to one or more UEs 102.

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

[0100] It should also be noted that one or more of the elements or components included in one or more eNBs 160s and one or more UEs 102s 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 performed using hardware. For example, one or more of the methods described herein may be implemented using 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.

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

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

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

[0104] exist Figure 3 In this context, 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. A downlink radio frame may include multiple pairs of downlink resource blocks (RBs) 391, which are also referred to as physical resource blocks (PRBs). Downlink RB pairs are units used to allocate downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and time slots.

[0105] A downlink RB pair may include two consecutive downlink RBs 391 in the time domain. Additionally or alternatively, a 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 and time domains, respectively.

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

[0107] Each element in resource grid 301 (e.g., antenna port p) and subcarrier configuration u is referred to as resource element 389 and is uniquely identified by index pairs (k, l), where k = 0, ..., It is the index in the frequency domain, and I refers to the symbol position in the time domain. The resource element (k,l)389 and subcarrier spacing configuration μ on antenna port p are represented as (k,l). p , μ Physical resource block 391 is limited to the frequency domain. A continuous subcarrier. Physical resource block 391 in the frequency domain from 0 to... Number. Physical resource block number in the frequency domain. n The relationship between PRB and resource element (k,l) is given below:

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

[0109] UE 102 can monitor a candidate set of PDCCHs 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 DL control channel (e.g., the candidate set of PDCCHs) according to the monitored DCI format. Additionally, the candidates for PDCCHs may be candidates for DL ​​control channels that might be mapped, allocated, and / or transmitted.

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

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

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

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

[0114] Here, the index "0" of the CORESET (i.e., the value "0" of the CORESET) 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. Alternatively or additionally, the gNB 160 can transmit information for configuring CORESET#0 using the SIB. Alternatively or additionally, the gNB 160 can transmit information for configuring CORESET#0 using dedicated RRC messages.

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

[0116] Here, gNB 106 can transmit information about the indexes used to configure the DL BWP (e.g., indexes other than index "0") using RRC messages (e.g., MIB, SIB, and / or dedicated RRC messages). Additionally, gNB 106 can transmit information about the indexes used to configure the UL BWP (e.g., indexes other than index "0") using RRC messages (e.g., MIB, SIB, and / or dedicated RRC messages).

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

[0118] Additionally or alternatively, for each of the one or more CORESETs, a search space set (e.g., a set of CSS and / or USS) can be configured. For example, first information can be configured for DL ​​BWPs. That is, first information can be configured for each DL BWP in the serving cell.

[0119] 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 periodicity and / or PDCCH monitoring offset of the PDCCH in the search space set in which UE 102 monitors it. Additionally or alternatively, the second information may include information for indicating the PDCCH monitoring pattern within a time slot. For example, information indicating the PDCCH monitoring pattern 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 pattern within the time slot.

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

[0121] 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). Here, the DCI format used to monitor the PDCCH in the USS can be scrambled by C-RNTI, CS-RNTI, and / or a first RNTI. For example, second information can be configured for a search space set. That is, second information can be configured for each search space set within the search space set.

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

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

[0124] 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, DL BWP ID) in that DL BWP set using RRC messages.

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

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

[0127] Figure 5 This is a diagram showing the CSI trigger state in CSI-AperiodicTriggerStateList and the CSI request fields in DCI format 0_1 ​​and DCI format 0_2.

[0128] Here, DCI format 0_Y (e.g., DCI format 0_2) may include a CSI request field for non-periodic CSI reporting. The number of bits (size) of the CSI request field is configured to have 0, 1, 2, 3, 4, 5, or 6 bits by a higher-level parameter or higher-level information (e.g., reportTriggerSize-ForDCIFormat0_2). This parameter can be configured separately for reportTriggerSize of DCI format 0_1. This parameter can be configured for reportTriggerSize of DCI format 0_2. The reportTriggerSize parameter can be configured for both DCI format 0_1 ​​and DCI format 0_2.

[0129] Here, each state of the CSI request field is configured by a higher-level parameter or higher-level information (e.g., CSI-AperiodicTriggerStateList-ForDCIFormat0_2). This parameter can be configured individually for CSI-AperiodicTriggerStateList for DCI Format0_1. The CSI-AperiodicTriggerStateList parameter can also be configured for both DCI Format0_1 and DCI Format0_2.

[0130] The CSI-AperiodicTriggerStateList information element (IE) can be used to configure UE 102 using a list of aperiodic trigger states. Each code point in the CSI request field of DCI format 0_1 ​​and / or DCI format 0_2 can be associated with a trigger event. Upon receiving a value associated with a trigger state, UE 102 can perform CSI-RS, CSI-IM, and / or SSB (reference signal) and aperiodic reported measurements at the physical layer (Layer 1 (L1)) based on all entries in the associatedReportConfigInfoList for that trigger state. Reconfiguration of CSI-AssociatedReportConfigInfo may not be supported.

[0131] Here, DCI format 0_Y (e.g., DCI format 0_2) may include a CSI request field for semi-persistent CSI reporting. Each trigger event in the CSI request field can be configured by CSI-SemiPersistentOnPUSCH-TriggerStateList-ForDCIFormat0_2. Each trigger state in CSI-SemiPersistentOnPUSCH-TriggerStateList-ForDCIFormat0_2 contains an associated CSI-ReportConfig. This parameter can be configured separately for DCI format 0_1's SemiPersistentOnPUSCH-TriggerStateList. The SemiPersistentOnPUSCH-TriggerStateList parameter can also be configured for both DCI format 0_1 ​​and DCI format 0_2.

[0132] When the number of bits in the CSI request field of DCI format 0_1 ​​is greater than the number of bits in the CSI request field of DCI format 0_2, and when CSI-AperiodicTriggerStateList is typically configured for both DCI format 0_1 ​​and DCI format 0_2, MACCE can select a trigger state to map each code point of the CSI request field in DCI format 0_2. Alternatively, the same value in the CSI request field in both DCI format 0_1 ​​and DCI format 0_2 can be associated with a trigger event configured by CSI-AperiodicTriggerStateList. Figure 5 An example illustrating this is shown below. With the seven trigger states configured by CSI-AperiodicTriggerStateList for DCI formats 0_1 and 0_2, and with three bits of the CSI request field in DCI format 0_1 ​​and two bits of the CSI request field in DCI format 0_2 configured, the seven trigger items are mapped to code points {001,010,011,100,101,110,111} (values ​​{1,2,3,4,5,6,7}) in the CSI request field of DCI format 0_1. For the CSI request field in DCI format 0_2, three trigger items are mapped to code points {01,10,11} (values ​​{1,2,3}) in the CSI request field. Here, code point "000" (value 0) means no CSI request (i.e., this code point is not associated with any trigger event).

[0133] Additionally or alternatively, for each DCI format, a separate MAC CE may select each trigger state in CSI-AperiodicTriggerStateList and CSI-AperiodicTriggerStateList-ForDCIFormat0_2 to map to each code point in DCI format0_1 and DCI format0_2, respectively. For example, a first MAC CE may select CSI trigger states configured by CSI-AperiodicTriggerStateList and map each state to each code point in DCI format0_1. A second MAC CE may select CSI trigger states configured by CSI-AperiodicTriggerStateList or CSI-AperiodicTriggerStateList-ForDCIFormat0_2 and map each state to each code point in DCI format0_2.

[0134] The time and frequency resources that UE 102 can use to report CSI are controlled by the gNB. CSI may include Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Block Resource Indicator (SSBRI), Layer Indicator (LI), Rank Indicator (RI), and / or Layer 1 Reference Signal Received Power (L1-RSRP).

[0135] When the number of bits in the CSI request field of DCI format 0_1 ​​is greater than the number of bits in the CSI request field of DCI format 0_2, and when SemiPersistentOnPUSCH-TriggerStateList is typically configured for both DCI format 0_1 ​​and DCI format 0_2, the MAC CE can select a trigger state to map each code point of the CSI request field in DCI format 0_2. Alternatively, the same value in the CSI request field in DCI format 0_1 ​​and DCI format 0_2 can be associated with a trigger event configured by CSI-SemiPersistentOnPUSCH-TriggerStateList. Similar to... Figure 5With the seven trigger states configured by SemiPersistentOnPUSCH-TriggerStateList for DCI formats 0_1 and 0_2, and with three bits of the CSI request field in DCI format 0_1 ​​and two bits of the CSI request field in DCI format 0_2 configured, the seven trigger items are mapped to code points {001,010,011,100,101,110,111} (values ​​{1,2,3,4,5,6,7}) in the CSI request field of DCI format 0_1. For the CSI request field in DCI format 0_2, three trigger items are mapped to code points {01,10,11} (values ​​{1,2,3}) in the CSI request field. Here, code point "000" (value 0) means no CSI request (i.e., this code point is not associated with any trigger event).

[0136] Additionally or alternatively, for each DCI format, a separate MAC CE may select each trigger state in CSI-SemiPersistentOnPUSCH-TriggerStateList-ForDCIFormat0_2 and SemiPersistentOnPUSCH-TriggerStateList-ForDCIFormat0_2 to map to each code point in DCI format0_1 and DCI format0_2, respectively. For example, a first MAC CE may select the CSI trigger states configured by CSI-SemiPersistentOnPUSCH-TriggerStateList-ForDCIFormat0_2 and map each state to each code point in DCI format0_1. A second MAC CE may select the CSI trigger states configured by either CSI-SemiPersistentOnPUSCH-TriggerStateList-ForDCIFormat0_2 or CSI-SemiPersistentOnPUSCH-TriggerStateList-ForDCIFormat0_2 and map each state to each code point in DCI format0_2.

[0137] Figure 6 Various components that can be used with UE 802 are shown. (Combined) Figure 6 The described UE 802 can be combined with Figure 1The UE 102 described herein is used for implementation. UE 802 includes a processor 803 that controls the operation of UE 802. 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 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 processor 803. Instructions 807b and / or data 809b loaded into processor 803 may also include instructions 807a and / or data 809a from memory 805 and loaded for execution or processing by processor 803. Instruction 807b may be executed by processor 803 to implement the methods described herein.

[0138] UE 802 may also include a housing that accommodates one or more transmitters 858 and one or more receivers 820 to allow data transmission and reception. Transmitters 858 and receivers 820 may be combined into one or more transceivers 818. One or more antennas 822a-n are attached to the housing and electrically coupled to the transceivers 818.

[0139] The various components of UE 802 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 6 The UE 802 is shown as a bus system 811. The UE 802 may also include a digital signal processor (DSP) 813 for processing signals. The UE 802 may also include a communication interface 815 that provides user access to the functionality of the UE 802. Figure 6 The UE 802 shown is a functional block diagram, not a list of specific components.

[0140] Figure 7 Various components that can be used with the gNB 960 are shown. (Combined) Figure 7 The described gNB 960 can be combined with Figure 1The described gNB 160 is used for implementation. The gNB 960 includes a processor 903 that controls the operation of the gNB 960. The processor 903 may also be referred to as a central processing unit (CPU). Memory 905 (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 907a and data 909a to the processor 903. A portion of memory 905 may also include non-volatile random access memory (NVRAM). Instructions 907b and data 909b may also reside in the processor 903. Instructions 907b and / or data 909b loaded into the processor 903 may also include instructions 907a and / or data 909a from memory 905, which are loaded for execution or processing by the processor 903. Instructions 907b may be executed by the processor 903 to implement the methods described herein.

[0141] The gNB 960 may also include a housing that accommodates one or more transmitters 917 and one or more receivers 978 to allow for the transmission and reception of data. The transmitters 917 and receivers 978 may be combined into one or more transceivers 976. One or more antennas 980a-n are attached to the housing and electrically coupled to the transceivers 976.

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

[0143] Figure 8 This is a block diagram illustrating one embodiment of a UE 1002 in which one or more of the systems and / or methods described herein may be implemented. The UE 1002 includes a transmitting device 1058, a receiving device 1020, and a control device 1024. The transmitting device 1058, the receiving device 1020, and the control device 1024 can be configured to perform combined... Figure 1 One or more of the functions described. (Above) Figure 6 It shows Figure 8 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 of a DSP. For example, a DSP can be implemented in software.

[0144] Figure 9 This is a block diagram illustrating one embodiment of gNB 1160 in which one or more of the systems and / or methods described herein may be implemented. gNB 1160 includes a transmitter 1117, a receiver 1178, and a control device 1182. The transmitter 1117, receiver 1178, and control device 1182 can be configured to perform combined... Figure 1 One or more of the functions described. (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 of a DSP. For example, a DSP can be implemented in software.

[0145] Figure 10 This is a block diagram illustrating a specific implementation of gNB 1260. gNB 1260 can be combined with... Figure 1 An example of the described gNB160. The gNB 1260 may include a high-level processor 1223, a DL transmitter 1225, a UL receiver 1233, and one or more antennas 1231. The DL transmitter 1225 may include a PDCCH transmitter 1227 and a PDSCH transmitter 1229. The UL receiver 1233 may include a PUCCH receiver 1235 and a PUSCH receiver 1237.

[0146] 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 PDSCH transmitter and provide transport parameters related to the transport blocks to the PDCCH transmitter.

[0147] DL transmitter 1225 can multiplex downlink physical channels and downlink physical signals (including reserved signals) and transmit them via transmit antenna 1231. UL receiver 1233 can receive and demultiplex the multiplexed uplink physical channels and uplink physical signals via receive antenna 1231. PUCCH receiver 1235 can provide UCI to higher-layer processor 1223. PUSCH receiver 1237 can provide received transport blocks to higher-layer processor 1223.

[0148] Figure 11 This is a block diagram illustrating a specific implementation of UE 1302. UE 1302 can be combined with... Figure 1An example of UE102 is described. UE 1302 may include a higher-level processor 1323, a UL transmitter 1351, a DL receiver 1343, and one or more antennas 1331. The UL transmitter 1351 may include a PUCCH transmitter 1353 and a PUSCH transmitter 1355. The DL receiver 1343 may include a PDCCH receiver 1345 and a PDSCH receiver 1347.

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

[0150] DL receiver 1343 can receive and demultiplexed downlink physical channels and downlink physical signals via receive antenna 1331. PDCCH receiver 1345 can provide DCI to higher-level processor 1323. PDSCH receiver 1347 can provide received transport blocks to higher-level processor 1323.

[0151] Figure 12 This is a flowchart illustrating communication method 1400 performed by UE 102. UE 102 may receive a Radio Resource Control (RRC) message 1402, which includes information for configuring a priority indication present in a Downlink Control Information (DCI) format. This DCI format can be used to schedule the Physical Downlink Shared Channel (PDSCH). The priority indication can be used to indicate the priority of Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) transmissions for the PDSCH.

[0152] UE 102 can perform HARQ-ACK transmission for PDSCH using 1404 based on this priority. This information can be configured for each control resource set (CORESET), except for the control resource set (CORESET) with index "0".

[0153] Figure 13 This is a flowchart illustrating a communication method 1500 performed by a base station device (gNB) 160. The gNB 160 can transmit a 1502RRC message, which includes information for configuring a priority indication present in a DCI format. This DCI format can be used to schedule PDSCH. The priority indication can be used to indicate the priority of HARQ-ACK transmissions for PDSCH.

[0154] The gNB 160 can perform HARQ-ACK reception for PDSCH 1504 based on this priority. This information can be configured for each CORESET, except for the CORESET with index "0".

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

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

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

[0158] It should be noted that one or more of the methods described herein can be implemented and / or executed using hardware. For example, one or more of the methods described herein can be implemented using 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.

[0159] Each of the methods 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.

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

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

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

[0163] 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 performed 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. The 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.

[0164] As used herein, the term “and / or” should be interpreted as referring to one or more items. For example, the phrase “A, B and / or C” should be interpreted as referring to any of the following: A only, B only, C only, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B and C. As used herein, the phrase “at least one” should be interpreted as referring to one or more items. For example, the phrase “at least one of A, B and C” or the phrase “at least one of A, B or C” should be interpreted as referring to any of the following: A only, B only, C only, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B and C. As used herein, the phrase “one or more” should be understood as referring to one or more items. For example, the phrase “one or more of A, B and C” or the phrase “one or more of A, B or C” should be interpreted as meaning any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B and C.

[0165] <Cross-reference>

[0166] This non-provisional application claims priority to provisional application 62 / 932,046, filed November 7, 2019, 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 first information, second information, third information from higher layers, and downlink control information (DCI) on the physical downlink control channel (PDCCH). The transmitter is configured to transmit Channel State Information (CSI) reports on the Physical Uplink Shared Channel (PUSCH), wherein The first information configuration specifies the first CSI request field in the first DCI format. The second information configuration includes a second CSI request field in a second DCI format that differs from the first DCI format. The first information includes the number of bits in the first CSI request field in the first DCI format. The second information includes the number of bits in the second CSI request field in the second DCI format. The third piece of information includes a list of non-periodic triggering states. When the UE receives the first DCI in the first DCI format The UE configures the number of bits in the first CSI request field in the first DCI format according to the first information. The UE associates the first code point of the first CSI request field with the first aperiodic trigger state from the list of aperiodic trigger states in the third information, and The UE performs a first measurement and generates a first aperiodic CSI report based on the first aperiodic trigger state, and When the UE receives the second DCI in the second DCI format The UE configures the number of bits in the second CSI request field in the second DCI format according to the second information. The UE associates the second code point of the second CSI request field with the second aperiodic trigger state from the list of aperiodic trigger states in the third information, and The UE performs a second measurement and generates a second aperiodic CSI report based on the second aperiodic trigger state.

2. A base station apparatus for communicating with a user equipment (UE), the base station apparatus comprising: The transmitter is configured to transmit first information, second information, third information at higher layers, and downlink control information (DCI) on the physical downlink control channel (PDCCH). The receiver is configured to receive Channel State Information (CSI) reports on the Physical Uplink Shared Channel (PUSCH), wherein The first information configuration specifies the first CSI request field in the first DCI format. The second information configuration includes a second CSI request field in a second DCI format that differs from the first DCI format. The first information includes the number of bits in the first CSI request field in the first DCI format. The second information includes the number of bits in the second CSI request field in the second DCI format. The third piece of information includes a list of non-periodic triggering states. When the base station device sends the first DCI in the first DCI format to the UE The UE configures the number of bits in the first CSI request field in the first DCI format according to the first information; The UE associates the first code point of the first CSI request field with the first aperiodic trigger state from the list of aperiodic trigger states in the third information; The UE performs a first measurement and generates a first aperiodic CSI report based on the first aperiodic trigger state; and The base station device receives the first aperiodic CSI report from the UE, and When the base station device sends the second DCI in the second DCI format to the UE The UE configures the number of bits in the second CSI request field in the second DCI format according to the second information; The UE associates the second code point of the second CSI request field with the second aperiodic trigger state from the list of aperiodic trigger states in the third information; The UE performs a second measurement and generates a second aperiodic CSI report according to the second aperiodic trigger state; and The base station device receives the second aperiodic CSI report from the UE.

3. A communication method for a user equipment (UE), the communication method comprising: Receive the first information, the second information, the third information from higher layers, and the downlink control information (DCI) on the physical downlink control channel (PDCCH), and Transmit Channel State Information (CSI) reports on the Physical Uplink Shared Channel (PUSCH), where The first information configuration specifies the first CSI request field in the first DCI format. The second information configuration includes a second CSI request field in a second DCI format that differs from the first DCI format. The first information includes the number of bits in the first CSI request field in the first DCI format. The second information includes the number of bits in the second CSI request field in the second DCI format. The third piece of information includes a list of non-periodic triggering states. The communication method further includes: When receiving the first DCI in the first DCI format Configure the number of bits in the first CSI request field in the first DCI format according to the first information. Associating the first code point of the first CSI request field with the first aperiodic triggering state from the list of aperiodic triggering states in the third information, and Perform a first measurement and generate a first aperiodic CSI report based on the first aperiodic trigger state, and When receiving the second DCI in the second DCI format Configure the number of bits in the second CSI request field in the second DCI format according to the second information. Associating the second code point of the second CSI request field with the second aperiodic triggering state from the list of aperiodic triggering states in the third information, and Perform a second measurement and generate a second aperiodic CSI report based on the second aperiodic trigger state.

Images