System and method for determining information indicative of cancellation

Abstract

The present invention discloses a system and method for wireless communication. In one embodiment, a base station configures a time domain granularity (G) indicated by a network side and determines the number of symbols (T) remaining in a first uplink resource, and the first uplink resource is used to indicate the cancellation of an uplink transmission on a second uplink resource. Based on T and G, the actual number of time domain portions of the first uplink transmission resource is determined.

Description

Technical Field

[0001] The present disclosure relates to the field of telecommunications, and in particular to detecting information indicative of preemption of transmission resources. Background Art

[0002] The demand for 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 massive connectivity in 5G systems. Summary of the invention

[0003] The example embodiments disclosed herein are intended to solve problems associated with one or more of the problems presented in the prior art, as well as to provide additional features that will become apparent by reference to the following detailed description when taken 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 a person of ordinary skill in the art who reads this disclosure that various modifications may be made to the disclosed embodiments while remaining within the scope of this disclosure.

[0004] In some embodiments, the base station configures a first uplink resource, the first uplink resource is defined using a configuration parameter, the configuration parameter includes at least one of a time domain start 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 to the wireless communication device an indication that an uplink transmission on a second uplink resource within the first uplink resource is canceled. The wireless communication device cancels the uplink transmission on the second uplink resource.

[0005] In some embodiments, the wireless communication device receives an indication from a base station that an uplink transmission on a second uplink resource within a first uplink resource is canceled. The first uplink resource is defined using a configuration parameter including at least one of a time domain start 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.

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

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

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

[0009] Various example embodiments of the present solution are described in detail below with reference to the following diagrams or drawings. The drawings are provided for illustrative purposes only and only depict example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered to limit 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.

[0010] Figure 1 is a schematic diagram illustrating preempted physical uplink shared channel (PUSCH) resources according to some embodiments of the present disclosure;

[0011] Figure 2 is a schematic diagram illustrating a process for canceling uplink transmission according to some embodiments of the present disclosure.

[0012] Figure 3 is a schematic diagram illustrating an example uplink resource region (RUR) according to some embodiments of the present disclosure.

[0013] Figure 4 is a schematic diagram showing an example of reference block (RB) distribution according to some embodiments of the present disclosure.

[0014] Figure 5 is a schematic diagram showing an example of RB distribution and frequency domain reference points according to some embodiments of the present disclosure.

[0015] Figure 6 is a schematic diagram illustrating a method for indicating preemption of uplink transmission resources within a RUR according to some embodiments of the present disclosure.

[0016] Fig. 7A is a schematic diagram illustrating a method for indicating preemption of uplink transmission resources within a RUR according to some embodiments of the present disclosure.

[0017] Figure 7B is a schematic diagram illustrating a method for indicating preemption of uplink transmission resources within a RUR according to some embodiments of the present disclosure.

[0018] Fig. 8Ais a schematic diagram illustrating a method for indicating preemption of uplink transmission resources within a RUR according to some embodiments of the present disclosure.

[0019] Figure 8B is a schematic diagram illustrating a method for indicating preemption of uplink transmission resources within a RUR according to some embodiments of the present disclosure.

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

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

[0022] Various example embodiments of the present solution are described below with reference to the accompanying drawings to enable a person of ordinary skill in the art to make and use the present solution. It will be apparent to a person of ordinary skill in the art that, 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. In addition, 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, a person of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or behaviors in a sample order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.

[0023] 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 2 ), ultra-low latency (e.g., less than 1ms), higher reliability, and higher energy efficiency (e.g., at least 100 times more efficient than previous systems). To achieve these improvements, in wireless communication systems under the 5G standard, different types of services are configured with different priorities based on different requirements and tolerances for latency, reliability, energy efficiency, etc. For example, different types of uplink services with different transmission delay reliability requirements can be transmitted, as well as different priority channels for the same service.

[0024] When different services with different priorities are transmitted in the same cell, in order to provide transmission capacity for high-priority services, the transmission resources of low-priority services can be preempted by high-priority services, and the transmission of low-priority services using these preempted transmission resources is canceled. This mechanism avoids conflicts between low-priority services and high-priority services when using the same transmission resources for transmission. In some cases, a first service with one or more of a higher priority, higher reliability, or shorter transmission time can preempt the transmission resources of a second service with one or more of a lower priority, lower reliability, or longer transmission time.

[0025] In order to minimize the performance impact, it is necessary to convey the preemption indication information to the UE whose transmission resources are preempted. The preempted transmission resources may be referred to as "canceled transmission resources", and the preemption indication information may be referred to as "cancellation indication information".

