Uplink signal transmission method and apparatus

Abstract

The application discloses an uplink signal sending method and device. The method comprises the following steps: receiving downlink control information; and performing uplink signal sending action according to the downlink control information and / or time domain characteristics of physical resources of the uplink signal. The application can improve the flexibility of the system and enhance the transmission efficiency.

Description

[0001] This application is a divisional application of Chinese invention patent No. 201910792505.9, filed on August 26, 2019, entitled "Uplink Signal Transmission Method and Apparatus". Technical Field

[0002] This invention relates to the field of mobile communication technology, and more specifically, to an uplink signal transmission method and apparatus, and a method and device for transmitting / receiving an uplink data channel, a control channel, a random access channel, and a downlink control channel. Background Technology

[0003] With the rapid development of the information industry, especially the growing demand from mobile internet and the Internet of Things (IoT), unprecedented challenges are being brought to future mobile communication technologies. According to the International Telecommunication Union (ITU) report ITU-RM. [IMT.BEYOND2020.TRAFFIC], it is projected that by 2020, mobile traffic will increase nearly 1000 times compared to 2010 (the 4G era), and the number of user-defined devices (UEs) will exceed 17 billion. As massive numbers of IoT devices gradually penetrate mobile communication networks, the number of connected devices will be even more staggering. To address these unprecedented challenges, the communications industry and academia have launched extensive research into fifth-generation mobile communication technology (5G) with a focus on 2020. Within 3GPP, the first phase of 5G work has been largely completed, and the second phase has already begun.

[0004] To meet the demands of massive service volumes, 5G systems are expected to operate in low-frequency bands, up to around 100GHz, including both licensed and unlicensed bands. Unlicensed bands primarily consider the 5GHz and 60GHz bands. We refer to 5G systems operating in unlicensed bands as NR-U systems, which can include: scenarios operating independently on unlicensed bands; and scenarios operating with licensed bands via dual connectivity (DC), such as... Figure 1As shown; and scenarios where licensed frequency bands operate via carrier aggregation (CA). In the 5GHz band, 802.11 series Wireless Fidelity (WiFi) systems, radar, and LTE Licensed Carrier Assisted Access (LAA) systems have been deployed. All of these follow the Listen before Talk (LBT) mechanism for channel access, meaning that the wireless channel must be detected before transmitting a signal, and the wireless channel can only be used to transmit a signal if it is detected to be idle.

[0005] In the existing system, there are two methods to support UE uplink transmission. One is based on real-time base station scheduling, which we call SUL (scheduled based UL grant). Before transmitting a signal, the UE needs to receive an uplink scheduling instruction (UL grant) from the base station. The UL grant contains information such as the time-frequency resources for the UE to transmit PUSCH. The UE transmits PUSCH on the resources indicated by the UL grant. On unlicensed frequency bands, the base station needs to perform LBT (Local Time-Based Transmission) before sending the UL grant, and the UE needs to perform LBT before the uplink subframe indicated by the UL grant. Only after both LBTs are successful can the PUSCH scheduled by the UL grant be transmitted. The other method is semi-static base station configuration of time-frequency resources, which we call GUL (UL transmission with configured grant). When the UE has data to transmit, no base station scheduling is required; the UE can attempt to transmit on these resources. If there is no data, transmission is not necessary. On unlicensed frequency bands, the UE needs to perform LBT before uplink transmission; if successful, it can transmit PUSCH on the configured resources. In a GUL-transmitted PUSCH, the UE can transmit both uplink data and uplink control information (UCI), such as symbols indicating the start and end of the PUSCH, mixed automatic repeat request (HARQ) information (e.g., NDI, RV, HARQ_ID), and UE identity information (UE ID). In 5G systems, both uplink transmission methods can be considered for transmissions on both licensed and unlicensed frequency bands.

[0006] To support GUL-based retransmission, the base station can explicitly indicate the HARQ-ACK information for the PUSCH of the GUL transmission via specific downlink control signaling (DCI). The UE can then determine whether to perform a retransmission or a new transmission based on the received HARQ-ACK information. On unlicensed frequency bands, the UE can also adjust the contention window size (CWS) of the LBT based on the received HARQ-ACK information. How the UE determines the validity of the received HARQ-ACK information, how it determines CWS adjustments based on this HARQ-ACK information, and how it determines GUL transmission behavior based on this HARQ-ACK information to improve LBT accuracy and GUL transmission efficiency are all issues that urgently require solutions.

[0007] Furthermore, when a UE is semi-statically configured to receive K repeated downlink physical channels, such as PDSCH, or transmit K repeated uplink physical channels, such as PUSCH, corresponding solutions are needed to determine how to receive K PDSCH or transmit K PUSCH based on the resource information configured semi-statically by the base station and the resource information dynamically indicated by the base station, as well as to reduce the impact of LBT on transmission efficiency in unlicensed frequency bands.

[0008] LBT mechanisms can be divided into two types. One is called Category 1 LBT, commonly known as Category 4 LBT (TS37.213), which randomly generates a backoff factor X based on the Carrier Sense Time Slot (CWS). If all X Carrier Sense Time Slots (CCA slots) are idle, the signal can be transmitted. Category 1 LBT is divided into four LBT priority classes, each corresponding to a different Quality Criterion Indicator (QCI). Different LBT priority classes have different CWS sizes (i.e., different sets of CW values), different backoff time units (defer period, which equals 16 + 9 * n microseconds, where n is an integer greater than or equal to 1), and different maximum channel occupancy time (MCOT), as shown in Table 1 below. The other type is called Category 2 LBT (TS 37.213), where the transmitter only needs to perform a 25µs (microsecond) Clear Channel Assessment (CCA) check before the standard-defined start of signal transmission. If the channel is idle, the signal can be transmitted.

[0009]

[0010] Table 1 Value set CWS of conflict window CW corresponding to LBT priority classification, maximum occupancy time MCOT, and backoff parameter n SUMMARY OF THE INVENTION

[0011] The present invention is provided to at least solve the above problems and at least provide the following advantages.

[0012] According to one aspect of the present invention, there is provided an uplink signal transmission method, including: receiving downlink control information; and performing an uplink signal transmission action according to the downlink control information and / or the time-domain characteristics of the physical resources of the uplink signal.

[0013] Wherein, the downlink control information includes hybrid automatic repeat request HARQ-ACK feedback information, and the HARQ-ACK feedback information is the HARQ-ACK information of the PUSCH of one or more HARQ processes of the UE carried by the base station through specific DCI. Wherein, determining the uplink signal transmission action includes: determining to stop transmitting the uplink signal, or continue to transmit the uplink signal, or retransmit the uplink signal

[0014] Wherein, for the configured grant uplink transmission GUL PUSCH with K times of repeated transmission, performing the uplink signal transmission action according to the downlink control information and / or the time-domain characteristics of the physical resources of the uplink signal includes at least one of the following: If the UE receives the HARQ-ACK feedback information at time m, where the HARQ-ACK corresponding to the GUL PUSCH of the HARQ process is ACK, and the GUL PUSCH of the HARQ process has been transmitted at least Ka times before time m - m_dfi, where Ka < K, then the UE stops transmitting the remaining repeated GUL PUSCH transmissions, where m_dfi is a predefined minimum processing delay; If the UE receives the HARQ-ACK feedback information at time m, where the HARQ-ACK corresponding to the HARQ process is NACK, and the UE has not completed K times of repeated transmission at time m, then the UE continues to transmit the repeated GUL PUSCH until it has transmitted K times or until it receives ACK; If the UE receives the HARQ-ACK feedback information at time m, where the HARQ-ACK corresponding to the HARQ process is NACK, and the UE has transmitted K times of repetition of the GUL PUSCH corresponding to the HARQ process at time m, then the UE attempts to retransmit the GUL PUSCH on the configured GUL resources.

[0015] Specifically, the uplink signal transmission action based on the time-domain characteristics of the physical resources of the downlink control information and / or uplink signal includes: determining the starting point of GUL PUSCH transmission based on the time-domain characteristics of the physical resources of the downlink control information and the uplink data channel signal PUSCH; transmitting GUL PUSCH based on the determined starting point; and / or determining the starting point of GUL PUCCH transmission based on the time-domain characteristics of the physical resources of the downlink control information and the uplink data channel signal PUCCH; transmitting GUL PUCCH based on the determined starting point.

[0016] The downlink control information includes information for determining uplink and / or downlink and / or flexible time slots / symbols, or information indicating channel occupancy time (COT). Based on the downlink control information and the time-domain characteristics of the physical resources of the uplink data channel signal PUSCH, the starting point for GUL PUSCH transmission is determined, including at least one of the following methods: determining a time slot / symbol that makes the GUL resources corresponding to K repetitive transmissions of GUL PUSCH temporally continuous as the starting point; determining a time slot / symbol that makes the GUL resources corresponding to K repetitive transmissions of GUL PUSCH belong to the same GUL resource period as the starting point; determining a time slot / symbol that makes the GUL resources corresponding to K repetitive transmissions of GUL PUSCH belong to the same COT as the starting point.

[0017] Specifically, the uplink signal transmission action based on the time-domain characteristics of the physical resources of the downlink control information and / or uplink signal includes: determining the number of GUL PUSCH transmissions based on the time-domain characteristics of the physical resources of the downlink control information and the uplink data channel signal PUSCH; transmitting the GUL PUSCH based on the determined number of transmissions; and / or determining the number of GUL PUCCH transmissions based on the time-domain characteristics of the physical resources of the downlink control information and the uplink data channel signal PUCCH; transmitting the GUL PUCCH based on the determined number of transmissions.

[0018] Among them, the downlink control information includes information for determining uplink and / or downlink and / or flexible time slots / symbols, or information indicating the channel occupancy time COT. According to the downlink control information and the time-domain characteristics of the physical resources of the uplink data channel signal PUSCH, the number of GUL PUSCH transmissions is determined, including at least one of the following methods: If the GUL resources corresponding to the PUSCH with K times of repeated transmissions are discontinuous in time, the UE only sends the PUSCH K_c times on the continuous GUL resources and abandons the K - K_c times of GUL PUSCH transmissions corresponding to the discontinuous GUL resources, where K_c < K; If the GUL resources corresponding to the GUL PUSCH with K times of repeated transmissions span the GUL resource configuration period, the UE only sends the PUSCH K_c times on the GUL resources within one period and abandons the K - K_c times of GUL PUSCH transmissions corresponding to the GUL resources after the one period, where K_c < K; If some of the GUL resources corresponding to the K times of GUL PUSCH transmissions are outside a channel occupancy time COT, the UE only sends the GUL PUSCH K_c times on the GUL resources within the same COT and abandons the K - K_c times of GUL PUSCH transmissions corresponding to the GUL resources outside the COT, where K_c < K; If some of the GUL resources corresponding to the K times of GUL PUSCH transmissions are outside a channel occupancy time COT, the UE performs a first type of channel access procedure and then sends K_d times of GUL PUSCH transmissions, where K_d is not more than K and makes the K_d times of PUSCH transmissions not exceed the COT length obtained by the UE through the first type of channel access procedure; If some of the GUL resources corresponding to the K times of GUL PUSCH transmissions are outside a channel occupancy time COT, the UE determines whether to stop sending the K times of GUL PUSCH transmissions at the end of the COT or continue to send the K times of GUL PUSCH transmissions according to the indication of the base station.

[0019] Among them, K_c ≥ a predefined threshold; the threshold is predefined or configured when the base station configures GUL; or, the threshold corresponds to the service type carried by the PUSCH, and / or the logical channel, and / or the redundancy version RV.

[0020] Among them, the downlink control information includes HARQ-ACK feedback information, and the HARQ-ACK feedback information is the HARQ-ACK information of the PUSCH of one or more HARQ processes of the UE carried by the base station through specific DCI. According to the time-domain characteristics of the physical resources of the downlink control information and / or the uplink signal, the uplink signal transmission action includes: determining the contention window length CWS of the channel access process before the uplink data channel signal transmission according to the downlink control information and the time-domain characteristics of the physical resources of the uplink data channel signal PUSCH, and transmitting the uplink signal after channel access according to the CWS.

[0021] Among them, determining the contention window length CWS of the channel access process before the uplink signal transmission includes determining the CWS according to the HARQ-ACK information. Among them, the time difference between the time m when the UE receives the HARQ-ACK information and the time n when the UE transmits the PUSCH corresponding to the HARQ-ACK information is not less than m_dfi_0, where m_dfi_0 is a predefined minimum processing delay; m_dfi_0 is in units of time slots or in units of OFDM symbols.

[0022] Among them, for the GUL PUSCH configured for K times of repeated transmission, determining the contention window length CWS of the channel access process before the uplink signal transmission includes at least one of the following: The UE determines the CWS according to the HARQ-ACK information. Among them, the UE receives the HARQ-ACK feedback information at time m, the HARQ-ACK corresponding to the HARQ process is ACK, and the PUSCH of the HARQ process has been transmitted at least K_a times before time m - m_dfi_0, where K_a < K; The UE determines the CWS according to the HARQ-ACK information. Among them, the HARQ-CK information that meets the following conditions is not used for the determination of CWS: For the GUL PUSCH configured for K times of repeated transmission, if the UE receives the HARQ-ACK feedback information at time m, where the HARQ-ACK corresponding to the HARQ process is NACK, and the number of transmissions of the PUSCH of the HARQ process before time m - m_dfi_0 < K_b. Among them, m_dfi_0 is a predefined minimum processing delay; m_dfi_0 is in units of time slots or in units of OFDM symbols.

[0023] Wherein, the PUSCH is the first PUSCH of the most recent uplink transmission that satisfies the time difference, or, the PUSCH is all the PUSCHs that satisfy the time difference in the first time slot of the most recent uplink transmission that satisfy the time difference, or, the PUSCH is the PUSCH that satisfies the time difference and is the earliest in time in the first time slot of the most recent uplink transmission that satisfies the time difference.

[0024] The downlink control information includes information for determining uplink and / or downlink and / or flexible time slots / symbols, or information indicating channel occupancy time (COT). When the uplink signal includes a semi-statically configured uplink signal, the uplink signal transmission action is performed based on the downlink control information and the time-domain characteristics of the physical resources of the uplink signal, including at least one of the following methods: For semi-statically configured uplink signal transmission, if the uplink signal transmission resource selected by the UE is a semi-statically configured uplink and / or flexible time slot / symbol, and the UE has not received downlink control information indicating that part or all of the resources of the uplink signal are downlink time slots / symbols, then the UE attempts to transmit the uplink signal on the selected transmission resource; For semi-statically configured uplink signal transmission, if the uplink signal transmission resource selected by the UE is a semi-statically configured uplink and / or flexible time slot / symbol, and the UE has not received information indicating that part or all of the resources are downlink and / or flexible time slots. If the UE receives downlink control information for a symbol, it will attempt to transmit the uplink signal on the selected transmission resource; otherwise, it will not transmit the uplink signal. For semi-static uplink signal transmission, if the uplink signal transmission resource selected by the UE is a semi-static uplink and / or flexible time slot / symbol, and part or all of the uplink signal resource is located between two adjacent Time Slot Format Indication (SFI), and the UE has not received downlink control information indicating part or all of the uplink signal resource for uplink / downlink / flexible time slot / symbol, then the UE may attempt to transmit the uplink signal on the uplink signal resource before the next possible SFI time slot. If an SFI is received in the SFI time slot, the UE will determine whether to continue transmitting the uplink signal or stop based on the SFI indication.

[0025] The uplink signals include PUSCH, PUCCH, and PRACH. At least two of PUSCH, PUCCH, and PRACH have different uplink signal transmission actions.

[0026] The downlink control information indicates downlink time slots / symbols, uplink time slots / symbols, flexible time slots / symbols, and special flexible time slots / symbols.

[0027] The downlink control information is transmitted in period K0, and the downlink control information indicates downlink time slots / symbols, uplink time slots / symbols, and flexible time slots / symbols for X time slots; within a certain downlink control information transmission period, the last K0-X time slots are special flexible time slots / symbols.

[0028] Specifically, in the special flexible time slot / symbol indicated by the downlink control information, the UE attempts to transmit a predefined semi-static configuration uplink signal; and / or, in the flexible time slot / symbol indicated by the downlink control information, the UE does not transmit the predefined semi-static configuration uplink signal.

