User Equipment, Base Station, and Signaling for Resource Allocation for Enhanced Uplink Transmission

Abstract

The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive downlink control information (DCI). The DCI includes a time domain resource allocation field, and the UE further includes a processor. The processor is configured to determine a resource allocation based on the DCI having the time domain resource allocation field.

Description

Technical Field

[0001] The present disclosure generally relates to communication systems. More specifically, the present disclosure relates to user equipment, base stations, and signaling for resource allocation for enhanced 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 reliant on wireless communication devices and expect reliable services, expanded coverage areas, 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 can be a device that communicates with wireless communication devices.

[0003] With the development of wireless communication devices, there has been a continuous search for ways to improve communication capacity, speed, flexibility, and / or efficiency. However, improving communication capacity, speed, flexibility, and / or efficiency can pose certain problems.

[0004] For example, a wireless communication device can communicate with one or more devices using a communication structure. However, the communication structure used may only provide limited flexibility and / or efficiency. As shown in this discussion, systems and methods for improving communication flexibility and / or efficiency may be advantageous. Summary of the Invention

[0005] In one example, a user equipment (UE) includes: a receiving circuit configured to receive a radio resource control (RRC) message including first parameters for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being for defining a time domain allocation for physical uplink shared channel (PUSCH) transmission, wherein a starting symbol and a length are jointly presented in the first allocation table, and the starting symbol and the length are separately presented in the second allocation table, the receiving circuit being configured to detect, in a UE-specific search space, a first downlink control information (DCI) format or a second DCI format including first information for indicating a row index of the first allocation table or the second allocation table, the DCI format being for scheduling the PUSCH; a transmitting circuit configured to perform PUSCH transmission based on either the first allocation table or the second allocation table based on detecting the first DCI format or the second DCI format, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on the DCI format.

[0006] In one example, a base station device includes: a transmission circuit configured to transmit a Radio Resource Control (RRC) message including first parameters for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used to define a time-domain allocation for Physical Uplink Shared Channel (PUSCH) transmission, wherein a starting symbol and a length are jointly presented in the first allocation table, and the starting symbol and the length are respectively presented in the second allocation table, the transmission circuit being configured to transmit a first Downlink Control Information (DCI) format or a second DCI format including first information for indicating a row index of the first allocation table or the second allocation table in a UE-specific search space, the DCI format being used to schedule PUSCH; a receiving circuit that receives a PUSCH transmission based on either the first allocation table or the second allocation table, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on the DCI format.

[0007] In one example, a communication method of a User Equipment (UE) includes: receiving a Radio Resource Control (RRC) message including first parameters for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used to define a time-domain allocation for Physical Uplink Shared Channel (PUSCH) transmission, wherein a starting symbol and a length are jointly presented in the first allocation table, and the starting symbol and the length are respectively presented in the second allocation table; detecting a first Downlink Control Information (DCI) format or a second DCI format including first information for indicating a row index of the first allocation table or the second allocation table in a UE-specific search space, the DCI format being used to schedule PUSCH; performing a PUSCH transmission based on either the first allocation table or the second allocation table based on the detected DCI format, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on the DCI format.

[0008] In one example, a communication method for a base station device, the communication method comprising: transmitting a Radio Resource Control (RRC) message including first parameters for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used to define a time domain allocation for Physical Uplink Shared Channel (PUSCH) transmission, wherein a starting symbol and a length are jointly presented in the first allocation table, and the starting symbol and the length are respectively presented in the second allocation table; transmitting a first Downlink Control Information (DCI) format or a second DCI format including first information for indicating a row index of the first allocation table or the second allocation table in a UE-specific search space, the DCI format being used to schedule PUSCH; receiving a PUSCH transmission based on either the first allocation table or the second allocation table, wherein it is determined based on the DCI format whether the first allocation table or the second allocation table is used for PUSCH transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 Figure 1 is a block diagram showing one implementation of one or more gNode Bs (gNBs) and one or more User Equipments (UEs) for enhanced uplink transmission.

[0010] Figure 2 Figure 2 is a diagram showing an example of a resource grid for the downlink.

[0011] Figure 3 Figure 3 is a diagram showing an example of a resource grid for the uplink.

[0012] Figure 4 Figure 4 shows examples of several parameters.

[0013] Figure 5 Figure 5 shows for Figure 4 an example of a subframe structure of the parameters shown in.

[0014] Figure 6 Figure 6 shows examples of time slots and sub - time slots.

[0015] Figure 7 Figure 7 shows an example of a scheduling timeline.

[0016] Figure 8 Figure 8 shows an example of a DL control channel monitoring area.

[0017] Figure 9 Figure 9 ​​​​​​​​​​​​​​​​​​Shows an example of a DL control channel including more than one control channel element.

[0018] Figure 10 Figure 10 Shows an example of a UL control channel structure.

[0019] Figure 11 Figure 11 Is a block diagram showing a specific implementation of a gNB.

[0020] Figure 12 Figure 12 Is a block diagram showing a specific implementation of a UE.

[0021] Figure 13 Figure 13 Shows various components that can be utilized in a UE.

[0022] Figure 14 Figure 14 Shows various components that can be utilized in a gNB.

[0023] Figure 15 Figure 15 Is a block diagram showing a specific implementation of a UE in which a system and method for resource allocation for enhanced uplink transmission can be implemented.

[0024] Figure 16 Figure 16 Is a block diagram showing a specific implementation of a gNB in which a system and method for resource allocation for enhanced uplink transmission can be implemented.

[0025] Figure 17 Figure 17 Is a flowchart showing a method performed by a UE.

[0026] Figure 18 Figure 18 Is a flowchart showing a method performed by a gNB. Detailed Description

[0027] The present invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive downlink control information (DCI). The DCI is a time domain resource allocation field. The UE further includes a processor configured to determine resource allocation based on the DCI having a time domain resource allocation field.

[0028] ​​​​​​​​​​​​​​​​​​The present invention also describes a base station (gNB). The gNB includes a processor configured to determine resource allocation for a user equipment (UE). The gNB also includes a transmission circuit configured to transmit downlink control information (DCI) to the UE. The DCI includes a time domain resource allocation field indicating the resource allocation.

[0029] The present invention also describes a method performed by a user equipment (UE). The method includes receiving signaling including downlink control information (DCI). The DCI is a time domain resource allocation field. The method also includes determining resource allocation based on the DCI having the time domain resource allocation field.

[0030] The present invention also describes a method performed by a base station (gNB). The method includes determining resource allocation for a user equipment (UE). The method also includes transmitting downlink control information (DCI) to the UE. The DCI includes a time domain resource allocation field indicating the resource allocation.

[0031] The 3rd Generation Partnership Project (also known as "3GPP") is a cooperation agreement aimed at formulating globally applicable technical specifications and technical reports for third-generation and fourth-generation wireless communication systems. 3GPP can formulate specifications for next-generation mobile networks, systems, and devices.

[0032] 3GPP Long-Term Evolution (LTE) is the name given to a project awarded to improve the standards of Universal Mobile Telecommunications System (UMTS) mobile phones or devices to meet future requirements. 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).

[0033] 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, and / or 12). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.

[0034] A wireless communication device can be an electronic device that is used to transmit voice and / or data to a base station, which in turn can communicate with the device's network (e.g., the Public Switched Telephone Network (PSTN), the Internet, etc.). When describing the systems and methods herein, the 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, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, the wireless communication device is typically referred to as a UE. However, since the scope of the present disclosure should not be limited to 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 more generally be referred to as a terminal device.

[0035] In 3GPP specifications, the base station is typically referred to as Node B, evolved Node B (eNB), Home Enhanced or evolved Node B (HeNB), or some other similar term. Since the scope of the present disclosure should not be limited to 3GPP standards, the terms "base station", "Node B", "eNB", "gNB", and / or "HeNB" may be used interchangeably herein to represent the more general term "base station". Additionally, the term "base station" may be used to represent an access point. An access point can be an electronic device that provides access to a network (e.g., a local area network (LAN), the Internet, etc.) for wireless communication devices. The term "communication device" may be used to represent a wireless communication device and / or a base station. An eNB may also more generally be referred to as a base station device.

[0036] It should be noted that, as used herein, a "cell" can be any such communication channel that is designated by a standardization or regulatory body for use in International Mobile Telecommunications - Advanced (IMT - Advanced) and all or a subset thereof, such that it is 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 overall 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 the system information that can be transmitted on the downlink resources.

[0037] "Configured cells" are those cells that the UE is aware of and has been granted permission by the eNB to transmit or receive information from. A "configured cell" can be a serving cell. The UE can receive system information and perform required measurements on all configured cells. The "configured cells" for a radio connection can include the primary cell and / or zero, one, or more secondary cells. An "active cell" is one of those configured cells on which the UE is transmitting and receiving. That is, an active cell is a cell on which the UE monitors its Physical Downlink Control Channel (PDCCH), and in the case of downlink transmission, a cell on which the UE decodes its Physical Downlink Shared Channel (PDSCH). A "deactivated cell" is one of those configured cells on which the UE does not monitor the transmitted PDCCH. It should be noted that "cells" can be described in different dimensions. For example, a "cell" can have time, space (e.g., geographical), and frequency characteristics.

[0038] Fifth-generation (5G) cellular communications (also referred to by 3GPP as "New Radio", "New Radio Access Technology", or "NR") envisions using time, frequency, and / or space resources to enable services such as enhanced mobile broadband (eMBB) communications and ultra-reliable low-latency communications (URLLC), as well as massive machine-type communications (MMTC). To meet latency targets and high reliability, micro-slot-based repetition with flexible transmission opportunities can be supported. Methods for applying micro-slot-based repetition are described herein. A New Radio (NR) base station can be referred to as a gNB. A gNB can also more generally be referred to as base station equipment.

[0039] Some configurations of the systems and methods described herein teach methods for URLLC transmission and / or retransmission management to meet latency and / or reliability requirements. Some requirements for URLLC relate to user (U)-plane latency and reliability. For URLLC, the target user plane latency is 0.5 milliseconds (ms) for both UL and DL. For X bytes within 1 millisecond (ms), the target reliability is 1 - 10 -5 .

[0040] These URLLC-specific constraints make the design of hybrid automatic repeat request (HARQ) and retransmission mechanisms difficult. For example, the receiver must respond with a fast acknowledgment (ACK) or negative acknowledgment (NACK) or uplink grant to meet latency requirements, or the transmitter can retransmit immediately without waiting for an ACK / NACK to improve reliability. On the other hand, support for grant-based or grant-free repetition is provided to further improve reliability. How to terminate the repetition is also an important issue. The systems and methods teach URLLC HARQ and / or retransmission design in different scenarios.

[0041] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, where like reference numerals may indicate functionally similar elements. The systems and methods generally described and illustrated in the accompanying drawings herein can be arranged and designed in a variety of different specific embodiments. Accordingly, the more detailed description of several specific embodiments presented below in the drawings is not intended to limit the scope of the claimed subject matter, but is merely representative of the systems and methods.

[0042] Figure 1 FIG. 4 is a block diagram illustrating one embodiment of one or more gNode Bs (gNBs) 160 and one or more user equipments (UEs) 102 for enhanced uplink transmission. One or more UEs 102 communicate with one or more gNBs 160 using one or more antennas 122a-n. For example, UE 102 transmits electromagnetic signals to gNB 160 and receives electromagnetic signals from gNB 160 using one or more antennas 122a-n. gNB 160 communicates with UE 102 using one or more antennas 180a-n.

[0043] UE 102 and gNB 160 may communicate with each other using one or more channels 119, 121. For example, UE 102 may transmit information or data to gNB 160 using one or more uplink channels 121. Examples of uplink channel 121 include PUCCH (Physical Uplink Control Channel), PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), etc. For example, uplink channel 121 (e.g., PUSCH) may be used to transmit UL data (i.e., transport block), MAC PDU, and / or UL-SCH (Uplink Shared Channel).

[0044] In some examples, UL data may include URLLC data. URLLC data may be UL-SCH data. In some examples, URLLC-PUSCH (i.e., a different physical uplink shared channel from PUSCH) may be defined to transmit URLLC data. For simplicity of description, the term "PUSCH" may represent any of the following: (1) only PUSCH (e.g., conventional PUSCH, non-URLLC-PUSCH, etc.), (2) PUSCH or URLLC-PUSCH, (3) PUSCH and URLLC-PUSCH, or (4) only URLLC-PUSCH (e.g., not conventional PUSCH).

[0045] Moreover, for example, the uplink channel 121 can be used to transmit Hybrid Automatic Repeat reQuest ACKnowledgment (HARQ-ACK), Channel State Information (CSI), and / or Scheduling Request (SR). The HARQ-ACK can include information indicating an ACKnowledgment (ACK) or Negative ACKnowledgment (NACK) of DL data (i.e., transport block), Media Access Control Protocol Data Unit (MAC PDU), and / or DL-SCH (Downlink Shared Channel).

[0046] The CSI can include information indicating the channel quality of the downlink. The SR can be used to request UL-SCH (Uplink Shared Channel) resources for new transmissions and / or retransmissions. For example, the SR can be used to request UL resources for transmitting UL data.

[0047] For example, one or more gNBs 160 can also use one or more downlink channels 119 to transmit information or data to one or more UEs 102. Examples of the downlink channel 119 include PDCCH, PDSCH, etc. Other types of channels can be used. The PDCCH can be used to transmit Downlink Control Information (DCI).

[0048] Each of the one or more UEs 102 can include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104, and a UE operation module 124. For example, one or more receive paths and / or transmit paths can 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) can be implemented.

[0049] The transceiver 118 can include one or more receivers 120 and one or more transmitters 158. One or more receivers 120 can receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 can receive and down-convert the signals to generate one or more received signals 116. The one or more received signals 116 can be provided to the demodulator 114. One or more transmitters 158 can transmit signals to the gNB 160 using one or more antennas 122a-n. For example, one or more transmitters 158 can up-convert and transmit one or more modulated signals 156.

[0050] 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 signals. 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 operation module 124 can use to perform one or more operations.

[0051] Generally speaking, the UE operation module 124 may enable the UE 102 to communicate with one or more gNBs 160. The UE operation module 124 may include a UE scheduling module 126.

[0052] The UE 102 may utilize the UE scheduling module 126 to perform one or more downlink receptions and / or one or more uplink transmissions. Downlink reception may include the reception of data, the reception of downlink control information, and / or the reception of downlink reference signals. Uplink transmission includes the transmission of data, the transmission of uplink control information, and / or the transmission of uplink reference signals.

[0053] In a radio communication system, physical channels (e.g., uplink physical channels and / or downlink physical channels) may be defined. The physical channels (e.g., uplink physical channels and / or downlink physical channels) may be used to convey (e.g., transmit and / or receive) information delivered from a higher layer.

[0054] For example, in the uplink, a physical random access channel (PRACH) may be defined. In some methods, the PRACH (and / or the random access process) may be used for an initial access connection establishment process, a handover process, a connection re-establishment, timing adjustment (e.g., for uplink transmission synchronization, for UL synchronization), and / or for requesting uplink shared channel (UL-SCH) resources (e.g., uplink physical shared channel (PSCH) (e.g., PUSCH) resources).

[0055] In some examples, a Physical Uplink Control Channel (PUCCH) may be defined. The PUCCH may be used to transmit uplink control information (UCI). The UCI may include Hybrid Automatic Repeat reQuest - ACK (HARQ - ACK), Channel State Information (CSI), and / or Scheduling Request (SR). The HARQ - ACK may be used to indicate an acknowledgement (ACK) or negative acknowledgement (NACK) of downlink data (e.g., transport block, Medium Access Control Protocol Data Unit (MAC PDU), and / or Downlink Shared Channel (DL - SCH)). The CSI may be used to indicate the state of a downlink channel (e.g., downlink signal). The SR may be used to request uplink data resources (e.g., transport block, MAC PDU, and / or Uplink Shared Channel (UL - SCH)).

[0056] The DL - SCH and / or UL - SCH may be one or more transport channels used in the MAC layer. One or more transport blocks (TBs) and / or MAC PDUs may be defined as units of the transport channels 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 the 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, the transport block may be mapped to one or more codewords.

[0057] In the downlink, a Physical Downlink Control Channel (PDCCH) may be defined. The PDCCH may be used to transmit downlink control information (DCI). In some examples, more than one DCI format may be defined for DCI transmission on the PDCCH. For example, a DCI format may be defined by fields, and the fields may be mapped to information bits (e.g., DCI bits).

[0058] In some examples, DCI format 1_0 for scheduling the Physical Downlink Shared Channel (PDSCH) in a cell may be defined as a DCI format for the downlink. As described herein, one or more Radio Network Temporary Identifiers (e.g., Cell Radio Network Temporary Identifier (C - RNTI), Configured Scheduling RNTI (CS - RNTI), System Information RNTI (SI - RNTI), and / or Random Access RNTI (RA - RNTI)) may be used to transmit DCI format 1_0. In some examples, 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). In some examples, DCI format 1_0 may be monitored (e.g., transmitted, mapped) only in the CSS.

[0059] For example, the DCI included in DCI format 1_0 can be a frequency-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 can be a time-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 can be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_0 can be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_0 can be a HARQ process number. Additionally or alternatively, the DCI included in DCI format 1_0 can be a transmission power control (TPC) command for the PUCCH used for scheduling.

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

[0061] For example, the DCI included in DCI format 1_1 can be a bandwidth part (BWP) indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a frequency-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a time-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_1 can be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_1 can be a HARQ process number. Additionally or alternatively, the DCI included in DCI format 1_1 can be a TPC command for the PUCCH used for scheduling. Additionally or alternatively, the DCI included in DCI format 1_1 can be a CSI request for requesting (e.g., triggering) the transmission of CSI (e.g., CSI report (e.g., aperiodic CSI report)). Additionally or alternatively, as described below, the DCI included in DCI format 1_1 can be information for indicating an index of the configuration of DL semi-persistent scheduling (SPS) (e.g., SPS configuration index).

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