[0026] Currently, with respect to downlink transmission resource preemption (e.g., downlink service cancellation), a base station (e.g., BS, gNB, eNB, etc.) uses downlink control information (DCI) to indicate the preempted resources in the reference downlink resource (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 the preemption status) to blocks. The 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 specific listening opportunity after the end of the preempted downlink transmission. DL PI is a "post-event" indication. The UE further completes the reception of the downlink transmission. After receiving the downlink transmission, the UE monitors the DL-PI to determine whether the previous downlink transmission has been preempted, and processes the downlink data in response to determining that the downlink transmission has not been preempted.

[0027] With regard to uplink transmission resource preemption (e.g., uplink service cancellation), similar indications may be defined for uplink time-frequency domain resources, such as, but not limited to, uplink cancellation indication (UL CI). In contrast to DL-PI, in order to prevent uplink transmission of the UE, the UE needs to be notified of the preemption via UL CI before the transmission of the uplink service. Based on this uplink cancellation indication, the uplink transmission of a service with a relatively low priority may be canceled (if not yet transmitted) or stopped (at the time of transmission) accordingly, thereby avoiding performance degradation caused by simultaneously transmitting two types of services using the same uplink transmission resource. The embodiments described herein relate to a manner in which the network side indicates or signals uplink transmission resource preemption or uplink service cancellation.

[0028] Figure 1 is a schematic diagram illustrating a process 100 for preempting PUSCH uplink transmission resources according to some embodiments of the present disclosure. Figure 1 , process 100 involves UE 102 and base station 104 (e.g., BS, gNB, eNB, etc.). Uplink transmission diagram 130 shows uplink activity of UE 102. Downlink transmission diagram 120 shows downlink activity of base station 104. Diagrams 120 and 130 show time slots divided in the time domain (represented by the horizontal axis). In some examples, a dimension or axis perpendicular to the time domain axis in each of diagrams 120 and 130 represents frequency, such as but not limited to bandwidth, activated uplink bandwidth part (BWP), etc. Frequency is discontinuous in different diagrams 120 and 130.

[0029] UE 102 sends a scheduling request (SR) 132 to base station 104 in the uplink. SR 132 requests uplink transmission resources for uplink traffic referred to as first uplink traffic from base station 104. Examples of first uplink traffic include, but are not limited to, enhanced mobile broadband (eMBB) traffic. Base station 104 allocates first 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 in the downlink to inform UE 102 that UE 102 can use PUSCH 134 to transmit the first uplink traffic.

[0030] After UE 102 sends SR 132 to base station 104, and base station 104 sends UL grant 122 to UE 102, UE 102 sends SR 112 to base station 104. SR 132 requests uplink transmission resources for uplink traffic referred to as second uplink traffic from base station 104. Examples of second uplink traffic include, but are not limited to, Ultra Reliable Low Delay Communication (URLLC) traffic.

[0031] In view of the fact that the second uplink service (e.g., URLLC service) of UE 106 has 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 the second uplink transmission resources (e.g., PUSCH 136) 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 at least a portion of PUSCH 136 (e.g., overlaps in time). In response to determining that the priority of the second uplink service (e.g., URLLC service) of UE 106 is higher than the priority of the first uplink service (e.g., eMBB service) of UE 102, base station 104 cancels the transmission of the first uplink service on the previously allocated uplink transmission resources (e.g., PUSCH 134). The UE 102 may cancel or continue transmission of the first uplink traffic in the remaining portion of the PUSCH 134 (eg, the portion of the PUSCH 134 after the PUSCH 136).

[0032] Various methods can be used to cancel low priority uplink transmissions. In one example, the base station 104 reschedules a new uplink transmission resource (not shown) 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 can retransmit the uplink grant (retransmission not shown) to the UE 102 to notify the UE 102 that the UE 102 can use the new PUSCH to transmit the first uplink service (e.g., the transmission is rescheduled to another uplink transmission resource PUSCH). The new data indicator (NDI) field of the new uplink grant is flipped to indicate that the new uplink grant corresponds to the first uplink service (e.g., eMBB service). 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. In addition, the new uplink transmission resource can be used to transmit the entire transport block (TB) or a portion thereof.

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

[0034] 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 the transmission of the first uplink service on the entire initially allocated uplink transmission resource (e.g., PUSCH 134) or a portion thereof, respectively. Thus, in response to receiving the transmission power reduction command / signal from the base station 104, the UE 102 cancels the transmission on the entire initially allocated uplink transmission resource (e.g., PUSCH 134) or a portion thereof.

[0035] The cancellation of the first uplink service due to a conflict with the high priority second uplink service described with reference to process 100 is an illustrative example of a scenario applicable to the present embodiment, and additional scenarios in which the uplink service is cancelled may be caused by other appropriate reasons and are also applicable to the present embodiment. Examples of such additional scenarios include, but are not limited to, uplink services cancelled due to a conflict with a frame structure configuration, uplink services cancelled due to a conflict with other uplink transmissions of the same UE or a different UE, uplink services cancelled due to power limitations of 102, and the like.

