CN114868414A

CN114868414A - System and method for determining information indicating cancellation

Info

Publication number: CN114868414A
Application number: CN201980102985.XA
Authority: CN
Inventors: 刘星; 郝鹏; 肖凯; 韩祥辉
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2019-12-31
Filing date: 2019-12-31
Publication date: 2022-08-05
Also published as: WO2021093125A1

Abstract

Systems and methods for wireless communication are disclosed herein. In one embodiment, a base station configures a time domain granularity (G) indicated on a network side and determines a number of symbols (T) remaining in a first uplink resource used to indicate a cancellation of uplink transmissions on a second uplink resource. The number of actual time domain portions of the first uplink transmission resource is determined based on T and G.

Description

System and method for determining information indicating cancellation

Technical Field

The present disclosure relates to the field of telecommunications, and in particular to detecting information indicating preemption of transmission resources.

Background

The demand for fifth generation mobile communication technology (5G) is rapidly increasing. The development of providing enhanced mobile broadband, ultra-high reliability, ultra-low delay transmission, and large-scale connectivity in 5G systems is ongoing.

Disclosure of Invention

Example embodiments disclosed herein are directed to solving problems associated with one or more of the problems presented in the prior art, and providing additional features that will become apparent by reference to the following detailed description when taken in conjunction with the drawings. According to various embodiments, example systems, methods, apparatus, and computer program products are disclosed herein. It is to be understood, however, that these embodiments are presented by way of example, and not limitation, and it will be apparent to those of ordinary skill in the art upon reading this disclosure that various modifications may be made to the disclosed embodiments while remaining within the scope of the present disclosure.

In some embodiments, the base station configures the first uplink resource, the first uplink resource being defined using a configuration parameter, the configuration parameter comprising at least one of a time domain starting point of the first uplink resource, a time domain duration of the first uplink resource, or a frequency domain range of the first uplink resource. The base station transmits an indication to the wireless communication device that uplink transmissions on a second uplink resource within the first uplink resource are cancelled. The wireless communication device cancels the uplink transmission on the second uplink resource.

In some embodiments, the wireless communication device receives an indication from the base station that uplink transmissions on a second uplink resource within the first uplink resource are cancelled. The first uplink resource is defined using a configuration parameter that includes at least one of a time domain starting point of the first uplink resource, a time domain duration of the first uplink resource, or a frequency domain range of the first uplink resource. The wireless communication device cancels the uplink transmission on the second uplink resource.

In some embodiments, the wireless communication device receives a network-side indicated time domain granularity (G) from a base station and determines a number of symbols (T) remaining in the first uplink resource. The first uplink resource is used to indicate a cancellation of uplink transmission on the second uplink resource. The wireless communication device determines a number of time domain portions of the first uplink transmission resource based on T and G.

In some embodiments, the base station configures a time domain granularity (G) indicated by the network side and determines a number of symbols (T) remaining in the first uplink resource. The first uplink resource is used to indicate a cancellation of uplink transmissions on the second uplink resource. An actual number of time domain portions of the first uplink transmission resource is determined based on T and G.

The above and other aspects and embodiments thereof are described in more detail in the accompanying drawings, the description and the claims.

Drawings

Various exemplary 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 merely depict example embodiments of the present solution to facilitate the reader's understanding of the present solution. Accordingly, the drawings should not be taken to limit the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, the drawings are not necessarily drawn to scale.

Fig. 1 is a schematic diagram illustrating a preempted Physical Uplink Shared Channel (PUSCH) resource in accordance with some embodiments of the present disclosure;

fig. 2 is a schematic diagram illustrating a process for cancelling uplink transmissions, in accordance with some embodiments of the present disclosure.

Fig. 3 is a schematic diagram illustrating an example uplink resource region (RUR) in accordance with some embodiments of the present disclosure.

Fig. 4 is a schematic diagram illustrating an example of a Reference Block (RB) distribution according to some embodiments of the present disclosure.

Fig. 5 is a schematic diagram illustrating an example of RB distribution and frequency domain reference points, according to some embodiments of the present disclosure.

Fig. 6 is a schematic diagram illustrating a method for indicating preemption of uplink transmission resources within an RUR, in accordance with some embodiments of the present disclosure.

Fig. 7A is a schematic diagram illustrating a method for indicating preemption of uplink transmission resources within an RUR in accordance with some embodiments of the present disclosure.

Fig. 7B is a schematic diagram illustrating a method for indicating preemption of uplink transmission resources within an RUR, in accordance with some embodiments of the present disclosure.

Fig. 8A is a schematic diagram illustrating a method for indicating preemption of uplink transmission resources within an RUR, in accordance with some embodiments of the present disclosure.

Fig. 8B is a schematic diagram illustrating a method for indicating preemption of uplink transmission resources within an RUR, in accordance with some embodiments of the present disclosure.

Fig. 9A illustrates a block diagram of an example base station, in accordance with some embodiments of the present disclosure; and

fig. 9B illustrates a block diagram of an example UE in accordance with some embodiments of the present disclosure.

Detailed Description

Various example embodiments of the present solution are described below with reference to the drawings to enable one of ordinary skill in the art to make and use the present solution. It will be apparent to those of ordinary skill in the art upon reading this disclosure that various changes or modifications can be made to the examples described herein without departing from the scope of the present solution. Accordingly, the present solution is not limited to the example embodiments and applications described and illustrated herein. Moreover, the particular order or hierarchy of steps in the methods disclosed herein is merely exemplary. Based upon design preferences, the particular order or hierarchy of steps in the methods or processes disclosed may be rearranged while remaining within the scope of the present solution. Thus, those of ordinary skill in the art will appreciate that the methods and techniques disclosed herein present the various steps or acts in a sample order, and that the present solution is not limited to the specific order or hierarchy presented unless otherwise explicitly stated.

The development of 5G wireless communication systems aims to achieve higher data communication rates (e.g., in Gbps), a large number of communication links (e.g., 1M/Km) ² ) Ultra-low delay (e.g., less than 1ms), higher reliability, and higher energy efficiency (e.g., less than 1ms)E.g., at least 100 times more efficient than previous systems). To achieve these improvements, in a wireless communication system under the 5G standard, different types of services are configured with different priorities according to different requirements and tolerances for delay, reliability, energy efficiency, and the like. For example, different types of uplink traffic with different transmission delay reliability requirements, and different priority channels for the same traffic may be transmitted.

