Wireless communication method, device and computer program product

Abstract

Disclosed herein are a wireless communication method, an apparatus, and a computer program product. The wireless communication method includes receiving, by a wireless communication device, a list of open loop power control parameter sets from a base station; receiving, by the wireless communication device, downlink control information (DCI) from the base station, the DCI comprising an open loop power control parameter set indication (OLI); determining, by the wireless communication device, a default subset from the list of sets of open-loop power control parameters; and determining, by the wireless communication device, an open loop power control parameter in the default subset according to the OLI.

Description

[0001] This application is a divisional application of the Chinese patent application with application number "201980102623.0", application date "September 29, 2019", and invention name "System and method for transmitting signals". Technical Field

[0002] The present disclosure relates to the field of telecommunications, and in particular, to uplink transmission of control information by wireless communication devices. Background Art

[0003] The demand for the fourth generation mobile communication technology (4G), Long-Term Evolution (LTE), Advanced LTE (LTE-Advanced or LTE-A), and the fifth generation mobile communication technology (5G) is growing rapidly. Development is underway to provide enhanced mobile broadband, ultra-high reliability, ultra-low latency transmission, and large-scale connectivity in 4G and 5G systems. Summary of the invention

[0004] The example embodiments disclosed herein are directed to solving problems related to one or more of the problems presented in the prior art, and to providing additional features that will become apparent when referring to the following detailed description in conjunction with the accompanying drawings. According to various embodiments, example systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and are not restrictive, and it will be apparent to those of ordinary skill in the art who have read this disclosure that various modifications may be made to the disclosed embodiments while remaining within the scope of this disclosure.

[0005] In some embodiments, the wireless communication device determines that uplink control information (UCI) transmitted on at least a portion of a first uplink resource is canceled. In response to determining that the UCI transmitted on the first resource is canceled, the wireless communication device determines that a second uplink resource is used to transmit the UCI. The wireless communication device transmits the UCI on the second uplink resource.

[0006] In some embodiments, the base station indicates to the wireless communication device that UCI transmitted on at least a portion of the first uplink resources is cancelled. The base station receives UCI from the wireless communication device on the second uplink resources.

[0007] The above and other aspects and embodiments thereof are described in more detail in the drawings, description and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Various example embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and depict only example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered as limiting the breadth, scope or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

[0009] Figure 1 is a schematic diagram showing that a physical uplink shared channel (PUSCH) resource is cancelled according to some embodiments of the present disclosure;

[0010] Figure 2 is a schematic diagram illustrating a method for determining a final physical uplink control channel (PUCCH) resource for transmitting uplink control information (UCI) according to some embodiments of the present disclosure;

[0011] Figure 3 is a schematic diagram illustrating a method for determining a PUCCH resource for transmitting UCI according to some embodiments of the present disclosure;

[0012] Figure 4 is a schematic diagram illustrating a method for recovering UCI transmission according to some embodiments of the present disclosure;

[0013] Figure 5 is a schematic diagram illustrating a method for recovering UCI transmission according to some embodiments of the present disclosure;

[0014] Figure 6 is a schematic diagram illustrating a method for recovering UCI transmission according to some embodiments of the present disclosure;

[0015] Figure 7 is a schematic diagram illustrating a method for determining a PUCCH resource for transmitting UCI according to some embodiments of the present disclosure;

[0016] Figure 8 is a schematic diagram illustrating a method for determining a PUCCH resource for transmitting UCI according to some embodiments of the present disclosure;

[0017] Fig. 9A and Fig. 9B is a flow chart illustrating a method for recovering UCI transmission according to some embodiments of the present disclosure;

[0018] Fig. 10A A block diagram illustrating an example base station according to some embodiments of the present disclosure; and

[0019] Fig. 10B A block diagram of an example UE according to some embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0020] Various example embodiments of the present solution are described below with reference to the accompanying drawings to enable those of ordinary skill in the art to make and use the present solution. As will be apparent to those of ordinary skill in the art, after reading this disclosure, various changes or modifications may be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the example embodiments and applications described and illustrated herein. Additionally, the specific order or hierarchy of steps in the methods disclosed herein are merely example methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes may be rearranged while remaining within the scope of the present solution. Therefore, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or actions in a sample order, and that the present solution is not limited to the specific order or hierarchy presented, unless otherwise expressly stated.

[0021] In order to support ultra-high reliability and ultra-low delay transmission, high reliability and low delay services are transmitted in relatively short transmission time intervals. When transmitting such high reliability and low delay services, in the case where high reliability and low delay services have a higher priority than other services with longer transmission time intervals, at least a portion of the resources used to transmit other services (which have not yet been transmitted or are being transmitted) with longer transmission time intervals can be preempted. In this case, different user terminals performing uplink transmission may not know this transmission resource preemption. In order to minimize the performance impact on high reliability and low delay services in this case, preemption indication information needs to be transmitted to user terminals whose transmission resources may be preempted. Based on this preemption indication information, the uplink transmission of services with relatively long transmission time intervals or relatively low reliability can be canceled (if not yet transmitted) or stopped (when being transmitted) accordingly, thereby avoiding the performance degradation caused by using the same uplink transmission resource to transmit two types of services at the same time.

[0022] Currently, regarding downlink transmission resource preemption, the configured reference downlink transmission resources are divided into 14 blocks, for example, using {M, N} = {14, 1} or {7, 2}. A bitmap that maps bits (indicating the preemption status) to blocks is used to indicate whether each of the blocks is preempted. M represents the number of partitions of the reference DL resource in the time domain. N represents the number of partitions of the reference DL resource in the frequency domain.

[0023] Regarding uplink transmission resource preemption, conventional solutions use uplink cancellation indication (UL CI). In response to a user equipment (UE) receiving an uplink CI and determining that the uplink transmission resources indicated by the UL CI overlap with the uplink transmission resources of the UE, the UE cancels the uplink transmission on the uplink transmission resources of the UE (if the uplink transmission has not been transmitted) or interrupts the uplink transmission on the uplink transmission resources of the UE (if the uplink transmission is being transmitted).

[0024] The canceled or interrupted uplink transmission may include UCI carried on PUCCH or PUSCH. For example, the canceled UCI includes hybrid automatic repeat request–acknowledgement (HARQ-ACK) information corresponding to the physical downlink shared channel (PDSCH). The HARQ-ACK information indicates the reception status (whether the downlink transmission carried in the PDSCH corresponding to the HARQ-ACK has been received by the UE). In this case, when the base station is not notified of the reception status of the downlink transmission in the PDSCH, the base station triggers the retransmission of all downlink transmissions corresponding to the canceled UCI, thereby greatly reducing the downlink transmission efficiency. In another example in which the canceled UCI includes channel state information (CSI) related to downlink scheduling, the base station cannot accurately perform downlink scheduling.

[0025] The present disclosure solves the UCI loss caused by the preemption of uplink transmission resources and the reduction in downlink data transmission efficiency caused by the cancellation of uplink transmission resources used to transmit UCI. In particular, the disclosed information transmission method, device and system effectively restore the transmission of UCI, thereby avoiding the reduction in downlink data transmission efficiency caused by the cancellation of UCI.

[0026] In some embodiments, with respect to uplink inter-UE multiplexing, power control can be used to provide transmission reliability for high priority services by dynamically increasing the transmission power used to transmit the high priority services. Specifically, in some examples, an open-loop power control parameter set indicator (OLI) field (e.g., N bits) is introduced into the scheduling downlink control information (DCI) for high priority services. Considering the sounding reference signal (SRS) resource indicator (SRI) field, which is also used to indicate the open-loop power control parameter set in the scheduling DCI, various methods can be used to determine the adopted open-loop power control parameter set.

[0027] In a first method, a list of open-loop power control parameter sets is configured using RRC signaling. The list of open-loop power control parameter sets is configured to include M subsets. SRI indicates a subset of the list of open-loop power control parameter sets. In some examples, OLI indicates an open-loop power control parameter set in a subset. The open-loop power control parameter set includes at least one of a received power P0 expected by a base station and a path loss compensation coefficient α. In an example in which the scheduled DCI does not include an SRI field, a first subset of the list of open-loop power control parameter sets is selected by default, and OLI indicates an open-loop power control parameter set in the first subset.

