CN115053596A

CN115053596A - System and method for downlink control information transmission

Info

Publication number: CN115053596A
Application number: CN202080095754.3A
Authority: CN
Inventors: 刘星; 肖凯; 张峻峰; 张晨晨; 韩祥辉; 郝鹏
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2020-05-15
Filing date: 2020-05-15
Publication date: 2022-09-13
Also published as: US20220361235A1; WO2021109463A1; EP4082273A4; EP4082273A1

Abstract

A system and method for wireless communication is disclosed herein. In one embodiment, the wireless communication device determines that the first resource indicated by the uplink cancellation information overlaps with the second resource. The wireless communication device receives an Uplink (UL) grant from the network scheduling a third resource. The end symbol of the first downlink control channel carrying the UL grant is no earlier than the first symbol of the second downlink control channel carrying the uplink cancellation information.

Description

System and method for downlink control information transmission

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 aim to address problems associated with one or more of the problems posed in the prior art and to provide additional features that will become apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. In accordance with various embodiments, example systems, methods, devices, 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 wireless communication device determines that the first resource indicated by the uplink cancellation information overlaps with the second resource. The wireless communication device receives an Uplink (UL) grant from the network scheduling a third resource. The end symbol of the first downlink control channel carrying the UL grant is no earlier than the first symbol of the second downlink control channel carrying the uplink cancellation information.

In some embodiments, the network transmits uplink cancellation information to the wireless communication device indicating the first resource. The first resource overlaps with a second resource of the wireless communication device. The network transmits an UL grant scheduling the third resource to the wireless communication device. The end symbol of the first downlink control channel carrying the UL grant is no earlier than the first symbol of the second downlink control channel carrying the uplink cancellation information.

The above and other aspects and embodiments thereof are described in more detail in the accompanying drawings, description and 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 are not to be considered limiting of 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 made to scale.

Fig. 1 is a schematic diagram illustrating Physical Uplink Shared Channel (PUSCH) resources being preempted 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 diagram illustrating a slot structure corresponding to an example configuration 400 of PDCCH monitoring occasions in accordance with various embodiments;

figure 5 is a schematic diagram illustrating an example RUR, according to some embodiments of the present disclosure;

figure 6 is a schematic diagram illustrating an example RUR, according to some embodiments of the present disclosure;

fig. 7 is a schematic diagram illustrating an example RUR according to some embodiments of the present disclosure;

FIG. 8 is a schematic diagram illustrating an example RUR according to a first method;

fig. 9 is a diagram illustrating an example RUR according to a third method;

fig. 10 is a diagram illustrating an example RUR according to a fourth method;

fig. 11 is a diagram illustrating an example RUR according to a fifth method;

fig. 12 is a diagram illustrating an example RUR according to a sixth method;

fig. 13 is a schematic diagram illustrating an example RUR according to a seventh method;

fig. 14 is a schematic diagram illustrating an example RUR according to an eighth method;

fig. 15 is a schematic diagram illustrating an example RUR according to a ninth method;

fig. 16 is a diagram illustrating an example RUR according to a tenth method;

fig. 17 is a schematic diagram illustrating an example RUR according to an eleventh method;

fig. 18A is a schematic diagram illustrating a method for downlink control information transmission, in accordance with some embodiments of the present disclosure.

Fig. 18B is a schematic diagram illustrating a method for downlink control information transmission, in accordance with some embodiments of the present disclosure.

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

fig. 19B 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 an example approach. Based upon design preferences, the specific 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/Km2), ultra-low latency (e.g., below 1ms), higher reliability, and improved energy efficiency (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 services with different transmission delay reliability requirements, and different priority channels for the same service may be transmitted.

When different services having different priorities are transmitted within the same cell, in order to provide the transmission capability of a high priority service, the transmission resources of a 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 collisions between low priority services and high priority services when transmitting using the same transmission resource. In some cases, a first service with one or more of a higher priority, higher reliability, or shorter transmission time may preempt transmission resources of a second service with 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 preempted transmission resource may be referred to as a "cancelled transmission resource". The preemption indication information may be referred to as "cancellation indication information".

With respect to uplink transmission resource preemption (e.g., uplink service cancellation), an indication, such as but not limited to an uplink cancellation indication (UL CI, which may also be referred to as DCI format 2_4 carried in PDCCH), may be defined for uplink time-frequency domain resources. To prevent uplink transmission by the UE, the UE needs to notify preemption through UL CI before transmission of uplink service. Based on such an uplink cancellation indication, uplink transmissions of services having a relatively low priority can be cancelled (if not already transmitted) or stopped (while transmitting) accordingly, thereby avoiding performance degradation due to simultaneous transmission of both types of services using the same uplink transmission resource. Embodiments described herein relate to a way for the network side to indicate uplink transmission resource preemption or uplink service cancellation or to signal this.

Fig. 1 is a schematic diagram illustrating a process 100 by which PUSCH uplink transmission resources are preempted, 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., BS, gNB, 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 active 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 an uplink service (referred to as a first uplink service) from the base station 104. Examples of the first uplink service include, but are not limited to, enhanced mobile broadband (eMBB) services. The base station 104 allocates a first uplink transmission resource (e.g., PUSCH 134) to the UE 102 through an uplink grant (UL grant) 122. The base station 104 sends a UL grant 122 in the downlink to the UE 102 to inform the UE 102 to: UE 102 may transmit the first uplink service using PUSCH 134.

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 112 requests an uplink transmission resource for an uplink service (referred to as a second uplink service) from the base station 104. Examples of the second uplink service include, but are not limited to, an ultra-reliable low-latency communication (URLLC) service.

In view of the ultra-high reliability and ultra-low latency transmission requirements of the second uplink service (e.g., URLLC service) 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 collides with (e.g., overlaps with) at least a portion of the PUSCH 136. 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 transmission of the first uplink service on the previously allocated uplink transmission resource (e.g., PUSCH 134). UE 102 may cancel or continue transmission of the first uplink service 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 the uplink grant (retransmission not shown) to the UE 102 to inform the UE 102 to: the UE 102 may transmit the first uplink service using the new PUSCH (e.g., transmission is rescheduled to another uplink transmission resource, PUSCH). A New Data Indicator (NDI) field of the new uplink grant is toggled, indicating that the new uplink grant corresponds to the first uplink service (e.g., the eMBB service). 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 inform the UE 102 to: the initially allocated uplink transmission resource (e.g., PUSCH 134) is preempted by high priority service transmissions using cancellation indication signaling (e.g., UL CI). 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 physical DCI on a 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 service 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 service due to a collision 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 suitable reasons and are equally applicable to the present embodiment. Examples of such additional scenarios include, but are not limited to, uplink services cancelled due to collisions with frame structure configurations, uplink services cancelled due to collisions with other uplink transmissions of the same UE or a different UE, uplink services cancelled due to power limitations 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 both low priority services and high priority services. A similar scheme to that used to cancel the first uplink transmission on PUSCH 134 may be implemented to cancel one or more other types of uplink transmissions having lower priorities, such as, but not limited to, those on Physical Uplink Control Channel (PUCCH), Sounding Reference Signal (SRS), Physical Random Access Channel (PRACH), etc., since preemption favors one or more other types of uplink transmissions having higher priorities. While the second uplink service transmitted using PUSCH 136 is shown as an example of a high priority uplink service that may result in cancellation of a low priority uplink service, transmissions of other types of high priority uplink services (e.g., uplink transmissions communicating on PUCCH, SRS, PRACH, etc.) may likewise result in cancellation of a low priority uplink service.

Fig. 2 is a schematic diagram illustrating a process 200 for cancelling uplink transmissions, in accordance with some embodiments of the present disclosure. Referring to fig. 1 and 2, process 200 involves UE 102 and 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 the time domain axis represents a frequency, such as, but not limited to, a bandwidth, an active uplink BWP, a carrier, 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 an uplink resource region (RUR) 202. In particular, the UL CI 201 is used to indicate or otherwise identify cancellation of transmission of an uplink service carried on an uplink resource (e.g., PUSCH 134) within the RUR 202 corresponding to the UL CI 201.

In some embodiments, the RUR 202 may be divided into a plurality of time-frequency resource sub-blocks. Each bit in the DCI corresponds to a time-frequency resource sub-block. A bit value that is a first value (e.g., 1) indicates that the time-frequency resource sub-block corresponding to the bit is a cancelled resource (e.g., uplink transmissions on the time-frequency resource sub-block are 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 transmissions on the time-frequency resource sub-block are not revoked).

The cancelled transmission may also be a grant Channel (CG) -PUSCH in a configured CG resource (e.g., CG-PUSCH). The CG resources are configured to the UE through Radio Resource Control (RRC) signaling (e.g., configuredgontonfig) so that the UE can transmit uplink transmissions on the CG resources without UL grant. If the higher layer does not deliver transport blocks for transmission on the resources allocated for uplink transmission without UL grant, the UE will not transmit anything on the configured resources.

In this regard, fig. 3 is a schematic diagram illustrating an example RUR 300, according to some embodiments of the present disclosure. Fig. 3 has a time domain as the horizontal axis and a frequency (e.g., bandwidth, active uplink bandwidth portion (BWP), carrier, etc.) as the vertical axis. Referring to FIGS. 1-3, RUR 300 is an example of RUR 202. UL grant 302 is an example of UL grant 124. The RUR 300 is shown as a rectangle defined by a dashed line. As shown in fig. 3, in the case where the cancelled resource 305 (which is cancelled by UL CI 301) overlaps with the CG resource 304 of the UE, the gNB [ "gnnodeb" ] does not know whether the uplink transmission will be transmitted on the CG resource 304 or whether the UE will cancel the uplink transmission. Therefore, the issue is in what case the UL grant 302 for PUSCH 2303 can be transmitted by the network side node.

In a wireless communication system, a control resource set (CORESET) includes one or more Resource Blocks (RBs) in a frequency domain and one or more Orthogonal Frequency Division Multiplexing (OFDM) symbols in a time domain. One or more Physical Downlink Control Channel (PDCCH) candidates are transmitted in the CORESET. The configuration parameters of the CORESET are configured for the UE by the network, and comprise a CORESET index, frequency domain resources, CORESET duration and the like. The UE may be configured with one or more CORESETs to monitor the PDCCH.

In a wireless communication system, a network configures one or more search space sets for a UE. The configuration parameters of the search space set include a search space index, an associated CORESET index, a PDCCH monitoring period and offset, a search space duration, a PDCCH monitoring pattern within a time slot, a search space type, and the like. In general, there are two types of search spaces, UE-specific search space (USS) and Common Search Space (CSS). The search space type also indicates a Downlink Control Information (DCI) format that the UE monitors. The set of search spaces is associated with CORESET. The PDCCH monitoring period and offset indicate the time slot in which the UE needs to monitor the PDCCH. According to the search space set configuration and the associated CORESET configuration, the UE is configured to: in a slot indicated by the PDCCH monitoring period and offset, a corresponding PDCCH having a DCI format indicated by a search space type is monitored on a resource indicated by CORESET.

Fig. 4 is a diagram illustrating a slot structure corresponding to an example configuration 400 of PDCCH monitoring occasions, in accordance with various embodiments. Referring to fig. 4, configuration 400 corresponds to time slots 402a, 402b, 402c, 402d, 402e, 402f, 402g, and 402h (collectively referred to as time slots 402a-402 h). The PDCCH monitoring period is a period in which the UE monitors the PDCCH. In configuration 400, the PDCCH monitoring period is 4 slots. That is, the slots 402a-402d are in the PDCCH monitoring period 406a, and the slots 402e-402h are in the PDCCH monitoring period 406 b. The PDCCH monitoring offset in configuration 400 is 0 (e.g., no offset). The search space in configuration 400 is 2 slots in duration. As shown, the search space duration 404a includes time slots 402a and 402b during a PDCCH monitoring period 406 a. Within PDCCH monitoring period 406b, search space duration 404b includes time slots 402e and 402 f. In configuration 400, 2 PDCCH Monitoring Occasions (MOs) are configured in a given slot within search duration 404a or 404 b. For example, slot 402a includes 44

OFDM symbols

410a, 410b, 410c, 410d, 410e, 410f, 410g, 410h, 410i, 410j, 410k, 410l, 410m, and 410n (collectively, symbols 410a-410 n). The symbols 410a and 410h are configured as the first symbol of the MO. Therefore, there are 4 MOs in each PDCCH monitoring period. For example, symbols 410a and 410h in slot 402b and the two additional first symbols of the MO are within PDCCH monitoring period 406 a. The two first symbols of the MO in each of slots 402e and 402f are within PDCCH monitoring period 406 b. In each MO, the UE monitors the PDCCH within one resource configured by CORESET.

In a wireless communication system, one or more Control Channel Element (CCE) Aggregation Levels (ALs) may be configured for a search space. For each AL, there are one or more PDCCH candidates, and each PDCCH candidate has a PDCCH candidate index. The PDCCH includes one or more CCEs, and each CCE has a CCE index. For a particular search space, the predefined formula may determine a CCE index for a particular AL corresponding to a particular PDCCH candidate index.

For UL CI monitoring, only one AL can be configured, and only one PDCCH candidate is defined for the configured AL. The UE will then monitor the UL CI among the defined PDCCH candidates using only the configured AL. The configured under-AL UL CI PDCCH candidates are defined as at least one of the following PDCCH candidates: 1) under AL for configuration of UL CI, there is no first PDCCH candidate configured for DCI format 2_ 0; 2) a second PDCCH candidate under configured AL for UL CI; 3) a third PDCCH candidate under configured AL for UL CI; 4) the last PDCCH candidate under the configured AL for UL CI; or 5) PDCCH candidate index under the configured AL of the UL CI configured by RRC signaling, MAC signaling, or a combination of RRC signaling and MAC signaling. For example, a PDCCH candidate list having N PDCCH candidate indexes is configured through RRC signaling, and the PDCCH candidate indexes are 1, 3, 4, and 5 for N ═ 4. One of the indices may be further indicated by MAC signaling (e.g.,

2 bits in signaling) so that "00" denotes "PDCCH candidate index 1", "01" denotes "PDCCH candidate index 3", "10" denotes "PDCCH candidate index 4", and "11" denotes "PDCCH candidate index 5"