When different services having different priorities are transmitted in the same cell, in order to provide the transmission capability of the high priority service, the transmission resources of the low priority service may be preempted by the high priority service, and the transmission of the low priority service using these preempted transmission resources is cancelled. This mechanism avoids low priority traffic and high priority traffic colliding when transmitted using the same transmission resources. In some cases, a first traffic having one or more of a higher priority, higher reliability, or shorter transmission time may preempt transmission resources of a second traffic having one or more of a lower priority, lower reliability, or longer transmission time.

To minimize the performance impact, it is necessary to communicate preemption indication information to UEs whose transmission resources are preempted. The transmission resource to be preempted may be referred to as "cancelled transmission resource", and the preemption indication information may be referred to as "cancellation indication information".

Currently, with respect to downlink transmission resource preemption (e.g., downlink traffic cancellation), a base station (e.g., BS, gNB, eNB, etc.) uses Downlink Control Information (DCI) to indicate the preemption resources in Reference Downlink Resources (RDR). Specifically, the configured RDR is divided into 14 blocks by the base station, for example, using { M, N } - {14, 1} or {7, 2 }. The bitmap maps bits (indicating preemption status) onto blocks. A bitmap is used to indicate whether each block is preempted. M represents the number of partitions of the RDR in the time domain. N represents the number of partitions of the RDR in the frequency domain. When preemption occurs, the base station may send a downlink preemption indication (DL-PI) at a particular listening opportunity after the end of preempting downlink transmissions. DL PI is a kind of "after the fact" indication. The UE further completes reception of the downlink transmission. The UE listens to the DL-PI after receiving the downlink transmission to determine whether a previous downlink transmission is preempted, and processes the downlink data in response to determining that the downlink transmission has not been preempted.

With respect to uplink transmission resource preemption (e.g., uplink traffic cancellation), a similar indication, such as but not limited to an uplink cancellation indication (UL CI), may be defined for uplink time-frequency domain resources. In contrast to DL-PI, to prevent uplink transmission of the UE, the UE needs to be informed of preemption via UL CI prior to transmission of uplink traffic. Based on such an uplink cancellation indication, uplink transmissions of traffic with a relatively low priority can be cancelled (if not already transmitted) or stopped (at the time of transmission) accordingly, thereby avoiding performance degradation due to simultaneous transmission of both types of traffic using the same uplink transmission resource. Embodiments described herein relate to a way for a network side to indicate or signal uplink transmission resource preemption or uplink traffic cancellation.

Fig. 1 is a schematic diagram illustrating a process 100 for preempting PUSCH uplink transmission resources in accordance with some embodiments of the present disclosure. Referring to fig. 1, a process 100 involves a UE 102 and a base station 104 (e.g., a BS, a gNB, an eNB, etc.). The uplink transmission diagram 130 illustrates uplink activity of the UE 102. The downlink transmission diagram 120 illustrates the downlink activity of the base station 104.

Graphs

120 and 130 show time slots (represented by the horizontal axis) divided in the time domain. In some examples, a dimension or axis of each of

graphs

120 and 130 perpendicular to a time domain axis represents a frequency, such as, but not limited to, a bandwidth, an activated uplink bandwidth portion (BWP), and the like. The frequencies are not continuous in the

different graphs

120 and 130.

UE 102 transmits a Scheduling Request (SR)132 in the uplink to base station 104. The SR 132 requests an uplink transmission resource for uplink traffic, which is referred to as first uplink traffic, from the base station 104. Examples of the first uplink traffic include, but are not limited to, enhanced mobile broadband (eMBB) traffic. The base station 104 allocates a first uplink transmission resource (e.g., PUSCH 134) to the UE 102 via an uplink grant (UL grant) 122. Base station 104 sends a UL grant 122 in the downlink to UE 102 to inform UE 102 that UE 102 may use PUSCH 134 for transmitting the first uplink traffic.

After UE 102 transmits SR 132 to base station 104, and after base station 104 transmits UL grant 122 to UE 102, UE 102 transmits SR 112 to base station 104. The SR 132 requests an uplink transmission resource for uplink traffic called second uplink traffic from the base station 104. Examples of the second uplink traffic include, but are not limited to, ultra-reliable low latency communication (URLLC) traffic.

In view of the ultra-high reliability and ultra-low latency transmission requirements of the second uplink traffic (e.g., URLLC traffic) of the UE 106, the base station 104 allocates uplink transmission resources as early in time as possible. The base station 104 determines that a second uplink transmission resource (e.g., PUSCH 136) meeting the ultra-high reliability and ultra-low delay transmission requirements may have been allocated to the UE 102. That is, the base station 104 determines that at least a portion of the PUSCH 134 conflicts with (e.g., overlaps in time with) at least a portion of the PUSCH 136. In response to determining that the priority of the second uplink traffic (e.g., URLLC traffic) for UE 106 is higher than the priority of the first uplink traffic (e.g., eMBB traffic) for UE 102, base station 104 cancels transmission of the first uplink traffic on the previously allocated uplink transmission resource (e.g., PUSCH 134). UE 102 may cancel or continue transmission of the first uplink traffic in the remaining portion of PUSCH 134 (e.g., the portion of PUSCH 134 that follows PUSCH 136).

Various methods may be used to cancel the low priority uplink transmission. In one example, the base station 104 reschedules the UE 102 for a new uplink transmission resource (not shown) and then cancels the uplink transmission on the originally allocated uplink transmission resource (e.g., PUSCH 134). The base station 104 may retransmit an uplink grant (retransmission not shown) to the UE 102 to inform the UE 102 that the UE 102 may use the new PUSCH to transmit the first uplink traffic (e.g., transmission is rescheduled to another uplink transmission resource, PUSCH). A New Data Indicator (NDI) field of the new uplink grant is flipped, indicating that the new uplink grant corresponds to the first uplink traffic (e.g., eMBB traffic). In some examples, this approach may be used to reschedule and release the entire initially allocated uplink transmission resource (e.g., PUSCH 134) or a portion thereof. In addition, the entire Transport Block (TB) or a portion thereof may be transmitted using the new uplink transmission resource.

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

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