[0028] In a second method, RRC signaling is used to configure a list of open-loop power control parameter sets. The list of open-loop power control parameter sets is configured to include M subsets. OLI indicates a subset of the list of open-loop power control parameter sets. In some examples, SRI indicates an open-loop power control parameter set in a subset. The open-loop power control parameter set includes at least one of a received power P0 expected by a base station and a path loss compensation coefficient α. In an example in which the scheduled DCI does not include an SRI field, OLI indicates a subset of the list of open-loop power control parameter sets. A first configuration in a subset of the open-loop power control parameter set (identified by OLI) is set by default to an open-loop power control parameter.

[0029] In a third method, RRC signaling is used to configure a list of open-loop power control parameter sets. SRI indicates an open-loop power control parameter set in the list of open-loop power control parameter sets. OLI indicates an offset (e.g., adjustment amount) ΔP0 of the received power P0 expected by the base station. The set of values ​​of ΔP0 is configured by RRC signaling. In an example in which the scheduled DCI does not contain an SRI field, the first configuration of the list of open-loop power control parameter sets is used by default (configured using RRC). The offset indicated by OLI is used to determine the final open-loop power control parameter set adopted. In other examples, OLI may be defined as an offset (e.g., adjustment amount) Δα of a path loss compensation coefficient α. In addition, a set of values ​​of Δα is configured accordingly by RRC signaling. In other examples, OLI may be defined as an offset (e.g., adjustment amount) (ΔP0, Δα) of the received power P0 and the path loss compensation coefficient α expected by the base station. The set of values ​​of (ΔP0, Δα) is configured accordingly by RRC signaling.

[0030] In other implementations, uplink inter-UE multiplexing may be implemented by canceling the transmission of low priority traffic. Figure 1 1 is a schematic diagram illustrating a process 100 of canceling a physical uplink shared channel (PUSCH) uplink transmission resource according to some embodiments of the present disclosure. Figure 1, process 100 involves UE 102, base station 104 (e.g., gNodeB or gNB), and UE 106. Uplink transmission diagram 130 shows uplink activity of UE 102. Uplink transmission diagram 110 shows uplink transmission activity of UE 106. Downlink transmission diagram 120 shows downlink activity of base station 104. Figures 110, 120, and 130 show time slots divided in the time domain (represented by the x-axis). In some examples, the dimension or axis perpendicular to the time domain axis of each of the figures 110, 120, and 130 represents frequency, such as but not limited to bandwidth, active uplink bandwidth part (BWP), etc., although the frequency is discontinuous in different figures 110, 120, and 130.

[0031] UE 102 sends a scheduling request (SR) 132 to base station 104. SR 132 requests uplink transmission resources for uplink services (such as, but not limited to, enhanced mobile broadband (eMBB) services) from base station 104. Base station 104 allocates uplink transmission resources (e.g., PUSCH 134) to UE 102 via uplink grant (UL grant) 122. Base station 104 sends UL grant 122 to UE 102 to inform UE 102 that UE 102 can use PUSCH 134 to transmit uplink services.

[0032] After UE 102 sends SR 132 to base station 104, and after base station 104 sends UL grant 122 to UE 102, UE 106 sends SR 112 to base station 104. SR 132 requests uplink transmission resources for uplink services (such as, but not limited to, ultra-reliable low latency communication (URLLC) services) from base station 104. In the case where the uplink services (e.g., URLLC services) of UE 106 have ultra-high reliability and ultra-low latency transmission requirements, base station 104 allocates uplink transmission resources as early as possible in time. Base station 104 determines that uplink transmission resources (e.g., PUSCH 114) that meet the ultra-high reliability and ultra-low latency transmission requirements may have been allocated to UE 102. That is, base station 104 determines that at least a portion of PUSCH 134 conflicts with (e.g., overlaps in time) at least a portion of PUSCH 114. In response to determining that the priority of UE 106's uplink traffic (e.g., URLLC traffic) is higher than the priority of UE 102's uplink traffic (e.g., eMBB traffic), base station 104 cancels UE 102's transmission on previously allocated uplink transmission resources (e.g., PUSCH 134).

[0033] Various methods may be used to cancel low priority uplink transmissions. In one example, the base station 104 reschedules a new uplink transmission resource (e.g., PUSCH 136) for the UE 102, and then cancels the uplink transmission on the initially allocated uplink transmission resource (e.g., PUSCH 134). The base station 104 may retransmit the UL grant 126 to the UE 102 to notify the UE 102 that the UE 102 may use the PUSCH 136 to transmit uplink traffic (e.g., the transmission is rescheduled to another uplink transmission resource PUSC 136). In some examples, the base station 104 may transmit the UL grant 126 simultaneously with the UL grant 124 (e.g., in the same time slot) using different frequency resources. The HARQ process identifier (ID) of the UL grant 126 is the same as the HARQ process ID of the UL grant 122. The new data indicator (NDI) field of the UL grant 126 is switched, thereby indicating that the uplink grant 126 corresponds to an uplink service (e.g., an eMBB service) for which uplink transmission resources (e.g., PUSCH 134) were previously allocated, and the previously allocated uplink transmission resources (e.g., PUSCH 134) are released. In some examples, this method can be used to reschedule and release the entire initially allocated uplink transmission resource (e.g., PUSCH 134) or a portion thereof. Moreover, the new uplink transmission resource (e.g., PUSCH 136) can be used to transmit the entire transport block (TB) or a portion thereof.

[0034] In another example, the base station 104 may use cancellation indication signaling (e.g., UL CI) to inform the UE 102 that the initially allocated uplink transmission resources (e.g., PUSCH 134) are preempted by high priority traffic transmission. Therefore, in response to receiving the cancellation indication signaling, the UE 102 cancels the transmission on the preempted resources (e.g., PUSCH 134). The cancellation indication signaling may be carried in the physical DCI or another specific signal sequence on the downlink control channel.

[0035] In yet another example, the base station 104 may instruct the UE 102 to reduce the transmission power on the entire initially allocated uplink transmission resource (e.g., PUSCH 134) or a portion thereof to zero to indirectly cancel transmission on the entire initially allocated uplink transmission resource (e.g., PUSCH 134) or a portion thereof, respectively. Thus, in response to receiving a transmission power reduction command / signal from the base station 104, the UE 102 cancels transmission on the entire initially allocated uplink transmission resource (e.g., PUSCH 134) or a portion thereof.

[0036] In some embodiments, UCI of low priority services (such as but not limited to eMBB services of UE 102 or low priority services of URLLC services) may be carried on PUCCH. The transmission of high priority services (such as but not limited to high priority services of URLLC services) may preempt uplink transmission resources occupied by PUCCH, thereby causing the transmission of low priority services on PUCCH to be cancelled. Therefore, due to such preemption, UCI may not be transmitted.

[0037] UCI includes one or more of HARQ-ACK feedback information, SR information, CSI, etc. Different types of UCI are separately configured PUCCH transmission resources. In an example where the PUCCH transmission resources of two or more types of UCI overlap in the time domain, different types of UCI (bits) are multiplexed according to predefined rules to generate multiplexed UCI. The PUCCH resources that transmit multiplexed UCI (including different types of UCI) are referred to as final PUCCH in this article.

[0038] Figure 2 is a schematic diagram illustrating a method 200 for determining a final PUCCH resource 210 for transmitting UCI according to some embodiments of the present disclosure. Figure 2 , different types of UCI include HARQ-ACK, CSI, and SR. HARQ-ACK, CSI, and SR are separately configured with PUCCH resources, namely, HARQ-ACK PUCCH resources 202, CSI PUCCH resources 204, and SRPUCCH resources 206. In response to determining that the PUCCH resources 202, 204, and 206 overlap with each other in the time domain, the bits of HARQ-ACK, CSI, and SR are multiplexed together to generate multiplexed UCI. The final PUCCH resource 210 for transmitting the multiplexed UCI is re-determined.