In a wireless communication system, in order for a Base Station (BS) to know uplink Power usage of a terminal more accurately, a Power Headroom Report (PHR) mechanism is supported. In other words, according to the configuration of the base station, the terminal will report the Power Headroom (PH) or both the PH and the maximum transmission power (Pcmax) when a specific trigger condition is satisfied.

For power headroom reporting, class 1 PHR and class 3 PHR are defined in New Radio (NR) systems. The UE determines a type 1 PHR that activates the serving cell based on the actual PUSCH transmission or the reference format. The UE determines to activate a class 3 PHR of a serving cell based on an actual Sounding Reference Signal (SRS) transmission or a reference SRS transmission. For class 1 PHR, there are two types of PUSCH transmissions: DG (DCI scheduling grant) PUSCH and CG PUSCH. DG PUSCH is dynamically scheduled by the gNB and CG PUSCH is semi-statically configured by the gNB. Further, the gNB may semi-statically configure a high priority or a low priority for each CG PUSCH.

In Carrier Aggregation (CA) or Dual Connectivity (DC) scenarios, once PHR is triggered, the UE will feed back one or more class 1 PHR of active serving cells in PUSCH. For each active serving cell, the actual or virtual PHR is determined by the UE and fed back to the gNB. For the active serving cell, if multiple CG PUSCHs overlap in the time domain, the CG PUSCHs carrying the PHR are defined such that the UE and the gNB have the same understanding of the PHR.

The UE may feed back the PHR to the base station in a PHR Media Access Control (MAC) Control Element (CE). And if the terminal does not support a plurality of cells, the terminal feeds back the PHR of a Single cell in a Single Entry PHR MAC CE. If the terminal supports Multiple cells, such as in a CA or DC scenario, the terminal feeds back PHR to the base station in a Multiple Entry PHR MAC CE. In addition to the PHR value, the attribute of each PHR value (i.e., whether the PHR value is an actual PHR or a virtual PHR) is also indicated in the PHR MAC CE.

Fig. 5 is a schematic diagram of an example UE 500. Fig. 5 has the time domain as the horizontal axis. UE 500 supports at least two uplink serving cells: serving cell 1505 and serving cell 2506. In the serving cell 1505, uplink transmission in the PUSCH 1501 is scheduled by the DCI 504. In the serving cell 2506, the CG PUSCH1502 and CG PUSCH 2503 are semi-statically configured by the gNB, and the gNB also configures the priorities of the CG PUSCH1502 and CG PUSCH 2503. CG PUSCH1502 is configured to be high priority and CG PUSCH 2503 is configured to be low priority, such that CG PUSCH1502 and CG PUSCH 2503 are at different priorities. The time domain resources allocated to CG PUSCH1502 and CG PUSCH 2503 overlap in some time units, which may be OFDM symbols, micro-slots, or slots. Whether the UE transmits uplink data in the CG PUSCH1502 is determined based on the data arrival, and the data here may be the UL-SCH or others.

After PHR is triggered at point 510, UE 500 receives DCI 504 scheduling PUSCH 1501 in serving cell 1505, so UE 500 determines to feed back PHR for serving cell 1505 and serving cell 2506. A corresponding PHR MAC CE is prepared by the UE 500, and a type 1 PHR for the serving cell 1505 and a type 1 PHR for the serving cell 2506 are loaded in a PHR Medium Access Control (MAC) Control Element (CE). In addition to the PHR value, the attribute of each PHR value (i.e., whether the PHR value is an actual PHR or a virtual PHR) is also indicated in the PHR MAC CE.

