CN115024003A

CN115024003A - Method and equipment for deactivating downlink channel

Info

Publication number: CN115024003A
Application number: CN202080095008.4A
Authority: CN
Inventors: 苟伟; 张峻峰; 郝鹏; 韩祥辉
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2020-08-07
Filing date: 2020-08-07
Publication date: 2022-09-06
Also published as: WO2022027668A1; EP4082266A4; EP4082266A1

Abstract

The present disclosure relates to a wireless communication method for use in a wireless terminal, the wireless communication method comprising receiving, from a radio network node, release downlink control information deactivating a first downlink channel, and deactivating the first downlink channel at or after a start time.

Description

Method and equipment for deactivating downlink channel

Technical Field

This document is generally directed to wireless communications.

Background

In the related art, when Downlink Control Information (DCI) is transmitted in a slot n (where n is an integer) and an SPS1PDSCH (Semi Persistent Scheduling physical downlink shared channel (SPS PDSCH) having an index value of 1) in the slot n is deactivated by the release DCI, HARQ-ACK (hybrid automatic repeat request acknowledgement (message)) indicating the release of the DCI and the SPS1PDSCH is transmitted in the same Physical Uplink Control Channel (PUCCH). For example, a User Equipment (UE) generates a 1-bit HARQ-ACK for releasing DCI. The UE does not expect to receive the SPS1PDSCH and does not generate HARQ-ACK for the SPS1 PDSCH. Therefore, the Base Station (BS) should refrain from transmitting the SPS1 PDSCH.

If multiple SPS PDSCHs overlap each other in the time domain, the UE may only receive the SPS PDSCH with the smallest index. For example, as shown in fig. 1, SPS1PDSCH and SPS2PDSCH (SPS PDSCH with index value of 2) overlap in the time domain, the UE receives SPS1PDSCH and generates HARQ-ACK for SPS1 PDSCH. Note that the UE does not receive SPS2PDSCH and does not generate HARQ-ACK for SPS2 PDSCH.

In addition, if the HARQ-ACK codebook contains HARQ-ACK for dynamically scheduled PDSCH (DG PDSCH) or HARQ-ACK for releasing DCI, the HARQ-ACK codebook is constructed according to a TDRA (time domain resource allocation) mechanism. If the HARQ-ACK codebook contains only HARQ-ACK for the SPS PDSCH, the HARQ-ACK codebook is constructed according to the SPS mechanism.

In fig. 1, if a release DCI is missed (not received) by a UE, the BS and the UE may have different understandings on the construction mechanism of the HARQ-ACK codebook.

Further, if the SPS1PDSCH is released by releasing the DCI, the UE does not determine whether deactivation of the SPS1PDSCH takes effect immediately, which may also lead to a different understanding between the BS and the UE.

Disclosure of Invention

This document relates to methods, systems and devices for deactivating downlink channels, and more particularly, to methods, systems and devices for deactivating overlapping downlink shared channels.

The present disclosure relates to a wireless communication method used in a wireless terminal. The wireless communication method includes:

receiving release downlink control information deactivating a first downlink channel from a radio network node; and

deactivating the first downlink channel at or after a start time.

Various embodiments may preferably implement the following features:

preferably, the start time comprises at least one of:

a first time of a first symbol of an uplink channel, the uplink channel including an acknowledgment packet corresponding to the release of the downlink control information;

a second time that is a duration after an end symbol of the uplink channel, wherein the duration includes a value of 0 or a value expressed in one of a symbol, a sampling point, or a time unit;

a third time of N time slots after the time slot in which the uplink channel is located, wherein N is an integer; or

And fourth time of Q symbols after the ending symbol of the physical downlink control channel where the downlink control information is released, wherein Q is an integer.

Preferably, the uplink channel includes at least one of a physical uplink control channel or a physical uplink shared channel.

Preferably, the first downlink channel overlaps with the second downlink channel.

Preferably, at least one of the start symbol or the end symbol of the first downlink channel is configured to be before or not later than the start time, and the first downlink channel is activated.

Preferably, the wireless communication method further comprises receiving a first downlink channel from the radio network node.

Preferably, at least one of the start symbol or the end symbol of the first downlink channel is configured to be after the start time or not earlier than the start time, and the first downlink channel is deactivated.

Preferably, the wireless communication method further comprises not receiving the first downlink channel.

The present disclosure relates to a wireless communication method for use in a wireless network node, the wireless communication method comprising:

transmitting to the wireless terminal release downlink control information deactivating the first downlink channel, and

deactivating the first downlink channel at or after a start time.

Various embodiments may preferably implement the following features:

preferably, the start time comprises at least one of:

a third time of N time slots after the time slot of the uplink channel, wherein N is an integer; or

Preferably, the wireless communication method further comprises transmitting the first downlink channel to the wireless terminal.

Preferably, the wireless communication method further comprises not transmitting the first downlink channel.

receiving, from a radio network node, release downlink control information deactivating a first downlink channel, wherein the first downlink channel overlaps with a second downlink channel; and

transmitting a first acknowledgement message corresponding to the release downlink control information to the radio network node in a first uplink channel;

the first uplink channel is earlier than a second uplink channel, and a second acknowledgement message corresponding to the second downlink channel is transmitted in the second uplink channel.

Various embodiments may preferably implement the following features:

preferably, the first uplink channel does not overlap with the second uplink channel.

transmitting release downlink control information for deactivating a first downlink channel to a wireless terminal, wherein the first downlink channel overlaps with a second downlink channel; and

receiving a first acknowledgement message corresponding to the released downlink control information from the wireless terminal in a first uplink channel;

Various embodiments may preferably implement the following features:

The present disclosure relates to a wireless communication method used in a wireless terminal, the wireless communication method including:

receiving, from a radio network node, release downlink control information deactivating a first downlink channel; and

the first downlink channel and at least one second downlink channel overlapping the first downlink channel are not received.

Various embodiments may preferably implement the following features:

preferably, the first downlink channel and the at least one second downlink channel are in the same group.

Preferably, the group comprising the first downlink channel and the at least one second downlink channel corresponds to the same acknowledgement message.