[0029] In the contention window length (CWS) adjustment during the channel access process, for all HARQ-ACKs available for CWS adjustment, if the percentage of ACK exceeds a predefined threshold, or the percentage of NACK is lower than a predefined threshold, then CWS is reset; otherwise, CWS is increased to the next larger available value.

[0030] The downlink control information includes information for determining the time resource patterns of DMRS and / or PUSCH in M ​​consecutively scheduled PUSCH slots.

[0031] The downlink control information includes information for determining the timing resources of the Sounding Reference Signal (SRS), including at least one of the following: information indicating the time slot offset between the SRS and the DCI that triggered the SRS, or information indicating that the SRS is located in the same time slot as the PUSCH and / or PUCCH scheduled by the DCI that triggered the SRS.

[0032] According to one aspect of the present invention, an uplink signal transmitting device is also provided, comprising: a receiver for receiving downlink control information; and a transmitter for transmitting uplink signals based on the downlink control information and / or the time-domain characteristics of the physical resources of the uplink signal. Attached Figure Description

[0033] These and / or other aspects and advantages of the invention will become clear and more readily understood from the following description of the embodiments, taken in conjunction with the accompanying drawings, wherein:

[0034] Figure 1 A schematic diagram of a network deployment scenario using dual connectivity for licensed and unlicensed frequency bands;

[0035] Figure 2 This is a flowchart of the uplink signal transmission method according to the present invention;

[0036] Figure 3 This is a schematic block diagram of an uplink signal transmission device according to the present invention;

[0037] Figure 4 This is a schematic diagram illustrating the method for determining the transmission processing of uplink data channel signals according to a first exemplary embodiment of the present invention;

[0038] Figure 5 This is another schematic diagram illustrating the method for determining the transmission processing of uplink data channel signals according to a first exemplary embodiment of the present invention;

[0039] Figure 6 This is a schematic diagram illustrating the method for determining the transmission processing of uplink data channel signals according to a second exemplary embodiment of the present invention;

[0040] Figure 7 This is another schematic diagram illustrating the method for determining the transmission processing of uplink data channel signals according to a second exemplary embodiment of the present invention;

[0041] Figure 8 This is a schematic diagram illustrating the method for determining the transmission processing of uplink data channel signals according to a third exemplary embodiment of the present invention;

[0042] Figure 9 This is a schematic diagram illustrating the method for determining the transmission processing of uplink data channel signals according to a fourth exemplary embodiment of the present invention;

[0043] Figure 10 This is another schematic diagram illustrating the method for determining the transmission processing of uplink data channel signals according to a fourth exemplary embodiment of the present invention;

[0044] Figure 11 This is another schematic diagram illustrating the transmission processing method of uplink data channel signals according to the eleventh exemplary embodiment of the present invention. Detailed Implementation

[0045] The following description, provided with reference to the accompanying drawings, is intended to aid in a full understanding of embodiments of the invention as defined by the claims and their equivalents. Various specific details are included to aid understanding, but these details are to be considered exemplary only. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Furthermore, for clarity and brevity, descriptions of well-known functions and structures are omitted.

[0046] Figure 2 An example flowchart of a method for transmitting signals according to an embodiment of the present invention is shown.

[0047] In step 201, the UE receives downlink control information.

[0048] In step 202, the UE performs uplink signal transmission based on the downlink control information and the time-domain characteristics of the physical resources of the uplink signal.

[0049] The uplink signal includes at least one uplink signal: uplink data channel signal PUSCH, uplink control channel PUCCH, uplink random access channel PRACH, and uplink probe signal SRS.

[0050] Figure 3 An example block diagram of a device for transmitting signals according to an embodiment of the present invention is shown. Figure 3 As shown, the device includes a receiving module 301 and a transmitting module 302.

[0051] The receiving module 301 is used to receive downlink control information; the sending module 302 is used to send uplink signals based on the downlink control information and the time-domain characteristics of the physical resources of the uplink signals.

[0052] Example 1

[0053] When a UE sends a PUSCH, it can send one or more PUSCHs at a time, with each PUSCH corresponding to a different Transmission Block (TB). Alternatively, it can send K PUSCHs at a time, with each PUSCH being a repetition of the same TB.

[0054] The base station can semi-statically configure the retransmission of PUSCH through higher-layer signaling. Specifically, the base station can semi-statically configure the number of retransmissions K through higher-layer signaling, for example, via RRC signaling; or, the base station can dynamically indicate the number of retransmissions K through downlink scheduling signaling (DL assignment).

[0055] For a PUSCH transmission configured to be sent K times repeatedly, step 200 (not shown) may be included before step 201. In step 200, the UE is sending the PUSCH.

[0056] In step 201, the downlink control information includes at least Hybrid Automatic Repeat Request (HARQ-ACK) feedback information. The HARQ-ACK feedback information is the HARQ-ACK information of the PUSCH of one or more HARQ processes of the UE carried by the base station through a specific DCI. In this invention, the specific DCI is abbreviated as DFI (Downlink Feedback Information). For example, a DFI may contain the HARQ-ACK information of all UL HARQ processes or all UL HARQ processes of a UE on one carrier. Alternatively, a DFI may contain the HARQ-ACK information of all UL HARQ processes or all UL HARQ processes of a UE on multiple carriers. Or, a DFI may contain the HARQ-ACK information of the configured UL HARQ processes of multiple UEs. The UE can receive a DFI on a carrier, which contains HARQ-ACK information of the UL HARQ process for that carrier. The DFI can also contain HARQ-ACK information of the UL HARQ process for other carriers. For example, the DFI can indicate which carrier it is for by indicating the bit field of the carrier in the DFI.

[0057] For a PUSCH1 transmitted at time n, the UE expects the HARQ-ACK information for that PUSCH1 included in the received DFI to be no earlier than time n + m_dfi. In other words, if the UE receives a DFI before time n + m_dfi, the HARQ-ACK information in that DFI will not contain a valid HARQ-ACK feedback for PUSCH1. Typically, m_dfi reflects the minimum processing latency required for the base station to generate a HARQ-ACK based on the received PUSCH. In real-world systems, different base stations may have different processing capabilities, resulting in different minimum processing latency requirements. The standard defines one or a set of m_dfi, requiring all base stations to meet this minimum processing latency, but this does not preclude the possibility that more capable base stations can generate HARQ-ACK faster.

[0058] For example, suppose the DFI contains HARQ-ACK feedback for 16 HARQ processes. The UE sends PUSCH1 at time n, corresponding to HARQ process #3. The UE considers the HARQ-ACK for HARQ process #3 received in the DFI before time n + m_dfi to be a valid HARQ-ACK for PUSCH1, and does not use this feedback to determine whether the base station correctly received PUSCH1. As another example, the UE sends PUSCH1 at time n, corresponding to HARQ process #3, and receives the DFI at time m, where time m satisfies mn ≥ m_dfi. Furthermore, the UE did not receive a HARQ-ACK for PUSCH1 from the base station before time m. Therefore, the UE considers the HARQ-ACK for HARQ process #3 received in the DFI at time m to be a valid HARQ-ACK for PUSCH1, and uses this feedback to determine whether the base station correctly received PUSCH1. Preferably, the base station configures one m_dfi value for the UE, or a set of m_dfi values ​​for the UE applicable to different PUSCH transmission conditions. For example, the base station configures a set of m_dfi values ​​applicable to PUSCH mapping type A and PUSCH mapping type B, and / or applicable to different PUSCH end positions, and / or applicable to the presence or absence of multiple sets of discontinuous demodulation reference signals (DMRS). For example, the base station configures two m_dfi values, applicable to the cases where only one set of DMRS exists or where multiple sets of DMRS exist. Each set of DMRS occupies one or more consecutive time-domain symbols. Multiple sets of DMRS are time-interval.

[0059] In step 202, the uplink signal transmission action is performed to stop transmitting the PUSCH, or to continue transmitting the PUSCH, or to retransmit the PUSCH.

[0060] Specifically, in step 202, for the K - time repeated GUL PUSCH transmission, if the UE receives the DFI at time m, the HARQ - ACK of a certain HARQ process in the DFI is ACK, and the PUSCH of the GUL transmission of this HARQ process has been sent at least Ka times before time m - m_dfi, where Ka < K, then the UE can stop sending the remaining repeated PUSCH transmissions. Preferably, Ka = 1, that is, as long as the UE has sent this PUSCH at least once before time m - m_dfi, and the UE receives the HARQ - ACK corresponding to this PUSCH as ACK, then the UE considers this HARQ - ACK valid, indicating that the base station has correctly received this PUSCH, and the UE stops sending the remaining K - Kt times of PUSCH, where Kt is the number of times the PUSCH has been repeated when the UE receives the DFI. If the UE receives the DFI at time m, the HARQ - ACK of a certain HARQ process in the DFI is NACK, and the UE is sending the GUL PUSCH corresponding to this HARQ process at time m and has not completed K - time repeated transmission, then the UE continues to send the repeated PUSCH until it has sent K times or until it receives a valid ACK. If the UE completes K - time repeated transmission at time n, receives the DFI no earlier than time n + m_dfi, and the HARQ - ACK of this GULPUSCH is NACK, then the UE can attempt to re - transmit this GULPUSCH on the configured GUL resource. If the UE receives the DFI at time m, the HARQ - ACK of a certain HARQ process in the DFI is NACK, and the UE has sent K times of the repeated GUL PUSCH corresponding to this HARQ process at time m, then the UE can attempt to re - transmit this GULPUSCH on the configured GUL resource.

[0061] Such as Figure 4As shown, K = 4, K_a = 1, K_t = 3, and m_dfi = 10 symbols. The DFI contains HARQ-ACK information for four HARQ processes. The HARQ-ACK information can be ACK or NACK. The PUSCH of the first HARQ process is shown in the figure, and its HARQ-ACK information is ACK. The HARQ-ACK information of the other three HARQ processes is irrelevant to this example and is represented by X. Therefore, the DFI in the figure is shown as AXXX. It can be seen that when the UE receives the DFI indicating the HARQ-ACK information of carrier 2 on carrier 1, a PUSCH has been completely transmitted on carrier 2 in the previous time slot. Because the corresponding HARQ-ACK information is ACK, the UE can stop transmitting the uncompleted PUSCH after demodulating the DFI and obtaining the ACK information, for example, it does not transmit the fourth PUSCH.

[0062] like Figure 5 As shown, K = 4, K_a = 1, K_t = 3, and m_dfi = 10 symbols. The DFI contains HARQ-ACK information for four HARQ processes, with the PUSCH of the first HARQ process shown in the figure. The HARQ-ACK information for the other three HARQ processes is irrelevant to this example and is represented by X. It can be seen that when the UE receives the DFI indicating HARQ-ACK information for carrier 2 on carrier 1, a complete PUSCH has already been transmitted on carrier 2 in the previous time slot. The corresponding HARQ-ACK information is NACK, so the UE continues to transmit the remaining PUSCH until it has been transmitted four times.

[0063] Example 2

[0064] In step 201, the downlink control information includes at least information for determining uplink and / or downlink and / or flexible time slots / symbols, or information indicating channel occupancy time (COT).

[0065] In step 202, the uplink signal transmission action includes determining the starting resource for transmitting the PUSCH and transmitting the GUL PUSCH according to the determined starting point.

[0066] When a UE transmits a GUL PUSCH, if K repeated transmissions are required, the UE can determine the starting point for the GUL PUSCH transmission from the configured GUL resources using at least one of the following methods:

[0067] (2.1) When selecting the starting point for GUL PUSCH transmission, the UE must select a time slot / symbol that ensures the GUL resources corresponding to the K repetitive PUSCH transmissions are temporally continuous as the starting point. For example, such as Figure 6 As shown, the base station configures GUL resources via higher-layer signaling in a period of 40 time slots. A bitmap is used to indicate which time slots within a period are GUL resources. Assuming K=2, and time slots n, n+1, n+2, n+8, n+12… are the GUL resources configured by the base station, the UE can choose time slot n or n+1 as the starting time slot for sending two PUSCHs, but cannot choose time slots n+2 or n+8 as the starting point for sending two PUSCHs. If the semi-statically configured GUL resources are continuous, but the base station modifies the GUL resources via dynamic signaling, then resources that meet the continuous resource condition must be selected based on the modified GUL resources.

[0068] (2.2) When selecting the starting point for GUL PUSCH transmission, the UE must choose a time slot / symbol that ensures the GUL resources corresponding to the K repetitive PUSCH transmissions belong to the same GUL resource period. For example, the base station configures GUL resources in a period of 40 time slots via higher-layer signaling, and uses a bitmap to indicate which time slots within a period are GUL resources. Assume K = 2. If time slots n, n+1, n+2, n+8, n+12… are GUL resources configured by the base station, but time slots n and n+1 belong to the first 40ms period, and time slots n+2, n+8, n+12… belong to the second 40ms period, then the UE can choose time slot n as the starting time slot for transmitting two PUSCHs, but cannot choose time slot n+1 as the starting time slot for transmitting two PUSCHs.

[0069] Furthermore, when the UE selects the PUSCH transmission start point, it can be restricted that not only do the K repeated PUSCH transmissions belong to the same GUL resource period, but they also need to be mapped to GUL resources that are temporally continuous. Therefore, the UE can choose time slot n as the starting time slot for transmitting two PUSCHs, but cannot choose time slots n+1, n+2, n+8, or n+12 as the start point.

[0070] Alternatively, the UE can be restricted to select the starting point for PUSCH transmission such that K PUSCHs belong to the same GUL resource period, but can be mapped to GUL resources that are not contiguous in time. Then, the UE can choose time slots n, n+2, n+8, and n+12 as the starting time slots for transmitting two PUSCHs.

[0071] (2.3) When selecting the starting point for GUL PUSCH transmission, the UE must choose a time slot / symbol that ensures the GUL resources corresponding to the K repeated PUSCH transmissions belong to the same COT. If sending K PUSCH transmissions starting from time slot / symbol n would cause some PUSCH transmissions to occur outside of a channel occupancy time (COT), the UE cannot choose to start sending K PUSCH transmissions from time slot / symbol n. Instead, it should choose a time slot / symbol m that guarantees all K transmissions are within the same COT. For example, K = 2. Figure 7 As shown, after the base station completes the first type of LBT (as defined in TS 37.213), it occupies the channel starting from time slot n+4 and indicates that the COTs available for uplink are time slots n+8, n+9, and n+10. Therefore, the UE cannot choose to send two PUSCHs starting from time slot n+10; it can only choose to send two PUSCHs starting from time slot n+8 or time slot n+9.

[0072] Example 3

[0073] In step 201, the downlink control information includes at least information for determining uplink and / or downlink and / or flexible time slots / symbols, or information indicating channel occupancy time (COT).

[0074] In step 202, the uplink signal transmission action includes determining the number of times to transmit the PUSCH and transmitting the GUL PUSCH according to the determined number of transmissions.

[0075] When a UE sends a GUL PUSCH, if it needs to perform K repeated transmissions, but the GUL resources corresponding to the K repeated PUSCHs do not meet the predefined conditions, the UE can only send a portion of the PUSCHs. Specifically, which PUSCHs to send can be determined according to at least one of the following methods.

[0076] (3.1) If the GUL resources corresponding to the PUSCH for K repeated transmissions are discontinuous in time, assuming that the continuous GUL resources are sufficient to transmit the PUSCH up to \(K_c\) times, the UE only transmits the PUSCH \(K_c\) times on the continuous GUL resources and abandons \(K - K_c\) transmissions, where \(K_c < K\). For example, the GUL resources configured by the base station through high-layer signaling have a period of 40 time slots, and in the form of a bitmap, indicate which of the 40 time slots within a period are GUL resources. Assume that the GUL resources configured by the base station are time slots \(n\), \(n + 1\), \(n + 2\), \(n + 8\), \(n + 12\), …, and \(K = 4\). If the UE selects to start transmitting the PUSCH at time slot \(n\), since time slot \(n + 8\) and time slot \(n + 2\) are not adjacent time slots, the UE only transmits the PUSCH 3 times at time slots \(n\), \(n + 1\) and \(n + 2\), \(K_c = 3\), and then abandons \(4 - 3 = 1\) PUSCH transmission.