The PHR MAC CE is carried in PUSCH1 of serving cell 1505. For serving cell 1505, the PHR is calculated based on the actual PUSCH 1501 transmission. For the serving cell 2506, the PHR may be determined based on at least one of: 1) referring to the priorities configured by the gNB for CG PUSCH1502 and CG PUSCH 2503, UE 500 calculates the actual PHR based on which CG PUSCH has the high priority or the highest priority; 2) referring to the priorities configured by the gNB for CG PUSCHs 1502 and 2503, the UE 500 calculates a virtual PHR based on which CG PUSCH has a high priority or a highest priority; 3) referring to the time domain positions of CG PUSCH1502 and CG PUSCH 2503 configured by the gNB, UE 500 calculates the actual PHR based on which CG PUSCH is the first in the time domain. As shown in fig. 5, the starting time unit (e.g., OFDM symbol, micro-slot, slot) of CG PUSCH1502 is earlier than CG PUSCH 2503, so CG PUSCH1502 is the first PUSCH and CG PUSCH2 is the second PUSCH; 4) referring to the time domain locations of CG PUSCH1 and CG PUSCH2 configured by the gNB, UE 500 calculates the virtual PHR based on which CG PUSCH is the first in the time domain. As shown in fig. 5, the starting time unit (e.g., OFDM symbol, micro-slot, slot) of the CG PUSCH1502 is earlier than the CG PUSCH 2503, so the CG PUSCH1502 is the first PUSCH and the CG PUSCH 2503 is the second PUSCH.

Fig. 6 is a schematic diagram of an example UE 600. Fig. 6 has the time domain as the horizontal axis. UE 600 supports at least two uplink serving cells: serving cell 1605 and serving cell 2606. In the serving cell 1605, uplink transmission in the PUSCH 1601 is scheduled by the DCI 604. In the serving cell 2606, CG PUSCH 1602 and CG PUSCH 2603 are semi-statically configured by the gNB, and the gNB also configures priorities of CG PUSCH 1602 and CG PUSCH 2603. CG PUSCH 1602 is configured as high priority and CG PUSCH 2603 is configured as low priority, such that CG PUSCH 1602 and CG PUSCH 2603 are at different priorities. The time domain resources allocated for CG PUSCH 1602 and CG PUSCH 2603 overlap in some time units, which may be OFDM symbols, micro-slots, or slots. Whether the UE transmits uplink data in the CG PUSCH 1602 is determined based on data arrival, and the data here may be UL-SCH or the like.

After PHR is triggered at point 610, UE 600 receives DCI 604 scheduling PUSCH 1601 in serving cell 1605, so UE 600 determines to feed back PHR of serving cell 1605 and serving cell 2606. The corresponding PHR MAC CE is prepared by the UE 600, and the type 1 PHR for the serving cell 1605 and the type 1 PHR for the serving cell 2606 are loaded into a PHR Medium Access Control (MAC) Control Element (CE). In addition to the PHR value, the attribute of each PHR value (i.e., whether the PHR value is an actual PHR or a virtual PHR) is also indicated in the PHR MAC CE.

The PHR MAC CE is carried in the PUSCH 1601 in the serving cell 1605. For the serving cell 1605, the PHR is calculated based on the actual PUSCH 1601 transmission.

For serving cell 2606, CG PUSCH 1602 is configured by the gNB as low priority and CG PUSCH 2603 is configured by the gNB as low priority. In the timeline as shown in fig. 6, PHR is triggered at 610(t0), DCI 604 is received by UE 600 at point 640(t3), low priority data arrives at the PHY layer from higher layers at point 620(t1), and high priority data arrives at the PHY layer from higher layers at point 630(t 2). Low priority data should be loaded into CG PUSCH 1602 and high priority data should be loaded into CG PUSCH 2603. Both 620 and 630 precede 640. Due to the overlap between the time domain resource allocations of CG PUSCH 1602 and CG PUSCH 2603, there are three possibilities for the transmission of CG PUSCH 1602 and CG PUSCH 2603: 1) UE 600 transmits both CG PUSCH 1602 and CG PUSCH 2603; 2) the UE 600 does not transmit any of the CG PUSCH 1602 and CG PUSCH 2603; 3) UE 600 transmits one of CG PUSCH 1602 and CG PUSCH 2603.

The method for determining the PHR for the serving cell 2606 by the UE 600 depends on at least one of the following possibilities: 1) referring to the priorities configured by the gNB for CG PUSCHs 1602 and 2603, UE 600 calculates the actual PHR based on which CG PUSCH has the high or highest priority; 2) referring to the priorities configured by the gNB for CG PUSCHs 1602 and CG PUSCHs 2603, the UE 600 calculates a virtual PHR based on which CG PUSCH has a high priority or a highest priority; 3) the UE 600 determines the actual PHR based on which CG-PUSCH is transmitted to transmit data. If CG PUSCH 1602 is transmitted to transmit data, UE 600 determines the actual PHR based on CG PUSCH 1602. If CG PUSCH 2603 is transmitted to transmit data, UE 600 determines an actual PHR based on CG PUSCH 2603.

Fig. 7 is a schematic diagram of an example UE 700. Fig. 7 has the time domain as the horizontal axis. The UE 700 supports at least two uplink serving cells: serving cell 1705 and serving cell 2706. In the serving cell 1705, uplink transmission in the PUSCH 1701 is scheduled by the DCI 704. In the serving cell 2706, CG PUSCH 1702 and CG PUSCH 2703 are semi-statically configured by the gNB, and the gNB also configures the priorities of CG PUSCH 1702 and CG PUSCH 2703. CG PUSCH 1702 is configured to be high priority and CG PUSCH 2703 is configured to be low priority, such that CG PUSCH 1702 and CG PUSCH 2703 are at different priorities. The time domain resources allocated for CG PUSCH 1702 and CG PUSCH 2703 overlap in some time units, which may be OFDM symbols, micro-slots, or slots. Whether the UE transmits uplink data in CG PUSCH1 is determined based on data arrival, and the data here may be UL-SCH or the like.

After the PHR is triggered at point 710, the UE 700 receives the DCI 704 scheduling the PUSCH 1701 in the serving cell 1705, and thus the UE 700 determines to feed back the PHR of the serving cell 1705 and the serving cell 2706. The corresponding PHR MAC CE is prepared by the UE 700, and the type 1 PHR for the serving cell 1705 and the type 1 PHR for the serving cell 2706 are loaded in a PHR Medium Access Control (MAC) Control Element (CE). In addition to the PHR value, the attribute of each PHR value (i.e., whether the PHR value is an actual PHR or a virtual PHR) is also indicated in the PHR MAC CE.

The PHR MAC CE is carried in the PUSCH 1701 in the serving cell 1705. For the serving cell 1705, the PHR is calculated based on the actual PUSCH 1701 transmission.

For serving cell 2706, CG PUSCH 1702 is configured by gNB to low priority and CG PUSCH 2703 is configured by gNB to low priority. In the time axis as shown in fig. 7, PHR is triggered at 710(t0), DCI 704 is received by UE 700 at 740(t3), low priority data arrives at PHY layer from higher layers at 720(t1), and high priority data arrives at PHY layer from higher layers at 730(t 2). 720 before 740, and 730 after 740. Low priority data should be loaded into CG PUSCH 1702 and high priority data should be loaded into CG PUSCH 2703. For the serving cell 2706, the PHR may be determined based on at least one of: 1) based on the CG PUSCH whose data arrival time (720 or 730) is before the DCI reception time 740. As shown in fig. 7, 720 precedes 740, so UE 700 determines the PHR based on CG PUSCH 1702. In this example, if UE 700 transmits data in CG PUSCH 1702, the UE determines the actual PHR based on CG PUSCH 1. If the UE is not transmitting data in CG PUSCH1, the UE determines a virtual PHR; 2) CG PUSCH based on its data arrival time (720 or 730) before DCI reception time 740. As shown in fig. 7, 720 precedes 740, so UE 700 determines the PHR based on CG PUSCH 1702. In this example, regardless of whether there is data transmitted in CG PUSCH 1702, UE 700 always determines the actual PHR; 3) CG PUSCH based on its data arrival time (720 or 730) before DCI reception time 740. As shown in fig. 7, 720 precedes 740, so UE 700 determines the PHR based on CG PUSCH 1702. In this example, the UE 700 always determines the virtual PHR regardless of whether there is data transmitted in the CG PUSCH 1702.

In fig. 5, 6 and 7, PUSCH1(501, 601 or 701) in serving cell 1(505, 605 or 705) may also be a CG PUSCH. If PUSCH1 in serving cell 1 is a CG PUSCH, t3(640 or 740) may be a time when the UE (500, 600 or 700) determines to feedback PHR in PUSCH 1.