[0036] In some embodiments, a PUSCH (e.g., PUSCH 134) is an example of an uplink transmission resource that can carry data for both low priority traffic and high priority traffic. In order to favor one or more other types of uplink transmissions having higher priorities, a scheme similar to the scheme for canceling the first uplink transmission on PUSCH 134 can be implemented to cancel one or more other types of uplink transmissions having lower priorities due to preemption, such as, but not limited to, those on a physical uplink control channel (PUCCH), a sounding reference signal (SRS), a physical random access channel (PRACH), etc. Although the second uplink traffic transmitted using PUSCH 136 is shown as an example of high priority uplink traffic that can result in the cancellation of low priority uplink traffic, the transmission of other types of high priority uplink traffic (e.g., uplink transmissions transmitted on PUCCH, SRS, PRACH, etc.) can also result in the cancellation of low priority uplink traffic.

[0037] Figure 2 is a schematic diagram of a process 200 for canceling an uplink transmission according to some embodiments of the present disclosure. Figure 1 and 2, process 200 involves UE 102 and base station 104. Uplink transmission diagram 230 shows uplink activity of UE 102. Downlink transmission diagram 220 shows downlink activity of base station 104. Diagrams 220 and 230 show time slots divided in the time domain (represented by the horizontal axis). In some examples, the dimension or axis of each of the diagrams 220 and 230 perpendicular to the time domain axis represents frequency, such as but not limited to bandwidth, activated uplink BWP, etc. The frequency is discontinuous in different diagrams 220 and 230.

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

[0039] In some embodiments, RUR 202 may be divided into time-frequency resource subblocks. Each bit in the DCI corresponds to a time-frequency resource subblock. A bit value as a first value (e.g., 1) indicates that the time-frequency resource subblock corresponding to the bit is a cancelled resource (e.g., the uplink transmission on the time-frequency resource subblock is cancelled). A bit value as a second value (e.g., 0) indicates that the time-frequency resource subblock corresponding to the bit is not a cancelled resource (e.g., the uplink transmission on the time-frequency resource subblock is not cancelled).

[0040] in this regard, Figure 3 is a schematic diagram illustrating an example RUR 300 according to some embodiments of the present disclosure. Figure 1-3, RUR 300 is an example of RUR 202. RUR 300 is shown as a rectangle defined by dotted lines. The network side divides the entire RUR 300 into seven time domain parts and two frequency domain parts. Accordingly, RUR 300 includes a total of 14 time-frequency resource sub-blocks. That is, RUR 300 corresponds to a time domain granularity parameter of 7 (e.g., timeGranularityforCI=7) and an indication overhead parameter of 14 (e.g., CI-PayloadSize=14 bits). The time domain granularity parameter is used to indicate that RUR 300 is divided into seven time domain parts in the time domain. The indication overhead is used to indicate that 14 bits are used to signal the canceled resources in RUR 300. Based on the time domain granularity parameter and the indication overhead parameter, it can be determined that each of the seven time domain parts is further divided into two frequency domain parts. The bit value in the DCI corresponding to its time-frequency resource subblock and time-frequency resource subblock is a first value (eg, 1), indicating that the transmission of the first uplink service carried on the PUSCH 134 in the corresponding time-frequency resource subblock is cancelled.

[0041] Downlink symbols and symbols configured to receive synchronization signal blocks (SSBs) cannot be scheduled for uplink transmission. In order 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, first remove the symbols configured as semi-static downlink symbols and indicating SSBs or SS / PBCH blocks within the RUR from the range of RUR 300. Then, RUR 300 can be divided in the time domain (for example, based on the time domain granularity parameter timeGranularityforCI) to determine the time domain part. The time-frequency resource sub-block can be determined based on the time domain granularity parameter and the indication overhead parameter. These symbols can be configured as semi-static downlink symbols via the information element in the parameter tdd-UL-DL-ConfigurationCommon.

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

[0043] The time-frequency position configuration information (eg, configuration parameters) of the RUR includes at least one of a time domain start point of the RUR, a time domain duration of the RUR, and a frequency domain range of the RUR.

[0044] Regarding the time domain starting point of RUR, the time interval T after the end symbol of the detected UL CI is proc,2 The RUR starts, for example, 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 That is, the first symbol, that is, T after the end symbol of the detected UL CI proc,2 , is the starting symbol of RUR. proc,2 Corresponding to PUSCH processing capability 2. proc,2 Depends on the subcarrier spacing (SCS). For example, for an SCS of 15kHz, T proc,2 =5 symbols at 15kHz. For 30kHz SCS, T proc,2 This is equal to 5.5 symbols at 30kHz, and so on.

[0045] In one scenario, different UEs (with different SCSs) can 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 so as to reach a consensus on the same time domain starting point of the RUR. The SCS can be determined using one of various methods to ensure that different UEs detecting the same UL CI can determine the same time domain starting point of the RUR.