[0077] Furthermore, if \(K_c\) is less than a predefined threshold, the UE should select another starting point such that \(K_c\geq\) the predefined threshold. Preferably, the threshold can be predefined or configured when the base station configures the GUL. Preferably, the threshold can be related to the service type carried by the PUSCH, and / or the logical channel, and / or the redundancy version (RV). For example, \(K = 4\), the GUL resources configured by the base station are time slots \(n\), \(n + 1\), \(n + 4\), \(n + 5\), \(n + 6\), \(n + 12\), …, and the predefined threshold = 3. Since there are only 2 consecutive time slots starting from time slot \(n\), which are only sufficient to transmit \(K_c = 2\) PUSCHs, less than the predefined threshold, and there are 3 consecutive time slots starting from time slot \(n + 4\), \(K_c = 3\) is equal to the predefined threshold, so the UE cannot select to start at time slot \(n\) and can only select to start at time slot \(n + 4\) to transmit the PUSCH 3 times and abandon the last PUSCH transmission.

[0078] (3.2) If the GUL resources corresponding to the PUSCH transmitted K times span the GUL resource configuration period, assuming that the GUL resources in one of the spanned GUL resource configuration periods are sufficient to transmit up to K_c times of PUSCH, the UE only transmits K_c times of PUSCH on the resources in this period and abandons K - K_c transmissions, where K_c < K. For example, the GUL resources configured by the base station through higher layer signaling have a period of 40 time slots, and in the form of a bitmap, it indicates which time slots among the 40 time slots in one period are GUL resources. Suppose the UE selects to start transmitting PUSCH at time slot n, K = 4, K_c = 2, time slots n and n + 1 are GUL resources in one period, and time slot n + 2 is a GUL resource in the next period. Then, the UE only transmits PUSCH twice at time slots n and n + 1. In one period, it can be specified that PUSCH repetitions are only transmitted on GUL resources that are continuous in time, or, in one period, it can be transmitted on GUL resources that are logically continuous, while the time resources actually occupied by the GUL resources can be discontinuous.

[0079] Furthermore, if K_c is less than a predefined threshold, the UE should select another starting point such that K_c ≥ the predefined threshold. Preferably, the threshold can be predefined or configured by the base station when configuring GUL. Preferably, the threshold can be related to the service type carried by the PUSCH, and / or the logical channel, and / or the RV.

[0080] (3.3) If some of the resources corresponding to K times of PUSCH transmissions are outside a channel occupancy time (COT), assuming that the resources in the same COT are sufficient to transmit up to K_c times of PUSCH, the UE only transmits K_c times of PUSCH on the resources within the same COT and abandons K - K_c transmissions, where K_c < K. For example, K = 4. As Figure 8 shown, after the base station completes the first type of LBT (such as the first type of LBT defined in TS 37.213), it occupies the channel starting from time slot n + 4 and indicates that the COT available for uplink is time slots n + 8, n + 9, and n + 10. Then, if the UE selects to start transmitting PUSCH from time slot n + 8, it can transmit at most 3 times of PUSCH, or, if the UE selects to start transmitting PUSCH from time slot n + 9, it can only transmit 2 times of PUSCH, or, if the UE selects to start transmitting PUSCH from time slot n + 10, it can only transmit 1 time of PUSCH.

[0081] Furthermore, if K_c is less than a predefined threshold, the UE should select another starting point such that K_c ≥ the predefined threshold. For example, assume the predefined threshold is 2. Then Figure 8In this configuration, the UE can only choose to send 3 PUSCHs starting from time slot n+8, or 2 PUSCHs starting from time slot n+9. Preferably, the threshold value can be predefined, or configured when the base station configures GUL. Preferably, the threshold value can be related to the service type carried by the PUSCH, and / or logical channel, and / or RV.

[0082] (3.4) If the resources corresponding to K PUSCH transmissions are outside the Channel Occupied Time (COT), the UE can perform Type I LBT and then send K_d PUSCH transmissions, where K_d is no more than K and the K_d PUSCH transmissions do not exceed the COT length newly acquired by the UE through Type I LBT. Typically, K_d = K.

[0083] (3.5) If the resources corresponding to K PUSCH transmissions are outside a Channel Occupied Time (COT), the UE can determine, based on the base station's instruction, whether to stop transmitting K PUSCHs at the end of the COT or continue transmitting K PUSCHs.

[0084] Example 4

[0085] In step 201, the downlink control information includes at least HARQ-ACK information.

[0086] In step 202, the uplink data channel signal transmission action includes determining the contention window length (CWS) of the channel access procedure before uplink signal transmission, and transmitting the uplink signal after completing the LBT according to the CWS.

[0087] Similar to the HARQ-ACK processing in Example 1, for a PUSCH1 sent at time n, the UE expects the HARQ-ACK information for PUSCH1 included in the received DFI to be no earlier than time n + m_dfi. That is, if the UE receives a DFI before time n + m_dfi, the HARQ-ACK information in that DFI will not contain valid HARQ-ACK feedback for PUSCH1. Therefore, the HARQ-ACK information usable for CWS adjustment must satisfy the following: the time difference between the time m when the UE receives the HARQ-ACK information and the time n when the UE sends the PUSCH corresponding to the HARQ-ACK information is not less than m_dfi_0. Preferably, assuming the UE receives the DFI at time m, the UE has transmitted a PUSCH no later than time m-m_dfi_0, and the PUSCH is the closest in time to time m-m_dfi_0, and the base station has not transmitted the HARQ-ACK information of the PUSCH before time m, and the UE has not performed CWS adjustment based on the HARQ-ACK of the PUSCH, then the HARQ-ACK information corresponding to the PUSCH in the DFI can be used to determine the CWS adjustment. Preferably, m_dfi_0 is equal to m_dfi in Embodiment 1. Preferably, m_dfi_0 is in units of time slots or OFDM symbols.

[0088] Preferably, the PUSCH is the first PUSCH of the most recent uplink transmission that satisfies the time difference ≥ m_dfi_0, or the PUSCH is all PUSCHs that satisfy the time difference in the first time slot of the most recent uplink transmission that satisfy the time difference ≥ m_dfi_0, or the PUSCH is the PUSCH that satisfies the time difference and is the earliest in time in the first time slot of the most recent uplink transmission that satisfies the time difference ≥ m_dfi_0.

[0089] For example, the first time slot contains PUSCH1, PUSCH2, and PUSCH3, which are time-division multiplexed. Assuming the time interval from the end position of PUSCH3 to time slot m is less than m_dfi_0, and the time intervals from the end positions of PUSCH1 and PUSCH2 to time slot m are greater than or equal to m_dfi_0, then the HARQ-ACK of PUSCH1 and PUSCH2 can be used for CWS adjustment.

[0090] If the base station configures K times of repeated transmission of PUSCH, for example, when the base station configures GUL transmission, it configures K times of repeated transmission. If the UE receives a DFI at time m, and the HARQ-ACK of a certain HARQ process in the DFI is ACK, and the PUSCH of this HARQ process has been transmitted at least Ka times before time m - m_dfi_0, where Ka < K, then the UE considers that this HARQ-ACK can be used for CWS adjustment. Preferably, Ka = 1, that is, the UE has transmitted this PUSCH at least once before time m - m_dfi_0, and the HARQ-ACK corresponding to this PUSCH in the DFI received by the UE at time m is ACK, then the UE can use this HARQ-ACK to adjust the CWS. The UE only uses this HARQ-ACK to adjust the CWS once. As Figure 9 shown, K = 2, Ka = 1, m_dfi = 10 symbols. The DFI contains the HARQ-ACK information of 4 HARQ processes. The HARQ-ACK information can be ACK or can be NACK. The PUSCH of the first HARQ process is shown in the figure, and the HARQ-ACK information of the first HARQ process is ACK. The HARQ-ACK information of the other three HARQ processes is not relevant to this example and is replaced by X. Therefore, the DFI in the figure is shown as AXXX. It can be seen that when the UE receives a DFI indicating the HARQ-ACK information of carrier 2 on carrier 1, in the previous 1 time slot, a PUSCH has been completely transmitted on carrier 2. Because the corresponding HARQ-ACK information is ACK, the UE can reset the CWS of the next uplink transmission burst (PUSCH3) according to the ACK.

[0091] If the base station configures K times of repeated transmission of PUSCH, for example, when the base station configures GUL transmission, it configures K times of repeated transmission. If the UE receives a DFI at time m, and the HARQ-ACK of a certain HARQ process in the DFI is NACK, and the number of transmissions of the PUSCH of this HARQ process before time m - m_dfi_0 < Kb, then the UE considers that this HARQ-ACK is not used for CWS adjustment. Preferably, Kb = K. Preferably, Kb is the number of repeated transmissions that can be continuously transmitted, Kb ≤ K. For example, K = 4. In this transmission, due to the limitation of the COT length, only 2 times can be continuously transmitted, then Kb = 2. If the number of transmissions of the PUSCH of this HARQ process before time m - m_dfi_0 ≥ Kb, then the UE considers that this HARQ-ACK can be used for CWS adjustment. As Figure 10As shown, K = 2, K_b = 1, and m_dfi = 10 symbols. The DFI contains HARQ-ACK information for four HARQ processes. The HARQ-ACK information can be ACK or NACK. The PUSCH of the first and fourth HARQ processes is shown in the figure, and the HARQ-ACK information of the first and fourth HARQ processes is NACK. The HARQ-ACK information of the other two HARQ processes is irrelevant to this example and is represented by X. Therefore, the DFI in the figure is shown as NXXN. It can be seen that when the UE receives the DFI indicating the HARQ-ACK information of carrier 2 on carrier 1, only one PUSCH was completely transmitted on carrier 2 in the previous time slot. Because the corresponding HARQ-ACK information is NACK, the UE does not adjust the CWS of the next uplink transmission burst (PUSCH3) based on this NACK. Instead, it continues to find an uplink transmission burst (two PUSCH0 transmissions). Since the DFI indicates that the HARQ-ACK of PUSCH0 is NACK, and the UE has not yet adjusted the CWS with this NACK, the UE increases the CWS of PUSCH3 based on this NACK.

[0092] Before the uplink transmission of the PUSCH corresponding to the HARQ-ACK that can be used for CWS adjustment begins, the UE performs channel access for the first type of LBT.

[0093] In step 202, the CWS is adjusted according to the HARQ-ACK values ​​available for CWS adjustment determined by the above method. For all HARQ-ACK values ​​available for CWS adjustment, if the percentage of ACK exceeds a predefined threshold, or the percentage of NACK is lower than a predefined threshold, the CWS is reset; otherwise, the CWS is increased to the next larger available value.

[0094] Example 5

[0095] In step 201, the downlink control information includes at least information for determining uplink and / or downlink and / or flexible time slots / symbols, or information indicating channel occupancy time (COT).

[0096] In step 202, determining whether to perform the uplink signal transmission action includes determining whether to transmit or abandon the transmission of the uplink signal.

[0097] Base stations can semi-statically configure uplink time slots / symbols, downlink time slots / symbols, and flexible time slots / symbols via higher-layer signaling. If the base station does not configure this information via higher-layer signaling, it can treat these resources as semi-statically configured as flexible time slots / symbols for processing. Base stations can also indicate uplink time slots / symbols, downlink time slots / symbols, and flexible time slots / symbols via dynamic signaling, such as Slot Format Indication (SFI). Typically, a semi-statically indicated downlink time slot / symbol cannot be dynamically indicated as an uplink or flexible time slot / symbol, and a semi-statically indicated uplink time slot / symbol cannot be dynamically indicated as a downlink or flexible time slot / symbol. However, a semi-statically indicated flexible time slot / symbol can be dynamically indicated as an uplink, downlink, or flexible time slot / symbol.

[0098] The base station can periodically send indications for uplink / downlink / flexible time slots / symbols via dynamic signaling. The UE attempts to receive the indications on the corresponding resources. For example, the base station configures the period and offset of the SFI. The duration of the uplink / downlink / flexible time slot / symbol information indicated in the SFI is typically greater than or equal to the SFI period. For example, the base station intends to send SFIs in time slots n, n+10, n+20… The uplink / downlink / flexible time slot / symbol indicated in the SFI sent in time slot n applies to time slots starting from time slot n and with a length of L_sfi. L_sfi ≥ 10 time slots. If multiple SFIs indicate uplink / downlink / flexible time slot / symbol information for the same resource, the information indicated by these SFIs should be consistent, or determined by the indication of the most recently received SFI.

[0099] The base station can also send dynamic signaling to indicate uplink / downlink / flexible time slots / symbols at the start of a downlink transmission burst. For example, the base station can indicate downlink COT information, such as COT length, start point, and which time slots / symbols within the COT are uplink and which are downlink, etc.

[0100] In the following description, unless otherwise specified, the specific form of dynamic signaling used to indicate uplink / downlink / flexible time slots / symbols is not limited. The specific form of dynamic signaling can be one of the signaling forms described above, or a combination thereof. For ease of description, SFI is used instead.

[0101] Since transmitting signals on unlicensed frequency bands typically requires LBT (Local Level Bypass), if the base station fails to transmit the SFI (Simultaneous Signaling Indicator) before transmitting the dynamic signaling indication indicating uplink / downlink / flexible time slots / symbols, the base station cannot transmit the SFI. Alternatively, the base station may successfully complete the LBT and transmit the SFI, but the presence of a hidden terminal causes interference when the UE receives the SFI. In the prior art, for semi-static uplink signals, such as GUL transmissions, UE-initiated PRACH transmissions, periodically transmitted PUCCHs, and periodically transmitted SRSs, the UE cancels transmitting these signals if it fails to receive the SFI. On unlicensed frequency bands, this behavior leads to reduced uplink transmission efficiency. To improve transmission efficiency, semi-static uplink signals can be transmitted in at least one of the following ways.

[0102] (5.1) If the UE is configured with GUL transport resources, and the GUL transport resources selected for a given GUL PUSCH transmission are semi-statically configured uplink and / or flexible slots / symbols, the UE may attempt to transmit the PUSCH if it does not receive dynamic signaling indicating that some or all of the PUSCH resources are downlink slots / symbols. For example, if the UE does not receive an SFI indication, or if the UE receives an SFI indicating that some or all of the PUSCH resources are uplink and / or flexible slots / symbols, the UE may attempt to transmit the PUSCH. If the UE receives dynamic signaling indicating that some or all of the PUSCH resources are downlink slots / symbols, such as an SFI indication, or other DCI indication, such as an indication to schedule the reception of PDSCH / CSI-RS on the resource or an indication of downlink transport burst resources, the UE will not transmit the PUSCH.

[0103] Preferably, if the GUL PUSCH contains uplink control information, such as HARQ-ACK, if the PUSCH resources are semi-statically configured uplink and / or flexible slots / symbols, and the UE does not receive dynamic signaling indicating that some or all of the PUSCH resources are downlink slots / symbols, then the UE may attempt to send the PUSCH; for a GUL PUSCH containing only data, if the PUSCH resources are semi-statically configured flexible slots / symbols, and the UE does not receive dynamic signaling indication, or receives dynamic indication that it is a flexible slot / symbol, then the UE does not send the PUSCH.

[0104] (5.2) If the UE is configured with GUL transport resources, and the GUL transport resources selected for a given GUL PUSCH transmission are semi-statically configured uplink and / or flexible slots / symbols, the UE may attempt to transmit the PUSCH if it does not receive dynamic signaling indicating that part or all of the resources are downlink and / or flexible slots / symbols; otherwise, it will not transmit the PUSCH. For example, if the UE does not detect an SFI and does not receive any other DCI that can be used to determine that the resource is a downlink resource, the UE may attempt to transmit the PUSCH. As another example, if the UE receives an SFI indicating that the resource is a flexible slot / symbol, the UE may not attempt to transmit the PUSCH.

