Transmission method and device

Abstract

The present invention relates to a transmission method and apparatus, wherein the method comprises: receiving at least one downlink control information; determining a time resource and / or content of a hybrid automatic repeat request-response to be sent based on the downlink control information; and sending a hybrid automatic repeat request-response based on the determined time resource and / or content of the hybrid automatic repeat request-response.

Description

Technical Field

[0001] The present invention relates to a wireless communication method and device, and in particular to a transmission method and device in an unlicensed frequency band. Background Art

[0002] To meet the massive demand for services, 5G communication systems are expected to operate across frequency bands ranging from low to high frequencies around 100 GHz, including both licensed and unlicensed bands. Unlicensed bands primarily consider the 5 GHz and 60 GHz bands. We refer to 5G systems operating in unlicensed bands as NR-U systems. In the 5 GHz band, 802.11 series Wireless Fidelity (Wi-Fi) systems, radar, and LTE's licensed carrier-assisted access systems have already been deployed. These systems all adhere to the listen-before-talk (LBT) mechanism, requiring a channel access process and channel detection before transmitting signals. Only when the channel is idle can signals be transmitted. In the 60 GHz band, 802.11ay systems already exist, and therefore also require the LBT mechanism. In other unlicensed bands, effective coexistence strategies must be developed in accordance with relevant specifications.

[0003] Because LBT before a signal is transmitted may fail, the corresponding signal cannot be sent. To reduce the impact of LBT failure on transmission efficiency, new methods are needed to support multiple signal transmission opportunities. At the same time, new methods are also needed to evaluate the impact of LBT failure on transmission efficiency. Summary of the Invention

[0004] The object of the present invention is to provide a transmission method and device.

[0005] According to one embodiment of the present invention, a transmission method is provided, comprising: receiving at least one downlink control information; determining a time resource and / or a hybrid automatic repeat request-response content of a hybrid automatic repeat request-response to be sent based on the downlink control information; and sending a hybrid automatic repeat request-response based on the determined time resource and / or hybrid automatic repeat request-response content of the hybrid automatic repeat request-response.

[0006] According to another embodiment of the present invention, a transmission method is provided, comprising: receiving uplink signal transmission resource information; determining frequency domain resources occupied by sending uplink signals based on the uplink signal transmission resource information; and attempting to send the uplink signal on the determined frequency domain resources.

[0007] According to another embodiment of the present invention, a transmission method is provided, comprising: sending at least one downlink control information; receiving a hybrid automatic repeat request-response time resource determined based on the downlink control information and / or a hybrid automatic repeat request-response sent by the hybrid automatic repeat request-response information.

[0008] According to another embodiment of the present invention, a transmission method is provided, comprising: sending uplink signal transmission resource information; and attempting to receive the uplink signal on a frequency domain resource determined based on the uplink signal transmission resource information.

[0009] According to another embodiment of the present invention, a transmission device is provided, including: a first receiving module for receiving at least one downlink control information; a first determining module for determining the time resources and / or the content of the hybrid automatic repeat request-response to be sent based on the downlink control information; and a first sending module for sending the hybrid automatic repeat request-response based on the determined time resources and / or the content of the hybrid automatic repeat request-response.

[0010] According to another embodiment of the present invention, a transmission device is provided, including: a second receiving module for receiving uplink signal transmission resource information; a second determining module for determining the frequency domain resources occupied by sending the uplink signal based on the uplink signal transmission resource information; and a second sending module for attempting to send the uplink signal on the determined frequency domain resources.

[0011] According to another embodiment of the present invention, a transmission device is provided, including: a first base station sending module, used to send at least one downlink control information; a first base station receiving module, receiving a hybrid automatic repeat request-response sent based on the time resources of the hybrid automatic repeat request-response and / or the hybrid automatic repeat request-response content determined based on the downlink control information.

[0012] According to another embodiment of the present invention, a transmission device is provided, including: a second base station sending module, used to send uplink signal transmission resource information; a second base station receiving module, used to attempt to receive the uplink signal on the frequency domain resources determined based on the uplink signal transmission resource information. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 This is a flow chart of an embodiment of a transmission method of the present invention.

[0014] Figure 2 FIG. 4 is a schematic diagram of a base station scheduling multiple PDSCHs according to another embodiment of the present invention.

[0015] Figure 2A This is a first enlarged schematic diagram of a base station scheduling multiple PDSCHs in another embodiment of the present invention.

[0016] Figure 2B This is a second enlarged schematic diagram of a base station scheduling multiple PDSCHs in another embodiment of the present invention.

[0017] Figure 2C This is a third enlarged schematic diagram of a base station scheduling multiple PDSCHs according to another embodiment of the present invention.

[0018] Figure 2D This is a fourth enlarged schematic diagram of a base station scheduling multiple PDSCHs according to another embodiment of the present invention.

[0019] Figure 2E This is a fifth enlarged schematic diagram of a base station scheduling multiple PDSCHs according to another embodiment of the present invention.

[0020] Figure 3 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention.

[0021] Figure 4 FIG. 4 is a schematic diagram of a base station scheduling multiple PDSCHs according to another embodiment of the present invention.

[0022] Figure 4A This is a first enlarged schematic diagram of a base station scheduling multiple PDSCHs in another embodiment of the present invention.

[0023] Figure 4B This is a second enlarged schematic diagram of a base station scheduling multiple PDSCHs in another embodiment of the present invention.

[0024] Figure 4C This is a third enlarged schematic diagram of a base station scheduling multiple PDSCHs according to another embodiment of the present invention.

[0025] Figure 5 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention.

[0026] Figure 6 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention.

[0027] Figure 7 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention.

[0028] Figure 8 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention.

[0029] Figure 9 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention.

[0030] Figure 10 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention.

[0031] Figure 11FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention.

[0032] Figure 12 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention.

[0033] Figure 13 FIG. 1 is a module diagram of a transmission device according to an embodiment of the present invention.

[0034] Figure 14 FIG. 4 is a module diagram of another embodiment of the transmission device of the present invention.

[0035] Figure 15 The figure shows a detailed schematic diagram of a hardware entity applicable to the present application.

[0036] Figure 16A FIG. 4 is a schematic diagram of feeding back HARQ-ACK in PUSCH according to another embodiment of the present invention.

[0037] Figure 16B FIG. 4 is a schematic diagram of feeding back HARQ-ACK in PUSCH according to another embodiment of the present invention. DETAILED DESCRIPTION

[0038] The present application will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely for the purpose of explaining the relevant invention and are not intended to limit the invention. It should also be noted that, for ease of description, only portions relevant to the relevant invention are shown in the accompanying drawings.

[0039] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in this application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0040] Figure 1 FIG. 1 is a flow chart of an embodiment of a transmission method of the present invention. Figure 1 The transmission method according to this embodiment may include:

[0041] In step 101, a user equipment (UE) receives at least one downlink control information (DCI) for feeding back a hybrid automatic repeat request-ACK (HARQ-ACK).

[0042] Step 102: The UE determines the time resource and / or HARQ-ACK content of the HARQ-ACK to be sent according to the received DCI.

[0043] The DCI may include: a first bit region, a second bit region, and a third bit region. The first bit region is used to indicate the index of the PDSCH group scheduled by the DCI; the second bit region is used to indicate the ACK status of the PDSCH group scheduled by the DCI; and the third bit region is used to indicate that all processes feedback HARQ-ACK and is used to determine the ACK status of another PDSCH group other than the PDSCH group scheduled by the DCI.

[0044] Specifically, the third bit region consists of two bits and has a first state, a second state, a third state, and a fourth state. For example, the first state may be represented by "00," the second state may be represented by "01," the third state may be represented by "10," and the fourth state may be represented by "11."

[0045] The first state is used to trigger HARQ-ACK feedback of the current physical downlink shared channel (PDSCH) group.

[0046] The second state is used to trigger HARQ-ACK feedback of two PDSCH groups.

[0047] The third state is used to trigger HARQ-ACK feedback of all HARQ processes and is used to indicate that the ACK state of another PDSCH group other than the PDSCH group scheduled by the DCI is in a flipped state.

[0048] The fourth state is used to trigger HARQ-ACK feedback of all HARQ processes and is used to indicate that the ACK state of another PDSCH group other than the PDSCH group scheduled by the DCI is a non-flip state.

[0049] Furthermore, the UE determines, based on the received DCI, that the HARQ-ACK status information to be sent may include: the HARQ-ACK of the current PDSCH group; or the HARQ-ACK of two PDSCH groups; or the HARQ-ACK of all HARQ processes.

[0050] Step 103: Since the HARQ-ACK status information to be sent is determined in the above steps, the UE sends the HARQ-ACK according to the determined HARQ-ACK status information.

[0051] If in step 102 the UE determines to feedback the HARQ-ACK of all HARQ processes based on the received DCI, the HARQ-ACK value of each HARQ-ACK process is determined according to the ACK status of the current PDSCH group indicated by the second bit area and the ACK status of another PDSCH group other than the current PDSCH group indicated by the third bit area.

[0052] According to an embodiment of the transmission method of the present invention, four states can be fed back respectively through the two bits of the third bit area of ​​​​DCI, namely, triggering HARQ-ACK feedback of the current PDSCH group, triggering HARQ-ACK feedback of two PDSCH groups, triggering HARQ-ACK feedback of all HARQ processes and used to indicate that the ACK state of another PDSCH group other than the current PDSCH group is a flipped state, triggering HARQ-ACK feedback of all HARQ processes and used to indicate that the ACK state of another PDSCH group other than the current PDSCH group is a non-flipped state.

[0053] However, in the prior art, when triggering HARQ-ACK feedback for the current PDSCH group, and triggering HARQ-ACK feedback for two PDSCH groups, one bit is required for implementation; when triggering HARQ-ACK feedback for all HARQ processes and indicating that the ACK state of another PDSCH group other than the current PDSCH group is in a flipped state, and when triggering HARQ-ACK feedback for all HARQ processes and indicating that the ACK state of another PDSCH group other than the current PDSCH group is not in a flipped state, one bit is required for implementation. That is, according to the prior art, if one wants to implement feedback of the four states of an embodiment of the transmission method of the present invention, three bits are required.

[0054] Therefore, the transmission method according to an embodiment of the present invention reduces the DCI overhead by 1 / 3 compared with the prior art.

[0055] The following describes in detail a technical solution for determining HARQ-ACK status information in conjunction with a specific implementation method.

[0056] To reduce the impact of LBT failure on HARQ-ACK feedback, it is necessary to support the HARQ-ACK retransmission mechanism. The base station can trigger the UE to retransmit the HARQ-ACK that the base station failed to successfully receive.

[0057] Specifically, the base station can configure a dynamic HARQ-ACK codebook based on PDSCH grouping for the UE. The base station can trigger HARQ-ACK feedback for one or more PDSCH groups. If the UE fails to send HARQ-ACK due to LBT failure, or the base station misses the HARQ-ACK sent by the UE due to a hidden terminal, the base station can trigger HARQ-ACK feedback for the PDSCH groups containing these HARQ-ACKs to obtain these HARQ-ACK information again.

[0058] In addition, the base station can also configure HARQ-ACK feedback based on all PDSCH processes for the UE and obtain this HARQ-ACK information again. To achieve flexible selection between overhead and robustness, the base station can configure the UE to dynamically switch between a dynamic HARQ-ACK codebook and a HARQ-ACK codebook for all PDSCH processes. To avoid excessive overhead in the downlink control information DCI, this embodiment combines the characteristics of the two codebooks to design the bit field for HARQ-ACK feedback in the DCI.

[0059] The downlink DCI for scheduling PDSCH contains a bit field for HARQ-ACK feedback. To support HARQ-ACK retransmission, the bit field for HARQ-ACK feedback includes: HARQ-ACK feedback group information (PDSCH group index) for the currently scheduled PDSCH, ACK feedback indication information (ACK-feedback group indicator) for a PDSCH group, HARQ-ACK feedback request group information (PDSCH set), and downlink assignment index (DAI).

[0060] The multiple PDSCHs scheduled by the base station can be divided into one or more PDSCH groups. The HARQ-ACK of all PDSCHs in the same PDSCH group is fed back in the same physical uplink control channel (PUCCH).

[0061] The base station indicates to which PDSCH group the currently scheduled PDSCH belongs through the PDSCH group index.

[0062] Each PDSCH group has an ACK-feedback group indicator, which is used to indicate whether the UE needs to feedback the HARQ-ACK information in the previous HARQ-ACK feedback of the group when feeding back the HARQ-ACK of the current PDSCH. For example, if the ACK-feedback group indicator is flipped relative to the ACK-feedback groupindicator of the previous same group, the previous HARQ-ACK information does not need to be fed back in the current feedback (the previous HARQ-ACK information may contain a single or multiple HARQ-ACKs of PDSCHs belonging to the same group). If the ACK-feedback groupindicator remains unchanged relative to the ACK-feedback group indicator of the previous same group, the previous HARQ-ACK information needs to be fed back in the current feedback.

[0063] The HARQ-ACK feedback request group information PDSCH set is a set of PDSCH groups that need to simultaneously feedback HARQ-ACK in the same PUCCH. For example, the HARQ-ACK feedback request group information includes triggering HARQ-ACK feedback only for the currently scheduled PDSCH group, or HARQ-ACK feedback for the currently scheduled PDSCH group and at least one other group, or HARQ-ACK feedback for all HARQ processes.

[0064] The dynamic HARQ-ACK codebook must at least determine: the PDSCH group index of the current PDSCH, the ACK feedback status of this PDSCH group (i.e., whether the UE also needs to feedback the HARQ-ACK information in the previous HARQ-ACK feedback for this group when feeding back the HARQ-ACK for the current PDSCH), and the PDSCH set that can trigger this PDSCH group. The HARQ-ACK codebook for all PDSCH processes must at least be able to trigger the PDSCH set for all PDSCH processes.

[0065] Furthermore, in order to more accurately determine the HARQ-ACK value of each PDSCH process, it is necessary to indicate the ACK feedback status of the PDSCH of each PDSCH process.

[0066] A simple implementation method is to indicate the ACK feedback status for each PDSCH process separately, but the overhead is too large.