In a first method relating to conditional definition of UL grant transmission after UL CI, in response to determining that a starting symbol of a PDCCH carrying a UL grant is located after an ending symbol of a PDCCH carrying a UL CI by a time interval equal to or greater than a predefined value, a UE may be scheduled by the UL grant for PUSCH 2. As shown in fig. 5, in case that the resource indicated by the UL CI overlaps with a CG resource of the UE (e.g., a PUSCH resource configured by RRC signaling such as configuredGrantConfig), a gap between an end position of a PDCCH carrying the UL CI and a start position of a PDCCH carrying a UL grant of PUSCH2 should be not less than a predefined value (e.g., X1). In other words, the network (e.g., one or more base stations) transmits the UL grant for scheduling PUSCH2 to the UE in response to determining that the UL grant is a predefined time interval after the end of the PDCCH carrying the UL CI. The value of X1 is configured through RRC signaling or provided in the specification. Alternatively, in response to determining that the resource indicated by the UL CI does not overlap with the CG resource of the UE, the UE will not be de-operated, so the UE can receive a UL grant whose ending symbol is no earlier than the first symbol of the PDCCH carrying the UL CI without waiting for the predefined time gap.

Fig. 5 is a schematic diagram illustrating an example RUR 800 according to a first method. Fig. 8 has a time domain as a horizontal axis and a frequency (e.g., bandwidth, active uplink bandwidth portion (BWP), carrier, etc.) as a vertical axis. Referring to FIGS. 1-5, the RUR 800 is an example of the RUR 202. UL grant 802 is an example of UL grant 124. UL CI 802 is an example of UL CI 201. The RUR 300 is shown as a rectangle defined by a dashed line. As shown in fig. 8, the cancelled resource 805 indicated by UL CI 801 overlaps with CG resource 804. PUSCH 2803 corresponding to UL grant 802 can be scheduled because UL grant 802 is located X1 symbols after UL CI 801 in time.

In a second approach related to the conditionality definition of UL grant transmission after UL CI, in response to determining that the first symbol of the PDCCH carrying the UL grant is located after the end symbol of the PDCCH carrying the UL CI by a time interval equal to or greater than a predefined value, the UE may be scheduled by the UL grant for a PUSCH (e.g., PUSCH 2). In case the resource indicated by the UL CI overlaps with the PUSCH resource of the UE, which is configured by RRC signaling (e.g., CG resource) or scheduled by the UL grant with an end symbol earlier than the first symbol of the UL CI, the gap between the end position of the PDCCH carrying the UL CI and the start position of the PDCCH carrying the UL grant for PUSCH2 should be no less than a predefined value (e.g., X1). In other words, the network (e.g., one or more base stations) transmits the UL grant for scheduling PUSCH2 to the UE in response to determining that the UL grant is a predefined time interval after the end of the PDCCH carrying the UL CI. The value of X1 is configured through RRC signaling or provided in the specification. Alternatively, in response to determining that the resource indicated by the UL CI does not overlap with the PUSCH resource of the UE configured by RRC signaling or scheduled by the UL grant, there will be no cancellation operation for the UE, so the UE can receive a UL grant whose end symbol is no earlier than the first symbol of the PDCCH carrying the UL CI without being limited by the predefined time interval.

In a third approach related to the conditionality definition of UL grant transmission after an UL CI, in case the resource indicated by the first UL CI (e.g., UL CI1) overlaps with the CG resource of the UE (e.g., PUSCH resource configured by RRC signaling such as configuredrgrantconfig), in response to determining that the end symbol of the PDCCH carrying the UL grant is not earlier in time than the first symbol of the PDCCH carrying the next UL CI, the UE may be scheduled by this UL grant for another PUSCH. In other words, the network (e.g., one or more base stations) transmits the UL grant for scheduling PUSCH2 to the UE in response to determining that the UL grant occurs after another UL CI (later than the UL CI indicating overlapping resources). In response to determining that the end symbol of the PDCCH carrying the UL grant is earlier in time than the first symbol of the PDCCH carrying the next UL CI (e.g., UL CI2) after UL CI1, the UE will not receive the PDCCH carrying the UL grant. Alternatively, in response to determining that the resource indicated by UL CI1 does not overlap with the CG resource of the UE, there will be no cancellation operation for the UE, so the UE may receive a UL grant whose ending symbol is no earlier than the first symbol of the PDCCH carrying the UL CI.

Fig. 9 is a schematic diagram illustrating an example RUR 900 according to a third method. Fig. 9 has a time domain as a horizontal axis and a frequency (e.g., bandwidth, active uplink bandwidth portion (BWP), carrier, etc.) as a vertical axis. Referring to FIGS. 1-6, the RUR 900 is an example of the RUR 202. UL grants 902 and 904 are examples of UL grants 124. UL CI 1902 and UL CL 2904 are examples of UL CI 201. The RUR 900 is shown as a rectangle defined by a dashed line. As shown in fig. 9, in the case where CG resource 905 overlaps with cancel resource 906 indicated by UL CI 1901, UL grant 902 after UL CI 1901 but earlier in time than UL CI 2903 will not be allowed to be transmitted. However, UL grant 904, which is subsequent in time to UL CI 1901 and UL CI 2903, will be allowed to be transmitted.

In a fourth method related to the conditional definition of UL grant transmission after a UL CI, in case that a resource indicated by a first UL CI (e.g., UL CI1) overlaps with a PUSCH resource of a UE configured by RRC signaling or scheduled by a UL grant, while an end symbol of the UL grant is earlier than a first symbol of the UL CI, the UE may be scheduled by the UL grant for another PUSCH in response to determining that the end symbol of the PDCCH carrying the UL grant is not earlier than the first symbol of the PDCCH carrying the next UL CI (e.g., UL CI 2). In response to determining that the end symbol of the PDCCH carrying the UL grant is earlier than the first symbol of the PDCCH carrying UL CI2, the UE will not receive the PDCCH carrying the UL grant. In other words, the network (e.g., one or more base stations) may transmit the UL grant for scheduling PUSCH2 to the UE in response to determining that the UL grant occurs after another UL CI (later than the UL CI indicating overlapping resources). Alternatively, in response to determining that the resource indicated by UL CI1 does not overlap with the PUSCH resource of the UE configured by RRC signaling or scheduled by the UL grant, there will be no cancellation operation for the UE so the UE may receive a UL grant whose ending symbol is no earlier than the first symbol of the PDCCH carrying the UL CI.

Fig. 10 is a schematic diagram illustrating an example RUR 1000 according to a fourth method. Fig. 10 has a time domain as a horizontal axis and a frequency (e.g., bandwidth, active uplink bandwidth portion (BWP), carrier, etc.) as a vertical axis. Referring to FIGS. 1-7, RUR 1000 is an example of RUR 202. UL grants 1002 and 1004 are examples of UL grant 124. UL CI 11001 and UL CL 21003 are examples of UL CI 201. The RUR 1000 is shown as a rectangle defined by a dashed line. As shown in fig. 10, in case PUSCH 1005 scheduled by the signaling configuration or by another UL grant overlaps with cancelled resource 1006 indicated by UL CI 11001, UL grant 1002 after UL CI 11001 but earlier in time than UL CI 21003 will not be allowed to be transmitted. However, UL grant 1004, which is temporally subsequent to UL CI 11001 and UL CI 21003, will be allowed to be transmitted.

In a fifth method related to conditional location of a PUSCH scheduled by an UL grant following an UL CI, transmission of the UL grant to a UE is allowed in response to determining that a PUSCH scheduled by the UL grant (e.g., PUSCH2) begins later than an end symbol of a first PUSCH resource of the UE configured by RRC signaling or scheduled by another, different UL grant. The end symbol of another different UL grant is earlier than the first symbol of the PDCCH carrying the UL CI. In other words, the network (e.g., one or more base stations) transmits the UL grant to the UE in response to determining that the PUSCH2 scheduled by the UL grant does not overlap with an earlier PUSCH.

Fig. 11 is a schematic diagram illustrating an example RUR 1100 according to a fifth method. Fig. 11 has time domain as horizontal axis and frequency (e.g., bandwidth, active uplink bandwidth portion (BWP), carrier, etc.) as vertical axis. Referring to FIGS. 1-8, RUR 1100 is an example of RUR 202. UL grant 1102 is an example of UL grant 124. UL C11101 is an example of UL CI 201. The RUR 1100 is shown as a rectangle defined by a dashed line. As shown in fig. 11, in case PUSCH 1104, either configured by signaling or scheduled by another UL grant, overlaps with cancelled resources 1105 indicated by UL CI 1101, UL grant 1102 associated with PUSCH 21103 is scheduled since PUSCH 21103 starts after end symbol 1106 of PUSCH 1104.

In a sixth method related to conditional location of a PUSCH scheduled by a UL grant after a UL CI, transmission of the UL grant to a UE is allowed in response to determining that a PUSCH scheduled by the UL grant (e.g., PUSCH2) does not overlap with resources indicated by the UL CI. Thus, when PUSCH1 initially overlaps with the resource indicated by the UL CI, PUSCH2 begins later than the end of the end symbol of the first PUSCH resource (PUSCH1) at a UE configured by RRC signaling or scheduled by a different UL grant (whose end symbol is earlier than the first symbol of the UL CI). In other words, the network (e.g., one or more base stations) transmits the UL grant to the UE in response to determining that PUSCH2 scheduled by the UL grant does not overlap with the cancelled resources indicated by UL Ci.