[0105] Preferably, if the GUL PUSCH contains uplink control information, such as HARQ-ACK, if the PUSCH resources are semi-statically configured uplink and / or flexible time slots / symbols, and the UE does not receive dynamic signaling indicating that some or all of the PUSCH resources are downlink and / or flexible time slots / symbols, then the UE may attempt to send the PUSCH; for a GUL PUSCH containing only data, if the PUSCH resources are semi-statically configured flexible time slots / symbols, and the UE does not receive dynamic signaling indication, or receives dynamic indication that it is a flexible time slot / symbol, then the UE does not send the PUSCH.

[0106] Preferably, based on the method in (5.1) or (5.2), when the base station configures GUL transmission for the UE, it can configure whether the UE should attempt GUL transmission on GUL resources where no dynamic signaling indication has been received indicating that the resource is a downlink slot / symbol. For example, if the UE does not receive dynamic signaling indicating that some or all of the resource is a downlink slot / symbol, the base station configures the UE to attempt GUL transmission on the configured GUL resources; if the GUL transmission resource is not a semi-statically configured uplink resource, and the UE does not receive dynamic signaling indicating that the resource is an uplink resource, the base station can also configure the UE not to attempt GUL transmission on the configured GUL resources.

[0107] Preferredly, based on the method of (5.1) or (5.2), when the base station configures GUL transmission for the UE, it can configure whether the UE attempts GUL transmission on GUL resources where no dynamic signaling indication is received for downlink and / or flexible time slots / symbols.

[0108] Preferredly, based on the method of (5.1) or (5.2), when the base station configures GUL transmission for the UE, it can configure the UE to attempt GUL transmission on GUL resources where no dynamic signaling indication is received for downlink slots / symbols, or to attempt GUL transmission on GUL resources where no dynamic signaling indication is received for downlink and / or flexible slots / symbols.

[0109] For example, multiple GUL transmissions can be configured for the UE for different service base stations.

[0110] For time-sensitive services, such as Ultra Reliable and Low Latency Communication (URLLC), in order to ensure timely transmission of this type of service, when configuring GUL transmission to carry such services, if the UE does not receive dynamic signaling indicating that some or all of the PUSCH resources are downlink slots / symbols, the base station can configure the UE to attempt to transmit on GUL resources; otherwise, the base station can configure the UE not to attempt to transmit on GUL resources.

[0111] For GUL transmissions carrying enhanced Mobile Broadband (eMBB) services, when configuring GUL transmissions for such services, if the UE receives dynamic or semi-static signaling indicating that all resources of the PUSCH are uplink slots / symbols, the base station can configure the UE to attempt to transmit on GUL resources; otherwise, the base station can configure the UE not to attempt to transmit on GUL resources.

[0112] Preferably, the base station can indicate whether the UE can perform GUL transmissions on specific resources through other signaling. For example, similar to the bits in the Common Downlink Control Channel (C-PDCCH) of TS 36.213 used to indicate whether the UE is allowed to transmit GUL transmissions within the Maximum Channel Occupancy Time (MCOT), the base station can indicate whether the UE is allowed to transmit GUL transmissions within the COT in the SFI or other DCI indicating COT signaling. This type of indication can be used in combination with the rules for determining whether GUL transmissions can be transmitted described above in (5.1) and / or (5.2).

[0113] (5.3) If the UE is configured with GUL transmission resources, and the GUL transmission resources selected for a certain GUL PUSCH transmission are semi-statically configured uplink and / or flexible slots / symbols, if part or all of the PUSCH resources are located between two adjacent SFI indications, and the UE has not received dynamic indication information indicating the uplink / downlink / flexible slots / symbols of part or all of the PUSCH resources, then the UE may attempt to transmit the PUSCH on the PUSCH resources before the next possible SFI slot; if an SFI is received in the SFI slot, the UE determines whether to continue transmitting the PUSCH or stop based on the SFI indication.

[0114] For example, the expected time slots for transmitting SFI are time slots n, n+4, n+8, ..., and the GUL transmission of PUSCH resources starts at time slot n+2, with K=4. If the UE does not receive the uplink / downlink / flexible time slot information indicating time slots n+2 and n+3 for SFI in time slot n, then the UE can attempt to transmit PUSCH in time slot n+2 and continue until time slot n+3, but the UE needs to attempt to receive SFI in time slot n+4.

[0115] Preferably, if the DL MCOT and SFI are independent dynamic signaling, and if the UE does not receive the SFI but receives the DL MCOT signaling indicating that some or all of the resources of the PUSCH are downlink, then the UE cannot send the PUSCH.

[0116] (5.4) The PRACH transmitted autonomously by the UE can also be determined according to the methods described in (5.1) to (5.3) above. Preferably, for different types of PRACH transmissions, the UE can determine whether to attempt PRACH transmission on a dynamically indicated downlink, or downlink and / or flexible time slot / symbol, according to predefined rules. For example, the first type of PRACH transmission is a PRACH transmission on a Pcell or Scell, and the second type of PRACH transmission is a PRACH transmission on an Scell. For another example, if the resources used by the PRACH are those configured in RACH-ConfigCommon, then it belongs to the first type of PRACH transmission; otherwise, it belongs to the second type of PRACH transmission.

[0117] For example, the first type of PRACH transmission is the initial access PRACH or the handover PRACH, and the other PRACHs are the second type of PRACH, or the non-contention-based PRACH belongs to the first type of PRACH, and the contention-based PRACH belongs to the second type of PRACH, and so on.

[0118] For example, for a PRACH transmission of type 1, the UE can attempt to send a PRACH on the configured PRACH resource. If the UE does not receive an indication that the resource is a downlink transmission resource, the UE can send a PRACH on the resource; otherwise, it will not send the PRACH.

[0119] For PRACH transmissions of type 2, the UE may attempt to transmit on the configured PRACH resource. If the UE does not receive an indication that the resource is for downlink and / or flexible slots / symbols, the UE may attempt to transmit PRACH on the resource; otherwise, it may not transmit the PRACH.

[0120] PRACH triggered by dynamic signaling can attempt to send on the resource indicated by the dynamic signaling without referring to the dynamic uplink / downlink and / or flexible time slots / symbols. Alternatively, PRACH triggered by dynamic signaling can attempt to send on the first resource indicated by the dynamic signaling without referring to the dynamic uplink / downlink and / or flexible time slots / symbols, while subsequent resources are processed as PRACH of type 1.

[0121] (5.5) Specific types of PUCCHs can also be determined according to the methods described in (5.1) to (5.3) above. For example, if the PUCCH that the UE expects to send contains a scheduling request (SR), and the UE has not received an SFI indicating that the PUCCH has a resource, the UE may attempt to send the PUCCH. As another example, if the PUCCH that the UE expects to send contains an SR, and the UE has received an SFI indicating that the PUCCH has a flexible resource, the UE may attempt to send the PUCCH.

[0122] Ideally, sending semi-static uplink information requires avoiding the time-frequency resources of the SFI. For example, if the SFI is sent in the first OFDM symbol of time slots n, n+k0, and n+2*k0, then the UE cannot attempt to send semi-static uplink information on the BWP or LBT subband or carrier where the SFI is located in the first OFDM symbol of these time slots.

[0123] (5.6) Specific types of SRS can also be determined according to the methods described in (5.1) to (5.3) above.

[0124] Preferably, in step 201, the downlink control information may indicate downlink time slots / symbols, uplink time slots / symbols, flexible time slots / symbols, and special flexible time slots / symbols. In a special flexible time slot / symbol, the UE may attempt to transmit predefined semi-static configuration uplink signals, such as GUL, and / or PRACH. Preferably, in a special flexible time slot / symbol, the UE may attempt to transmit a specific type of PUCCH, such as a PUCCH containing SR, or a PUCCH containing HARQ-ACK. Preferably, in a special flexible time slot / symbol, the UE performs Type I LBT, and the special flexible time slot / symbol is not counted as a downlink MCOT length. Preferably, in a special flexible time slot / symbol, the UE does not attempt to receive predefined semi-static configuration downlink signals, such as PDCCH and / or synchronization signal / broadcast channel (SS / PBCH), or the UE attempts to receive predefined semi-static configuration downlink signals, such as PDCCH and SS / PBCH. Preferably, in a special flexible slot / symbol, if the base station indicates a downlink slot / symbol, for example, by triggering an aperiodic CSI-RS via DCI, the UE can perform measurements based on the CSI-RS; otherwise, the UE does not perform measurements based on the CSI-RS.

[0125] Preferably, the UE attempts to receive the configured PDCCH and / or SS / PBCH in a flexible time slot / symbol, but does not attempt to receive other downlink signals in a semi-static configuration, such as periodic CSI-RS, and does not attempt to transmit uplink signals in a predefined semi-static configuration.

[0126] Preferably, the UE attempts to receive downlink signals but does not attempt to transmit uplink signals in downlink time slots / symbols; and attempts to transmit uplink signals but does not attempt to receive downlink signals in uplink time slots / symbols.

[0127] Preferably, the special flexible time slot / symbol can be explicitly indicated by dynamic signaling. For example, D, U, F, and SF can be defined to represent downlink, uplink, flexible, and special flexible symbols, respectively. The SFI indicates which of these four states each symbol in each of the X time slots belongs to, where X ≥ the period k0 of the SFI. Preferably, if multiple SFIs indicate the state of the same time slot / symbol, if the time slot / symbol is a special flexible symbol, the state of the time slot / symbol is determined based on the most recently received SFI; if the time slot / symbol belongs to one of the other three states, the states indicated by the multiple SFIs should be the same.

[0128] Preferably, the special flexible time slot / symbol can be implicitly indicated by dynamic signaling. For example, if the time slot X indicated by SFI is less than the period k0 of SFI, then the last k0–X time slots within one SFI period are special flexible time slots.

[0129] Preferably, if the base station can send SFI and dynamic signaling indicating COT information separately, and the resources where the downlink transmission burst indicated by COT is located cannot overlap with the uplink resources indicated by SFI, the resources available for uplink transmission indicated by COT cannot overlap with the downlink resources indicated by SFI, the resources where the uplink or downlink transmission burst indicated by COT is located can overlap with the flexible resources indicated by SFI, and the resources where the uplink or downlink transmission burst indicated by COT is located can overlap with the special flexible resources indicated by SFI, then the UE can attempt to send uplink signals and receive downlink signals in the uplink or downlink resources indicated by COT.

[0130] Preferably, if the UE overlaps with a flexible resource indicated by the SFI in a resource not indicated by the COT, the UE will not attempt to receive PDCCH or periodic CSI-RS on the overlapping resource, and the UE will not attempt to transmit a semi-static uplink signal. Preferably, if the UE overlaps with a special flexible resource indicated by the SFI in a resource not indicated by the COT, the UE may attempt to transmit a predefined semi-static uplink signal on the overlapping resource. Preferably, if the UE overlaps with a special flexible resource indicated by the SFI in a resource not indicated by the COT, the UE may attempt to receive PDCCH on the overlapping resource.

[0131] Preferably, if the UE attempts to transmit uplink in a resource not indicated by the COT, it should use the first type of LBT, namely Cat-4 LBT.

[0132] Preferably, if the UE attempts to transmit uplink in the resources indicated by the COT, it can use a second type of LBT, such as a 25µs LBT, or not perform an LBT at all.

[0133] Preferably, the method described above is only used for transmission in unlicensed frequency bands. For transmission in licensed frequency bands, the method described in TS38.213 shall apply.

[0134] Preferably, the method described above is used for transmission in both unlicensed and licensed frequency bands.

[0135] Based on the dynamic scheduling of downlink signal reception or uplink signal transmission by the base station, the UE determines reception / transmission according to the scheduling signaling, without relying on the dynamic indication signaling. For the reception of K downlink signals or the transmission of K uplink signals dynamically scheduled by the base station, at least the first reception or transmission is determined according to the scheduling signaling, without relying on the dynamic indication signaling.

[0136] Example 6

[0137] In step 201, the downlink control information includes at least the time resource information of the PUSCH.

[0138] In step 202, determining the uplink signal transmission action includes transmitting PUSCH and / or PUSCH DMRS with a selected time resource pattern.

[0139] The PUSCH timing resource information indicated in the downlink control information may include type A or type B indication information. Type A indicates that the PUSCH DMRS is transmitted in the 3rd or 4th symbol of a time slot, while type B indicates that the PUSCH DMRS is transmitted in the 1st complete symbol of a PUSCH within a time slot. Furthermore, the starting point of a type A PUSCH is the first symbol of a time slot, while the starting point of a type B PUSCH can be any symbol within a time slot.

[0140] When a base station schedules a UE to transmit on M>1 time slots via a DCI, or when a base station configures a UE to transmit on M>1 time slots via higher-layer signaling, the PUSCH and / or the DMRS pattern of the PUSCH in the M time slots can be determined according to at least one of the following methods:

[0141] (1) Determine the DMRS type in M ​​time slots according to the instructions of the base station. The DMRS type of these M time slots is the same.

[0142] (2) According to the instructions of the base station, determine the DMRS type of the first time slot in the M time slots, and the DMRS type of the other M-1 time slots respectively, and the DMRS type of the other M-1 time slots is the same; or, determine the DMRS type of the first time slot in the M time slots, the DMRS type of the last time slot in the M time slots, and the DMRS type of the other M-2 time slots respectively, and the DMRS type of the other M-2 time slots is the same; or, determine the DMRS type of the first time slot and the last time slot in the M time slots, and the DMRS type of the other M-2 time slots respectively, and the DMRS type of the first and last time slots is the same, and the DMRS type of the other M-2 time slots is the same;

[0143] (3) Based on the base station's instruction, determine the DMRS type of the first time slot out of M time slots, and determine the DMRS type of the other M-1 time slots according to a predefined rule; or, determine the DMRS types of the first and last time slots out of M time slots, and determine the DMRS type of the other M-2 time slots according to a predefined rule; or determine the DMRS types of the first and last time slots out of M time slots respectively, and determine the DMRS type of the other M-2 time slots according to a predefined rule. The predefined rule is that the DMRS type of the other M-1 time slots or the other M-2 time slots is type A, or the predefined rule is that the DMRS type of the other M-1 time slots or the other M-2 time slots is type B.

[0144] (4) Based on the instructions of the base station, determine the PUSCH time domain resources in M ​​time slots, with each time slot having the same PUSCH time domain resources. If there are gaps between the PUSCH resources of each time slot, then after the UE completes the first type of LBT for the first time and before the start of other time slots, the second type of LBT can be performed, for example, a 25us LBT.

[0145] (5) According to the instructions of the base station, determine the PUSCH time domain resources in M ​​time slots, wherein the PUSCH time domain resources of the first time slot and the last time slot are determined according to the instructions in the DCI, and the PUSCH of the middle M-2 time slots occupy a complete time slot.

[0146] (6) The base station can indicate whether the PUSCH time domain resource mapping in the M time slots is determined according to method (4) or (5). For example, when configuring the PUSCH time resource information, the base station can configure which method is used to determine the PUSCH and DMRS pattern. For example, an information mappingType_per_slot can be added to PUSCH-TimeDomainResourceAllocation to indicate whether the PUSCH pattern is determined according to method (4) or (5). For another example, the base station can indicate the method in the DCI by a separate bit field or by reusing other bit fields.

[0147]

[0148] Correspondingly, the determination of the time-domain resource mapping method of PUSCH can have a one-to-one correspondence with the time-domain pattern of DMRS. For example, if PUSCH adopts (4), then DMRS adopts (1); if PUSCH adopts (5), then DMRS adopts (3).

[0149] The determination of the time-domain resource mapping method of PUSCH can be independent of the determination of the time-domain pattern of DMRS.

[0150] If the scheduling granularity of PUSCH is a sub-slot, the above method also applies; simply replace the slot with a sub-slot.

[0151] The above method also applies to the transmission of M time slots of GUL PUSCH. The base station indication is sent via DCI activation of the GUL transmission, or via higher-layer signaling configured for the GUL transmission.

[0152] Example 7

[0153] In step 201, the downlink control information includes at least the modulation and coding scheme (MCS) information of the PUSCH and information based on the coded block group (CBG).

[0154] In step 202, determining the uplink signal transmission action includes transmitting PUSCH with the selected CBG.

[0155] When a base station schedules a UE to transmit on M>1 time slots via a DCI, or when a base station configures a UE to transmit on M>1 time slots via higher-layer signaling, the CBG and / or MCS of the PUSCH in the M time slots can be determined according to at least one of the following methods.