[0063] For example, the DCI included in DCI format 1_2 can be a BWP indicator (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_2 can be a frequency-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_2 can be a time-domain resource allocation (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_2 can be a modulation and coding scheme (e.g., for PDSCH). Additionally or alternatively, the DCI included in DCI format 1_2 can be a new data indicator. Additionally or alternatively, the DCI included in DCI format 1_2 can be a HARQ process number. Additionally or alternatively, the DCI included in DCI format 1_2 can be a TPC command for scheduling PUCCH. Additionally or alternatively, the DCI included in DCI format 1_2 can be a CSI request for requesting (e.g., triggering) the transmission of CSI (e.g., CSI report (e.g., aperiodic CSI report)). Additionally or alternatively, the DCI included in DCI format 1_2 can be a configurable field, e.g., antenna port [0 - 2 bits], transmission configuration indicator [0 - 3 bits], rate matching indicator [0 - 2 bits], sounding reference signal (SRS) request [0 - 3 bits], PRB bundling size indicator [0 - 1 bit], carrier indicator [0 - 3 bits], CSI request [0 - 3 bits], ZP CSI-RS trigger [0 - 2 bits], β offset indicator [0 - 2 bits], SRS resource indicator [0 - 4 bits], repetition factor [0 - 2 bits], and / or priority indicator [0 - 3 bits]. Additionally or alternatively, as described below, the DCI included in DCI format 1_2 can be information (e.g., SPS configuration index) for indicating an index of the configuration for DL semi-persistent scheduling (SPS).

[0064] Additionally or alternatively, DCI format 0_0 for scheduling PUSCH in a cell may be defined as a DCI format for the uplink. Additionally or alternatively, C-RNTI, CS-RNTI, and / or temporary C-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 CSS and / or USS. In some examples, DCI format 0_0 may be monitored (e.g., transmitted, mapped) only in CSS.

[0065] 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 HARQ process number. 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 scheduling PUSCH.

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

[0067] 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 HARQ process number. Additionally or alternatively, the DCI included in DCI format 0_1 may be a TPC command for the PUSCH to be scheduled. 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 the configuration index of a configured grant (e.g., CG configuration index).

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

[0069] For example, the DCI included in DCI format 0_2 may be a BWP indicator (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_2 may be a frequency-domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_2 may be a time-domain resource allocation (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_2 may be a modulation and coding scheme (e.g., for PUSCH). Additionally or alternatively, the DCI included in DCI format 0_2 may be a new data indicator. Additionally or alternatively, the DCI included in DCI format 0_2 may be a HARQ process number. Additionally or alternatively, the DCI included in DCI format 0_2 may be a TPC command for the PUSCH to be scheduled. Additionally or alternatively, the DCI included in DCI format 0_2 may be a CSI request for requesting a CSI report. Additionally or alternatively, the DCI included in DCI format 0_2 may be a configurable field, e.g., antenna port [0 - 2 bits], transmission configuration indicator [0 - 3 bits], rate matching indicator [0 - 2 bits], SRS request [0 - 3 bits], PRB bundling size indicator [0 - 1 bit], carrier indicator [0 - 3 bits], CSI request [0 - 3 bits], ZP CSI-RS trigger [0 - 2 bits], β offset indicator [0 - 2 bits], SRS resource indicator [0 - 4 bits], repetition factor [0 - 2 bits] and / or priority indicator [0 - 3 bits]. Additionally or alternatively, as described below, the DCI included in DCI format 0_2 may be information for indicating the index of the configured grant (e.g., CG configuration index).

[0070] Additionally or alternatively, in the case of receiving DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 (e.g., based on detecting DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2), UE 102 may perform PDSCH reception. Additionally or alternatively, in the case of receiving DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2 (e.g., based on detecting DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2), UE 102 may perform PUSCH transmission.

[0071] In some examples, as described above, the RNTI (e.g., radio network temporary identifier) assigned to UE 102 may be used for the transmission of DCI (e.g., DCI format, DL control channel (e.g., PDCCH)). For example, gNB 160 may transmit information for configuring (e.g., allocating) the RNTI to UE 102 (e.g., by using an RRC message).

[0072] For example, cyclic redundancy check (CRC) parity bits generated based on DCI (which may be simply referred to as CRC) may be appended to the DCI, and after the appending, the CRC parity bits may be scrambled by an RNTI. The UE 102 may attempt to decode (e.g., blindly decode, monitor, detect) the DCI to which the CRC parity bits scrambled by the RNTI are appended. For example, the UE 102 may detect a DL control channel (e.g., PDCCH, DCI, DCI format) based on blind decoding. For example, the UE 102 may use the CRC scrambled by the RNTI to decode the DL control channel. In other words, the UE 102 may use the RNTI to monitor the DL control channel. For example, the UE 102 may use the RNTI to detect the DCI format.

[0073] In some examples, the RNTI may include a C-RNTI (Cell-RNTI), a CS-RNTI (Configured Scheduling C-RNTI), an SI-RNTI (System Information RNTI), an RA-RNTI (Random Access RNTI), and / or a Temporary C-RNTI. For example, the C-RNTI may be a unique identifier for identifying an RRC connection and / or scheduling. Additionally or alternatively, the CS-RNTI may be a unique identifier for scheduling transmission based on configured authorization. Additionally or alternatively, the SI-RNTI may be used to identify system information (SI) (e.g., SI message) mapped on the BCCH and dynamically carried on the DL-SCH. Additionally or alternatively, the SI-RNTI may be used for broadcasting of SI. Additionally or alternatively, the RA-RNTI may be an identifier for a random access procedure (e.g., Msg.2 transmission). Additionally or alternatively, the Temporary C-RNTI may be used for scheduling of a random access procedure (e.g., (re)transmission of Msg.3 (e.g., Msg.3 PUSCH (re)transmission)).

[0074] Additionally or alternatively, a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) may be defined. For example, in the case of scheduling the PDSCH (e.g., PDSCH resource) by using a DCI format, the UE 102 may receive downlink data on the scheduled PDSCH (e.g., PDSCH resource). Additionally or alternatively, in the case of scheduling the PUSCH (e.g., PUSCH resource) by using a DCI format, the UE 102 transmits uplink data on the scheduled PUSCH (e.g., PUSCH resource). For example, the PDSCH may be used to transmit downlink data (e.g., DL-SCH, downlink transport block). Additionally or alternatively, the PUSCH may be used to transmit uplink data (e.g., UL-SCH, uplink transport block).

[0075] In some examples, the PDSCH and / or PUSCH may be used to transmit information of a higher layer (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 (e.g., 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 CE). In some examples, RRC messages and / or MAC CE may be referred to as higher layer signals.

[0076] 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). In some examples, system information may be divided into the MIB and a plurality of system information blocks (SIB). 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.

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

[0078] In radio communication for the uplink, the UL reference signal (RS) may be used as an uplink physical signal. Additionally or alternatively, in radio communication for the downlink, the DL RS may be used as a downlink physical signal. In some examples, the uplink physical signal and / or the downlink physical signal may not be used to transmit information provided by the higher layer, but are used by the physical layer.

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

[0080] The UE scheduling module 126 can perform operations for micro-slot based repetitions. In New Radio (NR), the UE 102 can support multiple types of UL transmissions (PUSCH transmissions). The UL transmissions can include grant-based UL transmissions (e.g., UL transmissions with grants, dynamic grants, PUSCH transmissions with grants, PUSCH transmissions scheduled by DCI (e.g., DCI format 0_0, DCI format 0_1)) and grant-free UL transmissions (e.g., UL transmissions without grants or configured grants, PUSCH transmissions with configured grants).

[0081] There can be two types of grant-free UL transmissions (e.g., UL transmissions without grants, with configured grants, PUSCH transmissions with configured grants). One type of grant-free UL transmission is configured grant type 1, and the other is configured grant type 2.

[0082] For type 1 PUSCH transmissions with configured grants, the relevant parameters can be fully RRC-configured (e.g., configured by using RRC signaling). For example, the parameters for resource allocation provided by an RRC message (rrc-ConfiguredUplinkGrant), such as time domain resource allocation (timeDomainOffset, timeDomainAllocation), frequency domain resource allocation (frequencyDomainAllocation), modulation and coding scheme (MCS) (e.g., mcsAndTBS), antenna port value, bit value for DMRS sequence initialization, precoding information and number of layers, SRS resource indicator (provided by antennaPort, dmrs-SeqInitialization, precodingAndNumberOfLayers, and srs-ResourceIndicator respectively), frequency offset between two frequency hops (frequencyHoppingOffset), etc.

[0083] Activation (e.g., PDCCH, DCI activation) may not be used for type 1 configured grants. For example, for configured grant type 1, the uplink grant is provided by RRC and stored as a configured uplink grant. Retransmissions of configured grant type 1 can be scheduled by a PDCCH with a CRC scrambled by CS-RNTI (configured scheduling RNTI).

[0084] For type 2 PUSCH transmissions with configured grants, the relevant parameters follow the higher layer configuration (e.g., periodicity, number of repetitions, etc.) and the UL grant received on a DCI addressed to the CS-RNTI (PDCCH with CRC scrambled by the CS-RNTI, L1 activation and / or reactivation). For example, for configured grant type 2, the uplink grant can be provided by the PDCCH and stored or cleared as the configured uplink grant based on L1 signaling indicating the activation or deactivation of the configured uplink grant.

[0085] Retransmissions of configured grant type 2 can be scheduled by a PDCCH with CRC scrambled by the CS-RNTI (e.g., with NDI = 1). For example, retransmissions other than repeating the configured uplink grant can use the uplink grant addressed to the CS-RNTI. If the higher layer does not deliver a transport block for transmission on the resources allocated for uplink transmission without a grant, UE 102 may not transmit anything on the resources configured for PUSCH transmission with a configured grant.

[0086] Thus, in NR, UE 102 may support multiple types of uplink transmissions without a grant (also referred to as grant-free (GF) uplink transmissions or GF transmissions or transmissions using a configured grant). The first type (type 1) of GF transmission can be a grant-free UL data transmission, which can be based only on RRC (re)configuration without any L1 signaling. In the second type (type 2) of GF transmission, the grant-free UL data transmission is based on RRC configuration and L1 signaling for the activation and / or deactivation of the grant-free UL data transmission. An example of an RRC configuration is shown in List 1.

[0087]

[0088]

[0089]

[0090]

[0091] List 1

[0092] For type 2, PDCCH activation is required. Lists 2 and 3 show examples of DCI format 0_0 (e.g., fallback DCI) and format 0_1, which can be used to activate type 2 configured grants, and / or retransmit type 2 configured grants and / or type 1 configured grants.

[0093]

[0094]

[0095] List 2

[0096]

[0097]

[0098] List 3

[0099] For both type 1 and type 2 PUSCH transmissions with configured grants, when UE 102 is configured with repK > 1, UE 102 may repeat the TB across repK consecutive time slots, thereby applying the same symbol allocation in each time slot. The parameter repK may be referred to as the number of configured transmission occasions for the repetition (including the initial transmission) of the TB. If the UE procedure for determining the time slot configuration determines that the symbols of the time slot allocated for PUSCH are downlink symbols, then for multi-time slot PUSCH transmissions, the transmission on that time slot may be omitted.

[0100] For grant-based transmissions, PUSCH transmissions are scheduled by DCI (e.g., DCI format 0_0 and DCI format 0_1 shown above). The PUSCH may be allocated (e.g., scheduled) by DCI format 0_0 / 0_1 with a CRC scrambled by a C-RNTI, new-RNTI (e.g., the first RNTI), TC-RNTI, or SP-CSI-RNTI. In the specification, new-RNTI may be referred to as MCS-C-RNTI. Some UE-specific PUSCH parameters may be configured by RRC (i.e., using RRC messages (RRC signaling)). An example of RRC configuration is shown in List 4. For example, pusch-AggregationFactor in PUSCH-Config indicates the number of repetitions of the data. When UE 102 is configured with pusch-AggregationFactor > 1, the same symbol allocation may be applied across pusch-AggregationFactor consecutive time slots, and the PUSCH may be limited to a single transmission layer. UE 102 may repeat the transport block (TB) across pusch-AggregationFactor consecutive time slots, thereby applying the same symbol allocation in each time slot. If the UE procedure for determining the time slot configuration determines that the symbols of the time slot allocated for PUSCH are downlink symbols, then for multi-time slot PUSCH transmissions, the transmission on that time slot may be omitted.

[0101] For PUSCH retransmissions scheduled by a PDCCH with a CRC scrambled by a CS-RNTI with NDI = 1, the parameters in pusch-Config are applicable to PUSCH transmission, in addition to p0-NominalWithoutGrant, p0-PUSCH-Alpha, powerControl-LoopToUse, pathlossReferenceIndex, mcs-Table, mcs-TableTransformPrecoder, and transformPrecoder that may be provided in configuredGrantConfig.

[0102] For PUSCH retransmissions of a PDCCH-scheduled PUSCH with a CRC scrambled by a CS-RNTI with a new data indicator (NDI) equal to 1 (i.e., NDI = 1), if UE 102 is configured with pusch-AggregationFactor, the same symbol allocation may be applied across consecutive slots of pusch-AggregationFactor, and the PUSCH may be limited to a single transport layer. UE 102 may repeat the TB across consecutive slots of pusch-AggregationFactor, thus applying the same symbol allocation in each slot.

[0103]

[0104]

[0105]

[0106]

[0107] List 4

[0108] As described above, for both license-free transmissions and license-based transmissions, if repetition is configured for UE 102, for the repetition, consecutive time slots and the same time-domain resource allocation (e.g., starting symbol and / or length) can be applied to each time slot, which may be referred to herein as slot-based repetition. In another design, two or more PUSCH repetitions can be scheduled and / or configured in one time slot, or two or more PUSCH repetitions can be scheduled and / or configured across time-slot boundaries in consecutively available time slots. In yet another design, two or more PUSCH repetitions in consecutively available time slots can have one repetition in each time slot where the starting symbol and / or duration may be different. Two or more PUSCH repetitions in one time slot or across time-slot boundaries in consecutively available time slots, and / or two or more PUSCH repetitions in consecutively available time slots (where the starting symbol and / or duration may be different) may be referred to as mini-slot-based repetition.

[0109] For example, for slot-based repetition, only one transmission occasion can be scheduled (e.g., allocated) within a time slot (e.g., 14 OFDM symbols and / or 14 SC-FDMA symbols). In some examples, one transmission occasion may correspond to the PUSCH resource to be applied to the PUSCH transmission. Also, the PUSCH resource (e.g., the one transmission occasion) can be identified (e.g., indicated, defined) by using the time-domain resource allocation. For example, the PUSCH resource (e.g., the one transmission occasion) can be identified by using the starting symbol and / or length (i.e., the starting symbol and / or length of the PUSCH resource). For example, for slot-based repetition, the same transmission occasion can be used in the time slot, where the same transmission occasion can be applied to each consecutive time slot.

[0110] Additionally or alternatively, for mini-slot-based repetition, two or more transmission occasions can be scheduled (e.g., allocated) within a time slot. In some examples, each transmission occasion may correspond to the PUSCH resource to be applied to the PUSCH transmission. For example, two or more time-domain resource allocations (two or more values of the starting symbol and / or two or more values of the length) are used to schedule the PUSCH resource (e.g., the transmission occasion) in the time slot. Also, each PUSCH resource (e.g., each transmission occasion) can be identified by using each time-domain resource allocation. For example, the PUSCH resource (e.g., each transmission occasion) can be identified by using each value of the starting symbol and / or each value of the length. For example, for mini-slot-based repetition, the two or more transmission occasions can be used in the time slot, where each transmission occasion among the two or more transmission occasions can be identified by using each starting symbol and / or each length. For example, different starting symbols and / or different lengths can be applied to the two or more transmission occasions in the time slot.

[0111] Additionally or alternatively, for micro-slot based repetitions, each transmission occasion identified by using each start symbol and / or each length may be applied for each slot (e.g., each consecutive slot). For example, different start symbols and / or different lengths may be applied for two or more transmission occasions in two or more slots.

[0112] In one example, if UE 102 is configured by RRC or indicated by L1 / L2 signaling to allow two or more PUSCH repetitions in one slot, after one repetition of the repetition (including the initial transmission) of the TB is completed in the slot, the next repetition may use the remaining available symbols in the slot. For example, in the slot, the transmission occasion (e.g., the remaining available symbols) may be used for the repetition (e.g., the next repetition in the slot). As described above, the available symbols (e.g., the transmission occasion) may be defined as L_r consecutive uplink symbols (i.e., consecutive symbols) starting from symbol S_r (i.e., the start symbol), where symbol S_r may be defined as the first uplink symbol (or the first uplink symbol among the first L_r consecutive uplink symbols in the slot), and L_r is defined as the length of the repetition or the initial transmission (e.g., the symbol). For example, for the second transmission of the repetition in the slot, symbol S_r may be defined as the first uplink symbol after the first transmission of the repetition in the slot (or the first uplink symbol among the first L_r consecutive uplink symbols after the first transmission of the repetition in the slot, or a predefined start position, such as symbol #7, symbol #2, symbol #4, symbol #8, symbol #10). If there are no L_r consecutive uplink symbols in the slot according to the UE procedure for determining the slot configuration (e.g., after the first transmission of the repetition in the slot), the next repetition (e.g., the second transmission of the repetition in the slot) may be skipped (e.g., discarded in the slot, not performed in the slot), or the next repetition in the slot may be omitted (e.g., omitted in the slot).

[0113] For example, gNB 160 may configure information for configuring the execution of micro-slot based repetition by using an RRC message. Also, in the case of executing micro-slot based repetition, if there is no transmission opportunity for transmission in a time slot, UE 102 may skip (e.g., discard, not execute, and / or omit) the transmission. In some examples, as described above, a transmission opportunity (e.g., each transmission opportunity in a time slot) may be identified (e.g., indicated by gNB 160 using DCI format 0_0 and / or 0_1) by using time domain resource allocation (e.g., each time domain resource allocation (e.g., each starting symbol and / or each length)). For example, UE 102 may perform a repeated transmission (e.g., a repeated first transmission, a transmission in a repetition) on a transmission opportunity in a time slot (i.e., if the transmission opportunity is identified by using time domain resource allocation). Moreover, if there is no transmission opportunity (i.e., if there is no transmission opportunity identified based on time domain resource allocation), then UE 102 may skip the repeated transmission (e.g., a repeated second transmission, a transmission in a repetition) in the time slot.

[0114] In yet another design, an available symbol (e.g., a transmission opportunity) may be defined as L_r consecutive symbols (uplink symbols and / or flexible symbols) starting from symbol S_r, where symbol S_r is the first symbol (uplink symbol and / or flexible symbol) after repetition in a time slot (or the first symbol (uplink symbol and / or flexible symbol) among the first L_r consecutive symbols (uplink symbols and / or flexible symbols) after repetition in a time slot, or a predefined starting position, e.g., symbol #7, symbol #2, symbol #4, symbol #8, symbol #10), and L_r is the length of the repetition or the initial transmission. If there are no L_r consecutive symbols (uplink symbols and / or flexible symbols) in a time slot after repetition according to the UE procedure for determining the time slot configuration, then the next repetition may skip that time slot, or the next repetition in the time slot may be omitted. For example, the L_r consecutive symbols may include uplink symbols and / or flexible symbols.

[0115] In yet another example, if the UE 102 is configured by RRC or indicated by L1 / L2 signaling to allow two or more PUSCH repetitions to be performed in one time slot, and different repetitions may use different lengths (number of symbols), then the next repetition immediately following the completion of one repetition in the repetition (including the initial transmission) of the TB in the time slot may use the remaining available symbols in the time slot. The available symbols (e.g., transmission occasion) may be defined as L_rd consecutive uplink symbols starting from symbol S_rd, where symbol S_rd is the first uplink symbol after the repetition in the time slot (or the first uplink symbol among the first L_rd consecutive uplink symbols after the repetition in the time slot, or a predefined starting position, e.g., symbol #7, symbol #2, symbol #4, symbol #8, symbol #10), and L_rd may be a different length compared to the length of the repetition or the initial transmission (i.e., L_r). L_rd may be configured by RRC or indicated by L1 / L2 signaling or fixed by the specification. L_rd may be determined by L_r (e.g., L_rd = L_r - L_delta and L_delta may be a predefined or indicated or configured value (e.g., 1, 2, -1, -2, 0)). L_rd may be determined by the time slot configuration (e.g., L_rd is the number of consecutive uplink symbols remaining in the time slot). If there are not L_rd consecutive uplink symbols in the time slot after the repetition according to the UE procedure for determining the time slot configuration, then the next repetition may skip the time slot, or the next repetition in the time slot may be omitted.

[0116] In yet another design, the available symbols (e.g., transmission opportunities) can be defined as L_rd consecutive symbols (uplink symbols and / or flexible symbols) starting from symbol S_rd, where symbol S_rd is the first symbol (uplink symbol and / or flexible symbol) after a repetition in a time slot (or the first symbol (uplink symbol and / or flexible symbol) among the first L_rd consecutive symbols (uplink symbols and / or flexible symbols) after a repetition in a time slot, or a predefined starting position, e.g., symbol #7, symbol #2, symbol #4, symbol #8, symbol #10), and L_rd can be a length different from the length of the repetition or the initial transmission (i.e., L_r). L_rd can be configured by RRC or indicated by L1 / L2 signaling or fixed by the specification. L_rd can be determined by L_r (e.g., L_rd = L_r - L_delta and L_delta can be a predefined or indicated or configured value (e.g., 1, 2, -1, -2, 0)). L_rd can be determined by the time slot configuration (e.g., L_rd can be the number of consecutive uplink symbols and / or flexible symbols remaining in the time slot). If there are not L_rd consecutive symbols (uplink symbols and / or flexible symbols) after a repetition in the time slot according to the UE procedure used to determine the time slot configuration, the next repetition can skip that time slot, or the next repetition in the time slot can be omitted.

[0117] When UE 102 is configured by RRC or indicated by L1 / L2 signaling to be allowed to perform two or more PUSCH repetitions in a time slot, the two or more PUSCH repetitions may or may not share a demodulation reference signal (DMRS (e.g., DMRS associated with PUSCH transmission)). Whether the two or more PUSCH repetitions share the DMRS can be configured by RRC or indicated by L1 / L2 signaling. For example, if UE 102 is configured by RRC or indicated by L1 / L2 signaling to be allowed to perform two or more PUSCH repetitions in a time slot and the two or more PUSCH repetitions can share the DMRS, the DMRS of the first repetition in the time slot can be reused by subsequent repetitions in the time slot. For example, gNB 160 can transmit information for indicating whether the repetitions in the time slot (and / or across time slots) share the DMRS associated with PUSCH transmission by using an RRC message and / or DCI format (e.g., DCI format 0_0 and / or 0_1).

[0118] For repetitions in consecutive time slots, the same starting symbol may or may not be applied in each time slot. For example, after one or more repetitions of a TB in a completed time slot, the repetition in the next time slot may start at a symbol that may be different from the starting symbol of the repetition in the previous time slot, the starting symbol of the initial transmission, the starting symbol indicated by the PDCCH (e.g., activation of a type 2 configured grant), or the starting symbol configured by the RRC (e.g., configuration of a type 1 configured grant).

[0119] In one example, if UE 102 is configured by the RRC or indicated by L1 / L2 signaling to allow PUSCH repetitions in consecutive time slots to start at different symbols and the length of the repetitions should remain the same, then after one or more repetitions of the TB (including the initial transmission) in a time slot are completed, the next repetition in consecutive time slots may start at symbol S_d in the consecutive time slot. The starting symbol S_d may be defined as the first uplink symbol in consecutive time slots, or the first symbol among the available symbols in consecutive time slots for the repetition (or the first symbol among the first L_r consecutive uplink symbols in consecutive time slots, or a predefined starting position, e.g., symbol #7, symbol #2, symbol #4, symbol #8, symbol #10, or a starting position indicated by the RRC or L1 / L2 signaling) according to the UE procedure for determining the time slot configuration. The available symbols in consecutive time slots for the repetition (e.g., the transmission occasion) may be defined as L_r consecutive uplink symbols in consecutive time slots, where L_r is the length of the repetition or the initial transmission in the previous time slot or the length configured by the RRC (e.g., configuration of a type 1 configured grant) or indicated by the PDCCH (e.g., activation of a type 2 configured grant). If there are no L_r consecutive uplink symbols in consecutive time slots after the repetition according to the UE procedure for determining the time slot configuration, the next repetition in consecutive time slots may skip that time slot, or the next repetition in the concatenated time slots may be omitted.

[0120] In yet another design, the starting symbol S_d may be defined as the first uplink symbol and / or flexible symbol in consecutive time slots, or the first symbol among the available symbols for repetition in consecutive time slots (or the first symbol among the first L_r consecutive symbols (uplink symbols and / or flexible symbols) in consecutive time slots, or a predefined starting position, such as symbol #7, symbol #2, symbol #4, symbol #8, symbol #10, or a starting position indicated by RRC or L1 / L2 signaling), according to the UE procedure for determining the time slot configuration. The available symbols in consecutive time slots (e.g., transmission opportunities) may be defined as L_r consecutive symbols (uplink symbols and / or flexible symbols) in consecutive time slots, where L_r is the length of the repetition or initial transmission in the previous time slot or the length configured by RRC (e.g., the grant configuration of type 1 configuration) or indicated by PDCCH (e.g., the grant activation of type 2 configuration). If there are no L_r consecutive symbols (uplink symbols and / or flexible symbols) in consecutive time slots according to the UE procedure for determining the time slot configuration, the next repetition in the consecutive time slots may skip that time slot, or the next repetition in the connecting time slots may be omitted.

[0121] In yet another example, if the UE 102 is configured by RRC or indicated by L1 / L2 signaling to allow the PUSCH repetitions in consecutive time slots to start at different symbols and the lengths of the repetitions can be different, then after one or more repetitions of the TB repetition (including the initial transmission) in a time slot are completed, the next repetition in consecutive time slots can start at symbol S_d in the consecutive time slots. The starting symbol S_d can be defined as the first uplink symbol in the consecutive time slots, or the first symbol among the available symbols for the repetition in the consecutive time slots (or the first symbol among the first L_rd consecutive uplink symbols in the consecutive time slots, or a predefined starting position, such as symbol #7, symbol #2, symbol #4, symbol #8, symbol #10, or a starting position indicated by RRC or L1 / L2 signaling) according to the UE procedure for determining the time slot configuration. The available symbols for the repetition in the consecutive time slots (e.g., transmission opportunity) can be defined as L_rd consecutive uplink symbols in the consecutive time slots, where L_rd can be a length different from the length represented by L_r, and L_r is the length of the repetition or the initial transmission in the previous time slot or the length configured by RRC (e.g., the authorized configuration of Class 1 configuration) or indicated by PDCCH (e.g., the activation of the authorized configuration of Class 2 configuration). L_rd can be configured by RRC or indicated by L1 / L2 signaling or fixed by the specification. L_rd can be determined by L_r (e.g., L_rd = L_r - L_delta and L_delta can be a predefined or indicated or configured value (e.g., 1, 2, -1, -2, 0)). L_rd can be determined by the time slot configuration (e.g., L_rd is the number of consecutive uplink symbols in the consecutive time slots, or the maximum number of consecutive uplink symbols in the consecutive time slots). If there are no L_rd consecutive uplink symbols in the consecutive time slots according to the UE procedure for determining the time slot configuration, the next repetition in the consecutive time slots can skip that time slot, or the next repetition in the connection time slots can be omitted.

[0122] In yet another design, the starting symbol S_d can be defined as the first uplink symbol and / or flexible symbol in consecutive time slots, or the first symbol among the available symbols for repetition in consecutive time slots (or the first symbol among the first L_rd consecutive symbols (uplink symbols and / or flexible symbols) in consecutive time slots, or a predefined starting position, such as symbol #7, symbol #2, symbol #4, symbol #8, symbol #10, or a starting position indicated by RRC or L1 / L2 signaling), according to the UE procedure for determining the time slot configuration. The available symbols in consecutive time slots (e.g., transmission opportunities) can be defined as L_rd consecutive symbols (uplink symbols and / or flexible symbols) in consecutive time slots, where L_rd can be a different length compared to the length represented by L_r, and L_r is the length of the repetition or initial transmission in the previous time slot or the length configured by RRC (e.g., the grant configuration of class 1 configuration) or indicated by PDCCH (e.g., the grant activation of class 2 configuration). L_rd can be configured by RRC or indicated by L1 / L2 signaling or fixed by the specification. L_rd can be determined by L_r, for example, L_rd = L_r - L_delta, and L_delta can be a predefined or indicated or configured value (e.g., 1, 2, -1, -2, 0). L_rd can be determined by the time slot configuration (e.g., L_rd is the number of consecutive uplink and / or flexible symbols in consecutive time slots, or the maximum number of consecutive uplink and / or flexible symbols in consecutive time slots). If there are no L_rd consecutive symbols (uplink symbols and / or flexible symbols) in consecutive time slots according to the UE procedure for determining the time slot configuration, the next repetition in the consecutive time slots can skip that time slot, or the next repetition in the connecting time slots can be omitted.

[0123] The PUSCH preparation time N_2 [symbols] can be defined as the minimum time for UE 102 to prepare the PUSCH for the TB. N_2 can be determined by parameters and / or UE capabilities. N_2 can be defined in the specification and / or configured by RRC and / or indicated by L1 / L2 signaling. The PUSCH preparation time for the repetition of non-initial transmission can be the same as or different from the PUSCH preparation time for the initial transmission. The PUSCH preparation time for the repetition of non-initial transmission can be represented by N_2r. N_2r can be determined by parameters and / or UE capabilities. N_2r can be defined in the specification and / or configured by RRC and / or indicated by L1 / L2 signaling.

[0124] If UE 102 is configured by a higher layer to transmit PUSCH repetitions in a set of symbols of a time slot as described above (which may not be an initial transmission), and UE 102 detects DCI format 1_0, DCI format 1_1, or DCI format 0_1 indicating that UE 102 receives CSI-RS or PDSCH in a symbol subset from the set of symbols, then UE 102 does not expect to cancel the transmission in some symbols from the set of symbols, where the symbols occur after a number of symbols less than the PUSCH preparation time for the repetition as described above relative to the last symbol of the control resource set in which UE 102 detects DCI format 1_0 or DCI format 1_1 or DCI format 0_1, or UE 102 cancels the PUSCH repetition in the remaining symbols in the set of symbols.

[0125] If UE 102 is scheduled by DCI to transmit PUSCH over multiple time slots and different starting symbols and / or lengths can be applied for each repetition as described above, and if a higher layer parameter (when provided to UE 102) indicates that for a time slot from the multiple time slots, at least one symbol in the set of symbols in which UE 102 is scheduled to transmit PUSCH in the time slot is a downlink symbol, then UE 102 does not transmit PUSCH in the time slot.

[0126] The time slot format includes downlink symbols, uplink symbols, and flexible symbols. The time slot format can be indicated by RRC messages (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated) and / or dynamic signaling (e.g., time slot format indicator (SFI), dynamic SFI, DCI format 2_0, information included in DCI format 2_0). The downlink symbols, uplink symbols, and flexible symbols configured by using RRC messages can be named semi-static UL symbols, semi-static DL symbols, and semi-static flexible symbols respectively. For example, gNB 160 can transmit information for configuring semi-static UL symbols, semi-static DL symbols, and / or semi-static flexible symbols by using RRC messages. UE 102 can determine semi-static UL symbols, semi-static DL symbols, and / or semi-static flexible symbols based on the information included in the RRC messages. The downlink symbols, uplink symbols, and flexible symbols indicated by using dynamic signaling can be named dynamic UL symbols, dynamic DL symbols, and dynamic flexible symbols respectively. For example, gNB 160 can transmit information for indicating dynamic UL symbols, dynamic DL symbols, and / or dynamic flexible symbols by using dynamic signaling. UE 102 can determine dynamic UL symbols, dynamic DL symbols, and / or dynamic flexible symbols based on the information included in the dynamic signaling.

[0127] For a set of symbols in a time slot indicated to be flexible to a UE 102 by higher layer parameters (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated when provided to the UE 102), or when no higher layer parameters (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated) are provided to the UE 102 and in the case where the UE 102 detects DCI format 2_0 that provides a format for the time slot using a time slot format value (e.g., other than 255), if the UE 102 is configured by higher layers to transmit PUSCH repetitions in a set of symbols of the time slot as described above, the UE 102 may transmit PUSCH repetitions in the time slot only if the SFI index field value in DCI format 2_0 indicates the set of symbols of the time slot as uplink.

[0128] If a set of symbols of a time slot includes symbols corresponding to any repetitions of PUSCH transmission as described above, the UE 102 may not expect to detect in DCI format 2_0 an SFI index field value that indicates the set of symbols of the time slot as downlink or flexible.

[0129] If the UE 102 is configured by higher layers to transmit PUSCH repetitions in a set of symbols of the time slot as described above, and the UE 102 detects DCI format 2_0 with a time slot format value (e.g., other than 255) indicating the time slot format in the case where a symbol subset of the set of symbols is downlink or flexible, or the UE 102 detects DCI format 1_0, DCI format 1_1, or DCI format 0_1 indicating that the UE 102 receives CSI-RS or PDSCH in a symbol subset from the set of symbols, the UE 102 may not expect to cancel transmission in some symbols from the set of symbols that occur after a number of symbols less than the PUSCH preparation time for the repetition as described above relative to the last symbol of the CORESET in which the UE 102 detects DCI format 2_0 or DCI format 1_0 or DCI format 1_1 or DCI format 0_1, or the UE 102 cancels PUSCH repetitions in the remaining symbols in the set of symbols.

[0130] For a set of symbols of a slot indicated as flexible by higher layer parameters (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated when provided to UE 102), or when no higher layer parameters (e.g., TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated) are provided to UE 102 and in the case where UE 102 does not detect DCI format 2_0 that provides a slot format for the slot, if UE 102 is configured by higher layer to transmit PUSCH repetitions in a set of symbols of the slot as described above, UE 102 may not transmit PUSCH repetitions in some symbols of the set of symbols of the slot from the slot, if any, which start after the last symbol of the control resource set in which UE 102 is configured to monitor DCI format 2_0 of PDCCH and before the number of symbols that is equal to the PUSCH preparation time N_2r of the corresponding PUSCH timing capability, or, UE 102 may not be expected to cancel PUSCH repetitions in some symbols of the set of symbols from the slot, if any, which start after the last symbol of the CORESET in which the UE is configured to monitor DCI format 2_0 of PDCCH and before the number of symbols that is equal to the PUSCH preparation time N_2r of the corresponding PUSCH timing capability.

[0131] As described above, there may be two types of PUSCH repetitions. One may be referred to as slot-based repetition, which means that the repetitions may use consecutive slots and the same time domain resource allocation (e.g., starting symbol and / or length) may be applied to each slot. The other may be referred to as mini-slot-based repetition, which means that multiple PUSCH repetitions may be in one slot and / or PUSCH repetitions in consecutive available slots may use different starting symbols and / or durations / lengths.

[0132] This document describes which of slot-based repetition or mini-slot-based repetition is applied and / or how to switch between slot-based repetition and mini-slot-based repetition.

[0133] In one design, it can be explicitly configured whether to apply slot-based repetition or mini-slot-based repetition via RRC (i.e., by using RRC messages (RRC signaling)). For example, for grant-free PUSCH transmission (e.g., type 1 configured grant or type 2 configured grant), if the RRC parameter mini-slot-repetition-enabler in the configured grant configuration (e.g., Configured-GrantConfig) is configured or indicated as true, mini-slot-based repetition can be applied. If the RRC parameter mini-slot-repetition-enabler in the configured grant configuration (e.g., ConfiguredGrantConfig) is not configured or it is indicated as false, slot-based repetition can be applied. For grant-based PUSCH transmission (e.g., PUSCH allocated (e.g., scheduled) by DCI format 0_0 / 0_1 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, or SP-CSI-RNTI), if the RRC parameter mini-slot-repetition-enabler in the PUSCH configuration (e.g., PUSCH-Config) is configured or indicated as true, mini-slot-based repetition can be applied. If the RRC parameter mini-slot-repetition-enabler in the PUSCH configuration (e.g., PUSCH-Config) is not configured or it is indicated as false, slot-based repetition can be applied. For retransmission of grant-free transmission (e.g., PUSCH scheduled by DCI format 0_0 / 0_1 with CRC scrambled by CS-RNTI with NDI = 1), whether to apply slot-based repetition or mini-slot-based repetition can follow the RRC parameter in the configured grant configuration as configured above, or follow the RRC parameter in the PUSCH configuration as configured above.

[0134] In yet another design, slot-based repetition and mini-slot-based repetition can indicate the number of repetitions using different parameters (also referred to herein as repetition parameters). For example, for grant-free PUSCH transmission (e.g., grant of type 1 configuration or grant of type 2 configuration), if the RRC parameter repK-new (indicating the number of repetitions for mini-slot-based repetition) is configured and / or indicated to be greater than 1, mini-slot-based repetition can be applied. This RRC parameter repK-new can be different from repK in the configured grant configuration (e.g., ConfiguredGrantConfig) (indicating the number of repetitions for slot-based repetition). If both repK-new and repK are configured, repK-new can overwrite repK, and / or mini-slot-based repetition can be applied. If both repK-new and repK are configured, repK can overwrite repK-new, and / or slot-based repetition can be applied.

[0135] For grant-based PUSCH transmission (e.g., PUSCH allocated (e.g., scheduled) by DCI format 0_0 / 0_1 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, or SP-CSI-RNTI), if the RRC parameter pusch-AggregationFactor-new (indicating the number of repetitions for micro-slot-based repetition) is configured and / or indicated to be greater than 1, micro-slot-based repetition can be applied. This RRC parameter pusch-AggregationFactor-new can be different from the pusch-AggregationFactor in the PUSCH configuration (e.g., PUSCH-Config) (indicating the number of repetitions for slot-based repetition). If both pusch-AggregationFactor-new and pusch-AggregationFactor are configured, pusch-AggregationFactor-new can overwrite pusch-AggregationFactor, and / or micro-slot-based repetition can be applied. In another example, if both pusch-AggregationFactor-new and pusch-AggregationFactor are configured, pusch-AggregationFactor can overwrite pusch-AggregationFactor-new, and / or slot-based repetition can be applied. For retransmission of grant-free transmission (e.g., PUSCH scheduled by DCI format 0_0 / 0_1 with CRC scrambled by CS-RNTI with NDI = 1), whether to apply slot-based repetition or micro-slot-based repetition can follow the RRC parameter in the grant configuration configured as above, or can follow the RRC parameter in the PUSCH configuration as above.

[0136] In another design, whether to apply slot-based repetition or micro-slot-based repetition can depend on a periodicity parameter. For example, for grant-free PUSCH transmission (e.g., type 1 configured grant or type 2 configured grant), if the RRC parameter periodicity in the configured grant configuration (e.g., ConfiguredGrantConfig) is greater than (or less than) a certain value (e.g., a single predetermined value and / or threshold), micro-slot-based repetition can be applied. If the RRC parameter periodicity in the configured grant configuration (e.g., ConfiguredGrantConfig) is less than (or greater than) a certain value (e.g., a single predetermined value and / or threshold), slot-based repetition can be applied.

[0137] In yet another design, whether to apply slot-based repetition or micro-slot-based repetition may depend on the modulation and coding scheme (MCS) table. For example, for unlicensed PUSCH transmission (e.g., grant of type 1 configuration or grant of type 2 configuration) and / or retransmission of unlicensed transmission (e.g., PUSCH scheduled by DCI format 0_0 / 0_1 with CRC scrambled by CS-RNTI having NDI = 1), if a low spectral efficiency (SE) MCS table is configured (e.g., the RRC parameter mcs-Table or mcs-TableTransformPrecoder in the configured grant configuration (e.g., ConfiguredGrantConfig) is configured as qam64LowSE), then micro-slot-based repetition may be applied; otherwise, slot-based repetition may be applied. In yet another design, if a low SE MCS table is configured (e.g., the RRC parameter mcs-Table or mcs-TableTransformPrecoder in the configured grant configuration (e.g., ConfiguredGrantConfig) is configured as qam64LowSE), then slot-based repetition may be applied; otherwise, micro-slot-based repetition may be applied. For grant-based PUSCH transmission (e.g., PUSCH allocated (e.g., scheduled) by DCI format 0_0 / 0_1 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, or SP-CSI-RNTI), if a low SE MCS table is configured (e.g., the RRC parameter mcs-Table or mcs-TableTransformPrecoder in the PUSCH configuration (e.g., PUSCH-Config) is configured as qam64LowSE), then micro-slot-based repetition may be applied; otherwise, slot-based repetition may be applied. In yet another design, if a low SE MCS table is configured (e.g., the RRC parameter mcs-Table or mcs-TableTransformPrecoder in the PUSCH configuration (e.g., PUSCH-Config) is configured as qam64LowSE), then slot-based repetition may be applied; otherwise, micro-slot-based repetition may be applied.

[0138] In yet another design, whether to apply slot-based repetition or micro-slot-based repetition may depend on the Radio Network Temporary Identifier (RNTI). For example, for PUSCH transmissions scheduled by DCI format 0_0 / 0_1 with CRC scrambled by MCS-C-RNTI and repetition configured, micro-slot-based repetition (or slot-based repetition) may always be applied. In another example, a new RNTI (e.g., REP-C-RNTI) may be introduced for micro-slot-based repetition. For example, for PUSCH transmissions scheduled by a DCI format with CRC scrambled by REP-C-RNTI and repetition configured, micro-slot-based repetition may always be applied.

[0139] In yet another design, whether to apply slot-based repetition or micro-slot-based repetition may depend on the Downlink Control Information (DCI) format. For example, micro-slot-based repetition may be applied only when using non-backoff DCI (e.g., DCI format 0_1). In another example, a new DCI format may be introduced for micro-slot-based repetition. For example, for PUSCH transmissions scheduled by the new DCI format and / or grant-free transmissions activated by the new DCI format, when repetition is enabled, micro-slot-based repetition is enabled. The new DCI format may include an indication for micro-slot repetition and / or a parameter indicating the number of micro-slot-based repetitions.

[0140] In yet another design, whether to apply slot-based repetition or micro-slot-based repetition may depend on the slot configuration. For example, if the slot configuration period configured by RRC is greater than (or less than) a threshold, micro-slot-based repetition may be applied; otherwise, slot-based repetition may be applied. In another example, if the number of slots with only downlink symbols configured by RRC is greater than (or less than) a threshold, micro-slot-based repetition may be applied; otherwise, slot-based repetition may be applied. In another example, if the number of slots with only uplink symbols configured by RRC is greater than (or less than) a threshold, micro-slot-based repetition may be applied; otherwise, slot-based repetition may be applied. In another example, if the number of downlink symbols configured by RRC is greater than (or less than) a threshold, micro-slot-based repetition may be applied; otherwise, slot-based repetition may be applied. In another example, if the number of uplink symbols configured by RRC is greater than (or less than) a threshold, micro-slot-based repetition may be applied; otherwise, slot-based repetition may be applied.

[0141] When configured and / or enabled with micro-slot based repetition as described above, fallback behavior may be supported in some cases (e.g., even if micro-slot based repetition is configured / enabled, slot based repetition may be applied (e.g., for specific conditions)). In one design, if UE 102 detects a fallback DCI (e.g., DCI format 0_0) in the CSS (e.g., and / or the CSS associated with CORESET#0), then UE 102 may perform slot based repetition even if micro-slot based repetition is configured / enabled as described above. For example, if micro-slot based repetition is configured by RRC (i.e., RRC message (RRC signaling)), then if UE 102 detects a fallback DCI (e.g., DCI format 0_0) in the CSS (e.g., and / or the CSS associated with CORESET#0), then UE 102 may perform slot based repetition. If both repK-new (pusch-AggregationFactor-new) and repK (pusch-AggregationFactor) are configured, then in the case where UE 102 detects a fallback DCI (e.g., DCI format 0_0) in the CSS (e.g., and / or the CSS associated with CORESET#0), UE 102 may perform slot based repetition and the repetition number repK (pusch-AggregationFactor) may be applied. In yet another design, UE 102 may perform slot based repetition according to the RNTI used to scramble the CRC attached to the DCI. For example, if a new RNTI (e.g., REP-C-RNTI) is configured for micro-slot based repetition, and if UE 102 detects a DCI with a CRC scrambled by a different RNTI (e.g., C-RNTI), then UE 102 may perform slot based repetition.

[0142] For example, in the case of detecting DCI format 0_0 in the CSS, slot based repetition may be used (e.g., by UE 102). For example, even if micro-slot based repetition is configured to be enabled, in the case of detecting DCI format 0_0 in the CSS, UE102 may perform slot based repetition. For example, if micro-slot based repetition is configured to be enabled, then in the case of detecting a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) in the USS, UE 102 may perform micro-slot based repetition.

[0143] Additionally or alternatively, in the case where a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET#0 (i.e., the CORESET with index "0"), slot-based repetition may be used. For example, even if micro-slot-based repetition is configured to be enabled, in the case where a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in CORESET#0 (e.g., the search space associated with CORESET#0 (e.g., CSS)), UE 102 may perform slot-based repetition. For example, if micro-slot-based repetition is configured to be enabled, in the case where a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in a CORESET other than CORESET#0, UE 102 may perform micro-slot-based repetition.

[0144] Additionally or alternatively, in the case where a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in search space set#0 (i.e., the search space set with index "0"), slot-based repetition may be used. For example, even if micro-slot-based repetition is configured to be enabled, in the case where a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in search space set#0, UE 102 may perform slot-based repetition. For example, if micro-slot-based repetition is configured to be enabled, in the case where a DCI format (e.g., DCI format 0_0 and / or DCI format 0_1) is detected in a search space set other than search space set#0, UE 102 may perform micro-slot-based repetition.

[0145] For configured grant and / or grant-based PUSCH transmission, multi-segment transmission and micro-slot repetition may also be supported. Micro-slot repetition and / or multi-segment transmission may be enabled and / or configured jointly or separately for each configured grant and / or each PUSCH configuration.

[0146] For example, one UL grant for the dynamic PUSCH and one configured grant for the grant-based PUSCH configured by option A can be used to support one or more actual PUSCH repetitions in one time slot, or two or more actual PUSCH repetitions across the time slot boundary in continuously available time slots. The number of repetitions signaled by the gNB 160 (dynamically signaled, e.g., DCI indication, or semi-statically signaled, e.g., RRC-configured, or a combination thereof) can represent the "nominal" number of repetitions. The actual number of repetitions can be greater than the nominal number. The time domain resource allocation (TDRA) field in the DCI or the TDRA parameter in the type 1 configured grant indicates the resources for the first "nominal" repetition. The time domain resources for the remaining repetitions are derived at least based on the resources for the first repetition and the UL / DL direction of the symbols. If the "nominal" repetition (transmission occasion) spans the time slot boundary or the DL / UL handover point, the "nominal" repetition (transmission occasion) can be split into multiple PUSCH repetitions (transmission occasions), where there is one PUSCH repetition (transmission occasion) in each UL period in the time slot (this behavior can be referred to as segmentation here). In cases where multiple configurations of the configured grant and / or multiple configurations of the PUSCH transmission are supported, option A can be configured and / or enabled individually or jointly for each configured grant configuration and / or each PUSCH transmission configuration. One or more new tables of the TDRA can be introduced for option A. The new table of the TDRA can be fixed by the specification (e.g., default table). The new table of the TDRA can be RRC-configured. The new table of the TDRA can generally be configured for multiple configurations of the configured grant and / or multiple configurations of the PUSCH transmission. The new table of the TDRA can be configured and / or enabled individually for each configured grant configuration and / or each PUSCH transmission configuration. How to determine the table of the TDRA can follow the same process as the determination of other parameters described above.

[0147] In yet another example, one UL grant for dynamic PUSCH and one configured grant configuration for grant-based PUSCH configured by option B are used to support one or more PUSCH repetitions in a time slot, or two or more PUSCH repetitions across time slot boundaries in consecutively available time slots. The time domain resource allocation (TDRA) field in the DCI or the TDRA parameter in a type 1 configured grant indicates an entry in a table configured by a higher layer. The number of repetitions, the starting symbol for each repetition, the length of each repetition, and the mapping of the repetitions to time slots can be obtained from each entry in the table. More than one repetition can be mapped to a time slot. The resource allocation for each repetition is contained within one time slot. Each transmitted repetition is contained within one UL period in the time slot. In cases where multiple configurations of the configured grant and / or multiple configurations of PUSCH transmissions are supported, option B can be configured and / or enabled separately or jointly for each configured grant configuration and / or each PUSCH transmission configuration. One or more new tables for TDRA can be introduced for option B. The new table for TDRA can be fixed by a specification (e.g., a default table). The new table for TDRA can be RRC-configured. The new table for TDRA can generally be configured for multiple configurations of the configured grant and / or multiple configurations of PUSCH transmissions. The new table for TDRA can be configured and / or enabled separately for each configured grant configuration and / or each PUSCH transmission configuration. How to determine the table for TDRA can follow the same process as for determining the other parameters described above.

[0148] Both option A and option B can be supported simultaneously. For example, option A can be enabled and / or configured for one of the multiple configurations, while option B can be enabled and / or configured for another of the multiple configurations. In yet another example, option A (or option B) can be enabled and / or configured for a configured grant, while option B (or option A) can be enabled and / or configured for grant-based PUSCH. In yet another example, option A (or option B) can be enabled and / or configured for configured grant type 1, while option B (or option A) can be enabled and / or configured for configured grant type 2.

[0149] For both option A and option B, frequency hopping can be supported. For option A, dynamic indication of the nominal number of repetitions in a DCI-scheduled dynamic PUSCH is supported for PUSCH enhancement. The dynamic indication can be enabled or disabled by the gNB.

[0150] Option A can be used with the following updates: The time domain resource allocation (TDRA) field in the DCI or the TDRA parameter in a type 1 configured grant indicates the resources for the first "nominal" repetition. Additionally, the detailed interaction with the process for UL / DL direction determination is described below.

[0151] Four cases are considered here. The first case (Case 1) is for dynamic grant (DG) PUSCH (e.g., DGPUSCH transmission). For example, UL transmission (e.g., PUSCH transmission) (including repetition) can be dynamically scheduled by an uplink grant in DCI (e.g., DCI format for uplink with CRC scrambled by C-RNTI). The second case (Case 2) is for configured grant (CG) PUSCH (e.g., CG PUSCH transmission, including repetition) except for the first type 2 CG PUSCH transmission (including all repetitions) activated by a UL grant (e.g., the first PUSCH transmission corresponding to type 2 CG). The third case (Case 3) is for the first type 2 CG PUSCH transmission (including all repetitions) activated by a UL grant. The fourth case (Case 4) is for PUSCH retransmission corresponding to a configured grant. For example, PUSCH retransmission (including repetition) is scheduled by a PDCCH with CRC scrambled by CS-RNTI with NDI = 1. In different cases, micro-slot repetition and / or multi-segment transmission may have different interactions with the process of UL / DL direction determination.

[0152] For DG PUSCH transmission (Case 1), how to handle the interaction between enhanced PUSCH (including micro-slot repetition and / or multi-segment transmission) and DL / UL direction may depend on whether the configuration on the dynamic SFI is configured. In some examples, the configuration on the dynamic SFI may include information indicating the monitoring of DCI format 2_0 (as described above) configured for UE 102. For example, for DGPUSCH transmission, based on whether the configuration on the dynamic SFI is configured, UE 102 may determine the interaction with the process of UL / DL direction.

[0153] For DG PUSCH transmission, for the case where the dynamic SFI is not configured (e.g., in this case) (Case 1-1), semi-static flexible symbols can be used for PUSCH transmission (e.g., DG PUSCH transmission). Segmentation can occur around semi-static DL symbols. For example, PUSCH can be divided into two or more PUSCHs around semi-static DL symbols (e.g., based on the position of semi-static DL symbols (e.g., time-domain position)). The processing method here can be referred to as Option 1-1. For example, Option 1-1 may include that PUSCH transmission can be performed on semi-static flexible symbols. Additionally or alternatively, Option 1-1 may include that segmentation of PUSCH occurs around semi-static DL symbols used for PUSCH transmission.

[0154] In some examples, semi-static UL symbols, semi-static DL symbols, and / or semi-static flexible symbols can be configured by using RRC messages. For example, gNB 160 can transmit information for configuring semi-static UL symbols, semi-static DL symbols, and / or semi-static flexible symbols by using RRC messages. UE 102 can determine semi-static UL symbols, semi-static DL symbols, and / or semi-static flexible symbols based on the information included in the RRC message.

[0155] For DG PUSCH transmission, for the case where dynamic SFI is configured (e.g., in this case) (Case 1-2), the behavior (e.g., the interaction with the UL / DL direction process) may not depend on (e.g., may be independent of) the dynamic SFI, which can be referred to as Option 1-2-1. For example, for Option 1-2-1-1, the same processing method as Option 1-1 can be applied. For example, semi-static flexible symbols are used for PUSCH (e.g., DG PUSCH transmission). Segmentation occurs around semi-static DL symbols. However, a conflict may occur between the dynamic SFI (e.g., the DL symbols indicated by the dynamic SFI (e.g., the information included in DCI format 2_0)) and the symbols (e.g., flexible symbols) indicated by the information included in the RRC message for PUSCH transmission, which may or may not be considered an error condition. In one design (Option 1-2-1-1a), the UE does not expect any semi-static flexible symbols to be indicated as DL within the PUSCH transmission time window. In another design (Option 1-2-1-1b), no error condition is defined, and generally, all semi-static flexible symbols are used for PUSCH within the PUSCH transmission time window. For example, UE 102 can perform PUSCH transmission in semi-static flexible symbols (e.g., assumed to be symbols for UL transmission). In another example (Option 1-2-1-2), semi-static DL and / or semi-static flexible symbols are not used for PUSCH. Segmentation occurs around semi-static DL symbols and / or semi-static flexible symbols. In another example (Option 1-2-1-3), the dynamic indication in the UL grant indicates which set of semi-static flexible symbols is used for PUSCH. Segmentation occurs around semi-static DL and the invalid symbols indicated by the dynamic indication. In another example (Option 1-2-1-4), predefined rules are used to determine which set of semi-static flexible symbols is used for PUSCH transmission. Segmentation occurs around the semi-static DL and invalid symbols defined in the rules. For example, UE 102 can perform PUSCH transmission in this set of semi-static flexible symbols, and this set of semi-static symbols used for PUSCH transmission can be specified (e.g., by the specification) and is known information between gNB 160 and UE 102.

[0156] For DG PUSCH transmission, for the case where dynamic SFI is configured (Case 1-2), the behavior may depend on the dynamic SFI, which may be referred to as Option 1-2-2. For example, the UE may use the SFI to determine the symbols for performing PUSCH transmission. For example (Option 1-2-2-1), in the case where the configuration on the dynamic SFI is configured and the SFI included in DCI format 2_0 is received, segmentation occurs around semi-static DL symbols and / or dynamic DL symbols and / or dynamic flexible symbols. In some examples, the dynamic DL symbols and / or dynamic flexible symbols may be indicated by the SFI included in DCI format 2_0. In yet another example (Option 1-2-2-2), in the case where the configuration on the dynamic SFI is configured and the SFI included in DCI format 2_0 is received, the dynamic flexible symbols are used for PUSCH transmission. Segmentation occurs around semi-static DL symbols and / or dynamic DL symbols. In yet another example (Option 1-2-2-3), in the case where the configuration on the dynamic SFI is configured and the SFI included in DCI format 2_0 is received, the dynamic flexible symbols are used for PUSCH transmission. If the repetition (e.g., (e.g., repeated) transmission occasion) conflicts with the dynamic DL symbol, the repetition is not transmitted (e.g., UE 102 may not perform PUSCH transmission (e.g., including the repetition)). In yet another example (Option 1-2-2-4), in the case where the configuration on the dynamic SFI is configured and the SFI included in DCI format 2_0 is received, if the repetition (e.g., (e.g., repeated) transmission occasion) conflicts with the dynamic DL symbol and / or the dynamic flexible symbol, the repetition is not transmitted (e.g., UE 102 may not perform PUSCH transmission (e.g., including the repetition)). In yet another example (Option 1-2-2-5), in the case where the configuration on the dynamic SFI is configured and the SFI included in DCI format 2_0 is not received, if the repetition (e.g., (e.g., repeated) transmission occasion) conflicts with the semi-static flexible symbol, the repetition is not transmitted (e.g., UE 102 may not perform PUSCH transmission (e.g., including the repetition)).

[0157] For CG PUSCH transmission other than the first Category 2 CG PUSCH transmission activated by UL grant (including all repetitions) (Case 2), how to handle the interaction between enhanced PUSCH (including micro-slot repetition and / or multi-segment transmission) and the DL / UL direction may depend on whether the configuration on the dynamic SFI is configured.

[0158] For CG PUSCH transmission other than the first Category 2 CG PUSCH transmission, for the case where dynamic SFI is not configured (Case 2-1), the semi-static flexible symbols may be used for PUSCH. Segmentation may occur around semi-static DL symbols. The processing method here may be referred to as Option 2-1.

[0159] For CG PUSCH transmissions other than the first type 2 CG PUSCH transmission, for the case where dynamic SFI is configured (Case 2-2), the behavior (e.g., interaction with UL / DL direction procedures) may not depend on (e.g., may be independent of) the dynamic SFI, which may be referred to as Option 2-2-1. For example, for Option 2-2-1-1, semi-static DL symbols and / or semi-static flexible symbols are not used for PUSCH. Segmentation occurs around semi-static DL and / or semi-static flexible symbols. In another example (Option 2-2-1-2), predefined rules are used to determine which set of semi-static flexible symbols is used for PUSCH transmission. Segmentation occurs around the semi-static DL and invalid symbols defined in the rules. For example, UE 102 may perform PUSCH transmission within this set of semi-static flexible symbols, and this set of semi-static symbols used for PUSCH transmission may be specified (e.g., by the specification) and is known information between gNB 160 and UE 102.

[0160] For CG PUSCH transmissions other than the first type 2 CG PUSCH transmission, for the case where dynamic SFI is configured (in this case) (Case 2-2), the behavior (e.g., interaction with UL / DL direction procedures) may depend on the dynamic SFI, which may be referred to as Option 2-2-2. For example, the UE may use the SFI to determine the symbols for performing PUSCH transmission. For example (Option 2-2-2-1), in the case where a configuration on the dynamic SFI is configured and an SFI included in DCI format 2_0 is received, segmentation occurs around semi-static DL symbols and dynamic DL and / or flexible symbols. In some examples, the dynamic DL symbols and / or dynamic flexible symbols may be indicated by the SFI included in DCI format 2_0. In another example (Option 2-2-2-2), in the case where a configuration on the dynamic SFI is configured and an SFI included in DCI format 2_0 is received, if the repetition (e.g., (e.g., repeated) transmission occasion) conflicts with semi-static DL symbols and / or dynamic DL and / or dynamic flexible symbols, the repetition is not transmitted (e.g., UE 102 may not perform PUSCH transmission (e.g., including repetition)). In another example (Option 2-2-2-3), in the case where a configuration on the dynamic SFI is configured and an SFI included in DCI format 2_0 is not received, if the repetition (e.g., (e.g., repeated) transmission occasion) conflicts with semi-static flexible symbols, the repetition is not transmitted (e.g., UE 102 may not perform PUSCH transmission (e.g., including repetition)).

[0161] For the first type 2 CG PUSCH transmission (including all repetitions) activated by UL authorization (scenario 3), the same behavior as that for DG PUSCH (scenario 1) can be used (e.g., processing method, interaction with the UL / DL direction determination process). Any option adopted / indicated / configured for scenario 1 (e.g., option 1-1, option 1-2-1, option 1-2-1-1, option 1-2-1-1a, option 1-2-1-1b, option 1-2-1-2, option 1-2-1-3, option 1-2-1-4, option 1-2-2, option 1-2-2-1, option 1-2-2-2, option 1-2-2-3, option 1-2-2-4, and / or option 1-2-2-5) can also be applied to scenario 3. The behaviors for scenario 1 and scenario 3 can be adopted / indicated / configured jointly or separately. For example, gNB 160 can configure the behaviors for scenario 1 and scenario 3 jointly (e.g., by using RRC messages). Additionally or alternatively, gNB 160 can configure the behaviors for scenario 1 and scenario 3 separately (e.g., by using RRC messages). Additionally or alternatively, gNB 160 can indicate the behaviors for scenario 1 and scenario 3 jointly (e.g., by using MAC CE and / or DCI (e.g., transmitted on PDCCH)). Additionally or alternatively, gNB 160 can indicate the behaviors for scenario 1 and scenario 3 separately (e.g., by using MAC CE and / or DCI (e.g., transmitted on PDCCH)). Additionally or alternatively, the behaviors for scenario 1 and scenario 3 can be specified jointly by the specification and can be known information between gNB 160 and UE 102. Additionally or alternatively, the behaviors for scenario 1 and scenario 3 can be specified separately by the specification and can be known information between gNB 160 and UE 102. One of the above options can be used for scenario 1, while a different one of the above options can be used for scenario 3. For example, option 1-2-1 and / or its sub-options (or option 1-2-2 and / or its sub-options) can be adopted / indicated / configured for scenario 1, while option 1-2-2 and / or its sub-options (or option 1-2-1 and / or its sub-options) can be adopted / indicated / configured for scenario 3. Option 1-2-1-2 (or option 1-2-1-1) can be adopted / indicated / configured for scenario 1, while option 1-2-1-1 (or option 1-2-1-2) can be adopted / indicated / configured for scenario 3. Option 1-2-2-2 (or option 1-2-2-1) can be adopted / indicated / configured for scenario 1, while option 1-2-2-1 (or option 1-2-2-2) can be adopted / indicated / configured for scenario 3. Option 1-2-2-1 (or option 1-2-2-4) can be adopted / indicated / configured for scenario 1, while option 1-2-2-4 (or option 1-2-2-1) can be adopted / indicated / configured for scenario 3.Option 1-2-2-3 (or Option 1-2-2-4) can be adopted / indicated / configured for Case 1, while Option 1-2-2-4 (or Option 1-2-2-3) can be adopted / indicated / configured for Case 3.

[0162] For the first Type 2 CG PUSCH (including all repetitions) activated by a UL grant (Case 3), the same behavior as for a CG PUSCH without an associated UL grant (Case 2) can be used. Any option adopted / indicated / configured for Case 2 (e.g., Option 2-1, Option 2-2-1, Option 2-2-1-1, Option 2-2-1-2, Option 2-2-2, Option 2-2-2-1, Option 2-2-2-2, or Option 2-2-2-3) can also be applied to Case 3. The behaviors for Case 2 and Case 3 can be adopted / indicated / configured jointly or separately. For example, gNB 160 can configure the behaviors for Case 2 and Case 3 jointly (e.g., by using an RRC message). Additionally or alternatively, gNB 160 can configure the behaviors for Case 2 and Case 3 separately (e.g., by using an RRC message). Additionally or alternatively, gNB 160 can indicate the behaviors for Case 2 and Case 3 jointly (e.g., by using a MAC CE and / or DCI (e.g., transmitted on a PDCCH)). Additionally or alternatively, gNB 160 can indicate the behaviors for Case 2 and Case 3 separately (e.g., by using a MAC CE and / or DCI (e.g., transmitted on a PDCCH)). Additionally or alternatively, the behaviors for Case 2 and Case 3 can be specified jointly by the specification and can be known information between gNB 160 and UE 102. Additionally or alternatively, the behaviors for Case 2 and Case 3 can be specified separately by the specification and can be known information between gNB 160 and UE 102. Case 2 can use one of the above options, while Case 3 can use a different one of the above options. For example, Option 2-2-1 and / or its sub-options (or Option 2-2-2 and / or its sub-options) can be adopted / indicated / configured for Case 2, while Option 2-2-2 and / or its sub-options (or Option 2-2-1 and / or its sub-options) can be adopted / indicated / configured for Case 3. Option 2-2-1-2 (or Option 2-2-1-1) can be adopted / indicated / configured for Case 2, while Option 2-2-1-1 (or Option 2-2-1-2) can be adopted / indicated / configured for Case 3. Option 2-2-2-2 (or Option 2-2-2-1) can be adopted / indicated / configured for Case 2, while Option 2-2-2-1 (or Option 2-2-2-2) can be adopted / indicated / configured for Case 3.

[0163] For the first type 2 CG PUSCH (including all repetitions) activated by UL authorization (scenario 3), different behaviors can be adopted / indicated / configured. For example (option 3-1), regardless of whether dynamic SFI is configured, semi-static flexible symbols are used for PUSCH, and segmentation occurs around semi-static DL symbols. In another example (option 3-2), regardless of whether dynamic SFI is configured, only semi-static UL symbols are used for PUSCH, and segmentation occurs around semi-static DL and / or semi-static flexible symbols. In another example (option 3-3), regardless of whether dynamic SFI is configured, if the repetition conflicts with semi-static flexible symbols, the repetition is not transmitted. In another example (option 3-4), regardless of whether dynamic SFI is configured, semi-static flexible symbols are used for PUSCH, and if the repetition conflicts with semi-static DL symbols, the repetition is not transmitted.

[0164] For the authorized PUSCH retransmissions (including repetitions) of the configuration (Case 4), the same behavior as that of DG PUSCH (Case 1) can be used (e.g., processing methods, interaction with the UL / DL direction determination procedure). Any option adopted / indicated / configured for Case 1 (e.g., Option 1-1, Option 1-2-1, Option 1-2-1-1, Option 1-2-1-1a, Option 1-2-1-1b, Option 1-2-1-2, Option 1-2-1-3, Option 1-2-1-4, Option 1-2-2, Option 1-2-2-1, Option 1-2-2-2, Option 1-2-2-3, Option 1-2-2-4, and / or Option 1-2-2-5) can also be applied to Case 4. The behaviors for Case 1 and Case 4 can be adopted / indicated / configured jointly or separately. For example, gNB 160 can (e.g., by using RRC messages) jointly configure the behaviors for Case 1 and Case 4. Additionally or alternatively, gNB 160 can (e.g., by using RRC messages) separately configure the behaviors for Case 1 and Case 4. Additionally or alternatively, gNB 160 can (e.g., by using MAC CE and / or DCI (e.g., transmitted on PDCCH)) jointly indicate the behaviors for Case 1 and Case 4. Additionally or alternatively, gNB 160 can (e.g., by using MAC CE and / or DCI (e.g., transmitted on PDCCH)) separately indicate the behaviors for Case 1 and Case 4. Additionally or alternatively, the behaviors for Case 1 and Case 4 can be jointly specified by the specification and can be known information between gNB 160 and UE 102. Additionally or alternatively, the behaviors for Case 1 and Case 4 can be separately specified by the specification and can be known information between gNB 160 and UE 102. Case 1 can use one of the above options, while Case 4 can use a different one of the above options. For example, Option 1-2-1 and / or its sub-options (or Option 1-2-2 and / or its sub-options) can be adopted / indicated / configured for Case 1, while Option 1-2-2 and / or its sub-options (or Option 1-2-1 and / or its sub-options) can be adopted / indicated / configured for Case 4. Option 1-2-1-2 (or Option 1-2-1-1) can be adopted / indicated / configured for Case 1, while Option 1-2-1-1 (or Option 1-2-1-2) can be adopted / indicated / configured for Case 4. Option 1-2-2-2 (or Option 1-2-2-1) can be adopted / indicated / configured for Case 1, while Option 1-2-2-1 (or Option 1-2-2-2) can be adopted / indicated / configured for Case 4. Option 1-2-2-1 (or Option 1-2-2-4) can be adopted / indicated / configured for Case 1, while Option 1-2-2-4 (or Option 1-2-2-1) can be adopted / indicated / configured for Case 4.Option 1-2-2-3 (or Option 1-2-2-4) can be adopted / indicated / configured for Case 1, while Option 1-2-2-4 (or Option 1-2-2-3) can be adopted / indicated / configured for Case 4.

[0165] Additionally or alternatively, for authorized PUSCH retransmissions (including repetitions) of the configuration (Case 4), the same behavior as for CG PUSCH without an associated UL grant (Case 2) can be used. Any option adopted / indicated / configured for Case 2 (e.g., Option 2-1, Option 2-2-1, Option 2-2-1-1, Option 2-2-1-2, Option 2-2-2, Option 2-2-2-1, Option 2-2-2-2, or Option 2-2-2-3) can also be applied to Case 4. The behaviors for Case 2 and Case 4 can be adopted / indicated / configured jointly or separately. For example, gNB 160 can (e.g., by using an RRC message) jointly configure the behaviors for Case 2 and Case 4. Additionally or alternatively, gNB 160 can (e.g., by using an RRC message) separately configure the behaviors for Case 2 and Case 4. Additionally or alternatively, gNB 160 can (e.g., by using MAC CE and / or DCI (e.g., transmitted on PDCCH)) jointly indicate the behaviors for Case 2 and Case 4. Additionally or alternatively, gNB 160 can (e.g., by using MAC CE and / or DCI (e.g., transmitted on PDCCH)) separately indicate the behaviors for Case 2 and Case 4. Additionally or alternatively, the behaviors for Case 2 and Case 4 can be jointly specified by the specification and can be known information between gNB 160 and UE 102. Additionally or alternatively, the behaviors for Case 2 and Case 4 can be separately specified by the specification and can be known information between gNB 160 and UE 102. Case 2 can use one of the above options, while Case 4 can use a different one of the above options. For example, Option 2-2-1 and / or its sub-options (or Option 2-2-2 and / or its sub-options) can be adopted / indicated / configured for Case 2, while Option 2-2-2 and / or its sub-options (or Option 2-2-1 and / or its sub-options) can be adopted / indicated / configured for Case 4. Option 2-2-1-2 (or Option 2-2-1-1) can be adopted / indicated / configured for Case 2, while Option 2-2-1-1 (or Option 2-2-1-2) can be adopted / indicated / configured for Case 4. Option 2-2-2-2 (or Option 2-2-2-1) can be adopted / indicated / configured for Case 2, while Option 2-2-2-1 (or Option 2-2-2-2) can be adopted / indicated / configured for Case 4.

[0166] For the authorized PUSCH retransmissions (including repetitions) of the configuration (scenario 4), different behaviors can be adopted / indicated / configured. For example (option 4-1), regardless of whether the dynamic SFI is configured, semi-static flexible symbols are used for PUSCH, and segmentation occurs around semi-static DL symbols. In another example (option 4-2), regardless of whether the dynamic SFI is configured, only semi-static UL symbols are used for PUSCH, and segmentation occurs around semi-static DL and / or semi-static flexible symbols. In another example (option 4-3), regardless of whether the dynamic SFI is configured, if the repetition conflicts with the semi-static flexible symbols, the repetition is not transmitted. In another example (option 4-4), regardless of whether the dynamic SFI is configured, semi-static flexible symbols are used for PUSCH, and if the repetition conflicts with the semi-static DL symbols, the repetition is not transmitted.

[0167] For the above behaviors, segmentation can always be performed at the slot boundary. For example, UE 102 can always apply segmentation to PUSCH transmissions (DG PUSCH transmissions, CG class 1 PUSCH transmissions, CG class 2 PUSCH transmissions, and / or retransmissions corresponding to CG class 1 and / or CG class 2 PUSCH transmissions) at the slot boundary.

[0168] In the case where the above-mentioned repetition is not transmitted, the entire repetition can be discarded, or only the repetition at the conflicting symbols can be discarded. In another design, a delay of the repetition can be applied. The delay can be applied in the case where the dynamic SFI is not configured and symbol conflicts occur as described above. The delay can be applied when the repetition conflicts with the semi-static flexible symbols.

[0169] To handle conflicts with SSB (synchronization and PBCH (physical broadcast channel) block) and / or PRACH symbols, any of the above behaviors can also be adopted / indicated / configured.

[0170] Regarding how to interpret the length L of all PUSCH transmissions (e.g., the number of symbols for repetition, PUSCH transmission, transmission occasion, or nominal repetition) and the number of repetitions K, the time window during which valid symbols (e.g., UL symbols and / or flexible symbols indicated by RRC messages and / or dynamic signaling) can be used for transmission is L*K. In yet another design, the time window during which valid symbols (e.g., UL symbols and / or flexible symbols indicated by RRC messages and / or dynamic signaling) are used for transmission can be longer than L*K symbols, and the time window is extended at least in the case of semi-static DL symbols. The extension of the time window can also be applied in the case of dynamic DL symbols and / or semi-static flexible symbols and / or reserved symbols (if defined) and / or SSB symbols and / or type 0 CSS in CORESET#0 (as indicated by the MIB). The maximum time window size can be defined in the specification, configured by RRC messages and / or indicated by L1 signaling (e.g., DCI, PDCCH) and / or MAC CE.

[0171] In some examples, the UE scheduling module 126 can perform time-domain resource allocation. Methods for determining time-domain resource allocation (TDRA) for one or more (e.g., all) channels are described herein.

[0172] As described above, a field named time-domain resource allocation can be used to indicate time-domain resource allocation of time slots and / or mini-slots and / or symbols. It should be noted that this field may have different names in some specifications related to, for example, resource allocation (RA). For example, the time-domain resource allocation field value m can provide (e.g., indicate) the row index m + 1 to an allocation table. The determination of the resource allocation table to be used can be defined based on some rules. The index row can define the value of time slot offset and / or mini-slot offset and / or symbol offset (e.g., K for downlink 0 and / or K for uplink 2 ). The index row can define the start and length indicator (SLIV), or can directly indicate the start symbol S and the allocation length L. The index row can define the value of PDSCH mapping and / or the PUSCH mapping type assumed in PDSCH / PUSCH reception. The index row can define the value of the number of repetitions assumed in PDSCH / PUSCH reception. For example, the time-domain resource allocation field can be used to indicate the time-domain relationship between PDCCH and PDSCH (e.g., K 0 and / or the position of time slot, mini-slot, and / or symbol of PDSCH scheduled by the corresponding PDCCH), or the time-domain relationship between PDCCH and PUSCH (e.g., K 2and / or time slots, mini-slots, and / or positions of symbols of PUSCH scheduled by using the corresponding PDCCH), or reference points (e.g., cycle boundary, time slot boundary, subframe boundary, system frame number (SFN) = 0, start symbol of the PDCCH monitoring occasion where DL / UL allocation / grant is detected, etc.) and the time domain relationship between PUSCH / PDSCH. K 0 can represent the delay between DL grant (e.g., PDCCH, DCI) and reception of the corresponding DL data (e.g., PDSCH). K 2 can represent the delay between reception of UL grant (e.g., PDCCH, DCI) in DL and transmission of the corresponding UL data (e.g., PUSCH). Note that the above K 0 and K 2 can be defined in units of time slots, sub-slots, and / or symbols.

[0173] The time domain resource allocation field may be included in the downlink control information (DCI) for uplink (UL) grant and / or downlink (DL) allocation. For example, the time domain resource allocation field may be included in the DCI format for scheduling PUSCH (e.g., DCI format 0_0 and / or DCI format 0_1 and / or DCI format 0_2). The time domain resource allocation field may be included in the DCI format for scheduling PDSCH (e.g., DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2). The time domain resource allocation field may be included in the DCI for activating configured grant type 2 (e.g., DCI format 0_0, DCI format 0_1, DCI format 0_2). The time domain resource allocation field may be included in the DCI for activating DL semi-persistent scheduling (SPS) (e.g., DCI format 1_0, DCI format 1_1, DCI format 1_2). The time domain resource allocation field (which may be referred to by different names, e.g., timeDomainAllocation) may be included in the radio resource control (RRC) signaling for configured grant type 1.

[0174] The network may indicate, in a downlink / uplink (DL / UL) allocation, which configured time-domain allocation (e.g., allocation table) the UE 102 may apply to the DL / UL allocation. A number of default allocation tables may be specified. In some examples, the default allocation tables may be defined only for a 4-bit time-domain resource allocation field. For example, the default allocation table may have 16 entities. Also, default allocation tables may be defined for more than 4-bit time-domain resource allocation fields. For example, under the condition of using the default allocation table, the 4-bit time-domain resource allocation field may always be used for time-domain resource allocation (RA) (e.g., for downlink and / or for uplink). The allocation table may be configured by using the information included in the RRC message. Some examples are shown in the following table. List (5) shows an example of the PUSCH-TimeDomainResourceAllocation information element. List (6) shows an example of the PDSCH-TimeDomainResourceAllocationList information element.

[0175]

[0176] List 5

[0177]

[0178] List - 6

[0179] The UE 102 may determine the number of bits (e.g., bit width, size) of the time-domain resource allocation field based on the number of entries in the allocation table. As described above, the number of entries may be determined (e.g., configured) based on the information included in the RRC message. In some examples, the maximum number of entries (e.g., maxNrofUL-Allocations or maxNrofDL-Allocations) in the configured allocation table may be set to 16 (or 32 or 64). In some examples, the maximum number of entries in the default allocation table may be 16 (or 32 or 64). In this case, the number of bits (e.g., maximum number of bits) of the time-domain resource allocation field may be 4 (or 5 or 6). For example, the number of bits of the time-domain resource allocation field in the fallback DCI (e.g., DCI format 0_0 or DCI format 1_0) may be 4. The number of bits of the time-domain resource allocation field in the non-fallback DCI (e.g., DCI format 0_1, or DCI format 1_1, DCI format 0_2, DCI format 1_2) may be 0, 1, 2, 3, 4, 5, or 6.

[0180] In some examples, the 16 entries in the allocation table (i.e., 16 time domain allocations) may not be sufficient to meet the requirements of flexible scheduling, dynamic indication of the number of repetitions, or other requirements. Therefore, in different designs, the allocation table with more than 16 entries can be configured by using the information included in the RRC message. For example, the number of entries (e.g., the maximum number of entries) (e.g., maxNrofUL-Allocations1 or maxNrofDL-Allocations1) in the configured allocation table can be set to be greater than 16 (e.g., 32 or 64). Additionally or alternatively, one or more default allocation tables with more than 16 entries can be defined. In this case, the time domain resource allocation field may require more than 4 bits. For example, UE102 may need to identify a 4-bit time domain resource allocation field and / or a time domain resource allocation field with more than 4 bits (e.g., a 5-bit or 6-bit time domain resource allocation field).

[0181] As described above, to support dynamic authorization and / or dynamic indication of the number of repetitions of configured authorization, the number of repetitions can be jointly encoded with SLIV in the TDRA table by adding an additional column for the number of repetitions in the TDRA table (default table and / or RRC-configured table). The maximum TDRA table size can be increased to 64. The start symbol S and length L can be used instead of SLIV. The TDRA table can be configured for each DCI format. Some examples are shown in the following table. List 7 shows an example of the PUSCH-TimeDomainResourceAllocation-ForDCIformat0_1 (and PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1) information element. List 8 shows an example of the PUSCH-TimeDomainResourceAllocation-ForDCIformat0_2 (and PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2) information element. List 9 shows an example of the PUSCH-TimeDomainResourceAllocation-ForDCIformat0_2 (and PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2) information element, where the startSymbolAndLengthSLIV is replaced by a separate start symbol S and length L.

[0182]

[0183] List 7

[0184]

[0185] List 8

[0186]

[0187] List 9

[0188] As described above, there may be a parameter aggregation factor (e.g., PUSCH-AggregationFactor) in an RRC message (e.g., PUSCH-Config) to indicate the semi-static number of repetitions. In the case of configuring both the aggregation factor with the number of repetitions and the TDRA table, some examples of the rules for determining the number of repetitions are described herein. For example, if the parameter aggregation factor (e.g., pusch-AggregationFactor) is RRC-configured (e.g., PUSCH-Config) and the TDRA table with numberofrepetitions is configured for a DCI format (e.g., DCI format 0_1, DCI format 0_2, or DCI format 0_0), when the UE detects the DCI format that schedules the PUSCH, the parameter aggregation factor can be ignored and the dynamic indication of the number of repetitions can be applied. For example, the numberofrepetitions in the row of the TDRA (indicated by the TDRA field in the DCI format) can always override the parameter aggregation factor (e.g., pusch-AggregationFactor) in the RRC message (e.g., PUSCH-Config), and the UE 102 can perform PUSCH repetition by using the number of repetitions. In yet another example, if the parameter aggregation factor (e.g., pusch-AggregationFactor) is RRC-configured (e.g., PUSCH-Config) and the TDRA table with the number of repetitions is configured for a DCI format (e.g., DCI format 0_1, DCI format 0_2, or DCI format 0_0), when the UE 102 detects the DCI format that schedules the PUSCH, the parameter aggregation factor can be applied and the dynamic indication of the number of repetitions can be disabled. For example, the parameter aggregation factor (e.g., pusch-AggregationFactor) in the RRC message (e.g., PUSCH-Config) can always override the numberofrepetitions in the row of the TDRA (indicated by the TDRA field in the DCI format), and the UE 102 can perform PUSCH repetition by using the parameter aggregation factor. In yet another example, there may be an RRC parameter to indicate whether to apply the semi-static indication of the number of repetitions (e.g., the parameter aggregation factor (e.g., pusch-AggregationFactor) in the RRC message (e.g., PUSCH-Config)) or to apply the dynamic indication of numberofrepetitions (e.g., the numberofrepetitions in the row of the TDRA (indicated by the TDRA field in the DCI format)).If the RRC parameter (e.g., RepIndicaitonTyple) indicates semi-static indication (or dynamic indication is not indicated by the RRC parameter, or the RRC parameter does not exist), the pusch-AggregationFactor can be applied to PUSCH transmission. If the RRC parameter (e.g., RepIndicaitonTyple) indicates dynamic indication (or semi-static indication is not indicated by the RRC parameter, or the RRC parameter does not exist), the numberofrepetitions in the row of TDRA (indicated by the TDRA field in the DCI format) is applied to PUSCH transmission. In yet another example, the UE may not expect to configure both the parameter aggregation factor (e.g., pusch-AggregationFactor) in the RRC message (e.g., PUSCH-Config) and the TDRA table with numberofrepetitions having a DCI format (e.g., DCI format 0_1, DCI format 0_2, or DCI format 0_0). For example, UE 102 can be configured with either the parameter aggregation factor (e.g., pusch-AggregationFactor) in the RRC message (e.g., PUSCH-Config) or the TDRA table with numberofrepetitions, but not both at the same time.

[0189] As described above, there may be a parameter repetition count (e.g., repK) in an RRC message (e.g., ConfiguredGrantConfig) to indicate the semi-static repetition count of a configured grant. In the case of both a configured repetition count (e.g., repK) and a TDRA table with numberofrepetitions, examples of some rules for determining the repetition count of a configured grant are described herein. For example, if the parameter repetition count (e.g., repK) is RRC-configured (e.g., ConfiguredGrantConfig) and a TDRA table with numberofrepetitions is configured for a DCI format (e.g., DCI format 0_1, DCI format 0_2, or DCI format 0_0), when UE 102 detects a DCI format for activating a configured grant type 2, the parameter repetition count (e.g., repK) may be ignored and the dynamic indication of the repetition count may be applied. For example, the numberofrepetitions in the row of the TDRA (indicated by the TDRA field in the DCI format for activation) may always override the parameter repetition count (e.g., repK) in the RRC message (e.g., ConfiguredGrantConfig), and UE 102 may perform configured grant PUSCH transmission by using the numberofrepetitions. In yet another example, if the parameter repetition count (e.g., repK) is RRC-configured (e.g., Configured-GrantConfig) and a TDRA table with numberofrepetitions is configured for a DCI format (e.g., DCI format 0_1, DCI format 0_2, or DCI format 0_0), when UE102 detects a DCI format for activating a configured grant type 2, the parameter repetition count (e.g., repK) may be applied and the dynamic indication of the repetition count may be disabled. For example, the parameter repetition count (e.g., repK) in the RRC message (e.g., ConfiguredGrantConfig) may always override the numberofrepetitions in the row of the TDRA (indicated by the TDRA field in the DCI format for activating the configured grant), and UE 102 may perform configured grant PUSCH repetition by using the parameter repetition count (e.g., repK) in the RRC message (e.g., ConfiguredGrantConfig).In yet another example, there may be an RRC parameter to indicate whether to apply a semi-static indication of the number of repetitions (e.g., the parameter number of repetitions (e.g., repK) in the RRC message (e.g., ConfiguredGrantConfig)) or to apply a dynamic indication of number of repetitions (e.g., number of repetitions in the row of the TDRA indicated by the TDRA field in the DCI format used to activate the configured grant). If the RRC parameter (e.g., RepIndicaitonTyple) indicates a semi-static indication (or the dynamic indication is not indicated by the RRC parameter, or the RRC parameter does not exist), then after activation by the DCI format, the number of repetitions (e.g., repK) in the RRC message (e.g., ConfiguredGrantConfig) can be applied to the configured grant PUSCH transmission. If the RRC parameter (e.g., RepIndicaitonTyple) indicates a dynamic indication (or the semi-static indication is not indicated by the RRC parameter, or the RRC parameter does not exist), then after activation by the DCI format, the number of repetitions in the row of the TDRA (indicated by the TDRA field in the DCI format) can be applied to the configured grant PUSCH transmission. In yet another example, UE 102 may not expect to configure both the parameter number of repetitions (e.g., repK) in the RRC message (e.g., ConfiguredGrantConfig) and the TDRA table with number of repetitions having a DCI format (e.g., DCI format 0_1, DCI format 0_2, or DCI format 0_0). For example, UE 102 may be configured with the parameter number of repetitions (e.g., repK) in the RRC message (e.g., ConfiguredGrantConfig) or the TDRA table with number of repetitions, but not both at the same time.

[0190] For dynamic grants (DG, e.g., PUSCH transmissions scheduled by a DCI format with a CRC scrambled by a C-RNTI) and retransmissions of CGs (e.g., PUSCH transmissions scheduled by a DCI format with a CRC scrambled by a CS-RNTI and NDI = 1), an RRC parameter can be introduced for each of DCI format 0_1 and the new UL DCI format (DCI format 0_2) to indicate whether UE102 follows the behavior of slot-based repetition or micro-slot-based repetition as described above (e.g., option A). For example, there can be an RRC parameter to indicate whether to apply slot-based repetition or micro-slot-based repetition (e.g., option A). If the RRC parameter (e.g., RepTyple) indicates slot-based repetition (or micro-slot-based repetition is not indicated by the RRC parameter, or the RRC parameter does not exist), then slot-based repetition can be applied to the PUSCH transmission. If the RRC parameter (e.g., RepTyple) indicates micro-slot-based repetition (or slot-based repetition is not indicated by the RRC parameter, or the RRC parameter does not exist), then micro-slot-based repetition can be applied to the PUSCH transmission. In yet another example, if the parameter aggregation factor (e.g., PUSCH-AggregationFactor) is RRC-configured (e.g., PUSCH-Config), then slot-based repetition can always be applied regardless of whether micro-slot-based repetition is enabled and / or whether a TDRA table with numberofrepetitions is configured for the DCI format. In yet another example, if a TDRA table with numberofrepetitions is configured for the DCI format, then micro-slot-based repetition can always be applied to DGs and / or retransmissions of CGs scheduled by the DCI format regardless of whether slot-based repetition is enabled and / or whether the parameter aggregation factor (e.g., pusch-AggregationFactor) is RRC-configured (e.g., PUSCH-Config). In yet another example, if the mappingType in a row of the TDRA table (e.g., indicated by the TDRA field in the DCI format) indicates type A, then slot-based repetition can be applied. If the mappingType in a row of the TDRA table (e.g., indicated by the TDRA field in the DCI format) indicates type B, then micro-slot-based repetition can be applied.

[0191] As described above, there may be multiple TDRA tables. For example, the PUSCH-TimeDomainResourceAllocationList in a UE-specific RRC message (e.g., PUSCH-Config), the pusch-TimeDomainAllocationList provided in a common RRC message (e.g., pusch-ConfigCommon), the PUSCH-TimeDomainRe-sourceAllocationList-ForDCIformat0_1 in a UE-specific RRC message (e.g., PUSCH-Config), the PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2 in a UE-specific RRC message (e.g., PUSCH-Config), and / or a defined default TDRA table. Examples of the determination of the resource allocation table for PUSCH are described herein. For example, if UE 102 detects DCI format 0_1 for scheduling PUSCH (and / or activating configured grant type 2) (e.g., in any common search space associated with CORESET 0, in any common search space not associated with CORESET 0, and / or in a UE-specific search space) and PUSCH-timedomainresourcallocationlist-fordciformat0_1 is configured, then PUSCH-timedomainresourcallocationlist-fordciformat0_1 can always be applied to the time-domain resource allocation of the corresponding PUSCH transmission (e.g., DG, CG type 2, and / or retransmission of CG) scheduled (and / or activated) by DCI format 0_1, regardless of whether other tables are configured (e.g., the PUSCH-TimeDomainResourceAllocationList in a UE-specific RRC message (e.g., PUSCH-Config), the pusch-TimeDomainAllocationList provided in a common RRC message (e.g., pusch-ConfigCommon), the PUSCH-TimeDomainRe-sourceAllocationList-ForDCIformat0_2 in a UE-specific RRC message (e.g., PUSCH-Config)).

[0192] If the UE 102 detects DCI format 0_2 for scheduling the PUSCH (and / or activating configured grant type 2) (e.g., in any common search space associated with CORESET 0, in any common search space not associated with CORESET 0, and / or in a UE-specific search space) and PUSCH-TimeDomainRe-sourceAllocationList-ForDCIformat0_2 is configured, then PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2 can always be applied to the time-domain resource allocation of the corresponding PUSCH transmission (e.g., DG, CG type 2, and / or retransmission of CG) scheduled (and / or activated) by DCI format 0_2, regardless of whether other tables are configured (e.g., PUSCH-TimeDomainResourceAllocationList in a UE-specific RRC message (e.g., PUSCH-Config), pusch-TimeDomainAllocationList provided in a common RRC message (e.g., pusch-ConfigCommon), PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1 in a UE-specific RRC message (e.g., PUSCH-Config)). If the UE 102 detects DCI format 0_0 for scheduling the PUSCH (and / or activating configured grant type 2) (e.g., in any common search space associated with CORESET 0, in any common search space not associated with CORESET 0, and / or in a UE-specific search space) and PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1 and / or PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2 are configured, then PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1 and / or PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2 may not be applied to the time-domain resource allocation of the corresponding PUSCH transmission (e.g., DG, CG type 2, and / or retransmission of CG) scheduled (and / or activated) by DCI format 0_0.

[0193] If the UE 102 detects DCI format 0_0 for scheduling the PUSCH (and / or activating configured grant type 2) (e.g., in any common search space associated with CORESET 0, in any common search space not associated with CORESET 0, and / or in a UE-specific search space) and a PUSCH-TimeDomainResourceAllocationList is configured in a UE-specific RRC message (e.g., PUSCH-Config), the PUSCH-TimeDomainResourceAllocationList in the UE-specific RRC message (e.g., PUSCH-Config) can be applied to the time-domain resource allocation of the corresponding PUSCH transmission (e.g., DG, CG type 2, and / or retransmission of CG) scheduled (and / or activated) by DCI format 0_0, regardless of whether a PUSCH-TimeDomainResourceAllocationList is configured in a common RRC message (e.g., PUSCH-ConfigCommon). If the UE 102 detects DCI format 0_1 for scheduling the PUSCH (and / or activating configured grant type 2) (e.g., in any common search space associated with CORESET 0, in any common search space not associated with CORESET 0, and / or in a UE-specific search space, for example) and PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1 is not configured, but a PUSCH-TimeDomainResourceAllocationList is configured in a UE-specific RRC message (e.g., PUSCH-Config), the PUSCH-TimeDomainResourceAllocationList in the UE-specific RRC message (e.g., PUSCH-Config) can be applied to the time-domain resource allocation of the corresponding PUSCH transmission (e.g., DG, CG type 2, and / or retransmission of CG) scheduled (and / or activated) by DCI format 0_1.If the UE 102 detects DCI format 0_2 for scheduling PUSCH (and / or type 2 of the activation configuration grant) (e.g., in any common search space associated with CORESET 0, in any common search space not associated with CORESET 0, and / or in a UE-specific search space, for example), and PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2 is not configured, but PUSCH-TimeDomainResourceAllocationList in the UE-specific RRC message (e.g., PUSCH-Config) is configured, then the PUSCH-TimeDomainResourceAllocationList in the UE-specific RRC message (e.g., PUSCH-Config) can be applied to the time-domain resource allocation of the corresponding PUSCH transmission (e.g., DG, CG type 2, and / or retransmission of CG) scheduled (and / or activated) by DCI format 0_2.

[0194] If the UE 102 detects a DCI format (e.g., DCI format 0_0, DCI format 0_1, or DCI format 0_2) for scheduling PUSCH (and / or type 2 of the activation configuration grant) in any common search space associated with CORESET 0, and there is no RRC-configured TDRA table, then the default table can be applied to the time-domain resource allocation of the corresponding PUSCH transmission (e.g., DG, CG type 2, and / or retransmission of CG) scheduled (and / or activated) by the DCI format. If the UE 102 detects a DCI format (e.g., DCI format 0_0, DCI format 0_1, or DCI format 0_2) for scheduling PUSCH (and / or type 2 of the activation configuration grant) in any common search space associated with CORESET 0, and only pusch-TimeDomainAllocationList in the common RRC message (e.g., pusch-ConfigCommon) is configured, then the pusch-TimeDomainAllocationList in the common RRC message (e.g., pusch-ConfigCommon) can be applied to the time-domain resource allocation of the corresponding PUSCH transmission (e.g., DG, CG type 2, and / or retransmission of CG) scheduled (and / or activated) by the DCI format.

[0195] If UE 102 detects a DCI format (e.g., DCI format 0_0, DCI format 0_1, or DCI format 0_2) for scheduling PUSCH (and / or grant type 2 for activation configuration) in any common search space and / or UE-specific search space not associated with CORESET 0, and there is no RRC-configured TDRA table, the default table can be applied to the time-domain resource allocation of the corresponding PUSCH transmission (e.g., DG, CG type 2, and / or retransmission of CG) scheduled (and / or activated) by the DCI format. If UE 102 detects a DCI format (e.g., DCI format 0_0, DCI format 0_1, or DCI format 0_2) for scheduling PUSCH (and / or grant type 2 for activation configuration) in any common search space and / or UE-specific search space not associated with CORESET 0, and only the pusch-TimeDomainAllocationList in the common RRC message (e.g., pusch-ConfigCommon) is configured, the pusch-TimeDomainAllocationList in the common RRC message (e.g., pusch-ConfigCommon) can be applied to the time-domain resource allocation of the corresponding PUSCH transmission (e.g., DG, CG type 2, and / or retransmission of CG) scheduled (and / or activated) by the DCI format.

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

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

[0198] The UE operation module 124 may provide the information 136 to the decoder 108. For example, the UE operation module 124 may notify the decoder 108 of the coding expected for the transmission from the gNB 160.

[0199] The UE operation module 124 may provide the information 142 to the encoder 150. The information 142 may include the 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.

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

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

[0202] The UE operation module 124 may provide information 140 to one or more transmitters 158. This information 140 may include instructions for the one or more transmitters 158. For example, the UE operation module 124 may indicate to the one or more transmitters 158 when to transmit signals to the gNB 160. For example, the one or more transmitters 158 may transmit during the UL subframe. The one or more transmitters 158 may up-convert the modulated signals 156 and transmit the modulated signals to one or more gNBs 160.

[0203] 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 operation 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.

[0204] 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 antennas 180a-n. For example, the receiver 178 may receive and down-convert the signals 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 antennas 180a-n. For example, the one or more transmitters 117 may up-convert and transmit one or more modulated signals 115.

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

[0206] Generally speaking, the gNB operation module 182 can enable the gNB 160 to communicate with one or more UEs 102. The gNB operation module 182 can include a gNB scheduling module 194. The gNB scheduling module 194 can perform operations for resource allocation for enhanced uplink transmission as described herein.

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

[0208] The gNB operation module 182 can provide information 186 to the decoder 166. For example, the gNB operation module 182 can notify the decoder 166 of the coding expected for transmissions from one or more UEs 102.

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

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

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

[0212] The gNB operation module 182 can provide information 192 to one or more transmitters 117. The information 192 can include instructions for one or more transmitters 117. For example, the gNB operation module 182 can indicate to one or more transmitters 117 when (when not) to transmit signals to one or more UEs 102. One or more transmitters 117 can up-convert the modulated signal 115 and transmit the modulated signal to one or more UEs 102.

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

[0214] It should also be noted that one or more of the elements or their components included in one or more eNBs 160 and one or more UEs 102 can be implemented in hardware. For example, one or more of these elements or their components can be implemented as chips, circuits, or hardware components, etc. It should also be noted that one or more of the functions or methods described herein can be implemented in hardware and / or executed using hardware. For example, one or more of the methods described herein can be implemented in a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc., and / or implemented using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI), or an integrated circuit, etc.

[0215] URLLC can coexist with other services (e.g., eMBB). Due to latency requirements, in some methods, URLLC may have the highest priority. Some examples of URLLC coexisting with other services are given herein (e.g., in one or more of the following figure descriptions).

[0216] Figure 2 is a diagram showing an example of a resource grid for the downlink. Figure 2 The shown resource grid can be used in some specific implementations of the systems and methods disclosed herein. More details about the resource grid are given in conjunction with Figure 1 given.

[0217] InFigure 2 In this case, a downlink subframe 269 may include two downlink time slots 283. N DL RB The downlink bandwidth configuration for the serving cell is expressed as a multiple of N RB sc where N RB sc is the size of a resource block 289 in the frequency domain, expressed as the number of subcarriers, and N DL 符号 is the number of OFDM symbols 287 in a downlink time slot 283. A resource block 289 may include a plurality of resource elements (REs) 291.

[0218] For the PCell, N DL RB is broadcast as part of the system information. For an SCell (including a licensed-assisted access (LAA) SCell), N UL RB is configured by an RRC message dedicated to the UE 102. For PDSCH mapping, the available REs 291 may be the REs 291 whose index l satisfies l >= I 数据，开始 and / or I 数据，结束 >= I in the subframe.

[0219] In the downlink, an OFDM access scheme with a cyclic prefix (CP) may be adopted, which may also be referred to as CP-OFDM. In the downlink, PDCCH, enhanced PDCCH (EPDCCH), PDSCH, etc. may be transmitted. A downlink radio frame may include multiple pairs of downlink resource blocks (RBs), 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 includes two downlink RBs that are consecutive in the time domain.

[0220] A downlink RB includes twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in the time domain. A region defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is referred to as a resource element (RE) and is uniquely identified by an index pair (k, l) in a time slot, where k and l are the indices in the frequency domain and the time domain, respectively. Although a downlink subframe in a single component carrier (CC) is discussed herein, a downlink subframe is defined for each CC, and the downlink subframes are substantially synchronized with each other between the CCs.

[0221] Figure 3 is a diagram illustrating an example of a resource grid for the uplink. Figure 3The resource grid shown can be used in some specific implementations of the systems and methods disclosed herein. In conjunction with Figure 1 more details about the resource grid are given.

[0222] In Figure 3 an uplink subframe 369 may include two uplink time slots 383. N UL RB is the uplink bandwidth configuration for the serving cell, expressed as a multiple of N RB sc where N RB sc is the size of a resource block 389 in the frequency domain, expressed as the number of subcarriers, and N UL 符号 is the number of SC-FDMA symbols 393 in an uplink time slot 383. A resource block 389 may include a plurality of resource elements (REs) 391.

[0223] For the PCell, N UL RB is broadcast as part of the system information. For an SCell (including an LAA SCell), N UL RB is configured via an RRC message dedicated to the UE 102.

[0224] In the uplink, in addition to CP-OFDM, a single-carrier frequency-division multiple access (SC-FDMA) access scheme may also be employed, which is also known as discrete Fourier transform spread OFDM (DFT-S-OFDM). In the uplink, PUCCH, PUSCH, PRACH, etc. may be transmitted. An uplink radio frame may include multiple pairs of uplink resource blocks. 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 includes two uplink RBs that are consecutive in the time domain.

[0225] An uplink RB may include twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM and / or DFT-S-OFDM symbols in the time domain. The region defined by one subcarrier in the frequency domain and one OFDM and / or DFT-S-OFDM symbol in the time domain is called an RE and is uniquely identified by an index pair (k, l) in a time slot, where k and l are the indices in the frequency domain and the time domain, respectively. Although an uplink subframe in a component carrier (CC) is discussed herein, an uplink subframe is defined for each CC.

[0226] Figure 4Shows an example of several parameters 401. Parameter #1 401a can be a basic parameter (e.g., a reference parameter). For example, the RE 495a of the basic parameter 401a can be defined to have a subcarrier spacing 405a of 15 kHz in the frequency domain and a length of 2048Ts + CP in the time domain (i.e., symbol length #1 403a) (e.g., 160Ts or 144Ts), where Ts represents the baseband sampling time unit defined as 1 / (15000*2048) seconds. For the i-th parameter, the subcarrier spacing 405 can be equal to 15*2 i and the effective OFDM symbol length 2048*2 -i *Ts. This can make the symbol length 2048*2 -i *Ts + CP length (e.g., 160*2 -i *Ts or 144*2 -i *Ts). In other words, the subcarrier spacing of the i+1-th parameter is twice that of the i-th parameter, and the symbol length of the i+1-th parameter is half that of the i-th parameter. Figure 4 Shows four parameters, but the system can support another number of parameters. In addition, the system does not have to support all of the 0-th parameter to the I-th parameter (i = 0, 1,..., I).

[0227] For example, the first UL transmission on the first SPS resource as described above can be performed only on parameter #1 (e.g., with a subcarrier spacing of 15 kHz). In some examples, the UE 102 can obtain (detect) parameter #1 based on the synchronization signal. Moreover, the UE 102 can receive a dedicated RRC signal including information (e.g., a handover command) configuring parameter #1. The dedicated RRC signal can be a UE-specific signal. In some examples, the first UL transmission on the first SPS resource can be performed on parameter #1, parameter #2 (subcarrier spacing of 30 kHz), and / or parameter #3 (subcarrier spacing of 60 kHz).

[0228] Moreover, the second UL transmission on the second SPS resource as described above can be performed only on parameter #3. In some examples, the UE 102 can receive system information (e.g., the Master Information Block (MIB) and / or System Information Block (SIB)) including information configuring parameter #2 and / or parameter #3.

[0229] Moreover, the UE 102 may receive a dedicated RRC signal including information (e.g., a handover command) of configuration parameter #2 and / or parameter #3. System information (e.g., MIB) may be transmitted on the BCH (Broadcast Channel) and / or the dedicated RRC signal. System information (e.g., SIB) may contain information on when to evaluate whether the UE 102 is allowed to access the cell and / or information when defining the scheduling of other system information. The system information (SIB) may contain radio resource configuration information shared by multiple UEs 102. For example, the dedicated RRC signal may include each of multiple parameter configurations (first parameter, second parameter, and / or third parameter) for each of the UL transmissions (e.g., each of the UL-SCH transmissions, each of the PUSCH transmissions). Moreover, the dedicated RRC signal may include each of multiple parameter configurations (first parameter, second parameter, and / or third parameter) for each of the DL transmissions (e.g., each of the PDCCH transmissions).

[0230] Figure 5 illustrates Figure 4 an example of the subframe structure of parameter 501 shown in. Considering that slot 283 includes N DL 符号 (or N UL 符号 ) = 7 symbols, the slot length of the (i + 1)-th parameter 501 is half of the slot length of the i-th parameter 501, and the number of slots 283 in a subframe (e.g., 1 ms) will eventually double. It should be noted that a radio frame may include 10 subframes, and the radio frame length may be equal to 10 ms.

[0231] Figure 6 illustrates examples of slot 683 and sub-slot 607. If the sub-slot 607 is not configured by a higher layer, the UE 102 and the eNB and / or gNB 160 may use only slot 683 as a scheduling unit. More specifically, a given transport block may be assigned to slot 683. If the sub-slot 607 is configured by a higher layer, the UE 102 and the eNB and / or gNB 160 may use the sub-slot 607 as well as slot 683. The sub-slot 607 may include one or more OFDM symbols. The maximum number of OFDM symbols constituting the sub-slot 607 may be N DL 符号 -1 (or N UL 符号 -1).

[0232] The sub-slot length may be configured by higher layer signaling. Alternatively, the sub-slot length may be indicated by a physical layer control channel (e.g., via DCI format).

[0233] Sub - slot 607 can start from any symbol within slot 683, unless it conflicts with the control channel. Based on the limitation of the starting position, there may be a limitation on the micro - slot length. For example, a sub - slot 607 with a length of N DL 符号 - 1 (or N UL 符号 - 1) can start from the second symbol in slot 683. The starting position of sub - slot 607 can be indicated by the physical layer control channel (e.g., via DCI format). Alternatively, the starting position of sub - slot 607 can be derived from the information of the physical layer control channel that schedules the data in sub - slot 607 (e.g., search space index, blind decoding candidate index, frequency and / or time resource index, PRB index, control channel element index, control channel element aggregation level, antenna port index, etc.).

[0234] In the case of configuring sub - slot 607, a given transport block can be allocated to slot 683, sub - slot 607, aggregated sub - slot 607, or aggregated sub - slot 607 and slot 683. This unit can also be a unit for HARQ - ACK bit generation.

[0235] Figure 7 An example of the scheduling timeline 709 is shown. For the normal DL scheduling timeline 709a, the DL control channel is mapped to the initial part of slot 783a. The DL control channel 711 schedules the DL shared channel 713a in the same slot 783a. The HARQ - ACK for the DL shared channel 713a (i.e., each HARQ - ACK indicating whether the transport block in each DL shared channel 713a is successfully detected) is reported via the UL control channel 715a in the subsequent slot 783b. In this case, a given slot 783 can contain either a DL transmission or a UL transmission.

[0236] For the normal UL scheduling timeline 709b, the DL control channel 711b is mapped to the initial part of slot 783c. The DL control channel 711b schedules the UL shared channel 717a in the subsequent slot 783d. For these cases, the associated timing (time offset) between the DL slot 783c and the UL slot 783d can be fixed or configured by higher - layer signaling. Alternatively, it can be indicated by the physical layer control channel (e.g., DL allocation DCI format, UL grant DCI format, or another DCI format, such as the UE common signaling DCI format that can be monitored in the common search space).

[0237] For the self - contained basic DL scheduling timeline 709c, the DL control channel 711c is mapped to the initial part of the time slot 783e. The DL control channel 711c schedules the DL shared channel 713b in the same time slot 783e. The HARQ - ACK for the DL shared channel 713b is reported in the UL control channel 715b, and these UL control channels are mapped to the end part of the time slot 783e.

[0238] For the self - contained basic UL scheduling timeline 709d, the DL control channel 711d is mapped to the initial part of the time slot 783f. The DL control channel 711d schedules the UL shared channel 717b in the same time slot 783f. For these cases, the time slot 783f may include a DL part and a UL part, and there may be a guard period between the DL transmission and the UL transmission.

[0239] The use of self - contained time slots may be based on the configuration of self - contained time slots. Alternatively, the use of self - contained time slots may be based on the configuration of sub - time slots. Still alternatively, the use of self - contained time slots may be based on the configuration of shortened physical channels (e.g., PDSCH, PUSCH, PUCCH, etc.).

[0240] Figure 8 An example of a DL control channel monitoring region is shown. One or more sets of PRBs may be configured for DL control channel monitoring. In other words, a control resource set is a set of PRBs in the frequency domain, within which the UE 102 attempts to blindly decode the downlink control information, where the PRBs may or may not be frequency - continuous. The UE 102 may have one or more control resource sets, and one DCI message may be located in one control resource set. In the frequency domain, a PRB is the resource unit size for the control channel (which may or may not include the demodulation reference signal (DMRS)). The DL shared channel may start at an OFDM symbol later than the symbol carrying the detected DL control channel. Alternatively, the DL shared channel may start at the last OFDM symbol carrying the detected DL control channel (or at a symbol earlier than the last OFDM symbol). In other words, at least dynamic reuse of at least a part of the resources in the control resource sets for data of the same or different UEs 102 is supported, at least in the frequency domain.

[0241] Figure 9 An example of a DL control channel including more than one control channel element is shown. When the control resource set spans multiple OFDM symbols, the control channel candidate may be mapped to multiple OFDM symbols or may be mapped to a single OFDM symbol. One DL control channel element may be mapped to the RE defined by a single PRB and a single OFDM symbol. If more than one DL control channel element is used for a single DL control channel transmission, DL control channel element aggregation may be performed.

[0242] The number of aggregated DL control channel elements is referred to as the DL control channel element aggregation level. The DL control channel element aggregation level can be 1 or a power of 2 up to an integer. gNB 160 may notify UE 102 which control channel candidates are mapped to each subset of OFDM symbols in a control resource set. If a DL control channel is mapped to a single OFDM symbol and does not span multiple OFDM symbols, DL control channel element aggregation is performed within one OFDM symbol, e.g., multiple DL control channel elements are aggregated within one OFDM symbol. Otherwise, DL control channel elements may be aggregated in different OFDM symbols.

[0243] Figure 10 An example of the UL control channel structure is shown. The UL control channel may be mapped on the REs defined by PRBs and time slots in the frequency domain and time domain respectively. This UL control channel may be referred to as the long format (or simply the first format). The UL control channel may be mapped on the REs on a limited number of OFDM symbols in the time domain. This may be referred to as the short format (or simply the second format). The UL control channel with the short format may be mapped on the REs within a single PRB. Alternatively, the UL control channel with the short format may be mapped on the REs within multiple PRBs. For example, an interleaved mapping may be applied, e.g., the UL control channel may be mapped to every Nth PRB (e.g., 5 or 10) within the system bandwidth.

[0244] Figure 11 FIG. is a block diagram showing a specific implementation of gNB 1160. gNB 1160 may include a high-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.

[0245] The high-layer processor 1123 may manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide high-layer parameters to the physical layer. The high-layer processor 1123 may obtain transport blocks from the physical layer. The high-layer processor 1123 may send and / or obtain high-layer messages such as RRC messages and MAC messages to and / or from the high layer of the UE. The high-layer processor 1123 may provide transport blocks to the PDSCH transmitter and provide transport parameters related to the transport blocks to the PDCCH transmitter.

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

[0247] Figure 12 is a block diagram showing a specific implementation of the UE 1202. The 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.

[0248] The higher layer processor 1223 can manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide 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 / or obtain higher layer messages such as RRC messages and MAC messages to and / or from the higher layer of the UE. The higher layer processor 1223 can provide transport blocks to the PUSCH transmitter and UCI to the PUCCH transmitter 1253.

[0249] The DL receiver 1243 can receive and demultiplex the multiplexed downlink physical channels and downlink physical signals via the receive antenna 1231. The PDCCH receiver 1245 can provide DCI to the higher layer processor 1223. The PDSCH receiver 1247 can provide the received transport block to the higher layer processor 1223.

[0250] It should be noted that the names of the physical channels described herein are examples. Other names may be used, such as "NR PDCCH, NR PDSCH, NR PUCCH, and NR PUSCH", "New Generation (G) PDCCH, G PDSCH, G PUCCH, and G PUSCH", etc.

[0251] Figure 13 shows various components that can be used for the UE 1302. In conjunction with Figure 13 The UE 1302 described in conjunction with Figure 1Implemented by the described UE 102. UE 1302 includes a processor 1303 that controls the operation of UE 1302. The processor 1303 may also be referred to as a central processing unit (CPU). A memory 1305 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device that can store information) provides instructions 1307a and data 1309a to the processor 1303. A portion of the memory 1305 may also include non-volatile random access memory (NVRAM). Instructions 1307b and data 1309b may also reside in the processor 1303. The instructions 1307b and / or data 1309b loaded into the processor 1303 may also include instructions 1307a and / or data 1309a from the memory 1305, which are loaded for the processor 1303 to execute or process. The instructions 1307b may be executed by the processor 1303 to implement the above method.

[0252] UE 1302 may also include a housing that houses one or more transmitters 1358 and one or more receivers 1320 to allow for the transmission and reception of data. The transmitter 1358 and the receiver 1320 may be combined into one or more transceivers 1318. One or more antennas 1322a-n are attached to the housing and electrically coupled to the transceivers 1318.

[0253] The various components of UE 1302 are coupled together by a bus system 1311 (which may include a power bus, a control signal bus, and a status signal bus in addition to the data bus). However, for clarity, the various buses are shown as the bus system 1311 in Figure 13 UE 1302 may also include a digital signal processor (DSP) 1313 for processing signals. UE 1302 may also include a communication interface 1315 that provides a user with access to the functions of UE 1302. Figure 13 The illustrated UE 1302 is a functional block diagram rather than a list of specific components.

[0254] Figure 14 Shows the various components that can be used for gNB 1460. In combination with Figure 14 The described gNB 1460 may be according to the combination with Figure 1Implemented by the described gNB 160. gNB 1460 includes a processor 1403 that controls the operation of gNB 1460. The processor 1403 may also be referred to as a central processing unit (CPU). A memory 1405 (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 1407a and data 1409a to the processor 1403. A portion of the memory 1405 may also include non-volatile random access memory (NVRAM). Instructions 1407b and data 1409b may also reside in the processor 1403. The instructions 1407b and / or data 1409b loaded into the processor 1403 may also include instructions 1407a and / or data 1409a from the memory 1405, which are loaded for the processor 1403 to execute or process. The instructions 1407b may be executed by the processor 1403 to implement the above method.

[0255] gNB 1460 may also include a housing that houses one or more transmitters 1417 and one or more receivers 1478 to allow for the transmission and reception of data. The transmitter 1417 and the receiver 1478 may be combined into one or more transceivers 1476. One or more antennas 1480a-n are attached to the housing and electrically coupled to the transceiver 1476.

[0256] The various components of gNB 1460 are coupled together by a bus system 1411 (which may include a power bus, a control signal bus, and a status signal bus in addition to the data bus). However, for clarity, the various buses are shown as the bus system 1411 in Figure 14 gNB 1460 may also include a digital signal processor (DSP) 1413 for processing signals. gNB 1460 may also include a communication interface 1415 that provides the function of allowing users to access gNB 1460. Figure 14 The gNB 1460 shown is a functional block diagram rather than a list of specific components.

[0257] Figure 15 is a block diagram showing a specific implementation of a UE 1502 in which a system and method for resource allocation for enhanced uplink transmission can be implemented. The UE 1502 includes a transmitting device 1558, a receiving device 1520, and a control device 1524. The transmitting device 1558, the receiving device 1520, and the control device 1524 may be configured to perform one or more of the functions described above Figure 1 described. Figure 13 Shows Figure 15 A specific device structure example of Figure 1One or more of the functions. For example, the DSP can be implemented by software.

[0258] Figure 16 FIG. 1660 is a block diagram showing a specific implementation of the gNB 1660 that can implement resource allocation for enhanced uplink transmission. The gNB 1660 includes a transmitting device 1623, a receiving device 1678, and a control device 1682. The transmitting device 1623, the receiving device 1678, and the control device 1682 can be configured to perform one or more of the functions described above. Figure 1 One or more of the functions described above. Figure 14 Shows Figure 16 An example of the specific device structure. Various other structures can be implemented to achieve one or more of the functions. For example, the DSP can be implemented by software. Figure 1 One or more of the functions. For example, the DSP can be implemented by software.

[0259] Figure 17 FIG. 1700 is a flowchart showing a method 1700 performed by a user equipment (UE) 102. The UE 102 can receive signaling that includes a configuration 1702 for a configured grant physical uplink shared channel (PUSCH) or a grant-based PUSCH. The UE 102 can determine whether to use multi-segment transmission and micro-slot repetition 1704 for the configured grant PUSCH or the grant-based PUSCH. The UE 102 can transmit multi-segment transmission and micro-slot repetition 1706 for the configured grant PUSCH or the grant-based PUSCH.

[0260] In one method, a grant configuration for one uplink (UL) grant for the grant-based PUSCH and a configured grant configuration for the configured grant PUSCH are used to support one or more actual PUSCH repetitions in one time slot, or two or more actual PUSCH repetitions across time slot boundaries in continuously available time slots.

[0261] In another method, a grant configuration for one UL grant for the grant-based PUSCH and a configured grant configuration for the configured grant PUSCH are used to support one or more PUSCH repetitions in one time slot, or two or more PUSCH repetitions across time slot boundaries in continuously available time slots.

[0262] Figure 18is a flowchart showing a method 1800 performed by a base station (gNB) 160. The gNB 160 may transmit signaling to a user equipment (UE) 102, the signaling including a configuration 1802 for a configured grant physical uplink shared channel (PUSCH) or a grant-based PUSCH. The gNB 160 may determine whether to use multi-segment transmission and micro-slot repetition for the configured grant PUSCH or for the grant-based PUSCH 1804. The gNB 160 may receive multi-segment transmission and micro-slot repetition for the configured grant PUSCH or for the grant-based PUSCH 1806.

[0263] The term "computer-readable medium" refers to any available medium that can be accessed by a computer or a processor. As used herein, the term "computer-readable medium" may represent a non-transitory and tangible computer-readable medium and / or a processor-readable medium. By way of example and not limitation, a computer-readable medium or a processor-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, 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 a processor. As used herein, disk and optical disk include compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk, and optical disk, where disks generally reproduce data magnetically, while optical disks use lasers to reproduce data optically.

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

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

[0266] It should be understood that the claims are not limited to the exact configurations and components shown above. Without departing from the scope of the claims, various modifications, changes, and alterations may be made to the arrangements, operations, and details of the systems, methods, and apparatuses described herein.

[0267] The program running on the gNB 160 or the UE 102 according to the system and method is a program that controls a CPU or the like in a manner to implement the functions according to the system and method (a program for computer operation). Then, the information processed in these devices is temporarily stored in the RAM while being processed. Subsequently, this information is stored in various ROMs or HDDs and read by the CPU whenever needed for modification or writing. As a recording medium on which the program is stored, any of a semiconductor (e.g., ROM, non-volatile memory card, etc.), an optical storage medium (e.g., DVD, MO, MD, CD, BD, etc.), a magnetic storage medium (e.g., magnetic tape, floppy disk, etc.), etc. is possible. Additionally, in some cases, the functions according to the system and method described above are implemented by running the loaded program, and additionally, the functions according to the system and method are implemented based on instructions from the program in combination with an operating system or other application programs.

[0268] Furthermore, in the case where the program is commercially available, the program stored on a portable recording medium can be distributed, or the program can be transmitted to a server computer connected via a network such as the Internet. In this case, a storage device in the server computer is also included. Additionally, some or all of the gNB 160 and the UE 102 according to the above system and method can be implemented as an LSI, a typical integrated circuit. Each functional block of the gNB 160 and the UE 102 can be individually built into a chip, and some or all of the functional blocks can be integrated into a chip. Furthermore, the technology of the integrated circuit is not limited to LSI, and the integrated circuit for the functional block can be implemented using an application-specific circuit or a general-purpose processor. Additionally, if, with the continuous progress of semiconductor technology, an integrated circuit technology alternative to LSI emerges, then the integrated circuit applying this technology can also be used.

[0269] Moreover, each functional block or various features of the base station device and the terminal device used in each of the above specific embodiments can be implemented or executed by a circuit (usually one integrated circuit or multiple integrated circuits). The circuit designed to execute the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific or general-purpose integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, or discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller, or a state machine. The general-purpose processor or each of the above circuits can be configured by a digital circuit or can be configured by an analog circuit. Additionally, when, due to the progress of semiconductor technology, a technology for manufacturing an integrated circuit that replaces the current integrated circuit emerges, the integrated circuit produced by this technology can also be used.

[0270] As used herein, the term "and / or" shall be interpreted to mean one or more items. For example, the phrase "A, B, and / or C" shall be interpreted to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "at least one" shall be interpreted to mean one or more items. For example, the phrase "at least one of A, B, and C" or the phrase "at least one of A, B, or C" shall be interpreted to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C. As used herein, the phrase "one or more" shall be understood to refer to one or more items. For example, the phrase "one or more of A, B, and C" or the phrase "one or more of A, B, or C" shall be interpreted to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B), or all of A, B, and C.

[0271] <Summary of the Invention>

[0272] In one example, a user equipment (UE) includes: a receiving circuit configured to receive downlink control information (DCI), wherein the DCI includes a time domain resource allocation field; and a processor configured to determine resource allocation based on the DCI having the time domain resource allocation field.

[0273] In one example, a base station (gNB) includes: a processor configured to determine resource allocation for a user equipment (UE); and a transmission circuit configured to transmit downlink control information (DCI) to the UE, wherein the DCI includes a time domain resource allocation field indicating the resource allocation.

[0274] In one example, a method performed by a user equipment (UE) includes: receiving signaling including downlink control information (DCI), wherein the DCI includes a time domain resource allocation field; and determining resource allocation based on the DCI having the time domain resource allocation field.

[0275] In one example, a method performed by a base station (gNB) includes: determining resource allocation for a user equipment (UE); and transmitting downlink control information (DCI) to the UE, wherein the DCI includes a time domain resource allocation field indicating the resource allocation.

[0276] In one example, a user equipment (UE) includes: a receiving circuit configured to receive a radio resource control (RRC) message including first parameters for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used to define a time-domain allocation for physical uplink shared channel (PUSCH) transmission, wherein a starting symbol and a length are jointly presented in the first allocation table, and the starting symbol and the length are respectively presented in the second allocation table, the receiving circuit being configured to detect, in a UE-specific search space, a first downlink control information (DCI) format or a second DCI format including first information for indicating a row index of the first allocation table or the second allocation table, the DCI format being used to schedule the PUSCH; a transmitting circuit configured to perform PUSCH transmission based on either the first allocation table or the second allocation table upon detecting the first DCI format or the second DCI format, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on the DCI format.

[0277] In one example, for the UE, it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on a value of second information included in the DCI format, the second information being a new data indicator (NDI).

[0278] In one example, for the UE, it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on a radio network temporary identifier (RNTI) used for scrambling a cyclic redundancy check (CRC) of the DCI format.

[0279] In one example, a base station device includes: a transmitting circuit configured to transmit a radio resource control (RRC) message including first parameters for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used to define a time-domain allocation for physical uplink shared channel (PUSCH) transmission, wherein a starting symbol and a length are jointly presented in the first allocation table, and the starting symbol and the length are respectively presented in the second allocation table, the transmitting circuit being configured to transmit, in a UE-specific search space, a first downlink control information (DCI) format or a second DCI format including first information for indicating a row index of the first allocation table or the second allocation table, the DCI format being used to schedule the PUSCH; a receiving circuit configured to receive PUSCH transmission based on either the first allocation table or the second allocation table, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on the DCI format.

[0280] In one example, the base station device, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on the value of the second information included in the DCI format, and the second information is a new data indicator (NDI).

[0281] In one example, the base station device, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on the radio network temporary identifier (RNTI) used to scramble the cyclic redundancy check (CRC) of the DCI format.

[0282] In one example, a communication method for a user equipment (UE), the communication method comprising: receiving a radio resource control (RRC) message including first parameters for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used to define a time-domain allocation for physical uplink shared channel (PUSCH) transmission, wherein a starting symbol and a length are jointly presented in the first allocation table, and the starting symbol and the length are respectively presented in the second allocation table; detecting, in a UE-specific search space, a first downlink control information (DCI) format or a second DCI format including first information for indicating a row index of the first allocation table or the second allocation table, the DCI format being used to schedule the PUSCH; performing PUSCH transmission based on either the first allocation table or the second allocation table based on the detected DCI format, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on the DCI format.

[0283] In one example, the communication method, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on the value of the second information included in the DCI format, and the second information is a new data indicator (NDI).

[0284] In one example, the communication method, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on the radio network temporary identifier (RNTI) used to scramble the cyclic redundancy check (CRC) of the DCI format.

[0285] In one example, a communication method of a base station device, the communication method comprising: transmitting a radio resource control (RRC) message including first parameters for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used to define a time domain allocation for physical uplink shared channel (PUSCH) transmission, wherein a starting symbol and a length are jointly presented in the first allocation table, and the starting symbol and the length are respectively presented in the second allocation table; transmitting a first downlink control information (DCI) format or a second DCI format including first information for indicating a row index of the first allocation table or the second allocation table in a UE-specific search space, the DCI format being used to schedule PUSCH; receiving a PUSCH transmission based on either the first allocation table or the second allocation table, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on the DCI format.

[0286] In one example, the communication method, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on a value of second information included in the DCI format, the second information being a new data indicator (NDI).

[0287] In one example, the communication method, wherein it is determined whether the first allocation table or the second allocation table is used for PUSCH transmission based on a radio network temporary identifier (RNTI) used for scrambling a cyclic redundancy check (CRC) of the DCI format.

[0288] <Cross-reference>

[0289] This non-provisional application claims priority under 35 U.S.C. § 119 to Provisional Application No. 62 / 931,990, filed on November 7, 2019, the entire content of which is hereby incorporated by reference.

Claims

1. A user equipment (UE), the UE comprises: a receiving circuit configured to receive radio resource control (RRC) parameters for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used to define a time-domain allocation for physical uplink shared channel (PUSCH) transmission, wherein a starting symbol and a length are indicated as a single parameter in the first allocation table, and the starting symbol and the length are indicated as separate parameters in the second allocation table, the receiving circuit is configured to detect, in a UE-specific search space, a downlink control information (DCI) format including first information for indicating a row index of the first allocation table or the second allocation table, the DCI format being used to schedule the PUSCH transmission, and a transmitting circuit configured to perform the PUSCH transmission based on either the first allocation table or the second allocation table upon detecting the DCI format, wherein the allocation table for the PUSCH transmission is determined based on the DCI format, the DCI format is DCI format 0_2, and DCI format 0_2 is one of a plurality of DCI formats, and in response to determining that the DCI format 0_2 is detected among the plurality of DCI formats, and in response to determining that the RRC parameters include an information element for the DCI format 0_2, the determination of the second allocation table as the allocation table for the PUSCH transmission is made based on the information element, regardless of whether the RRC parameters include a plurality of other parameters for configuring the allocation table for PUSCH transmission.

2. A base station apparatus, the base station apparatus comprises: a transmitting circuit configured to transmit radio resource control (RRC) parameters for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used to define a time-domain allocation for physical uplink shared channel (PUSCH) transmission, wherein a starting symbol and a length are indicated as a single parameter in the first allocation table, and the starting symbol and the length are indicated as separate parameters in the second allocation table, the transmitting circuit is configured to transmit, in a UE-specific search space, a downlink control information (DCI) format including first information for indicating a row index of the first allocation table or the second allocation table, the DCI format being used to schedule the PUSCH transmission, and a receiving circuit configured to receive the PUSCH transmission based on either the first allocation table or the second allocation table, wherein the allocation table for the PUSCH transmission is determined based on the DCI format, the DCI format is DCI format 0_2, and DCI format 0_2 is one of a plurality of DCI formats, and In response to determining that the DCI format 0_2 is transmitted among the plurality of DCI formats, and in response to determining that the RRC parameter includes an information element for the DCI format 0_2, the determination of the second allocation table as the allocation table for the PUSCH transmission is made based on the information element, regardless of whether the RRC parameter includes a plurality of other parameters for configuring the allocation table for the PUSCH transmission.

3. A communication method for a user equipment UE, the communication method comprising: receiving radio resource control RRC parameters for configuring a first allocation table and a second allocation table, each of the first allocation table and the second allocation table being used to define a time-domain allocation for physical uplink shared channel PUSCH transmission, wherein a starting symbol and a length are indicated as a single parameter in the first allocation table, and a starting symbol and a length are indicated as separate parameters in the second allocation table; detecting, in a UE-specific search space, a downlink control information DCI format including first information for indicating a row index of the first allocation table or the second allocation table, the DCI format being used to schedule the PUSCH transmission; and performing the PUSCH transmission based on either the first allocation table or the second allocation table based on the detected DCI format, wherein the allocation table for the PUSCH transmission is determined based on the DCI format, the DCI format is DCI format 0_2, the DCI format 0_2 being one of the plurality of DCI formats, and in response to determining that the DCI format 0_2 is detected among the plurality of DCI formats, and in response to determining that the RRC parameter includes an information element for the DCI format 0_2, the determination of the second allocation table as the allocation table for the PUSCH transmission is made based on the information element, regardless of whether the RRC parameter includes a plurality of other parameters for configuring the allocation table for the PUSCH transmission.

Images