Cancellation of the first uplink traffic due to a collision with the high priority second uplink traffic described with reference to process 100 is an illustrative example of a scenario applicable to the present embodiment, and additional scenarios in which uplink traffic is cancelled may be caused by other suitable reasons and are equally applicable to the present embodiment. Examples of such additional scenarios include, but are not limited to, uplink traffic cancelled due to a collision with a frame structure configuration, uplink traffic cancelled due to a collision with other uplink transmissions of the same UE or a different UE, uplink traffic cancelled due to a power limitation of 102, and so forth.

In some embodiments, a PUSCH (e.g., PUSCH 134) is an example of an uplink transmission resource capable of carrying data for low priority traffic and high priority traffic. To facilitate one or more other types of uplink transmissions having higher priorities, a scheme similar to the scheme for cancelling the first uplink transmission on PUSCH 134 may be implemented that cancels one or more other types of uplink transmissions having lower priorities due to preemption, such as, but not limited to, those on Physical Uplink Control Channel (PUCCH), Sounding Reference Signal (SRS), Physical Random Access Channel (PRACH), and so on. While the second uplink traffic transmitted using PUSCH 136 is shown as an example of high priority uplink traffic that may result in cancellation of low priority uplink traffic, transmission of other types of high priority uplink traffic (e.g., uplink transmissions transmitted on PUCCH, SRS, PRACH, etc.) may also result in cancellation of low priority uplink traffic.

Fig. 2 is a schematic diagram of a process 200 for cancelling uplink transmissions, in accordance with some embodiments of the present disclosure. Referring to fig. 1 and 2, a process 200 involves a UE 102 and a base station 104. The uplink transmission diagram 230 illustrates uplink activity of the UE 102. The downlink transmission diagram 220 illustrates the downlink activity of the base station 104.

Graphs

220 and 230 show time slots (represented by the horizontal axis) divided in the time domain. In some examples, a dimension or axis of each of

graphs

220 and 230 perpendicular to a time domain axis represents frequency, such as, but not limited to, bandwidth, activated uplink BWP, and the like. The frequencies are not continuous in the

different graphs

220 and 230.

In some embodiments, the base station 104 may send the UL CI 201 to the UE 102 in the downlink. The UL CI 201 corresponds to cancellation of uplink transmissions in uplink transmission resources within a reference uplink time-frequency resource region, such as, but not limited to, the RUR 202. In particular, the UL CI 201 is used to indicate or otherwise identify cancellation of transmission of uplink traffic carried on uplink resources (e.g., PUSCH 134) within the RUR 202 corresponding to the UL CI 201.

In some embodiments, the RUR 202 may be divided into time-frequency resource sub-blocks. Each bit in the DCI corresponds to a time-frequency resource sub-block. A bit value as a first value (e.g., 1) indicates a resource for which the time-frequency resource sub-block corresponding to the bit is cancelled (e.g., uplink transmission on the time-frequency resource sub-block is cancelled). A bit value that is a second value (e.g., 0) indicates that the time-frequency resource sub-block corresponding to the bit is not a revoked resource (e.g., uplink transmission on the time-frequency resource sub-block is not revoked).

In this regard, fig. 3 is a schematic diagram illustrating an example RUR 300, according to some embodiments of the present disclosure. Referring to FIGS. 1-3, RUR 300 is an example of RUR 202. The RUR 300 is shown as a rectangle defined by a dashed line. The network side divides the entire RUR 300 into seven time domain portions and two frequency domain portions. Accordingly, the RUR 300 includes a total of 14 time-frequency resource sub-blocks. That is, the RUR 300 corresponds to a time domain granularity parameter of 7 (e.g., timegranulithforci ═ 7) and an indication overhead parameter of 14 (e.g., CI-PayloadSize ═ 14 bits). The time domain granularity parameter is used to indicate that the RUR 300 is divided into seven time domain portions in the time domain. The indication overhead is used to indicate that 14 bits are used to signal the cancelled resources in the RUR 300. Based on the time-domain granularity parameter and the indicated overhead parameter, it may be determined that each of the seven time-domain portions is further divided into two frequency-domain portions. The bit value in the DCI corresponding to its time-frequency resource sub-block and time-frequency resource sub-block is a first value (e.g., 1), indicating that transmission of the first uplink traffic carried on the PUSCH 134 in the corresponding time-frequency resource sub-block is cancelled.

Downlink symbols, as well as symbols configured to receive Synchronization Signal Blocks (SSBs), cannot be scheduled for uplink transmission. To avoid invalid indications, symbols configured as semi-static downlink symbols and indicated as SSBs or synchronization signal physical broadcast channel blocks (SS/PBCH blocks) need to be excluded from the RUR. That is, symbols within the RUR configured as semi-static downlink symbols and indicating SSB or SS/PBCH blocks are first removed from the range of the RUR 300. The RUR 300 may then be partitioned in the time domain (e.g., based on a time domain granularity parameter, timegranularity for ci) to determine a time domain portion. The time-frequency resource sub-blocks may be determined based on a time-domain granularity parameter and an indicated overhead parameter. These symbols may be configured as semi-static downlink symbols via an information element in the parameter tdd-UL-DL-configuration common.

Some embodiments of the present disclosure relate to configuring an RUR and indicating to cancel uplink transmission on an uplink transmission resource. As described above, in some embodiments, the network side (e.g., base station 104) indicates an RUR (e.g., RUR 202 or 300). The RUR corresponds to a UL CI (e.g., UL CI 201). The UL CI 201 indicates or otherwise identifies cancellation of uplink transmission of uplink traffic (e.g., first uplink traffic) carried on uplink resources (e.g., PUSCH 134) within the RUR corresponding to the UL CI 201. One or more UEs (e.g., UE 102) may receive UL CI 201. The one or more UEs may respectively determine whether uplink transmission within the RURs is cancelled based on the UL CI.

The time-frequency location configuration information (e.g., configuration parameters) of the RUR includes at least one of a time domain start of the RUR, a time domain duration of the RUR, and a frequency domain range of the RUR.

With respect to the time domain start of the RUR, the time interval T of the RUR after the detected end symbol of the UL CI _proc,2 To begin, e.g., the RUR is at a time interval T after the end symbol of the Physical Downlink Control Channel (PDCCH) control resource set (CORESET) carrying the UL CI _proc,2 And starting. That is, the first symbol, i.e., T, after the detected end symbol of the UL CI _proc,2 And is the starting symbol of the RUR. T is _proc,2 Corresponding to PUSCH processing capability 2. T is _proc,2 Depending on the subcarrier spacing (SCS). For example, for SCS of 15kHz, T _proc,2 Equal to 5 symbols at 15 kHz. For SCS of 30kHz, T _proc,2 Equal to 5.5 symbols at 30kHz, and so on.