[0156] (a) If the DCI indicates that the PUSCHI contains only a portion of the CBG of a TB, then the transport block TB size of this PUSCHI is based on the DCI that last scheduled this TB. j The TB size indicated in the middle is determined. If the DCI that previously scheduled this TB scheduled one PUSCH, and the indicated MCS is a value between 0 and 27, then this DCI is a DCI. j If the last DCI that scheduled this TB scheduled M>1 PUSCHes and scheduled all CBGs for this TB (for example, indicated as TB-based transports), then this DCI is a DCI. j .

[0157] For example, a DCI can schedule M>1 PUSCHs. This DCI contains bit fields indicating whether each PUSCH is transmitted based on TB or CBG, a CBGTI indicating a PUSCH transmitted based on CBG, and an NDI (New Data Indicator) indicating a PUSCH transmitted based on TB. If the DCI indicates that PUSCH PUSCH Hi is a PUSCH transmitted based on CBG, and the CBGTI indicates that PUSCH PUSCH contains only a portion of the CBG in a TB, then the UE does not determine the TB size of PUSCH PUSCH based on the MCS indicated by the current DCI, but rather determines the TB size based on the MCS information indicated by the previous DCI that scheduled this TB and contained TB size information. If the DCI indicates that PUSCH PUSCH Hi is a PUSCH transmitted based on TB, then the UE determines the TB size based on the MCS indicated by the current DCI.

[0158] (b) If the DCI indicates that PUSCHi is a CBG-based transport, and the CBGTI value belongs to set A, then the transport block TB size of this PUSCHi is based on the DCI of the last time this TB was scheduled. j The TB size indicated in the DCI is determined. If the CBGTI value of the PUSCH indicated by the DCI belongs to set B, then the transport block TB size of this PUSCH is determined according to the TB size indicated in the DCI. The intersection of set A and set B is an empty set. If the DCI indicates that the PUSCH is a TB-based transport, then the transport block TB size of this PUSCH is determined according to the TB size indicated in the DCI. If the DCI that previously scheduled this TB scheduled one PUSCH, and the indicated MCS is a value from 0 to 27, then this DCI is a DCI. j If the last DCI that scheduled this TB scheduled M>1 PUSCHes and indicated a TB-based transport, or if the CBGTI value of this TB indicated by the DCI belongs to set B, then this DCI is a DCI. j .

[0159] Ideally, set B contains CBGTI with all values ​​being 0.

[0160] Ideally, set A contains all values ​​of CBGTI except for all zeros.

[0161] Ideally, set B contains CBGTI with all values ​​being 1.

[0162] Ideally, set A contains all values ​​of CBGTI except for all 1s.

[0163] For example, a DCI can schedule M>1 PUSCHs. This DCI contains bit fields indicating whether each PUSCH is based on TB or CBG transmission, a CBGTI indicating a CBG-based PUSCH, and an NDI (New Data Indicator) indicating each PUSCH. Assume set B contains CBGTI values ​​of all 1s, and set A contains all values ​​other than all 1s for CBGTI. If the DCI indicates that PUSCH PUSCH PUSCHi is a CBG-based PUSCH, and the CBGTI indicates that PUSCH PUSCHi contains only a portion of the CBGs in a TB (i.e., the CBGTI is neither all 0s nor all 1s), or the CBGTI indicates that PUSCH PUSCHi contains all the CBGs in a TB and the CBGTI value is all 0s, then the UE does not determine the TB size of PUSCH based on the MCS indicated by the current DCI, but rather determines the TB size based on the MCS information indicated by the previous DCI that scheduled this TB and contained TB size information. If the DCI indicates that PUSCHi in the M PUSCHs is a PUSCH based on TB transmission, or a CBG-based transmission with CBGTI set to all 1s, then the UE sends all CBGs of this TB and determines the TB size according to the MCS indicated by the current DCI.

[0164] Better, UE is based not only on DCI j Determine the TB size and according to DCI. j The indicated MCS determines the modulation scheme.

[0165] Preferred, UE is based on DCI j The TB size is determined, and the modulation scheme is determined based on the modulation scheme indication bit field of the current DCI. For example, a DCI contains an MCS bit field and a modulation scheme bit field. The TB size, modulation, and coding rate of the PUSCH scheduled by this DCI are determined based on the MCS bit field of this DCI, or the modulation scheme is determined based on the modulation scheme bit field of this DCI, the TB size is determined based on the MCS indicated by the DCIj, and the coding rate is determined based on the time-frequency resources indicated by this DCI.

[0166] In another aspect of this embodiment, when determining the TB size based on the MCS indicated by DCIj, if the time-frequency resources indicated by DCIj overlap with the time-frequency resources of SRS, then the time-frequency resources used to calculate the TB size are jointly determined based on the time-frequency resources indicated by DCIj and the time-frequency resources of SRS. For example, assuming the UE does not transmit PUSCH in the symbols transmitted by SRS, the number of symbols indicated by DCIj is M, of which N symbols overlap with SRS symbols, then the number of resources (REs) for each PRB used to calculate the TB size is N'. RE =N rb_sc*(MN)-Ndmrs-Nprb, where N rb_sc Ndmrs is the number of subcarriers within an RB, Nprb is the number of REs in the DMRS within each RB, and Nprb is a configured parameter. When determining the PUSCH transmission resources based on the indicated PUSCH time-frequency resources, if the SRS time-frequency resources and the indicated PUSCH time-frequency resources do not map the PUSCH in the symbols containing the SRS, the peak-to-average power ratio of the uplink signal can be reduced.

[0167] Example 8

[0168] In step 201, the downlink control information includes at least control information for scheduling M>1 PUSCHs. The DCI format used to carry the control information for scheduling M>1 PUSCHs is denoted as formats0-0B and formats0-1B.

[0169] In step 202, the uplink signal transmission action includes sending M PUSCHs according to the uplink scheduling information.

[0170] In existing technologies, when a search space is configured as a user-specific search space (USS), the configurable DCI format is formats0-0-And-1-0 or formats0-1-And-1-1. The DCI formats formats0-0, 1-0, 0-1, and 1-1 all support scheduling a single PDSCH or PUSCH. In new scenarios, it is necessary to support DCI formats that can schedule M>1 PDSCHs or PUSCHs. How to configure the search space for such DCI formats is a new problem. For ease of description, let's denote the DCI formats for scheduling a single PDSCH as formats1-0A and formats1-1A, and the DCI formats for scheduling multiple PDSCHs as formats1-0B and formats1-1B. Similarly, the DCI formats for scheduling a single PUSCH are formats0-0A and formats0-1A, and the DCI formats for scheduling multiple PUSCHs are formats0-0B and formats0-1B.

[0171] According to one implementation, when configuring the search space, the configurable DCI format includes at least a standard DCI format that schedules multiple PDSCHs or PUSCHs. The configurable DCI format also includes a standard DCI format that schedules a single PDSCH or PUSCH plus a standard DCI format that schedules a single PDSCH.

[0172] For example, when a search space is configured as a user-specific search space (USS), the configurable DCI formats are formats0-0-And-1-0, formats0-1A-And-1-1, or formats0-1B. Here, formats0-0 and 1-0 are fallback DCI formats, formats0-1A is a standard DCI format for scheduling a single PUSCH, 1-1 is a standard DCI format for scheduling a single PDSCH, and formats0-1B is a standard DCI format for scheduling multiple PUSCHs.

[0173]

[0174] Base stations can configure different USSs, for example, three USSs with corresponding DCI formats of formats0-0-And-1-0, formats0-1A-And-1-1, and formats0-1B, to provide both single-PUSCH scheduling and multi-PUSCH scheduling for the UE. Base stations can also schedule a single PUSCH by configuring only one USS. For example, configuring two USSs with corresponding DCI formats of formats0-0-And-1-0 and formats0-1A-And-1-1.

[0175] According to one implementation, when configuring the search space, the configurable DCI formats include at least the DCI formats for scheduling multiple PUSCHs and scheduling a single PDSCH, such as formats0-1B-And-1-1.

[0176] For example, when a search space is configured as a user-specific search space (USS), the configurable DCI format is formats0-0-And-1-0, or formats0-1A-And-1-1, or

[0177]

[0178] Base stations can configure different USS (User Servers) to provide UEs with single-PUSCH scheduling, multi-PUSCH scheduling, single-PUSCH scheduling, or multi-PUSCH scheduling. For example, three USS can be configured with corresponding DCI formats of formats0-0-And-1-0, formats0-1A-And-1-1, and formats0-1B-And-1-1. Alternatively, two USS can be configured with corresponding DCI formats of formats0-0-And-1-0 and formats0-1A-And-1-1. Or, two separate USS can be configured with corresponding DCI formats of formats0-0-And-1-0 and formats0-1B-And-1-1.

[0179] According to one implementation, when configuring the search space, the configurable DCI formats include at least a normal DCI format for scheduling multiple PDSCHs or PUSCHs, a normal DCI format for scheduling a single PUSCH, and a normal DCI format for scheduling a single PDSCH.

[0180] For example, when a search space is configured as a user-specific search space (USS), the configurable DCI format is formats0-0-And-1-0, or formats0-1A-And-1-1, or formats0-1B-And-1-1, or formats0-1B-And-formats0-1A-And1-1.

[0181]

[0182] Base stations can configure different USS (User Servers) to provide UEs with single-PUSCH scheduling, multi-PUSCH scheduling, single-PUSCH scheduling, or only multi-PUSCH scheduling. For example, configuring two USS with corresponding DCI formats of formats0-0-And-1-0 and formats0-1B-And-formats0-1A-And-1-1 allows for scheduling of both single and multiple PUSCHs via normal DCI, and single PUSCH scheduling via fallback DCI. Alternatively, configuring two USS with corresponding DCI formats of formats0-0-And-1-0 and formats0-1B-And-1-1 allows for scheduling of multiple PUSCHs via normal DCI and single PUSCH scheduling via fallback DCI. Or, configuring two USS with corresponding DCI formats of formats0-0-And-1-0 and formats0-1A-And-1-1 allows for scheduling of a single PUSCH via either normal DCI or fallback DCI.

[0183] In one implementation, when configuring the search space, you can configure which DCI formats can be skipped. For example, you can configure dci-Formats as formats0-0-And-1-0 or formats0-1-And-1-1, and configure which uplink DCI formats can be skipped using separate bit regions, such as either formats0-1A or formats0-1B.

[0184] Example 9

[0185] In step 201, the downlink control information is uplink scheduling information sent by the scheduling PUSCH, and the uplink scheduling information is carried by the uplink backoff DCI.

[0186] In step 202, the uplink signal transmission action includes determining the LBT subband based on the uplink scheduling information and transmitting PUSCH on the LBT subband.

[0187] To support flexible uplink resource allocation, the uplink scheduling information carried by the standard uplink DCI includes not only indications of interlacing resources but also indications of LBT subbands. For example, an uplink BWP bandwidth of 80MHz can be divided into four non-overlapping 20MHz LBT subbands. The standard uplink DCI includes a bit field indicating the interlacing number occupied by the PUSCH and another bit field indicating that the PUSCH occupies one or more of these four LBT subbands.

[0188] Optionally, both indications can be included in the uplink fallback DCI to achieve the same resource allocation flexibility. To ensure a fixed bit length for the uplink fallback DCI, the bit length used to indicate the LBT subband in this DCI is fixed, for example, fixed at log2. Where X is a standard predefined value, or X is determined based on the bandwidth of the BWP, for example, X = In a standard DCI, the bit length used to indicate the LBT subband is configurable; for example, X is configurable.

[0189] Optionally, the uplink fallback DCI does not include LBT subband indication. This saves DCI overhead and has little impact on system performance. According to one implementation, the PUSCH scheduled by this DCI corresponds to the entire bandwidth of the uplink BWP. For example, the active uplink BWP bandwidth is 80MHz, divided into 4 LBT subbands, and the corresponding active downlink BWP bandwidth is also 80MHz, divided into 4 LBT subbands. Regardless of which downlink LBT subband the UE receives the uplink fallback DCI scheduled PUSCH on, this PUSCH is located within the 80MHz bandwidth of the active uplink BWP; that is, one or more allocated intersections occupy a portion of the PRB in each of the 4 UL LBT subbands. As another example, the initial uplink BWP bandwidth is 20MHz, the same as the bandwidth of one LBT subband. The uplink fallback DCI scheduled PUSCH is located in one or more intersections within the 20MHz bandwidth of the initial uplink BWP. In another implementation, the LBT subband where the DCI-scheduled PUSCH resides is defined to have the same subband number as the LBT subband where the received DCI resides. For example, if the active uplink BWP bandwidth is 80MHz and divided into 4 LBT subbands, the corresponding active downlink BWP bandwidth is also divided into 4 LBT subbands. If the UE receives an uplink backoff DCI-scheduled PUSCH on DL LBT subband 1, then that PUSCH is located in UL LBT subband 1.

[0190] Optionally, the uplink backoff DCI located in the common search space does not include the LBT subband indicator, while the uplink backoff DCI in other search spaces includes the LBT subband indicator.

[0191] Optionally, when the uplink DCI needs to be truncated, the bit portion used to indicate interlacing is truncated first. Only when the truncated bit portion used to indicate interlacing is insufficient to meet the requirements is the LBT subband indicator truncated.

[0192] Optionally, when the uplink DCI needs to be truncated, the LBT subband indicator is truncated first. Only when the truncated bits used to indicate the LBT subband are insufficient to meet the requirements is the bit portion used to indicate the interlace truncated.

[0193] Example 10

[0194] In step 201, the downlink control information is the control information for configuring GUL PUSCH resources.

[0195] In step 202, the uplink signal transmission action includes the UE selecting the actual starting point for uplink transmission according to the control information configuring GUL PUSCH resources, and transmitting the GUL PUSCH according to the starting point.

[0196] The control information for GUL PUSCH resources includes GUL PUSCH timing resource information, such as the start symbol of the GUL PUSCH timing resource and / or GUL PUSCH candidate transmission start information. The GUL PUSCH candidate transmission start is determined based on the start symbol of the GUL PUSCH timing resource and the GUL PUSCH candidate transmission start information referenced to that start symbol. For example, the start symbol of the GUL PUSCH timing resource is the Mth symbol of an uplink slot n. The GUL PUSCH candidate transmission start information is a set of time offsets {X1, X2, X3…} relative to the start of the Mth symbol. Therefore, the GUL PUSCH candidate transmission start is selected from {X1, X2, X3…} starting from the Mth symbol and offsetting forward.

[0197] Optionally, step 202 may also include indicating the actual transmission start point in the uplink control information (UCI) in the GUL PUSCH.

[0198] After the UE selects a GUL PUSCH candidate transmission start point, it indicates the time offset of the actual transmission start point relative to the reference time point in the UCI, for example, the reference time point is the Mth symbol or the 1st symbol of the time slot.

[0199] For example, the base station configures the time resources for GUL PUSCH in symbols 5 to 14 of the nth time slot, and the time offset {X1, X2, X3…} = {16us, 25us, 34us, 43us, 52us, 61us, 70us}. Taking a subcarrier spacing of 30kHz as an example, based on the starting point of the GUL PUSCH time resource (the 5th symbol) and the GUL PUSCH candidate transmission starting point information {16us, 25us, 34us, 43us, 52us, 61us, 70us} relative to that starting symbol, the candidate transmission starting points for GUL PUSCH are determined to be {within the 5th symbol, within the 5th symbol, starting point of the 6th symbol, within the 6th symbol, within the 6th symbol, within the 6th symbol, starting point of the 7th symbol}. The UE selects a starting point from this set of candidate transmission points, for example, selecting 70us, i.e., the 7th symbol starting point, as the actual transmission starting point and transmits the GUL PUSCH.

[0200] If the UE indicates the actual transmission start point via the UCI of the GUL PUSCH, in this example, 2 bits are used to indicate which symbol the actual transmission start point is, or how many symbols the offset is relative to the 5th symbol. For example, '00' indicates an offset of less than 1 symbol and greater than 0 symbols relative to the 5th symbol, '01' indicates an offset of 1 symbol relative to the 5th symbol, '01' indicates an offset of less than 2 symbols and greater than 1 symbol relative to the 5th symbol, and '11' indicates an offset of 2 symbols relative to the 5th symbol.