[0067] Another implementation method can use the PDSCH group index of the dynamic HARQ-ACK codebook and the ACK feedback status of each PDSCH group to determine the HARQ-ACK of the HARQ processes belonging to these PDSCH groups, thereby reducing DCI overhead. That is, when the base station triggers HARQ-ACK feedback for all HARQ processes, the base station indicates the ACK feedback status of all PDSCH groups.

[0068] For example, the base station configures a maximum of 2 PDSCH groups for the UE, and the base station configures dynamic switching between a dynamic HARQ-ACK codebook and a HARQ-ACK codebook based on all HARQ processes.

[0069] In the DCI, the first bit area PDSCH group index is used to indicate the group information of the HARQ-ACK feedback of the currently scheduled PDSCH. The second bit area ACK-feedback group indicator indicates the ACK feedback status of the group where the currently scheduled PDSCH is located. The third bit area is used to indicate respectively: triggering HARQ-ACK feedback only for the group where the currently scheduled PDSCH is located; triggering HARQ-ACK feedback for two PDSCH groups; triggering HARQ-ACK feedback for all HARQ processes, and the ACK feedback indication for the other group except the group where the currently scheduled PDSCH is located is flipped; triggering HARQ-ACK feedback for all HARQ processes, and the ACK feedback indication for the other group except the group where the currently scheduled PDSCH is located is not flipped.

[0070] Alternatively, in the DCI, the first bit region indicates the PDSCH group index. The second bit region, ACK-feedback group indicator, indicates the ACK feedback status of the current PDSCH group. The third bit region indicates whether HARQ-ACK feedback is triggered for the current PDSCH group or for another PDSCH group, or indicates the ACK feedback status of another PDSCH group. The fourth bit region indicates whether HARQ-ACK feedback is triggered for all HARQ processes.

[0071] Specifically, when the fourth bit area triggers HARQ-ACK feedback for all HARQ processes, the third bit area indicates the ACK feedback status of another PDSCH. When the fourth bit area does not trigger HARQ-ACK feedback for all HARQ processes, the third bit area indicates triggering HARQ-ACK feedback for the current PDSCH group or triggering HARQ-ACK feedback for the current and another PDSCH group.

[0072] For example, the DCI contains 4 bits, of which the first bit is the PDSCH group index, the second bit is the ACK feedback status of the current PDSCH group, and the fourth bit is the HARQ-ACK feedback indication for triggering all HARQ processes. When the fourth bit triggers the HARQ-ACK feedback of all HARQ processes, for example, when the fourth bit takes the value of 1, the third bit is used to indicate the ACK feedback status of another PDSCH group other than the current PDSCH group. When the fourth bit does not trigger the HARQ-ACK feedback of all HARQ processes, for example, when the fourth bit takes the value of 0, the third bit is used to indicate the feedback of the HARQ-ACK of the current PDSCH group (for example, the third bit is 0) or the current HARQ-ACK feedback with another PDSCH group (for example, the third bit is 1). The present invention does not limit the order of these bit fields.

[0073] If the base station triggers HARQ-ACK feedback for all HARQ processes, if a HARQ process does not belong to any PDSCH group, or if the base station indicates that no further feedback is required after the last HARQ-ACK feedback for this HARQ process (the ACK feedback state is flipped) and this HARQ process has not been scheduled since then (relative to the ACK feedback state of this PDSCH group in the DCI that last transmitted the HARQ process, the ACK feedback state of the PDSCH group in the DCI that triggered HARQ-ACK feedback for all HARQ processes is flipped), then the HARQ-ACK value of this HARQ process is NACK. If a HARQ process belongs to a PDSCH group and is not indicated by the base station as no further feedback is required, ACK or NACK is generated based on the decoding result of the PDSCH.

[0074] Figure 2 FIG. 4 is a schematic diagram of a base station scheduling multiple PDSCHs according to another embodiment of the present invention. Figure 2A This is a first enlarged schematic diagram of a base station scheduling multiple PDSCHs in another embodiment of the present invention. Figure 2B This is a second enlarged schematic diagram of a base station scheduling multiple PDSCHs in another embodiment of the present invention. Figure 2C This is a third enlarged schematic diagram of a base station scheduling multiple PDSCHs according to another embodiment of the present invention. Figure 2D This is a fourth enlarged schematic diagram of a base station scheduling multiple PDSCHs according to another embodiment of the present invention. Figure 2E This is a fifth enlarged schematic diagram of a base station scheduling multiple PDSCHs according to another embodiment of the present invention.

[0075] like Figures 2 to 2EAs shown, assuming that the base station schedules PDSCH 1 to 3, PDSCH group 1 is indicated in the DCI for scheduling PDSCH (PDSCH group index takes the value 0), the ACK feedback status of PDSCH group 1 takes the value 0, and only the HARQ-ACK of PDSCH group 1 is fed back (the last 2 bits take the value 00), the HARQ-ACK of PDSCH 1 to 3 is sent in PUCCH1, and the base station correctly receives PUCCH1.

[0076] The base station schedules PDSCH 4 to 6, indicating PDSCH group 2 (PDSCH group index is 1). The ACK feedback status of PDSCH group 2 is 0, and only the HARQ-ACK of PDSCH group 2 is fed back (the last 2 bits are 00). The HARQ-ACK of PDSCH 4 to 6 is sent in PUCCH2, and the base station does not correctly receive PUCCH2.

[0077] The base station schedules PDSCH 7 to 9, indicating PDSCH group 1 (PDSCH group index is 0), the ACK feedback status of PDSCH group 1 is 1 (flipped, indicating that there is no need to send HARQ-ACK for PDSCH 1 to 3), and only the HARQ-ACK of PDSCH group 1 is fed back (the last 2 bits are 00). The HARQ-ACK of PDSCH 7 to 9 is sent in PUCCH3, and the base station does not receive PUCCH3 correctly.

[0078] The base station schedules PDSCH 10-11, indicating PDSCH group 2 (PDSCH group index is 1), the ACK feedback status of PDSCH group 2 is 0 (not flipped, HARQ-ACK for PDSCH 4-6 needs to be sent), and only HARQ-ACK for PDSCH group 2 is fed back (the last 2 bits are 00).

[0079] The base station schedules PDSCH 12, indicating PDSCH group 2 (PDSCH group index takes the value of 1), the ACK feedback status of PDSCH group 2 takes the value of 0 (not flipped, and HARQ-ACK for PDSCH 4 to 6 needs to be sent), and the HARQ-ACK of PDSCH group 1 and group 2 is fed back (because the base station did not successfully receive PUCCH3, it triggered PDSCH group 1 and group 2 to send HARQ-ACK together. The last 2 bits take the values ​​01), and the HARQ-ACK of PDSCH 4 to 12 is sent in PUCCH4. The base station did not receive PUCCH4 correctly.

[0080] The base station schedules PDSCH 13 and 14, indicating PDSCH group 2 (PDSCH group index takes the value of 1), the ACK feedback status of PDSCH group 2 takes the value of 0 (not flipped, and HARQ-ACK for PDSCH 4 to 6 needs to be sent), and the HARQ-ACK of all PDSCH processes is fed back (because the base station did not successfully receive PUCCH4, the HARQ-ACK of all PDSCH processes is triggered, and the ACK feedback status of PDSCH group 1 is not flipped relative to the previous ACK feedback status of PDSCH group 1. The last 2 bits take the value 11), and the HARQ-ACK of all PDSCH processes (assuming 16 processes) is sent in PUCCH5.

[0081] The UE returns a 16-bit HARQ-ACK. The HARQ-ACKs for the PDSCHs corresponding to HARQ processes 1, 2, 4, and 12 are actual ACK / NACKs. HARQ processes 3, 13, and 16 do not belong to any PDSCH group or have been instructed not to send HARQ-ACKs. Therefore, the HARQ-ACKs for these five HARQ processes are NACKs.

[0082] The downlink DCI (UL grant) that schedules PUSCH contains a bit field for HARQ-ACK feedback. When the resource where the HARQ-ACK is located overlaps with the PUSCH, the UE sends the HARQ-ACK in the PUSCH resource. When the base station instructs the UE to use a dynamic HARQ-ACK codebook based on the PDSCH group, in order to avoid errors in the HARQ-ACK codebook size, the total number of bits of all HARQ-ACKs to be fed back is indicated in the UL grant. For example, 2 bits of DAI, or 4 bits of DAI (when TB-based and CBG-based HARQ-ACK subcodebooks are configured). According to another implementation method, the base station indicates the HARQ-ACK codebook size of a PDSCH group in the UL grant. In order to avoid the UE from misunderstanding the PDSCH group corresponding to the indicated HARQ-ACK codebook size, the base station should avoid triggering HARQ-ACK for more than one PDSCH group to be sent on the same PUSCH at the same time. The UE considers that the HARQ-ACK codebook size indicated in the UL grant corresponds to the PDSCH group for which HARQ-ACK is sent in the PUSCH scheduled by this UL grant. Preferably, for a PUSCH, if the base station does not indicate the HARQ-ACK codebook size in the UL grant that schedules this PUSCH, or this PUSCH is not scheduled based on the UL grant (for example, based on a configured PUSCH), the base station should avoid triggering HARQ-ACK for more than one PDSCH group to be sent simultaneously on the same PUSCH.

[0083] like Figure 16A As shown, if the base station sends PDCCH scheduling PDSCH of PDSCH group 2 in the 4th downlink transmission opportunity, and triggers the UE to feedback HARQ-ACK of PDSCH group 1 and group 2 on PUSCH in the figure, sends PDCCH scheduling PDSCH of PDSCH group 1 in the 5th downlink transmission opportunity, and triggers the UE to feedback HARQ-ACK of PDSCH group 1 and group 2 on PUSCH in the figure, then the base station subsequently sends UL grant scheduling PUSCH, and indicates that the HARQ-ACK codebook size is 3. If the UE assumes that the PDSCH group corresponding to the HARQ-ACK codebook size indicated in the UL grant is the last received PDSCH group index for which HARQ-ACK will be fed back in the PUSCH, when the UE does not detect the PDCCH in the 5th downlink transmission opportunity, the UE believes that the last received PDSCH group index for which HARQ-ACK will be fed back in the PUSCH is PDSCH group 2 (PDSCH group 2 scheduled by the PDCCH in the 4th transmission opportunity), and therefore determines that a 5-bit HARQ-ACK needs to be fed back in the PUSCH, where PDSCH group 1 contains 2 bits and PDSCH group 2 contains 3 bits (determined according to the HARQ-ACK codebook size indicated in the UL grant). Then, the HARQ-ACK expected to be received by the base station is PDSCH group 1 containing 3 bits (determined according to the HARQ-ACK codebook size indicated in the UL grant) and PDSCH group 2 containing 2 bits. Therefore, the bit order of the HARQ-ACK codebook is incorrect.

[0084] If it is limited that when HARQ-ACK is sent on PUSCH, the base station can only trigger HARQ-ACK for one PDSCH group, the base station can Figure 16B For example, scheduling is performed. The base station sends a PDCCH to schedule the PDSCH of PDSCH group 1 in the 4th downlink transmission opportunity, and triggers the UE to feedback the HARQ-ACK of PDSCH group 1 on the PUSCH in the figure. In the 5th downlink transmission opportunity, the base station sends a PDCCH to schedule the PDSCH of PDSCH group 1, and triggers the UE to feedback the HARQ-ACK of PDSCH group 1 on the PUSCH in the figure. Subsequently, the base station sends a UL grant to schedule the PUSCH and indicates that the HARQ-ACK codebook size is 4. Therefore, although the UE does not receive the PDCCH in the 5th downlink transmission opportunity, the UE can determine that the HARQ-ACK codebook size indicated in the UL grant is the HARQ-ACK codebook size of PDSCH group 1 based on the PDCCH in the 4th downlink transmission opportunity. The UE feeds back 4-bit HARQ-ACK for PDSCH group 1 in the PUSCH.

[0085] For a PDSCH group, if the UE does not detect any PDCCH triggering the HARQ-ACK feedback of this PDSCH group in the PUSCH, and the HARQ-ACK codebook size of this group indicated in the UL grant is not 0, the UE sends an N-bit NACK, where N is determined according to the HARQ-ACK codebook size indicated in the UL grant, and N is less than 2 M , M is the number of bits indicating the HARQ-ACK codebook size of this group in the UL grant.

[0086] When the base station instructs the UE to provide HARQ-ACK codebook feedback based on all PDSCH processes, the HARQ-ACK codebook size is fixed, so these DAI information are not needed. To fully utilize these bits, they can be reused for ACK feedback indication information for each PDSCH group. For example, if the base station configures a UE with up to two PDSCH groups, each with one bit of ACK feedback indication information, a two-bit DAI can be reused.

[0087] In steps 102 and 103, when the HARQ-ACK resources determined by the UE overlap with the configured PUSCH resources, and when the number of bits in the HARQ-ACK codebook exceeds the number of bits determined according to the configured number of PUSCH resources and the configured modulation and coding parameters for determining uplink control information, the UE sends HARQ-ACK on the PUCCH resources determined according to the DCI that triggers the HARQ-ACK transmission, and the UE does not send the configured PUSCH. If the number of bits in the HARQ-ACK codebook does not exceed the number of bits determined according to the configured number of PUSCH resources and the configured modulation and coding parameters for determining uplink control information, the UE sends the configured PUSCH and sends HARQ-ACK on the PUSCH. Alternatively, when the number of bits in the HARQ-ACK codebook and the configured uplink control information (CG-UCI, including uplink control information for configured PUSCH demodulation) of the PUSCH exceeds the number of bits determined according to the configured PUSCH resources and the configured modulation and coding parameters for determining the uplink control information, the UE sends HARQ-ACK on the PUCCH resources determined according to the DCI that triggers the sending of HARQ-ACK, and the UE does not send the configured PUSCH. Otherwise, the UE sends the configured PUSCH and sends HARQ-ACK on the PUSCH. Alternatively, when the number of bits in the HARQ-ACK codebook exceeds the number of bits determined according to the configured PUSCH resources available for sending HARQ-ACK and the configured modulation and coding parameters for determining the uplink control information, the UE sends HARQ-ACK on the PUCCH resources determined according to the DCI that triggers the sending of HARQ-ACK, and the UE does not send the configured PUSCH. Otherwise, the UE sends the configured PUSCH and sends HARQ-ACK on the PUSCH. Among them, the number of resources of the configured PUSCH is the number of REs determined according to the time-frequency resources of the configured PUSCH, and the number of resources of the configured PUSCH that can be used to send HARQ-ACK is the number of REs determined according to the time-frequency resources of the configured PUSCH minus the time-frequency resources used for CG-UCI. For any of the above methods, if the UE sends the configured PUSCH, it must send CG-UCI at the same time. For any of the above methods, if there is other uplink control information, such as CSI, and the UE sends HARQ-ACK on the PUCCH resources determined according to the DCI that triggers the sending of HARQ-ACK, the UE can send CSI information on the PUCCH resources at the same time. If the UE sends the configured PUSCH, the UE can send CSI information on the configured PUSCH at the same time. Figure 3 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention. Figure 3 The transmission method according to this embodiment may include:

[0088] Step 301: A UE receives multiple DCIs from a base station. Among the multiple DCIs received, a HARQ-ACK timing value indicated by one DCI is a non-numeric value.

[0089] The DCI includes: a first bit area and a second bit area.

[0090] The first bit area is used to indicate the PDSCH group index scheduled by the DCI; the second bit area is used to indicate the ACK status of the PDSCH group scheduled by the DCI.

[0091] Step 302: Determine the time resource for the HARQ-ACK to be sent according to the DCI.

[0092] At this time, the step of determining the time resource of the HARQ-ACK to be sent according to the DCI includes: determining the time resource of the HARQ-ACK corresponding to the first DCI according to the timing value in the second DCI.

[0093] Furthermore, the step of determining the time resource of the HARQ-ACK corresponding to the first DCI according to the timing value in the second DCI includes: determining, based on the DCI having the same value in the first bit region, the same value in the second bit region, and the smallest time interval, that its HARQ-ACK time resource is the same as the time resource of the HARQ-ACK with a non-numeric timing value. Specifically, searching for a DCI having the same value in the first bit region, the same value in the second bit region, and the smallest time interval, and then determining that the HARQ-ACK time resource of the DCI is the same as the time resource of the HARQ-ACK with a non-numeric timing value.

[0094] In addition, if the value of the first bit area is the same, and the value of the second bit area is the same, and there are two DCIs with the smallest time interval, then it is determined that the time resources of the HARQ-ACK of the two DCIs are the same as the time resources of the HARQ-ACK with a non-numeric timing value.

[0095] Step 303: Send HARQ-ACK according to the determined HARQ-ACK time resource and / or HARQ-ACK status information.

[0096] According to a transmission method of another embodiment of the present invention, when receiving a DCI whose HARQ-ACK timing value is a non-numeric value, the time resource of the HARQ-ACK corresponding to the first DCI can be determined according to the timing value in the second DCI.

[0097] However, in the prior art, when receiving a DCI with a non-numeric HARQ-ACK timing value, retransmission is required.

[0098] Therefore, compared with the prior art, the transmission method according to another embodiment of the present invention can significantly reduce system overhead and improve system efficiency.

[0099] The following describes in detail the technical solution for determining the time resources of HARQ-ACK in combination with specific implementation methods.

[0100] The HARQ-ACK timing K1 indicated in the DCIi of the scheduled PDSCH can be a precise time information. For example, the value of K1 is a specific numeric value, representing n time slots or symbols, or it can represent a non-numeric time information (this non-numeric state can be represented by a specific K1 value), indicating that the HARQ-ACK timing needs to be determined jointly with another DCIj.

[0101] In specific implementations, if the time difference between DCIi or the PDSCH scheduled by DCIi and the nearest PUCCH is less than the HARQ-ACK processing delay, the base station may indicate K1 as a non-numeric value. Alternatively, due to the limited number of bits of K1, when the limited K1 value cannot point to a suitable PUCCH resource, the base station may also indicate K1 as a non-numeric value. Then, according to predefined rules, the HARQ-ACK transmission time of the PDSCH scheduled by DCIi is determined using the HARQ-ACK timing information of another DCIj.

[0102] Specifically, if the HARQ-ACK sending time of the PDSCH scheduled by DCIi needs to be jointly determined by another DCIj. For example, the HARQ-ACK timing K1 in the DCIi that schedules PDSCH1 indicates non-numerical time information. If DCIj indicates the same PDSCH group index as PDSCH1 (the same as the PDSCH group index in DCIi), and the ACK feedback indication bit has the same value, and is the DCI closest to DCIj in the time dimension, then the HARQ-ACK of the PDSCH scheduled by DCIi is sent together with the HARQ-ACK of the PDSCH scheduled by DCIj. DCIj may not be earlier than DCIi in the time dimension. Alternatively, DCIj may be earlier than DCIi in the time dimension.

[0103] Figure 4 FIG. 4 is a schematic diagram of a base station scheduling multiple PDSCHs according to another embodiment of the present invention. Figure 4A This is a first enlarged schematic diagram of a base station scheduling multiple PDSCHs in another embodiment of the present invention. Figure 4B This is a second enlarged schematic diagram of a base station scheduling multiple PDSCHs in another embodiment of the present invention. Figure 4 and Figure 4A and 4BAs shown, "X" represents a non-numeric K1. PDSCH1 and PDSCH2 belong to the same PDSCH group 1 (PDSCH group index 0), have the same ACK feedback status (both 0), and PDSCH2 is closest to PDSCH1 in the time dimension.

[0104] At this time, the HARQ-ACKs of PDSCH1 and PDSCH2 are fed back in the same HARQ-ACK codebook, so it is inferred that K1=4 of PDSCH1.

[0105] PDSCH3 and PDSCH4 belong to the same PDSCH group 2 (PDSCH group index 1) and have the same ACK feedback state (both are 0). PDSCH4 and PDSCH5 / 6 belong to the same PDSCH group 2 (PDSCH group index 1) but have different ACK feedback states. In this case, the HARQ-ACK timing of PDSCH4 cannot be determined based on PDSCH5 / 6, but is determined based on PDSCH3. Therefore, K1=4 for PDSCH4.

[0106] If the HARQ-ACK timing of the PDSCH scheduled by DCIi needs to be jointly determined by another DCIj. For example, the HARQ-ACK timing K1 in the DCIi that schedules PDSCH1 indicates non-numerical time information. If the PDSCH group index indicated by DCIj is different from the PDSCH group index of PDSCH1, and the HARQ-ACK feedback of the PDSCH group including PDSCH1 is triggered, and it is closest to DCIj in the time dimension, then the HARQ-ACK of the PDSCH scheduled by DCIi and the HARQ-ACK of the PDSCH scheduled by DCIj belong to the same HARQ-ACK codebook. Preferably, DCIj is not earlier than DCIi in the time dimension.

[0107] Figure 4C FIG3 is a third enlarged schematic diagram of a base station scheduling multiple PDSCHs in another embodiment of the present invention. Figure 4 and Figure 4CAs shown, "X" represents a non-numeric K1. PDSCH1 / 2 belongs to PDSCH group 1 and only triggers the HARQ-ACK feedback of PDSCH group 1. PDSCH3 belongs to PDSCH group 2 and only triggers the HARQ-ACK feedback of PDSCH group 2. The value of K1 is X. PDSCH4 / 5 belongs to PDSCH group 1 and triggers the HARQ-ACK feedback of PDSCH group 1 and PDSCH group 2. Then, the HARQ-ACK of PDSCH3 is fed back together with PDSCH 4 / 5. It is not difficult to see that in this case, there is no need to detect whether the ACK feedback status indication in the DCIi scheduling PDSCH3 is the same as the ACK feedback status in the DCIj scheduling PDSCH4.

[0108] Figure 5 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention. Figure 5 The transmission method according to this embodiment may include:

[0109] Step 501: Receive uplink signal transmission resource information.

[0110] Step 502: Determine the time-frequency resources occupied by sending the uplink signal.

[0111] The uplink signal transmission resource information in step 501 includes at least one of time resource information, frequency domain resource information, and LBT information of the uplink signal. The uplink signal transmission resource information is carried by physical layer signaling or higher layer signaling.

[0112] The step of determining the time-frequency resources occupied by sending the uplink signal includes: determining the frequency domain resources occupied by sending the uplink signal based on the uplink signal transmission resource information, the channel occupancy time and the LBT sub-band corresponding to the COT; and sending the uplink signal on the determined frequency domain resources.

[0113] Furthermore, the step of determining the frequency domain resources occupied by sending the uplink signal based on the uplink signal transmission resource information, the channel occupancy time and the LBT sub-band corresponding to the COT includes: when the uplink signal is located within the COT, determining the LBT sub-band where the uplink signal is located based on the LBT sub-band where the COT is located; when the uplink signal is located outside the COT, determining the LBT sub-band where the uplink signal is located based on the uplink signal transmission resource information.

[0114] Furthermore, the step of determining the time-frequency resources occupied by sending the uplink signal based on the uplink signal transmission resource information, the channel occupancy time and the LBT sub-band corresponding to the COT includes: when the LBT sub-band corresponding to the COT is the LBT sub-band where the PDCCH that triggers the uplink signal transmission is located, the PDCCH that triggers the uplink signal transmission and the uplink signal belong to the same COT; or, the LBT sub-band corresponding to the COT is the LBT sub-band where the COT is located.

[0115] Step 503: Send the uplink signal on the determined time-frequency resource.

[0116] The transmission method of another embodiment of the present invention determines the LBT subband of the uplink signal based on the LBT subband of the COT when the uplink signal is within the COT; and determines the LBT subband of the uplink signal based on uplink signal transmission resource information when the uplink signal is outside the COT. Furthermore, the transmission method of another embodiment of the present invention determines that when the LBT subband corresponding to the COT is the LBT subband of the PDCCH that triggers the transmission of the uplink signal, the PDCCH that triggers the transmission of the uplink signal and the uplink signal belong to the same COT; or, alternatively, the LBT subband corresponding to the COT is the LBT subband of the COT.

[0117] The transmission method of another embodiment of the present invention reduces system overhead and improves system efficiency through the above method.

[0118] The technical solution for performing LBT is described in detail below in conjunction with specific implementation methods.

[0119] When a UE operates in an unlicensed frequency band, it may need to perform a channel access procedure before transmitting a signal. Transmission can only be performed if and only if the channel is detected to be idle. This process is also known as LBT (Listen before talk).

[0120] LBT can be divided into at least two cases: broadband LBT and sub-band LBT.

[0121] Assuming the signal bandwidth to be transmitted by the transmitter is BW1, the transmitter performs the same LBT process simultaneously across the entire BW1, which is called wideband LBT. If BW1 can be divided into N LBT subbands (LBT bandwidth), each with a bandwidth of BW2, the transmitter performs LBT separately on each LBT subband within BW1, which is called subband LBT.

[0122] For example, if BW1 = 80 MHz, it is divided into N = 4 LBT subbands, and BW2 = 20 MHz for each subband. The UE can perform LBT independently on these four LBT subbands, or select an LBT subband for the first type of LBT (for example, Cat-4 LBT). If LBT is successful on the LBT subband, the second type of LBT can be performed on other subbands.

[0123] After a base station occupies a channel using Type 1 LBT, it can transmit downlink signals within the maximum channel occupancy time (MCOT). Alternatively, the UE served by the base station can perform Type 2 LBT or transmit uplink signals without LBT. If subband-based LBT is used, and the base station successfully performs Type 1 LBT on at least one subband, it can transmit downlink signals within the maximum channel occupancy time (MCOT) on all subbands where LBT was successfully completed. Alternatively, the UE served by the base station can perform Type 2 LBT or transmit uplink signals without LBT. This situation is called a base station-shared COT.

[0124] Similarly, after a UE occupies a channel using Type 1 LBT, it can perform Type 2 LBT or transmit uplink signals without performing LBT within the maximum channel occupancy time (MCOT). If subband-based LBT is used, and a UE successfully performs Type 1 LBT on at least one subband, it can perform Type 2 LBT or transmit uplink signals without performing LBT on each subband where LBT successfully completed within the maximum channel occupancy time (MCOT). This situation is called UE-shared COT.

[0125] If the PUCCH to be sent is located within the COT, the UE determines the LBT subband for sending the PUCCH based on the one or more LBT subbands where the COT is located.

[0126] Preferably, the UE determines whether the PUCCH is within the COT based on the LBT type of the PUCCH indicated by the base station. For example, if the LBT type is Type-1 channel access (also known as Cat-4 LBT), the PUCCH is considered to be outside the COT. If the LBT type is Type-2 channel access (also known as Cat-2 LBT) or Cat-1 LBT, the PUCCH is considered to be within the COT. Preferably, the UE determines whether the PUCCH is within the COT based on the COT time information indicated by the base station. For example, if the PUCCH is in time slot n+2, and the base station indicates that time slot n to time slot n+4 are within the COT, the PUCCH is within the COT.

[0127] Preferably, the UE determines the LBT subband where the PUCCH resource is located based on the uplink LBT subband corresponding to the downlink LBT subband where the PDCCH that triggered the PUCCH is located. The PDCCH and PUCCH belong to the same COT. For example, if the UCI carried by the PUCCH includes HARQ-ACK, the HARQ-ACK of the PDSCH scheduled by the PDCCH that triggered the PUCCH is carried by the PUCCH.

[0128] If all such PDCCHs are located in the same downlink LBT subband, the PUCCH is sent in the uplink LBT subband corresponding to this downlink LBT subband.

[0129] If all such PDCCHs are located in at least two different downlink LBT subbands, the uplink LBT subbands corresponding to one or more downlink LBT subbands are determined to be used for sending the PUCCH according to predefined rules. For example, the PUCCH may be sent in the uplink LBT subband corresponding to the downlink LBT subband where the latest PDCCH is located, or in the uplink LBT subband corresponding to the downlink LBT subband where the earliest PDCCH is located, or in the uplink LBT subband corresponding to each downlink LBT subband of all PDCCHs.