Preferably, the first acknowledgement message corresponding to the release downlink control information, the second acknowledgement message corresponding to the first downlink channel, and the at least one third acknowledgement message corresponding to the at least one second downlink channel are indicated to the same uplink channel or the same timeslot.

Preferably, the release downlink control information, the first downlink channel and the at least one second downlink channel are in the same time slot.

Preferably, the wireless terminal does not generate at least one third acknowledgement message corresponding to the at least one second downlink channel.

Preferably, the at least one second downlink channel includes at least one of a dynamically scheduled physical downlink shared channel or a semi-persistently scheduled physical downlink shared channel.

the first downlink channel and at least one second downlink channel overlapping the first downlink channel are not transmitted to the wireless terminal.

Various embodiments may preferably implement the following features:

The present disclosure relates to a wireless terminal, comprising:

a communication unit configured to receive, from a radio network node, release downlink control information deactivating a first downlink channel; and

a processor configured to deactivate the first downlink channel at or after a start time.

Various embodiments may preferably implement the following features:

preferably, the processor is further configured to perform the wireless communication method of any of the foregoing methods.

The present disclosure relates to a wireless network node, comprising:

a communication unit configured to transmit, to the wireless terminal, release downlink control information deactivating the first downlink channel; and

Various embodiments may preferably implement the following features:

The present disclosure relates to a wireless terminal, comprising:

a communication unit configured to:

Various embodiments may preferably implement the following features:

preferably, the wireless terminal further comprises a processor configured to perform the wireless communication method of any of the foregoing methods.

The present disclosure relates to a radio network node, comprising:

a communication unit configured to:

Various embodiments may preferably implement the following features:

preferably, the radio network node further comprises a processor configured to perform the wireless communication method of any of the preceding methods.

The present disclosure relates to a wireless terminal, comprising:

a communication unit configured to:

Various embodiments may preferably implement the following features:

preferably, the wireless terminal further comprises a processor configured to perform the wireless communication method of any of the preceding methods.

The present disclosure relates to a wireless network node, comprising:

a communication unit configured to:

Various embodiments may preferably implement the following features:

The present disclosure relates to a computer program product comprising a computer readable program medium code stored thereon, which when executed by a processor, causes the processor to perform the wireless communication method of any of the aforementioned methods.

The exemplary embodiments disclosed herein are intended to provide features that will become apparent by reference to the following description in conjunction with the accompanying drawings. In accordance with various embodiments, exemplary 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.

Accordingly, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the particular order and/or hierarchy of steps in the methods disclosed herein is merely exemplary of the methods. The particular order or hierarchy of steps in the methods or processes disclosed may be rearranged based on design preferences, while remaining within the scope of the present disclosure. Accordingly, one of ordinary skill in the art will understand that the methods and techniques disclosed herein present the various steps or actions in a sample order, and unless otherwise explicitly stated, the disclosure is not limited to the specific order or hierarchy presented.

Drawings

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

Fig. 1 shows a schematic diagram of release DCI, SPS1PDSCH, SPS2PDSCH and PUCCH.

Fig. 2 shows a schematic diagram of a wireless terminal according to an embodiment of the disclosure.

Fig. 3 shows a schematic diagram of a radio network node according to an embodiment of the disclosure.

Fig. 4 shows a schematic diagram of release DCI, SPS1PDSCH, and SPS2PDSCH, according to an embodiment of the disclosure.

Fig. 5 shows a schematic diagram of release DCI, SPS1PDSCH, SPS2PDSCH, PUCCH1 and PUCCH2 according to an embodiment of the present disclosure.

Fig. 6 shows a flow chart of a process according to an embodiment of the present disclosure.

Fig. 7 shows a flow chart of a process according to an embodiment of the present disclosure.

Fig. 8 shows a flow chart of a process according to an embodiment of the present disclosure.

Fig. 9 shows a flow chart of a process according to an embodiment of the disclosure.

Fig. 10 shows a flow chart of a process according to an embodiment of the present disclosure.

Fig. 11 shows a flow chart of a process according to an embodiment of the disclosure.

Detailed Description

Fig. 2 relates to a schematic diagram of a wireless terminal 20 according to an embodiment of the disclosure. The wireless terminal 20 may be a User Equipment (UE), a mobile phone, a laptop computer, a tablet computer, an e-book, or a portable computer system, but is not limited thereto. The wireless terminal 20 may include a processor 200 such as a microprocessor or an Application Specific Integrated Circuit (ASIC), a storage unit 210, and a communication unit 220. The memory unit 210 may be any data storage device that stores program code 212 accessed and executed by the processor 200. Examples of the storage unit 210 include, but are not limited to, a Subscriber Identity Module (SIM), a read-only memory (ROM), a flash memory, a random-access memory (RAM), a hard disk, and an optical data storage device. The communication unit 220 may be a transceiver and serves to transmit and receive signals (e.g., messages or packets) according to the processing result of the processor 200. In an embodiment, the communication unit 220 transmits and receives signals through at least one antenna 222 shown in fig. 2.

In an embodiment, the storage unit 210 and the program code 212 may be omitted, and the processor 200 may include a storage unit in which the program code is stored.

The processor 200 may implement any of the steps of the illustrated embodiments on the wireless terminal 20, for example, by executing the program code 212.

The communication unit 220 may be a transceiver. Alternatively or additionally, the communication unit 220 may combine a transmitting unit and a receiving unit configured to transmit and receive signals to and from a radio network node (e.g. a base station), respectively.

Fig. 3 relates to a schematic diagram of a radio network node 30 according to an embodiment of the present disclosure. The Radio Network node 30 may be a satellite, a Base Station (BS), a Network Entity, a Mobility Management Entity (MME), a Serving Gateway (S-GW), a Packet Data Network (PDN) Gateway (P-GW), a Radio Access Network (RAN), a next generation RAN (NG-RAN), a Data Network, a core Network, or a Radio Network Controller (RNC), and is not limited herein. Further, the radio network node 30 may include (perform) at least one network function, such as an access and mobility management function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a Policy Control Function (PCF), an Application Function (AF), and the like. The radio network node 30 may comprise a processor 300, such as a microprocessor or ASIC, a memory unit 310 and a communication unit 320. Memory unit 310 may be any data storage device that stores program code 312 accessed and executed by processor 300. Examples of the storage unit 310 include, but are not limited to, a SIM, a ROM, a flash memory, a RAM, a hard disk, and an optical data storage device. The communication unit 320 may be a transceiver and serves to transmit and receive signals (e.g., messages or packets) according to the processing result of the processor 300. In one example, the communication unit 320 transmits and receives signals through at least one antenna 322 shown in fig. 3.