[0201] Example 11

[0202] In step 201, the downlink control information includes at least the time resource information of the PUSCH.

[0203] In step 202, determining the uplink signal transmission action includes determining the PUSCH for transmitting uplink control information, and transmitting the PUSCH and the uplink control information.

[0204] The downlink control information includes a UL grant for scheduling PUSCH transmission, or the downlink control information includes scheduling information that triggers GUL PUSCH.

[0205] The uplink control information includes at least HARQ-ACK.

[0206] Preferably, the uplink control information includes at least channel information (CSI).

[0207] Preferably, the uplink control information includes at least a scheduling request (SR).

[0208] The uplink control information can be carried through PUCCH or PUSCH. For example, when the PUCCH resources of a UE's uplink control information overlap with the time resources of the UE's PUSCH, the uplink control information is carried on the PUSCH.

[0209] When a PUCCH resource overlaps with multiple PUSCH resources in time, if the processing latency is acceptable, uplink control information is typically carried on the first overlapping PUSCH in time, which reduces the latency of uplink control information. However, if the UE needs to perform LBT before sending this PUSCH, for example, if the PUSCH can only be sent if and only if the LBT is successful, sending uplink control information on the first overlapping PUSCH will reduce the probability of the UE sending uplink control information. Conversely, sending HARQ-ACK on the last overlapping PUSCH can greatly increase the probability of sending uplink control information. For example, the time resource of a PUCCH is the 3rd to 14th symbols of an uplink time slot. In the same time slot, the PUSCHs to be sent by the UE are PUSCH1 occupying the 3rd to 6th symbols, PUSCH2 occupying the 7th to 10th symbols, and PUSCH3 occupying the 11th to 14th symbols. Uplink control information is carried in PUSCH3. If the UE completes LBT before the start of PUSCH1, PUSCH2, or PUSCH3, the transmission of uplink control information can be guaranteed. Figure 11 If uplink control information is carried in PUSCH1, the UE will be unable to send uplink control information if it has not completed LBT before PUSCH1 begins.

[0210] Preferably, the processing method differs between unlicensed and licensed carriers. For example, on unlicensed carriers, uplink control information is transmitted on the last PUSCH overlapping with the PUCCH. On licensed carriers, uplink control information is transmitted on the first PUSCH overlapping with the PUCCH, or on the first PUSCH that meets the delay requirement.

[0211] Ideally, the base station indicates which processing method to use. For example, the base station configures the uplink control information via higher-layer signaling or via DCI, specifying whether to send the uplink control information on the last PUSCH overlapping with the PUCCH, the first PUSCH overlapping with the PUCCH, or the first PUSCH that meets the latency requirement.

[0212] Preferably, if the UE does not need to perform LBT before one or more PUSCHs that overlap with the PUCCH, the UE sends uplink control information on the first PUSCH that overlaps with the PUCCH, or on the first PUSCH that meets the delay requirement.

[0213] Preferably, if the UE does not need to perform LBT before one or more PUSCHs overlapping with the PUCCH (e.g., Cat-1 LBT), then the UE sends uplink control information on the first PUSCH overlapping with the PUCCH, or on the first PUSCH that meets the latency requirement. If the UE needs to perform LBT, then the UE sends uplink control information on the last PUSCH overlapping with the PUCCH.

[0214] Preferably, if the UE does not need to perform LBT before one or more PUSCHs that overlap with PUCCH, or performs Cat-2 LBT, such as 16us or 25us LBT, then the UE sends uplink control information on the first PUSCH that overlaps with PUCCH, or on the first PUSCH that meets the delay requirement.

[0215] Preferably, if the UE does not need to perform LBT before one or more PUSCHs overlapping with the PUCCH, or performs Cat-2 LBT (e.g., 16µs or 25µs LBT), then the UE sends uplink control information on the first PUSCH overlapping with the PUCCH, or on the first PUSCH that meets the latency requirement. If the UE needs to perform Cat-4 LBT, then the UE sends uplink control information on the last PUSCH overlapping with the PUCCH.

[0216] Preferably, if the UE performs Cat-4LBT before one or more PUSCHs that overlap with the PUCCH, the UE sends uplink control information on the last PUSCH that overlaps with the PUCCH.

[0217] Preferably, if at least one PUSCH overlapping with the PUCCH is located in the first time slot of an uplink burst, the PUSCH carrying uplink control information is determined in one of the ways described above.

[0218] Preferably, if at least one PUSCH overlapping with the PUCCH is located in the first time slot of an uplink burst, the UE sends uplink control information on the last PUSCH overlapping with the PUCCH; otherwise, the UE sends uplink control information on the first PUSCH overlapping with the PUCCH, or on the first PUSCH that meets the delay requirement.

[0219] Preferably, the PUSCH carrying uplink control information is determined according to one of the methods described above if and only if one or more PUSCHs overlapping with the PUCCH are PUSCH mapping scheme Type-B. Otherwise, the UE transmits uplink control information on the first PUSCH overlapping with the PUCCH, or on the first PUSCH that meets the delay requirement.

[0220] Example 12

[0221] In step 201, the downlink control information includes at least the SRS time resource information.

[0222] In step 202, determining that the uplink signal transmission action includes transmitting SRS with a selected time resource pattern.

[0223] The SRS time resource information indicated in the downlink control information may include time slots and / or symbol positions indicating the transmission of the SRS. The indication information includes at least one of the following time information:

[0224] (1) The time offset between the time slot where the SRS is sent and the time slot where the DCI that triggers the SRS is sent.

[0225] (2) The index of the starting symbol of the SRS sent. For example, if the starting symbol of the SRS is 0, it means that the starting symbol of the SRS is located at the last symbol of a time slot. If the starting symbol of the SRS is 5, it means that the starting symbol of the SRS is located at the 6th symbol from the end of a time slot.

[0226] (3) The time slot in which the SRS is transmitted is the same time slot as the PUSCH in which the DCI scheduling that triggers the SRS is located. Preferably, it can be used in conjunction with (2) to determine which symbol in the time slot the SRS begins to be transmitted.

[0227] (4) The start symbol of the transmitted SRS is adjacent to the end symbol of the PUSCH that triggered the DCI scheduling of the SRS. For example, if the PUSCH ends at the 4th symbol, then the start symbol of the SRS is the 5th symbol. Or, for example, if the PUSCH ends at the last symbol of slot 1, then the start symbol of the SRS is the first symbol of slot 2.

[0228] (5) The end symbol of the transmitted SRS is adjacent to the start symbol of the PUSCH that triggered the DCI scheduling of the SRS. For example, if the PUSCH starts at the 4th symbol, then the end symbol of the SRS is the 3rd symbol.

[0229] (6) The SRS sent is temporally adjacent to the PUSCH of the DCI scheduling that triggers the SRS. Preferably, it can be used in conjunction with (1) to determine the time slot of the SRS if the start or end symbol of the SRS in this time slot is determined to be temporally adjacent to the PUSCH.

[0230] (7) The time slot in which the SRS is transmitted is the same time slot as the PUCCH in which the DCI scheduling that triggers the SRS is located. Preferably, it can be used in conjunction with (2) to determine which symbol in the time slot the SRS begins to be transmitted.

[0231] (8) The start symbol of the SRS sent is adjacent to the end symbol of the PUCCH that triggers the DCI scheduling of the SRS.

[0232] (9) The end symbol of the SRS sent is adjacent to the start symbol of the PUCCH that triggers the DCI scheduling of the SRS.

[0233] (10) The SRS sent is time-adjacent to the PUCCH that triggers the DCI scheduling of the SRS. Preferably, it can be used in conjunction with (1) to determine the time slot of the SRS if the start or end symbol of the SRS in this time slot is determined to be time-adjacent to the PUCCH.

[0234] (11) If the PUSCH that triggers the DCI scheduling of the SRS is a PUSCH with M time slots, then the configured time slot offset is relative to the first time slot of the PUSCH, and the time slot offset is modulo M.

[0235] If the UE successfully occupies a channel through the first type of LBT, and then sends multiple uplink channels / signals within the COT, but these signals are not adjacent in time, the UE can perform the second type of LBT before sending the signals.

[0236] When configuring SRS resources, base stations can configure different time information for different SRS resources. Base stations can also configure different time information for different DCIs, such as the DCI for scheduling PUSCH, or the DCI for scheduling PDSCH, or the DCI dedicated to SRS.

[0237] The base station can indicate at least one of the above time information in the DCI by using a separate bit field or by reusing other bit fields.

[0238] If the SRS time resource information indicated in the downlink control information is X symbols consecutive in time, the UE will continuously transmit the remaining Y symbols starting from the most recent SRS symbol after completing LBT, where Y≤X.

[0239] The downlink control information indicates the SRS time resource information. If an SRS group contains N SRS resources (N>1), the UE can sequentially exchange the time order of the N SRS resources according to a predefined order each time it transmits the SRS group. For example, if an SRS group contains 4 SRS resources, each SRS resource is one symbol and they are adjacent to each other, and each SRS resource corresponds to a different transmit antenna port, namely antenna ports 0, 1, 2, and 3. Then, when the UE transmits this SRS group for the first time, it transmits the SRS of ports 0, 1, 2, and 3 sequentially on the 4 symbols; when it transmits this SRS group for the second time, it transmits the SRS of ports 1, 2, 3, and 0 sequentially on the 4 symbols; when it transmits this SRS group for the third time, it transmits the SRS of ports 2, 3, 0, and 1 sequentially on the 4 symbols; and when it transmits this SRS group for the fourth time, it transmits the SRS of ports 3, 0, 1, and 2 sequentially on the 4 symbols. The advantage of doing this is that when a set of SRS is sent, if one or more previous SRSs fail to be sent due to the late end time of LBT, they will be sent later in the next transmission, thus increasing the probability of successful transmission.

[0240] Example 13

[0241] In step 201, the downlink control information includes at least information that triggers HARQ-ACK transmission.

[0242] In step 202, determining the uplink signal transmission action includes determining the HARQ-ACK bit in the PUCCH and transmitting the PUCCH.

[0243] The information that triggers HARQ-ACK transmission includes carrier information for the HARQ-ACK to be fed back. For example, in the DCI that triggers HARQ-ACK feedback, a bitmap is used to determine whether each configured or active carrier needs to feed back HARQ-ACK. If the bit value for each carrier is X1, it indicates that the carrier needs to feed back HARQ-ACK; if the bit value is X2, it indicates that the carrier does not need to feed back HARQ-ACK. As another example, if higher-layer signaling configures a combination of multiple carriers, the DCI that triggers HARQ-ACK feedback indicates one of these combinations to determine which carriers need to feed back HARQ-ACK, and / or which carriers do not. Assume the base station configures M bits to indicate the HARQ-ACK feedback information for each carrier, corresponding to 2... MA combination of carrier information. If the indicated combination includes carrier i, the HARQ-ACK corresponding to carrier i needs to be fed back. For example, in a PUCCH group containing 4 downlink carriers, carriers 1 to 4, each carrier is configured with 16 HARQ processes. The base station configures 2 bits, with values ​​0 to 3 corresponding to the 4 carrier combinations. Carrier combination 1 includes carriers 1 and 2, carrier combination 2 includes carriers 2 and 3, carrier combination 3 includes carriers 3 and 4, and carrier combination 4 includes carriers 1 to 4. If the base station indicates carrier combination 1, the UE feeds back 16 HARQ processes for carriers 1 and 2, for a total of 32 bits of HARQ-ACK. If the base station indicates carrier combination 4, the UE feeds back 16 HARQ processes for carriers 1 to 4, for a total of 64 bits of HARQ-ACK.

[0244] Furthermore, based on the base station configuration or predefined rules, it can be determined whether each carrier i within a carrier feeds back HARQ-ACKs for all HARQ processes, or HARQ-ACKs for some HARQ processes of carrier i. For example, the base station can semi-statically configure the HARQ process groups for each carrier, with each HARQ process group containing one or more HARQ processes. In actual systems, the number of HARQ processes configured for each carrier may differ, and the configuration of the HARQ process groups may also differ. Preferably, the base station indicates that the HARQ process group indices for the same carrier group are the same. For example, in the DCI, there are two bit fields, one indicating the carrier group information and the other indicating the HARQ process group for that carrier group. Alternatively, when configuring carrier group information, the base station also configures the common HARQ process group for that carrier group; in the DCI, a single bit field indicates both the carrier group information and the HARQ process group. Preferably, the base station indicates that the HARQ process group indices for the same carrier group can be different. For example, when configuring carrier group information, the base station also configures the HARQ process groups for each carrier within that carrier group. In the DCI, a single bit field indicates both the carrier group information and the HARQ process groups. Taking four carriers as an example: Assume carrier 1 has four HARQ processes (0-3), and carrier 2 has sixteen HARQ processes (0-15). The base station configures four carrier groups: the first carrier group includes all HARQ processes for carrier 1; the second carrier group includes all HARQ processes for carrier 2; the third carrier group includes HARQ processes 0-1 for carrier 1 and HARQ processes 0-7 for carrier 2; and the fourth carrier group includes HARQ processes 2-3 for carrier 1 and HARQ processes 8-15 for carrier 2. Two bits in the DCI indicate one of these four carrier groups and one of the corresponding HARQ processes. The UE determines the HARQ-ACK bit in the PUCCH based on the configured carrier groups and HARQ processes, as well as the indication in the DCI.

[0245] Preferably, a specific DCI format is used to indicate the HARQ-ACK transmission information of a single UE, or the HARQ-ACK transmission information of multiple UEs. The bit length of the HARQ-ACK transmission information for each UE is configurable or predefined. For example, the carrier information bit field and / or the HARQ process group information bit field (all configured HARQ processes or HARQ process groups) in the HARQ-ACK transmission information bits of each UE, and / or the indication information bit field used to indicate whether the base station has received HARQ-ACK feedback from each HARQ process (e.g., each HARQ process, each HARQ process group, or each PDSCH group has a bit indication for indicating whether the UE should retransmit the HARQ-ACK of the PDSCH of this HARQ process, process group, or PDSCH group), can be configured separately, such as whether to include this bit field and the bit field length.

[0246] Example 14

[0247] In step 201, the downlink control information includes at least information that triggers HARQ-ACK transmission.

[0248] In step 202, determining the uplink signal transmission action includes determining the HARQ-ACK bit in the PUCCH and transmitting the PUCCH.

[0249] To support HARQ-ACK feedback based on dynamic codebooks, the downlink DCI for scheduling PDSCHs must include a bit field for HARQ-ACK feedback. To support HARQ-ACK retransmission, this bit field includes the PDSCH group index for HARQ-ACK feedback, the ACK-feedback group indicator for each group's HARQ-ACK feedback, the PDSCH set for the HARQ-ACK feedback request group, and the downlink assignment index (DAI). Multiple PDSCHs scheduled by the base station can be divided into one or more PDSCH groups. HARQ-ACKs for all PDSCHs within the same PDSCH group are fed back in the same PUCCH. The base station uses the PDSCH group index to indicate which PDSCH group the currently scheduled PDSCH belongs to. Each PDSCH group has an ACK-feedback group indicator to indicate whether the UE needs to report the HARQ-ACK information from the previous HARQ-ACK feedback in that group when reporting the HARQ-ACK for the current PDSCH. For example, if the ACK-feedback group indicator flips relative to the previous ACK-feedback group indicator for the same group, then the previous HARQ-ACK information does not need to be reported in the current feedback (the previous HARQ-ACK information may contain one or more HARQ-ACKs belonging to the same PDSCH group). If the ACK-feedback group indicator remains unchanged relative to the previous ACK-feedback group indicator for the same group, then the previous HARQ-ACK information needs to be reported in the current feedback. The PDSCH set of HARQ-ACK feedback request group information is the set of PDSCH groups that need to report HARQ-ACKs simultaneously in the same PUCCH. For example, the HARQ-ACK feedback request group information includes HARQ-ACK feedback triggered only for the currently scheduled PDSCH group, HARQ-ACK feedback from the currently scheduled PDSCH group and at least one other group, and HARQ-ACK feedback from all PDSCH groups. The HARQ-ACK feedback from the currently scheduled PDSCH group and at least one other group is a standard predefined combination or configured via higher-level signaling. As another example, the HARQ-ACK feedback request group information may also include HARQ-ACK feedback from all HARQ processes.For example, the HARQ-ACK feedback request group information also includes triggering HARQ-ACK feedback for only one or more PDSCH groups other than the currently scheduled PDSCH group. Taking two PDSCH groups as an example, the 1-bit HARQ-ACK feedback request group information indicates that '0' triggers the currently scheduled PDSCH group, and '1' indicates both PDSCH groups. Alternatively, the 2-bit HARQ-ACK feedback request group information indicates that '00' triggers the currently scheduled PDSCH group, '01' triggers both PDSCH groups, and '10' triggers PDSCH for all HARQ processes.