[0046] In the first method, the SCS used to determine the time domain starting point of the RUR (referred to as the reference SCS) is the lowest SCS in the SCS list (e.g., scs-SpecificCarrierList) in the uplink carrier frequency information. In some embodiments, the network side configures the uplink carrier frequency information (such as but not limited to the information element FrequencyInfoUL) and transmits the uplink carrier frequency information in the system information, such as but not limited to the system information block 1 (SIB1). The uplink carrier frequency information includes an SCS list (e.g., scs-SpecificCarrierList) of all SCSs used in the uplink carrier. The UE can use the SCS list to configure the available RB distribution for each SCS within the carrier.

[0047] For each SCS in the SCS list of the uplink carrier frequency information, the offset between the lowest available subcarrier of the SCS and point A (configured by the parameter offsetToCarrier), and the number of RBs of the SCS (configured by the parameter carrierBandwidth) are configured or determined accordingly. Figure 4 is a schematic diagram showing an example of RB distribution 400 according to some embodiments of the present disclosure. Figure 1-4 , the SCS list includes SCSs of 30kHz and 15kHz. RB distribution 400 includes RB distributions 410 and 420. RB distribution 410 is the distribution of available RBs for the SCS of 30kHz. RB distribution 420 is the distribution of available RBs for the SCS of 15kHz. Point A refers to the common starting point of the common RB (CRB) of all SCSs of the carrier. That is, subcarrier 0 of CRB0 of all SCSs within the carrier is aligned with point A. For each SCS of 30kHz or 15kHz in the SCS list, an offset is configured between the lowest available subcarrier of each SCS of 30kHz or 15kHz and point A (for example, offset 415 or 425, respectively). In addition, for each SCS of 30kHz or 15kHz, the number of RBs of the SCS is configured (for example, the number of RBs of 30kHz or 15kHz, respectively).

[0048] In some examples, in response to the UE detecting the UL CI, the UE may determine T 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 the SCS list (e.g., scs-SpecificCarrierList) in the UL carrier frequency information. Figure 4 As shown, the lowest SCS in the SCS list is the SCS of 15 kHz, and therefore, the reference SCS is the SCS of 15 kHz.

[0049] In the second method, the reference SCS is the largest SCS in the SCS list (e.g., scs-SpecificCarrierList) in the uplink carrier frequency information. Figure 4 As shown, the largest SCS in the SCS list is the SCS of 30 kHz, and therefore, the reference SCS is the SCS of 30 kHz.

[0050] In the third method, the reference SCS is the SCS in the SCS list that is closest to the UL CI. In an example where the SCS list of the uplink carrier frequency information includes SCSs of 15kHz and 60kHz, and the SCS of UL CI 201 is 30kHz, the SCS of 15kHz is determined as the reference SCS since 15kHz is closer to 30kHz.

[0051] In the fourth method, the reference SCS is the lower SCS of the SCS of UL CI 201 and the lowest SCS among multiple SCSs in the SCS list of the uplink carrier frequency information. In the example where the SCS of UL CI 201 is 15kHz and the SCSs in the SCS list are 30kHz and 60kHz, the reference SCS is the SCS of UL CI 201, which is 15kHz.

[0052] Regarding the time domain duration of the RUR, the base station can configure the number of symbols corresponding to the time domain duration of the RUR via radio resource control (RRC) layer parameters (e.g., those starting with "+-"). Similar to the time domain start 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 can be determined using one of the various methods applicable to the SCS for determining the time domain start point to ensure that different UEs detecting the same UL CI can determine the same RUR time domain duration.

[0053] That is, in the first method, the reference SCS used to determine the time domain duration of the RUR is the lowest SCS in the SCS list (e.g., scs-SpecificCarrierList) in the uplink carrier frequency information. In the second method, the reference SCS used to determine the time domain duration of the RUR is the largest SCS in the SCS list (e.g., scs-SpecificCarrierList) in the uplink carrier frequency information. In the third method, the reference SCS used to determine the time domain duration of the RUR is the SCS in the SCS list that is closest to the UL CI. In the fourth method, the reference SCS is the lower SCS of the UL CI and the lowest SCS in the SCS list of the uplink carrier frequency information.

[0054] Regarding the frequency domain range of the RUR, the network side (including the base station 104) configures the frequency domain start 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 the parameter frequencyRegionforCI). For example, the frequency domain start 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 start 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 the frequency domain start point and the number of RBs of the RUR.

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

[0056] That is, in the first 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 lowest SCS in the SCS list (e.g., scs-SpecificCarrierList) in the uplink carrier frequency information. In the 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 the SCS list (e.g., SCS-specific carrier list) in the uplink carrier frequency information. In the third 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 SCS in the SCS list that is closest to the UL CI. In the fourth method, the reference SCS is the lowest SCS of the UL CI and is the lowest SCS in the SCS list of the uplink carrier frequency information.