[0039] In some examples, the final PUCCH resource 210 is determined by selecting a PUCCH resource set based on the number of bits of the multiplexed UCI. The PUCCH resource is selected from the PUCCH resource set based on an indication in the scheduling DCI of the last PDSCH corresponding to the HARQ-ACK. The PUCCH format is determined based on an indication in the scheduling DCI of the last PDSCH corresponding to the HARQ-ACK. The UE may transmit the multiplexed UCI on the final PUCCH resource 210. A similar method may be used to determine the PUCCH resource and the format of the PUCCH resource for transmitting HARQ-ACK multiplexed with either CSI or SR.

[0040] Figure 33 is a schematic diagram illustrating a method 300 for determining a PUCCH resource (eg, a CSI PUCCH resource 304) for transmitting UCI according to some embodiments of the present disclosure. Figure 3 , method 300 involves multiplexing types of UCI other than HARQ-ACK. As shown, two different types of UCI (except HARQ-ACK), such as but not limited to CSI and SR, are separately configured with PUCCH resources, CSIPUCCH resources 304 and SR resources PUCCH 306. In response to determining that PUCCH resources 304 and 306 overlap each other in the time domain, bits of CSI and SR are multiplexed together to generate multiplexed UCI. The UE transmits the multiplexed UCI using CSIPUCCH resources 304. That is, CSIPUCCH resources 304 are selected as the final PUCCH resource on which the multiplexed UCI is transmitted.

[0041] In other embodiments, the UE transmits UCI on the PUSCH. For example, in response to determining that the PUCCH carrying UCI (e.g., including HARQ-ACK feedback information, SR information, CSI, etc.) overlaps with the scheduled PUSCH of the UE in the time domain, the UE transmits UCI on a portion of the PUSCH resources. The UCI and uplink data are independently encoded. The encoded UCI is mapped to a portion of the PUSCH resources determined according to a predefined rule. In the case where a portion of the PUSCH resources is occupied by UCI, puncturing or rate matching transmission is used to transmit the PUSCH, and the uplink data is mapped to the remaining portion of the PUSCH resources not occupied by UCI.

[0042] Thus, in response to determining that a UCI transmission on a PUSCH or PUCCH is canceled in the manner described herein (particularly in examples where the UCI includes HARQ-ACK feedback information), the UCI may be retransmitted (e.g., the UCI transmission is resumed). The scenario of cancellation of transmission on a PUSCH or PUCCH due to a conflict with a high priority service transmission is used for illustrative purposes. Cancellation of transmission on a PUSCH resource or a PUCCH resource may be caused by other reasons. For example, if a transmission on a PUSCH resource or a PUCCH resource is determined to conflict with a frame structure configuration, the transmission may be canceled. In another example, a transmission on a PUSCH resource or a PUCCH resource may be canceled due to a conflict with other uplink transmissions of the same UE or a different UE. In yet another example, a transmission on a PUSCH resource or a PUCCH resource may be canceled due to a power limitation of the UE (e.g., the UE does not have sufficient power to transmit data on a PUSCH resource or a PUCCH resource).

[0043] Figure 4 4 is a schematic diagram illustrating a method 400 for recovering UCI transmission according to some embodiments of the present disclosure. Figures 1 to 4 , method 400 involves downlink activity of a UE (shown in downlink transmission diagram 410) and uplink activity of a UE (shown in uplink transmission diagram 420). Diagrams 410 and 420 show time slots in the time domain (represented by the x-axis). In some examples, a dimension or axis perpendicular to the time domain axis of each of diagrams 410 and 420 represents frequency, such as but not limited to bandwidth, active uplink BWP, etc., although frequency is discontinuous on different diagrams 410 and 420.

[0044] like Figure 4 As shown, the UE receives a downlink transmission from the network (e.g., a base station) on PDSCH 412. The UE is initially instructed to transmit UCI on uplink transmission resource PUCCH 406. In some examples, the UCI includes feedback information (e.g., HARQ-ACK feedback information) that provides feedback for PDSCH 412. The UE receives an uplink scheduling PDCCH 414 that schedules transmissions on uplink transmission resource PUSCH 402. In some examples, in response to determining that PUCCH 406 and PUSCH 402 overlap in the time domain, the UCI (initially to be transmitted using PUCCH 406) is multiplexed with uplink data to be transmitted using PUSCH 402 to generate multiplexed data. The UE determines to transmit the multiplexed data (including UCI) on PUSCH 402. In some examples, the UCI is mapped to a portion of PUSCH 402 according to a predefined rule. The PUSCH 402 and the PUCCH 406 overlap in the time domain while occupying different frequency bandwidths (eg, different frequency resources) in the active UL BWP.

[0045] The UE then receives a UL CI 416 from the network (e.g., a base station). The UL CI 416 indicates that at least a portion of the PUSCH 402 is cancelled. In one example, the reason for the cancellation may be that a transmission on the uplink resources 404 (by another UE or by the same UE) conflicts with at least a portion of the PUSCH 402, where the uplink resources 404 and a portion of the PUSCH 402 overlap with each other. In response to the UL CI 416, the UE determines to cancel the transmission 402 on the PUSCH. In some examples, the UE cancels the transmission on the cancelled portion of the PUSCH 402. The cancelled portion of the PUSCH 402 is the portion indicated by the UL CI 416 to be cancelled (e.g., the portion overlapping with the uplink resources 404 in the time domain) and any remaining portion after the portion indicated by the UL CI 416 in the time domain. As shown, the cancelled portion of the PUSCH 402 starts at time point A and ends when the PUSCH 402 ends. In other words, the UE cancels any uplink transmission on the PUSCH 402 that occurs after time point A (time point). The UE does not cancel any uplink transmission on the PUSCH 402 that occurs before time point A.

[0046] The UCI may be initially scheduled to be transmitted on the canceled portion of the PUSCH 402. A processing time (e.g., N symbols) is required to process (e.g., decode) the UL CI 416 and cancel the transmission on the canceled portion of the PUSCH 402. The time interval P represents the time interval between the end of the UL CI 416 (e.g., the end of the last symbol of the UL CI 416) and the beginning of the canceled portion of the PUSCH 402 (e.g., the beginning of the first symbol of the canceled portion of the PUSCH 402). If the time interval P is greater than the processing time, the UE may successfully cancel the transmission on the canceled portion of the PUSCH 402. On the other hand, if the time interval P is less than the processing time, the UE may not be able to successfully cancel the transmission on the canceled portion of the PUSCH 402.

[0047] In the method 400, the PUCCH 406 is not cancelled. In some examples, cancellation of the PUCCH 406 by any uplink transmission with a higher priority is not allowed. In some examples, although cancellation of the PUCCH 406 is allowed, the PUCCH 406 is not cancelled if the PUCCH 406 does not collide with any uplink transmission with a higher priority and the start of the first symbol of the PUCCH 406 is not earlier than the time point A.

[0048] The UE determines whether the PUCCH 406 can be retransmitted on the PUCCH. A time interval from the end of the last symbol of the UL CI 416 to the start of the first symbol of the PUCCH 406 is defined as a time interval T. In response to determining that the time interval T is greater than or equal to a time interval defined as a length of time required for the UE to decode the UL CI 416 and prepare to transmit UCI on the PUCCH 406, the UE determines to transmit UCI on the PUCCH 406. On the other hand, in response to determining that the time interval T is less than the time required for the UE to decode the UL CI 416 and prepare to transmit UCI on the PUCCH 406, the UE cannot complete decoding the UL CI 416 and preparing to transmit UCI on the PUCCH 406, and therefore determines not to transmit UCI on the PUCCH 406.

[0049] Alternatively, in response to determining that transmission on the PUCCH 406 is not cancelled and the start of the first symbol of the PUCCH 406 is at or no earlier than time point A, the UE determines to transmit the UCI on the PUCCH 406 .