In an embodiment, the storage unit 310 and the program code 312 may be omitted. The processor 300 may include a memory unit storing program code.

The processor 300 may implement any of the steps described in the illustrated embodiments on the radio network node 30, e.g., by running the program code 312.

The communication unit 320 may be a transceiver. Alternatively or additionally, the communication unit 320 may combine a transmitting unit and a receiving unit configured to transmit and receive signals to and from a wireless terminal (e.g., user equipment), respectively.

Fig. 4 shows a schematic diagram of release DCI, SPS1PDSCH and SPS2PDSCH according to an embodiment of the present disclosure. In fig. 4, SPS1PDSCH and SPS2PDSCH in slot n (where n is an integer) are activated and overlap in the time domain. In embodiments, the BS and the UE do not have a consistent understanding of the time to effect the release of DCI (transmitted over PDCCH). For example, the BS may consider the release DCI to take effect after symbol N, while the UE considers the release DCI to take effect after symbol M (where M and N are integers and M is greater than N). In this case, in the view of the BS, the SPS1PDSCH is deactivated (e.g., deactivated) after symbol N; but in the UE's view, the SPS1PDSCH is deactivated after symbol M. If the released SPS1PDSCH is located between symbol N and symbol M and overlaps the SPS2PDSCH in the time domain, the BS may consider the SPS1PDSCH to be deactivated and may not consider the overlap between the SPS1PDSCH and the SPS2PDSCH when constructing the HARQ-ACK codebook. On the other hand, the UE considers the SPS1PDSCH not to be deactivated and still considers the overlap between the SPS1PDSCH and the SPS2PDSCH in constructing the HARQ-ACK codebook. Thus, these two different understandings may lead to different HARQ-ACK processing results. More specifically, according to the understanding of the BS, the UE only needs to generate HARQ-ACK as SPS1PDSCH, while according to the understanding of the UE, the UE needs to handle the time domain overlap between SPS1PDSCH and SPS2 PDSCH. When the UE receives an SPS PDSCH with the smallest index (e.g., SPS1 PDSCH), the UE generates HARQ-ACK for SPS1 PDSCH. When the UE does not receive the SPS2PDSCH, the UE does not generate a HARQ-ACK for the SPS2 PDSCH.

In the present disclosure, the effective time may be equal to the start time. For example, the effective time for releasing the DCI may be a starting time for applying the release DCI to deactivation of the corresponding SPS PDSCH or a starting time for deactivation of the SPS PDSCH based on the release DCI.

In this disclosure, "no later" may be equal to "before … or at time …".

In the present disclosure, "not earlier than" may be equal to "at time … or after …".

In the present disclosure, various embodiments are disclosed for avoiding disagreement in understanding of a generated HARQ-ACK codebook between a BS and a UE.

Example 1

In the present disclosure, a PUCCH/PUSCH containing HARQ-ACK to release DCI (i.e., HARQ-ACK to release DCI is ACK) is referred to as a first PUCCH/PUSCH.

In an embodiment, the effective time for releasing DCI may be defined in at least one of the following options.

1) The time point at which the first symbol of the first PUCCH/PUSCH starts is taken as the effective time (earliest) for releasing DCI.

2) The time point of duration T after the end symbol of the first PUCCH/PUSCH ends is taken as the effective time (earliest) for releasing DCI. In an embodiment, the duration T comprises a value 0 or a value expressed in one of a symbol, a sample point or a time unit. In the embodiment, it lastsThe time T may be a system-specified duration or time unit. For example, the duration T may be T as defined in the TS38.214 or TS38.213 specifications _proc,1 、N、N1、T _proc,2 、N2、Z、Z’、T _proc,CSI And N3. In an embodiment, the duration T may be any value as long as it is agreed in advance between the BS and the UE. When T ═ 0, the end of the end symbol (i.e., the last symbol) of the first PUCCH/PUSCH is the effective time to release DCI. In an embodiment, when T ═ 1 and the end symbol of the first PUCCH/PUSCH is in symbol n, the end of symbol n +1 (i.e. the start of symbol n + 2) is the validation time for subsequent release of DCI.

3) And taking the time point N time slots after the time slot of the first PUCCH/PUSCH as the effective time (earliest) for releasing the DCI. In this embodiment, N is a predefined integer. For example, N may be one of 0, 1, 2, 3, …, 20. In embodiments, N may also be indicated to the UE by the BS through signaling, or may be selected and reported to the BS by the UE. In an embodiment, when N is 0, the end time of slot N (i.e., the beginning of slot N + 1) where the first PUCCH/PUSCH is located is the effective time to release DCI. In an embodiment, when N ═ 1 and the first PUCCH/PUSCH is in slot N, the end of slot N +1 (i.e., the beginning of slot N + 2) is the validation time for subsequent release of DCI.

4) And taking the time point of Q symbols after the PDCCH ending symbol (namely the last symbol of the PDCCH) where the DCI is released ends as the effective time (earliest) of the DCI release. Here, Q symbols may be a decoding time for the UE to finish decoding the PDCCH, where Q is a given integer, e.g., one of 0, 1, 2, 3, …, 20. In embodiments, Q may also be indicated to the UE by the BS through signaling, or may be selected by the UE and reported to the BS. When Q is 0, the end of the PDCCH end symbol where DCI is released is the effective time for releasing DCI. In an embodiment, when Q ═ 1 and the PDCCH ending symbol where DCI is released is located in symbol n, the end of symbol n +1 (i.e. the beginning of symbol n + 2) is the effective time for the subsequent release of DCI.

