User equipment, base station and method for indicating uplink transmission

Abstract

The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a first DCI format including a one-bit uplink shared channel (UL-SCH) indicator, the first DCI format being used to schedule a PUSCH. The receiving circuit is also configured to receive a second DCI format including more than one bit of a UL-SCH indicator, the second DCI format being used to schedule a PUSCH. The UE also includes a transmitting circuit configured to transmit on the PUSCH based on detecting the first DCI format. The transmitting circuit is also configured to transmit on the PUSCH based on detecting the second DCI format. The one bit of the UL-SCH indicator is used to indicate whether a UL-SCH is transmitted on the PUSCH. The more than one bit of the UL-SCH indicator is used to indicate whether UCI is transmitted on the PUSCH.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems and, more particularly, to a user equipment (UE), a base station, and a method for instructing uplink transmissions. Background Art

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

[0003] With the development of wireless communication equipment, 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 provide limited flexibility and / or efficiency. As shown in this discussion, systems and methods that improve communication flexibility and / or efficiency may be advantageous. Summary of the Invention

[0005] In one example, a user equipment (UE) includes: a receiving circuit, the receiving circuit being configured to receive a first downlink control information (DCI) format including one bit of an uplink shared channel (UL-SCH) indicator, the first DCI format being used to schedule a physical uplink shared channel (PUSCH), the receiving circuit being configured to receive a second DCI format including more than one bit of a UL-SCH indicator, the second DCI format being used to schedule the PUSCH; and a transmitting circuit, the transmitting circuit being configured to perform transmission on the PUSCH based on detecting the first DCI format, the transmitting circuit being configured to perform transmission on the PUSCH based on detecting the second DCI format, wherein the one bit of the UL-SCH indicator is used to indicate whether the UL-SCH is transmitted on the PUSCH, and the more than one bit of the UL-SCH indicator is used to indicate whether uplink control information (UCI) is transmitted on the PUSCH.

[0006] In one example, a base station device includes: a transmitting circuit, the transmitting circuit being configured to transmit a first downlink control information (DCI) format including one bit of an uplink shared channel (UL-SCH) indicator, the first DCI format being used to schedule a physical uplink shared channel (PUSCH), the transmitting circuit being configured to transmit a second DCI format including more than one bit of a UL-SCH indicator, the second DCI format being used to schedule the PUSCH; and a receiving circuit, the receiving circuit being configured to perform reception on the PUSCH based on the transmission of the first DCI format, the receiving circuit being configured to perform reception on the PUSCH based on the transmission of the second DCI format, wherein the one bit of the UL-SCH indicator is used to indicate whether the UL-SCH is transmitted on the PUSCH, and the more than one bit of the UL-SCH indicator is used to indicate whether uplink control information (UCI) is transmitted on the PUSCH.

[0007] In one example, a communication method for a user equipment (UE) includes: receiving a first downlink control information (DCI) format including one bit of an uplink shared channel (UL-SCH) indicator, the first DCI format being used to schedule a physical uplink shared channel (PUSCH); receiving a second DCI format including more than one bit of a UL-SCH indicator, the second DCI format being used to schedule the PUSCH; based on detecting the first DCI format, performing transmission on the PUSCH; and based on detecting the second DCI format, performing transmission on the PUSCH, wherein the one bit of the UL-SCH indicator is used to indicate whether the UL-SCH is transmitted on the PUSCH, and the more than one bit of the UL-SCH indicator is used to indicate whether uplink control information (UCI) is transmitted on the PUSCH.

[0008] In one example, a communication method for a base station device includes: sending a first downlink control information (DCI) format including one bit of an uplink shared channel (UL-SCH) indicator, the first DCI format being used to schedule a physical uplink shared channel (PUSCH); sending a second DCI format including more than one bit of a UL-SCH indicator, the second DCI format being used to schedule PUSCH; performing reception on the PUSCH based on the sending of the first DCI format; and performing reception on the PUSCH based on the sending of the second DCI format, wherein the one bit of the UL-SCH indicator is used to indicate whether UL-SCH is sent on the PUSCH, and the more than one bit of the UL-SCH indicator is used to indicate whether uplink control information (UCI) is sent on the PUSCH. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0010] [ Figure 2 ] Figure 2 Examples of multiple parameters are shown.

[0011] [ Figure 3 ] Figure 3 is a diagram showing one example of a resource grid and resource blocks.

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

[0013] [ Figure 5 ] Figure 5 An example of uplink transmission is shown.

[0014] [ Figure 6 ] Figure 6 An example of an indication for UL transmission is shown.

[0015] [ Figure 7 ] Figure 7 Various components that may be utilized in a UE are shown.

[0016] [ Figure 8 ] Figure 8 Various components that may be utilized in a gNB are shown.

[0017] [ Figure 9 ] Figure 9 is a block diagram illustrating one embodiment of a UE in which one or more of the systems and / or methods described herein may be implemented.

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

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

[0020] [ Figure 12 ] Figure 12 is a block diagram illustrating a specific implementation of a UE. DETAILED DESCRIPTION

[0021] The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive a first downlink control information (DCI) format including a one-bit uplink shared channel (UL-SCH) indicator, the first DCI format being used to schedule a PUSCH. The receiving circuit is also configured to receive a second DCI format including more than one bit of a UL-SCH indicator, the second DCI format being used to schedule a PUSCH. The UE also includes a transmitting circuit configured to transmit on the PUSCH based on detecting the first DCI format. The transmitting circuit is also configured to transmit on the PUSCH based on detecting the second DCI format. The one bit of the UL-SCH indicator is used to indicate whether the UL-SCH is transmitted on the PUSCH. The more than one bit of the UL-SCH indicator is used to indicate whether uplink control information (UCI) is transmitted on the PUSCH.

[0022] The UCI may be transmitted on the PUSCH together with the UL-SCH.The more than one bit of the UL-SCH indicator may be further used to indicate a value corresponding to an offset value for determining a number of resources for UCI transmitted on the PUSCH.

[0023] The receiving circuit may be configured to receive a radio resource control (RRC) message including information for configuring a number of bits for a UL-SCH indicator included in a second DCI format. When one bit is configured for the UL-SCH indicator, the one bit of the UL-SCH indicator may be used to indicate whether the UL-SCH is transmitted on the PUSCH.

[0024] The UCI may include hybrid automatic repeat request acknowledgement (HARQ-ACK) and / or channel state information (CSI).

[0025] The present invention also describes a base station device. The base station includes a transmitting circuit configured to transmit a first DCI format including one bit of a UL-SCH indicator, the first DCI format being used to schedule a PUSCH. The transmitting circuit is further configured to transmit a second DCI format including more than one bit of a UL-SCH indicator, the second DCI format being used to schedule a PUSCH. The base station device also includes a receiving circuit configured to perform reception on the PUSCH based on the transmission of the first DCI format. The receiving circuit is further configured to perform reception on the PUSCH based on the transmission of the second DCI format. The one bit of the UL-SCH indicator is used to indicate whether a UL-SCH is transmitted on the PUSCH. The more than one bit of the UL-SCH indicator is used to indicate whether UCI is transmitted on the PUSCH.

[0026] The present invention also describes a communication method for a UE. The method includes receiving a first DCI format including a one-bit UL-SCH indicator, the first DCI format being used to schedule a PUSCH. The method also includes receiving a second DCI format including more than one bit of a UL-SCH indicator, the second DCI format being used to schedule a PUSCH. The method also includes performing transmission on the PUSCH based on detecting the first DCI format. The method also includes performing transmission on the PUSCH based on detecting the second DCI format. The one bit of the UL-SCH indicator is used to indicate whether a UL-SCH is transmitted on the PUSCH. The more than one bit of the UL-SCH indicator is used to indicate whether UCI is transmitted on the PUSCH.

[0027] The present invention also describes a communication method for a base station device. The method includes sending a first DCI format including a one-bit UL-SCH indicator, the first DCI format being used to schedule a PUSCH. The method also includes sending a second DCI format including more than one bit of a UL-SCH indicator, the second DCI format being used to schedule a PUSCH. The method also includes performing reception on the PUSCH based on the transmission of the first DCI format. The method also includes performing reception on the PUSCH based on the transmission of the second DCI format. The one bit of the UL-SCH indicator is used to indicate whether a UL-SCH is transmitted on the PUSCH. The more than one bit of the UL-SCH indicator is used to indicate whether UCI is transmitted on the PUSCH.

[0028] The 3rd Generation Partnership Project (also known as "3GPP") is a collaborative agreement that develops globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. 3GPP develops specifications for next generation mobile networks, systems, and devices.

[0029] 3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future 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).

[0030] At least some aspects of the systems and methods disclosed herein may be described in conjunction with 3GPP LTE, LTE-Advanced (LTE-A), and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, and / or 15). However, the scope of the present disclosure should not be limited in this respect. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.

[0031] A wireless communication device may be an electronic device that transmits voice and / or data to a base station, which in turn may communicate with a network of devices (e.g., a public switched telephone network (PSTN), the Internet, etc.). When describing the systems and methods herein, a wireless communication device 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 devices include cellular phones, smartphones, personal digital assistants (PDAs), laptops, netbooks, e-readers, wireless modems, etc. In the 3GPP specifications, a wireless communication device is generally referred to as a UE. However, since the scope of the present disclosure should not be limited to the 3GPP standards, the terms "UE" and "wireless communication device" may be used interchangeably herein to represent the more general term "wireless communication device." A UE may also be more generally referred to as a terminal device.

[0032] In the 3GPP specifications, a base station is often referred to as a Node B, an evolved Node B (eNB), a home-enhanced or evolved Node B (HeNB), or some other similar term. Because the scope of the present disclosure should not be limited to the 3GPP standards, the terms "base station," "Node B," "eNB," "gNB," and "HeNB" may be used interchangeably herein to refer to the more general term "base station." In addition, the term "base station" may be used to refer to an access point. An access point may be an electronic device that provides wireless communication devices with access to a network (e.g., a local area network (LAN), the Internet, etc.). The term "communication device" may be used to refer to a wireless communication device and / or a base station. An eNB may also be more generally referred to as a base station device.