[0050] Figure 5 is a schematic diagram illustrating a method 500 for recovering UCI transmission according to some embodiments of the present disclosure. Figures 1 to 5 , method 500 involves downlink activity of a UE (shown in downlink transmission diagram 510) and uplink activity of a UE (shown in uplink transmission diagram 520). Diagrams 510 and 520 show time slots in the time domain (represented by the x-axis). In some examples, the dimension or axis perpendicular to the time domain axis of each of diagrams 510 and 520 represents frequency, such as but not limited to bandwidth, active uplink BWP, etc., although frequency is discontinuous on different diagrams 510 and 520.

[0051] like Figure 5As shown, the UE receives a downlink transmission from the network (e.g., a base station) on PDSCH 512. The UE is initially instructed to transmit UCI on uplink transmission resource PUCCH 506. In some examples, the UCI includes feedback information (e.g., HARQ-ACK feedback information) that provides feedback for PDSCH 512. The UE receives an uplink scheduling PDCCH 514 that schedules transmissions on uplink transmission resource PUSCH 502. In some examples, in response to determining that PUCCH 506 and PUSCH 502 overlap in the time domain, UCI (initially to be transmitted using PUCCH 506) is multiplexed with data bits to be transmitted using PUSCH 502 to generate multiplexed data. The UE determines to transmit the multiplexed data (including UCI) on PUSCH 502. In some examples, according to a predefined rule, UCI is mapped to a portion of PUSCH 502. The PUSCH 502 and PUCCH 506 overlap in the time domain while occupying different frequency bandwidths (eg, different frequency resources) in the active UL BWP.

[0052] The UE then receives UL CI 516 from the network (e.g., a base station). UL CI 516 indicates that at least a portion of PUSCH 502 is cancelled. In one example, the reason for the cancellation may be that a transmission on uplink resources 504 (by another UE or by the same UE) collides with at least a portion of PUSCH 502, in the case where uplink resources 504 and a portion of PUSCH 502 overlap in the time domain. In response to UL CI 516, the UE determines to cancel the transmission 502 on PUSCH.

[0053] The UCI may be initially scheduled for transmission on the cancellation portion of the PUSCH 502. The UE requires processing time (e.g., N symbols) to process (e.g., decode) the UL CI 516 and cancel the transmission on the cancellation portion of the PUSCH 502. If the time interval between the end of the UL CI 516 (e.g., after the end of the last symbol of the UL CI 516) and the beginning of the cancellation portion of the PUSCH 502 (e.g., before the beginning of the first symbol of the cancellation portion of the PUSCH 502) is greater than the processing time, the UE may successfully cancel the transmission on the cancellation portion of the PUSCH 502. On the other hand, if the time interval between the end of the UL CI 516 and the beginning of the cancellation portion of the PUSCH 502 is less than the processing time, the UE may not successfully cancel the transmission on the cancellation portion of the PUSCH 502.

[0054] The UE cancels uplink transmissions on the canceled portion of the PUSCH 502. In some examples, the UE cancels the portion of the PUSCH 502 N symbols after the end of the UL CI 516 (e.g., after the end of the last symbol of the UL CI 516). As shown, the canceled portion of the PUSCH 502 starts at time point B and ends at the end of the PUSCH 502. In other words, the UE cancels any uplink transmissions on the PUSCH 502 that occur after time point B (time point). The UE does not cancel any uplink transmissions on the PUSCH 502 that occur before time point B.

[0055] In the method 500, the PUCCH 506 is not cancelled. In some examples, cancellation of the PUCCH 506 by any uplink transmission with a higher priority is not allowed. In some examples, although cancellation of the PUCCH 506 is allowed, the PUCCH 506 is not cancelled if the PUCCH 506 does not collide with any uplink transmission with a higher priority and the start of the first symbol of the PUCCH 506 is not earlier than the time point B.

[0056] The UE determines whether the PUCCH 506 can be retransmitted on the PUCCH. A time interval from the end of the last symbol of the UL CI 516 to the start of the first symbol of the PUCCH 506 is defined as a time interval T. In response to determining that the time interval T is greater than or equal to a time interval defined as a length of time required for the UE to decode the UL CI 516 and prepare to transmit UCI on the PUCCH 506, the UE determines to transmit UCI on the PUCCH 506. On the other hand, in response to determining that the time interval T is less than the time required for the UE to decode the UL CI 516 and prepare to transmit UCI on the PUCCH 506, the UE cannot complete decoding the UL CI 516 and preparing to transmit UCI on the PUCCH 506, and therefore determines not to transmit UCI on the PUCCH 506.

[0057] Alternatively, in response to determining that transmission on the PUCCH 506 is not cancelled and the start of the first symbol of the PUCCH 406 is at or no earlier than time point B, the UE determines to transmit the UCI on the PUCCH 506 .

[0058] Figure 6 is a schematic diagram illustrating a method 600 for recovering UCI transmission according to some embodiments of the present disclosure. Figures 1 to 6 , as referenced Figure 4 and Figure 5As described above, the UE cancels transmission on the canceled portion of PUSCH 402 or PUSCH 502 according to UL CI 416 or 516. Specifically, the UE cancels transmission on the portion of PUSCH 402 after time point A. The UE cancels transmission on the portion of PUSCH 502 after time point B. The portions of PUSCH 402 and PUSCH 502 before time point A and time point B, respectively, can still be used to transmit data. Figure 6 As shown, PUSCH 402 or PUSCH 502 includes a transmission portion 610 and a cancellation portion 620. Cancellation portion 620 corresponds to a portion of PUSCH 402 after time point A or a portion of PUSCH 502 after time point B.

[0059] The UE determines whether all bits of the UCI are transmitted on the transmission portion 610 of the PUSCH 402 or 502. That is, in response to determining that the complete UCI (e.g., all bits of the UCI) is transmitted on the transmission portion 610 of the PUSCH 402 or 502, the UE does not need to transmit any part of the UCI on the PUCCH 406 or 506.

[0060] In response to determining that the complete UCI is not transmitted on the transmission portion 610 (e.g., not all bits of the UCI are transmitted on the transmission portion 610), the UE determines whether the UCI can be transmitted on the PUCCH 406 or 506. In some embodiments, in response to determining that the PUCCH 406 or 506 is not cancelled, the start of the first symbol of the PUCCH 406 or 506 is after the time point A or the time point B, respectively, and the time interval T (e.g., the time interval from the end of the last symbol of the UL CI 416 or 516 to the start of the first symbol of the PUCCH 406 or 506, respectively) is greater than or equal to the time required for the UE to decode the UL CI 416 or 516 and prepare for PUCCH transmission, the UE determines to transmit the UCI on the PUCCH 406 or 506, respectively. On the other hand, in response to determining that PUCCH 406 or 506 is canceled, the start of the first symbol of PUCCH 406 or 506 is before time point A or time point B, respectively, or the time interval T is less than the time required for the UE to decode UL CI 416 or 516 and prepare for PUCCH transmission, the UE determines not to transmit UCI on PUCCH 406 or 506.

[0061] Alternatively, in response to determining that the complete UCI is not transmitted on the transmission portion 610, the UE determines whether the UCI can be transmitted on the PUCCH 406 or 506. In response to determining that the PUCCH 406 or 506 is not cancelled and the start of the first symbol of the PUCCH 406 or 506 is not earlier than the time point A or the time point B, respectively, the UE determines to transmit the UCI on the PUCCH 406 or 506. In some examples, bits of the UCI that have not been transmitted in the transmission portion 610 are transmitted on the PUCCH 406 or 506. In some examples, all bits of the UCI are transmitted on the PUCCH 406 or 506. On the other hand, in response to determining that the PUCCH 406 or 506 is cancelled or the start of the first symbol of the PUCCH 406 or 506 is earlier than the time point A or the time point B, respectively, the UE determines not to transmit the UCI on the PUCCH 406 or 506.

[0062] In some embodiments, as shown in reference Figure 4 and Figure 5 As described, the UE cancels transmission on the canceled portion of PUSCH 402 or PUSCH 502 according to UL CI 416 or 516. Specifically, the UE cancels transmission on the portion of PUSCH 402 after time point A. The UE cancels transmission on the portion of PUSCH 502 after time point B. The portions of PUSCH 402 and PUSCH 502 before time points A and B, respectively, can still be used to transmit data.