[0130] Preferably, the UE determines the LBT subband where the PUCCH resource is located based on the uplink LBT subband corresponding to the downlink LBT subband that successfully completed LBT. If more than one downlink LBT subband successfully completed LBT within a COT, the UE determines, based on predefined rules, which uplink LBT subbands correspond to one or more downlink LBT subbands to transmit the PUCCH. For example, the PUCCH is transmitted in the uplink LBT subband corresponding to the LBT subband with the lowest or highest LBT subband index among these downlink LBT subbands, or in the uplink LBT subband corresponding to all LBT subbands.

[0131] Preferably, the UE determines the LBT subband where the PUCCH resource is located based on the uplink LBT subband corresponding to the LBT subband where the PUSCH in the same uplink COT as the PUCCH is located. For example, if the UE transmits a PUSCH after performing the first type of LBT, the LBT subband set for transmitting the PUSCH is BW3. If the UE transmits the PUCCH after the PUSCH, and there is no gap in time between the two signals, the UE transmits the PUCCH in the LBT subband with the lowest or highest index in BW3, or transmits the PUCCH in every LBT subband within BW3.

[0132] If the first type of LBT is required before PUCCH is sent, that is, it does not belong to the shared COT, the UE determines the uplink LBT subband for sending PUCCH based on the LBT subband index indicated in the configured PUCCH resource.

[0133] Preferably, the base station configures the UE to determine the uplink LBT subband for sending PUCCH according to the LBT subband index indicated in the configured PUCCH resource, or determines the uplink LBT subband for sending PUCCH according to whether it is located in the COT.

[0134] According to another embodiment of the present invention, when configuring PUCCH resources, the base station configures whether the PUCCH resources can determine the LBT subband where the PUCCH is located based on the LBT subband where the shared COT is located.

[0135] If it is configured to determine the LBT subband where the PUCCH is located based on the LBT subband where the shared COT is located, the LBT subband where the PUCCH is located can be determined according to the method described above. Otherwise, the PUCCH can only be sent in the LBT subband configured in the PUCCH resource. This allows the base station to control the transmission resources of the PUCCH more flexibly. For example, the base station configures 8 PUCCH resources for the UE, and each PUCCH resource is configured to determine whether the PUCCH resource can determine the LBT subband where the PUCCH is located based on the LBT subband where the shared COT is located. For example, the 1st to 3rd PUCCH resources can determine the LBT subband where the PUCCH is located based on the LBT subband where the shared COT is located, while the 4th to 8th PUCCH resources cannot. If the base station expects the UE to send PUCCH strictly according to the LBT subband configured by the PUCCH resource, it can indicate one of the 4th to 8th PUCCH resources.

[0136] When configuring PUCCH resources, the base station can configure both the interlace index and the LBT subband index. According to the method described above, when predefined conditions are met, for example, when the PUCCH is located within the shared COT, the LBT subband index of the PUCCH determined based on the LBT subband of the COT overrides the LBT subband index in the configured PUCCH resource. When the PUCCH is located outside the shared COT, the LBT subband index in the configured PUCCH resource is used to determine the LBT subband where the PUCCH is located.

[0137] When configuring SRS resources, the base station can configure multiple SRS groups. Each SRS group contains one or more SRS resources. Each SRS resource can be located in the same LBT subband or in different LBT subbands. Preferably, an SRS resource is limited to one LBT subband. Preferably, an SRS resource can be in multiple LBT subbands, but the frequency domain resources of an SRS resource are continuous. Therefore, it is possible that within the same time unit, the UE has SRS resources to be transmitted in multiple LBT subbands.

[0138] Preferably, when configuring SRS resources, the base station also configures the physical resource block (PRB) and comb information for the SRS. The PRB information can be used to determine the LBT subband information for the SRS resource. Alternatively, when configuring SRS resources, the base station also configures the LBT subband index, as well as the PRB and comb information within the LBT subband.

[0139] Similarly, for an uplink sounding signal (SRS), the uplink LBT subband for sending the SRS may also be determined based on whether the SRS is located within the shared COT.

[0140] If the SRS to be sent is located within the COT, the UE determines the LBT subband for sending the SRS based on one or more LBT subbands where the COT is located. If the first type of LBT is required before sending the SRS, that is, it does not belong to the shared COT, the UE determines the uplink LBT subband for sending the SRS based on the LBT subband index indicated in the configured SRS resource. Alternatively, the base station configures the UE to determine the uplink LBT subband for sending the SRS based on the LBT subband index indicated in the configured SRS resource, or determines the uplink LBT subband for sending the SRS based on whether it is located within the COT. Alternatively, when configuring the SRS resource, the base station configures whether the SRS resource can determine the LBT subband where the SRS is located based on the LBT subband where the shared COT is located. If it is configured to determine the LBT subband where the SRS is located based on the LBT subband where the shared COT is located, the LBT subband where the SRS is located can be determined according to the method described above. Otherwise, the SRS can only be sent in the LBT subband configured in the SRS resource.

[0141] Preferably, the UE determines the LBT subband where the SRS resource is located based on the uplink LBT subband corresponding to the downlink LBT subband where the PDCCH that triggers the non-periodic SRS is located. The PDCCH and SRS belong to the same COT. Preferably, the UE determines on which LBT subbands to send the SRS based on the intersection of the LBT subband information of the configured SRS resources and the downlink LBT subband where the PDCCH is located. The intersection of the LBT subband where the SRS triggered by the base station is located and the LBT subband where the PDCCH that triggers the SRS is located is not an empty set. For example, the SRS triggered by the base station includes SRS1 in LBT subband 1 and SRS2 in LBT subband 2, and the PDCCH that triggers the SRS is on LBT subband 1, then the UE only sends SRS1 on LBT subband 1.

[0142] Preferably, the UE determines the LBT subband where the SRS resource is located based on the uplink LBT subband corresponding to the downlink LBT subband where LBT is successfully completed. Preferably, the UE determines on which LBT subbands to send the SRS based on the intersection of the LBT subband information of the configured SRS resource and the downlink LBT subband where LBT is successful for the COT where the SRS is located. The intersection of the LBT subband where the SRS triggered by the base station is located and the LBT subband where the PDCCH that triggers the SRS is located is not an empty set. For example, the SRS triggered by the base station includes SRS1 in LBT subband 1, SRS2 in LBT subband 2, and SRS in LBT subband 3, and LBT is successful for LBT subband 1 and subband 2 of the COT where the SRS is located, then the UE only sends SRS1 on LBT subband 1 and SRS2 on LBT subband 2.

[0143] Preferably, the UE determines the LBT subband where the SRS resource is located based on the uplink LBT subband corresponding to the LBT subband where the PUSCH in the same uplink COT as the SRS is located. The UE determines on which LBT subbands to send the SRS based on the intersection of the configured LBT subband information of the SRS resource and the uplink LBT subband where the PUSCH is sent in the same COT as the SRS. The intersection of the LBT subband where the SRS triggered by the base station is located and the LBT subband where the PUSCH is located is not an empty set. For example, the UE sends a PUSCH after performing the first type of LBT, and the LBT subband where the PUSCH is sent is LBT subband 1. The SRS triggered by the base station in the same COT as the PUSCH includes SRS1 in LBT subband 1 and SRS2 in LBT subband 2. In this case, the UE only sends SRS1 on LBT subband 1.

[0144] Preferably, if the intersection described above is an empty set, the UE determines the LBT subband for transmitting the SRS based on the one or more LBT subbands in which the COT is located. In this case, the LBT subband index of the SRS determined by the UE based on the LBT subband of the COT overwrites the LBT subband index in the configured SRS resource.

[0145] Preferably, if an SRS is located in at least two LBT subbands, and at least one of the LBT subbands does not belong to the intersection described above, the UE does not send the SRS.

[0146] Preferably, if an SRS is located in at least two LBT subbands, and at least one of the LBT subbands does not belong to the intersection described above, the UE only sends the SRS on the intersection.

[0147] Preferably, if the intersection of the LBT subband where the PUCCH or SRS is located and the COT subband is an empty set, for example, when the SRS or PUCCH resource indicated by the base station is to send the SRS or PUCCH in the configured LBT subband, and the intersection of the configured LBT subband and the COT subband is an empty set, the UE needs to perform the first type of LBT process. If the configured LBT subband partially overlaps with the COT subband (excluding the case where the configured LBT subband is a COT subband), the UE needs to perform the first type of LBT process on at least one of the configured LBT subbands.

[0148] The present invention does not limit how the UE determines the COT subband information. For example, the UE may determine the COT subband information through subband signaling sent by the base station, or by detecting a reference signal.

[0149] According to another embodiment of the present invention, the frequency domain resource information in the uplink signal transmission resource information in step 501 includes frequency domain resource information of a first type of frequency domain resource allocation mode and / or frequency domain resource information of a second type of frequency domain resource allocation mode. The first type of frequency domain resource allocation mode is frequency domain resource allocation based on interlace, and the second type of frequency domain resource allocation mode is frequency domain resource allocation information based on physical resource blocks (PRBs) or resource block groups (RBGs). Preferably, the resources allocated by the second type of frequency domain resource allocation mode are continuous in the frequency domain.

[0150] According to one implementation, a UE receives a fallback mode DCI scheduling an uplink signal, and the frequency domain resource allocation mode in the fallback mode DCI is determined based on the first type of configuration information. Preferably, the first type of configuration information is system information, and the system information indicates the first type or the second type of frequency domain resource allocation mode.

[0151] Preferably, if the system information does not indicate the frequency domain resource allocation mode, the frequency domain resource allocation in the fallback mode DCI is determined according to the predefined frequency domain resource allocation mode. Preferably, the predefined frequency domain resource allocation mode is the second type of frequency domain resource allocation mode.

[0152] Preferably, the frequency domain resource allocation mode in the fallback mode DCI in the common search space CSS of the control resource set CORESET 0 is determined according to the first type of configuration information; if the frequency domain resource allocation mode is not indicated in the first type of configuration information, it is determined according to a predefined frequency domain resource allocation mode.

[0153] The frequency domain resource allocation mode of the uplink scheduling information in the MAC RAR is determined according to the first type of configuration information; if the frequency domain resource allocation mode is not indicated in the first type of configuration information, it is determined according to a predefined frequency domain resource allocation mode.

[0154] Preferably, the frequency domain resource allocation mode in the fallback mode DCI in the CSS or user-specific search space USS of other CORESETs except COREST0 is determined according to the first type of configuration information; if the frequency domain resource allocation mode is not indicated in the first type of configuration information, it is determined according to a predefined frequency domain resource allocation mode.

[0155] According to another implementation, the frequency domain resource allocation pattern in the fallback mode DCI in the CSS or the user-specific search space USS of other CORESETs except COREST0 is determined according to a predefined frequency domain resource allocation pattern.

[0156] According to another implementation, after the UE receives UE-specific signaling indicating the first and / or second type of frequency domain resource allocation mode (referred to as the second type of configuration information), the frequency domain resource allocation mode in the fallback mode DCI in the CSS or user-specific search space USS of other CORESETs other than COREST0 is determined according to the UE-specific signaling; if the UE does not receive the second type of configuration information, the frequency domain resource allocation mode in the DCI is determined according to the predefined frequency domain resource allocation mode. Alternatively, if the UE does not receive the second type of configuration information, but the UE receives the first type of configuration information, the UE determines the frequency domain resource allocation mode in the DCI according to the first type of configuration information.

[0157] According to another implementation, before the UE receives the second type of configuration information, the frequency domain resource allocation mode in the fallback mode DCI is determined according to the first type of configuration information; if the frequency domain resource allocation mode is not indicated in the first type of configuration information, it is determined according to a predefined frequency domain resource allocation mode. After the UE receives the second type of configuration information, the frequency domain resource allocation mode in the fallback mode DCI is determined according to the second type of configuration information.

[0158] Preferably, the frequency domain resource allocation mode in the fallback mode DCI located in the common search space is determined according to the first type of configuration information; if the frequency domain resource allocation mode is not indicated in the first type of configuration information, it is determined according to a predefined frequency domain resource allocation mode.

[0159] Preferably, after the UE receives the second type of configuration information, the frequency domain resource allocation mode in the fallback mode DCI in the UE-specific search space is determined according to the second type of configuration information; if the UE does not receive the second type of configuration information, the frequency domain resource allocation mode in the DCI is determined according to a predefined frequency domain resource allocation mode. Alternatively, if the UE does not receive the second type of configuration information but receives the first type of configuration information, the UE determines the frequency domain resource allocation mode in the DCI according to the first type of configuration information.

[0160] According to another implementation, assuming that the uplink fallback mode DCI size for supporting the first type of frequency domain resource allocation mode is A, the uplink fallback mode DCI size for supporting the second type of frequency domain resource allocation mode is B, and the downlink fallback mode DCI size is C, if max(A,B)<C, and if the UE receives the first type of configuration information indicating the first type of frequency domain resource allocation mode, then the uplink fallback mode DCI can support dynamic switching between the first and second types of frequency domain resource allocation modes. If max(A,B)>C, the frequency domain resource allocation mode that the uplink fallback mode DCI can support is determined to be one of the first or second type of frequency domain resource allocation modes according to the first or second type of configuration information, and the size of the uplink fallback mode DCI is determined according to the corresponding frequency domain resource allocation mode. For non-fallback mode DCI, the frequency domain resource allocation mode that the DCI can support is determined to be one of the first or second type of frequency domain resource allocation modes according to the first or second type of configuration information, and the size of the uplink fallback mode DCI is determined according to the corresponding frequency domain resource allocation mode. Typically, to reduce the burden on UEs blindly detecting the PDCCH, the sizes of uplink and downlink DCIs in fallback mode are guaranteed to be the same. For example, by reducing the number of bits in larger DCIs or adding padding bits to smaller DCIs, the final sizes of different DCIs are made the same, thereby reducing the number of blind DCI detections. If the uplink fallback mode DCI size max(A,B) is smaller than the downlink fallback mode DCI size C, padding bits are required for the uplink fallback mode DCI. In this case, using the maximum uplink fallback mode DCI size max(A,B) can support more flexible frequency domain resource allocation modes without increasing the final DCI size (the final size is C). Typically, to avoid excessive DCI overhead or impact on scheduling performance, the DCI sizes of uplink and downlink non-fallback modes are not required to be the same. Therefore, the processing of uplink fallback and non-fallback DCIs should be different.