[0033] It should be noted that, as used herein, a "cell" can be any communication channel designated by standardization or regulatory agencies for use with International Mobile Telecommunications-Advanced (IMT-Advanced), and all or a subset thereof, adopted by 3GPP as an authorized frequency band (e.g., a frequency band) for communication between an eNB and a UE. It should also be noted that, in the general description 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 frequency of the downlink resources and the carrier frequency of the uplink resources can be indicated in system information sent on the downlink resources.

[0034] The fifth-generation communication system, referred to as NR (New Radio Technology) by 3GPP, envisions the use of time / frequency / space 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 parts (BWPs) in a serving cell and / or one or more serving cells may be designated (e.g., configured) for transmission of different services. A user equipment (UE) may receive downlink signals and / or transmit uplink signals in the BWP of the serving cell.

[0035] In order for services to efficiently use time, frequency, and / or space resources, it would be useful to be able to effectively control downlink and / or uplink transmissions. Therefore, a process for effectively controlling downlink and / or uplink transmissions should be designed. Therefore, a detailed design of the process for downlink and / or uplink transmissions may be beneficial.

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

[0037] Figure 1 is a block diagram illustrating one embodiment of one or more gNBs 160 and one or more UEs 102 in which systems and methods for signaling may be implemented. The one or more UEs 102 communicate with the one or more gNBs 160 using one or more physical antennas 122a-n. For example, the UE 102 transmits electromagnetic signals to the gNB 160 and receives electromagnetic signals from the gNB 160 using the one or more physical antennas 122a-n. The gNB 160 communicates with the UE 102 using one or more physical antennas 180a-n. In some implementations, the terms "base station," "eNB," and / or "gNB" may refer to and / or be replaced by the term "transmit receive point (TRP)." For example, in some implementations, in conjunction with Figure 1 The gNB 160 described may be a TRP.

[0038] UE 102 and gNB 160 may communicate with each other using one or more channels and / or one or more signals 119, 121. For example, UE 102 may use one or more uplink channels 121 to send 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 may also use one or more downlink channels 119 to send 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 may also be used.

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

[0040] The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. The one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert a signal to produce one or more received signals 116. The one or more received signals 116 may be provided to the demodulator 114. The one or more transmitters 158 may transmit signals to the gNB 160 using one or more physical antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit the one or more modulated signals 156.

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

[0042] Generally speaking, the UE operations module 124 may enable the UE 102 to communicate with one or more gNBs 160. The UE operations module 124 may include one or more of the UE scheduling modules 126.

[0043] The UE scheduling module 126 may perform downlink reception and uplink transmission. The one or more downlink receptions may include reception of data, reception of downlink control information, and / or reception of downlink reference signals. Additionally, uplink transmissions may include transmission of data, transmission of uplink control information, and / or transmission of uplink reference signals.

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

[0045] For example, in the uplink, a PRACH (physical random access channel) may be defined. In some methods, the PRACH (e.g., a random access procedure) may be used for an initial access connection establishment procedure, a handover procedure, a connection reestablishment, timing adjustment (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).

[0046] In another example, a physical uplink control channel (PUCCH) may be defined. The PUCCH may be used to transmit uplink control information (UCI). The UCI may include a hybrid automatic repeat request acknowledgement (HARQ-ACK), channel state information (CSI), and / or a scheduling request (SR). The HARQ-ACK is used to indicate a positive acknowledgement (ACK) or negative acknowledgement (NACK) of downlink data (e.g., a transport block, a medium access control protocol data unit (MAC PDU), and / or a downlink shared channel (DL-SCH)). The CSI is used to indicate the state of a downlink channel (e.g., a downlink signal). In addition, the SR is used to request resources for uplink data (e.g., a transport block, a MAC PDU, and / or an uplink shared channel (UL-SCH)).

[0047] Here, DL-SCH and / or UL-SCH may be transport channels used in the MAC layer. Furthermore, a transport block (TB) and / or a MAC PDU may be defined as a unit of a transport channel used in the MAC layer. A transport block may be defined as a unit of data delivered from the MAC layer to the physical layer. The MAC layer may deliver a transport block to the physical layer (e.g., the MAC layer delivers data as a transport block to the physical layer). In the physical layer, a transport block may be mapped to one or more codewords.

[0048] In the downlink, a physical downlink control channel (PDCCH) may be defined. The PDCCH may be used to transmit downlink control information (DCI). Here, more than one DCI format may be defined for DCI transmission on the PDCCH. That is, fields may be defined in the DCI format and mapped to information bits (e.g., DCI bits).

[0049] For example, DCI format 1_0 for scheduling the PDSCH in a cell may be defined as a DCI format for the downlink. In addition, 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) may be used to transmit DCI format 1_0. Furthermore, DCI format 1_0 may be monitored (e.g., transmitted, mapped) in a common search space (CSS) and / or a UE-specific search space (USS). Alternatively, DCI format 1_0 may be monitored (e.g., transmitted, mapped) only in the CSS.

[0050] 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 a scheduled 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). That is, the β offset indicator may not be included in DCI format 1_0.

[0051] Here, the priority indication may be used to indicate the priority of PDSCH transmission and / or PDSCH reception (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 (e.g., decodes, receives) a DCI format for downlink including a priority indication, UE 102 may recognize that PDSCH transmission and / or PDSCH reception is prioritized (e.g., PDSCH transmission and / or PDSCH reception has higher priority, highest priority, lower priority, and / or lowest priority).

[0052] Additionally or alternatively, a priority indication may be used to indicate a priority of HARQ-ACK transmission for PDSCH 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 for downlink including a priority indication, UE 102 may recognize that HARQ-ACK transmission for PDSCH and / or HARQ-ACK reception for PDSCH is prioritized (e.g., HARQ-ACK transmission for PDSCH and / or HARQ-ACK reception for PDSCH has a higher priority, a highest priority, a lower priority, and / or a lowest priority). Additionally or alternatively, when UE 102 detects a DCI format for downlink including a priority indication, UE 102 may generate two HARQ-ACK codebooks for two PDSCH transmissions. For example, when UE 102 detects a DCI format for downlink including a priority indication, a first HARQ-ACK codebook is generated for the first PDSCH transmission, and a second HARQ-ACK codebook is generated for the second PDSCH transmission. Additionally or alternatively, UE 102 may simultaneously transmit two HARQ-ACK codebooks (e.g., in symbols and / or time slots). That is, UE 102 may simultaneously transmit a first HARQ-ACK corresponding to the first HARQ-ACK codebook and a second HARQ-ACK corresponding to the second HARQ-ACK codebook (e.g., in symbols and / or time slots).

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

[0054] 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 a scheduled PUCCH. Additionally or alternatively, the DCI included in DCI format 1_1 may be a CSI request for requesting (e.g., triggering) transmission of CSI (e.g., a CSI report (e.g., an aperiodic CSI report)). Additionally or alternatively, the DCI included in DCI format 1_1 may be a PUCCH resource indicator. Additionally or alternatively, the DCI included in DCI format 1_1 may be a PDSCH-to-HARQ feedback timing indicator. Additionally or alternatively, the DCI included in DCI format 1_1 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_1 may be a priority indication (e.g., for HARQ-ACK transmission of PDSCH and / or for HARQ-ACK reception of PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 may be a β offset indicator.

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

[0056] 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 a scheduled 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)). Additionally or alternatively, the DCI included in DCI format 1_X may be a PUCCH resource indicator. Additionally or alternatively, the DCI included in DCI format 1_X may be a PDSCH-to-HARQ feedback timing indicator. Additionally or alternatively, the DCI included in DCI format 1_X 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_X may be a priority indication (e.g., for HARQ-ACK transmission of PDSCH and / or for HARQ-ACK reception of PDSCH). Additionally or alternatively, the DCI included in DCI format 1_X may be a beta offset indicator.

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

[0058] Additionally or alternatively, DCI format 1_X (and / or DCI format 1_X including a priority indication, and / or DCI format 1_X with a CRC scrambled by the first RNTI, and / or DCI format 1_X with a CRC scrambled by the first RNTI including a priority indication) may be used to indicate a priority (e.g., higher priority, highest priority, lower priority, and / or lowest priority) of HARQ-ACK transmission for PDSCH and / or HARQ-ACK reception for PDSCH. For example, in the case where UE 102 detects DCI format 1_X (and / or DCI format 1_X including a priority indication, and / or DCI format 1_X with a CRC scrambled by a first RNTI, and / or DCI format 1_X with a CRC scrambled by a first RNTI including a priority indication), UE 102 may recognize 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 a higher priority, a highest priority, a lower priority, and / or a lowest priority).

[0059] Additionally or alternatively, when the UE 102 detects DCI format 1_X (and / or DCI format 1_X including a priority indication, and / or DCI format 1_X with a CRC scrambled by the first RNTI, and / or DCI format 1_X with a CRC scrambled by the first RNTI including a priority indication), the UE 102 may generate two HARQ-ACK codebooks for two PDSCH transmissions. For example, when the UE 102 detects a DCI format for downlink including a priority indication, a first HARQ-ACK codebook is generated for the first PDSCH transmission, and a second HARQ-ACK codebook is generated for the second PDSCH transmission. Additionally or alternatively, the UE 102 may transmit the two HARQ-ACK codebooks simultaneously (e.g., in symbols and / or slots). That is, the UE 102 may simultaneously send a first HARQ-ACK corresponding to the first HARQ-ACK codebook and a second HARQ-ACK corresponding to the second HARQ-ACK codebook (eg, in symbols and / or time slots).

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

[0061] For example, the DCI included in DCI format 0_0 may be a frequency domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a time domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_0 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_0 may be a redundancy version. Additionally or alternatively, the DCI included in DCI format 0_0 may be a TPC command for a scheduled PUSCH. 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). That is, the β offset indicator may not be included in DCI format 0_0. In addition, the UL-SCH indicator may not be included in DCI format 0_0.