In one scenario, different UEs (with different SCS) may detect the same UL CI and determine the time domain starting point of the RUR corresponding to the UL CI. In this scenario, different UEs need to use the same SCS to determine the time domain starting point of the RUR in order to agree on the same time domain starting point of the RUR. The SCS may be determined using one of various methods to ensure that different UEs detecting the same UL CI may determine the same time domain starting point for the RUR.

In the first method, the SCS (referred to as a reference SCS) used to determine the time domain starting point of the RUR is the lowest SCS in a list of SCS (e.g., SCS-specific carrierlist) in the uplink carrier frequency information. In some embodiments, the network side configures uplink carrier frequency information (such as, but not limited to, the information element frequencyinful) and transmits the uplink carrier frequency information in system information, such as, but not limited to, system information block 1(SIB 1). The uplink carrier frequency information includes a SCS list (e.g., SCS-specific carrierlist) of all SCS's used in the uplink carrier. The UE may configure the available RB distribution for each SCS within a carrier using the SCS list.

For each SCS in the SCS list of uplink carrier frequency information, the offset between the lowest available subcarrier of the SCS and point a (configured by the parameter offset tocarrier), and the number of RBs of the SCS (configured by the parameter carrierBandwidth) are configured or determined accordingly. Fig. 4 is a schematic diagram illustrating an example of an RB distribution 400 according to some embodiments of the present disclosure. Referring to fig. 1-4, the SCS list includes SCS at 30kHz and 15 kHz. RB distribution 400 includes RB distributions 410 and 420. RB distribution 410 is the distribution of SCS available RBs at 30 kHz. RB distribution 420 is a distribution of SCS available RBs of 15 kHz. Point a refers to the common starting point of the common rb (crb) of all SCS's of the carrier. That is, subcarrier 0 of CRB0 of all SCS within the carrier is aligned with point a. For each SCS of 30kHz or 15kHz in the list of SCS's, an offset (e.g., offsets 415 or 425, respectively) is configured between the lowest available subcarrier of each SCS of 30kHz or 15kHz and point a. Further, for each SCS of 30kHz or 15kHz, the number of RBs of the SCS is configured (e.g., 30kHz RB or 15kHz RB, respectively).

In some examples, in response to the UE detecting the UL CI, the UE may determine T by determining based on the reference SCS _proc,2 To determine the time domain starting point of the RUR corresponding to the UL CI, where the reference SCS is the lowest SCS in a list of SCS (e.g., SCS-specific carrierlist) in the UL carrier frequency information. As shown in fig. 4, the lowest SCS in the SCS list is a 15kHz SCS, and thus, the reference SCS is a 15kHz SCS.

In a second approach, the reference SCS is the largest SCS in a list of SCS's in the uplink carrier frequency information (e.g., SCS-specific carrierlist). As shown in fig. 4, the largest SCS in the list of SCS is a 30kHz SCS, and thus, the reference SCS is a 30kHz SCS.

In a third method, the reference SCS is the SCS closest to the UL CI in the list of SCS. In the example where the SCS list of uplink carrier frequency information includes SCS of 15kHz and 60kHz, and the SCS of UL CI 201 is 30kHz, the SCS of 15kHz is determined to be the reference SCS given that 15kHz is closer to 30 kHz.

In the fourth method, the reference SCS is the lower SCS of the SCS of UL CI 201 and the lowest SCS of the SCS's in the list of SCS's of uplink carrier frequency information. In the example where the SCS of UL CI 201 is 15kHz and the SCS in the list of SCS is 30kHz and 60kHz, the reference SCS is the SCS of UL CI 201, which is 15 kHz.

With respect to the time domain duration of the RUR, the base station may configure the number of symbols corresponding to the time domain duration of the RUR via Radio Resource Control (RRC) layer parameters (e.g., those beginning with "+ -"). Similar to the time domain starting point, the time domain duration of the RUR depends on the SCS. Different UEs need to use the same SCS to determine the time domain duration of the RUR in order to agree on the same time domain duration of the RUR. The reference SCS may be determined using one of various methods applicable to the SCS that determines the time domain starting point to ensure that different UEs detecting the same UL CI may determine the same RUR time domain duration.

That is, in the first method, the reference SCS for determining the time domain duration of the RUR is the lowest SCS in a list of SCS (e.g., SCS-specific carrierlist) in the uplink carrier frequency information. In a second approach, the reference SCS used to determine the time-domain duration of the RUR is the largest SCS in a list of SCS (e.g., SCS-specific carrierlist) in the uplink carrier frequency information. In a third method, the reference SCS used to determine the time domain duration of the RUR is the SCS closest to the UL CI in the list of SCS. In a fourth method, the reference SCS is the lower one of the SCS of the UL CI and the lowest SCS in the SCS list of uplink carrier frequency information.

With respect to the frequency domain range of the RUR, the network side (including the base station 104) configures the frequency domain starting point of the RUR and the number of RBs included in the frequency domain range via RRC signaling (e.g., such as, but not limited to, a parameter frequency registration for ci). For example, the frequency domain starting point and the number of RBs may be defined as independent parameters in the RRC message and may be indicated separately. In other examples, the frequency domain starting point and the number of RBs may be defined as the same parameter in the RRC message and may be indicated jointly. That is, the same parameter may indicate a combination of a frequency domain start point and the number of RBs of the RUR.

The frequency domain starting point may be defined as a frequency domain offset from a frequency domain reference point. The frequency domain reference point may be defined as the lowest available subcarrier with reference to the SCS. The number of RBs may also be determined based on a reference SCS. The reference SCS may be determined using one of various methods applicable to SCS for determining time domain starting point and time domain duration to ensure that different UEs detecting the same UL CI may determine the same frequency domain starting point and number of RBs of the RUR.