[0161] If the UE is configured for the first type of frequency domain resource allocation mode, the base station indicates not only the interlace index information but also the LBT subband information to which the allocated interlace belongs. Assume that the uplink fallback mode DCI size supporting interlace index information is A1, and the uplink fallback mode DCI size supporting both interlace index information and LBT subband information is A2, where A2>A1. The downlink fallback mode DCI size is C. If A2≤C, then the uplink fallback mode DCI may indicate both the interlace index information and the LBT subband information. If A2>C, then the uplink fallback mode DCI only indicates the interlace index information and does not indicate the LBT subband information.

[0162] In step 502, the frequency domain resources occupied by uplink signals are determined according to the frequency domain resource allocation mode, and in step 503, uplink signals are sent on the frequency domain resources.

[0163] According to another embodiment of the present invention, the time domain resource information in the uplink signal transmission resource information in step 501 includes the starting time of uplink signal transmission, or the duration of the occupied channel signal. For example, the base station may indicate the symbol starting point of the PUSCH valid signal in the UL Grant, where the starting point is the symbol boundary. The base station may also indicate the duration of the occupied channel signal before the valid signal symbol starting point in the UL Grant, or indicate the starting point of the occupied channel signal, where the starting point is located at the symbol boundary or within the symbol. The occupied channel signal may be the cyclic prefix extension (CP extention) of the first valid signal symbol.

[0164] Preferably, the length of the occupied channel signal does not exceed one symbol. The time length of the occupied channel signal is Among them L S is the symbol length, L i For a predefined length of time. S The length of can vary with the subcarrier spacing SCS, for example, the symbol length L when SCS is 15KHz S is the symbol length L when SCS is 30KHz S 2 times. L S The length of L may vary with the CP type (e.g., long CP or normal CP). In some scenarios, the CP lengths of multiple symbols in a slot / mini-slot are different, so L S Also different. In calculating O Li When the CP length of each symbol corresponding to the occupied channel signal is used, the corresponding S is determined. i , i=0,1,2,..I-1, is a set of predefined time lengths, for example, L0=0, L1=25us(microseconds), L2=25us+TA, L3=16us+TA. The base station directly or indirectly indicates L i , UE according to the indicated L i Determine the duration of the occupied channel signal O Li The time starting point of the occupied channel signal is one symbol before the starting point of the valid signal symbol. When L0=0, no occupied channel signal is sent.

[0165] Figure 6 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention. Figure 6 The embodiment shown is Figure 5The embodiments shown have similar contents, so similar contents will not be described in detail. Figure 6 The transmission method according to this embodiment may include:

[0166] Step 601: Count the number of failures of the joint LBT or the individual LBT performed on the uplink channel resources, wherein the frequency domain resources occupied by the uplink signal transmission include multiple uplink channel resources.

[0167] The joint LBT is performed in the following manner: a first type of channel access is performed on the i-th uplink channel resource; after the first type of channel access is successfully performed on the i-th uplink channel resource, a second type of channel access is performed on the j-th uplink channel resource. The step of counting the number of failures of the joint LBT or individual LBT performed on the uplink channel resource includes:

[0168] When the first type of channel access for the i-th uplink channel resource fails, the second type of channel access result for the j-th uplink channel resource is not counted as an LBT failure for the j-th uplink channel resource; at the same time, it is not counted as an LBT success for the j-th uplink channel resource.

[0169] Among them, the step of counting the number of joint LBT or individual LBT failures performed on the frequency domain resources occupied by multiple uplink signals includes: performing a first type of channel access for the i-th uplink channel resource; after the first type of channel access for the i-th uplink channel resource is successful, performing a second type of channel access for the j-th uplink channel resource; when the first type of channel access is successful but the second type of channel access fails, the second type of channel access result for the j-th uplink channel resource is not counted as an LBT failure for the frequency domain resources occupied by the i-th uplink signal; it is counted as an LBT failure for the frequency domain resources occupied by the j-th uplink signal.

[0170] In addition, when counting the number of failures, the number of LBT failures on one carrier, one BWP, or one LBT subband is counted.

[0171] In addition, when counting the number of LBT failures of a BWP, it is determined whether the current BWP has an LBT failure based on the LBT results of each LBT subband within a BWP.

[0172] Step 602: If the number of LBT failures exceeds the set threshold, LBT failure information is reported.

[0173] According to a transmission method of another embodiment of the present invention, when the first type of channel access for the i-th uplink channel resource fails, the second type of channel access result for the j-th uplink channel resource is not counted as an LBT failure for the j-th uplink channel resource; and at the same time, it is not counted as an LBT success for the j-th uplink channel resource. Furthermore, according to a transmission method of another embodiment of the present invention, when the first type of channel access is successful but the second type of channel access fails, the second type of channel access result for the j-th uplink channel resource is not counted as an LBT failure for the frequency domain resources occupied by the i-th transmitted uplink signal; and it is counted as an LBT failure for the frequency domain resources occupied by the j-th transmitted uplink signal. The transmission method of another embodiment of the present invention reduces system overhead and improves system efficiency through the above method.

[0174] The following describes in detail the technical solution for counting the number of LBT failures in conjunction with specific implementation methods.

[0175] When a UE operates in an unlicensed frequency band, it may need to perform a channel access procedure before transmitting a signal. Transmission can only be performed if and only if the channel is detected to be idle. This process is also known as LBT (Listen before talk).

[0176] To prevent the UE from continuously operating in a highly congested unlicensed frequency band carrier, BWP, or LBT subband, the UE can count the number of LBT failures. For example, the UE side maintains a counter that starts at 0 and increments by 1 each time the UE detects an LBT failure. In some scenarios, if the UE detects an LBT success, or detects N consecutive LBT successes, the counter is cleared and restarted. When the number of LBT failures exceeds the set threshold, the UE can report the LBT failure information to the base station. Accordingly, the base station can schedule the UE to another unlicensed frequency band carrier, BWP, or LBT subband based on this information.

[0177] The UE performs LBT on one or more uplink resources and counts the number of LBT failures. An uplink resource is a carrier, BWP, or LBT subband. If the UE performs LBT on multiple carriers, BWPs, or LBT subbands separately, the LBT count is determined based on the success of each individual LBT. If the UE performs joint LBT on multiple carriers, BWPs, or LBT subbands, the LBT success of each carrier, BWP, or LBT subband may be correlated.

[0178] If LBT fails or signal transmission fails on carrier i / BWPi / LBT subband i due to a busy channel on carrier i / BWPi / LBT subband i, this LBT failure reflects the busy / idle status of the channel on carrier i / BWPi / LBT subband i. If LBT fails or signal transmission fails on carrier j / BWPj / LBT subband j due to a busy channel on carrier i / BWPi / LBT subband i, this does not reflect the busy / idle status of the channel on carrier j / BWPj / LBT subband j. Therefore, this situation is not counted as an LBT failure on carrier j / BWPj / LBT subband j, nor is it counted as an LBT success on carrier j / BWPj / LBT subband j. In other words, this situation is not counted.

[0179] Specifically, when a UE is configured to perform joint LBT on multiple uplink carriers, if the UE fails to complete Type-1 channel access (also known as Cat-4 LBT) on one carrier i, resulting in the UE being unable to send uplink signals on other carriers j, it cannot be considered that the UE has failed LBT on carrier j. For example, if the UE selects a carrier i for Type-1 channel access, it can only perform Type-2 channel access on other carriers j if and only if carrier i successfully completes Type-1 channel access. And it can only perform uplink transmission on carrier j if and only if Type-2 channel access on carrier j is successful.

[0180] If the UE successfully completes the first type of channel access on carrier i but fails to access the second type of channel on carrier j, it is counted as an LBT failure of carrier j and cannot be counted as an LBT failure of carrier i.

[0181] If the UE fails to successfully complete the first type of channel access on carrier i, resulting in an inability to send uplink signals on carrier j, this is considered an LBT failure for carrier i and not an LBT failure for carrier j. In other words, an LBT failure for carrier i is considered an LBT failure only if the channel access process on carrier i fails.

[0182] If a UE is configured to perform LBT on a single BWP and perform joint LBT on the BWPs of multiple uplink carriers, if the UE fails to complete Type-1 channel access (also known as Cat-4 LBT) within a BWP on carrier i, resulting in the UE being unable to transmit uplink signals on the BWPs of other carriers j, this is not considered a LBT failure for the UE on the BWP of carrier j. For example, if a UE selects a BWP on carrier i for Type-1 channel access, it can only perform Type-2 channel access on the BWPs of other carriers j if and only if it successfully completes Type-1 channel access on the BWP of carrier i. Furthermore, it can only perform uplink transmission on the BWP of carrier j if and only if it successfully completes Type-2 channel access on the BWP of carrier j.

[0183] If a UE successfully completes the first type of channel access on the BWP of carrier i but fails to access the second type of channel on the BWP of carrier j, this is considered an LBT failure for the BWP of carrier j, and not an LBT failure for the BWP of carrier i. If a UE fails to successfully complete the first type of channel access on the BWP of carrier i, resulting in an inability to send uplink signals on the BWP of carrier j, this is considered an LBT failure for the BWP of carrier i, and not an LBT failure for the BWP of carrier j. In other words, an LBT failure for the BWP of carrier i is considered an LBT failure only if the channel access process on the BWP of carrier i fails.

[0184] When a UE is configured to perform joint LBT on multiple LBT subbands, if the UE fails to complete channel access on one LBT subband i, resulting in the UE being unable to transmit uplink signals on other LBT bandwidths j, this is not considered an LBT failure for the UE on LBT bandwidth j. For example, a UE selects an LBT subband i for first-category channel access. It can only perform second-category channel access on other LBT subbands j if and only if it successfully completes first-category channel access on LBT subband i. Furthermore, it can only perform uplink transmission on LBT subband i and LBT subband j if and only if it successfully completes second-category channel access on LBT subband j. If the UE successfully completes first-category channel access on LBT subband i but fails second-category channel access on LBT subband j, resulting in the UE being unable to transmit signals on both LBT subband i and LBT subband j, this is considered an LBT failure for LBT subband j, and not an LBT failure for LBT subband i. If the UE fails to successfully complete the first-category channel access on LBT subband i, resulting in an inability to transmit uplink signals on LBT subband j, this is considered an LBT failure for LBT subband i, and not an LBT failure for LBT subband j. In other words, an LBT failure for LBT subband i is considered an LBT failure only if the channel access procedure on LBT subband i fails.

[0185] It is not difficult to see that if a signal cannot be transmitted on a carrier / BWP / LBT subband, but LBT is not performed on this carrier / BWP / LBT subband, it cannot be counted as an LBT failure.

[0186] When the transmitter counts LBT failures, it does not count the aforementioned cases where a carrier, BWP, or LBT subband fails to transmit due to other carriers, BWPs, or LBT subbands. This prevents one carrier, BWP, or LBT subband from affecting the busy / idle statistics of another carrier, BWP, or LBT subband.

[0187] Preferably, LBT failure is counted based on carrier granularity, preferably, LBT failure is counted based on BWP granularity, and preferably, LBT failure is counted based on configured LBT subband granularity.

[0188] Preferably, when statistics are taken at the carrier granularity, LBT failures of each BWP or LBT subband are jointly counted.

[0189] Preferably, when statistics are calculated at the BWP granularity, LBT failures for all LBT subbands within a BWP are jointly counted. For example, if at least one LBT subband fails LBT in an uplink transmission, it is counted as a BWP LBT failure. Alternatively, if all LBT subbands fail LBT, it is counted as a BWP LBT failure. Alternatively, an LBT failure factor for a BWP is calculated using a weighted summation method for each LBT subband in an uplink transmission. If this LBT failure factor exceeds a preset threshold, it is counted as a BWP LBT failure. Alternatively, if the number of LBT subbands with LBT failures, or the ratio of the number of LBT subbands with LBT failures to the total number of LBT subbands in an uplink transmission, exceeds a preset threshold, it is counted as a BWP LBT failure. Preferably, as previously mentioned, failure to perform LBT on an LBT subband due to failures in other LBT subbands is not counted as an LBT failure for that LBT subband.

[0190] Preferably, when statistics are calculated at the BWP granularity, if an uplink transmission fails within that BWP due to an LBT failure within that BWP, it is counted as an LBT failure for that BWP. For example, the bandwidth of the currently activated BWP is 60 MHz, divided into three LBT subbands, each of which is 20 MHz. An uplink transmission is PUSCH1, and the base station allocates 40 MHz of uplink resources for PUSCH1, corresponding to two LBT subbands. If the UE succeeds in LBT on one LBT subband but fails on another, resulting in the inability to transmit PUSCH on either LBT subband, this is counted as an LBT failure. For another example, an uplink transmission is two SRS signals, SRS1 and SRS2, located on LBT subband 1 and LBT subband 2, respectively. If the UE succeeds in LBT on LBT subband 1 but fails on LBT subband 2, the UE can transmit SRS1 on LBT subband 1, and this does not count as an LBT failure. For another example, according to the method described in this embodiment, if the UE fails LBT on the BWP of another carrier, resulting in a transmission failure on the BWP of this carrier, it cannot be counted as an LBT failure of this BWP.

[0191] Preferably, when statistics are calculated at the BWP granularity, each BWP is counted separately. For example, if a UE can only operate on one active BWP at a time, but can operate on different BWPs at different times, each BWP can have a timer or counter to count LBT failures for each BWP. The LBT failure statistics for each BWP are determined using the method described above and will not be repeated here.

[0192] Figure 7 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention. Figure 7 The embodiment shown is Figure 5 The embodiments shown have similar contents, so similar contents will not be described in detail. Figure 7 The transmission method according to this embodiment may include:

[0193] Step 701: After successfully accessing the first type of channel, the UE sends a message A including a preamble sequence and a PUSCH.

[0194] Step 702: The UE adjusts the CWS according to the feedback information for the preamble sequence and / or PUSCH.