[0063] In some examples where the UCI to be transmitted includes two or more different types of UCI (e.g., two or more different types of HARQ-ACK, SR, and CSI), the UE determines whether to transmit all bits of each type of UCI in the portion before time point A of the PUSCH 402 or in the portion before time point B of the PUSCH 502. Although HARQ-ACK is used for illustrative purposes, the same process may be performed for other types of UCI, such as, but not limited to, SR and CSI.

[0064] In some implementations, the UE determines whether all bits of the HARQ-ACK are transmitted on the transmission portion of the PUSCH 402 or 502. In response to determining that a complete HARQ-ACK (e.g., all bits of the HARQ-ACK) is transmitted on the transmission portion of the PUSCH 402 or 502, the UE does not need to transmit any portion of the HARQ-ACK on the PUCCH 406 or 506.

[0065] In response to determining that a complete HARQ-ACK for UCI is not transmitted on the transmission portion of PUSCH 402 or 502 (e.g., not all bits of HARQ-ACK are transmitted on the transmission portion of PUSCH 402 or 502), the UE determines whether HARQ-ACK can be transmitted on PUCCH 406 or 506. In response to determining that PUCCH 406 or 506 is not cancelled and the start of the first symbol of PUCCH 406 or 506 is not earlier than time point A or time point B, respectively, the UE determines to transmit HARQ-ACK on PUCCH 406 or 506. In some examples, bits of HARQ-ACK that are not transmitted in the transmission portion of PUSCH 402 or 502 are transmitted on PUCCH 406 or 506. In some examples, all bits of HARQ-ACK are transmitted on PUCCH 406 or 506. On the other hand, in response to determining that the PUCCH 406 or 506 is canceled or the start of the first symbol of the PUCCH 406 or 506 is earlier than the time point A or the time point B, respectively, the UE determines not to transmit HARQ-ACK on the PUCCH 406 or 506.

[0066] Alternatively, in some embodiments, in response to determining that a complete HARQ-ACK is not transmitted on the transmission portion of the PUSCH 402 or 502 (e.g., not all bits of the HARQ-ACK are transmitted on the transmission portion of the PUSCH 402 or 502), the UE determines whether the HARQ-ACK can be transmitted on the PUCCH 406 or 506. For example, in response to determining that the PUCCH 406 or 506 is not cancelled, the start of the first symbol of the PUCCH 406 or 506 is after the time point A or the time point B, respectively, and the time interval T (e.g., the time interval from the end of the last symbol of the UL CI 416 or 516 to the start of the first symbol of the PUCCH 406 or 506, respectively) is greater than or equal to the time required for the UE to decode the UL CI 416 or 516 and prepare for PUCCH transmission, the UE determines to transmit the HARQ-ACK on the PUCCH 406 or 506, respectively. On the other hand, in response to determining that PUCCH 406 or 506 is canceled, the start of the first symbol of PUCCH 406 or 506 is before time point A or time point B, respectively, or the time interval T is less than the time required for the UE to decode UL CI 416 or 516 and prepare for PUCCH transmission, the UE determines not to transmit HARQ-ACK on PUCCH 406 or 506.

[0067] In some embodiments, the UE cancels transmission on the canceled portion of PUSCH 402 or PUSCH 502 according to UL CI 416 or 516. Specifically, the UE cancels transmission on the portion of PUSCH 402 after time point A. The UE cancels transmission on the portion of PUSCH 502 after time point B. The portions of PUSCH 402 and PUSCH 502 before time points A and B, respectively, can still be used to transmit data. Figure 6 As shown, PUSCH 402 or PUSCH 502 includes a transmission portion 610 and a cancellation portion 620 , wherein data may be transmitted on the transmission portion 610 .

[0068] In some examples where the UCI to be transmitted includes two or more different types of UCI (e.g., two or more different types of HARQ-ACK, SR, and CSI), the UE determines whether to transmit all bits of each type of UCI in the transmission portion 610 (e.g., the portion before time point A of the PUSCH 402 or the portion before time point B of the PUSCH 502). In a scenario, all bits of one or more types of UCI (e.g., all bits of HARQ-ACK) can be transmitted on the transmission portion 610, while all bits of other types of UCI (e.g., all bits of CSI and SR) cannot be transmitted on the transmission portion 610, and the UE determines whether to use the PUCCH to transmit the other types of UCI that are not completed.

[0069] As reference Figure 2As described, different types of UCI include HARQ-ACK, CSI, and SR. HARQ-ACK, CSI, and SR are separately configured with PUCCH resources, HARQ-ACK PUCCH resources 202, CSI PUCCH resources 204, and SRPUCCH resources 206. In response to determining that the PUCCH resources 202, 204, and 206 overlap each other in the time domain, the bits of HARQ-ACK, CSI, and SR are multiplexed together to generate multiplexed UCI. The final PUCCH resource 210 for transmitting the multiplexed UCI is re-determined. In some examples, the final PUCCH resource 210 is determined by selecting a PUCCH resource set according to the number of bits of the multiplexed UCI. According to the indication in the scheduling DCI of the last PDSCH corresponding to the HARQ-ACK, the PUCCH resource is selected from the PUCCH resource set. The PUCCH format is determined according to the indication in the scheduling DCI of the last PDSCH corresponding to the HARQ-ACK. The UE can transmit the multiplexed UCI on the final PUCCH resource 210. A similar method may be used to determine the PUCCH resources and the format of the PUCCH resources used to transmit HARQ-ACK multiplexed with either CSI or SR.

[0070] Figure 7 is a schematic diagram illustrating a method 700 for determining PUCCH resources for transmitting UCI according to some embodiments of the present disclosure. Figures 1 to 7 In some cases, all bits of one type of UCI (e.g., as an example, HARQ-ACK) are transmitted on the transmission portion 610 (of the PUCCH resource 710, which may be the PUCCH 406 or 506). The initially allocated HARQ-ACK PUCCH resources 702 are not used. The remaining portion of the UCI that needs to be transmitted includes other types of UCI (e.g., as an example, CSI and SR). In the case where the initially configured uplink transmission resources for transmitting CSI (e.g., CSIPUCCH resources 704) overlap in the time domain with the initially configured uplink transmission resources for transmitting SR (e.g., SR PUCCH resources 706), as shown in the method 700, the bits of the SR information are multiplexed with the bits of the CSI to generate multiplexed UCI. The UE transmits the multiplexed UCI on the initially configured CSIPUCCH resources 704.