That is, in the first method, the reference SCS for determining the frequency domain starting point (e.g., frequency domain reference point) and the number of RBs of the RUR is the lowest SCS among a list of SCS (e.g., SCS-specific carrierlist) in the uplink carrier frequency information. In a second method, the reference SCS used to determine the frequency domain starting point (e.g., frequency domain reference point) and the number of RBs of the RUR is the largest SCS in a list of SCS (e.g., SCS-specific carrier list) in the uplink carrier frequency information. In a third method, the reference SCS for determining the frequency domain starting point (e.g., frequency domain reference point) and the number of RBs of the RUR is the SCS of the SCS closest to the UL CI in the SCS list. In a fourth method, the reference SCS is the lowest SCS of the UL CI and is the lowest SCS in the SCS list of uplink carrier frequency information.

As described above, the time-frequency location configuration information (e.g., configuration parameters) of the RUR may be configured by the base station and determined by the UE based on the reference SCS according to the method.

In some embodiments, the reference SCS may be determined based on whether the SCS list in the uplink carrier frequency information includes SCS of the UL CI. For example, in response to determining that the list of SCS (e.g., SCS-specific carrierlist) in the uplink carrier frequency information includes SCS of the UL CI, the reference SCS is set to the SCS of the UL CI. On the other hand, in response to determining that the SCS list in the uplink carrier frequency information does not include SCS of the UL CI, the reference SCS is determined using one of the various methods described. That is, in the first method, the reference SCS is the lowest SCS in the SCS list in the uplink carrier frequency information. In the second method, the reference SCS is the largest SCS in the list of SCS's in the uplink carrier frequency information. In a third method, the reference SCS is the SCS of the SCS closest to the UL CI in the list of SCS. In a fourth method, the reference SCS is the lower of the SCS of the UL CI and the lowest SCS in the SCS list of uplink carrier frequency information.

In some embodiments, the reference SCS is determined to be the SCS of the UL CI. To configure the SCS of the UL CI, the base station can only configure one SCS in a SCS list (SCS-specific carrierlist) in the uplink carrier frequency information as the SCS of the UL CI. That is, the UE expects SCS of UL CI in SCS list. Therefore, the UE may select the SCS of the UL CI from the SCS list as the reference SCS.

As described above, the frequency domain start point of the frequency domain range of the RUR may be defined as the frequency domain offset of the frequency domain reference point, which is defined as the lowest available subcarrier with reference to the SCS. The number of RBs may be determined based on the reference SCS. In some embodiments, the SCS of the UL CI is determined to be a reference SCS. In response to determining that the SCS list of uplink carrier frequency information (e.g., SCS-specific carrierlist) does not include SCS of UL CI, a frequency domain reference point is determined based on uplink carrier point a and downlink carrier frequency information.

In some examples, the location of the lowest available subcarrier of the SCS (e.g., 15kHz) of the UL CI is indicated using the parameter offsetttocarrier in the SCS list in the downlink carrier frequency information. Fig. 5 is a schematic diagram illustrating an example of RB distribution 510 and frequency domain reference points 520, according to some embodiments of the present disclosure. Referring to fig. 1-5, RB distribution 510 is the distribution of available RBs for 15kHz SCS for UL CI. The RB distribution 510, including the lowest available subcarrier of UL CI at 15kHz, is indicated by the parameter offsetttocarrier in the SCS list in the downlink carrier frequency information. Downlink carrier point a refers to the common starting point of the common rbs (crb) of all SCS of the 15kHz downlink carrier. That is, subcarrier 0 of CRB0 of all SCS within the downlink carrier is aligned with point a. The offset 515 between the lowest available subcarrier at SCS (e.g., 15kHz) of the UL CI and point a is configured. Further, the RB number of 15kHz RBs for UL CI is configured and indicated using the parameter offset tocarrier in the SCS list in the downlink carrier frequency information. In some embodiments, the frequency domain reference point 520 for the uplink is point a of the uplink carrier plus (in frequency) an offset 515. Accordingly, the frequency domain range of the RUR is defined based on the frequency domain reference point 520 and the frequency domain offset 515 shown in fig. 5. The frequency domain offset 515 and the number of RBs are indicated by frequency region for ci.

Fig. 6 is a schematic diagram illustrating a method 600 for indicating preemption of uplink transmission resources within an RUR 620 in accordance with some embodiments of the present disclosure. Referring to fig. 1-6, a base station may configure a slot format 601 via suitable RRC signaling (e.g., TDD-UL-DL-ConfigCommon). As shown, a portion of the slot format 201 includes at least eight slots 611-618. The dimension or axis perpendicular to the time domain axis in fig. 6 represents frequency, such as but not limited to bandwidth, active BWP, and the like. The resource type of the time slots 611-618 is configured as "DFFFDFFF", where "D" denotes the

downlink time slots

611 and 615 and "F" denotes the flexible time slots 612-614 and 616-618.

The base station configures the RUR 620 with configuration parameters including a time domain duration of 56 symbols, a time domain granularity (G) of 28 symbols, and an indicated overhead N of 112 bits. For example, the time domain duration may be configured by the parameter timediviationforci. The temporal granularity may be configured by the parameter timeGranularityforCI. The indication overhead N may be configured by the parameter CI-PayloadSize.

The RUR 620 contains four slots, including three flexible slots and one semi-static downlink slot. The semi-static downlink slot includes 14 symbols. Further, RUR 620 comprises six SSB 633-638. Each of

SSBs

631 and 638 occupy 4 consecutive symbols. Assuming that all six SSBs 633-. After subtracting the semi-static downlink symbols (14 symbols) and SSB symbols (24 symbols) from the time domain duration (56 symbols) configured in timescheduling for CI, the remaining 18 symbols (referred to as T) are symbols that may correspond to UL CI.

T may be divided according to configured G. The first x time domain portions comprise

A symbol, wherein:

the rest of

A time domain part comprising

A symbol.

In response to determining that the number of remaining symbols T in the RUR 620 after the downlink symbols and SSB symbols are removed from the time domain duration is less than the configured number of time domain partitions, the first 10 time domain portions contain 0 symbols and the last 18 time domain portions will contain 1 symbol.

Furthermore, whether or not the divided time domain portion actually contains any symbol, it indicates that the overhead N ═ 112 bits are divided into 28 time domain portions on average. Each time domain portion occupies 4 bits. That is, the frequency domain indicates a granularity of 1/4. Thus, the first 10 time domain portions still occupy 40 bits, although the first 10 time domain portions do not actually correspond to any uplink transmission resource. Therefore, 40 bits are wasted and the indication efficiency is low.