In an embodiment, the BS and the UE agree to release DCI invalidity before the effective time for the release DCI. That is, the SPS PDSCH released by the release DCI is still considered as an activated SPS PDSCH before the effective time of the release DCI. For example, in fig. 4, if the SPS1PDSCH is before the effective time of releasing DCI, the time domain overlap of SPS1PDSCH and SPS2PDSCH needs to be considered to generate the corresponding HARQ-ACK. In other words, SPS1PDSCH is still an activated SPS PDSCH. Alternatively, if SPS1PDSCH is after the effective time of release DCI, then HARQ-ACK need not be generated considering the time domain overlap of SPS1PDSCH and SPS2 PDSCH. That is, the SPS1PDSCH is a deactivated SPS PDSCH, and the UE only generates HARQ-ACKs for the SPS2 PDSCH.

In an embodiment, if an SPS PDSCH is deactivated by release DCI, and if a start symbol or an end symbol of the SPS PDSCH is before an effective time of the release DCI, the SPS PDSCH is still considered as an activated SPS PDSCH, although release DCI corresponding to the SPS PDSCH has been transmitted or received.

In an embodiment, the SPS PDSCH is deactivated if it is deactivated by a release DCI, and if a starting symbol or an ending symbol of the SPS PDSCH is after an effective time of the release DCI, the release DCI corresponding to the SPS PDSCH.

In an embodiment, if the SPS PDSCH is deactivated by the release DCI, and if the start symbol or the end symbol of the SPS PDSCH is at the time of validity of the release DCI, the release DCI corresponding to the SPS PDSCH, the BS and the UE agree that the SPS PDSCH is deactivated or still considered activated.

Example 2

In an embodiment, the first PUCCH/PUSCH on which the HARQ-ACK corresponding to the release DCI is located is no later than the second PUCCH/PUSCH. In this embodiment, the construction of the HARQ-ACK codebook in the second PUCCH/PUSCH will be affected by the SPS PDSCH released by the release DCI.

In this embodiment, the construction of the HARQ-ACK codebook in the second PUCCH/PUSCH requires consideration of the released SPS PDSCH (if it is not released). For example, a portion (or all) of the PDSCH corresponding to the HARQ-ACK codebook in the second PUCCH/PUSCH overlaps the released SPS PDSCH in the time domain. In an embodiment, for multiple PDSCHs that overlap in the time domain, time domain overlap between the multiple PDSCHs is handled when generating HARQ-ACK.

In an embodiment, when constructing the HARQ-ACK codebook according to the SPS mechanism, the UE receives only the SPS PDSCH with the smallest index for a plurality of SPS PDSCHs overlapping in the time domain and generates HARQ-ACK for the SPS PDSCH with the smallest index. The SPS mechanism is used when the HARQ-ACK codebook includes only HARQ-ACK of the SPS PDSCH.

In an embodiment, when the HARQ-ACK codebook is constructed according to the TDRA mechanism, for a plurality of PDSCHs overlapping in the time domain, the UE divides PDSCHs in a slot into a plurality of groups according to an agreed rule. Each group may contain one or more PDSCHs and only 1 HARQ-ACK information may be generated per group. The division of the groups will be described in detail in example 3 below. The TDRA mechanism is used when there is at least one HARQ-ACK of a dynamically scheduled PDSCH or at least one HARQ-ACK of a released DCI in the HARQ-ACK codebook.

In embodiment 2, the first PUCCH/PUSCH is transmitted earlier than the second PUCCH/PUSCH. In this case, the BS may receive the first PUCCH/PUSCH earlier and know whether the UE correctly receives the release DCI. When the BS receives the second PUCCH/PUSCH, the BS can accurately know the construction mode of the HARQ-ACK codebook in the second PUCCH/PUSCH.

In an embodiment, embodiment 2 may be described as:

the first PUCCH/PUSCH is transmitted earlier than the second PUCCH/PUSCH. In this embodiment, the BS schedules the first PUCCH/PUSCH to be transmitted earlier than the second PUCCH/PUSCH and ensures that the first PUCCH/PUSCH and the second PUCCH/PUSCH do not overlap in the time domain. That is, the second PUCCH/PUSCH is transmitted after the first PUCCH/PUSCH. For example, after a first PUCCH/PUSCH, the BS may schedule a second PUCCH/PUSCH to be transmitted and ensure that they do not overlap in the time domain.

Fig. 5 shows a schematic diagram of release DCI, SPS1PDSCH, SPS2PDSCH, PUCCH1, and PUCCH2 according to an embodiment of the present disclosure. Note that PUCCH1 may be the first PUCCH/PUSCH described above, and PUCCH2 may be the second PUCCH/PUSCH described above. In fig. 5, SPS1PDSCH is deactivated by release DCI, and SPS1PDSCH and SPS2PDSCH overlap in the time domain. PUCCH1 is transmitted earlier than PUCCH2, which PUCCH1 corresponds to HARQ-ACK to release DCI, where HARQ-ACK for SPS2PDSCH carried by PUCCH2 is transmitted. As shown in fig. 5, HARQ-ACK codebook construction in PUCCH2 may be affected if SPS1PDSCH is not released. For example, since SPS1PDSCH and SPS2PDSCH overlap in the time domain, the UE needs to receive SPS1PDSCH and generate HARQ-ACK, but not receive SPS2 PDSCH. In this case, the HARQ-ACK in PUCCH2 is for the SPS1PDSCH instead of the SPS2PDSCH (generated). In fig. 5, PUCCH1 is transmitted to the BS before PUCCH 2. After receiving the PUCCH1, the BS confirms whether the release DCI is correctly received by the UE (i.e., the BS knows whether the release DCI has been validated on the UE side), so that the BS can correctly determine the HARQ-ACK codebook construction method in the PUCCH 2.

Based on embodiment 2, HARQ-ACK of release DCI can be fed back to the BS as early as possible, and the BS knows whether the release DCI is correctly received at the UE side. Therefore, misunderstanding in the construction of the subsequent HARQ-ACK codebook can be avoided. Furthermore, it is possible to prevent ambiguity of the construction mechanism of the HARQ-ACK codebook due to the missed detection of the release DCI. Furthermore, the inconsistency of understanding between the BS and the UE of the effective time for releasing the DCI is also avoided.