[0062] Here, the priority indication may be used to indicate the priority of PUSCH transmission and / or PUSCH reception (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 for uplink including a priority indication, UE 102 may recognize that PUSCH transmission and / or PUSCH reception is prioritized (e.g., PUSCH transmission and / or PUSCH reception has a higher priority, a highest priority, a lower priority, and / or a lowest priority). Additionally or alternatively, when UE 102 detects a DCI format for uplink including a priority indication, UE 102 may generate two PUSCHs for two UL-SCH transmissions. For example, when the UE 102 detects a DCI format for the uplink that includes a priority indication, a first transmission is performed on a first PUSCH (e.g., for a first UL-SCH, a first PUSCH to which the first UL-SCH is mapped), and a second transmission is performed on a second PUSCH (e.g., for a second UL-SCH, a second PUSCH to which the second UL-SCH is mapped). Additionally or alternatively, the UE 102 may perform simultaneous transmission of two PUSCHs (e.g., in a symbol and / or time slot). For example, the UE 102 may perform simultaneous transmission of a first PUSCH corresponding to the first UL-SCH and a second PUSCH corresponding to the second UL-SCH (e.g., in a symbol and / or time slot).

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

[0064] 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 a scheduled 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 a configuration index for a configuration grant. Additionally or alternatively, the DCI included in DCI format 0_1 may be a priority indicator (e.g., for PUSCH transmission and / or for PUSCH reception). Additionally or alternatively, the DCI included in DCI format 0_1 may be a beta offset indicator. Additionally or alternatively, the DCI included in DCI format 0_1 may be a UL-SCH indicator.

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

[0066] 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 a scheduled 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 a configuration index for a configuration grant. 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). Additionally or alternatively, the DCI included in DCI format 0_1 may be a beta offset indicator. Additionally or alternatively, the DCI included in DCI format 0_1 may be a UL-SCH indicator.

[0067] Here, DCI format 0_Y (and / or DCI format 0_Y including a priority indication, and / or DCI format 0_Y having a CRC scrambled by the first RNTI, and / or DCI format 0_Y having a CRC scrambled by the first RNTI including a priority indication) may be used to indicate a priority (e.g., higher priority, highest priority, lower priority, and / or lowest priority) of PUSCH transmission and / or PUSCH reception. For example, when UE 102 detects DCI format 0_Y (and / or DCI format 0_Y including a priority indication, and / or DCI format 0_Y having a CRC scrambled by the first RNTI, and / or DCI format 0_Y having a CRC scrambled by the first RNTI including a priority indication), UE 102 may recognize that PUSCH transmission and / or PUSCH reception is prioritized (e.g., PUSCH transmission and / or PUSCH reception has a higher priority, the highest priority, the lower priority, and / or the lowest priority).

[0068] Additionally or alternatively, when the UE 102 detects DCI format 0_Y (and / or DCI format 0_Y including a priority indication, and / or DCI format 0_Y with a CRC scrambled by the first RNTI, and / or DCI format 0_Y with a CRC scrambled by the first RNTI including a priority indication), the UE 102 may generate two PUSCHs for two UL-SCH transmissions. For example, when the UE 102 detects a DCI format for the uplink including a priority indication, a first transmission may be performed on a first PUSCH (e.g., for a first UL-SCH, a first PUSCH to which the first UL-SCH is mapped), and a second transmission may be performed on a second PUSCH (e.g., for a second UL-SCH, a second PUSCH to which the second UL-SCH is mapped). Additionally or alternatively, the UE 102 may perform simultaneous transmission of the two PUSCHs (e.g., in symbols and / or slots). For example, the UE 102 can perform simultaneous transmission (eg, in symbols and / or time slots) of a first PUSCH corresponding to a first UL-SCH and a second PUSCH corresponding to a second UL-SCH.

[0069] Additionally or alternatively, upon receiving DCI format 1_0, DCI format 1_1, and / or DCI format 1_X (e.g., based on detecting DCI format 1_0, DCI format 1_1, 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 detecting DCI format 0_0, DCI format 0_1, DCI format 0_Y), UE 102 may perform PUSCH transmission.

[0070] Here, as described above, the RNTI (e.g., Radio Network Temporary Identifier) allocated to UE 102 may be used for 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 may transmit information for configuring (e.g., allocating) the RNTI to UE 102 (e.g., by using an RRC message).

[0071] For example, CRC (cyclic redundancy check) parity bits (also referred to as CRC) generated based on the DCI are attached to the DCI, and after attachment, the CRC parity bits are scrambled by the RNTI. UE 102 may attempt to decode (e.g., blindly decode, monitor, or detect) the DCI to which the CRC parity bits scrambled by the RNTI are attached. For example, UE 102 may detect a downlink control channel (e.g., PDCCH, DCI, or DCI format) based on blind decoding. That is, UE 102 may decode the downlink control channel using the CRC scrambled by the RNTI. In other words, UE 102 may monitor the downlink control channel using the RNTI. For example, UE 102 may detect the DCI format using the RNTI.

[0072] Here, the 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.

[0073] For example, the C-RNTI can be a unique identifier for identifying an RRC connection and / or scheduling. Additionally or alternatively, the CS-RNTI can be a unique identifier for scheduling transmissions based on configuration-based authorization. Additionally or alternatively, the SI-RNTI can be used to identify a system message (SI) (e.g., an SI message) mapped on the BCCH and dynamically carried on the DL-SCH. Additionally or alternatively, the SI-RNTI can be used for broadcasting of the SI. Additionally or alternatively, the RA-RNTI can be an identifier for a random access procedure (e.g., Msg.2 transmission). Additionally or alternatively, a temporary C-RNTI can be used for a random access procedure (e.g., scheduling of a Msg.3 (re)transmission (e.g., Msg.3 PUSCH (re)transmission)).

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

[0075] Additionally or alternatively, as described above, the first RNTI may be an identifier for indicating the priority (e.g., higher priority, highest priority, lower priority, and / or lowest priority) of PDSCH transmission and / or PDSCH reception. Additionally or alternatively, as described above, the first RNTI may be an identifier for indicating the priority (e.g., higher priority, highest priority, lower priority, and / or lowest priority) of PUSCH transmission and / or PUSCH reception.

[0076] Additionally or alternatively, a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) may be defined. For example, when a PDSCH (e.g., PDSCH resources) is scheduled using a DCI format for the downlink, the UE 102 may receive downlink data on the scheduled PDSCH (e.g., PDSCH resources). Additionally or alternatively, when a PUSCH (e.g., PUSCH resources) is scheduled using a DCI format for the uplink, the 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 blocks). Additionally or alternatively, the PUSCH may be used to transmit uplink data (e.g., UL-SCH, uplink transport blocks).

[0077] Furthermore, the PDSCH and / or PUSCH may be used to transmit information from higher layers (e.g., the radio resource control (RRC) layer and / or the MAC layer). For example, the PDSCH (e.g., from the gNB 160 to the UE 102) and / or the PUSCH (e.g., from the UE 102 to the gNB 160) may be used to transmit RRC messages (RRC signals). Additionally or alternatively, the PDSCH (e.g., from the gNB 160 to the UE 102) and / or the PUSCH (e.g., from the UE 102 to the gNB 160) may be used to transmit MAC control elements (MAC CEs). Herein, the RRC messages and / or MAC CEs are also referred to as higher layer signals.

[0078] In some methods, a physical broadcast channel (PBCH) may be defined. For example, the PBCH may be used to broadcast a Master Information Block (MIB). Here, system information may be divided into a MIB and multiple System Information Blocks (SIBs). For example, the MIB may be used to carry minimum system information. Additionally or alternatively, the SIB may be used to carry system information messages.

[0079] In some methods, in the downlink, a synchronization signal (SS) may be defined. The SS may be used to acquire time and / or frequency synchronization with a cell. Additionally or alternatively, the SS may be used to detect the physical layer cell ID of a cell.

[0080] In uplink radio communication, the UL RS may be used as an uplink physical signal. Additionally or alternatively, in downlink radio communication, the DL RS may be used as a downlink physical signal. The uplink physical signal and / or the downlink physical signal may not be used to transmit information provided by a higher layer, but may be used by the physical layer.

[0081] Here, for simplicity of description, in some implementations, it may be assumed that the downlink physical channels and / or downlink physical signals described herein are included in downlink signals (e.g., DL signals). Additionally or alternatively, for simplicity of description, in some implementations, it may be assumed that the uplink physical channels and / or uplink physical signals described herein are included in uplink signals (i.e., UL signals).

[0082] Furthermore, in carrier aggregation (CA), gNB 160 and UE 102 may 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 may use an RRC message to transmit information for configuring one or more secondary cells to form a serving cell set together with the primary cell. That is, a set of serving cells may include a primary cell and one or more secondary cells. Here, the primary cell may be always activated. Furthermore, gNB 160 may activate one or more secondary cells within the configured secondary cells. Here, in the downlink, the carrier corresponding to the primary cell may be a downlink primary component carrier (i.e., DL PCC), and the carrier corresponding to the secondary cell may be a downlink secondary component carrier (i.e., DL SCC). Furthermore, in the uplink, the carrier corresponding to the primary cell may be an uplink primary component carrier (i.e., UL PCC), and the carrier corresponding to the secondary cell may be an uplink secondary component carrier (i.e., UL SCC).

[0083] The UE operations module 124 may provide information 148 to the one or more receivers 120. For example, the UE operations module 124 may inform the one or more receivers 120 when to receive a retransmission.

[0084] UE operations module 124 may provide information 138 to demodulator 114. For example, UE operations module 124 may inform demodulator 114 of the modulation pattern expected for transmissions from gNB 160.

[0085] The UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of the encoding to expect for the transmission from the gNB 160.

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

[0087] The encoder 150 may encode the transmission data 146 and / or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and / or other information 142 may involve error detection and / or correction coding, mapping the data to spatial, time, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to a modulator 154.

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

[0089] UE operations module 124 may provide information 140 to one or more transmitters 158. The information 140 may include instructions for one or more transmitters 158. For example, UE operations module 124 may instruct one or more transmitters 158 when to transmit signals to gNB 160. For example, one or more transmitters 158 may transmit during a UL subframe. One or more transmitters 158 may upconvert one or more modulated signals 156 and transmit the one or more modulated signals to one or more gNB 160.

[0090] Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162, and a gNB operations module 182. For example, one or more receive paths and / or transmit paths may be implemented in the gNB 160. For convenience, 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.

[0091] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals from the UE 102 using one or more physical antennas 180a-n. For example, the receiver 178 may receive and downconvert a signal to produce one or more received signals 174. The one or more received signals 174 may be provided to the demodulator 172. The one or more transmitters 117 may transmit signals to the UE 102 using one or more physical antennas 180a-n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.

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