[0071] In some embodiments, the UE further determines whether to transmit the remaining part of the UCI (e.g., the CSI and SR in the multiplexed UCI), which needs to be transmitted on the uplink transmission resource (e.g., the CSIPUCCH resource 704) initially configured for one of the remaining parts of the UCI. For example, in response to determining that the CSI PUCCH resource 704 is not cancelled (e.g., no conflict) and the start of the first symbol of the CSIPUCCH resource 704 is respectively at time point A (relative to the reference Figure 4 described embodiments) or time point B (relative to reference Figure 5 After the UE determines to transmit the multiplexed UCI on the CSIPUCCH resource 704. On the other hand, in response to determining that the CSIPUCCH resource 704 is cancelled (e.g., conflicted) or the start of the first symbol of the CSIPUCCH resource 704 is respectively at time point A (relative to the reference Figure 4 described embodiments) or time point B (relative to reference Figure 5 Before the described embodiment), the UE determines not to transmit the multiplexed UCI on the CSIPUCCH resource 704.

[0072] In some embodiments, the UE uses an alternative method to determine whether to transmit the multiplexed UCI on the CSIPUCCH resource 704. For example, in response to determining that the CSIPUCCH resource 704 is not cancelled (e.g., there is no conflict), the start of the first symbol of the CSIPUCCH resource 704 is respectively at time point A (relative to the reference Figure 4 described embodiments) or time point B (relative to reference Figure 5 The UE determines to transmit the multiplexed UCI on the CSIPUCCH resource 704 in response to determining that the CSIPUCCH resource 704 is cancelled (e.g., conflicted), the start of the first symbol of the CSIPUCCH resource 704 is respectively at time point A (relative to the reference 4 embodiment) and the time interval T (e.g., the time interval from the end of the last symbol of the UL CI 416 or 516 to the start of the first symbol of the CSIPUCCH resource 704) is greater than or equal to the time required for the UE to decode the UL CI 416 or 516 and prepare for PUCCH transmission of the multiplexed UCI. On the other hand, in response to determining that the CSIPUCCH resource 704 is cancelled (e.g., conflicted), the start of the first symbol of the CSIPUCCH resource 704 is respectively at time point A (relative to the reference 4 embodiment). Figure 4 described embodiments) or time point B (relative to reference Figure 5 The UE determines not to transmit the multiplexed UCI on the CSIPUCCH resource 704 before the described embodiment) and the time interval T is less than the time required for the UE to decode the UL CI 416 or 516 and prepare for PUCCH transmission of the multiplexed UCI.

[0073] In some embodiments, the UE cancels transmission on the canceled portion of PUSCH 402 or PUSCH 502 according to UL CI 416 or 516. Specifically, the UE cancels transmission on the portion of PUSCH 402 after time point A. The UE cancels transmission on the portion of PUSCH 502 after time point B. The portions of PUSCH 402 and PUSCH 502 before time points A and B, respectively, can still be used to transmit data. Figure 6 As shown, PUSCH 402 or PUSCH 502 includes a transmission portion 610 and a cancellation portion 620 , wherein data may be transmitted on the transmission portion 610 .

[0074] In some examples where the UCI to be transmitted includes two or more different types of UCI (e.g., two or more different types of HARQ-ACK, SR, and CSI), the UE determines whether to transmit all bits of each type of UCI in the transmission portion 610 (e.g., the portion before time point A of the PUSCH 402 or the portion before time point B of the PUSCH 502). In a scenario, all bits of one or more types of UCI (e.g., all bits of CSI) can be transmitted on the transmission portion 610, while all bits of other types of UCI (e.g., all bits of HARQ-ACK and SR) cannot be transmitted on the transmission portion 610, and the UE determines whether to use the PUCCH to transmit the other types of UCI that are not completed.

[0075] in this regard, Figure 8 8 is a schematic diagram illustrating a method 800 for determining a PUCCH resource for transmitting UCI according to some embodiments of the present disclosure. Figures 1 to 8 , HARQ-ACK, CSI and SR are separately configured with PUCCH resources - HARQ-ACK PUCCH resources 802, CSI PUCCH resources 804 and SR PUCCH resources 806. PUCCH resources 810 are based on Figure 2The PUCCH resources determined in the described manner, for example, PUCCH resource 810 is the final PUCCH resource 210 for carrying multiplexed UCI including multiplexed HARQ-ACK, CSI and SR. In some examples, a portion of the PUCCH resource 810 is canceled, and the complete CSI is transmitted on the transmission portion of the PUCCH resource 810, while the complete HARQ-ACK and SR are not transmitted on the transmission portion of the PUCCH resource 810. In this case, the bits of HARQ-ACK and SR are multiplexed together to generate a new multiplexed UCI. Therefore, many bits in the new multiplexed UCI have been changed, resulting in the PUCCH resource set being changed. RRC signaling configures multiple PUCCH resource sets for the UE based on different numbers of bits of the UCI. That is, different PUCCH resource sets correspond to different numbers of bits in the new multiplexed UCI. PUCCH resource 812 is selected from the PUCCH resource set according to the indication in the scheduling DCI of the last PDSCH corresponding to HARQ-ACK. The PUCCH format of the PUCCH resource 812 is determined according to the indication in the scheduling DCI of the last PDSCH corresponding to HARQ-ACK. The UE may transmit the new multiplexed UCI 812 on the PUCCH resource.

[0076] In some embodiments, the UE also determines whether to transmit the remaining portion of the UCI that needs to be transmitted on the PUCCH resource (e.g., HARQ-ACK and SR in the newly multiplexed UCI) 812. For example, in response to determining that the PUCCH resource 812 is not cancelled (e.g., no conflict) and the start of the first symbol of the PUCCH resource 812 is respectively at time point A (relative to the reference Figure 4 described embodiments) or time point B (relative to reference Figure 5 After the UE determines to transmit the newly multiplexed UCI on the PUCCH resource 812, the UE determines to transmit the newly multiplexed UCI on the PUCCH resource 812. On the other hand, in response to determining that the PUCCH resource 812 is cancelled (e.g., conflicted) or the start of the first symbol of the PUCCH resource 812 is respectively at the time point A (relative to the reference Figure 4 described embodiments) or time point B (relative to reference Figure 5 Before the described embodiment), the UE determines not to transmit new multiplexed UCI on the CSIPUCCH resource 812.

[0077] In some embodiments, the UE uses an alternative method to determine whether to transmit the newly multiplexed UCI on the PUCCH resource 812. For example, in response to determining that the PUCCH resource 812 is not cancelled (e.g., there is no conflict), the start of the first symbol of the PUCCH resource 812 is respectively at time point A (relative to the reference Figure 4described embodiments) or time point B (relative to reference Figure 5 The UE determines to transmit the new multiplexed UCI on the PUCCH resource 812 in response to determining that the PUCCH resource 812 is cancelled (e.g., colliding), the start of the first symbol of the PUCCH resource 812 is respectively at time point A (relative to the reference 400), and the time interval T (e.g., the time interval from the end of the last symbol of the UL CI 416 or 516 to the start of the first symbol of the PUCCH resource 812) is greater than or equal to the time required for the UE to decode the UL CI 416 or 516 and prepare for PUCCH transmission of the new multiplexed UCI. On the other hand, in response to determining that the PUCCH resource 812 is cancelled (e.g., colliding), the start of the first symbol of the PUCCH resource 812 is respectively at time point A (relative to the reference 400), and the start of the first symbol of the PUCCH resource 812 is respectively at time point A (relative to the reference 400). Figure 4 described embodiments) or time point B (relative to reference Figure 5 The UE determines not to transmit new multiplexed UCI on the CSIPUCCH resource 812 before the described embodiment) and the time interval T is less than the time required for the UE to decode the UL CI 416 or 516 and prepare for PUCCH transmission of the new multiplexed UCI.

[0078] In some embodiments, the UE cancels transmission on the canceled portion of PUSCH 402 or PUSCH 502 according to UL CI 416 or 516. Specifically, the UE cancels transmission on the portion of PUSCH 402 after time point A. The UE cancels transmission on the portion of PUSCH 502 after time point B. In some examples, in response to the UL CI, all of PUSCH 402 or PUSCH 502 may be canceled.

[0079] In some cases, when determining whether the PUCCH can be used to transmit UCI in the manner described, the UE determines that the PUCCH (e.g., PUCCH 406 or 506) is also cancelled, for example, when the PUCCH is allowed to be cancelled by any uplink transmission with a higher priority and the PUCCH resource overlaps with another uplink transmission resource indicated by the UL CI (for uplink transmission with a higher priority). Alternatively, when, for example, the start of the first symbol of the PUCCH resource is earlier than the time point A (relative to the reference Figure 4 described embodiments) or time point B (relative to reference Figure 4 In the case of the embodiment described above, the UE determines that the PUCCH is not available for transmitting the UCI. In response to determining that the initial PUCCH cannot be used to transmit the UCI, the UE continues to determine a new PUCCH resource for transmitting the UCI.

[0080] In some embodiments, the UE selects a PUCCH resource within a PUCCH resource set to which the initial PUCCH resource belongs, wherein the selected PUCCH resource has the same format as the format of the initial PUCCH resource. The start of the first symbol of the selected PUCCH resource is no earlier than time point A (relative to the reference Figure 4 described embodiments) or time point B (relative to reference Figure 5 Embodiments described herein). The UE uses the selected PUCCH resource as a new PUCCH resource on which to transmit UCI. In response to determining that multiple PUCCH resources satisfy the conditions described herein, a selection rule may be implemented to select one of these PUCCH resources for transmitting UCI. In some examples, the first PUCCH resource in the PUCCH resource set that satisfies the conditions described herein is selected to transmit UCI. In another example, the earliest starting PUCCH resource with the first symbol among multiple PUCCH resources (satisfying the conditions described herein) is selected to transmit UCI. Other selection rules may also be implemented.

[0081] Fig. 9A is a flow chart illustrating a method 900a for resuming UCI transmission according to some embodiments of the present disclosure. Figures 1 to 9A , method 900a is implemented by the UE in the manner described herein.

[0082] At 910a, the UE determines that transmission UCI on at least a portion of a first uplink resource (e.g., a PUSCH) is canceled. In some examples, the UCI includes at least one of HARQ confirmation information, CSI, or SR. In some examples, in response to the UCI transmitted on the first uplink resource colliding with a transmission having a higher priority than the UCI transmitted on the first uplink resource, the UCI transmitted on the first uplink resource is canceled.

[0083] In some examples, in response to receiving an uplink grant from the base station indicating the release of the first uplink resource, the UE determines to cancel the UCI transmitted on the first uplink resource. In some examples, in response to receiving an UL CI from the base station indicating that the transmission on the first uplink resource is canceled, the UE determines that the UCI transmitted on the first uplink resource is canceled. In some examples, in response to receiving a transmission power reduction command, the UE determines that the UCI transmitted on the first uplink resource is canceled.

[0084] At 920a, in response to determining that UCI transmitted on the first resource is cancelled, the UE determines a second uplink resource for transmitting UCI (eg, PUCCH).

[0085] In some examples, determining that a second uplink resource is used to transmit UCI includes: defining a first time interval from the end of a last symbol of a UL CI to the beginning of a first symbol of a second uplink resource; defining a second time interval as a length of time required for a UE to decode the UL CI and prepare to transmit UCI on a second uplink resource; and in response to determining that the first time interval is greater than or equal to the second time interval, determining that the second uplink resource is used to transmit UCI.

[0086] In some examples, in response to determining that a canceled portion of a first uplink resource starts from a start time point indicated by a UL CI, determining that a second uplink resource is not canceled, and determining that a start of a first symbol of the second uplink resource is no earlier than the start time point, the second uplink resource is determined to be used to transmit UCI.

[0087] In some examples, in response to determining that the UE cancels transmission on the canceled portion of the first uplink resource starting from a time interval after the end of the last symbol of the UL CI, the time interval corresponds to the length of time required for the UE to decode the UL CI and prepare to transmit UCI on the second uplink resource, and the start of the first symbol of the second uplink resource is no earlier than the start time point of the canceled portion of the first uplink resource, it is determined that the second uplink resource is used to transmit UCI.

[0088] In some examples, the first uplink resource includes a cancellation portion and a transmission portion. Method 900a also includes determining whether all bits of UCI are transmitted on the transmission portion of the first uplink resource. In some examples, in response to determining that not all bits of UCI are transmitted on the transmission portion of the first uplink resource, determining that the second uplink resource is not canceled, determining that the start of the first symbol of the second uplink resource is not earlier than the start time point of the cancellation portion of the first uplink resource, and determining that the first time interval is greater than or equal to the second time interval, the UE receives a UL CI indicating that the transmission on the first uplink resource is canceled, and determines that the second uplink resource is used to transmit UCI. The first time interval is defined as from the end of the last symbol of the UL CI to the beginning of the first symbol of the second uplink resource. The second time interval is defined as the length of time required for the UE to decode the UL CI and prepare to transmit UCI on the second uplink resource.

[0089] In some examples, in response to determining that all bits other than UCI are transmitted on the transmission portion of the first uplink resource, the second uplink resource is not canceled, and the start of the first symbol of the second uplink resource is no earlier than the start time point of the canceled portion of the first uplink resource, the second uplink resource is determined to be used to transmit UCI.

[0090] In some examples, the UCI includes different types of UCI. In response to determining that all bits that are not one of the different types of UCI are transmitted on the transmission portion of the first uplink resource, the second uplink resource is not canceled, the start of the first symbol of the second uplink resource is after the start time point of the canceled portion of the first uplink resource, and the first time interval is greater than or equal to the second time interval, and the UE receives a UL CI indicating that the transmission on the first uplink resource is canceled, it is determined that the second uplink resource is used to transmit one of the different types of UCI. The first time interval is defined as from the end of the last symbol of the UL CI to the beginning of the first symbol of the second uplink resource. The second time interval is defined as the length of time required for the UE to decode the UL CI and prepare to transmit one of the different types of UCI on the second uplink resource.

[0091] In some examples, in response to determining that all bits of one of the different types of UCI are not transmitted on the transmission portion of the first uplink resource, the second uplink resource is not canceled, and the start of the first symbol of the second uplink resource is no earlier than the start time point of the canceled portion of the first uplink resource, it is determined that the second uplink resource is used to transmit one of the different types of UCI.

[0092] In some examples, determining that the second uplink resource is used to transmit UCI includes: determining that all bits of a first type in UCI of different types are transmitted on a transmission portion of the first uplink resource, determining that all bits of a second type in UCI of different types are not transmitted on a transmission portion of the first uplink resource; and determining that the second uplink resource is used to transmit the second type of UCI. In some examples, method 900a also includes transmitting, by the UE, multiplexed UCI generated by multiplexing bits of the second type of UCI. The second uplink resource is initially configured to carry one of the second type of UCI in the transmission. The second uplink resource is determined based on the number of bits of the multiplexed UCI.

[0093] At 930a, the UE transmits UCI on the second uplink resource.

[0094] Fig. 9B is a flow chart illustrating a method 900b for resuming UCI transmission according to some embodiments of the present disclosure. Figures 1 to 9B In response to determining that the UCI transmitted on the first uplink resource conflicts with a transmission having a higher priority than the UCI transmitted on the first uplink resource, the base station determines to cancel the UCI transmitted on the first uplink resource.

[0095] At 910b, the base station indicates to the UE that UCI transmitted on at least a portion of the first uplink resources is canceled. In some examples, the base station indicates that UCI transmitted on at least the portion of the first uplink resources is canceled by transmitting to the wireless communication device one of an uplink grant indicating that the portion of the first uplink resources is released, a UL CI indicating that transmission on the first uplink resources is canceled, or a transmission power reduction command.

[0096] At 920b, the base station receives UCI from the UE on the second uplink resource.

[0097] Fig. 10A A block diagram of an example base station 1002 is shown in accordance with some embodiments of the present disclosure. Fig. 10B FIG. 1 is a block diagram of an example UE 1001 according to some embodiments of the present disclosure. Figures 1 to 10B , UE 1001 (or wireless communication device) is an example implementation of a UE described herein, and base station 1002 is an example implementation of a base station described herein.

[0098] Base station 1002 and UE 1001 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In an illustrative embodiment, base station 1002 and UE 1001 may be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as network system architecture 100 and slice deployment 200, as described above. For example, base station 1002 may be a base station (e.g., gno deb (GNB) etc.), a server, a node or any suitable computing device for implementing various network functions.

[0099] The base station 1002 includes a transceiver module 1010, an antenna 1012, a processor module 1014, a memory module 1016, and a network communication module 1018. The modules 1010, 1012, 1014, 1016, and 1018 are operably coupled and interconnected to each other via a data communication bus 1020. The UE 1001 includes a UE transceiver module 1030, a UE antenna 1032, a UE memory module 1034, and a UE processor module 1036. The modules 1030, 1032, 1034, and 1036 are operably coupled and interconnected to each other via a data communication bus 1040. The base station 1002 communicates with the UE 1001 or another base station via a communication channel, which may be any wireless channel or other medium suitable for data transmission as described herein.

[0100] As will be understood by those skilled in the art, the base station 1002 and the UE 1001 may also include Fig. 10A and Fig. 10BAny number of modules other than the modules shown in the embodiment disclosed herein. The various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. In order to illustrate the interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described in terms of their functions. Whether such functions are implemented as hardware, firmware, or software may depend on specific applications and design constraints imposed on the entire system. The embodiments described herein can be implemented in a manner suitable for each specific application, but any implementation decision should not be interpreted as limiting the scope of the present disclosure.

[0101] According to some embodiments, the UE transceiver 1030 includes a radio frequency (RF) transmitter and an RF receiver each including a circuit system coupled to an antenna 1032. A duplex switch (not shown) can couple the RF transmitter or receiver to the antenna in a time division duplex manner. Similarly, according to some embodiments, the transceiver 1010 includes an RF transmitter and an RF receiver each having a circuit system coupled to an antenna 1012 or an antenna of another base station. Alternatively, the duplex switch can couple the RF transmitter or receiver to the antenna 1012 in a time division duplex manner. The operation of the two transceiver modules 1010 and 1030 can be coordinated in time so that the receiver circuit system is coupled to the antenna 1032 for receiving transmissions made through a wireless transmission link while the transmitter is coupled to the antenna 1012. In some embodiments, there is close time synchronization with a minimum guard time between changes in duplex direction.

[0102] UE transceiver 1030 and transceiver 1010 are configured to communicate via a wireless data communication link and cooperate with an appropriately configured RF antenna device 1012 / 1032 capable of supporting a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, UE transceiver 1010 and transceiver 1010 are configured to support industry standards such as Long Term Evolution (LET) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to specific standards and associated protocols in application. On the contrary, UE transceiver 1030 and base station transceiver 1010 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0103] Transceiver 1010 and a transceiver of another base station (such as but not limited to transceiver 1010) are configured to communicate via a wireless data communication link and cooperate with an appropriately configured RF antenna device capable of supporting a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, transceiver 1010 and a transceiver of another base station are configured to support industry standards such as LTE and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to specific standards and associated protocols in application. Instead, transceiver 1010 and a transceiver of another base station can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0104] According to various embodiments, the base station 1002 may be a base station, such as but not limited to an eNB, a service eNB, a target eNB, a femtocell or a microcell. The base station 1002 may be an RN, a conventional base station, a DeNB, a gNB or an IAB donor. In some embodiments, the UE 1001 may be embodied in various types of UEs, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, etc. The processor modules 1014 and 1036 may be implemented or implemented using a general-purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, a discrete gate or transistor logic, a discrete hardware component or any combination thereof designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.

[0105] In addition, the methods or algorithms disclosed herein may be implemented directly in hardware, in firmware, in software modules executed by processor modules 1014 and 1036, respectively, or any practical combination thereof. Memory modules 1016 and 1034 may be implemented as RAM memory, flash memory, ROM read-only memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 1016 and 1034 may be coupled to processor modules 1010 and 1030, respectively, so that processor modules 1010 and 1030 may read information from and write information to memory modules 1016 and 1034, respectively. Memory modules 1016 and 1034 may also be integrated into their respective processor modules 1010 and 1030. In some embodiments, memory modules 1016 and 1034 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 1010 and 1030, respectively. Memory modules 1016 and 1034 may also each include non-volatile memory for storing instructions to be executed by processor modules 1010 and 1030, respectively.

[0106] The network communication module 1018 generally represents the hardware, software, firmware, processing logic and / or other components of the base station 1002 that implement bidirectional communication between the transceiver 1010 and other network components and communication nodes that communicate with the base station 1002. For example, the network communication module 1018 can be configured to support Internet or WiMAX services. In deployment, but not limited to this, the network communication module 1018 provides an 802.3 Ethernet interface so that the transceiver 1010 can communicate with a conventional Ethernet-based computer network. In this way, the network communication module 1018 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). In some embodiments in which the base station 1002 is an IAB donor, the network communication module 1018 includes a fiber optic transmission connection configured to connect the base station 1002 to the core network. The terms "configured for," "configured to," and variations thereof, as used herein with respect to a specific operation or function, refer to devices, components, circuits, structures, machines, signals, etc. that are physically constructed, programmed, formatted, and / or arranged to perform a specific operation or function.