In an embodiment, the first PUCCH/PUSCH and the second PUCCH/PUSCH are the same PUCCH/PUSCH. That is, HARQ-ACK for release DCI and HARQ-ACK for SPS2PDSCH may be transmitted on the same PUCCH. In this embodiment, the base station side may determine the method for HARQ-ACK codebook construction through blind detection. For example, the BS detects the HARQ-ACK codebook based on assuming that the release DCI is correctly received and then based on assuming that the release DCI is not correctly received.

The HARQ-ACK in the first PUCCH/PUSCH and the HARQ-ACK in the second PUCCH/PUSCH may be multiplexed in the first or second or new PUCCH/PUSCH if the first PUCCH/PUSCH and the second PUCCH/PUSCH overlap in a time domain.

Example 3

In an embodiment, if the BS transmits the release DCI in slot n (where n is an integer), the SPS PDSCH released by the release DCI is also in slot n, and the HARQ-ACK of the release DCI and the HARQ-ACK of the released SPS PDSCH (assuming it is still activated) are in the same PUCCH/PUSCH, the UE does not expect to receive the released SPS PDSCH. Accordingly, the BS prohibits transmission of the SPS PDSCH.

More specifically, in the above case, the UE needs to construct the HARQ-ACK codebook according to the TDRA mechanism. In this case, the position of the HARQ-ACK releasing DCI in the HARQ-ACK codebook is determined according to the position of the released SPS PDSCH. In this embodiment, the released SPS PDSCH may not have its own HARQ-ACK because the location of the SPS PDSCH may only correspond to 1-bit HARQ-ACK feedback.

Further, under the TDRA mechanism, for a plurality of PDSCHs including a DG PDSCH and an SPS PDSCH overlapped in the time domain, the corresponding number of HARQ-ACK bits is determined according to an agreed rule, which will be described in detail in the division of the group in this embodiment. For example, in fig. 4, the SPS1PDSCH and the SPS2PDSCH overlap in the time domain. When constructing the HARQ-ACK codebook according to the TDRA mechanism, the SPS1PDSCH and the SPS2PDSCH will be divided into one group. One group corresponds to 1 HARQ-ACK information, so the UE can only generate 1-bit HARQ-ACK information for SPS1PDSCH and SPS2 PDSCH.

In the embodiment based on fig. 4, if HARQ-ACK of released DCI, HARQ-ACK of released SPS1PDSCH (assuming it is still activated) and HARQ-ACK of SPS2PDSCH are indicated to be transmitted in the same PUCCH, the HARQ-ACK codebook transmitted in this PUCCH needs to be constructed according to the TDRA mechanism. In this case, transmission of SPS1PDSCH is prohibited and the UE does not expect to receive SPS1 PDSCH. In this embodiment, it needs to be made clear whether the SPS2PDSCH should be transmitted and how the corresponding HARQ-ACK should be determined.

In embodiments, the UE also does not desire to process the SPS2PDSCH and/or does not generate HARQ-ACKs for the SPS2PDSCH because the SPS1PDSCH and the SPS2PDSCH overlap in the time domain. Accordingly, the BS prohibits transmission of the SPS2 PDSCH. In this way, the UE generates only a 1-bit HARQ-ACK, which corresponds to the HARQ-ACK releasing the DCI and is associated with the location of the released SPS PDSCH.

In an embodiment, the release DCI is transmitted in slot n, the released SPS1PDSCH is also in slot n, and the SPS1PDSCH and SPS2PDSCH overlap in the time domain. In this embodiment, if HARQ-ACK for release DCI, HARQ-ACK for released SPS1PDSCH (when activated), and HARQ-ACK for SPS2PDSCH are indicated to the same PUCCH/PUSCH or same slot for transmission, the UE does not expect to receive SPS2PDSCH and does not generate HARQ-ACK for SPS2PDSCH because SPS2PDSCH and released SPS1PDSCH overlap in the time domain and can only generate 1-bit HARQ-ACK for them. In this embodiment, the SPS2PDSCH may be a DG PDSCH, and the same procedure may be applied.

In an embodiment, the SPS2PDSCH needs to meet at least one of the following requirements. For the HARQ-ACK codebook structure, the SPS2PDSCH and the released SPS1PDSCH are in one group, and only 1-bit HARQ-ACK can be generated for the group. It should be noted that for multiple PDSCHs in a group, only 1-bit HARQ-ACKs can be generated for them. The HARQ-ACK is 1 bit if the UE is configured with TB level HARQ-ACK feedback. The HARQ-ACK is L bits if the UE is configured with CBG level HARQ-ACK feedback. Herein, L is the (maximum) CBG number configured. In the present disclosure, TB level HARQ-ACK feedback is assumed.

In an embodiment, the release DCI is transmitted in time slot n, and the released SPS PDSCH is also in time slot n, and the released SPS PDSCH overlaps with other PDSCHs in the time domain. In this embodiment, if HARQ-ACK for release DCI, HARQ-ACK for released SPS PDSCH (when it is activated), and HARQ-ACK for other PDSCHs are transmitted in the same PUCCH/PUSCH or in the same slot based on the HARQ-ACK codebook, the UE does not expect to receive all PDSCHs in the group including DG PDSCH, SPS PDSCH, generates only 1-bit HARQ-ACK for release DCI, and does not generate HARQ-ACK for PDSCHs in the group. That is, the UE does not expect to receive the PDSCH in the group and does not generate HARQ-ACKs for the PDSCH in the group. Note that the group is the group in which the released SPS PDSCH resides.

In an embodiment, the determination of the group is performed. In this embodiment, for a plurality of PDSCHs in one slot, the plurality of PDSCHs are divided into each group in the following manner. Among the plurality of PDSCHs, a PDSCH having an earliest end position is a first PDSCH, and a PDSCH overlapping the first PDSCH is a second PDSCH. The first PDSCH and the second PDSCH are divided into a group. Next, the above process is repeated for the remaining PDSCHs in the time slots other than the first PDSCH and the second PDSCH to determine the group until each PDSCH in the time slot is processed. Subsequently, the UE generates 1-bit HARQ-ACK information for each group.