[0093] Generally, the gNB operations module 182 may enable the gNB 160 to communicate with one or more UEs 102. The gNB operations module 182 may include one or more of the gNB scheduling modules 194. The gNB scheduling module 194 may perform scheduling of downlink and / or uplink transmissions as described herein.

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

[0095] The gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of the encoding to be expected for transmissions from one or more UEs 102.

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

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

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

[0099] The gNB operations module 182 may provide information 192 to the one or more transmitters 117. The information 192 may include instructions for the one or more transmitters 117. For example, the gNB operations module 182 may instruct the one or more transmitters 117 when (or when not) to transmit signals to the one or more UEs 102. The one or more transmitters 117 may upconvert the one or more modulated signals 115 and transmit the one or more modulated signals to the one or more UEs 102.

[0100] It should be noted that DL subframes may be sent from the gNB 160 to one or more UEs 102, and UL subframes may be sent from one or more UEs 102 to the gNB 160. In addition, both the gNB 160 and one or more UEs 102 may transmit data in standard special subframes.

[0101] It should also be noted that one or more of the elements or components thereof included in one or more eNBs 160 and one or more UEs 102 may be implemented in hardware. For example, one or more of these elements or components may be implemented as a chip, a circuit, a hardware component, 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 in and / or implemented using a chipset, an application specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc.

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

[0103] Additionally or alternatively, the number of OFDM symbols 203 per slot may be determined based on μ (eg, subcarrier spatial configuration). Here, for example, slot configuration 0 (eg, the number of OFDM symbols 203 per slot may be 14) and / or slot configuration (eg, the number of OFDM symbols 203 per slot may be 7) may be defined.

[0104] Figure 3 is a diagram illustrating one example of a resource grid 301 and resource blocks 391 (eg, for downlink and / or uplink). Figure 3 The resource grid 301 and resource blocks 391 shown may be used in some implementations of the systems and methods disclosed herein.

[0105] exist Figure 3 In the example, a subframe 369 may include Symbols 387. Additionally or alternatively, a 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 adopted, 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). A downlink RB pair is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. A downlink RB pair may include two downlink RBs 391 that are consecutive in the time domain.

[0106] 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 region 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 indices in the frequency domain and time domain, respectively.

[0107] Additionally or alternatively, in the uplink, in addition to CP-OFDM, a single-carrier frequency division multiple access (SC-FDMA) access scheme, also known as discrete Fourier transform spread 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 for allocating uplink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot. An uplink RB pair may include two uplink RBs 391 that are consecutive 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 region 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 indices in the frequency and time domains, respectively.

[0108] Each element (eg, antenna port p) and subcarrier configuration μ in the resource grid 301 is referred to as a resource element 389 and is uniquely identified by an index pair (k, l), where k=0, ..., is an index in the frequency domain, and l refers to the symbol position in the time domain. The resource element (k, l) 389 on antenna port p and the subcarrier spacing configuration μ are denoted as (k, l) p, μ. The physical resource RR block 391 is defined as The physical resource block 391 is from 0 to Number. Physical resource block number in the frequency domain n The relationship between PRB and resource element (k, l) is given by:

[0109] 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., a control resource set (i.e., CORESET)) can be configured for DL control channel monitoring (e.g., PDCCH monitoring). For example, a CORESET is a set 401 of PRBs 491 in the frequency domain and / or time domain, within which a UE 102 attempts to decode DCI (e.g., DCI format, PDCCH). In the case where the PRBs 491 may or may not be frequency-contiguous and / or time-contiguous, the UE 102 can be configured with one or more control resource sets (e.g., CORESETs), and one DCI message can be mapped within the one control resource set. In the frequency domain, a PRB 491 is the resource unit size of a DL control channel (which may or may not include a DM-RS).

[0110] UE 102 may monitor a set of PDCCH candidates in one or more control resource sets (e.g., CORESETs) on the active DL bandwidth part (BWP) on each activated serving cell according to the corresponding search space set. Here, the term "monitoring" may imply that UE 102 attempts to decode each PDCCH (e.g., a set of PDCCH candidates) according to the monitored DCI format. In addition, the PDCCH candidates may be candidates to which a DL control channel may be mapped, allocated, and / or transmitted.

[0111] The set of PDCCH candidates to be monitored by UE 102 may be defined according to a search space set (e.g., also referred to as a search space). UE 102 may monitor the PDCCH candidate set according to 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).

[0112] That is, the CSS and / or USS may be defined (e.g., configured) in a region of the DL control channel. For example, the CSS may be used to send DCI to multiple UEs 102. For example, a Type 0-PDCCH common search space may be defined for one or more DCI formats having a CRC scrambled by an SI-RNTI. Additionally or alternatively, a Type 1-PDCCH common search space may be defined for a DCI format having a CRC scrambled by an RA-RNTI, a temporary C-RNTI, and / or a C-RNTI. Additionally or alternatively, a Type 3-PDCCH common search space may be defined for one or more DCI formats having a CRC scrambled by a C-RNTI and / or a CS-RNTI.

[0113] The USS may be used to send DCI to a specific UE 102. For example, the USS may be determined based on a radio network temporary identifier (RNTI) (e.g., C-RNTI). For example, the USS may be defined for one or more DCI formats having a CRC scrambled by the C-RNTI and / or CS-RNTI.

[0114] Here, the gNB 160 may transmit first information for configuring (e.g., determining) one or more CORESETs using an RRC message. For example, for each DL BWP in a DL BWP (e.g., each DL BWP in a serving cell), the gNB 106 may transmit first information for configuring one or more CORESETs using an RRC message. For example, the first information may include information for configuring an index of the CORESET. In addition, the first information may include information for configuring a plurality of consecutive symbols for the CORESET. In addition, the first information may include information for configuring a resource block set of the CORESET.