[0195] On the one hand, the step of adjusting the CWS according to the feedback information for the preamble sequence and / or PUSCH may include: resetting the CWS when the feedback information is a fallback random access response.

[0196] On the other hand, the step of adjusting the CWS according to the feedback information for the preamble sequence and / or PUSCH may include: resetting the CWS when the feedback information is a successful random access response.

[0197] According to another embodiment of the transmission method of the present invention, when the feedback information is a fallback random access response, the CWS remains unchanged, and when the feedback information is a successful random access response, the CWS is reset. Thus, the transmission method according to another embodiment of the present invention improves the accuracy of channel busy / idle determination, thereby reducing system overhead and improving system efficiency.

[0198] The following describes in detail the technical solution for adjusting the CWS in conjunction with specific implementation methods.

[0199] To reduce the probability of collisions between hidden terminals, the HARQ-ACK result of the last transmission can be used to indicate whether a collision has occurred between different transmitting nodes, and the contention window size (CWS) of the channel access process can be adjusted accordingly. Generally, negative acknowledgement (NACK) can indicate a collision to a certain extent. When the percentage of NACKs exceeds a set threshold, the transmitter increases the CWS; otherwise, it resets the CWS.

[0200] In the two-step random access process, the UE sends Msg A, including the random access preamble sequence, and PUSCH. If the UE receives feedback from the base station after sending Msg A, the UE does not increase the CWS. For example, if the UE sends Msg A preamble and Msg A PUSCH after completing the first type of channel access, if the UE receives its own fallback RAR, the UE resets the CWS. In the prior art, if the HARQ-ACK of the previous PUSCH is NACK or the base station schedules PUSCH retransmission, the UE increases the CWS. In this embodiment, although the base station did not successfully receive Msg A PUSCH and scheduled Msg A PUSCH retransmission through the fallback RAR, considering that the base station correctly received the preamble, it means that no collision of hidden terminals occurred or the mutual impact was very small, so there is no need to further increase the CWS to reduce the collision probability. If the UE does not receive any feedback from the UE, for example, the UE neither receives its own fallback RAR nor its own success RAR, the UE increases the CWS. According to another more conservative CWS adjustment method, if the UE receives its own success RAR, the UE resets the CWS; if the UE receives its own fallback RAR, the UE keeps the CWS unchanged; if the UE receives neither its own fallback RAR nor its own success RAR, the UE increases the CWS.

[0201] To avoid additional LBT between the Msg A preamble and the PUSCH, the two signals should be temporally contiguous. If the two signals cannot be temporally contiguous, padding can be sent and / or the PUSCH cyclic prefix can be increased to eliminate a gap between the two signals. Alternatively, if the time gap between the two signals is no greater than a set threshold, for example, a gap of 16µs, then no LBT is required before the Msg A PUSCH is sent, or a 16µs LBT can be performed.

[0202] The following describes the technical solution of paging opportunity in detail in conjunction with specific implementation methods.

[0203] To minimize the impact of LBT failures on the paging channel, multiple PDCCH monitoring occasions (PDCCH MOs) for paging are defined for each beam direction in a paging occasion. For example, a PO contains S*M PDCCH MOs, where S is the number of beams and M is the number of PDCCH MOs per beam.

[0204] In the licensed band, S is determined based on the number of SSBs actually sent. In the unlicensed band, the number of SSBs that can be sent each time may be different due to different LBT results before each SSB is sent. For example, the base station expects to send 4 SSBs. In one SSB transmission window, due to the late LBT success time, only 3 SSBs can be sent in the SSB transmission window. In the next SSB transmission window, due to the early LBT success time, 4 SSBs can be sent. To avoid the impact of the changing number of SSBs on the PDCCH MO, S cannot be determined based on the actual number of SSBs sent, but is determined based on the expected number of SSBs to be sent. The expected number of SSBs to be sent can be sent to the UE through system information or high-layer signaling.

[0205] If the base station can send two or more SSBs in an SSB transmission window, and these SSBs satisfy the QCL (Quasi-co-located) relationship, then the SSBs that satisfy Mod(Ai, Q) = Mod(Aj, Q) correspond to the same PDCCH MO, where Q is the QCL parameter and Ai and Aj are the DMRS indices of the SSB. For example, if the expected number of SSBs to be sent is S=4, Q=2, and M=4, a PO includes 4×4 PDCCH MOs, and the SSB of DMRS sequence i corresponds to the i-th, i+Q, i*2Q, ... PDCCH MOs.

[0206] Preferably, when calculating the PDCCH MO for paging in the PO, the number of SSBs expected to be sent that do not meet the QCL relationship is used, and the SSBs that meet the QCL relationship correspond to the same PDCCH MO. For example, if the number of SSBs expected to be sent is S=4, Q=2, and M=4, a PO includes 4×min(Q, S)=8 PDCCH MOs.

[0207] The present invention is applicable to transmission and reception in unlicensed frequency bands. In addition, the present invention is also applicable to applicable scenarios in licensed frequency bands.

[0208] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

[0209] If you say Figures 1 to 7 The illustrated embodiment is a detailed description of the embodiment of the present invention from the perspective of a UE, and the embodiment of the present invention will be described in detail from the perspective of a base station with reference to the corresponding drawings.

[0210] Figure 8 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention. Figure 8 The transmission method of the embodiment of the present invention shown includes:

[0211] Step 801: Send at least one DCI.

[0212] The DCI includes: a first bit area, a second bit area, and a third bit area. The first bit area is used to indicate the PDSCH group index scheduled by the DCI, the second bit area is used to indicate the ACK status of the PDSCH group scheduled by the DCI, and the third bit area is used to indicate that all processes feedback HARQ-ACK and is used to determine the ACK status of another PDSCH group other than the PDSCH group scheduled by the DCI.

[0213] The third bit region is composed of two bits and has a first state, a second state, a third state, and a fourth state. The first state is used to trigger HARQ-ACK feedback for the PDSCH group scheduled by the DCI, the second state is used to trigger HARQ-ACK feedback for two PDSCH groups, and the third state is used to trigger HARQ-ACK feedback for all HARQ processes and to indicate that the ACK state of another PDSCH group other than the PDSCH group scheduled by the DCI is a flipped state.

[0214] The fourth state is used to trigger HARQ-ACK feedback of all HARQ processes and is used to indicate that the ACK state of another PDSCH group other than the PDSCH group scheduled by the DCI is a non-inverting state.

[0215] The HARQ-ACK status information to be determined includes: the ACK status of the HARQ-ACK to be determined; the HARQ-ACK content to be determined also includes: the HARQ-ACK of the current PDSCH group, or the HARQ-ACK of two PDSCH groups, or the HARQ-ACK of all HARQ processes.

[0216] Step 802: Receive HARQ-ACK sent based on the HARQ-ACK time resource and / or HARQ-ACK status information determined by the DCI.

[0217] The step of sending HARQ-ACK further includes:

[0218] The third bit area includes two sub-bit areas. When the first sub-bit area triggers feedback of HARQ-ACK for all HARQ processes, the second sub-bit area indicates the ACK status of another PDSCH group other than the PDSCH group scheduled by the DCI. The HARQ-ACK value of each HARQ-ACK process is determined according to the ACK status of the other PDSCH group other than the PDSCH group scheduled by the DCI and the ACK status of the PDSCH group scheduled by the DCI indicated by the second bit area.

[0219] When the first sub-bit area does not trigger the feedback of HARQ-ACK for all HARQ processes, the second sub-bit area triggers the feedback of HARQ-ACK for the PDSCH group scheduled by the DCI, or HARQ-ACK for two PDSCH groups, and the value of HARQ-ACK for the PDSCH group is determined according to the ACK status of the PDSCH group scheduled by the DCI indicated by the second bit area.

[0220] Figure 1 The embodiment shown is an embodiment described on the UE side. Figure 8 The embodiment shown is an embodiment described on the base station side. There are some overlapping parts between the two embodiments, and the detailed description is omitted. However, those skilled in the art will understand Figure 1 The embodiments shown are sufficient to understand Figure 8 The embodiment shown.

[0221] According to an embodiment of the transmission method of the present invention, four states can be fed back respectively through the two bits of the third bit area of ​​​​DCI, namely, triggering HARQ-ACK feedback of the current PDSCH group, triggering HARQ-ACK feedback of two PDSCH groups, triggering HARQ-ACK feedback of all HARQ processes and used to indicate that the ACK state of another PDSCH group other than the current PDSCH group is a flipped state, triggering HARQ-ACK feedback of all HARQ processes and used to indicate that the ACK state of another PDSCH group other than the current PDSCH group is a non-flipped state.

[0222] However, in the prior art, when triggering HARQ-ACK feedback for the current PDSCH group, and triggering HARQ-ACK feedback for two PDSCH groups, one bit is required for implementation; when triggering HARQ-ACK feedback for all HARQ processes and indicating that the ACK state of another PDSCH group other than the current PDSCH group is in a flipped state, and when triggering HARQ-ACK feedback for all HARQ processes and indicating that the ACK state of another PDSCH group other than the current PDSCH group is not in a flipped state, one bit is required for implementation. That is, according to the prior art, if one wants to implement feedback of the four states of an embodiment of the transmission method of the present invention, three bits are required.

[0223] Therefore, the transmission method according to an embodiment of the present invention reduces the DCI overhead by 1 / 3 compared with the prior art.

[0224] Figure 9 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention. Figure 9 The transmission method of the embodiment of the present invention may include:

[0225] Step 901: Send multiple DCIs.

[0226] The HARQ-ACK timing value indicated in a DCI is a non-numeric value.

[0227] The DCI includes: a first bit area and a second bit area.

[0228] The first bit region is used to indicate the PDSCH group index scheduled by the DCI.

[0229] The second bit region is used to indicate the ACK status of the PDSCH group scheduled by the DCI.

[0230] Step 902: Receive HARQ-ACK sent based on the HARQ-ACK time resource and / or HARQ-ACK status information determined by the DCI.

[0231] Furthermore, the step of receiving the HARQ-ACK sent based on the HARQ-ACK time resource and / or HARQ-ACK status information determined by the DCI includes: determining, based on the DCI having the same value in the first bit area, the same value in the second bit area, and the smallest time interval, that its HARQ-ACK time resource is the same as the HARQ-ACK time resource with a non-numeric timing value; and receiving the HARQ-ACK according to the determined HARQ-ACK time resource.

[0232] Further, if the value of the first bit area is the same, and the value of the second bit area is the same, and there are two DCIs with the smallest time interval, then it is determined that the time resources of the HARQ-ACK of the two DCIs are the same as the time resources of the HARQ-ACK with a non-numeric timing value.

[0233] Figure 3 The embodiment shown is an embodiment described on the UE side. Figure 9 The embodiment shown is an embodiment described on the base station side. There are some overlapping parts between the two embodiments, and the detailed description is omitted. However, those skilled in the art will understand Figure 3 The embodiments shown are sufficient to understand Figure 9 The embodiment shown.

[0234] According to a transmission method of another embodiment of the present invention, when receiving a DCI whose HARQ-ACK timing value is a non-numeric value, the time resource of the HARQ-ACK corresponding to the first DCI can be determined according to the timing value in the second DCI.

[0235] However, in the prior art, when receiving a DCI with a non-numeric HARQ-ACK timing value, retransmission is required.

[0236] Therefore, compared with the prior art, the transmission method according to another embodiment of the present invention can significantly reduce system overhead and improve system efficiency.

[0237] Figure 10 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention. Figure 10 The transmission method of the embodiment of the present invention may include:

[0238] Step 1001: Send uplink signal transmission resource information.

[0239] Step 1002: Receive the uplink signal on the frequency domain resources determined based on the uplink signal transmission resource information.

[0240] Among them, the step of determining the frequency domain resources based on the uplink signal transmission resource information includes: determining the frequency domain resources occupied by sending the uplink signal according to the uplink signal transmission resource information, the channel occupancy time and the LBT sub-band corresponding to the COT; and receiving the uplink signal on the determined frequency domain resources.

[0241] Furthermore, the step of determining the frequency domain resources occupied by sending the uplink signal according to the uplink signal transmission resource information, the channel occupancy time, and the LBT subband corresponding to the COT includes:

[0242] When the uplink signal is located in the COT, determining the LBT sub-band where the uplink signal is located according to the LBT sub-band where the COT is located;

[0243] When the uplink signal is located outside the COT, the LBT sub-band where the uplink signal is located is determined according to the uplink signal transmission resource information.

[0244] Furthermore, the step of determining the frequency domain resources occupied by sending the uplink signal according to the uplink signal transmission resource information, the channel occupancy time, and the LBT subband corresponding to the COT includes:

[0245] When the LBT subband corresponding to the COT is the LBT subband where the PDCCH that triggers the uplink signal transmission is located, the PDCCH that triggers the uplink signal transmission and the uplink signal belong to the same COT; or,

[0246] The LBT sub-band corresponding to the COT is the LBT sub-band where the COT is located.

[0247] Figure 5 The embodiment shown is an embodiment described on the UE side. Figure 10 The embodiment shown is an embodiment described on the base station side. There are some overlapping parts between the two embodiments, and the detailed description is omitted. However, those skilled in the art will understand Figure 5 The embodiments shown are sufficient to understand Figure 10 The embodiment shown.

[0248] The transmission method of another embodiment of the present invention determines the LBT subband of the uplink signal based on the LBT subband of the COT when the uplink signal is within the COT; and determines the LBT subband of the uplink signal based on uplink signal transmission resource information when the uplink signal is outside the COT. Furthermore, the transmission method of another embodiment of the present invention determines that when the LBT subband corresponding to the COT is the LBT subband of the PDCCH that triggers the transmission of the uplink signal, the PDCCH that triggers the transmission of the uplink signal and the uplink signal belong to the same COT; or, alternatively, the LBT subband corresponding to the COT is the LBT subband of the COT.

[0249] The transmission method of another embodiment of the present invention reduces system overhead and improves system efficiency through the above method.

[0250] Figure 11 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention. Figure 11 The transmission method of the embodiment of the present invention may include:

[0251] Step 1001: Send uplink signal transmission resource information.

[0252] Step 1102: If the number of LBT failures exceeds the set threshold, LBT failure information is received, where the number of LBT failures is the number of failures of joint LBT or individual LBT performed on the frequency domain resources occupied by sending the uplink signal, where the frequency domain resources occupied by sending the uplink signal include: carrier and / or BWP and / or LBT bandwidth.

[0253] Furthermore, the number of LBT failures is: performing first-type channel access for the i-th uplink channel resource; after the first-type channel access for the i-th uplink channel resource is successful, performing second-type channel access for the j-th uplink channel resource; when the second-type channel access fails due to the failure of the first-type channel access, the LBT of the frequency domain resources occupied by the i-th uplink signal fails; the LBT of the frequency domain resources occupied by the j-th uplink signal does not fail; and at the same time, the LBT of the frequency domain resources occupied by the j-th uplink signal does not succeed.

[0254] Furthermore, the number of LBT failures is: performing first-type channel access for the i-th uplink channel resource; after the first-type channel access for the i-th uplink channel resource is successful, performing second-type channel access for the j-th uplink channel resource; when the first-type channel access is successful but the second-type channel access fails, the second-type channel access result for the j-th uplink channel resource is not counted as an LBT failure of the frequency domain resources occupied by the i-th uplink signal sent; it is counted as an LBT failure of the frequency domain resources occupied by the j-th uplink signal sent.

[0255] When counting the number of failures, the number of LBT failures on one carrier, one BWP, or one LBT subband is counted.

[0256] Among them, when counting the number of LBT failures of a BWP, it is determined whether the current BWP has LBT failure based on the LBT results of each LBT subband within a BWP.

[0257] Figure 6 The embodiment shown is an embodiment described on the UE side. Figure 11 The embodiment shown is an embodiment described on the base station side. There are some overlapping parts between the two embodiments, and the detailed description is omitted. However, those skilled in the art will understand Figure 6 The embodiments shown are sufficient to understand Figure 11 The embodiment shown.

[0258] According to a transmission method of another embodiment of the present invention, when the first type of channel access for the i-th uplink channel resource fails, the second type of channel access result for the j-th uplink channel resource is not counted as an LBT failure for the j-th uplink channel resource; and at the same time, it is not counted as an LBT success for the j-th uplink channel resource. Furthermore, according to a transmission method of another embodiment of the present invention, when the first type of channel access is successful but the second type of channel access fails, the second type of channel access result for the j-th uplink channel resource is not counted as an LBT failure for the frequency domain resources occupied by the i-th transmitted uplink signal; and it is counted as an LBT failure for the frequency domain resources occupied by the j-th transmitted uplink signal. The transmission method of another embodiment of the present invention reduces system overhead and improves system efficiency through the above method.

[0259] Figure 12 FIG. 1 is a flow chart of another embodiment of the transmission method of the present invention. Figure 12 The transmission method of the embodiment of the present invention may include:

[0260] Step 1201: After successful access to the first type of channel, a message A including a preamble sequence and a PUSCH is received.

[0261] The preamble sequence and PUSCH are continuous in time.

[0262] Step 1202: Accept adjustment of the CWS according to feedback information on the preamble sequence and / or PUSCH.

[0263] Further, the step of accepting the adjustment of the CWS according to the feedback information for the preamble sequence and / or PUSCH includes: accepting the adjustment of the CWS when the feedback information is a fallback random access response.

[0264] Figure 7 The embodiment shown is an embodiment described on the UE side. Figure 12 The embodiment shown is an embodiment described on the base station side. There are some overlapping parts between the two embodiments, and the detailed description is omitted. However, those skilled in the art will understand Figure 7 The embodiments shown are sufficient to understand Figure 12 The embodiment shown.

[0265] According to a transmission method in another embodiment of the present invention, when the feedback information is a fallback random access response, the CWS is reset, and when the feedback information is a fallback random access response, the CWS is reset. Thus, the transmission method in another embodiment of the present invention improves the accuracy of determining whether a channel is busy or idle, thereby reducing system overhead and improving system efficiency.

[0266] Figure 13 FIG. 1 is a module diagram of an embodiment of a transmission device of the present invention. Figure 13 As shown, the transmission device U1300 in this embodiment of the present invention may include at least: a first receiving module U1301, a first determining module U1302 and a first sending module U1303.

[0267] The first receiving module U1301 is configured to receive at least one DCI.

[0268] The DCI includes: a first bit area, a second bit area, and a third bit area. The first bit area is used to indicate the PDSCH group index scheduled by the DCI, the second bit area is used to indicate the ACK status of the PDSCH group scheduled by the DCI, and the third bit area is used to indicate that all processes feedback HARQ-ACK and is used to determine the ACK status of another PDSCH group other than the PDSCH group scheduled by the DCI.

[0269] The third bit area consists of two bits and has a first state, a second state, a third state, and a fourth state. The first state is used to trigger HARQ-ACK feedback of the PDSCH group scheduled by the DCI, the second state is used to trigger HARQ-ACK feedback of two PDSCH groups, the third state is used to trigger HARQ-ACK feedback of all HARQ processes and to indicate that the ACK state of another PDSCH group other than the PDSCH group scheduled by the DCI is a flipped state, and the fourth state is used to trigger HARQ-ACK feedback of all HARQ processes and to indicate that the ACK state of another PDSCH group other than the PDSCH group scheduled by the DCI is a non-flipped state.

[0270] The HARQ-ACK status information to be sent includes: the ACK status of the HARQ-ACK to be determined; the HARQ-ACK content to be determined also includes: the HARQ-ACK of the current PDSCH group, or the HARQ-ACK of two PDSCH groups, or the HARQ-ACK of all HARQ processes.

[0271] The first determination module U1302 is configured to determine the time resource and / or HARQ-ACK status information of the HARQ-ACK to be sent according to the DCI.

[0272] The first sending module U1303 is configured to send HARQ-ACK according to the determined HARQ-ACK time resource and / or HARQ-ACK status information.

[0273] The third bit area includes two sub-bit areas. The first sending module U1303 also includes:

[0274] A first sending sub-determination module is configured to, when the first sub-bit region triggers feedback of HARQ-ACK for all HARQ processes, indicate an ACK status of another PDSCH group other than the PDSCH group scheduled by the DCI, and determine a HARQ-ACK value for each HARQ-ACK process based on the ACK status of the other PDSCH group other than the PDSCH group scheduled by the DCI and the ACK status of the PDSCH group scheduled by the DCI indicated by the second bit region;

[0275] When the first sub-bit area does not trigger the feedback of HARQ-ACK for all HARQ processes, the second sub-bit area triggers the feedback of HARQ-ACK for the PDSCH group scheduled by the DCI, or HARQ-ACK for two PDSCH groups, and the value of HARQ-ACK for the PDSCH group is determined according to the ACK status of the PDSCH group scheduled by the DCI indicated by the second bit area.

[0276] Figure 13 The embodiment of the transmission device shown is Figure 1 There are some similarities between the two embodiments, and the detailed description is omitted. However, those skilled in the art will understand the hardware form of the transmission method embodiment. Figure 1 The transmission method embodiment shown is sufficient to understand Figure 13 The embodiment of the transmission device is shown.

[0277] According to one embodiment of the transmission device of the present invention, four states can be fed back respectively through the two bits of the third bit area of ​​​​DCI, namely, triggering HARQ-ACK feedback of the current PDSCH group, triggering HARQ-ACK feedback of two PDSCH groups, triggering HARQ-ACK feedback of all HARQ processes and used to indicate that the ACK state of another PDSCH group other than the current PDSCH group is a flipped state, triggering HARQ-ACK feedback of all HARQ processes and used to indicate that the ACK state of another PDSCH group other than the current PDSCH group is a non-flipped state.

[0278] However, in the prior art, when triggering HARQ-ACK feedback for the current PDSCH group, and triggering HARQ-ACK feedback for two PDSCH groups, one bit is required for implementation; when triggering HARQ-ACK feedback for all HARQ processes and indicating that the ACK state of another PDSCH group other than the current PDSCH group is in a toggle state, and when triggering HARQ-ACK feedback for all HARQ processes and indicating that the ACK state of another PDSCH group other than the current PDSCH group is not in a toggle state, one bit is required for implementation. That is, according to the prior art, if one wants to implement feedback for the four states of an embodiment of the transmission device of the present invention, three bits are required.

[0279] Therefore, an embodiment of the transmission device of the present invention reduces the DCI overhead by 1 / 3 compared with the prior art.

[0280] Figure 14 FIG. 1 is a module diagram of another embodiment of the transmission device of the present invention. Figure 14As shown, the transmission device U1500 in this embodiment of the present invention may include at least: a second receiving module U1501 , a second determining module U1502 , and a second sending module U1503 .

[0281] The second receiving module U1501 is configured to receive uplink signal transmission resource information.

[0282] The second determining module U1502 determines the frequency domain resources occupied by sending the uplink signal according to the uplink signal transmission resource information.

[0283] The second determination module U1502 may include: a second determination submodule (not shown) and a second determination submodule (not shown). The second determination submodule (not shown) is configured to determine the frequency domain resources occupied by the uplink signal based on the uplink signal transmission resource information, the channel occupancy time, and the LBT subband corresponding to the COT; and the second determination submodule (not shown) attempts to send the uplink signal on the determined frequency domain resources.

[0284] In addition, the second determination sub-determination module (not shown) is also used to determine the LBT sub-band where the uplink signal is located according to the LBT sub-band where the COT is located when the uplink signal is located within the COT; and to determine the LBT sub-band where the uplink signal is located according to the uplink signal transmission resource information when the uplink signal is located outside the COT.

[0285] In addition, the second determination sub-determination module (not shown) is also used to determine that the LBT sub-band corresponding to the COT is the LBT sub-band where the PDCCH that triggers the uplink signal transmission is located, and the PDCCH that triggers the uplink signal transmission and the uplink signal belong to the same COT.

[0286] The second sending module U1503 attempts to send the uplink signal on the determined frequency domain resources.

[0287] Figure 14 The embodiment of the transmission device shown is Figure 5 There are some similarities between the two embodiments, and the detailed description is omitted. However, those skilled in the art will understand the hardware form of the transmission method embodiment. Figure 5 The transmission method embodiment shown is sufficient to understand Figure 14 The embodiment of the transmission device is shown.

[0288] The transmission device of another embodiment of the present invention determines the LBT subband of the uplink signal based on the LBT subband of the COT when the uplink signal is within the COT; and determines the LBT subband of the uplink signal based on uplink signal transmission resource information when the uplink signal is outside the COT. Furthermore, the transmission device of another embodiment of the present invention determines that when the LBT subband corresponding to the COT is the LBT subband of the PDCCH that triggers the transmission of the uplink signal, the PDCCH that triggers the transmission of the uplink signal and the uplink signal belong to the same COT; or, alternatively, the LBT subband corresponding to the COT is the LBT subband of the COT.

[0289] The transmission device of another embodiment of the present invention reduces system overhead and improves system efficiency through the above method.

[0290] Figure 15 The figure shows a detailed schematic diagram of a hardware entity applicable to the present application. Figure 15 The hardware entity shown may be suitable for use as a base station, UE, or server in various embodiments of the present application. The hardware entity includes one or more processors, transceivers, etc., such as one or more central processing units (CPUs) 2301, and / or one or more coprocessors 2313. The processor may perform various appropriate actions and processes according to executable instructions stored in a read-only memory (ROM) 2302 or executable instructions loaded from a storage unit 2308 into a random access memory (RAM) 2303. The transceiver 2312 may include a transmitter and a receiver.

[0291] The processor can communicate with the read-only memory 2302 and / or the random access memory 2303 to execute executable instructions, be connected to the transceiver 2312 through the bus 2304, and connect with other entities through the transceiver 2312, thereby completing the operation corresponding to any method provided in the embodiments of the present application.

[0292] In addition, various programs and data required for device operation may also be stored in RAM 2303. CPU 2301, ROM 2302, and RAM 2303 are connected to each other via bus 2304. In the case of RAM 2303, ROM 2302 is an optional module. RAM 2303 stores executable instructions, or writes executable instructions into ROM 2302 during operation, and the executable instructions cause CPU 2301 to perform operations corresponding to the above-mentioned communication method. Input / output (I / O) interface 2305 is also connected to bus 2304. Transceiver 2312 can be integrated or configured to have multiple submodules (e.g., multiple IB network cards) and be connected on the bus.

[0293] The following components can be connected to the I / O interface 2305: an input unit 2306 including a keyboard, a mouse, and the like; an output unit 2307 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage unit 2308 including a hard disk; and a communication unit 609 including a network interface card such as a LAN card or a modem. The communication unit 609 performs communication processing via a network such as the Internet. A drive 2310 is also connected to the I / O interface 2305 as needed. A removable medium 2311, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 2310 as needed, so that a computer program read therefrom can be installed into the storage unit 2308 as needed.

[0294] If necessary, Figure 15 The architecture shown is only an optional implementation method. In the actual practice, the above architecture can be modified according to actual needs. Figure 15 The number and type of components can be selected, deleted, added, or replaced; different functional components can be configured separately or integrated. For example, the GPU and CPU can be configured separately or the GPU can be integrated with the CPU, and the transceiver can be configured separately or integrated with the CPU or GPU. These alternative implementations all fall within the scope of protection disclosed in this application.

[0295] In addition, according to the embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the present application provides a non-transitory machine-readable storage medium, which stores machine-readable instructions, and the machine-readable instructions can be executed by a processor to execute instructions corresponding to the method steps provided in the present application. In such an embodiment, the computer program can be downloaded and installed from the network through the communication unit 609, and / or installed from the removable medium 2311. When the computer program is executed by the central processing unit (CPU) 2301, the above-mentioned functions defined in the method of the present application are performed.

[0296] The methods and apparatus of the present application may be implemented in many ways. For example, the methods and apparatus of the present application may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above order of steps for the above method is for illustration only, and the steps of the method of the present application are not limited to the order specifically described above, unless otherwise specifically stated. In addition, in some embodiments, the present application may also be implemented as programs recorded in a recording medium, which include machine-readable instructions for implementing the methods according to the present application. Therefore, the present application also covers recording media that store programs for executing the methods according to the present application.