Fig. 6 shows a flow chart of a process according to an embodiment of the present disclosure. The process shown in fig. 6 may be used in a wireless terminal (e.g., UE) and includes the steps of:

step 600: receiving, from the radio network node, release downlink control information deactivating the first downlink channel.

Step 601: deactivating the first downlink channel at or after a start time.

More specifically, the wireless terminal receives release DCI from a radio network node (e.g., BS), wherein the release DCI deactivates (e.g., de-activates) the first downlink channel (e.g., SPS1PDSCH shown in fig. 4 or fig. 5). In this embodiment, the first downlink channel is deactivated at or after the start time.

In an embodiment, the start time comprises at least one of:

a first time comprising a first symbol of an uplink channel corresponding to an acknowledgement message (e.g., HARQ-ACK) releasing DCI;

A fourth time of Q symbols after the end symbol of the PDCCH where the DCI is released, wherein Q is an integer.

In an embodiment, the uplink channel comprises at least one of PUCCH or PUSCH.

In an embodiment, wherein the first downlink channel overlaps with the second downlink channel (e.g., the SPS2PDSCH shown in fig. 4 or fig. 5).

In an embodiment, the first downlink channel is still activated when at least one of a start symbol or an end symbol of the first downlink channel is configured to be before or not later than the start time. That is, the wireless terminal may still (expect to) receive the first downlink channel.

In an embodiment, the first downlink channel is deactivated (e.g., deactivated) when at least one of the start symbol or the end symbol of the first downlink channel is configured to be after or not earlier than the start time. In other words, the wireless terminal may not (expect to) receive the first downlink channel.

Fig. 7 shows a flow chart of a process according to an embodiment of the present disclosure. The procedure shown in fig. 7 may be used in a radio network node (e.g., BS) and comprises the steps of:

step 700: and transmitting the release downlink control information for deactivating the first downlink channel to the wireless terminal.

Step 701: deactivating the first downlink channel at or after a start time.

In the process shown in fig. 7, the radio network node transmits a release DCI to the wireless terminal (e.g., UE), wherein the release DCI is configured to deactivate (e.g., deactivate) the first downlink channel (e.g., SPS1PDSCH shown in fig. 4 or fig. 5). In this embodiment, the first downlink channel is deactivated at or after the start time.

In an embodiment, the start time comprises at least one of:

a third time of N time slots after the time slot in which the uplink channel is located, wherein N is an integer; or alternatively

In an embodiment, the uplink channel comprises at least one of PUCCH or PUSCH.

In an embodiment, the first downlink channel is still activated when at least one of the start symbol or the end symbol of the first downlink channel is configured to be before or not later than the start time. That is, the radio network node may still (expect to) transmit the first downlink channel.

In an embodiment, the first downlink channel is deactivated (e.g., deactivated) when at least one of the start symbol or the end symbol of the first downlink channel is configured to be after or not earlier than the start time. In other words, the radio network node may not (expect to) transmit the first downlink channel.

Fig. 8 shows a flow chart of a process according to an embodiment of the present disclosure. The process shown in fig. 8 may be used in a wireless terminal (e.g., UE) and includes the steps of:

step 800: receiving, from a radio network node, release downlink control information deactivating a first downlink channel, wherein the first downlink channel overlaps with a second downlink channel.

Step 801: and transmitting a first acknowledgement message corresponding to the release downlink control information to the radio network node in a first uplink channel.

In this embodiment, a wireless terminal receives a release DCI from a radio network node (e.g., a BS) deactivating a first downlink channel (e.g., SPS1PDSCH shown in fig. 4 or fig. 5), wherein the first downlink channel overlaps a second downlink channel (e.g., SPS2PDSCH shown in fig. 4 or fig. 5). The wireless terminal transmits a first acknowledgement message (e.g., HARQ-ACK) corresponding to the release DCI in a first uplink channel (e.g., PUCCH1 shown in fig. 5) to the radio network node. It should be noted that the first uplink channel is earlier than the second uplink channel (e.g., PUCCH2 shown in fig. 5), and the second acknowledgement message corresponding to the second downlink channel is transmitted in the second uplink channel.

In an embodiment, the first uplink channel does not overlap with the second uplink channel.

In an embodiment, the first downlink channel is deactivated (e.g., deactivated) when at least one of the start symbol or the end symbol of the first downlink channel is configured to be after the start time or not earlier than the start time. In other words, the radio network node may not (expect to) transmit the first downlink channel.

Fig. 9 shows a flow chart of a process according to an embodiment of the present disclosure. The procedure shown in fig. 9 may be used in a radio network node (e.g., BS) and comprises the steps of:

step 900: and transmitting release downlink control information for deactivating a first downlink channel to the wireless terminal, wherein the first downlink channel is overlapped with a second downlink channel.

Step 901: a first acknowledgement message corresponding to the released downlink control information is received from the wireless terminal in a first uplink channel.

In this embodiment, a wireless network node transmits to a wireless terminal (e.g., a UE) release DCI deactivating a first downlink channel (e.g., SPS1PDSCH shown in fig. 4 or fig. 5), where the first downlink channel overlaps a second downlink channel (e.g., SPS2PDSCH shown in fig. 4 or fig. 5). The radio network node receives a first acknowledgement message (e.g., HARQ-ACK) in a first uplink channel corresponding to the release DCI. It should be noted that the first uplink channel is earlier than the second uplink channel (e.g., PUCCH2 shown in fig. 5), and the second acknowledgement message (e.g., HARQ-ACK) corresponding to the second downlink channel is transmitted in the second uplink channel.

Fig. 10 shows a flow chart of a process according to an embodiment of the present disclosure. The process shown in fig. 10 may be used in a wireless terminal (e.g., UE) and includes the steps of:

step 1000: receiving, from the radio network node, release downlink control information deactivating the first downlink channel.

Step 1001: the first downlink channel and at least one second downlink channel overlapping the first downlink channel are not received.

More specifically, the wireless terminal receives a release DCI from a radio network node (e.g., BS) deactivating a first downlink signal (e.g., SPS1PDSCH shown in fig. 4 or fig. 5). In this embodiment, the wireless terminal does not (expect to) receive the first downlink channel and at least one second downlink channel (e.g., SPS2PDSCH shown in fig. 4 or fig. 5) that overlaps the first downlink channel.