[0115] Here, the index "0" of the CORESET (i.e., the value "0" of the CORESET) can be configured by 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, an index of a CORESET other than the value "0" can be configured as the index of the CORESET. In addition, the index of the CORESET with the value "0" can be configured by using information of CORESET-zero. In addition, the index "0" of the CORESET can be configured by using a dedicated RRC message (i.e., a UE-specific RRC message and / or a serving cell-specific RRC message). That is, the gNB 160 can transmit information for configuring the CORESET with the index "0" (i.e., CORESET#0) by using the MIB. Additionally or alternatively, the gNB 160 can transmit information for configuring CORESET#0 by using the SIB. Additionally or alternatively, the gNB 160 can transmit information for configuring CORESET#0 by using a dedicated RRC message.

[0116] Here, CORESET #0 may be configured for an initial BWP (e.g., an initial DL BWP). Here, the gNB 160 may transmit information for the initial BWP (e.g., an initial DL BWP) using an RRC message (e.g., an MIB, an SIB, and / or a dedicated RRC message). Furthermore, the index of the initial BWP (e.g., an initial DL BWP) may be "0." That is, an index of "0" (e.g., a value of "0") may be applied (e.g., defined) to the initial BWP (e.g., an initial DL BWP). For example, (e.g., for a primary cell), the initial BWP (i.e., a BWP with an index of "0") may be the BWP used for initial access. Additionally or alternatively, (e.g., for a secondary cell), the initial BWP (i.e., a BWP with an index of "0") may be the BWP configured for the UE to first operate in the secondary cell when the secondary cell is activated.

[0117] Here, the gNB 160 may transmit information on the index (e.g., index other than index '0') for configuring the DL BWP by using an RRC message (e.g., MIB, SIB, and / or dedicated RRC message). Additionally, the gNB 160 may transmit information on the index (e.g., index other than index '0') for configuring the UL BWP by using an RRC message (e.g., MIB, SIB, and / or dedicated RRC message).

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

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

[0120] Additionally or alternatively, gNB 160 may transmit second information for configuring the search space set using an RRC message. 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 a PDCCH monitoring periodicity and / or a PDCCH monitoring offset for monitoring PDCCHs in the search space set. Additionally or alternatively, the second information may include information for indicating a PDCCH monitoring pattern within a timeslot. For example, the information for indicating the PDCCH monitoring pattern may indicate the first symbol within the timeslot for PDCCH monitoring. For example, UE 102 may determine a PDCCH monitoring timing based on the PDCCH monitoring periodicity, the PDCCH monitoring offset, and / or the PDCCH monitoring pattern within the timeslot.

[0121] Additionally or alternatively, the second information may include information indicating the type of the 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 of one or more DCI formats for instructing UE 102 to monitor 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 a 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 for monitoring the PDCCH in the CSS may be scrambled by a C-RNTI, a CS-RNTI, a RA-RNTI, a temporary C-RNTI, an SI-RNTI, and / or a first RNTI.

[0122] Additionally or alternatively, if the search space set is a USS (e.g., if the search space set is configured as a USS), DCI format 0_0, DCI format 1_0, DCI format 0_Y, and / or DCI format 1_X may be configured to monitor a PDCCH (e.g., a PDCCH candidate). Additionally or alternatively, if the search space set is a USS, DCI format 0_1, DCI format 1_1, DCI format 0_Y, and / or DCI format 1_X may be configured to monitor a PDCCH (e.g., a PDCCH candidate). For example, if the search space set is a USS, any of the first group of DCI formats (e.g., DCI format 0_0, DCI format 1_0, and / or DCI format 0_Y, and / or DCI format 1_X) or the second group of DCI formats (e.g., DCI format 0_1, DCI format 1_1, DCI format 0_Y, and / or DCI format 1_X) may be configured to monitor a PDCCH (e.g., a PDCCH candidate). Here, the DCI format for monitoring the PDCCH in the USS may be scrambled by the C-RNTI, CS-RNTI, and / or the first RNTI. For example, the second information may be configured according to the search space set. That is, the second information may be configured for each search space set.

[0123] Here, the search space set index "0" (i.e., the search space set value "0") may be configured using the MIB and / or SIB. For example, the search space set index "0" may 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" may be configured as the search space index. Furthermore, the index of a search space set with the value "0" may be configured using information related to search space-zero. Furthermore, the search space set index "0" may be configured using a dedicated RRC message (i.e., a UE-specific RRC message and / or a serving cell-specific RRC message). That is, the gNB 160 may transmit information for configuring the search space set with the index "0" (i.e., search space set #0) using the MIB. Additionally or alternatively, the gNB 160 may transmit information for configuring search space set #0 using the SIB. Additionally or alternatively, the gNB 160 may transmit information for configuring search space set #0 using a dedicated RRC message. Here, search space set #0 may be configured for an initial BWP (eg, initial DL BWP).

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

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

[0126] Additionally or alternatively, for the serving cell, the gNB 160 may configure four UL BWP sets (e.g., up to four UL BWPs, one UL BWP set) using RRC messaging (e.g., for transmission by the UE 102). Additionally or alternatively, the gNB 160 may indicate the active UL BWP using a DCI format for the uplink. Additionally or alternatively, for each UL BWP in the UL BWP set, the gNB 160 may configure the subcarrier spacing, cyclic prefix, number of consecutive PRBs 491 (e.g., bandwidth of the PRBs), index (e.g., index of the UL BWP, UL BWPID) in the UL BWP set using RRC messaging.

[0127] Additionally or alternatively, the UE 102 may perform reception on the PDCCH in the DL BWP and / or reception on the PDSCH in the DL BWP based on the configuration for the DL BWP. Additionally or alternatively, the UE 102 may perform based on the configuration for the UL BWP.

[0128] Figure 5 An example of uplink transmission is shown. Figure 5As shown, processing (e.g., processing structure) for a UL-SCH transport channel on one UL cell may be performed. Here, UL-SCH (e.g., uplink data) may be mapped to PUSCH (e.g., resources (i.e., resource elements) of PUSCH). Additionally or alternatively, UCI (i.e., HARQ-ACK, CSI and / or SR) may be mapped to PUSCH (e.g., resources (i.e., resource elements) of PUSCH). Here, the CSI report may include an aperiodic CSI report, a semi-persistent CSI report and / or a periodic CSI report. Additionally or alternatively, the CSI report may include a CSI part 1 report, a CSI part 2 report, a CQI (e.g., channel quality information) report, a PMI (e.g., precoding matrix information) report and / or an RI (e.g., rank indication) report.

[0129] For example, if the UE 102 is to perform a PUSCH transmission without UL-SCH on the serving cell, which PUSCH transmission overlaps with a PUSCH transmission including UCI (e.g., HARQ-ACK and / or positive SR information) on the serving cell, the UE 102 may not perform the PUSCH transmission. Additionally or alternatively, if the UE 102 is to perform a PUSCH transmission without UL-SCH on the serving cell, which PUSCH transmission overlaps with a PUSCH transmission including a CSI report (e.g., a semi-persistent CSI report) on the serving cell, the UE 102 may not perform the PUSCH with the CSI report (e.g., a semi-persistent CSI report). If UE 102 performs (e.g., will perform) a PUSCH transmission with UL-SCH that overlaps with a PUCCH transmission including UCI (e.g., HARQ-ACK, semi-persistent CSI information, and / or periodic CSI information), UE 102 may multiplex the UCI (e.g., HARQ-ACK, semi-persistent CSI information, and / or periodic CSI information) on the PUSCH.

[0130] For example, in the case where a PUSCH transmission overlaps with a PUCCH transmission including UCI (e.g., HARQ-ACK and / or CSI) at the same timing (e.g., in the same slot and / or symbol), the UE 102 may multiplex the UL-SCH (e.g., uplink data) and the UCI (e.g., HARQ-ACK and / or CSI) on the PUSCH. For example, the UE 102 may transmit the UL-SCH together with the UCI (e.g., HARQ-ACK and / or CSI) on the PUSCH at the same timing (e.g., in the same slot and / or the same symbol).

[0131] Here, the HARQ-ACK may include one or more HARQ-ACKs. That is, the HARQ-ACK may include one or more HARQ-ACK codebooks (e.g., two HARQ-ACK codebooks as described above). For example, the HARQ-ACK may include one or more HARQ-ACKs for one or more PDSCHs (e.g., PDSCH transmissions).

[0132] For example, HARQ-ACK-1 519 (i.e., a first HARQ-ACK codebook) for one or more PDSCHs and HARQ-ACK-2 521 (i.e., a second HARQ-ACK codebook) for one or more PDSCHs may be sent (e.g., simultaneously, as described above) on a single PUSCH resource (e.g., mapped to a single, same PUSCH resource). Additionally or alternatively, HARQ-ACK-1 519 and HARQ-ACK-2 521 may be independently (e.g., separately) encoded and mapped to PUSCH resources. For example, the number of resources (e.g., the number of resource elements, the number of coded symbols, and / or the number of coded modulation symbols) of HARQ-ACK-1 519 may be dynamically changed according to the PUSCH (e.g., the PUSCH resource). Additionally or alternatively, the number of resources (e.g., the number of resource elements, the number of coded symbols, and / or the number of coded modulation symbols) of HARQ-ACK-2 521 may be dynamically changed according to the PUSCH (e.g., PUSCH resources). Additionally or alternatively, the number of resources of HARQ-ACK-1 519 and the number of resources of HARQ-ACK-2 521 may be changed separately according to the PUSCH (e.g., PUSCH resources). For example, the number of resources of HARQ-ACK-1 519 and the number of resources of HARQ-ACK-2 521 may be changed separately based on configuration (e.g., RRC configuration) and / or indication (e.g., DCI indication).

[0133] Additionally or alternatively, the CSI may include one or more CIS. That is, the CSI may include one or more CSI reports (e.g., two CSI reports). For example, the CSI may include one or more CIS for one or more PDSCHs (e.g., PDSCH transmissions). For example, CSI-1 515 (i.e., a first CSI report) for one or more PDSCHs and CSI-2 517 (i.e., a second CSI report) for one or more PDSCHs may be transmitted (e.g., transmitted simultaneously) on a single PUSCH resource (e.g., mapped to a single PUSCH resource (e.g., mapped to a single, identical PUSCH resource)). Additionally or alternatively, CSI-1 515 and CSI-2 517 may be independently (e.g., separately) encoded and mapped to PUSCH resources. For example, the number of resources (e.g., the number of resource elements, the number of coded symbols, and / or the number of coded modulation symbols) of CSI-1 515 may be dynamically changed according to the PUSCH (e.g., PUSCH resources). Additionally or alternatively, the resource quantity (e.g., the number of resource elements, the number of coded symbols, and / or the number of coded modulation symbols) of CSI-2 517 may be dynamically changed according to the PUSCH (e.g., PUSCH resources). Additionally or alternatively, the resource quantity of CSI-1 515 and the resource quantity of CSI-2 517 may be changed separately according to the PUSCH (e.g., PUSCH resources). For example, the resource quantity of CSI-1 515 and the resource quantity of CSI-2 517 may be changed separately based on configuration (e.g., RRC configuration) and / or indication (e.g., DCI indication).

[0134] Targeted Figure 5 Refer to one or more of the following descriptions. For uplink shared channel, Figure 5 The processing structure of the UL-SCH transport channel on a UL cell is shown. Data arrives at the coding unit in the form of up to two transport blocks per transmission time interval (TTI) per UL cell. The following coding steps can be identified for each transport block 501 of the UL cell:

[0135] Adding CRC 503 to the transport block 501;

[0136] Code block segmentation and code block CRC appending 505;

[0137] Channel coding 507a-e for data and control information;

[0138] Rate matching 509;

[0139] Code block concatenation 511a-b;

[0140] Multiplexing of data and control information;

[0141] Channel interleaver 513.

[0142] An example of transport block CRC addition is as follows. Error detection is provided for each UL-SCH transport block by a cyclic redundancy check (CRC). The entire transport block is used to calculate the CRC parity bits. The bits delivered to layer 1 in the transport block are represented by a0, a1, a2, a3, ..., a A-1 Represented by, and the parity bits are P0, P1, P2, P3, ..., P L-1 A is the size of the transport block, and L is the number of parity bits. The lowest-order information bit a0 is mapped to the most significant bit of the transport block. Parity bits are calculated and appended to the UL-SCH transport block.

[0143] An example of code block segmentation and code block CRC appending is described below. The bits input to the code block segmentation are represented by b0, b1, b2, b3, ..., b B-1 , where B is the number of bits in the transport block (including CRC). Additionally or alternatively, code block segmentation and code block CRC appending are performed. The bits after code block segmentation are represented by c γ0 、c γ1 、c γ2 、c γ3 ,...,c γ (K γ -1) where γ is the code block number and K γ is the number of bits of the code block number γ.

[0144] An example of channel coding for UL-SCH is given below. The code block is delivered to the channel coding block. The bits in the code block are represented by c γ0 、c γ1 、c γ2 、c γ3 ,...,c γ (K γ -1), where γ is the code block number and Kγ is the number of bits in the code block number r. The total number of code blocks is denoted by C, and each code block is encoded separately. After encoding, the bits are represented by Denotes, where i = 0, 1 and 2, and where D γ is the number of bits on the ith coded stream of code block number r, for example, D γ =K γ +4.

[0145] An example of rate matching is given below. The coded blocks are delivered to the rate matching block. They are where i = 0, 1, and 2, and where γ is the code block number, i is the coded stream index, and D γis the number of bits in each coded stream of code block number γ. The total number of code blocks is denoted by C, and each coded block is rate matched individually. After rate matching, the bits are represented by e γ0 、e γ1 、e γ2 、e γ3 、...、e γ (E γ -1) where r is the coding block number, and where E γ is the number of rate matching bits for code block number γ.

[0146] An example of code block concatenation is given below. For γ = 0, ..., Cl, the bits input to the code block concatenation block are given by e γ0 、e γ1 、e γ2 、e γ3 、...、e γ (E γ -1) indicates that, and where E γ is the number of rate matching bits of the rth code block. Additionally or alternatively, code block concatenation is performed. When control information is multiplexed with UL-SCH transmission, the bits after code block concatenation are f0, f1, f2, f3, ..., f G-1 Indicates that G is used in N L The total number of coded bits used to transmit a given transport block over all transport layers, excluding bits used to control the transmission.

[0147] An example of channel coding of control information is given below. For example, UCI (i.e., control data) arrives at the coding unit in the form of CSI (e.g., CSI-1 515 and / or CSI-2 517) and / or HARQ-ACK (e.g., HARQ-ACK-1 519 and / or HARQ-ACK-2 521). Additionally or alternatively, different coding rates for UCI (e.g., CSI-1 515, CSI-2 517, HARQ-ACK-1 519 and / or HARQ-ACK-2 521, respectively) are achieved by allocating different numbers of resources (e.g., different numbers of resources for each of the UCIs multiplexed on the PUSCH). For example, in the case of transmitting UCI on the PUSCH, channel coding of HARQ-ACK1, HARQ-ACK2, CSI-1 515 and / or CSI-2 517 is performed independently.

[0148] For example, in the case where the UE sends HARQ-ACK (e.g., HARQ-ACK-1 519 (e.g., HARQ-ACK-1 bit) and / or HARQ-ACK-2 521 (e.g., HARQ-ACK-2 bit), the number of resources for HARQ-ACK (e.g., HARQ-ACK-1 519 and / or HARQ-ACK-2 521, respectively) can be determined as follows.

[0149]

[0150] In formula (1):

[0151] O is the number of HARQ-ACK bits (e.g., HARQ-ACK-1 bit and / or HARQ-ACK-2 bits, respectively);

[0152] · is the scheduled bandwidth for PUSCH transmission in the current timing of the transport block (e.g., in slots and / or symbols), expressed as the number of subcarriers and / or subcarrier spacing;

[0153] · is the number of SC-FDMA symbols per slot used for initial PUSCH transmission;

[0154] · C and K γ Obtained from the initial PDCCH. For example, May be given by a frequency resource allocation field included in a DCI format for uplink (e.g., DCI);

[0155] For HARQ-ACK transmission, as described in this article, (For example, and the offset value of HARQ-ACK). Here, in order to simplify the description, in some specific implementations, it can be assumed that and Included in the offset value of HARQ-ACK.

[0156] Additionally or alternatively, for CSI (e.g., CSI-1 515 and / or CSI-2 517, respectively), in the case where the UE sends CSI (e.g., CSI-1 515 (e.g., CSI-1 bits) and / or CSI-2 517 (e.g., CSI-2 bits)), respectively, the number of resources for CSI may be determined as follows.

[0157]

[0158] In formula (2):

[0159] O is the number of CQI bits (e.g., CSI-1 bits and / or CSI-2 bits, respectively) and / or PMI bits;

[0160] L is the number of CRC bits, given by given;

[0161] · is the scheduled bandwidth for PUSCH transmission in the current timing of the transport block (e.g., in slots and / or symbols), expressed as the number of subcarriers and / or subcarrier spacing;

[0162] · Q m This may be by using the modulation scheme indicated by the DCI format for uplink;

[0163] Obtained from the initial PDCCH C (x) and

[0164] For example, C (x) and may be given by a frequency resource allocation field included in a DCI format for uplink (e.g., DCI); and

[0165] · is the number of symbols per slot used for initial PUSCH transmission.

[0166] As described in this article, for CSI, (For example, and the offset value of CSI). Here, for example, Can be based on and Here, in order to simplify the description, in some specific implementations, it can be assumed that and Included in the offset value of CSI.

[0167] For example, the number of resources for HARQ-ACK-1 519 and the number of resources for HARQ-ACK-2 521 may be determined based on the above formula (1), respectively. Additionally or alternatively, the number of resources for CSI-1 515 and the number of resources for CSI-2 517 may be determined based on the above formula (2), respectively. For example, HARQ-ACK-1 519 and HARQ-ACK-2 521 may be sent with different reliabilities on the PUSCH (e.g., PUSCH resources). Additionally or alternatively, CQI-1 and CQI-2 may be sent with different reliabilities on the PUSCH (e.g., PUSCH resources).

[0168] That is, an offset value for HARQ-ACK may be defined (e.g., configured and / or indicated) to determine the number of resources for HARQ-ACK to be sent on the PUSCH (e.g., sent together with the UL-SCH). Additionally, an offset value for CSI may be defined (e.g., configured and / or indicated) to determine the number of resources for CSI to be sent on the PUSCH (e.g., sent together with the UL-SCH).

[0169] Additionally or alternatively, the gNB 160 may transmit third information for configuring an offset value (e.g., an offset value for HARQ-ACK and / or an offset value for CSI) using an RRC message. Additionally or alternatively, the gNB 160 may transmit a DCI format (e.g., a DCI format for uplink) including DCI (i.e., a β offset indicator) indicating an offset value (e.g., an offset value for HARQ-ACK and / or an offset value for CSI). Additionally or alternatively, the gNB 160 may transmit fourth information (e.g., the fourth information may be the third information) for configuring more than one offset value (e.g., four offset values for HARQ-ACK and / or four offset values for CSI) using an RRC message. Additionally or alternatively, the gNB 160 may transmit a DCI format (e.g., a DCI format for uplink) including DCI (i.e., a β offset indicator) indicating an offset value (e.g., an offset value of HARQ-ACK and / or an offset value of CSI) from among more than one value (four offset values of HARQ-ACK and / or four offset values of CSI). That is, the β offset indicator included in the DCI format (e.g., a DCI format for uplink) may be used to indicate an offset value (e.g., an offset value of HARQ-ACK and / or an offset value of CSI) to determine the amount of resources (e.g., HARQ-ACK and / or CSI).

[0170] Figure 6An example of an indication for UL transmission is shown. As described herein, an offset value (e.g., an offset value for HARQ-ACK and / or an offset value for CSI) may be defined (e.g., configured and / or indicated) to determine the amount of resources (e.g., the amount of resources of the PUSCH for HARQ-ACK and / or CSI). That is, the UE 102 may determine the amount of resources for the HARQ-ACK to be sent on the PUSCH (e.g., sent together with the UL-SCH) based on the offset value for the HARQ-ACK. Additionally or alternatively, the UE 102 may determine the amount of resources for the CSI to be sent on the PUSCH (e.g., sent together with the UL-SCH) based on the offset value for the CSI. Here, one or more offset values for one or more HARQ-ACKs may be defined to respectively determine the amount of resources for one or more HARQ-ACKs. Additionally or alternatively, one or more offset values for one or more CSIs may be defined to respectively determine the amount of resources for one or more CSIs.

[0171] Here, the second DCI format 603 may be DCI format 1_X and / or DCI format 0_Y. Furthermore, the second DCI format 603 may be a DCI format having a CRC scrambled by the first RNTI (e.g., DCI format 1_1, DCI format 1_X, DCI format 0_1, and / or DCI format 0_Y). Furthermore, the second DCI format 603 may be a DCI format detected in a CORESET configured by the gNB 160 (e.g., DCI format 1_1, DCI format 1_X, DCI format 0_0, and / or DCI format 0_Y). That is, the gNB 160 may transmit the fifth information for configuring the CORESET corresponding to the second DCI format 603 by using an RRC message. That is, when the UE 102 detects a DCI format in the CORESET configured using the fifth information, the UE 102 may recognize the detected DCI format as the second DCI format 603. Here, gNB 160 may configure fifth information for a CORESET other than CORESET #0. Additionally or alternatively, second DCI format 603 may be a DCI format detected in a search space set configured by gNB 160 (e.g., DCI format 1_0, DCI format 1_1, DCI format 1_X, DCI format 0_0, DCI format 0_1, and / or DCI format 0_Y). That is, gNB 160 may transmit sixth information for configuring a search space set corresponding to second DCI format 603 by using an RRC message. That is, when UE 102 detects a DCI format in the search space set configured using the sixth information, UE 102 may recognize the detected DCI format as first DCI format 601. Here, gNB 160 may configure sixth information for a search space set other than search space set #0.

[0172] Here, as described above, DCI format 0_1 (i.e., first DCI format 601) may include at least a beta offset indicator. Furthermore, DCI format 0_1 (i.e., first DCI format 601) may include at least a UL-SCH indicator. Here, for first DCI format 601, a field for the beta offset indicator and a field for the UL-SCH indicator may be defined separately. For example, the number of bits of the beta offset indicator included in first DCI format 601 may be 0 or 2 bits. For example, gNB 160 may transmit seventh information for determining (e.g., configuring) the number of bits of the beta offset indicator (e.g., 0 or 2 bits) using an RRC message. Furthermore, for example, the UL-SCH indicator included in first DCI format 601 may always be 1 bit.

[0173] For example, as described above, the values "01," "10," and / or "11" (e.g., the value of the 2-bit field of the beta offset indicator included in the first DCI format 601) may be used to indicate an offset value from among more than one value configured by the gNB 160 using an RRC message. UE 102 may use the indicated offset value to determine the number of resources for UCI (e.g., HARQ-ACK and / or CSI). Here, if the beta offset indicator is not configured for the first DCI format 601 (e.g., if the number of bits of the beta offset indicator is configured as "0 bits," or if the beta offset indicator is not present in the first DCI format 601), the offset value configured by the gNB 160 using the RRC message (e.g., the offset value configured using the third information described above) may be used. That is, if the beta offset indicator is not configured for the first DCI format 601, UE 102 may use the configured offset value (e.g., the offset value configured using the third information) to determine the number of resources for UCI (e.g., HARQ-ACK and / or CSI).

[0174] Additionally or alternatively, a value of "0" (e.g., the value of a 1-bit field of the UL-SCH indicator included in the first DCI format 601) may be used to indicate that the UL-SCH is not transmitted on the PUSCH (e.g., the UL-SCH should not be transmitted on the PUSCH). Furthermore, a value of "1" (e.g., the value of a 1-bit field of the UL-SCH indicator included in the first DCI format 601) may be used to indicate that the UL-SCH is transmitted on the PUSCH (e.g., the UL-SCH should be transmitted on the PUSCH).

[0175] That is, the UL-SCH indicator included in the first DCI format 601 may be used to indicate whether the UL-SCH is transmitted on the PUSCH. For example, upon receiving the first DCI format 601 including the UL-SCH indicator set to "1" (i.e., the value of the 1-bit field of the UL-SCH indicator is set to "1"), the UE 102 may transmit the UL-SCH along with UCI (e.g., HARQ-ACK and / or CSI) on the PUSCH. Alternatively, upon receiving the first DCI format 601 including the UL-SCH indicator set to "0" (i.e., the value of the 1-bit field of the UL-SCH indicator is set to "0"), the UE 102 may transmit UCI (e.g., HARQ-ACK and / or CSI) on the PUSCH. That is, when the UL-SCH indicator is set to "0," only UCI is transmitted on the PUSCH (e.g., UCI is transmitted without the UL-SCH).

[0176] Additionally or alternatively, the second DCI format 603 may not include a beta offset indicator. That is, the beta offset indicator may not always be present in the second DCI format 603. Here, the second DCI format 603 may include at least a UL-SCH indicator. For example, the number of bits of the UL-SCH indicator included in the second DCI format 603 may be 0, 1, or 2 bits. For example, the gNB 160 may transmit eighth information for determining (e.g., configuring) the number of bits of the UL-SCH indicator (e.g., 0, 1, or 2 bits) by using an RRC message.

[0177] Here, for the second DCI format 603, the value of the field used for the UL-SCH indicator (e.g., the value of the 2-bit field used for the UL-SCH indicator) may be used to indicate that UCI (e.g., HARQ-ACK and / or CSI) is not to be transmitted on the PUSCH (e.g., UCI (e.g., HARQ-ACK and / or CSI) should not be transmitted on the PUSCH). Additionally or alternatively, for the second DCI format 603, the value of the field used for the UL-SCH indicator (e.g., the value of the 2-bit field used for the UL-SCH indicator) may be used to indicate that UCI (e.g., HARQ-ACK and / or CSI) is to be transmitted on the PUSCH (e.g., UCI (e.g., HARQ-ACK and / or CSI) should be transmitted on the PUSCH). That is, the UL-SCH indicator included in the second DCI format 603 may be used to indicate whether UCI is to be transmitted on the PUSCH. For example, in the case where the number of bits of the UL-SCH indicator is configured as "2 bits" (ie, more than one bit), the UL-SCH indicator (eg, a field of the UL-SCH indicator) may be used to indicate whether UCI is transmitted on the PUSCH.

[0178] Additionally or alternatively, for the second DCI format 603, the value of the UL-SCH indicator field (e.g., the value of the 2-bit field of the UL-SCH indicator) may be used to indicate a value (e.g., an offset value) for determining the number of resources for UCI (e.g., HARQ-ACK and / or CSI). That is, for the second DCI format 603, the value of the UL-SCH indicator field (e.g., the value of the 2-bit field of the UL-SCH indicator) may be used to indicate an offset value (e.g., one offset value) from among the multiple offset values configured by the gNB 160 using an RRC message. That is, the gNB 160 may transmit ninth information (e.g., the ninth information may be the third information) for configuring the multiple offset values using an RRC message. Furthermore, the gNB 160 may indicate an offset value (e.g., one offset value) from among the multiple offset values configured using the ninth information by using the value of the UL-SCH indicator field included in the second DCI format 603.

[0179] For example, a value of "00" (e.g., a value for the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that UCI (e.g., HARQ-ACK and / or CSI) is not to be transmitted on the PUSCH (e.g., UCI (e.g., HARQ-ACK and / or CSI) should not be transmitted on the PUSCH). That is, upon receiving the second DCI format 603 including the UL-SCH indicator set to "00" (i.e., the value of the 2-bit field of the UL-SCH indicator is set to "00"), the UE 102 may not transmit UCI (e.g., HARQ-ACK and / or CSI) on the PUSCH. For example, even if the UE 102 performs (e.g., will perform) a PUSCH transmission with a UL-SCH that overlaps with a PUCCH transmission including UCI, upon receiving the second DCI format 603 including the UL-SCH indicator set to "00", the UE 102 may not multiplex the UCI on the PUSCH. That is, upon receiving the second DCI format 603 including the UL-SCH indicator set to "00", the UE 102 may not multiplex the UL-SCH and UCI on the PUSCH. That is, upon receiving the second DCI format 603 including the UL-SCH indicator set to "00", the UE 102 may discard (e.g., omit) the UCI (e.g., UCI transmission). For example, upon receiving the second DCI format 603 including the UL-SCH indicator set to "00", the UE 102 may transmit only the UL-SCH on the PUSCH with the same timing (e.g., in the same time slot and / or the same symbol).

[0180] That is, the value "00" (e.g., the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that the UL-SCH is transmitted on the PUSCH (e.g., the UL-SCH should be transmitted on the PUSCH). Additionally or alternatively, the value "00" (e.g., the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that the UL-SCH is transmitted only on the PUSCH (e.g., the UL-SCH should be transmitted only on the PUSCH). Additionally or alternatively, the value "00" (e.g., the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that the UL-SCH without UCI is transmitted only on the PUSCH (e.g., the UL-SCH without UCI should be transmitted only on the PUSCH).

[0181] Additionally or alternatively, a value of "00" (e.g., the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that the offset value of UCI (e.g., HARQ-ACK and / or CSI) is "0.0" (i.e., zero). That is, a value of "00" (e.g., the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that the number of resources of UCI (e.g., HARQ-ACK and / or CSI) is "0.0" (i.e., zero).

[0182] Additionally or alternatively, a value of "01" (e.g., the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that UCI (e.g., HARQ-ACK and / or CSI) is to be transmitted on the PUSCH (e.g., UCI (e.g., HARQ-ACK and / or CSI) should be transmitted on the PUSCH). That is, upon receiving the second DCI format 603 including the UL-SCH indicator set to "01" (i.e., the value of the 2-bit field of the UL-SCH indicator is set to "01"), the UE 102 may transmit UCI (e.g., HARQ-ACK and / or CSI) on the PUSCH. For example, even if the UE 102 performs (e.g., will perform) a PUSCH transmission with a UL-SCH that overlaps with a PUCCH transmission including UCI, upon receiving the second DCI format 603 including the UL-SCH indicator set to "01", the UE 102 may not multiplex the UL-SCH on the PUSCH. That is, upon receiving the second DCI format 603 including the UL-SCH indicator set to "01", the UE 102 may not multiplex the UL-SCH and UCI on the PUSCH. That is, upon receiving the second DCI format 603 including the UL-SCH indicator set to "01", the UE 102 may drop (e.g., omit) the UL-SCH (e.g., UL-SCH transmission). For example, upon receiving the second DCI format 603 including the UL-SCH indicator set to "01", the UE 102 may transmit only the UCI on the PUSCH with the same timing (e.g., in the same time slot and / or the same symbol).

[0183] That is, a value of "01" (e.g., the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that UCI is transmitted on the PUSCH (e.g., UCI should be transmitted on the PUSCH). Additionally or alternatively, a value of "01" (e.g., the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that UCI is transmitted only on the PUSCH (e.g., UCI should be transmitted only on the PUSCH). Additionally or alternatively, a value of "01" (e.g., the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that UCI without UL-SCH is transmitted only on the PUSCH (e.g., UCI without UL-SCH should be transmitted only on the PUSCH). That is, the value '01' (eg, the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that UL-SCH is not transmitted on PUSCH (eg, UL-SCH should be transmitted on PUSCH).

[0184] Additionally or alternatively, the values '10' and / or '11' (e.g., the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that UCI (e.g., HARQ-ACK and / or CSI) is multiplexed with the UL-SCH on the PUSCH (e.g., UCI (e.g., HARQ-ACK and / or CSI) should be multiplexed on the PUSCH). That is, upon receiving the second DCI format 603 including the UL-SCH indicator set to '10' and / or '11' (i.e., the value of the 2-bit field of the UL-SCH indicator is set to '10' and / or '11'), the UE 102 may transmit the UCI (e.g., HARQ-ACK and / or CSI) multiplexed with the UL-SCH on the PUSCH. For example, if the UE 102 performs (e.g., will perform) a PUSCH transmission with a UL-SCH that overlaps with a PUCCH transmission including UCI, upon receiving the second DCI format 603 including the UL-SCH indicator set to "10" and / or "11," the UE 102 may multiplex the UL-SCH and the UCI on the PUSCH. For example, upon receiving the second DCI format 603 including the UL-SCH indicator set to "10" and / or "11," the UE 102 may transmit the UL-SCH and the UCI on the PUSCH with the same timing (e.g., in the same time slot and / or the same symbol). That is, upon receiving the second DCI format 603 including the UL-SCH indicator set to "10" and / or "11," the UE 102 may transmit the UCI together with the UL-SCH on the PUSCH.

[0185] Additionally or alternatively, the values "10 and / or 11" (e.g., the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate a value (e.g., an offset value) for determining the number of resources for UCI (e.g., HARQ-ACK and / or CSI). That is, as described above, the values "10 and / or 11" (e.g., the value of the 2-bit field of the UL-SCH indicator included in the second DCI format 603) may be used for an offset value (e.g., one offset value) from among more than one offset values configured using the ninth information. For example, the gNB 160 may transmit more than one offset value (e.g., two offset values) using an RRC message. Furthermore, the gNB 160 may transmit the second DCI format 603 including the values "10 and / or 11" for the UL-SCH indicator indicating an offset value (e.g., one offset value) from among two offset values. Furthermore, the UE 102 may determine the amount of resources for UCI (eg, HARQ-ACK and / or CSI) based on an offset value.

[0186] Additionally or alternatively, in a case where the number of bits of the UL-SCH indicator included in the second DCI format 603 is configured as “1 bit”, a value of “0” (e.g., the value of the 1-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that the UL-SCH is not transmitted on the PUSCH (e.g., the UL-SCH should not be transmitted on the PUSCH). In addition, in a case where the number of bits of the UL-SCH indicator included in the second DCI format 603 is configured as “1 bit”, a value of “1” (e.g., the value of the 1-bit field of the UL-SCH indicator included in the second DCI format 603) may be used to indicate that the UL-SCH is transmitted on the PUSCH (e.g., the UL-SCH should be transmitted on the PUSCH).

[0187] That is, when the number of bits of the UL-SCH indicator included in the second DCI format 603 is configured as "1 bit", the value of the field of the UL-SCH indicator included in the second DCI format 603 may be used to indicate whether the UL-SCH is transmitted on the PUSCH. For example, when receiving the second DCI format 603 including the UL-SCH indicator set to "1" (i.e., the value of the 1-bit field of the UL-SCH indicator is set to "1"), the UE 102 may transmit the UL-SCH together with UCI (e.g., HARQ-ACK and / or CSI) on the PUSCH. In addition, when receiving the second DCI format 603 including the UL-SCH indicator set to "0" (i.e., the value of the 1-bit field of the UL-SCH indicator is set to "0"), the UE 102 may transmit UCI (e.g., HARQ-ACK and / or CSI) on the PUSCH. That is, in a case where the UL-SCH indicator is set to '0', UCI is transmitted only on the PUSCH (eg, UCI is transmitted without UL-SCH).

[0188] Here, when the number of bits of the UL-SCH indicator included in the second DCI format 603 is configured as "1 bit", the offset value configured by the gNB 160 using the RRC message (for example, the offset value configured by the ninth information as described above) may be used. That is, when the number of bits of the UL-SCH indicator included in the second DCI format 603 is configured as "1 bit", the UE 102 may use the configured offset value (for example, the offset value configured by the ninth information) to determine the number of resources of UCI (for example, HARQ-ACK and / or CSI).

[0189] Additionally or alternatively, in a case where the number of bits of the UL-SCH indicator included in the second DCI format 603 is configured as “0 bit” (e.g., the UL-SCH indicator is not configured for the second DCI format 603, and the UL-SCH indicator does not exist in the second DCI format 603), the UE 102 may always multiplex the UL-SCH and the UCI on the PUSCH. For example, in a case where the number of bits of the UL-SCH indicator included in the second DCI format 603 is configured as “0 bit”, if the UE 102 performs (e.g., will perform) PUSCH transmission with UL-SCH, which PUSCH transmission overlaps with PUCCH transmission including UCI, the UE 102 may multiplex the UL-SCH and the UCI on the PUSCH.

[0190] Here, when the number of bits of the UL-SCH indicator included in the second DCI format 603 is configured as "0 bit", the offset value configured by the gNB 160 using the RRC message (for example, the offset value configured by the ninth information as described above) may be used. That is, when the number of bits of the UL-SCH indicator included in the second DCI format 603 is configured as "0 bit", the UE 102 may use the configured offset value (for example, the offset value configured by the ninth information) to determine the number of resources of UCI (for example, HARQ-ACK and / or CSI).

[0191] In the specification, the transmission method for HARQ-ACK is mainly explained. However, it should be noted that the above method (and / or a method similar to the above method) can be applied to the transmission method for CSI.

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

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

[0194] The various components of the UE 702 are coupled together via a bus system 711 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are not shown in FIG. Figure 7 7. The UE 702 is shown as a bus system 711. The UE 702 may also include a digital signal processor (DSP) 713 for processing signals. The UE 702 may also include a communication interface 715 that provides user access to the functions of the UE 702. Figure 7 The UE 702 is shown as a functional block diagram rather than a listing of specific components.

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

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

[0197] The various components of the gNB 860 are coupled together via a bus system 811 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are not referred to in the following sections. Figure 8 860 is shown as bus system 811. gNB 860 may also include a digital signal processor (DSP) 813 for processing signals. gNB 860 may also include a communication interface 815 that provides user access to the functions of gNB 860. Figure 8 The gNB 860 shown is a functional block diagram rather than a listing of specific components.

[0198] Figure 9 9 is a block diagram illustrating one embodiment of a UE 902 in which one or more of the systems and / or methods described herein may be implemented. The UE 902 includes a transmitting device 958, a receiving device 920, and a control device 924. The transmitting device 958, the receiving device 920, and the control device 924 may be configured to perform a combination of the above Figure 1 One or more of the functions described above. Figure 7 Shown Figure 9 Various other structures can be implemented to implement Figure 1 For example, the DSP may be implemented by software.

[0199] Figure 10 is a block diagram illustrating one embodiment of a gNB 1060 in which one or more of the systems and / or methods described herein may be implemented. The gNB 1060 includes a transmitting device 1017, a receiving device 1078, and a control device 1082. The transmitting device 1017, the receiving device 1078, and the control device 1082 may be configured to perform a combination of the above. Figure 1 One or more of the functions described above. Figure 8 Shown Figure 10 Various other structures can be implemented to implement Figure 1 For example, the DSP may be implemented by software.

[0200] Figure 11 is a block diagram illustrating a specific implementation of gNB 1160. gNB 1160 may be combined with Figure 1 1. An example of a gNB 160 is depicted. The gNB 1160 may include a higher layer processor 1123, a DL transmitter 1125, a UL receiver 1133, and one or more antennas 1131. The DL transmitter 1125 may include a PDCCH transmitter 1127 and a PDSCH transmitter 1129. The UL receiver 1133 may include a PUCCH receiver 1135 and a PUSCH receiver 1137.

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

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

[0203] Figure 12 1 is a block diagram illustrating a specific implementation of UE 1202. UE 1202 may be a combination of Figure 1 UE 1202 may include a higher layer processor 1223, a UL transmitter 1251, a DL receiver 1243, and one or more antennas 1231. The UL transmitter 1251 may include a PUCCH transmitter 1253 and a PUSCH transmitter 1255. The DL receiver 1243 may include a PDCCH receiver 1245 and a PDSCH receiver 1247.

[0204] The higher-layer processor 1223 manages the behavior of the physical layer (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 and receive higher-layer messages, such as RRC messages and MAC messages, to and from the higher layers of the UE. The higher-layer processor 1223 can provide transport blocks to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1253.

[0205] The DL receiver 1243 may receive and demultiplex the multiplexed downlink physical channel and the downlink physical signal via the reception antenna 1231. The PDCCH receiver 1245 may provide DCI to the higher layer processor 1223. The PDSCH receiver 1247 may provide the higher layer processor 1223 with the received transport block.

[0206] As described above, some methods for DL and / or UL transmission may be applied (e.g., specified). Here, a combination of one or more of the methods described herein may be applied to DL and / or UL transmission. The systems and methods may not exclude a combination of one or more of the methods described herein.

[0207] It should be noted that the names of the physical channels described herein are examples, and other names may be used, such as "NRPDCCH, NRPDSCH, NRPUCCH, and NRPUSCH," "new generation (G)PDCCH, GPDSCH, GPUCCH, and GPUSCH," and the like.

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

[0209] It should be noted that one or more of the 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 in and / or performed using a chipset, an application specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc.

[0210] 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 interchangeable with one another and / or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for the correct operation of the method, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

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

[0212] The program running on the gNB 160 or UE 102 according to the systems and methods described herein controls the CPU, etc., to implement the functions according to the systems and methods (a program that causes the computer to operate). Information processed by these devices is then temporarily stored in RAM while being processed. This information is then stored in various ROMs or HDDs and read by the CPU for modification or writing whenever necessary. Possible recording media on which the program is stored include semiconductors (e.g., ROMs, nonvolatile memory cards, etc.), optical storage media (e.g., DVDs, MOs, MDs, CDs, BDs, etc.), and magnetic storage media (e.g., magnetic tapes, floppy disks, etc.). In some cases, the functions according to the systems and methods described herein are implemented by executing the loaded program. Alternatively, the functions according to the systems and methods are implemented based on instructions from the program in conjunction with an operating system or other application programs.

[0213] Furthermore, if the program is commercially available, it can be distributed on a portable recording medium, or it can be sent to a server computer connected via a network such as the Internet. In this case, the storage device in the server computer is also included. Furthermore, some or all of the gNB 160 and UE 102 according to the systems and methods described herein can be implemented as LSIs, which are typical integrated circuits. Each functional block of the gNB 160 and UE 102 can be individually built into a chip, and some or all functional blocks can be integrated into a chip. Furthermore, integrated circuit technology is not limited to LSIs, and integrated circuits for functional blocks can be implemented using dedicated circuits or general-purpose processors. Furthermore, if integrated circuit technology that replaces LSIs emerges as semiconductor technology continues to advance, integrated circuits using this technology can also be used.

[0214] In addition, each functional block or various features of the base station equipment and terminal equipment used in each of the above-mentioned embodiments can be implemented or executed by a circuit (typically an integrated circuit or multiple integrated circuits). The circuit designed to perform the function described in this specification may include a general-purpose processor, a digital signal processor (DSP), a dedicated or general-purpose integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device or a discrete hardware component or a combination thereof. The general-purpose processor can be a microprocessor, or alternatively, the processor can be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or every kind of circuit described herein can be configured by a digital circuit, or can be configured by an analog circuit. In addition, when the technology of the integrated circuit replacing current integrated circuit occurs due to the progress of semiconductor technology, the integrated circuit produced by the technology can also be used.

[0215] <Cross Reference>

[0216] This nonprovisional patent application claims priority under 35 U.S.C. §119 to provisional patent application No. 62,837,325, filed on April 23, 2019, the entire contents of which are hereby incorporated by reference.

Claims

1. A user equipment (UE), comprising: a receiver, the receiver being configured to receive a first downlink control information DCI format in which the number of bits of a first uplink shared channel UL-SCH indicator is 1, the first DCI format being used for scheduling a first physical uplink shared channel PUSCH; as well as a transmitter configured to perform transmission on the first PUSCH based on detection of the first DCI format, wherein The receiver is further configured to receive a second DCI format in which the number of bits of the second UL-SCH indicator is 0 or 1, and the second DCI format is used for scheduling a second PUSCH. The transmitter is further configured to perform transmission on the second PUSCH based on detection of the second DCI format, In a case where the number of bits of the second UL-SCH indicator is 0, the transmitter is further configured to determine that the number of bits of the second UL-SCH indicator is 0, In a case where the number of bits of the second UL-SCH indicator is 1, the transmitter is further configured to determine that the number of bits of the second UL-SCH indicator is 1, The first UL-SCH indicator indicates whether a UL-SCH is transmitted on the first PUSCH, and When the number of bits of the second UL-SCH indicator is 1, the second UL-SCH indicator indicates whether a UL-SCH is transmitted on the second PUSCH.

2. A method performed by a user equipment (UE), the method comprising: receiving a first downlink control information DCI format in which the number of bits of a first uplink shared channel UL-SCH indicator is 1, where the first DCI format is used for scheduling a first physical uplink shared channel PUSCH; performing transmission on the first PUSCH based on detection of the first DCI format; receiving a second DCI format in which the number of bits of the second UL-SCH indicator is 0 or 1, where the second DCI format is used for scheduling a second PUSCH; performing transmission on the second PUSCH based on detection of the second DCI format; When the number of bits of the second UL-SCH indicator is 0, determining that the number of bits of the second UL-SCH indicator is 0, In a case where the number of bits of the second UL-SCH indicator is 1, determining the number of bits of the second UL-SCH indicator is 1, wherein The first UL-SCH indicator indicates whether a UL-SCH is transmitted on the first PUSCH, and When the number of bits of the second UL-SCH indicator is 1, the second UL-SCH indicator indicates whether a UL-SCH is transmitted on the second PUSCH.

Images