[0057] As described above, the time-frequency position configuration information (eg, 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.

[0058] In some embodiments, the reference SCS can be determined based on whether the SCS list in the uplink carrier frequency information includes the SCS of the UL CI. For example, in response to determining that the SCS list (e.g., scs-SpecificCarrierList) in the uplink carrier frequency information includes the 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 the 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 SCS list in the uplink carrier frequency information. In the third method, the reference SCS is the SCS of the SCS closest to the UL CI in the SCS list. In the fourth method, the reference SCS is the lower of the SCS of the UL CI and the lowest SCS in the SCS list of the uplink carrier frequency information.

[0059] In some embodiments, the reference SCS is determined to be the SCS of the UL CI. In order to configure the SCS of the UL CI, the base station can only configure one SCS in the SCS list (scs-SpecificCarrierList) in the uplink carrier frequency information as the SCS of the UL CI. That is, the UE expects the SCS of the UL CI to be in the SCS list. Therefore, the UE can select the SCS of the UL CI from the SCS list as the reference SCS.

[0060] As described above, the frequency domain starting point of the frequency domain range of the RUR can be defined as the frequency domain offset of the frequency domain reference point, and the frequency domain reference point is defined as the lowest available subcarrier of the reference SCS. The number of RBs can be determined based on the reference SCS. In some embodiments, the SCS of the UL CI is determined as the reference SCS. In response to determining that the SCS list (e.g., scs-SpecificCarrierList) of the uplink carrier frequency information does not include the SCS of the UL CI, the frequency domain reference point is determined based on the uplink carrier point A and the downlink carrier frequency information.

[0061] In some examples, the parameter offsetToCarrier in the SCS list in the downlink carrier frequency information is used to indicate the position of the lowest available subcarrier of the SCS (e.g., 15kHz) of the UL CI. Figure 5 is a schematic diagram showing an example of RB distribution 510 and frequency domain reference points 520 according to some embodiments of the present disclosure. Figure 1-5, RB distribution 510 is a distribution of available RBs for a 15kHz SCS for UL CI. RB distribution 510, including the lowest available subcarrier at 15kHz for UL CI, is indicated by the parameter offsetToCarrier in the SCS list in the downlink carrier frequency information. Downlink carrier point A refers to the common starting point of the common RB (CRB) of all SCSs of the downlink carrier of 15kHz. That is, subcarrier 0 of CRB0 of all SCSs within the downlink carrier is aligned with point A. An offset 515 between the lowest available subcarrier at the SCS (e.g., 15kHz) of the UL CI and point A is configured. In addition, the number of RBs of 15kHz RBs for UL CI is configured and indicated using the parameter offsetToCarrier 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 (increased by frequency) the offset 515. Therefore, based on Figure 5 The frequency domain range of the RUR is defined by the frequency domain reference point 520 and the frequency domain offset 515. The frequency domain offset 515 and the number of RBs are indicated by frequencyRegionforCI.

[0062] Figure 6 6 is a diagram illustrating a method 600 for indicating preemption of uplink transmission resources within a RUR 620 according to some embodiments of the present disclosure. Figure 1-6 The base station may configure the time slot format 601 via appropriate RRC signaling (eg, TDD-UL-DL-ConfigCommon). As shown, a portion of the time slot format 201 includes at least eight time slots 611-618. Figure 6 The dimension or axis perpendicular to the time domain axis in represents frequency, such as but not limited to bandwidth, activated BWP, etc. The resource type of time slots 611-618 is configured as "DFFFDFFF", where "D" represents downlink time slots 611 and 615, and "F" represents flexible time slots 612-614 and 616-618.

[0063] The base station configures 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. For example, the time domain duration can be configured by the parameter timedurationforCI. The time domain granularity can be configured by the parameter timeGranularityforCI. The indication overhead N can be configured by the parameter CI-PayloadSize.

[0064] RUR 620 includes four time slots, including three flexible time slots and one semi-static downlink time slot. The semi-static downlink time slot includes 14 symbols. In addition, RUR 620 includes six SSBs 633-638. Each of SSBs 631-638 occupies 4 consecutive symbols. Assuming that all six SSBs 633-638 in RUR 620 are actually transmitted, the SSBs 633-638 have a total of 24 symbols. After subtracting the semi-static downlink symbols (14 symbols) and the SSB symbols (24 symbols) from the time domain duration (56 symbols) configured in timedurationforCI, the remaining 18 symbols (referred to as T) are symbols that can correspond to UL CI.

[0065] T can be divided according to the configured G. The first x time domain parts contain symbols, where:

[0066]

[0067] Remaining The time domain part contains symbol.

[0068] In response to determining that the number of symbols T remaining in RUR 620 after 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 parts contain 0 symbols and the last 18 time domain parts will contain 1 symbol.

[0069] In addition, regardless of whether the divided time domain parts actually contain any symbols, the indication overhead N=112 bits are evenly divided into 28 time domain parts. Each time domain part occupies 4 bits. That is, the frequency domain indication granularity is 1 / 4. Therefore, the first 10 time domain parts still occupy 40 bits, although the first 10 time domain parts do not actually correspond to any uplink transmission resources. Therefore, 40 bits are wasted and the indication efficiency is low.

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

[0071] M=min{G,T} (2).

[0072] The RUR 620 is actually divided into M time domain parts in the time domain. The first x time domain parts include symbols, among which:

[0073]

[0074] Remaining The time domain part contains symbol.

[0075] RUR 620 is actually divided into 18 time domain parts, each of which contains 1 symbol. The frequency domain indication granularity of each time domain part is:

[0076]

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

[0078] In some embodiments, different numbers of bits are allocated to different time domain parts to efficiently utilize the indicator bits.The total indicator bits may be allocated to each time domain part according to one of the allocation methods.

[0079] In the first allocation method, the first Time domain part allocation bits. For the remaining time domain parts, allocated bits. Correspondingly, the previous The time domain part is divided into frequency domain parts, and the remaining The time domain part is divided into The frequency domain part.

[0080] In the second allocation method, the first Time domain part allocation bits. For the remaining time domain parts, allocated bits. Correspondingly, the previous The time domain part is divided into frequency domain parts, and the remaining The time domain part is divided into The frequency domain part.

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

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

[0083] In an example where the set of timeGranularityforCI values 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 < G). In this example, since 14 is the closest to G and less than T, the actual time domain granularity G' is selected to be 14. Thus, G' = 14. The RUR 620 can be practically divided into 14 time domain parts, where the first 10 (e.g., ) time domain parts contain 1 (e.g., ) symbol, and the remaining 4 (e.g., ) time domain parts contain 2 (e.g., ) symbols. The frequency domain indication granularity is Therefore, no bits are wasted.