[0107] Although various embodiments of the present solution have been described above, it should be understood that they are presented only as examples rather than as limitations. Similarly, various figures may depict example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the example features and functions of the present solution. However, it will be understood by these people that the present solution is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. Additionally, as will be appreciated by those of ordinary skill in the art, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any one of the above-described illustrative embodiments.

[0108] It should also be understood that any reference to an element using designations such as "first," "second," etc. herein generally does not limit the number or order of these elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or instances of elements. Thus, a reference to a first element and a second element does not mean that only two elements can be used, or that the first element must precede the second element in some manner.

[0109] Additionally, it will be understood by those skilled in the art that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols (e.g., which may be referenced in the above description) may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0110] It will be further understood by those of ordinary skill in the art that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the various aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of programs or design codes in conjunction with instructions (which may be referred to herein as "software" or "software modules" for convenience), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above in their functional aspects as a whole. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the entire system. A skilled technician may implement the described functionality in various ways for each specific application, but such implementation decisions will not result in a departure from the scope of this disclosure.

[0111] In addition, it will be understood by those of ordinary skill in the art that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or performed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. The general-purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors and a digital signal processor core, or any other suitable configuration to perform the functions described herein.

[0112] If implemented in software, the function can be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and the communication media include any medium that can be enabled to transfer a computer program or code from one place to another. The storage medium can be any available medium that a computer can access. As an example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer.