In an embodiment, the first downlink channel and the at least one second downlink channel are in the same group.

In an embodiment, the first downlink channel and the at least one second downlink channel are grouped in the same group based on the end positions of the first downlink channel and the at least one second downlink channel.

In an embodiment, a group comprising (including) the first downlink channel and the at least one second downlink channel corresponds to the same acknowledgement message (e.g., 1-bit HARQ-ACK).

In an embodiment, a first acknowledgement message (e.g., HARQ-ACK) corresponding to the release DCI, a second acknowledgement message corresponding to the first downlink channel, and at least one third acknowledgement message corresponding to the at least one second downlink channel are indicated to the same uplink channel or the same time slot.

In an embodiment, the release DCI, the first downlink channel and the at least one second downlink channel are in the same time slot.

In an embodiment, the wireless terminal generates the fourth acknowledgement message for a group comprising the first downlink channel and the at least one second downlink channel, because the first downlink channel overlaps with the at least one second channel. In an embodiment, the bit width of the fourth acknowledgment message is 1 bit. In an embodiment where CBG (codebook group) based transmission is configured, the bit width of the fourth acknowledgement message is L bits, where L is the maximum number of CBGs configured.

In an embodiment, the wireless terminal does not generate at least one third acknowledgement message corresponding to the at least one second downlink channel.

In an embodiment, the at least one second downlink channel comprises at least one of a DG PDSCH or an SPS PDSCH.

Fig. 11 shows a flow chart of a process according to an embodiment of the present disclosure. The process shown in fig. 11 may be used in a radio network node (e.g., BS) and comprises the steps of:

step 1100: and transmitting the release downlink control information for deactivating the first downlink channel to the wireless terminal.

Step 1101: the first downlink channel and at least one second downlink channel that overlaps with the first downlink channel are not transmitted to the wireless terminal.

In particular, the radio network node transmits a release DCI (e.g., SPS1PDSCH shown in fig. 4 or fig. 5) to deactivate the first downlink signal to the wireless terminal (e.g., UE). In this embodiment, the radio network node does not (expect to) transmit the first downlink channel and at least one second downlink channel (e.g., the SPS2PDSCH shown in fig. 4 or fig. 5) that overlaps the first downlink channel.

In an embodiment, a group containing (e.g., including) the first downlink channel and the at least one second downlink channel corresponds to the same acknowledgement message (e.g., 1-bit HARQ-ACK).

In an embodiment, the radio network node receives (e.g. corresponds to) a fourth acknowledgement message comprising (e.g. comprising) a group of the first downlink channel and the at least one second downlink channel, since the first downlink channel overlaps with the at least one second channel. In an embodiment, the bit width of the fourth acknowledgment message is 1 bit. In an embodiment where CBG (codebook group) based transmission is configured, the bit width of the fourth acknowledgement message is L bits, where L is the maximum number of CBGs configured.

While various embodiments of the present disclosure have been described above, it should be understood that the additional modules are presented by way of example only, and not limitation. Likewise, the various figures may depict example architectures or configurations, and are provided to enable one of ordinary skill in the art to understand the example features and functionality of the present disclosure. However, those of ordinary skill in the art will appreciate that the present disclosure is not limited to the example architectures or configurations shown, but may be implemented using a variety of alternative architectures and configurations. Additionally, 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 exemplary embodiments.

It will also be understood that any reference herein to an element using a name such as "first," "second," etc., does not generally limit the number or order of such elements. Rather, these designations are used herein to facilitate the distinction of 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 used, or that the first element must somehow precede the second element.

Additionally, 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 skill would further appreciate that any of the various illustrative logical blocks, units, 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 element"), or any combination of these technologies.

To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, units, 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 such technologies, 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. According to various embodiments, a processor, device, component, circuit, structure, machine, unit, etc. may be configured to perform one or more of the functions described herein. The terms "configured to" or "configured to" as used herein with respect to a particular operation or function refer to a processor, device, component, circuit, structure, machine, unit, etc., that is physically constructed, programmed, and/or arranged to perform the particular operation or function.

Furthermore, those skilled in the art will appreciate that the various illustrative logical blocks, units, devices, components, and circuits described herein may be implemented within or performed with an Integrated Circuit (IC), which may include a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other programmable logic device or any combination thereof. The logic blocks, units and circuits may also include antennas and/or transceivers to communicate with various components within the network or 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 for performing 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 as software stored in a computer readable medium.

Computer-readable media includes both computer storage media and communication media, including any medium that can transfer a computer program or code 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.

As used herein, the term "unit" refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purposes of discussion, the various elements are described as discrete elements; however, it will be apparent to one of ordinary skill in the art that two or more units may be combined to form a single unit that performs the associated functions according to embodiments of the present disclosure.

Further, in embodiments of the present disclosure, memory or other storage devices and communication components may be employed. It will be appreciated that the above description for clarity has described embodiments of the disclosure 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 departing from the disclosure. For example, functionality illustrated to be performed by separate processing logic elements or controllers may be performed by the same processing logic elements or controllers. Thus, references to specific functional units are only to references to suitable means for providing the described functionality rather than indicative of a strict logical or physical structure or organization.

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

Claims

1. A wireless communication method adapted for a wireless terminal, comprising:

deactivating the first downlink channel at or after a start time.

2. The wireless communication method of claim 1, wherein the start time comprises at least one of:

a first time of a first symbol of an uplink channel, the uplink channel including a confirmation message corresponding to the release of the downlink control information;

a second time that is a duration after an end symbol of the uplink channel, wherein the duration comprises a value of 0 or a value represented in one of a symbol, a sample point, or a unit of time;

And a fourth time of Q symbols after the ending symbol of the physical downlink control channel where the downlink control information is released, wherein Q is an integer.

3. The wireless communication method of claim 2, wherein the uplink channel comprises at least one of a physical uplink control channel or a physical uplink shared channel.

4. The wireless communication method according to any of claims 1 to 3, wherein the first downlink channel overlaps with a second downlink channel.