[0084] In response to determining that T ≥ G, the base station and the UE select G as the actual time domain granularity G'. The first time domain parts contain symbols, and the remaining time domain parts contain symbols.

[0085] In some embodiments, there is no restriction on the configured time domain granularity parameter (e.g., configured by timeGranularityforCI). In an example where the RUR includes symbols occupied by the SSB, the number of remaining symbols T in the RUR can be less than the configured time domain granularity parameter. If the time domain parts are divided according to the configured time domain granularity, some time domain parts do not contain any symbols. To avoid this situation, in some embodiments, the value of the configured time domain granularity parameter can be restricted during configuration. For example, the configured time domain granularity parameter G cannot be greater than the number of remaining symbols T. In other words, when the network side configures the time domain granularity parameter G, the number of remaining symbols T in the RUR is considered to ensure that the configured time domain granularity parameter G is less than or equal to the number of remaining symbols T. In this case, the configured time domain granularity parameter G can be used as the actual time domain granularity G'.

[0086] Fig. 7A is a schematic diagram showing a method 700a for indicating preemption of uplink transmission resources within the RUR according to some embodiments. Referring to Figure 1-5 and 7A, the method 700a is executed by the base station.

[0087] At 710, the base station configures a first uplink resource. The first uplink resource is defined using configuration parameters including at least one of a time domain start 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 a RUR. The second uplink resource is an uplink resource (e.g., PUSCH 134) within the RUR, wherein transmission of an uplink service carried on the uplink resource is to be canceled.

[0088] Configuration parameters of the first uplink resource are determined based on a reference SCS. In some embodiments, the reference SCS is the lowest SCS among multiple SCSs in the SCS list in the uplink carrier frequency information. In some embodiments, the reference SCS is the maximum SCS among multiple SCSs in the SCS list in the uplink carrier frequency information. In some embodiments, the reference SCS is the SCS that is closest to the indicated SCS among multiple SCSs in the SCS list in the uplink carrier frequency information. In some embodiments, the reference SCS is the lower one of the indicated SCS and the lowest SCS among multiple SCSs in the SCS list in the uplink carrier frequency information.

[0089] In some embodiments, in response to determining that the SCS list in the uplink carrier frequency information includes the indicated SCS, the reference SCS is the indicated SCS. In some embodiments, in response to determining that the SCS list in the uplink carrier frequency information does not include the indicated SCS, the reference SCS is one of the following: the lowest SCS among multiple SCSs in the SCS list, the maximum SCS among multiple SCSs in the SCS list, or the closest SCS to the indicated SCS among multiple SCSs in the SCS list.

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

[0091] 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 a reference SCS. The number of RBs is determined based on the reference SCS. In response to determining that the SCS list of the uplink carrier frequency information does not include the indicated SCS, the frequency domain reference point is determined based on the uplink carrier point A and the downlink carrier frequency information.

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