Fig. 12 is a schematic diagram illustrating an example RUR 1200 according to a sixth method. Fig. 12 has time domain as horizontal axis and frequency (e.g., bandwidth, active uplink bandwidth portion (BWP), carrier, etc.) as vertical axis. Referring to FIGS. 1-9, the RUR 1200 is an example of the RUR 202. UL grant 1202 is an example of UL grant 124. UL CI 1201 is an example of UL CI 201. The RUR 1200 is shown as a rectangle defined by a dashed line. As shown in fig. 12, in case PUSCH 1204, either configured by signaling or scheduled by another UL grant, overlaps with cancelled resources 1205 indicated by UL CI 1201, UL grant 1202 associated with PUSCH 21203 may be transmitted since PUSCH 21203 starts after end symbol 1206 of PUSCH 1204. Further, PUSCH 21203 does not overlap with the second cancelled resource 1207 indicated by UL CI 1201.

In a seventh approach related to conditional location of a PUSCH scheduled by a UL grant after a UL CI, transmission of the UL grant to a UE is allowed in response to determining that a PUSCH (e.g., PUSCH2) scheduled by the UL grant does not overlap with resources indicated by an earlier UL CI. In this case, the network (e.g., one or more base stations) transmits the UL grant to the UE in response to determining that PUSCH2 scheduled by the UL grant does not overlap with the cancelled resources indicated by the UL CI.

Fig. 13 is a schematic diagram illustrating an example RUR 1300 according to a seventh method. Fig. 13 has a time domain as a horizontal axis and a frequency (e.g., bandwidth, active uplink bandwidth portion (BWP), carrier, etc.) as a vertical axis. Referring to FIGS. 1-10, the RUR 1300 is an example of the RUR 202. UL grant 1302 is an example of UL grant 124. UL CI 1301 is an example of UL CI 201. The RUR 1300 is shown as a rectangle defined by a dashed line. As shown in fig. 13, in case that PUSCH 1304, configured by signaling or scheduled by another UL grant, overlaps with the first cancelled resource 1305 indicated by UL CI 1301, scheduling of UL grant 1302 associated with PUSCH 21303 is allowed, since PUSCH 21303 does not overlap with the first cancelled resource 1305 indicated by UL CI 1301. Further, PUSCH 21303 does not overlap with the second cancelled resource 1307 indicated by UL CI 1301.

In an eighth method related to conditional location of a PUSCH scheduled by a UL grant after a UL CI, transmission of the UL grant to a UE is allowed in response to determining that a second PUSCH (e.g., PUSCH2) scheduled by the UL grant does not begin earlier than a first symbol after a first predetermined point in time (e.g., a). Position of predetermined point in timeIs defined as the time interval after the end symbol of the UL CI. The time interval (e.g., X1) is determined as the sum of the first time interval and the second time interval. The first time interval is indicated as T _proc，2 A, and a second time interval is indicated as T _proc，2 B + d2 or T _proc，2 B. First time interval (T) _proc，2 A) Is defined as a time interval for decoding UL CI and canceling PUSCH, and a second time interval (T) _proc，2 B + d2 or T _proc，2 B) Is defined as the time interval for decoding the UL grant and preparing the PUSCH 2. In other words, the network (e.g., one or more base stations) transmits the UL grant to the UE in response to determining that PUSCH2 scheduled by the UL grant begins a time interval after the end symbol of the UL CI that is at least equal to the time it takes to decode the UL CI, cancel the PUSCH, decode the UL grant, and prepare the second PUSCH.

The value of each Tproc, 2A, Tproc, 2B, and d2 is related to the UE capability and subcarrier spacing (SCS) and may be defined in the specification, or configured by RRC signaling, or reported by the UE. Further, the values of Tproc, 2A, Tproc, 2B, and d2 may be defined according to the same SCS or different SCS. For example, if T is determined using SCS of PUSCH2 _proc，2 A、T _proc，2 Values of B and d2, then T _proc，2 The value of A will be equal to T _proc，2 The value of B. In another example, T is determined based on the lesser of the SCS configuration of the PDCCH and the minimum SCS configuration provided in the SCS configuration of the frequencyinfoal or the SCS configuration provided in the SCS-specific CarrierList of freqyinfoal-SIBs _proc，2 Value of A, and T is determined based on SCS of PUSCH2 _proc，2 The value of B.

Fig. 14 is a schematic diagram illustrating an example RUR 1400 according to an eighth method. Fig. 14 has a time domain as a horizontal axis and a frequency (e.g., bandwidth, active uplink bandwidth portion (BWP), carrier, etc.) as a vertical axis. Referring to FIGS. 1-11, the RUR 1400 is an example of the RUR 202. UL grant 1402 is an example of UL grant 124. UL CI 1401 is an example of UL CI 201. As shown in fig. 14, in case that PUSCH 1404 scheduled by signaling configuration or by another UL grant overlaps with cancelled resource 1405 indicated by UL CI 1401, transmission is allowed with PUSCH 21403 associated UL grant 1402 since PUSCH 21403 starts no earlier than point a of X1 symbols after the end point determined to be UL CI 1401. As shown in FIG. 14, the value of X1 is determined as T _proc，2 A and T _proc，2 The sum of B + d2, or determined as T _proc，2 A and T _proc，2 And (B) the sum of the two.

In a ninth method related to conditional location of a PUSCH scheduled by a UL grant after a UL CI, transmission of the UL grant to a UE is allowed in response to determining that a second PUSCH (e.g., PUSCH2) scheduled by the UL grant does not begin earlier than a first symbol after a second predetermined point in time (e.g., B). As shown in fig. 12, the location of the second predetermined time point is defined as a time interval (e.g., X2) after the start of the cancelled resource indicated by the UL CI. The location of the second predetermined point in time may also be defined as a time interval after the start of the cancelled portion (or cancellation portion) of the first PUSCH resource, either configured by RRC signaling or scheduled by the UL grant (with the end symbol earlier than the first symbol of the UL CI). The time interval is equal to the third time interval. A third time interval (e.g., T) _proc，2 B) Is defined as the time interval for decoding the UL grant and preparing the PUSCH 2. In other words, the network (e.g., one or more base stations) transmits the UL grant to the UE in response to determining that the PUSCH2 scheduled by the UL grant begins a time interval after the cancelled resource or cancelled portion (or cancellation portion) of the first PUSCH resource begins, which is equal to the time it takes to decode the UL grant and prepare the second PUSCH. The value of the time interval is related to the UE capability and SCS and may be defined in the specification or configured by RRC signaling. For example, the value of the third time interval may be defined according to the SCS of PUSCH2, the SCS of UL grant scheduling PUSCH2, or the smaller of the SCS of PUSCH2 and the SCS of UL grant scheduling PUSCH 2.

Fig. 15 is a schematic diagram illustrating an example RUR 1500 according to a ninth method. Fig. 15 has a time domain as a horizontal axis and a frequency (e.g., bandwidth, active uplink bandwidth portion (BWP), carrier, etc.) as a vertical axis. Referring to FIGS. 1-12, RUR 1500 is an example of RUR 202. UL grant 1502 is an example of UL grant 154. UL CI 1501 is an example of UL CI 201. As shown in fig. 15, the message is sent to the userHaving PUSCH 1504 configured or scheduled by another UL grant overlap with cancelled resources 1505 indicated by UL CI 1501, UL grant 1502 associated with PUSCH 21503 is scheduled because PUSCH 21503 starts after point B, which is determined as X2 symbols after the first symbol of cancelled resources 1505 or the cancelled portion (or cancelled portion) of PUSCH 1504. As shown in FIG. 15, the value of X2 is determined as T _proc，2 The value of B.

In a tenth method related to conditional location of a PUSCH scheduled by an UL grant after an UL CI, transmission of the UL grant to the UE is allowed in response to determining that a PUSCH scheduled by the UL grant (e.g., PUSCH2) begins no earlier in time than a first symbol after a third predetermined point (e.g., C). The location of the third predetermined point in time is defined as a time interval (e.g., X3) after the end symbol of the previous PUSCH resource, which is configured by RRC signaling or scheduled by UL grant (whose end symbol is earlier than the first symbol of UL CI). The time interval is equal to the third time interval (e.g., T) _proc，2 B) Which is defined above as the time interval for decoding the UL grant and preparing the PUSCH 2. In other words, the network (e.g., one or more base stations) transmits the UL grant to the UE in response to determining that the PUSCH2 scheduled by the UL grant begins a time interval after the first PUSCH (which is equal to the time it takes to decode the UL grant and prepare the second PUSCH). The value of the time interval is related to the UE capability and SCS and may be defined in the specification or configured by RRC signaling. For example, the value of the time interval may be defined according to the SCS of PUSCH2, the SCS of UL grant scheduling PUSCH2, or the lesser of the SCS of PUSCH2 and the SCS of UL grant scheduling PUSCH 2.