5. The wireless communication method of any of claims 1-4, wherein at least one of a start symbol or an end symbol of the first downlink channel is configured to be before or not later than the start time, and

wherein the first downlink channel is activated.

6. The wireless communication method of claim 5, further comprising:

receiving the first downlink channel from the radio network node.

7. The wireless communication method of any of claims 1-4, wherein at least one of a start symbol or an end symbol of the first downlink channel is configured to be after or not earlier than the start time, and

wherein the first downlink channel is deactivated.

8. The wireless communication method of claim 7, further comprising:

the first downlink channel is not received.

9. A method of wireless communication applicable to a wireless network node, comprising:

transmitting release downlink control information for deactivating the first downlink channel to the wireless terminal; and

deactivating the first downlink channel at or after a start time.

10. The wireless communication method of claim 9, wherein the start time comprises at least one of:

And a fourth time of Q symbols after the end symbol of the physical downlink control channel where the downlink control information is released, wherein Q is an integer.

11. The wireless communication method of claim 10, wherein the uplink channel comprises at least one of a physical uplink control channel or a physical uplink shared channel.

12. The wireless communication method according to any of claims 9 to 11, wherein the first downlink channel overlaps with a second downlink channel.

13. The wireless communication method of any of claims 1-12, wherein at least one of a start symbol or an end symbol of the first downlink channel is configured to be before or not later than the start time, and

wherein the first downlink channel is activated.

14. The wireless communication method of claim 13, further comprising:

transmitting the first downlink channel to the wireless terminal.

15. The wireless communication method of any of claims 9 to 12, wherein at least one of a start symbol or an end symbol of the first downlink channel is configured to be after or not earlier than the start time, and

wherein the first downlink channel is deactivated.

16. The wireless communication method of claim 15, further comprising:

not transmitting the first downlink channel.

17. A wireless communication method adapted for a wireless terminal, comprising:

and the first uplink channel is earlier than a second uplink channel, and a second confirmation message corresponding to the second downlink channel is transmitted in the second uplink channel.

18. The wireless communication method of claim 17, wherein the first uplink channel does not overlap with the second uplink channel.

19. A method of wireless communication applicable to a wireless network node, comprising:

transmitting release downlink control information for deactivating a first downlink channel to a wireless terminal, wherein the first downlink channel is overlapped with a second downlink channel; and

20. The wireless communication method of claim 19, wherein the first uplink channel does not overlap with the second uplink channel.

21. A wireless communication method adapted for a wireless terminal, comprising:

not receiving the first downlink channel and at least one second downlink channel overlapping the first downlink channel.

22. The wireless communication method of claim 21, wherein the first downlink channel and the at least one second downlink channel are in a same group.

23. The wireless communication method of claim 22, wherein the group comprising the first downlink channel and the at least one second downlink channel correspond to a same acknowledgement message.

24. The wireless communication method according to any of claims 21 to 23, wherein a first acknowledgement message corresponding to the release downlink control information, a second acknowledgement message corresponding to the first downlink channel and at least one third acknowledgement message corresponding to the at least one second downlink channel are indicated to a same uplink channel or a same timeslot.

25. The wireless communication method according to any of claims 21 to 24, wherein the release downlink control information, the first downlink channel and the at least one second downlink channel are in the same time slot.

26. The wireless communication method according to any of claims 21 to 25, wherein the wireless terminal does not generate at least one third acknowledgement message corresponding to the at least one second downlink channel.

27. The wireless communication method of any of claims 21 to 26, wherein the at least one second downlink channel comprises at least one of a dynamically scheduled physical downlink shared channel or a semi-persistently scheduled physical downlink shared channel.

28. A method of wireless communication applicable to a wireless network node, comprising:

not transmitting the first downlink channel and at least one second downlink channel overlapping the first downlink channel to the wireless terminal.

29. The wireless communication method of claim 28, wherein the first downlink channel and the at least one second downlink channel are in a same group.

30. The wireless communication method of claim 29, wherein the group comprising the first downlink channel and the at least one second downlink channel correspond to a same acknowledgement message.

31. The wireless communication method according to any of claims 28 to 30, wherein a first acknowledgement message corresponding to the release downlink control information, a second acknowledgement message corresponding to the first downlink channel and at least one third acknowledgement message corresponding to the at least one second downlink channel are indicated to a same uplink channel or a same timeslot.

32. The wireless communication method of any of claims 28 to 31, wherein the release downlink control information, the first downlink channel and the at least one second downlink channel are in the same time slot.

33. The wireless communication method according to any of claims 28 to 32, wherein the at least one second downlink channel comprises at least one of a dynamically scheduled physical downlink shared channel or a semi-persistently scheduled physical downlink shared channel.

34. A wireless terminal, comprising:

35. The wireless terminal of claim 34, wherein the processor is further configured to perform the wireless communication method of any of claims 2-8.

36. A wireless network node, comprising:

37. The radio network node in claim 36, wherein the processor is further configured to perform the wireless communication method in accordance with any of claims 10-16.

38. A wireless terminal, comprising:

a communication unit configured to:

receiving, from a wireless network node, release downlink control information deactivating a first downlink channel, wherein the first downlink channel overlaps with a second downlink channel; and

and transmitting a second acknowledgement message corresponding to the second downlink channel in the second uplink channel, wherein the first uplink channel is earlier than the second uplink channel.

39. The wireless terminal of claim 38, further comprising a processor configured to perform the wireless communication method of claim 18.

40. A wireless network node, comprising:

a communication unit configured to:

receiving a first acknowledgement message corresponding to the release downlink control information from the wireless terminal in a first uplink channel;

41. The radio network node in claim 40, further comprising a processor configured to perform the wireless communication method of claim 20.

42. A wireless terminal, comprising:

a communication unit configured to:

43. The wireless terminal of claim 42, further comprising a processor configured to perform the wireless communication method of any of claims 22-27.

44. A wireless network node, comprising:

a communication unit configured to:

45. The radio network node according to claim 44, further comprising a processor configured to perform the wireless communication method according to any of claims 29 to 33.

46. A computer program product comprising a computer readable program medium code stored thereon, which when executed by a processor, causes the processor to perform the wireless communication method of any of claims 1 to 33.