[0093] Figure 7B is a schematic diagram illustrating a method 700b for indicating preemption of uplink transmission resources within a RUR according to some embodiments. Figure 1-5 , 7A and 7B, method 700b is performed by the UE.

[0094] At 730, the UE receives an indication from the base station that uplink transmission on a second uplink resource within the first uplink resource is canceled. The first uplink resource is defined using a configuration parameter, the configuration parameter including at least one of a time domain start 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 uplink transmission on the second uplink resource.

[0095] Fig. 8A 8 is a schematic diagram illustrating a method 800a for indicating preemption of uplink transmission resources within a RUR according to some embodiments. Figure 1-3 , 6 and 8A, method 800a is performed by the UE.

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

[0097] In some embodiments, M is defined as M=min{G,T}. The first uplink resource is actually divided into M time domain parts. The first x time domain parts include symbols, among which Remaining The time domain part contains symbol.

[0098] In some embodiments, in response to determining that T is less than G, a time domain granularity value is selected from the time domain granularity set as the actual time domain granularity G'. The selected actual time domain granularity G' is less than T and closest to G. The time domain part includes The remaining first uplink resources The time domain part contains symbol.

[0099] 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. The time domain part includes The remaining first uplink resources The time domain part contains symbol.

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

[0101] Figure 8B 8 is a diagram illustrating a method 800b for indicating preemption of uplink transmission resources within a RUR according to some embodiments. Figure 1-3 , 6, 8A and 8B, method 800b is performed by the base station.

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

[0103] Fig.9A A block diagram of an example base station 902 is shown in accordance with some embodiments of the present disclosure. Fig. 9B FIG. 9 is a block diagram of an example UE 901 according to some embodiments of the present disclosure. Figure 1-9B In the present invention, UE 901 (eg, wireless communication device, terminal, mobile device, mobile user, etc.) is an example implementation of a UE described herein, and base station 902 is an example implementation of a base station described herein.

[0104] The base station 902 and the UE 901 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, as described above, the base station 902 and the UE 901 may be used to transmit (e.g., transmit and receive) data symbols in a wireless communication environment. For example, the base station 902 may be a base station (e.g., gNB, eNB, etc.), a server, a node, or any suitable computing device used to implement various network functions.

[0105] The 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 to each other 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 to 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.

[0106] As is understood by those skilled in the art, the base station 902 and the UE 901 may also include Fig.9A and 9B 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 actual combination thereof. In order to illustrate this interchangeability and compatibility of hardware, firmware and software, various illustrative components, blocks, modules, circuits and steps are usually described according to their functions. Whether such functions are implemented in hardware, firmware or software depends on the application of specific applications and the design constraints on the entire system. The embodiments described herein can be implemented in an appropriate manner for each specific application, but any implementation decision should not be interpreted as limiting the scope of the present disclosure.

[0107] According to some embodiments, the UE transceiver 930 includes a radio frequency (RF) transmitter and an RF receiver, each of which includes a circuit coupled to an antenna 932. A duplex switch (not shown) can alternately couple the RF transmitter or receiver to the antenna in a time duplex manner. Similarly, according to some embodiments, the transceiver 910 includes an RF transmitter and an RF receiver, each of which has a circuit coupled to an 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 can be coordinated in time so that the receiver circuit is coupled to the antenna 932 while the transmitter is coupled to the antenna 912 to receive the transmission on the wireless transmission link. In some embodiments, there is tight time synchronization with a minimum guard time between changes in duplex direction.

[0108] The UE transceiver 930 and the transceiver 910 are configured to communicate via a wireless data communication link and cooperate with an appropriately configured RF antenna arrangement 912 / 932 that can support a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 910 and the 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 specific standards and related protocols. Instead, the UE transceiver 930 and the base station transceiver 910 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0109] The transceiver 910 and the transceiver of another base station (such as but not limited to the transceiver 910) are configured to communicate via a wireless data communication link and cooperate with an appropriately configured RF antenna arrangement that can support a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the transceiver 910 and the 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 the application of specific standards and related protocols. On the contrary, the transceiver 910 and the transceiver of another base station can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0110] According to various embodiments, the base station 902 may be a base station, such as but not limited to an eNB, a serving eNB, a target eNB, a femtocell or a microcell. The base station 902 may be an RN, a conventional, a DeNB or a gNB. In some embodiments, the UE 901 may be embodied in various types of user equipment, 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 914 and 936 may be implemented or implemented 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, 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, for example, a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a digital signal processor core, or any other such configuration.

[0111] In addition, the methods or algorithms disclosed herein may be directly embodied in hardware, firmware, software modules executed by processor modules 914 and 936, respectively, or in any practical combination thereof. Memory modules 916 and 934 may be implemented as RAM memory, flash memory, ROM 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 916 and 934 may be coupled to processor modules 910 and 930, respectively, so that processor modules 910 and 930 can read information from and write information to memory modules 916 and 934, respectively. Memory modules 916 and 934 may also be integrated into respective processor modules 910 and 930. In some embodiments, memory modules 916 and 934 may each include a cache for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 910 and 930, respectively. Memory modules 916 and 934 may also each include non-volatile memory for storing instructions to be executed by processor modules 910 and 930, respectively.