Fig. 16 is a schematic diagram illustrating an example RUR 1600 according to a tenth method. Fig. 16 has a time domain as a horizontal axis and a frequency (e.g., bandwidth, active uplink bandwidth portion (BWP), carrier, etc.) as a vertical axis. Referring to FIGS. 1-13, RUR 1600 is an example of RUR 202. UL grant 1602 is an example of UL grant 124. UL CI 1601 is an example of UL CI 201. As shown in fig. 16, PUSCH 1604, which is configured by signaling or scheduled by another UL grant, overlaps with PUSCH 21603 in case of cancelled resource 1603 indicated by UL CI 1601The associated UL grant 1602 is scheduled because PUSCH 21603 starts after point C, which is determined to be X3 symbols after the end symbol of PUSCH 1604. As shown in FIG. 16, the value of X3 is determined as T _proc，2 The value of B.

In an eleventh method related to conditional location of a PUSCH scheduled by a UL grant after a UL CI, transmission of the UL grant to a UE is allowed in response to determining that a second PUSCH (e.g., PUSCH2) scheduled by the UL grant does not begin earlier than a first symbol after a first predetermined point in time (e.g., a). PUSCH2 does not overlap with the previous PUSCH resource scheduled by RRC signaling configuration or by a UL grant whose ending symbol is earlier than the first symbol of the UL CI. The first predetermined time point (e.g., a) is the same as the time point defined in the eighth method.

Fig. 17 is a schematic diagram illustrating an example RUR 1700 according to an eighth method. Fig. 17 has a time domain as a horizontal axis and a frequency (e.g., bandwidth, active uplink bandwidth portion (BWP), carrier, etc.) as a vertical axis. Referring to FIGS. 1-16, the RUR 1700 is an example of the RUR 202. UL grant 1702 is an example of UL grant 124. UL CI 1701 is an example of UL CI 201. The RUR 1700 is shown as a rectangle defined by a dashed line. As shown in fig. 17, in case of PUSCH 1704 scheduled by signaling configuration or by another UL grant overlapping cancelled resources 1705 indicated by UL CI 1701, both PUSCH 21703 between point a and point D and PUSCH 21706 after point E may be scheduled by UL grant 1702. Point D is determined as the starting point of the previous PUSCH resource, which is configured by RRC signaling, or scheduled by a UL grant whose ending symbol is earlier than the first symbol of the UL CI. Point E is determined as the end point of the previous PUSCH resource, which is configured by RRC signaling or scheduled by a UL grant whose end symbol is earlier than the first symbol of the UL CI. The point a is determined in the same manner as the eighth method. As shown in FIG. 17, the value of X1 is determined as T _proc，2 A and T _proc，2 B + d2, or is determined as T _proc，2 A and T _proc，2 And (B) the sum of the two.

In some embodiments, one of the conditions (e.g., one of the first, second, third, fourth, fifth, seventh, eighth, ninth, tenth, and eleventh methods described herein) needs to be met in order to schedule the UL grant. In other embodiments, two or more conditions (e.g., one of the first, second, third, fourth, fifth, seventh, eighth, ninth, tenth, and eleventh methods described herein) should be met simultaneously for transmission of the UL grant.

Fig. 18A is a schematic diagram illustrating a method 1800a for downlink control information transmission, in accordance with some embodiments. Referring to fig. 1-14A, a method 1800a is performed by a UE.

At 1810, the UE determines that the first resource indicated by the uplink cancellation information overlaps with the second resource. At 1820, the UE receives an UL grant from the network scheduling a third resource. The end symbol of the first downlink control channel (first PDCCH) carrying the UL grant is no earlier than the first symbol of the second downlink control channel carrying the uplink cancellation information. In some examples, the uplink cancellation information includes an UL CI. In some examples, the first, second, and third resources (e.g., PUSCH2) are uplink resources.

In some embodiments related to the first method, the second resource is a CG resource configured by the network through signaling (e.g., RRC signaling, etc.). The time interval (e.g., gap) between the end position of the second downlink control channel carrying the uplink cancellation information and the start position of the first downlink control channel carrying the UL grant is not less than a predetermined threshold. In some examples, the end position of the second downlink control channel carrying the uplink cancellation information is an end of an end symbol of the second downlink control channel carrying the uplink cancellation information. The starting position of the first downlink control channel carrying the UL grant is the start of the first symbol of the first downlink control channel carrying the UL grant. The end symbol of the second downlink control channel is the latest symbol of all symbols of the second downlink control channel. The first symbol of the first downlink control channel is the earliest symbol of all symbols of the first downlink control channel. The predetermined threshold is equal to the value X1. The value of X1 is configured by RRC signaling or provided in the specification.

In some embodiments related to the second method, the second resource is configured by the network communications through signaling (e.g., RRC signaling, etc.), or is scheduled by the network through another UL grant. The time interval (e.g., gap) between the end position of the second downlink control channel carrying the uplink cancellation information and the start position of the first downlink control channel carrying the UL grant is not less than a predetermined threshold. The end symbol of the other UL grant is earlier than the first symbol of the second downlink control channel carrying the uplink cancellation information. In some examples, the end position of the second downlink control channel carrying the uplink cancellation information is an end point of an end symbol of the second downlink control channel carrying the uplink cancellation information. The first downlink control channel start carrying the UL grant is the starting point of the first symbol of the first downlink control channel carrying the UL grant. The end symbol of each of the second downlink control channel and the further UL grant is the latest symbol of all symbols of the second downlink control channel and the further UL grant, respectively. The first symbol of each of the first and second downlink control channels is the earliest symbol of all symbols of the first and second downlink control channels, respectively. The predetermined threshold is equal to the value X1. The value of X1 is configured by RRC signaling or provided in the specification.

In some embodiments related to the third method, the second resource is a CG resource configured by the network through signaling (e.g., RRC signaling, etc.). The UL grant is carried on a first downlink control channel having an end symbol that is no earlier than the first symbol of a third downlink control channel carrying subsequent uplink cancellation information (next UL CI). The subsequent uplink cancellation information is received after the uplink cancellation information is received. In some examples, the end symbol of the UL grant carried on the first downlink control channel is the latest symbol of all symbols of the UL grant carried on the first downlink control channel. The first symbol of the third downlink control channel carrying the subsequent uplink cancellation information is the earliest of all symbols of the third downlink control channel carrying the subsequent uplink cancellation information.

In some embodiments related to the fourth method, the second resource is configured by the network through signaling (e.g., RRC signaling, etc.) or scheduled by the network through another UL grant. The UL grant is carried on a first downlink control channel with an end symbol that is no earlier than the first symbol of a third downlink control channel carrying subsequent uplink cancellation information (next UL CI). The subsequent uplink cancellation information is received after the uplink cancellation information is received. The end symbol of the further UL grant is earlier than the first symbol of the second downlink control channel carrying the uplink cancellation information. In some examples, the end symbol of the UL grant and the another UL grant carried on the first downlink control channel is the latest symbol of all symbols of the UL grant and the another UL grant carried on the first downlink control channel, respectively. The first symbol of the third downlink control channel carrying the subsequent uplink cancellation information and the second downlink control channel carrying the uplink cancellation information is the earliest of all symbols of the third downlink control channel carrying the subsequent uplink cancellation information and the second downlink control channel carrying the uplink cancellation information, respectively.

In some embodiments related to the fifth method, the third resource starts later than an end symbol of the second resource. The second resource is configured by the network through signaling (e.g., RRC signaling, etc.) or scheduled by the network through another UL grant. The end symbol of the other UL grant is earlier than the first symbol of the second downlink control channel carrying the uplink cancellation information. In some examples, the end symbol of the second resource and the other UL grant is the latest symbol of all symbols of the second resource and the other UL grant, respectively. The first symbol of the second downlink control channel is the earliest of all symbols of a third downlink control channel carrying the second downlink control channel.

In some embodiments related to the sixth method, the third resource does not overlap the first resource. The third resource begins later than an end symbol of the UL resource, which is configured by the network through signaling (e.g., RRC signaling, etc.) or scheduled by the network through another UL grant. In some examples, the end symbol of the UL resource is the latest symbol of all symbols in the UL resource.

In some embodiments related to the seventh method, the third resource does not overlap with the first resource, and the third resource starts no earlier than a predefined point in time. In some examples, the predefined point in time is an end of the first resource. The end position of the first resource is an end point of an end symbol of the first resource. The end symbol of the first resource is the latest symbol of all symbols of the first resource.

In some embodiments related to the eighth method, the third resource starts no earlier than a predefined point in time. In some examples, the predefined point in time is a position of a certain number of symbols after the end of the uplink cancellation information (UL CI). In some examples, the number of symbols is equal to a sum of the first interval and the second interval. The first interval is indicated as T _proc，2 A, and is defined as the amount of time to decode UL CI and cancel corresponding PUSCH. The second interval is indicated as T _proc，2 B + d2 or T _proc，2 B and is defined as the amount of time to decode the UL grant and prepare the corresponding PUSCH. The end position of the UL CI is an end point of an end symbol of the UL CI. The end symbol of the UL CI is the latest symbol of all symbols in the UL CI.