To improve efficiency, the time domain portion of the RUR 620 may be divided based on the smaller of G and T. For example, the parameter M may be defined as:

M＝min{G,T} (2)。

where the RUR 620 has been actually divided into M time domain portions in the time domain. The first x time domain portions comprise

A symbolWherein:

the rest of

A time domain part comprising

A symbol.

The RUR 620 is effectively divided into 18 time domain portions, each time domain portion containing 1 symbol. The frequency domain indication granularity for each time domain portion is:

in this way, of the 112-bit indication overhead N, only 4 bits (e.g., 112-6 · 18 ═ 4) are invalid. Accordingly, each time domain portion of the RUR 620 may be divided into the same number of frequency domain portions. In an example where the indication overhead N is not an integer multiple of the actual number of time domain portions, some bits may be wasted.

In some embodiments, different time domain portions are allocated different numbers of bits to efficiently utilize the indicator bits. The total indication bits may be allocated to each time domain portion according to one of the allocation methods.

In a first allocation method, the M time domain portions are preceded by

Time domain portion allocation

A bit. For the rest

A time domain part, allocation

And (4) a bit. Correspondingly, front

The time domain part is divided into

A frequency domain part and remains

The time domain part is divided into

A frequency domain portion.

In a second allocation method, the M time domain portions are preceded by

Time domain portion allocation

And (4) a bit. For the rest

A time domain part, allocation

And (4) a bit. Correspondingly, front

The time domain part is divided into

A frequency domain part and remains

The time domain part is divided into

A frequency domain portion.

As described above, the base station configures the RUR 620 with configuration parameters including a time domain duration of 56 symbols, a time domain granularity (G) of 28 symbols, and an indication overhead N of 112 bits. After subtracting the semi-static downlink symbols (14 symbols) and SSB symbols (24 symbols) from the time domain duration (56 symbols) configured in timescheduling for CI, the remaining 18 symbols (referred to as T) are symbols that may correspond to UL CI.

In response to determining T < G, the base station and the UE select a time domain granularity value from the time domain granularity set as an actual time domain granularity G'. Of the time domain granularity values of the set of time domain granularities that are less than T, the selected time domain granularity value is closest to G (as indicated by timeGranularityforCI).

In examples where the timegranulithforci value set includes {1,2,4,7,14,28}, and G is configured to be 28 (e.g., G ═ 28), T is less than G (e.g., T ═ 28)<G) In that respect In this example, the actual time-domain granularity G' is selected to be 14 given that 14 is closest to G and less than T. Thus G' is 14. The RUR 620 may be effectively divided into 14 time domain portions, the first 10 of which (e.g.,

) The time domain portion contains 1 (e.g.,

) The symbol, the remaining 4 (e.g.,

) The time domain portion contains 2 (e.g.,

) And (4) a symbol. The frequency domain indicates a granularity of

Thus, no bits are wasted.

In response to determining T ≧ G, the base station and the UE select G forIs the actual time domain granularity G'. Front side

A time domain part comprising

One symbol, the rest

A time domain part comprising

A symbol.

In some embodiments, there is no restriction on the configured temporal granularity parameter (e.g., configured by timeGranularityforCI). In examples where the RUR includes symbols occupied by SSBs, the number of symbols T remaining in the RUR may be less than the configured time domain granularity parameter. Some time domain portions do not contain any symbols if the time domain portions are divided according to a configured time domain granularity. To avoid this, in some embodiments, the value of the configured time-domain granularity parameter may be limited during configuration. For example, the configured time domain granularity parameter G cannot be larger than the remaining number of symbols T. In other words, when the network side configures the time domain granularity parameter G, the number of symbols T remaining in the RUR is considered to ensure that the configured time domain granularity parameter G is less than or equal to the number of symbols T remaining. In this case, the configured temporal granularity parameter G may be used as the actual temporal granularity G'.

Fig. 7A is a schematic diagram illustrating a method 700a for indicating preemption of uplink transmission resources within an RUR, in accordance with some embodiments. Referring to fig. 1-5 and 7A, a method 700a is performed by a base station.

At 710, the base station configures a first uplink resource. The first uplink resource is defined using a configuration parameter that includes at least one of a time domain starting point of the first uplink resource, a time domain duration of the first uplink resource, or a frequency domain range of the first uplink resource. The first uplink resource is an RUR. The second uplink resource is an uplink resource (e.g., PUSCH 134) within the RUR, where transmission of uplink traffic carried on the uplink resource is to be cancelled.

A configuration parameter for the first uplink resource is determined based on the reference SCS. In some embodiments, the reference SCS is a lowest SCS of a plurality of SCS's in a list of SCS's in the uplink carrier frequency information. In some embodiments, the reference SCS is a largest SCS of a plurality of SCS's in a list of SCS's in the uplink carrier frequency information. In some embodiments, the reference SCS is the SCS of the plurality of SCS in the list of SCS in the uplink carrier frequency information that is closest to the indicated SCS. In some embodiments, the reference SCS is a lower one of the lowest SCS of the plurality of SCS in the list of SCS's in the indicated SCS and uplink carrier frequency information.

In some embodiments, the reference SCS is an indicated SCS in response to determining that the list of SCS's in the uplink carrier frequency information includes the indicated SCS. In some embodiments, in response to determining that the list of SCS's in the uplink carrier frequency information does not include an indicated SCS, the reference SCS is one of: a lowest SCS of the plurality of SCSs in the SCS list, a largest SCS of the plurality of SCSs in the SCS list, or a closest indicated SCS of the plurality of SCSs in the SCS list.

In some embodiments, the reference SCS is an indicated SCS, and the indicated SCS is one of a plurality of SCS in a list of SCS in the uplink carrier frequency information.

In some embodiments, the frequency domain range of the first uplink resource is defined by a frequency domain starting point and a number of RBs. The frequency domain starting point is determined based on a frequency domain offset from a frequency domain reference point. The frequency domain reference point is the lowest available subcarrier of the reference SCS. The number of RBs is determined according to the reference SCS. In response to determining that the SCS list of uplink carrier frequency information does not include the indicated SCS, a frequency domain reference point is determined based on the uplink carrier frequency point a and the downlink carrier frequency information.

At 720, the base station transmits an indication to the UE that uplink transmission on a second uplink resource within the first uplink resource is cancelled. The indication is UL CI. The UE cancels the uplink transmission on the second uplink resource.