[0112] The network communication module 918 generally represents the hardware, software, firmware, processing logic and / or other components of the base station 902, which implements two-way communication between the transceiver 910 and other network components and communication nodes communicating with the base station 902. For example, the network communication module 918 can 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 a conventional computer network based on Ethernet. In this way, the network communication module 918 can 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 includes a fiber optic transmission connection configured to connect the base station 902 to the core network. The terms "configured for", "configured to" and their conjunctions, 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 a specified operation or function.

[0113] Although various embodiments of the present solution have been described above, it should be understood that they are presented only by way of example and not by way of limitation. Similarly, various figures may depict example architectures or configurations, and the example architectures or configurations provided enable those of ordinary skill in the art to understand the example features and functions of the present solution. However, these people will understand that the solution is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. In addition, as will be understood 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 of the illustrative embodiments described above.

[0114] It should also be understood that any reference to an element using names such as "first", "second", etc. herein does not generally limit the number or order of these elements. Instead, these names can be used herein as a convenient means of distinguishing two or more elements or element instances. Therefore, 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 be located before the second element in some way.

[0115] In addition, those skilled in the art will appreciate that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0116] Those of ordinary skill in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of the two), firmware, various forms of programs or design codes incorporating instructions (which, for convenience, may be referred to herein as "software" or "software modules"), 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 generally described above according to their functions. Whether such functions are implemented in hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the entire system. Those skilled in the art may implement the described functions in various ways for each specific application, but such implementation decisions will not result in deviations from the scope of this disclosure.

[0117] 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 or performed within 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 further 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 plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration to perform the functions described herein.

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

[0119] 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. In addition, for the purpose of ease of discussion, various modules are described as discrete modules; however, it is obvious to those of ordinary skill in the art that two or more modules can be combined to form a single module that performs the relevant functions according to embodiments of the present solution.

[0120] In addition, in the embodiment of the present solution, memory or other memory and communication components can be used. It should be understood that, for the sake of clarity, the above description has described the embodiment of the present solution with reference to different functional units and processors. However, it is obvious that any appropriate functional distribution between different functional units, processing logic elements or domains can be used without affecting the present solution. For example, the functions shown as being performed by different processing logic elements or controllers can be performed by the same processing logic element or controller. Therefore, reference to a specific functional unit is only a reference to an appropriate means for providing the described functions, rather than an indication of a strict logical or physical structure or organization.

[0121] 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 given the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims.

Claims

1. A wireless communication method, comprising: The wireless communication device receives the time domain granularity G indicated by the network side from the base station, and 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; as well as The wireless communication device determines, based on T and G, a number of time domain portions of the first uplink transmission resource, wherein: M is defined as M=min{G,T}, the first uplink resource is actually divided into M time domain parts, the first x time domain parts include symbols, and the remaining The time domain part contains symbols; or, in response to determining that T is less than G, a time domain granularity value selected from the time domain granularity set is used as the actual time domain granularity G', the selected actual time domain granularity G' is less than T and closest to G, the front of the first uplink resource The time domain part contains symbols, and the remaining of the first uplink resource The time domain part contains symbols; or, G is less than or equal to T, and G is determined based on T.

2. The method according to claim 1, wherein: In response to determining that T is greater than or equal to G, G is determined as the actual time domain granularity; The first uplink resource The time domain part contains symbols; and The remaining amount of the first uplink resource The time domain part contains symbol.

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

4. 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 according to claim 1.

5. A wireless communication method, comprising: The time domain granularity G indicated by the network side is configured by the base station; The base station determines, by the base station, 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, wherein the number of actual time domain portions of the first uplink transmission resource is determined based on T and G, wherein: M is defined as M=min{G,T}, the first uplink resource is actually divided into M time domain parts, the first x time domain parts include symbols, and the remaining The time domain part contains symbols; or, T is less than G, the time domain granularity value selected from the time domain granularity set is used as the actual time domain granularity G', the selected actual time domain granularity G' is less than T and closest to G, the front of the first uplink resource The time domain part contains symbols, and the remaining of the first uplink resource The time domain part contains symbols; or, G is less than or equal to T, and G is determined based on T.

6. The method according to claim 5, wherein: T is greater than or equal to G, and G is determined as the actual time domain granularity; The first uplink resource The time domain part includes symbols; and The remaining amount of the first uplink resource The time domain part contains symbol.

7. A wireless communication device, comprising at least one processor and a memory, wherein the at least one processor is configured to read a code from the memory and implement the method according to claim 5.

8. 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 according to claim 5.

Images