[0250] Assuming the base station schedules multiple PDSCHs, each can be divided into at most two PDSCH groups, with each PDSCH group index being 0 or 1. For each PDSCH group, there is a 1-bit ACK-feedback group indicator, and the 1-bit PDSCH set value of 0 indicates that only the HARQ-ACK of the current PDSCH group is fed back, while 1 indicates that HARQ-ACKs of both PDSCH groups are fed back. Within each group, the number of HARQ-ACK bits and the HARQ-ACK bit ranking for each group are determined based on the count DAI (C-DAI) and total DAI (T-DAI) in the DCI. Based on the above bit field indications used for HARQ-ACK feedback, the base station can flexibly support HARQ-ACK retransmissions of multiple PDSCH groups. The corresponding cost is a large DCI overhead, especially when there are many PDSCH groups, for example, with 4 PDSCH groups, the overhead is as high as 13 bits (PDSCH group index 2 bits, ACK-feedback group indicator 4 bits, PDSCH set 3 bits, DAI 4 bits). Including all these bit fields in the downlink fallback DCI would lead to a decrease in detection performance and affect the robustness of the system.

[0251] To achieve a trade-off between robustness and flexibility, different HARQ-ACK feedback bit domains can be designed for ordinary DCI and back-off DCI.

[0252] Optionally, to ensure flexibility, the number of PDSCH groups supported in the normal downlink DCI can be configured, or fixed to a number larger than the number of PDSCH groups supported by the backoff DCI. For example, the base station can configure the number of PDSCH groups supported in the normal downlink DCI to be 2, 3, or 4. Correspondingly, the total number of bits is 8 bits (PDSCH group index 1 bit, ACK-feedback group indicator 2 bits, PDSCH set 1 bit, DAI 4 bits), 11 bits (PDSCH group index 2 bits, ACK-feedback group indicator 3 bits, PDSCH set 2 bits, DAI 4 bits), and 13 bits (PDSCH group index 2 bits, ACK-feedback group indicator 4 bits, PDSCH set 3 bits, DAI 4 bits).

[0253] Optionally, the bit fields used for HARQ-ACK feedback in the downlink backoff DCI are predefined. The number of bit fields and / or bits related to PDSCH packets used for HARQ-ACK feedback in the downlink backoff DCI is less than the number of bit fields and / or the maximum number of bits related to PDSCH packets used for HARQ-ACK feedback in the normal DCI. For example, the bit fields related to PDSCH packets used for HARQ-ACK feedback in the downlink backoff DCI may only contain C-DAI, or only contain C-DAI and ACK-feedback group indicator, or only contain C-DAI, PDSCH group index, and ACK-feedback group indicator, while the bit fields related to PDSCH packets used for HARQ-ACK feedback in the normal DCI may contain PDSCH group index, ACK-feedback group indicator, PDSCH group set, and DAI.

[0254] According to one example, the downlink backoff DCI includes a 1-bit PDSCH group index, where 0 represents PDSCH group 0 and 1 represents PDSCH group 1; or, it does not include a PDSCH group index, and the PDSCH scheduled by the downlink backoff DCI belongs to a predefined PDSCH group, such as PDSCH group 0. In addition, the downlink backoff DCI also includes a 1-bit ACK-feedback group indicator, corresponding to the current PDSCH group. It does not include a bit field indicating the PDSCH set, i.e., it assumes that only HARQ-ACK feedback is fed back for the PDSCH group to which the current PDSCH belongs. It also only includes C-DAI. Optionally, for the same PUCCH, if the UE only receives PDSCHs scheduled by the downlink backoff DCI, the UE determines the HARQ-ACK feedback only based on the bit fields in the downlink backoff DCI, and only feeds back the HARQ-ACK for the PDSCH group to which the current PDSCH belongs. For the same PUCCH, if the UE receives both downlink back-off DCI scheduled PDSCH and normal DCI scheduled PDSCH, then the PDSCH group set for HARQ-ACK feedback and the ACK-feedback group indicator for each PDSCH are determined according to the PDSCH set indicated in the normal DCI.For example, the base station schedules PDSCH 1 via normal DCI 1, indicating PDSCH groupindex = "00", ACK-feedback group indicator = "0000", PDSCH set = "000" (indicating only feedback for the current PDSCH group 0), C-DAI = 1, T-DAI = 1. The base station schedules PDSCH 2 via backoff DCI 2, indicating ACK-feedback group indicator = "0", C-DAI = 2 (PDSCH2 belongs to the predefined PDSCH group 0, therefore PDSCH 1 and PDSCH2 belong to the same PDSCH group, the C-DAI of PDSCH2 is accumulated based on PDSCH 1, and the ACK-feedback group indicator of PDSCH2 indicates that HARQ-ACK for both PDSCH1 and PDSCH2 in PDSCH group 0 needs to be fed back). The base station schedules PDSCH 3 via normal DCI 3, indicating PDSCH group index = "01", ACK-feedback group... With indicator = "0000", PDSCH set = "001" (indicating feedback of the current PDSCH group 1 and the previous PDSCH group 0), C-DAI = 1, T-DAI = 1, then when the UE receives DCI 3, it will send HARQ-ACKs for PDSCH1, PDSCH2, and PDSCH3 in the same PUCCH. If the UE does not receive DCI 3 and DCI 1, but only receives DCI 2, then the UE will only send a 2-bit HARQ-ACK for PDSCH group 0 in the same PUCCH, where the HARQ-ACK for PDSCH2 corresponds to the second bit.

[0255] According to another example, the downlink backoff DCI includes a 1-bit PDSCH group index, where 0 represents PDSCH group 0 and 1 represents PDSCH group 1, or it may not contain a PDSCH group index and is fixed to a predefined PDSCH group. It does not indicate the PDSCH set or the ACK-feedback group indicator, and only supports HARQ-ACK feedback for the PDSCH group to which the current PDSCH belongs. It also only includes C-DAI. Optionally, for the same PUCCH, if the UE only receives the downlink backoff DCI-scheduled PDSCH, the UE determines the HARQ-ACK feedback based solely on the bit fields in the downlink backoff DCI, only feeding back the HARQ-ACK for the PDSCH group to which the current PDSCH belongs, and assumes the ACK-feedback group indicator is in a flipped state, meaning there is no need to retransmit previous HARQ-ACKs. For the same PUCCH, if the UE receives both downlink back-to-back DCI scheduled PDSCH and normal DCI scheduled PDSCH, then the PDSCH group(s) for HARQ-ACK feedback is determined according to the PDSCH group indicated in the normal DCI, and whether each PDSCH group needs to be retransmitted for HARQ-ACK is determined according to the ACK-feedback group indicator of each PDSCH group.

[0256] According to another example, the downlink backoff DCI includes C-DAI but does not include the PDSCH group index, ACK-feedback group indicator, or PDSCH set. Optionally, PDSCHs scheduled by the downlink backoff DCI that do not contain HARQ-ACK feedback bit fields related to PDSCH groups are processed according to the fact that the PDSCH belongs to the first PDSCH group (equivalent to PDSCH groupindex = 0) and the ACK-feedback group indicator is toggled, and only HARQ-ACKs for this group of PDSCHs can be fed back, not HARQ-ACKs for other PDSCH groups. Optionally, for the same PUCCH, if the UE only receives downlink backoff DCIs, and the PDSCHs scheduled by these downlink backoff DCIs belong to the same PDSCH group 0, the UE determines the PUCCH only based on the HARQ-ACK feedback timing K1 indicated in the downlink backoff DCI, and determines the number of HARQ-ACK bits fed back in the same PUCCH for PDSCH group 0 based on the C-DAI in the downlink backoff DCI and the assumption that the ACK-feedback group indicator is toggled. Optionally, for the same PUCCH, if the UE receives both a downlink back-off DCI and a DCI containing HARQ-ACK feedback bit fields related to PDSCH packets, the UE determines the HARQ-ACK feedback based on the latter's HARQ-ACK feedback bit fields related to PDSCH packets. For example, in time slot n, the base station schedules PDSCH 1 via ordinary DCI 1, K1=4, indicating PDSCH group index="00", ACK-feedback group indicator="0000", PDSCH set="000" (indicating only feedback of the current PDSCH group 0), C-DAI=1, T-DAI=1. In time slot n+1, the base station schedules PDSCH 2 via backoff DCI 2, K1=3, indicating C-DAI=2. In time slot n+8, the base station schedules PDSCH 3 via ordinary DCI 3, K1=2, indicating PDSCH group index="01", ACK-feedback group indicator="0000", PDSCH set="001" (indicating feedback of the current PDSCH group 1 and PDSCH group 0), C-DAI=1, T-DAI=1.Since PDSCH1 and PDSCH2 belong to the same PDCCH group 0, and according to K1, the HARQ-ACKs for these two PDSCHs are sent in the same PUCCH, the UE sends HARQ-ACKs for PDSCH1 and PDSCH2 in time slot n+4. After the UE receives DCI3 in time slot n+8, the UE sends back HARQ-ACKs for PDSCHs 1, 2, and 3 in time slot n+10. For example, in time slot n, the base station schedules PDSCH 1 via ordinary DCI 1, K1=4, indicating PDSCH group index="10", ACK-feedback group indicator="0000", PDSCH set="000" (indicating only feedback of the current PDSCH group 0), C-DAI=1, T-DAI=1. In time slot n+7, the base station schedules PDSCH 2 via backoff DCI 2, K1=3, indicating C-DAI=1. In time slot n+8, the base station schedules PDSCH 3 via ordinary DCI 3, K1=2, indicating PDSCH group index="00", ACK-feedback group indicator="0000", PDSCH set="011" (indicating feedback of the current PDSCH group 0 and PDSCH group 2), C-DAI=2, T-DAI=2. Therefore, when the UE receives DCI 3, it determines that both PDSCH 2 and PDSCH 3 belong to PDSCH group 0, and based on K1, they belong to the same PUCCH. According to the indication in DCI 3, the UE sends HARQ-ACKs for PDSCH 1, PDSCH 2, and PDSCH 3 within the same PUCCH. If the UE does not receive DCI 3 and only receives DCI 2, then the UE sends only a HARQ-ACK for PDSCH 2 within the PUCCH.

[0257] Optionally, the bit fields used for HARQ-ACK feedback included in the downlink backoff DCI of the secondary cell and the primary cell are different. Optionally, the downlink backoff DCI format of the secondary cell includes the PDSCH group index for HARQ-ACK feedback, the ACK-feedback group indicator for the current PDSCH group, or only the PDSCH group index, or only the ACK-feedback group indicator. The downlink backoff DCI format of the primary cell does not include either of the above two types of information. For example, in the downlink backoff DCI format 1-0 of the secondary cell, it includes a 1-bit PDSCH group index, a 1-bit ACK-feedback group indicator for the current PDSCH group, and 2 bits of C-DAI. In the DCI format 1-0 of the primary cell, it only includes 2 bits of C-DAI.

[0258] Furthermore, the downlink backoff DCI in the common search space of the primary cell does not include the HARQ-ACK feedback bit field related to PDSCH packets, and the downlink backoff DCI in the user search space of the primary cell has the same HARQ-ACK feedback bit field composition as the downlink backoff DCI format of the secondary cell.

[0259] Alternatively, the downlink backoff DCI in the common search space of the primary cell's initial BWP does not include the HARQ-ACK feedback bit field related to PDSCH packets, and the other downlink backoff DCIs of the primary cell have the same HARQ-ACK feedback bit field composition as the downlink backoff DCI format of the secondary cell.

[0260] Optionally, the bit fields for HARQ-ACK feedback included in the downlink backoff DCI in the public search space differ from those included in the downlink backoff DCI in the user-specific search space. The downlink backoff DCI in the public search space contains fewer bit fields for HARQ-ACK feedback than the downlink backoff DCI in the user search space. For example, the downlink backoff DCI in the user search space includes the PDSCH group index for HARQ-ACK feedback, the ACK-feedback group indicator for the current PDSCH group, and C-DAI; the downlink backoff DCI in the public search space only includes C-DAI; or, the bit fields for HARQ-ACK feedback include the PDSCH group index and C-DAI, or the ACK-feedback group indicator and C-DAI.

[0261] Employing different designs for downlink backoff DCI in different search spaces and / or different cells can reduce the overhead of downlink backoff DCI used for scheduling system information and PDSCH before RRC connection establishment. System information does not require HARQ-ACK feedback, therefore the bit fields in the DCI used for HARQ-ACK feedback are redundant. HARQ-ACK for PDSCH before RRC connection establishment does not require PDSCH packets, therefore the bits related to PDSCH packets in the bit fields used for HARQ-ACK feedback are also redundant. Reducing the bit overhead for HARQ-ACK feedback in the downlink backoff DCI of the primary cell or a specific search space of the primary cell can improve efficiency.

[0262] To distinguish between downlink backoff DCI containing HARQ-ACK feedback bit fields related to PDSCH packets and downlink backoff DCI containing HARQ-ACK feedback bit fields related to PDSCH packets, two different DCI formats can be defined, or the same DCI format can be used with restrictions on the conditions under which specific bit fields appear in this DCI format.

[0263] Example 15

[0264] In step 201, the downlink control information includes at least information that triggers HARQ-ACK transmission.

[0265] In step 202, the uplink signal transmission action includes transmitting the GUL PUSCH according to the determined end position of the GUL PUSCH.

[0266] The information that triggers the HARQ-ACK transmission includes information on the resources of the uplink channel that will carry the HARQ-ACK. This may include HARQ-ACK timing information and PUCCH resource information.

[0267] If the UE transmits a PUCCH on carrier i based on the received HARQ-ACK transmission information, and the UE is transmitting a GUL PUSCH on another carrier j, then the UE needs to stop transmitting this GUL PUSCH before time t. Time t is determined based on the reference start point of the PUCCH to be transmitted on carrier i and a predefined time difference. For example, the reference start point of the PUCCH is the start point of the first symbol of the PUCCH, or the start point of the time slot or sub-time slot containing the first symbol of the PUCCH. The predefined time difference is X time units, which can be a symbol, a time slot / sub-time slot, a CCA time slot, or a microsecond / millisecond, etc. Time t is X time units prior to the reference start point of the PUCCH. Preferably, if time t does not belong to a candidate end position of the GUL PUSCH, then the GUL PUSCH transmission stops at a candidate end position of the GUL PUSCH earlier than time t. For example, the reference start point of the PUCCH is the PUCCH start point, located at symbol #10 of time slot n, with a time difference X of 2 OFDM symbols. The candidate end positions of the GUL PUSCH are symbols #12 and #13. Therefore, the time t determined by the PUCCH reference start point and X is symbol #8 of time slot n, meaning the GUL PUSCH must stop transmitting before the start of symbol #8 in time slot n. However, since symbol #8 is not a candidate position for the GUL PUSCH, the UE can only stop transmitting the GUL PUSCH at symbol #12 or #13 of time slot n-1.

[0268] Ideally, X is predefined or configured by the base station.

[0269] Preferably, if the UE will send a PUSCH on carrier i according to the downlink control information UL grant received in step 201, and the UE is sending a GUL PUSCH on another carrier j, then the UE needs to stop sending this GUL PUSCH before time t1.

[0270] According to another aspect of this embodiment, in step 201, the downlink control information includes at least information about PRACH resources.