[0297] The above description is merely a preferred embodiment of the present application and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of protection provided in this application is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but also encompasses other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the technical concept. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A method performed by a user equipment (UE) in a communication system, characterized in that: include: Receive at least one downlink control information, the downlink control information including: a first bit area, a second bit area, and a third bit area, wherein: The first bit area is used to indicate the physical downlink shared channel group index scheduled by the downlink control information, The second bit area is used to indicate the response status of the physical downlink shared channel group scheduled by the downlink control information, The third bit region includes two sub-bit regions and has a first state, a second state, a third state, and a fourth state, wherein: The first state is used to trigger hybrid automatic repeat request-acknowledgement feedback of the physical downlink shared channel group scheduled by the downlink control information, The second state is used to trigger hybrid automatic repeat request-acknowledgement feedback of two physical downlink shared channel groups, The third state is used to trigger hybrid automatic repeat request-acknowledgement feedback of all hybrid automatic repeat request processes and is used to indicate that the response state of another physical downlink shared channel group other than the physical downlink shared channel group scheduled by the downlink control information is in a toggle state. The fourth state is used to trigger hybrid automatic repeat request-acknowledgement feedback of all hybrid automatic repeat request processes and is used to indicate that the response state of another physical downlink shared channel group other than the physical downlink shared channel group scheduled by the downlink control information is a non-reversal state; determining a time resource and / or content of a hybrid automatic repeat request-response to be sent according to the downlink control information; The hybrid automatic repeat request-acknowledgement is sent according to the determined time resource and / or content of the hybrid automatic repeat request-acknowledgement.

2. The method according to claim 1, characterized in that The hybrid automatic repeat request-response content to be sent includes: the response status of the hybrid automatic repeat request-response to be sent; The hybrid automatic repeat request-response content to be sent also includes: Hybrid Automatic Repeat Request-Appointment for the current physical downlink shared channel group, or Hybrid Automatic Repeat Request-Acknowledgement for two physical downlink shared channel groups, or HARQ-Response for all HARQ processes.

3. The method according to claim 2, characterized in that The step of sending a hybrid automatic repeat request-acknowledgement further comprises: When the first sub-bit area in the third bit area triggers feedback of the hybrid automatic repeat request-acknowledgement of all hybrid automatic repeat request processes, the second sub-bit area in the third bit area indicates the response status of another physical downlink shared channel group other than the physical downlink shared channel group scheduled by the downlink control information, and the value of the hybrid automatic repeat request-acknowledgement of each hybrid automatic repeat request-acknowledgement process is determined according to the response status of the other physical downlink shared channel group other than the physical downlink shared channel group scheduled by the downlink control information and the response status of the physical downlink shared channel group scheduled by the downlink control information indicated by the second bit area; and / or When the first sub-bit area in the third bit area does not trigger feedback of the hybrid automatic repeat request-acknowledgement of all hybrid automatic repeat request processes, the second sub-bit area in the third bit area triggers feedback of the hybrid automatic repeat request-acknowledgement of the physical downlink shared channel group scheduled by the downlink control information, or the hybrid automatic repeat request-acknowledgements of two physical downlink shared channel groups, and the value of the hybrid automatic repeat request-acknowledgement of the physical downlink shared channel group scheduled by the downlink control information is determined according to the response status of the physical downlink shared channel group scheduled by the downlink control information indicated by the second bit area.

4. The method according to claim 1, wherein The step of receiving at least one downlink control information comprises: receiving first downlink control information and second downlink control information, wherein the hybrid automatic repeat request-acknowledgement timing value indicated in the first downlink control information is a non-numeric value, and the hybrid automatic repeat request-acknowledgement timing value indicated in the second downlink control information is a numeric value; The step of determining the time resource of the hybrid automatic repeat request-reply to be sent according to the downlink control information includes: Determine, according to the timing value in the second downlink control information, a time resource of the hybrid automatic repeat request-response corresponding to the first downlink control information.

5. The method according to claim 4, characterized in that in, The step of determining, according to the timing value in the second downlink control information, a time resource of a hybrid automatic repeat request-response corresponding to the first downlink control information includes: According to the downlink control information with the same value in the first bit area, the same value in the second bit area, and the smallest time interval, it is determined that the time resource of the hybrid automatic repeat request-response is the same as the time resource of the hybrid automatic repeat request-response with a non-numeric timing value.

6. The method according to claim 4, characterized in that If the value of the first bit area is the same, the value of the second bit area is the same, and there are two downlink control information with the smallest time interval, then it is determined that the time resources of the hybrid automatic repeat request-response of the two downlink control information are the same as the time resources of the hybrid automatic repeat request-response with a non-numeric timing value.

7. The method according to claim 1, characterized in that The method further comprises: receiving uplink signal transmission resource information; Determining, according to the uplink signal transmission resource information, the time-frequency resources occupied by sending the uplink signal; Attempt to send the uplink signal on the determined time-frequency resource.

8. The method according to claim 7, characterized in that The step of determining the time-frequency resources occupied by sending the uplink signal includes: Determining frequency domain resources occupied by sending the uplink signal according to the uplink signal transmission resource information, the channel occupancy time, and the listen-before-send subband corresponding to the channel occupancy time; Attempt to send the uplink signal on the determined frequency domain resource.

9. The method according to claim 8, characterized in that The step of determining the time-frequency resources occupied by sending the uplink signal according to the uplink signal transmission resource information, the channel occupancy time, and the listen-before-send subband corresponding to the channel occupancy time includes: When the uplink signal is within the channel occupation time, determining the listen-before-send sub-band where the uplink signal is located according to the listen-before-send sub-band where the channel occupation time is located; When the uplink signal is outside the channel occupancy time, the listen-before-send subband where the uplink signal is located is determined according to the uplink signal transmission resource information.

10. The method according to claim 7, characterized in that After determining the time-frequency resources occupied by sending the uplink signal, the method further includes: The frequency domain resources occupied by sending the uplink signal include multiple uplink channel resources; Counting the number of failures of the joint listen-before-send or individual listen-before-send operations on the uplink channel resource; If the number of listen-before-send failures exceeds the set threshold, the listen-before-send failure information will be reported.

11. The method according to claim 10, characterized in that Perform joint listening before sending in the following way: For the i-th uplink channel resource, perform first-category channel access; After the first type of channel access for the i-th uplink channel resource is successfully performed, the second type of channel access is performed for the j-th uplink channel resource; The step of counting the number of failures of the joint listen-before-send or the separate listen-before-send on the uplink channel resource comprises: When the first type of channel access for the i-th uplink channel resource fails, the second type of channel access result for the j-th uplink channel resource is not regarded as a listen-before-send failure for the j-th uplink channel resource and is counted; It is not considered as a successful listen-before-send of the j-th uplink channel resource and is counted.

12. The method according to claim 10, characterized in that Perform joint listening before sending in the following way: For the i-th uplink channel resource, perform first-category channel access; After the first type of channel access is successfully performed for the i-th uplink channel resource, the second type of channel access is performed for the j-th uplink channel resource; The step of counting the number of failures of the joint listen-before-send or the separate listen-before-send on the uplink channel resource comprises: When the first type of channel access succeeds but the second type of channel access fails, the second type of channel access result for the jth uplink channel resource is not counted as a listen-before-send failure for the frequency domain resource occupied by the i-th uplink signal transmission; This is regarded as a listen-before-send failure of the jth frequency domain resource occupied by sending the uplink signal, and is counted.

13. The method according to claim 10, characterized in that in, When counting the number of failures, the number of listen-before-send failures on one carrier, one broadband portion, or one listen-before-send subband is counted.

14. The method according to claim 13, characterized in that When counting the number of listen-before-send failures of a broadband part, whether the current broadband part fails to listen-before-send is determined jointly according to the listen-before-send results of each listen-before-send subband within the broadband part.

15. The method according to claim 7, characterized in that The step of attempting to send the uplink signal on the determined frequency domain resource includes: After the first type of channel access is successful, a message A including a preamble sequence and a physical uplink shared channel is sent; The contention window size is adjusted according to feedback information on the preamble sequence and / or the physical uplink shared channel.

16. The method according to claim 8, characterized in that The step of adjusting the contention window size according to feedback information on the preamble sequence and / or the physical uplink shared channel includes: When the feedback information is a fallback random access response, resetting the contention window size; Alternatively, when the feedback information is a fallback random access response, the contention window size is kept unchanged.

17. A method performed by a base station in a communication system, characterized in that: include: Send at least one downlink control information, the downlink control information including: a first bit area, a second bit area, and a third bit area, wherein: The first bit area is used to indicate the physical downlink shared channel group index scheduled by the downlink control information, The second bit area is used to indicate the response status of the physical downlink shared channel group scheduled by the downlink control information, The third bit region includes two sub-bit regions and has a first state, a second state, a third state, and a fourth state, wherein: The first state is used to trigger hybrid automatic repeat request-acknowledgement feedback of the physical downlink shared channel group scheduled by the downlink control information, The second state is used to trigger hybrid automatic repeat request-acknowledgement feedback of two physical downlink shared channel groups, The third state is used to trigger hybrid automatic repeat request-acknowledgement feedback of all hybrid automatic repeat request processes and is used to indicate that the response state of another physical downlink shared channel group other than the physical downlink shared channel group scheduled by the downlink control information is in a toggle state. The fourth state is used to trigger hybrid automatic repeat request-acknowledgement feedback of all hybrid automatic repeat request processes and is used to indicate that the response state of another physical downlink shared channel group other than the physical downlink shared channel group scheduled by the downlink control information is a non-reversal state; Receive a hybrid automatic repeat request-acknowledgement time resource determined based on the downlink control information and / or a hybrid automatic repeat request-acknowledgement sent by the hybrid automatic repeat request-acknowledgement information.

18. The method according to claim 17, characterized in that The hybrid automatic repeat request-response includes: a response state of the hybrid automatic repeat request-response; The hybrid automatic repeat request-response further includes: Hybrid Automatic Repeat Request-Appointment for the current physical downlink shared channel group, or Hybrid Automatic Repeat Request-Acknowledgement for two physical downlink shared channel groups, or HARQ-Response for all HARQ processes.

19. The method according to claim 18, characterized in that When the first sub-bit area in the third bit area triggers feedback of the hybrid automatic repeat request-acknowledgement of all hybrid automatic repeat request processes, the second sub-bit area in the third bit area indicates the response status of another physical downlink shared channel group other than the physical downlink shared channel group scheduled by the downlink control information, and the value of the hybrid automatic repeat request-acknowledgement of each hybrid automatic repeat request-acknowledgement process is determined according to the response status of the other physical downlink shared channel group other than the physical downlink shared channel group scheduled by the downlink control information, and the response status of the physical downlink shared channel group scheduled by the downlink control information indicated by the second bit area; and / or When the first sub-bit area in the third bit area does not trigger feedback of the hybrid automatic repeat request-acknowledgement of all hybrid automatic repeat request processes, the second sub-bit area in the third bit area triggers feedback of the hybrid automatic repeat request-acknowledgement of the physical downlink shared channel group scheduled by the downlink control information, or the hybrid automatic repeat request-acknowledgement of two physical downlink shared channel groups, and the value of the hybrid automatic repeat request-acknowledgement of the physical downlink shared channel group is determined according to the response status of the physical downlink shared channel group scheduled by the downlink control information indicated by the second bit area.

20. The method according to claim 17, wherein The step of sending at least one downlink control information comprises: Sending first downlink control information and second downlink control information; wherein the hybrid automatic repeat request-acknowledgement timing value indicated in the first downlink control information is a non-numeric value, and the hybrid automatic repeat request-acknowledgement timing value indicated in the second downlink control information is a numeric value; The time resource of the hybrid automatic repeat request-response corresponding to the first downlink control information is determined according to the timing value in the second downlink control information.

21. The method according to claim 20, characterized in that The time resource of the hybrid automatic repeat request-response corresponding to the first downlink control information is the same as the time resource of the hybrid automatic repeat request-response with a non-numeric timing value, which is determined based on the downlink control information having the same value in the first bit area, the same value in the second bit area, and the smallest time interval.

22. The method according to claim 20, characterized in that If the value of the first bit area is the same, and the value of the second bit area is the same, and there are two downlink control information with the smallest time interval, the time resources of the hybrid automatic repeat request-response of the two downlink control information are the same as the time resources of the hybrid automatic repeat request-response with a non-numeric timing value.

23. The method according to claim 17, wherein The method further comprises: Sending uplink signal transmission resource information; Attempt to receive the uplink signal on frequency domain resources determined based on the uplink signal transmission resource information.

24. The method according to claim 23, wherein Attempting to receive the uplink signal on a frequency domain resource determined based on the uplink signal transmission resource information includes: Determining frequency domain resources occupied by the uplink signal according to the uplink signal transmission resource information, the channel occupancy time, and the listen-before-send subband corresponding to the channel occupancy time; The uplink signal is received on the determined frequency domain resource.

25. The method according to claim 24, characterized in that The step of determining the time-frequency resources occupied by the uplink signal according to the uplink signal transmission resource information, the channel occupancy time, and the listen-before-send subband corresponding to the channel occupancy time includes: When the uplink signal is within the channel occupation time, determining the listen-before-send sub-band where the uplink signal is located according to the listen-before-send sub-band where the channel occupation time is located; When the uplink signal is outside the channel occupancy time, the listen-before-send subband where the uplink signal is located is determined according to the uplink signal transmission resource information.

26. The method according to claim 23, wherein After determining the time-frequency resources occupied by the received uplink signal, the method further includes: The frequency domain resources occupied by sending the uplink signal include multiple uplink channel resources; When the number of listen-before-send failures exceeds a set threshold, listen-before-send failure information reported by the user equipment is received.

27. A user equipment UE, characterized in that include: transceiver; as well as A processor is coupled to the transceiver and configured to execute the method according to any one of claims 1 to 16.

28. A base station, characterized in that: include: transceiver; as well as A processor is coupled to the transceiver and configured to execute the method according to any one of claims 17 to 26.

Images