In some embodiments related to the ninth method, the third resource starts no earlier than a predefined point in time. The predefined point in time is a position a certain number of symbols after the start of the cancelled part of the second resource. In some examples, the number of symbols is equal to the third time interval. The third interval is indicated as T _proc，2 B, and is defined as the amount of time used to decode the UL grant and prepare the corresponding PUSCH. The start of the cancelled portion of the second resource is the starting point of the first symbol of the cancelled portion of the second resource. The cancelled portion of the second resource is a portion of the second resource that overlaps in time and frequency with the first resource indicated by the uplink cancellation information. The second resource is configured by the network through signaling (e.g., RRC signaling, etc.) or scheduled by the network through another UL grant whose ending symbol is earlier than the first symbol of the uplink cancellation information. The cancelled portion of the second resource and the first symbol of the uplink cancellation information are the second resource, respectivelyAnd an earliest symbol of all symbols in the uplink cancellation information. The end symbol of the second resource is the latest symbol of all symbols in the second resource.

In some embodiments related to the tenth method, the third resource starts no earlier than a predefined point in time. The predefined point in time is a position a certain number of symbols after the end of the second resource. In some examples, the number of symbols is equal to the third time interval. The third interval is indicated as T _proc，2 B and is defined as the amount of time to decode the UL grant and prepare the corresponding PUSCH. The second resource is configured by the network through signaling (e.g., RRC signaling, etc.) or scheduled by the network through another UL grant whose ending symbol is earlier than the first symbol of the uplink cancellation information. The end position of the second resource is an end point of an end symbol of the second resource. The ending symbol of the second resource is the latest symbol of all symbols in the second resource. The first symbol of the uplink cancellation information is the earliest of all symbols in the cancelled portion of the uplink cancellation information.

In some embodiments related to the eleventh method, the third resource does not overlap in time with the second resource, and the third resource starts no earlier than the predefined point in time. In some examples, the predefined time point is defined in the same manner as in the eighth method.

Fig. 18B is a schematic diagram illustrating a method 1800B for downlink control information transmission, in accordance with some embodiments. Referring to fig. 1-14B, a method 1800B is performed by a base station.

At 1830, the base station transmits uplink cancellation information to the wireless communication device (e.g., UE) indicating that the first resource overlaps with a second resource of the UE. At 1840, the base station transmits an Uplink (UL) grant scheduling a third resource (e.g., PUSCH2) to the UE. The end symbol of the first downlink control channel (first PDCCH) carrying the UL grant is no earlier than the first symbol of the second downlink control channel carrying the uplink cancellation information. In some examples, the uplink cancellation information includes UL CI. In some examples, the first resource, the second resource, and the third resource are uplink resources.

In some embodiments related to the first method, the second resource is a CG resource configured by the network through signaling (e.g., RRC signaling, etc.). The time interval (e.g., gap) between the end position of the second downlink control channel carrying the uplink cancellation information and the start position of the first downlink control channel carrying the UL grant is not less than a predetermined threshold. In some examples, the end position of the second downlink control channel carrying the uplink cancellation information is an end point of an end symbol of the second downlink control channel carrying the uplink cancellation information. The start of the first downlink control channel carrying the UL grant is the starting point of the first symbol of the first downlink control channel carrying the UL grant. The end symbol of the second downlink control channel is the latest symbol of all symbols of the second downlink control channel. The first symbol of the first downlink control channel is the earliest of all symbols of the first downlink control channel. The predetermined threshold is equal to the value X1. The value of X1 is configured by RRC signaling or provided in the specification.

In some embodiments related to the second method, the second resource is configured by the network via signaling (e.g., RRC signaling, etc.) or is scheduled by the network via another UL grant. The time interval (e.g., gap) between the end position of the second downlink control channel carrying the uplink cancellation information and the start position of the first downlink control channel carrying the UL grant is not less than a predetermined threshold. The end symbol of the other UL grant is earlier than the first symbol of the second downlink control channel carrying the uplink cancellation information. In some examples, the end position of the second downlink control channel carrying the uplink cancellation information is an end point of an end symbol of the second downlink control channel carrying the uplink cancellation information. The start of the first downlink control channel carrying the UL grant is the starting point of the first symbol of the first downlink control channel carrying the UL grant. The end symbol of each of the second downlink control channel and the further UL grant is the latest symbol of all symbols of the second downlink control channel and the further UL grant, respectively. The first symbol of each of the first and second downlink control channels is the earliest symbol of all symbols of the first and second downlink control channels, respectively. The predetermined threshold is equal to the value X1. The value of X1 is configured by RRC signaling or provided in the specification.

In some embodiments related to the third method, the second resource is a CG resource configured by the network through signaling (e.g., RRC signaling, etc.). The UL grant is carried on a first downlink control channel with an end symbol that is no earlier than the first symbol of a third downlink control channel carrying subsequent uplink cancellation information (next UL CI). Subsequent uplink cancellation information is transmitted after receiving the uplink cancellation information. In some examples, the end symbol of the UL grant carried on the first downlink control channel is the latest symbol of all symbols of the UL grant carried on the first downlink control channel. The first symbol of the third downlink control channel carrying the subsequent uplink cancellation information is the earliest of all symbols of the third downlink control channel carrying the subsequent uplink cancellation information.

In some embodiments related to the fourth method, the second resource is configured by the network through signaling (e.g., RRC signaling, etc.) or scheduled by the network through another UL grant. The UL grant is carried on a first downlink control channel with an end symbol that is no earlier than the first symbol of a third downlink control channel carrying subsequent uplink cancellation information (next UL CI). The subsequent uplink cancellation information is transmitted after the uplink cancellation information is transmitted. The end symbol of the further UL grant is earlier than the first symbol of the second downlink control channel carrying the uplink cancellation information. In some examples, the end symbol of the UL grant and the another UL grant carried on the first downlink control channel is the latest symbol of all symbols of the UL grant and the another UL grant carried on the first downlink control channel, respectively. The first symbol of the third downlink control channel carrying the subsequent uplink cancellation information and the second downlink control channel carrying the uplink cancellation information is the earliest of all symbols of the third downlink control channel carrying the subsequent uplink cancellation information and the second downlink control channel carrying the uplink cancellation information, respectively.

In some embodiments related to the fifth method, the third resource begins later than an end symbol of the second resource. The second resource is configured by the network through signaling (e.g., RRC signaling, etc.) or scheduled by the network through another UL grant. The end symbol of the other UL grant is earlier than the first symbol of the second downlink control channel carrying the uplink cancellation information. In some examples, the end symbol of the second resource and the other UL grant is the latest symbol of all symbols of the second resource and the other UL grant, respectively. The first symbol of the second downlink control channel is the earliest of all symbols of a third downlink control channel carrying the second downlink control channel.

In some embodiments related to the sixth method, the third resource does not overlap the first resource. The third resource begins later than the end of the end symbol of the UL resource, which is configured by the network through signaling (e.g., RRC signaling, etc.) or scheduled by the network through another UL grant. In some examples, the end symbol of the UL resource is the latest symbol of all symbols in the UL resource.

In some embodiments related to the eighth method, the third resource starts no earlier than a predefined point in time. In some examples, the predefined point in time is a position of a certain number of symbols after the end of the uplink cancellation information (UL CI). In some examples, the number of symbols is equal to a sum of the first interval and the second interval. The first interval is indicated as T _proc，2 A, and is defined as the amount of time to decode UL CI and cancel corresponding PUSCH. The second interval is indicated as T _proc，2 B + d2 or T _proc，2 B, and is defined as the solutionCode UL grant and amount of time to prepare corresponding PUSCH. The end position of the UL CI is an end point of an end symbol of the UL CI. The end symbol of the UL CI is the latest symbol of all symbols in the UL CI.

In some embodiments related to the ninth method, the third resource starts no earlier than a predefined point in time. The predefined point in time is a position a certain number of symbols after the start of the cancelled part of the second resource. In some examples, the number of symbols is equal to the third time interval. The third interval is indicated as T _proc，2 B and is defined as the amount of time to decode the UL grant and prepare the corresponding PUSCH. The start of the cancelled portion of the second resource is the starting point of the first symbol of the cancelled portion of the second resource. The cancelled portion of the second resource is a portion of the second resource that overlaps in time and frequency with the first resource indicated by the uplink cancellation information. The second resource is configured by the network through signaling (e.g., RRC signaling, etc.) or scheduled by the network through another UL grant whose ending symbol is earlier than the first symbol of the uplink cancellation information. The cancelled portion of the second resource and the first symbol of the uplink cancellation information are the earliest of all symbols in the cancelled portion of the second resource and the uplink cancellation information, respectively. The end symbol of the second resource is the latest symbol of all symbols in the second resource.

In some embodiments related to the tenth method, the third resource starts no earlier than a predefined point in time. The predefined point in time is a position a certain number of symbols after the end of the second resource. In some examples, the number of symbols is equal to the third time interval. The third interval is indicated as T _proc，2 B and is defined as the amount of time to decode the UL grant and prepare the corresponding PUSCH. The second resource is configured by the network through signaling (e.g., RRC signaling, etc.) or scheduled by the network through another UL grant whose ending symbol is earlier than the first symbol of the uplink cancellation information. The end position of the second resource is an end point of an end symbol of the second resource. The end symbol of the second resource is the latest symbol of all symbols in the second resource. The first symbol of the uplink cancellation information is the earliest symbol of all symbols in the cancelled portion of the uplink cancellation information.