[0113] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for the purpose of discussion, various modules are described as discrete modules; however, as is apparent to one of ordinary skill in the art, according to embodiments of the present solution, two or more modules may be combined to form a single module that performs the associated functions.

[0114] Additionally, in an embodiment of the present solution, a memory or other storage device and a communication component may be used. It should be understood that, for clarity, the above description has described an embodiment of the present solution with reference to different functional units and processors. However, it is apparent that any suitable functional distribution between different functional units, processing logic elements or domains may be used without departing from the present solution. For example, a function shown to be performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, reference to a specific functional unit is merely a reference to a suitable means for providing the described functionality, rather than indicating a strict logical or physical structure or organization.

[0115] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as set forth in the above claims.

Claims

1. A wireless communication method, comprising: Receiving, by the wireless communication device, a list of open loop power control parameter sets from a base station; The wireless communication device receives downlink control information DCI from the base station, wherein the DCI includes an open-loop power control parameter set indication OLI; Determining, by the wireless communication device, a default subset from the list of open-loop power control parameter sets; as well as The wireless communication device determines an open-loop power control parameter in the default subset according to the OLI.

2. The wireless communication method according to claim 1, further comprising: Power control is performed, by the wireless communication device, on transmissions scheduled by the DCI using the open loop power control parameters.

3. The wireless communication method according to claim 1 or 2, wherein: The open loop power control parameter set includes the received power expected by the base station.

4. The wireless communication method according to claim 3, wherein: The default subset determined by the wireless communication device is a first open loop power control parameter set from the list of open loop power control parameter sets.

5. The wireless communication method according to claim 1, wherein: The DCI does not include a sounding reference signal SRS resource indication SRI.

6. A wireless communication device, comprising a memory and at least one processor, wherein the at least one processor is configured to read a code from the memory and implement the following steps: receiving a list of open loop power control parameter sets from a base station; Receiving downlink control information DCI from the base station, the DCI including an open-loop power control parameter set indication OLI; determining a default subset from the list of open-loop power control parameter sets; as well as An open-loop power control parameter in the default subset is determined according to the OLI.

7. The wireless communications apparatus of claim 6, the at least one processor further configured to implement the step of performing power control on transmissions scheduled by the DCI using the open loop power control parameters.

8. The wireless communication device according to claim 6 or 7, wherein: The open loop power control parameter set includes the received power expected by the base station.

9. The wireless communication device according to claim 8, wherein: The default subset determined by the wireless communication device is a first open loop power control parameter set from the list of open loop power control parameter sets.

10. The wireless communication device according to claim 6, wherein: The DCI does not include a sounding reference signal SRS resource indication SRI.

11. A computer program product comprising computer readable program medium code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement the method of any one of claims 1-5.

Images