Fig. 7B is a schematic diagram illustrating a method 700B for indicating preemption of uplink transmission resources within an RUR, in accordance with some embodiments. Referring to fig. 1-5, 7A, and 7B, method 700B is performed by a UE.

At 730, the UE receives an indication from the base station that uplink transmissions on a second uplink resource within the first uplink resource are cancelled. The first uplink resource is defined using a configuration parameter that includes at least one of a time domain starting point of the first uplink resource, a time domain duration of the first uplink resource, or a frequency domain range of the first uplink resource. At 740, the UE cancels the uplink transmission on the second uplink resource.

Fig. 8A is a schematic diagram illustrating a method 800a for indicating preemption of uplink transmission resources within an RUR, in accordance with some embodiments. Referring to fig. 1-3, 6 and 8A, a method 800a is performed by a UE.

At 810, the UE receives a network-side indicated time domain granularity (G) from the base station. At 820, the UE determines a number of symbols (T) remaining in the first uplink resource. A first uplink resource used to indicate a cancellation of uplink transmission on a second uplink resource. The first uplink resource is an RUR. The second uplink resource is an uplink resource (e.g., PUSCH 134) within the RUR, where transmission of uplink traffic carried on the uplink resource is to be cancelled. At 830, the UE determines a number of time domain portions of the first uplink transmission resource based on T and G.

In some embodiments, M is defined as M ═ min { G, T }. The first uplink resource is actually divided into M time domain portions. The first x time domain portions comprise

A symbol in which

Remainder of

A time domain part comprising

A symbol.

In some embodiments, in response to determining that T is less than G, a time domain granularity value is selected from the set of time domain granularities as the actual time domain granularity G'. The actual time-domain granularity G' selected is less than T and closest to G. First uplink resource

A time domain part including

A symbol. Remainder of first uplink resource

A time domain part comprising

A symbol.

In some embodiments, in response to determining that T is greater than or equal to G, G is determined to be the actual time-domain granularity. First uplink resource

A time domain part including

A symbol. Remainder of first uplink resource

A time domain part comprising

A symbol.

In some embodiments, G is less than or equal to T. G is determined based on T.

Fig. 8B is a schematic diagram illustrating a method 800B for indicating preemption of uplink transmission resources within an RUR, in accordance with some embodiments. Referring to fig. 1-3, 6, 8A, and 8B, method 800B is performed by a base station.

At 840, the base station configures the time domain granularity (G) indicated by the network side. At 850, the base station determines a number of symbols (T) remaining in the first uplink resource. A first uplink resource used to indicate a cancellation of uplink transmission on a second uplink resource. An actual number of time domain portions of the first uplink transmission resource is determined based on T and G.

Fig. 9A illustrates a block diagram of an example base station 902, in accordance with some embodiments of the present disclosure. Fig. 9B illustrates a block diagram of an example UE 901, in accordance with some embodiments of the present disclosure. Referring to fig. 1-9B, a UE 901 (e.g., a wireless communication device, terminal, mobile device, mobile user, etc.) is an example embodiment of a UE described herein, and a base station 902 is an example embodiment of a base station described herein.

Base station 902 and UE 901 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, base station 902 and UE 901 can be employed to transmit (e.g., transmit and receive) data symbols in a wireless communication environment, as described supra. For example, base station 902 can be a base station (e.g., a gNB, eNB, etc.), a server, a node, or any suitable computing device utilized to implement various network functions.

Base station 902 includes a transceiver module 910, an antenna 912, a processor module 914, a memory module 916, and a network communication module 918. The

modules

910, 912, 914, 916, and 918 are operatively coupled and interconnected with one another via a data communication bus 920. The UE 901 includes a UE transceiver module 930, a UE antenna 932, a UE memory module 934, and a UE processor module 936. The

modules

930, 932, 934 and 936 are operatively coupled and interconnected with each other via a data communication bus 940. The base station 902 communicates with the UE 901 or another base station via a communication channel, which may be any wireless channel or other medium suitable for data transmission as described herein.

As understood by those of ordinary skill in the art, the base station 902 and UE 901 may also include any number of modules in addition to those shown in fig. 9A and 9B. The various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer readable software, firmware, or any practical combination thereof. To illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software depends upon the particular application and design constraints imposed on the overall system. The examples described herein may be implemented in an appropriate manner for each particular application, but any implementation decisions should not be interpreted as limiting the scope of the present disclosure.

According to some embodiments, UE transceiver 930 includes a Radio Frequency (RF) transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 932. A duplex switch (not shown) may alternately couple the RF transmitter or receiver to the antenna in a time-duplex manner. Similarly, in accordance with some embodiments, transceiver 910 includes an RF transmitter and an RF receiver, each of which has circuitry coupled to antenna 912 or an antenna of another base station. The duplex switch can alternately couple the RF transmitter or receiver to the antenna 912 in a time-duplex manner. The operation of the two

transceiver modules

910 and 930 may be coordinated in time such that the receiver circuit is coupled to the antenna 932 at the same time that the transmitter is coupled to the antenna 912 for receiving transmissions over the wireless transmission link. In some embodiments, there is tight time synchronization with minimal guard time between changes in duplex direction.

UE transceiver 930 and transceiver 910 are configured to communicate via a wireless data communication link and cooperate with a suitably configured RF antenna arrangement 912/932 that may support particular wireless communication protocols and modulation schemes. In some demonstrative embodiments, UE transceiver 910 and transceiver 910 are configured to support industry standards, such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to the application of a particular standard and related protocol. Rather, UE transceiver 930 and base station transceiver 910 may be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

Transceiver 910 and a transceiver of another base station, such as but not limited to transceiver 910, are configured to communicate via a wireless data communication link and cooperate with a suitably configured RF antenna arrangement that may support a particular wireless communication protocol and modulation scheme. In some demonstrative embodiments, transceiver 910 and the transceiver of another base station are configured to support industry standards, such as the LTE and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to the application of a particular standard and related protocol. Rather, transceiver 910 and the transceiver of another base station may be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

According to various embodiments, base station 902 may be a base station such as, but not limited to, an eNB, a serving eNB, a target eNB, a femto station, or a pico station. Base station 902 can be an RN, regular, DeNB, or gNB. In some embodiments, the UE 901 may be embodied in various types of user equipment, such as a mobile phone, a smartphone, a Personal Digital Assistant (PDA), a tablet, a laptop, a wearable computing device, and so forth. The