[0271] In step 202, the uplink signal transmission action includes transmitting the GUL PUSCH according to the determined end position of the GUL PUSCH.

[0272] If the UE will transmit a PRACH on carrier i based on the received PRACH resource information, and the UE is transmitting a GUL PUSCH on another carrier j, then the UE needs to stop transmitting this GUL PUSCH before time t. The method for determining time t is similar to that described above and will not be repeated.

[0273] Preferably, the time point for stopping GUL PUSCH transmission varies depending on the uplink channel to be transmitted on carrier i, or the content carried by the uplink channel. For example, if the uplink channel to be transmitted on carrier i is PUCCH, or a PUSCH carrying only uplink control information, or a PRACH, the time difference used to determine the stopping time of GUL PUSCH transmission is X. If the uplink channel to be transmitted on carrier i is a PUSCH carrying data, the time difference used to determine the stopping time of GUL PUSCH transmission is X1, where X is not equal to X1, or X and X1 are independently configured.

[0274] Example 16

[0275] In step 201, the downlink control information includes at least an uplink scheduling indication UL grant for scheduling PUSCH.

[0276] In step 202, the uplink data channel signal transmission action includes determining the channel access procedure type before uplink signal transmission, and performing LBT according to the channel access procedure type before transmitting the uplink signal.

[0277] An uplink scheduling indication (UL grant) can schedule only one PUSCH. Alternatively, a UL grant can schedule the transmission of M PUSCHs, where 1 ≤ M ≤ Mmax, and Mmax is the maximum number of PUSCHs that can be scheduled by a UL grant. Mmax is predefined by the standard or configured by the base station.

[0278] Transmitting signals on unlicensed frequency bands typically requires a channel access procedure before transmission. Channel access procedures can be of several types, such as Type I (see section 4.2.1.1 of standard TS 37.213), Type II (e.g., 16µs LBT or 25µs LBT, see section 4.2.1.2 of standard TS 37.213), and Type III (no carrier detection / LBT required). Each type of channel access procedure corresponds to a different scenario, and the transmitting end must determine the appropriate channel access procedure type based on the specific scenario. For example, when a base station occupies a channel through a Type I access procedure, if the time interval between downlink transmission and subsequent uplink transmission within the downlink COT is equal to 16µs, a Type II access procedure with a 16µs LBT can be performed before uplink transmission. If the time interval between downlink transmission and subsequent uplink transmission within the downlink COT is greater than or equal to 25µs, a Type II access procedure with a 25µs LBT can be performed before uplink transmission. If the uplink transmission is not within the downlink COT, a Type I access procedure is performed before uplink transmission.

[0279] In one implementation, the base station indicates the channel access procedure type in the UL grant for scheduling the PUSCH. Before sending the PUSCH, the UE performs channel access according to this channel access procedure type. For example, 2 bits in the UL grant indicate the first type of access procedure, the 16us LBT of the second type of access procedure, the 25us LBT of the second type of access procedure, and the third type of access procedure, respectively.

[0280] If the UE is scheduled to send these PUSCHs in a continuous time resource by a UL grant that can simultaneously schedule M>1 PUSCHs, and if the channel access type indicated in the UL grant is a specific channel access type A, and if the UE fails to access the channel before the j-th PUSCH is sent, then the UE cannot access the channel according to the indicated channel access type A before the (j+1)-th PUSCH is sent, but will access the channel according to channel access type B.

[0281] A preferred approach is a second-type channel access procedure with channel access type A of 16µs.

[0282] The preferred channel access type B is the second type channel access procedure and the first type channel access procedure, which are both 25µs.

[0283] For example, if a UE is scheduled to send M>1 PUSCHs simultaneously in a continuous time resource by a UL grant, and if the channel access type indicated in the UL grant is 16us LBT of the Type II access procedure, and if the UE fails to access the channel before the j-th PUSCH is sent, then the UE cannot access the channel according to the indicated 16us LBT of the Type II access procedure before the (j+1)-th PUSCH is sent, but instead accesses the channel according to the 25us LBT of the Type II access procedure.

[0284] If the UE is scheduled to transmit these PUSCHs in a continuous time resource by a UL grant that can simultaneously schedule M>1 PUSCHs, and if the channel access type indicated in the UL grant is a specific channel access type C, and if the UE fails to access the channel before the j-th PUSCH is transmitted, then the UE will access the channel according to the channel access type C indicated in the UL grant before the (j+1)-th PUSCH is transmitted.

[0285] The preferred channel access types are the second type, the first type, and the third type, with a channel access type C of 25µs.

[0286] Once the UE successfully completes channel access before sending the (j+1)th PUSCH, it can continuously send the remaining PUSCHs after starting to send the (j+1)th PUSCH, with no time gap between these PUSCHs.

[0287] Based on the above methods, the following examples are given:

[0288] The base station occupies the channel through a Type I channel access procedure, starting downlink transmission in time slot n, and the downlink COT continues until the end of time slot n+6. In time slot n+1, the base station sends a UL grant scheduling M = 4 PUSCHs, where the first PUSCH starts from the 8th symbol of time slot n+3 and continues until the end of time slot n+3. The 2nd to 4th PUSCHs occupy each complete time slot from n+4 to n+6, and these 4 PUSCHs are sequential in time. Since the interval between the end of the downlink transmission in the first half of time slot n+3 and the start of the first PUSCH is 16µs, the base station indicates in the UL grant that the channel access type is a Type II access procedure with a 16µs LBT. Before sending the first PUSCH, the UE performs a Type II access procedure with a 16µs LBT. If the LBT is successful, the UE continuously sends the 4 scheduled PUSCHs. If the UE fails to perform a 16us LBT before sending the first PUSCH, it cannot perform a 16us LBT before attempting to send the second PUSCH, but can perform a 25us LBT for the Type 2 access procedure. If the UE successfully performs a 25us LBT before attempting to send the second PUSCH, it can continuously send PUSCH 2 through PUSCH 4. If the UE fails to perform a 25us LBT before attempting to send the second PUSCH, it performs a 25us LBT before attempting to send the third PUSCH. If successful, it can continuously send PUSCH 3 and PUSCH 4, and so on. If the UE still fails to perform a 25us LBT before attempting to send the fourth PUSCH, it cannot send any of PUSCH 1 through PUSCH 4. In this example, if the UE fails to perform a 16us LBT before sending the first PUSCH, the time difference between the start of the next uplink signal transmission and the end of the downlink transmission in the first half of time slot n+3 is greater than 16us, therefore a 16us LBT cannot be performed. Meanwhile, since the start and end points of the next uplink signal transmission for the UE both fall within the same downlink COT, the UE can perform Type II 25µs LBT. In some practical scenarios, if the start or end point of the next uplink signal transmission for the UE is outside the downlink COT, the UE needs to perform Type I channel access. For example, the base station occupies the channel through Type I channel access, starting downlink transmission in time slot n, and the downlink COT lasts until the end of time slot n+6. The base station transmits a UL grant scheduling M = 4 PUSCHs in time slot n+1, where the first PUSCH starts from the 8th symbol of time slot n+3 and continues until the end of time slot n+3. The 2nd to 4th PUSCHs occupy each complete time slot from n+4 to n+6, and these 4 PUSCHs are sequential in time.If the base station indicates in the UL grant that the channel access type is Type 3 access procedure, then the UE does not need to perform LBT and can directly send these 4 PUSCHs continuously starting from the first PUSCH. For example, if the base station indicates in the UL grant that the channel access type is Type 2 access procedure 25us LBT, then the UE will attempt 25us LBT before the first PUSCH. If successful, it will send 4 PUSCHs continuously; if unsuccessful, it will attempt 25us LBT again before the second PUSCH, and so on.

[0289] In another implementation, the base station cannot indicate a specific channel access type A in a UL grant that schedules M > 1 PUSCH. Instead, the base station can only indicate one specific channel access type C in a UL grant that schedules M > 1 PUSCH. Then, the UE processes the request according to the behavior described above for channel access type C. This method has certain scheduling limitations, but the base station can still indicate a specific channel access type A by scheduling a UL grant for a single PUSCH. This method is relatively simple to implement.

[0290] Similarly, a base station can schedule multiple temporally consecutive PUSCHs through multiple UL grants. When the base station indicates the same channel access type in each UL grant, if the indicated channel access type is a specific channel access type A, and if the UE fails to access the channel before the j-th PUSCH is sent, then the UE cannot access the channel according to the indicated channel access type A before the (j+1)-th PUSCH is sent, but will access the channel according to channel access type B. If the indicated channel access type is a specific channel access type C, and if the UE fails to access the channel before the j-th PUSCH is sent, then the UE will access the channel according to the channel access type C indicated in the UL grant before the (j+1)-th PUSCH is sent.

[0291] For example, if a base station sends four UL grants, each scheduling one PUSCH, and the time resources of these four PUSCHs are contiguous, assuming that the channel access type information indicated in the UL grants of PUSCHs with contiguous time resources must be identical, then when the base station indicates the channel access type in these UL grants as a 16us LBT of the Type II access procedure, if the UE fails to access the channel before the first PUSCH is sent, the UE cannot access the channel according to the indicated 16us LBT of the Type II access procedure before the second PUSCH is sent; instead, it will access the channel according to the 25us LBT of the Type II access procedure. In this case, the UE can automatically switch to a more conservative channel access type than the indicated one. If the channel access type indicated in the UL grant is Type I, Type II 25us LBT, or Type III, then after failing to access the channel before the first PUSCH, the UE will attempt to send the next PUSCH according to the channel access type indicated in the UL grant. If channel access is successfully completed before the start of the next PUSCH, the remaining PUSCHs will be sent continuously. If it is assumed that the channel access type information indicated in the UL grant of PUSCHs with continuous scheduling time resources can be different, channel access is performed according to the channel access type indicated in the UL grant of scheduling the j-th PUSCH before the start of the j-th PUSCH. If successful, the remaining PUSCHs are sent starting from the j-th PUSCH, without the need for LBT in between.

[0292] The above description is only a partial embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method performed by a terminal in a communication system, the method comprising: detecting a first downlink control information (DCI) format and a second DCI format scheduling physical downlink shared channel (PDSCH) reception, wherein a first hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback timing information is included in the first DCI format, a second HARQ-ACK feedback timing information and PDSCH grouping related information are included in the second DCI format, the first HARQ-ACK feedback timing information and the second HARQ-ACK feedback timing information indicate a same physical uplink control channel (PUCCH); generating HARQ-ACK information corresponding to PDSCHs scheduled by the first DCI format and the second DCI format based on the PDSCH grouping related information in the second DCI format; transmitting the HARQ-ACK information in the PUCCH.

2. The method of claim 1, wherein, The PDSCH grouping related information includes at least one of the following: a second PDSCH grouping index, HARQ-ACK feedback indication information corresponding to PDSCH grouping, a number of requested PDSCH groupings.

3. The method of claim 2, wherein, If the HARQ-ACK feedback indication information corresponding to PDSCH grouping is different from a previous HARQ-ACK feedback indication information of the PDSCH grouping, the previous HARQ-ACK information of the PDSCH grouping is not retransmitted.

4. The method of claim 2, wherein, The number of requested PDSCH groupings is 1 or 2. 5.The method of claim 1, further comprising: if only the first DCI format is detected, generating HARQ-ACK information based on a bit field in the first DCI format. 6.The method of claim 1, a PDSCH index of the PDSCH scheduled by the first DCI format is set to a fixed value.

7. The method of claim 6, wherein, The fixed value is 0. 8.The method of claim 1, the method further comprising: receiving, through higher layer signaling, first configuration information indicating a symbol of a first slot as a flexible symbol; receiving, through higher layer signaling, second configuration information configuring the terminal to transmit an uplink channel and / or an uplink signal in the symbol of the first slot; if the terminal does not receive downlink control information (DCI) providing a slot format indicator (SFI) of the first slot, transmitting the uplink channel and / or the uplink signal based on information of a configured uplink transmission attempt by a base station.

9. The method of claim 8, wherein, The uplink channel and / or the uplink signal include one or more of a physical uplink shared channel (PUSCH), a sounding reference signal (SRS), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH). 10.The method of claim 1, the method further comprising: receiving a third DCI format for scheduling a physical uplink shared channel (PUSCH); determining resources of the PUSCH based on the third DCI format; transmitting the PUSCH on the determined resources, The determining the resource of the PUSCH comprises determining a listen before talk (LBT) subband, The resource of the PUSCH is determined based on whether the third DCI format is located in a common search space or a terminal-specific search space.

11. The method of claim 10, wherein: in a case that the third DCI format is located in the common search space, the third DCI format does not comprise an LBT subband indication; and / or in a case that the third DCI format is located in the terminal-specific search space, the third DCI format comprises an LBT subband indication.

12. The method of claim 11, wherein: in a case that the third DCI format is located in the terminal-specific search space, the resource of the PUSCH is determined based on the LBT subband indication.

13. A method performed by a base station in a communication system, the method comprising: transmitting a first downlink control information (DCI) format and a second DCI format scheduling a physical downlink shared channel (PDSCH), wherein a first hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback timing information is comprised in the first DCI format, a second HARQ-ACK feedback timing information and information related to PDSCH grouping are comprised in the second DCI format, the first HARQ-ACK feedback timing information and the second HARQ-ACK feedback timing information indicate a same physical uplink control channel (PUCCH); and receiving, in the PUCCH, HARQ-ACK information corresponding to the PDSCH scheduled by the first DCI format and the second DCI format, wherein the HARQ-ACK information is generated based on the information related to PDSCH grouping in the second DCI format.

14. The method of claim 13, wherein, The information related to PDSCH grouping comprises at least one of: a second PDSCH grouping index, HARQ-ACK feedback indication information corresponding to PDSCH grouping, a number of requested PDSCH groupings.

15. The method of claim 13, wherein, If the HARQ-ACK feedback indication information corresponding to a PDSCH grouping is different from a previous HARQ-ACK feedback indication information of the PDSCH grouping, the previous HARQ-ACK information of the PDSCH grouping is not retransmitted.

16. The method of claim 13, wherein, The number of requested PDSCH groupings is 1 or 2.

17. The method of claim 13, wherein, If only the first DCI format is detected, the HARQ-ACK information is generated based on a bit field in the first DCI format.

18. The method of claim 13, a PDSCH index of the PDSCH scheduled by the first DCI format is set to a fixed value.

19. The method of claim 18, wherein, The fixed value is 0.

20. The method of claim 13, the method further comprising: transmitting, to a terminal, first configuration information indicating a symbol of a first time slot as a flexible symbol through higher layer signaling; transmitting, to the terminal, second configuration information configuring the terminal to transmit an uplink channel and / or an uplink signal in the symbol of the first time slot through higher layer signaling; receive the uplink channel and / or uplink signal, wherein the uplink channel and / or uplink signal is transmitted based on information of a base station configured attempted uplink transmission if the DCI providing the SFI of the first time slot is not received by the terminal.

21. The method of claim 20, wherein, The uplink channel and / or uplink signal comprises one or more of: a physical uplink shared channel (PUSCH), a sounding reference signal (SRS), a physical uplink control channel (PUCCH), a physical random access channel (PRACH).

22. The method of claim 13, further comprising: transmitting a third DCI format, the third DCI format being for scheduling a physical uplink shared channel (PUSCH); receiving the PUSCH on resources of the PUSCH, wherein the resources of the PUSCH are determined based on the third DCI format, wherein determining the resources of the PUSCH comprises determining a listen before talk (LBT) subband, wherein the resources of the PUSCH are determined based on whether the third DCI format is located in a common search space or a terminal-specific search space.

23. The method of claim 22, wherein: in a case that the third DCI format is located in the common search space, the third DCI format does not comprise an LBT subband indication; and / or in a case that the third DCI format is located in the terminal-specific search space, the third DCI format comprises an LBT subband indication.

24. The method of claim 22 or 23, wherein: in a case that the third DCI format is located in the terminal-specific search space, the resources of the PUSCH are determined based on the LBT subband indication.

25. A terminal in a communication system, the terminal comprising: a transceiver; and a controller configured to perform the method of any of claims 1-12.

26. A base station in a communication system, the base station comprising: a transceiver; and a controller configured to perform the method of any of claims 13-24.

Images