Fig. 19A illustrates a block diagram of an example base station 1902, according to some embodiments of the present disclosure. Fig. 15B illustrates a block diagram of an example UE1901, in accordance with some embodiments of the present disclosure. Referring to fig. 1-15B, a UE1901 (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 1902 is an example embodiment of one or more base stations described herein.

The base station 1902 and the UE1901 can include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, the base station 1902 and the UE1901 can be utilized for transmitting (e.g., transmitting and receiving) data symbols in a wireless communication environment, as described supra. For example, base station 1902 may be a base station (e.g., a gNB, eNB, etc.), a server, a node, or any suitable computing device used to implement various network functions.

The base station 1902 includes a transceiver module 1910, an antenna 1912, a processor module 1914, a memory module 1916, and a network communications module 1918. The

modules

1910, 1912, 1914, 1916, and 1918 are operatively coupled together and interconnected by a data communication bus 1920. UE1901 includes a UE transceiver module 1930, a UE antenna 1932, a UE memory module 1934, and a UE processor module 1936.

Modules

1930, 1932, 1934, and 1936 are operatively and interconnected by a data communication bus 1940. The base station 1902 communicates with the UE1901 or another base station over a communication channel, which may be any wireless channel or other medium suitable for data transmission as described herein.

As will be appreciated by one of ordinary skill in the art, the base station 1902 and the UE1901 may also include any number of modules in addition to those shown in fig. 19A and 19B. The various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented as 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.

In accordance with some embodiments, UE transceiver 1930 includes a Radio Frequency (RF) transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 1932. A duplex switch (not shown) may alternately couple the RF transmitter or receiver to the antenna in a time-duplex manner. Similarly, the transceiver 1910 includes an RF transmitter and an RF receiver each having circuitry coupled to an antenna 1912 or an antenna of another base station according to some embodiments. The duplex switch may alternatively couple the RF transmitter or receiver to the antenna 1912 in a time-duplex manner. The operation of the two

transceiver modules

1910 and 1930 can be coordinated in time such that the receiver circuitry is coupled with the antenna 1932 to receive transmissions over a wireless transmission link while the transmitter is coupled with the antenna 1912. In some embodiments, there is tight time synchronization with minimal guard time between changes in duplex direction.

UE transceiver 1930 and transceiver 1910 are configured to communicate over a wireless data communication link and cooperate with a suitably configured RF antenna arrangement 1912/1532 that may support specific wireless communication protocols and modulation schemes. In some demonstrative embodiments, UE transceivers 1910 and transceivers 1910 are configured to support industry standards, such as Long Term Evolution (LTE) and emerging 5G standards. It should be understood, however, that the present disclosure is not necessarily limited to the application of a particular standard and related protocols. Rather, UE transceiver 1930 and base station transceiver 1910 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

Transceiver 1910 and a transceiver of another base station, such as but not limited to transceiver 1910, are configured to communicate over 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 1910 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 1910 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 1902 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 1902 may be an RN, regular, DeNB, or gNB. In some embodiments, the UE1901 may be embodied in various types of user devices, such as mobile phones, smart phones, Personal Digital Assistants (PDAs), tablets, laptops, wearable computing devices, and so forth. The

processor modules

1914 and 1936 may be 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, 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.

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

processor modules

1914 and 1936, respectively, or in any practical combination thereof.

Memory modules

1916 and 1934 may 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

1916 and 1934 may be coupled with the

processor modules

1910 and 1930, respectively, such that the

processor modules

1910 and 1930 may read information from and write information to the

memory modules

1916 and 1934, respectively.

Memory modules

1916 and 1934 may also be integrated into their

respective processor modules

1910 and 1930. In some embodiments, the

memory modules

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

processor modules

1910 and 1930, respectively. The

memory modules

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

processor modules

1910 and 1930, respectively.

The network communications module 1918 generally represents hardware, software, firmware, processing logic, and/or other components of the base station 1902 that enable bidirectional communication between the transceiver 1910 and other network components and communication nodes communicating with the base station 1902. For example, the network communication module 1918 may be configured to support internet or WiMAX traffic. In deployment, without limitation, the network communication module 1918 provides an 802.3 ethernet interface such that the transceiver 1910 can communicate with a conventional ethernet-based computer network. In this manner, the network communication module 1918 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). In some embodiments, the network communications module 1918 includes a fiber optic transmission connection configured to connect the base station 1902 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 that are provided to enable those of ordinary skill in the art to understand the 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.

Further, 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 include general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), or other programmable logic devices, or any combinations 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 will be apparent to one of ordinary skill in the art that two or more modules may be combined to form a single module that performs the relevant functions in accordance with 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 element or controller. 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:

determining, by the wireless communication device, that the first resource indicated by the uplink cancellation information overlaps with the second resource;

receiving, by the wireless communication device, an Uplink (UL) grant from a network scheduling a third resource, wherein an ending symbol of a first downlink control channel carrying the UL grant is no earlier than a first symbol of a second downlink control channel carrying the uplink cancellation information.

2. The method of claim 1, wherein

The uplink cancellation information comprises an uplink cancellation indication (UL CI); and

the first resource, the second resource, and the third resource are uplink resources.

3. The method of claim 1, wherein

The second resource is configured by the network through signaling or scheduled by the network through another UL grant; and

the end symbol of the another UL grant is earlier than a first symbol of the second downlink control channel carrying the uplink cancellation information.

4. The method of claim 1, wherein

A time interval between an end position of the second downlink control channel carrying the uplink cancellation information and a start position of the first downlink control channel carrying the UL grant is not less than a predetermined threshold.

5. The method of claim 1, wherein

The UL grant is carried on a first downlink control channel with the following end symbol: the end symbol is no earlier than a first symbol of a third downlink control channel carrying subsequent uplink cancellation information received after receiving the uplink cancellation information.

6. The method of claim 1, wherein

The third resource starts later than an end symbol of the second resource.

7. The method of claim 1, wherein

The third resource is non-overlapping with the first resource; and

the third resource starts later than an end symbol of the second resource.

8. The method of claim 1, wherein

The third resource is non-overlapping with the first resource; and

the third resource starts no earlier than a predefined point in time.

9. The method of claim 8, wherein

The predefined point in time is a position of a certain number of symbols after the end of the uplink cancellation information.

10. The method of claim 8, wherein

The predefined point in time is a position a certain number of symbols after the start of the cancelled part of the second resource.

11. The method of claim 8, wherein the predefined point in time is a position a number of symbols after the end of the second resource.

12. The method of claim 1, wherein

The third resource is non-overlapping in time with the second resource; and

the third resource starts no earlier than a predefined point in time.

13. The method of claim 12, wherein

14. A wireless communications apparatus comprising at least one processor and memory, wherein the at least one processor is configured to read code from the memory and implement the method of claims 1-13.

15. A computer program product comprising computer readable program medium code stored thereon, which when executed by the at least one processor, causes the at least one processor to carry out the method according to claims 1 to 13.

16. A method of wireless communication, comprising:

transmitting, by a network to a wireless communication device, uplink cancellation information indicating a first resource, wherein the first resource overlaps with a second resource of the wireless communication device; and

transmitting, by the network to the wireless communication device, an Uplink (UL) grant scheduling a third resource, wherein an ending symbol of a first downlink control channel carrying the UL grant is no earlier than a first symbol of a second downlink control channel carrying the uplink cancellation information.

17. The method of claim 16, wherein

The uplink cancellation information comprises an uplink cancellation indication (UL CI);

the first resource, the second resource, and the third resource are uplink resources of the wireless communication device.

18. The method of claim 16, wherein

19. The method of claim 16, wherein

20. The method of claim 16, wherein

The UL grant is carried on a first downlink control channel having an end symbol that is no earlier than a first symbol of a third downlink control channel carrying subsequent uplink cancellation information that is transmitted after transmission of the uplink cancellation information.

21. The method of claim 16, wherein

The third resource starts later than the end of the end symbol of the second resource.

22. The method of claim 16, wherein

The third resource is non-overlapping with the first resource; and

the third resource starts later than an end symbol of the second resource.

23. The method of claim 16, wherein

The third resource is non-overlapping with the first resource; and

the third resource starts no earlier than a predefined point in time.

24. The method of claim 23, wherein

25. The method of claim 23, wherein

26. The method of claim 23, wherein

The predefined point in time is a position a certain number of symbols after the end of the second resource.

27. The method of claim 16, wherein

The third resource is non-overlapping in time with the second resource; and

the third resource starts no earlier than a predefined point in time.

28. The method of claim 27, wherein

29. A wireless communication apparatus comprising at least one processor and memory, wherein the at least one processor is configured to read code from the memory and implement the method of claims 16-28.

30. A computer program product comprising computer readable program medium code stored thereon, which when executed by the at least one processor, causes the at least one processor to carry out the method according to claims 16 to 28.