processor modules

914 and 936 may be implemented or realized with 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, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. In this manner, a processor may be implemented as a microprocessor, controller, microcontroller, state machine, or the like. A processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

Further, the methods or algorithms disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by the

processor modules

914 and 936, respectively, or in any practical combination thereof.

Memory modules

916 and 934 can be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, the

memory modules

916 and 934 may be coupled to the

processor modules

910 and 930, respectively, such that the

processor modules

910 and 930 may read information from and write information to the

memory modules

916 and 934, respectively. The

memory modules

916 and 934 may also be integrated into the

respective processor modules

910 and 930. In some embodiments, the

memory modules

916 and 934 may each include a cache for storing temporary variables or other intermediate information during execution of instructions to be executed by the

processor modules

910 and 930, respectively. The

memory modules

916 and 934 may also each include non-volatile memory for storing instructions to be executed by the

processor modules

910 and 930, respectively.

Network communication module 918 generally represents the hardware, software, firmware, processing logic, and/or other components of base station 902 that enable bi-directional communication between transceiver 910 and other network components and communication nodes in communication with base station 902. For example, the network communication module 918 may be configured to support internet or WiMAX traffic. In deployment, without limitation, the network communication module 918 provides an 802.3 ethernet interface so that the transceiver 910 can communicate with an ethernet-based conventional computer network. In this manner, the network communication module 918 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). In some embodiments, the network communication module 918 comprises a fiber optic transmission connection configured to connect the base station 902 to a core network. The terms "configured to," "configured to," and the conjunctions thereof, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted, and/or arranged to perform the specified operation or function.

While various embodiments of the present solution have been described above, it should be understood that they have been presented by way of example only, and not limitation. Similarly, the various figures may depict example architectures or configurations provided to enable one of ordinary skill in the art to understand example features and functionality of the present solution. However, those skilled in the art will appreciate that the solutions are not limited to the example architectures or configurations shown, but may be implemented using a variety of alternative architectures and configurations. In addition, as one of ordinary skill in the art will appreciate, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.

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

In addition, those of ordinary skill in the art would understand 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 that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of ordinary skill would further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two), firmware, various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as "software" or a "software module"), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or combinations of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

Furthermore, those of ordinary skill in the art will appreciate that the various illustrative logical blocks, modules, devices, components, and circuits described herein may be implemented or performed with Integrated Circuits (ICs) that 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 further include antennas and/or transceivers to communicate with various components within the network or within the device. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration, to perform the functions described herein.

If implemented in software, the functions may be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein may be embodied in software stored on a computer readable medium. Computer-readable media includes both computer storage media and communication media including any medium that enables a computer program or code to be transferred from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. Moreover, for purposes of discussion, the various modules are described as discrete modules; however, it is obvious to a person skilled in the art that two or more modules may be combined to form a single module performing the relevant functions according to embodiments of the present solution.

Further, in embodiments of the present solution, memory or other storage and communication components may be employed. It should be appreciated that the above description for clarity has described embodiments of the present solution with reference to different functional units and processors. It will be apparent, however, that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without affecting the present solution. For example, functionality illustrated to be performed by different processing logic elements or controllers may be performed by the same processing logic elements or controllers. Thus, references to specific functional units are only to references to suitable means for providing the described functionality rather than indicative of a strict logical or physical structure or organization.

Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the disclosure. Thus, the present 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 recited in the claims.

Claims

1. A method of wireless communication, comprising:

receiving, by the wireless communication device, a time domain granularity (G) indicated by the network side from the base station, an

Determining, by the wireless communication device, a number of symbols (T) remaining in a first uplink resource, the first uplink resource being used to indicate cancellation of uplink transmission on a second uplink resource; and

determining, by the wireless communication device, a number of time domain portions of the first uplink transmission resource based on T and G.

2. The method of claim 1, wherein:

m is defined as M ═ min { G, T };

the first uplink resource is actually divided into M time domain portions;

the first x time domain portions comprise

A symbol;

and

the rest of

A time domain part comprising

A symbol.

3. The method of claim 1, wherein:

in response to determining that T is less than G, selecting a time domain granularity value from the set of time domain granularities as an actual time domain granularity G ', the selected actual time domain granularity G' being less than T and closest to G;

a front of the first uplink resource

A time domain part comprising

A symbol; and

remaining of the first uplink resource

A time domain part comprising

A symbol.

4. The method of claim 1, wherein:

in response to determining that T is greater than or equal to G, G is determined to be the actual time-domain granularity;

a front of the first uplink resource

A time domain part comprising

A symbol; and

remaining of the first uplink resource

A time domain part comprising

A symbol.

5. The method of claim 1, wherein:

g is less than or equal to T; and

g is determined based on T.

6. A wireless communication apparatus comprising at least one processor and a memory, wherein the at least one processor is configured to read code from the memory and implement the method of claim 1.

7. 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 claim 1.

8. A method of wireless communication, comprising:

configuring, by a base station, a time domain granularity (G) indicated by a network side;

determining, by the base station, a number of symbols (T) remaining in a first uplink resource used to indicate cancellation of uplink transmission on a second uplink resource, wherein a number of actual time domain portions of the first uplink transmission resource is determined based on T and G.

9. The method of claim 8, wherein:

m is defined as M ═ min { G, T };

the first uplink resource is actually divided into M time domain portions;

the first x time domain portions comprise

A symbol;

and

the rest of

A time domain part comprising

A symbol.

10. The method of claim 8, wherein:

t is smaller than G, a time domain granularity value is selected from the time domain granularity set to serve as an actual time domain granularity G ', and the selected actual time domain granularity G' is smaller than T and is closest to G;

a front of the first uplink resource

A time domain part including

A symbol; and

remaining of the first uplink resource

A time domain part comprising

A symbol.

11. The method of claim 8, wherein:

t is greater than or equal to G, which is determined to be the actual time domain granularity;

a front of the first uplink resource

A time domain part including

A symbol; and

remaining of the first uplink resource

A time domain part comprising

A symbol.

12. The method of claim 8, wherein:

g is less than or equal to T; and

g is determined based on T.

13. A wireless communication apparatus comprising at least one processor and a memory, wherein the at least one processor is configured to read code from the memory and implement the method of claim 8.

14. 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 claim 8.