WO2024207449A1

WO2024207449A1 - Devices, methods, and medium for communication

Info

Publication number: WO2024207449A1
Application number: PCT/CN2023/086958
Authority: WO
Inventors: Lei Chen; Gang Wang
Original assignee: NEC Corp
Current assignee: NEC Corp
Priority date: 2023-04-07
Filing date: 2023-04-07
Publication date: 2024-10-10
Anticipated expiration: 2025-10-07

Abstract

Example embodiments of the present disclosure relate to devices, methods, and computer storage medium for communication. A terminal device may receive first CG PUSCH information indicating multiple CG PUSCH occasions in a first CG period from a network device. The terminal device may determine a first CG PUSCH occasion in the first CG period for transmitting a first PUSCH. If the first CG PUSCH occasion would overlap with a second transmission occasion for transmitting a second PUSCH, the terminal device may further cancel the first PUSCH or the second PUSCH based on at least one of: a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether first uplink control information (UCI) has been transmitted, a CG PUSCH occasion used for transmitting the first UCI, or whether the first CG PUSCH occasion is unused. As such, the network device and the terminal device may have a common understanding on the operations in case an overlap occurs, e.g., cancelling the first PUSCH or the second PUSCH, and therefore the confusion between the network device and the terminal device for a transmission may be avoided.

Description

DEVICES, METHODS, AND MEDIUM FOR COMMUNICATION

FIELD

Example embodiments of the present disclosure generally relate to the field of communication techniques and in particular, to devices, methods, and a computer readable medium for communication.

BACKGROUND

Recently, a new work item on the enhancements for extended reality (XR) services is ongoing in new radio (NR) release 18 (Rel-18) . To better support the XR services, enhancement on power saving and capacity will be studied and specified.

Configured grant (CG) physical uplink shared channel (PUSCH) is beneficial for meeting some requirements of the XR services since no scheduling request (SR) and buffer status report (BSR) reporting is needed. However, the enhancement of CG PUSCH is further to be studied.

SUMMARY

In general, example embodiments of the present disclosure provide devices, methods, and a computer storage medium for communication.

In a first aspect, there is provided a terminal device. The terminal device comprises at least one processor configured to cause the terminal device at least to: receive, from a network device, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period; determine a first CG PUSCH occasion in the first CG period for transmitting a first PUSCH; in accordance with a determination that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for transmitting a second PUSCH, perform the cancellation of the first PUSCH or the second PUSCH based on at least one of: a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether first uplink control information (UCI) has been transmitted, a CG PUSCH occasion used for transmitting the first UCI, or whether the first CG PUSCH occasion is unused.

In a second aspect, there is provided a network device. The terminal device comprises at least one processor configured to cause the network device at least to: transmit, to a terminal device, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period; determine a first CG PUSCH occasion in the first CG period for receiving a first PUSCH; and in accordance with a determination that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for receiving a second PUSCH, determine that one of the first PUSCH or the second PUSCH is to be cancelled by the terminal device based on at least one of:a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether first uplink control information (UCI) has been received, a CG PUSCH occasion used for receiving the first UCI, or whether the first CG PUSCH occasion is unused.

In a third aspect, there is provided a method of communication. The method comprises: receiving, at a terminal device from a network device, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period; determining a first CG PUSCH occasion in the first CG period for transmitting a first PUSCH; and in accordance with a determination that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for transmitting a second PUSCH, performing the cancellation of the first PUSCH or the second PUSCH based on at least one of: a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether first uplink control information (UCI) has been transmitted, a CG PUSCH occasion used for transmitting the first UCI, or whether the first CG PUSCH occasion is unused.

In a fourth aspect, there is provided a method of communication. The method comprises: transmitting, at a network device to a terminal device, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period; determining a first CG PUSCH occasion in the first CG period for receiving a first PUSCH; and in accordance with a determination that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for receiving a second PUSCH, determining that one of the first PUSCH or the second PUSCH is to be cancelled by the terminal device based on at least one of: a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether first uplink control information (UCI) has been received, a CG PUSCH occasion used for receiving the first UCI, or whether the first CG PUSCH occasion is unused.

In a fifth aspect, there is provided a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the third or the fourth aspect above.

It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Through the more detailed description of some example embodiments of the present disclosure in the accompanying drawings, the above and other objects, features and advantages of the present disclosure will become more apparent, wherein:

FIG. 1 illustrates an example communication system in which some embodiments of the present disclosure can be implemented;

FIG. 2 illustrates a signalling chart illustrating communication process in accordance with some embodiments of the present disclosure;

FIG. 3 illustrates a schematic diagram of an overlap in time in accordance with some embodiments of the present disclosure;

FIG. 4 illustrates another schematic diagram of an overlap in time in accordance with some embodiments of the present disclosure;

FIG. 5A illustrates a schematic diagram of a gap from an end time of the first UCI to a start time of the PDCCH in accordance with some embodiments of the present disclosure;

FIG. 5B illustrates a schematic diagram of a gap from an end time of the first UCI to a start time of the PDCCH in accordance with some embodiments of the present disclosure;

FIG. 6 illustrates a flowchart of an example method implemented at a terminal device in accordance with some embodiments of the present disclosure;

FIG. 7 illustrates a flowchart of an example method implemented at a network device in accordance with some embodiments of the present disclosure; and

FIG. 8 illustrates a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

In some examples, values, procedures, or apparatus are referred to as “best, ” “lowest, ” “highest, ” “minimum, ” “maximum, ” or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.

As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , 5.5G, 5G-Advanced networks, or the sixth generation (6G) communication protocols, and/or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

As used herein, the term “terminal device” refers to any device having wireless or wired communication capabilities. Examples of terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV) commonly known as a drone which is an aircraft without any human pilot, devices on high speed train (HST) , or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also be incorporated one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM. The term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.

As used herein, the term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of a network device include, but not limited to, a satellite, a unmanned aerial systems (UAS) platform, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.

In one embodiment, the terminal device may be connected with a first network device and a second network device. One of the first network device and the second network device may be a master node and the other one may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs) . In one embodiment, the first network device may be a first RAT device and the second network device may be a second RAT device. In one embodiment, the first RAT device is eNB and the second RAT device is gNB. Information related with different RATs may be transmitted to the terminal device from at least one of the first network device and the second network device. In one embodiment, first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device. In one embodiment, information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.

Communications discussed herein may conform to any suitable standards including, but not limited to, New Radio Access (NR) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , cdma2000, and Global System for Mobile Communications (GSM) and the like. Furthermore, the communications may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.85G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , and the sixth (6G) communication protocols. The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.

The terminal device or the network device may have Artificial intelligence (AI) or machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.

The terminal device or the network device may work on several frequency ranges, e.g. FR1 (410 MHz –7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band larger than 100GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum. The terminal device may have more than one connection with the network device under Multi-Radio Dual Connectivity (MR-DC) application scenario. The terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.

The embodiments of the present disclosure may be performed in test equipment, e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, or channel emulator.

The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.

The term “circuitry” used herein may refer to hardware circuits and/or combinations of hardware circuits and software. For example, the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware. As a further example, the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions. In a still further example, the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation. As used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.

As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term “includes” and its variants are to be read as open terms that mean “includes, but is not limited to. ” The term “based on” is to be read as “based at least in part on. ” The term “one embodiment” and “an embodiment” are to be read as “at least one embodiment. ” The term “another embodiment” is to be read as “at least one other embodiment. ” The terms “first, ” “second, ” and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.

As mentioned above, Power saving and capacity of XR services may be enhanced. There are some important features of the XR traffic which are quite different from other serveries, for example:

● Jitter of packet arrival time: for a downlink (DL) or uplink (UL) video stream, there is a significant jitter effect for the data packet arrival time. This means, the packet can arrive to the gNB or UE at any time within a specific range, e.g., [-4ms, 4ms] , around a theoretically average arrival time.

● Delay budget: transmission of the video and pose/control packets with low latency is very critical for XR service to provide good user experience; therefore a very stringent requirement of delay budget is needed, e.g., 10ms, 15ms, etc.

● Large and varying packet size: for a high quality video stream, a video frame usually has a large size, e.g., around 1M bits per frame after compression for a video stream. In addition, the data packet size is varying over time, and it is difficult to predict the packet size before it arrives.

CG PUSCH is beneficial for meeting the stringent delay budget since no SR and BSR reporting is needed. However, the large and variable packet size should be considered in the enhancement of CG PUSCH.

Multiple CG PUSCH transmission occasions may be supported in a period of a single CG PUSCH configuration. Dynamic indication of unused CG PUSCH occasion (s) based on uplink control information (UCI) also may be supported. For example, a physical channel that carries the UCI that provides information about unused CG PUSCH transmission occasion (s) is CG PUSCH.

For convenience in discussion, the term “multi-PUSCHs CG” may refer to a CG PUSCH configuration with multiple CG PUSCH transmission occasions within a period of the CG PUSCH configuration. Similarly, a term “single-PUSCH CG” may refer to a CG PUSCH configuration with single CG PUSCH transmission occasion within a period of the CG PUSCH configuration.

Based on the multi-PUSCHs CG mechanism, there will be multiple CG PUSCH occasions in a CG period and the resource assignment for the occasions is semi-persistent, therefore there may be an overlap between the CG PUSCH occasion (s) with other uplink transmissions. In this case, how to perform the transmission when an overlap occurs needs to be further studied.

Embodiments of the present disclosure provide a solution of communication. In the solution, a terminal device may receive first CG PUSCH information indicating multiple CG PUSCH occasions in a first CG period from a network device. The terminal device may determine a first CG PUSCH occasion in the first CG period for transmitting a first PUSCH. If the first CG PUSCH occasion would overlap with a second transmission occasion for transmitting a second PUSCH, the terminal device may further cancel the first PUSCH or the second PUSCH based on at least one of: a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether first uplink control information (UCI) has been transmitted, a CG PUSCH occasion used for transmitting the first UCI, or whether the first CG PUSCH occasion is unused. As such, the network device and the terminal device may have a common understanding on the operations in case an overlap occurs, e.g., cancelling the first PUSCH or the second PUSCH, and therefore a confusion between the network device and the terminal device for a transmission may be avoided. Principles and implementations of the present disclosure will be described in detail below with reference to the figures.

FIG. 1 illustrates an example communication system 100 in which some embodiments of the present disclosure can be implemented. The communication network 100 includes a network device 110 and a terminal device 120. The network device 110 can provide services to the terminal device 120.

In the system 100, it is assumed that the terminal device 120 is located within coverage of the network device 110. In some examples, a link from the network device 110 to the terminal device 120 is referred to as a downlink (DL) , while a link from the terminal device 120 to the network device 110 is referred to as an uplink (UL) . In downlink, the network device 110 is a transmitting (TX) device (or a transmitter) and the terminal device 120 is a receiving (RX) device (or a receiver) . In uplink, the terminal device 120 is a transmitting TX device (or a transmitter) and the network device 110 is a RX device (or a receiver) . In some embodiments, the network device 110 and the terminal device 120 may communicate with direct links/channels. DL may comprise one or more logical channels, including but not limited to a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH) . UL may comprise one or more logical channels, including but not limited to a Physical Uplink Control Channel (PUCCH) and a Physical Uplink Shared Channel (PUSCH) . As used herein, the term “channel” may refer to a carrier or a part of a carrier consisting of a contiguous set of resource blocks (RBs) on which a channel access procedure is performed in shared spectrum.

Communications in the system 100, between the network device 110 and the terminal device 120 for example, may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Divided Multiple Address (CDMA) , Frequency Divided Multiple Address (FDMA) , Time Divided Multiple Address (TDMA) , Frequency Divided Duplexer (FDD) , Time Divided Duplexer (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Divided Multiple Access (OFDMA) and/or any other technologies currently known or to be developed in the future.

Embodiments of the present disclosure can be applied to any suitable scenarios. For example, embodiments of the present disclosure can be implemented at reduced capability NR devices. Alternatively, embodiments of the present disclosure can be implemented in one of the followings: NR multiple-input and multiple-output (MIMO) , NR sidelink enhancements, NR systems with frequency above 52.6GHz, an extending NR operation up to 71GHz, narrow band-Internet of Thing (NB-IOT) /enhanced Machine Type Communication (eMTC) over non-terrestrial networks (NTN) , NTN, UE power saving enhancements, NR coverage enhancement, NB-IoT and LTE-MTC, Integrated Access and Backhaul (IAB) , NR Multicast and Broadcast Services, or enhancements on Multi-Radio Dual-Connectivity.

It is to be understood that the numbers of devices (i.e., the network device 110 and the terminal device 120) and their connection relationships and types shown in FIG. 1 are only for the purpose of illustration without suggesting any limitation. The system 100 may include any suitable numbers of devices adapted for implementing embodiments of the present disclosure.

In the present disclosure, the term “a start time of” may be replaced by “an end time of” , “a middle time of” , etc. Similarly, the term “an end time of” may be replaced by “a start time of” , “a middle time of” , etc. In other words, a specific time may be suitable for the present disclosure. In one embodiment, “a start time” may be suitable for the present disclosure. In one embodiment, “a middle time” may be suitable for the present disclosure. In one embodiment, “an end time” may be suitable for the present disclosure.

In the present disclosure, “a CG PUSCH occasion is unused” may also refer to that a CG is to be (would be) unused. Similarly, “a CG PUSCH occasion is used” may also refer to that a CG PUSCH is to be (would be) used.

Reference is further made to FIG. 2, which illustrates a signalling chart illustrating communication process 200 in accordance with some example embodiments of the present disclosure. Only for the purpose of discussion, the process 200 will be described with reference to FIG. 1. The process 200 may involve the network device 110 and the terminal device 120.

The network device 110 transmits 210 first CG PUSCH information 212 to the terminal device 120. In some example embodiments, the first CG PUSCH information 212 may indicate a first number of CG PUSCH occasions in a first CG period. In some examples, the first number of CG PUSCH occasions may be represented as Ncg1, which may be an integer greater than 0. For example, 1≤Ncg1≤8. It is to be understood that the value of Ncg1 may be any integer and the present disclosure does not limit this aspect. In other words, the first CG PUSCH information 212 may indicate that there are Ncg1 CG PUSCH occasions in the first CG period. In some example embodiments, the first CG PUSCH information 212 may be associated with a first index, such as a first CG PUSCH configuration index.

In some example embodiments, the first CG PUSCH information 212 may indicate a type 1 CG. In some examples, the first CG PUSCH information 212 may include a CG PUSCH configuration, for example, the first CG PUSCH information 212 may be transmitted via a radio resource control (RRC) message/signalling.

In some example embodiments, the first CG PUSCH information 212 may indicate a type 2 CG. In some examples, the first CG PUSCH information 212 may be transmitted via an RRC message/signalling or may be transmitted via downlink control information (DCI) . In some example, the DCI may be used to activate the number of configured CG PUSCH occasions (i.e., Ncg1 configured CG PUSCH occasions) in a CG period.

In the present disclosure, a CG PUSCH occasion may also be called as a configured CG occasion or a configured CG PUSCH occasion, for example, it may refer to a transmission occasion for a CG PUSCH. For example, a CG PUSCH occasion may occupy multiple time units, where a time unit may be a symbol, a slot, a sub-frame, a frame, a millisecond, etc.

Accordingly, the network device 110 may indicate to the terminal device 120 that a first CG period comprises Ncg1 CG PUSCH occasions according to the first PUSCH information 212. On the other side of communication, the terminal device 120 receives 214 the first CG PUSCH information 212.

In addition or alternatively, the network device 110 may transmit 220 second CG PUSCH information 222 to the terminal device 120. In some example embodiments, the second CG PUSCH information 222 may indicate a single-PUSCH CG, e.g., the second PUSCH information 222 may indicate that there is one CG PUSCH occasion in a second CG period. In some other example embodiments, the second CG PUSCH information 222 may indicate a multi-PUSCHs CG, e.g., the second CG PUSCH information 222 may indicate a second number of CG PUSCH occasions in a second CG period. In some examples, the second number of CG PUSCH occasions may be represented as Ncg2, which may be an integer greater than 0. For example, 1≤Ncg2≤8. In some example embodiments, the second CG PUSCH information 222 may be associated with a second index, such as a second CG PUSCH configuration index. On the other side of communication, the terminal device 120 may receive 224 the second CG PUSCH information 222.

In addition or alternatively, the network device 110 may transmit 230 a DCI 232 to the terminal device 120. The DCI 232 is transmitted on a PDCCH and is scheduling a PUSCH, such as a second PUSCH. On the other side of communication, the terminal device 120 may receive 234 the DCI 232.

The terminal device 120 determines 240 a first CG PUSCH occasion in the first CG period, where the first CG PUSCH occasion is used for transmitting a first PUSCH.

In some example embodiments, the terminal device 120 may determine whether an overlap would occur (to be occurred or to be occurring) for the first PUSCH. For example, the terminal device 120 may determine whether there is another transmission would overlap in time with the first PUSCH.

In the present disclosure, it is assumed that the terminal device 120 determines that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for transmitting a second PUSCH. In other words, the terminal device 120 determines 242 that the first PUSCH would overlap in time with a second PUSCH.

In addition, if the first PUSCH would overlap in time with a second PUSCH, the terminal device 120 cancels 250 the first PUSCH or the second PUSCH. Specifically, the terminal device 120 may cancel the first PUSCH or the second PUSCH based on one or more of: a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether a first UCI has been transmitted, a CG PUSCH occasion used for transmitting the first UCI, whether the first CG PUSCH occasion is unused, a first priority of the first PUSCH, or a second priority of the second PUSCH.

For example, the first UCI may be used to indicate whether there are one or more unused CG PUSCH occasions in the first period, and/or which one (s) is/are unused.

In some example embodiments, the second PUSCH may be associated with one of CG PUSCH occasion (s) in the second CG period. For example, the first CG PUSCH occasion in the first CG period would overlap in time with a second CG PUSCH occasion in the second period, where the first CG PUSCH occasion is used for transmitting the first PUSCH and the second CG PUSCH occasion is used for transmitting the second PUSCH.

In some examples, if the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused and the transmission time of an earliest CG PUSCH occasion in the first CG period is started later than a further transmission time of an earliest CG PUSCH occasion in the second CG period, the terminal device 120 may cancel the first PUSCH. For example, the first PUSCH would be transmitted in the first CG PUSCH occasion which may be a used CG PUSCH occasion. For example, the first priority may be the same as the second priority, e.g., the first PUSCH and the second PUSCH have the same priority index. For example, at least one of the first priority and the second priority are not configured. For example, as shown in FIG. 2, the terminal device 120 may transmit 260 a transmission 262 including the second PUSCH.

In some examples, if the first index of the first CG PUSCH information is larger than a second index of the second CG PUSCH information and the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused, the terminal device 120 may cancel the first PUSCH. For example, the first UCI is transmitted before the first CG PUSCH occasion and indicates at least one unused CG PUSCH occasion, but the at least one unused CG PUSCH occasion does not include the first CG PUSCH occasion, in other words, the first CG PUSCH occasion is not indicated to be unused. For example, the first UCI is transmitted before the first CG PUSCH occasion and indicates at least one used CG PUSCH occasion which includes the first CG PUSCH occasion, in other words, the first CG PUSCH occasion is to be used. In some other examples, if the first index of the first CG PUSCH information is smaller than a second index of the second CG PUSCH information and the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused, the terminal device 120 may cancel the first PUSCH. For example, the transmission time of an earliest CG PUSCH occasion in the first CG period and a further transmission time of an earliest CG PUSCH occasion in the second CG period are started in a same symbol. For example, the first PUSCH would be transmitted in the first CG PUSCH occasion which may be a used CG PUSCH occasion. For example, the first priority may be the same as the second priority, e.g., the first PUSCH and the second PUSCH have the same priority index. For example, at least one of the first priority and the second priority are not configured. For example, as shown in FIG. 2, the terminal device 120 may transmit 260 a transmission 262 including the second PUSCH.

In some examples, if a predefined rule associated with a cancellation of the second PUSCH is met and the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused, the terminal device 120 may cancel the second PUSCH. For example, the first CG PUSCH occasion is a used CG PUSCH occasion. For example, as shown in FIG. 2, the terminal device 120 may transmit 260 a transmission 262 including the first PUSCH.

In some examples, if the predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the first PUSCH or the second PUSCH is smaller than a time threshold, the terminal device 120 may cancel the second PUSCH. For example, the first CG PUSCH occasion is an unused CG PUSCH occasion. For example, the gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the first PUSCH or the second PUSCH is smaller than the time threshold, e.g., there is not enough time for preparation of the transmission, in this case the second PUSCH may be cancelled.

In some other examples, if the predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the first PUSCH or the second PUSCH is not smaller than a time threshold, the terminal device 120 may not cancel the second PUSCH. In the present disclosure, the terminal device 120 does not cancel the second PUSCH may refer to the terminal device 120 transmit the second PUSCH. For example, as shown in FIG. 2, the terminal device 120 may transmit 260 a transmission 262 including the second PUSCH. For example, the first CG PUSCH occasion is an unused CG PUSCH occasion. For example, the gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the first PUSCH or the second PUSCH is not smaller (or larger) than the time threshold, e.g., there is enough time for preparation of the transmission, in this case the second PUSCH may not have to be cancelled, in other words, the cancellation decision based on the predefined rule may be overridden.

One example implementation of the predefined rule associated with a cancellation of the second PUSCH may include: a first priority of the first PUSCH is higher than a second priority of the second PUSCH. For example, the first PUSCH has a larger priority index (such as index 1) and the second PUSCH has a smaller priority index (such as index 0) . In some other example implementations, the predefined rule may be associated with another parameter of the second PUSCH, such as a delay requirement, a traffic amount, etc.

In addition or alternatively, the terminal device 120 may transmit 260 a transmission 262 to the network device 110. In some examples, the transmission 262 may include the first PUSCH or the second PUSCH. In some other example embodiments, there may be no transmission performed, in other words, the operation 260 is not performed.

In some example embodiments, there may be a second UCI is determined to be multiplexed in the first PUSCH. In this case, if the first PUSCH is canceled, the terminal device 120 may further determine whether to transmit the second UCI during another transmission occasion. In some examples, if the first PUSCH is to be cancelled and a second UCI has been determined to be multiplexed in the first PUSCH, the terminal device 120 may multiplex the second UCI in the second PUSCH in the second CG period, for example, if the second PUSCH is transmitted at 260. In some other examples, if the first PUSCH is to be cancelled and a second UCI has been determined to be multiplexed in the first PUSCH, the terminal device 120 may multiplex the second UCI in a further PUSCH transmitted in a further CG PUSCH occasion in the first CG period. For example, if there is a further PUSCH in the next available CG PUSCH occasion in the first CG period, the second UCI may be multiplexed in the further PUSCH in the first CG period. In some other examples, the terminal device 120 may drop the second UCI.

In some example embodiments, the terminal device 120 may determine the number of CG PUSCH occasions (such as single or multiple CG PUSCH occasions) in the first CG period based on the first CG PUSCH information 212.

In some examples, if the first PUSCH cancelled, the number of CG PUSCH occasions in the first CG period may not include the first CG PUSCH occasion. In other words, the first CG PUSCH occasion (with a cancelled first PUSCH) is not counted in the total number of CG PUSCH occasions in the first CG period, e.g., the terminal device 120 will determine an additional CG PUSCH occasion to keep the total number of CG PUSCH occasions unchanged. For example, the terminal device 120 may firstly determine Ncg1 CG PUSCH occasions including the first CG PUSCH occasion which is used for the first PUSCH, after the first PUSCH is determined to be cancelled, the terminal device 120 may determine an additional CG PUSCH occasion in the first CG period. For example, the terminal device 120 may determine an additional CG PUSCH occasion after the last CG PUSCH occasion based on the time and frequency domain resource allocation indicated in the first CG PUSCH information 212.

In some other examples, the number of CG PUSCH occasions in the first CG period may include the first CG PUSCH occasion which is used for the first PUSCH, regardless whether the first PUSCH is cancelled or not. In other words, the first CG PUSCH occasion (with a cancelled first PUSCH) is counted in the total number of CG PUSCH occasions in the first CG period, e.g., the terminal device 120 will not determine an additional CG PUSCH occasion to keep the total number of CG PUSCH occasions unchanged.

In addition or alternatively, the network device 110 may transmit an indication the terminal device 120, where the indication is used to indicate whether the canceled CG PUSCH occasion may be included in the total number of CG PUSCH occasions in the first (or the second) CG period. For example, the first CG PUSCH information 212 may include a first indication indicating whether the first CG PUSCH occasion would be included in the total number of CG PUSCH occasions in the first CG period if the first CG PUSCH occasion is to be cancelled. For example, the second CG PUSCH information 222 may include a second indication indicating whether the second CG PUSCH occasion would be included in the total number of CG PUSCH occasions in the second CG period if the second CG PUSCH occasion is to be cancelled. In some example embodiments, the terminal device 120 may determine the total number of CG PUSCH occasions in the first CG period based on the first indication.

As discussed above, in case a first CG PUSCH occasion for a first PUSCH would overlap in time with a second CG PUSCH occasion for a second PUSCH, at least one PUSCH may be cancelled. In this event, the transmission between the terminal device 120 and the network device 110 may be guaranteed.

In some other example embodiments, the second PUSCH may be scheduled by the DCI 232.

In some examples, the terminal device 120 should not expect the second PUSCH would overlap in time with the first CG PUSCH occasion in the first CG period for transmitting the first PUSCH. In some examples, if the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused, the terminal device 120 may cancel the second PUSCH. In some examples, if the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the PDCCH or the second PUSCH is smaller than a time threshold, the terminal device 120 may cancel the second PUSCH. In some examples, if the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a start time (or an end time) of the first UCI is later than a reception of the PDCCH, the terminal device 120 may cancel the second PUSCH. In some examples, if the first CG PUSCH occasion is the earliest CG PUSCH occasion in the first CG period, the terminal device 120 may cancel the second PUSCH. In some examples, if a second UCI has been determined to be multiplexed in the first PUSCH, wherein the second UCI is used to indicate at least one unused CG PUSCH occasion in the first period, the terminal device 120 may cancel the second PUSCH. In some examples, if the first priority is higher than the second priority, the terminal device 120 may cancel the second PUSCH. For example, as shown in FIG. 2, the terminal device 120 may transmit 260 a transmission 262 including the first PUSCH.

In some examples, the terminal device 120 can expect the second PUSCH would overlap in time with the first PUSCH. In some examples, if a first priority of the first PUSCH and a second priority of the second PUSCH are the same or there are no priorities of the first PUSCH and the second PUSCH are configured, the terminal device 120 may cancel the first PUSCH. In some examples, if the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the PDCCH or the second PUSCH is not smaller than a time threshold, the terminal device 120 may cancel the first PUSCH. For example, as shown in FIG. 2, the terminal device 120 may transmit 260 a transmission 262 including the second PUSCH.

In some example embodiments, the terminal device 120 may transmit the second PUSCH which is scheduled by the DCI 232. For example, the second priority of the second PUSCH may be higher than the first priority of the first PUSCH. For example, the second PUSCH has a larger priority index (such as index 1) and the first PUSCH has a smaller priority index (such as index 0) . In some examples, a minimum time duration from an end time (or a start time) of the PDCCH to a start time (or an end time) of the second PUSCH may be determined based on a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the PDCCH.

In some examples, if the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time (or an end time) of the PDCCH is smaller than a first threshold, or the DCI is received before the end time (or the start time) of the first UCI (e.g., the gap is less than 0) , the minimum time duration may equal to a first value. For example, the first value may be associated with at least one of: a cancelling time for cancelling the first PUSCH, or a preparation time for preparing the second PUSCH associated with a capability of the terminal device.

As a specific example, the first value may be determined based on the value of d_2, 1, where d_2, 1= d1 or d_2, 1= d1+d3, and where d1 and d3 are determined based on a capability of the terminal device 120, e.g., a reported UE capability. For example, d1 is an additional number of symbols needed beyond the PUSCH preparation time for cancelling the first PUSCH; and d3 is an additional number of symbols needed on top of a cancellation time (i.e., Release 16 cancellation time) . For example, a total cancellation time may be N2+d1+d3, where N2 may be associated with μ and determined based on Table 1 or Table 2, where Table 1 and Table 2 are for UE processing capability 1 and 2 respectively.

Table 1

Table 2

In some other examples, if the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, the DCI is received after the end time of the first UCI, and the gap from the end time (or a start time) of the first UCI to the start time (or an end time) of the PDCCH is not smaller (or larger) than the first threshold, the minimum time duration may equal to a second value. For example, the second value may be associated with a preparation time for preparing the second PUSCH associated with a capability of the terminal device. For example, the second value may be not associated with a cancelling time for cancelling the first PUSCH.

In some examples, the first threshold may be associated with at least one of: a processing time of the first UCI by the network device 110, or a preparation time for scheduling the second PUSCH by the network device 110. For example, the first threshold may be a function of the processing time of the first UCI by the network device 110 and the preparation time for scheduling the second PUSCH by the network device 100. As a specific example, the first threshold may equal to a sum of the processing time of the first UCI by the network device 110 and the preparation time for scheduling the second PUSCH by the network device 100.

In some examples, the minimum time duration may be associated with a PUSCH preparation time based on a processing capability of the terminal device 120.

As discussed above, in case a first CG PUSCH occasion for a first PUSCH would overlap in time with a transmission occasion for a second PUSCH scheduled by a DCI, the first PUSCH or the second PUSCH may be cancelled. In this event, the transmission between the terminal device 120 and the network device 110 may be guaranteed.

Additionally, a minimum time duration from an end time (or a start time) of the PDCCH to a start time (or an end time) of the second PUSCH may be determined, for example, in case the first UCI which indicates that the first CG PUSCH occasion is unused is transmitted, the network device 110 may have enough time to be aware of the first UCI and to transmit the second PUSCH.

As shown in FIG. 2, the network device 110 determines 241 a first CG PUSCH occasion in the first CG period, where the first CG PUSCH occasion is used for transmitting a first PUSCH. The network device 110 determines 243 that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for transmitting a second PUSCH. And the network device 110 determines 251 that the first PUSCH or the second PUSCH is to be cancelled by the terminal device 120. In some example embodiments, the operations 241, 243, and 251 are similar with the operations 240, 242, and 250 respectively, and thus will not be descried in detail for brevity.

In addition or alternatively, the terminal device 120 may transmit 260 the transmission 262, such as the first PUSCH or the second PUSCH discussed above, and accordingly, the network device 110 may receive 264 the transmission 262.

According to some embodiments described above with reference to FIG. 2, the network device 110 and the terminal device 120 may have a common understanding on the operations in case an overlap occurs, e.g., cancelling the first PUSCH or the second PUSCH, and therefore a confusion between the network device 110 and the terminal device 120 for a transmission may be avoided.

FIG. 3 illustrates a schematic diagram 300 of an overlap in time in accordance with some embodiments of the present disclosure. As shown in FIG. 3, it is assumed that there are 4 CG PUSCH occasions in the first CG period 302, and there are 3 CG PUSCH occasions in the second CG period 352.

It is assumed that a first PUSCH is to be transmitted in the CG PUSCH occasion 315 in the first CG period 302, a second PUSCH is to be transmitted in the CG PUSCH occasion 325 in the second CG period 352, the CG PUSCH occasion 315 would overlap with the CG PUSCH occasion 325 in time, and the first PUSCH and the second PUSCH have a same priority index. In this case, if a first UCI 310 has transmitted and does not indicate that the CG PUSCH occasion 315 is unused, then the terminal device 120 may determine to cancel one of the first PUSCH or the second PUSCH with a smaller CG configuration index.

FIG. 4 illustrates a schematic diagram 400 of an overlap in time in accordance with some embodiments of the present disclosure. As shown in FIG. 4, it is assumed that there are 4 CG PUSCH occasions in the first CG period 402, and there is a DCI transmitted on a PDCCH 420 to schedule a second PUSCH 425, which may be called as a DG PUSCH 425.

It is assumed that a first PUSCH is to be transmitted in the CG PUSCH occasion 415 in the first CG period 402, and the CG PUSCH occasion 415 would overlap with the DG PUSCH 425 in time. In this case, if a first UCI 410 has transmitted and indicates that the CG PUSCH occasion 415 is unused, then the terminal device 120 may determine not to cancel the second PUSCH, in other words, the second PUSCH may be transmitted at 425.

It should be understood that examples in FIGS. 3-4 are only for illustrative without any limitation, other examples may stilled be applied and the present disclosure will not list herein.

FIG. 5A illustrates a schematic diagram 500 of a gap from an end time of the first UCI to a start time of the PDCCH in accordance with some embodiments of the present disclosure. As shown in FIG. 5A, it is assumed that there are 4 CG PUSCH occasions in the first CG period 502, and there is a DCI transmitted on a PDCCH 520 to schedule a second PUSCH 525, which may be called as a DG PUSCH 525.

The first UCI 510 has been transmitted and indicates that the CG PUSCH occasion 515 is unused, and the CG PUSCH occasion 515 would overlap with the DG PUSCH 525.

Since the DCI is transmitted before the first UCI 510, in other words, the gap from an end time of the first UCI to a start time of the PDCCH (-T1) is a negative value, then a minimum time duration from an end time of the PDCCH 520 to a start time of the DG PUSCH 525 is a first value.

FIG. 5B illustrates a schematic diagram 550 of a gap from an end time of the first UCI to a start time of the PDCCH in accordance with some embodiments of the present disclosure. As shown in FIG. 5B, it is assumed that there are 4 CG PUSCH occasions in the first CG period 552, and there is a DCI transmitted on a PDCCH 560 to schedule a second PUSCH 575, which may be called as a DG PUSCH 575.

The first UCI 560 has been transmitted and indicates that the CG PUSCH occasion 565 is unused, and the CG PUSCH occasion 565 would overlap with the DG PUSCH 575.

Since the gap from an end time of the first UCI to a start time of the PDCCH (T1) is larger than a first threshold, then a minimum time duration from an end time of the PDCCH 520 to a start time of the DG PUSCH 525 is a second value.

According to the example embodiments described with reference to FIGS. 2-5B, the network device 110 and the terminal device 120 may have a common understanding on the operations in case an overlap occurs, e.g., cancelling the first PUSCH or the second PUSCH, and therefore a confusion between the network device 110 and the terminal device 120 for a transmission may be avoided.

FIG. 6 illustrates a flowchart of an example method 600 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 600 will be described from the perspective of the terminal device 120 with reference to FIG. 1.

At block 610, the terminal device 120 receives, from the network device 110, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period. At block 620, the terminal device 120 determines a first CG PUSCH occasion in the first CG period for transmitting a first PUSCH. At block 630, if the first CG PUSCH occasion is to be overlapped with a second transmission occasion for transmitting a second PUSCH, the terminal device 120 performs the cancellation of the first PUSCH or the second PUSCH based on at least one of: a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether first uplink control information (UCI) has been transmitted, a CG PUSCH occasion used for transmitting the first UCI, whether the first CG PUSCH occasion is unused, a first priority of the first PUSCH, or a second priority of the second PUSCH.

In some example embodiments, the terminal device 120 receives, from the network device, second CG PUSCH information indicating a second number of CG PUSCH occasions in a second CG period, where the second transmission occasion is a second CG PUSCH occasion in the second CG period for transmitting the second PUSCH.

In some example embodiments, the terminal device 120 cancels the first PUSCH based on a determination that: the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused, and the transmission time of an earliest CG PUSCH occasion in the first CG period is started later than a further transmission time of an earliest CG PUSCH occasion in the second CG period.

In some example embodiments, the terminal device 120 cancels the first PUSCH based on a determination that: the first index of the first CG PUSCH information is larger than a second index of the second CG PUSCH information, and the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused.

In some example embodiments, the terminal device 120 cancels the first PUSCH based on a determination that: the first index of the first CG PUSCH information is smaller than a second index of the second CG PUSCH information, and the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused.

In some example embodiments, the transmission time of an earliest CG PUSCH occasion in the first CG period and a further transmission time of an earliest CG PUSCH occasion in the second CG period are started in a same symbol.

In some example embodiments, the terminal device 120 cancels the second PUSCH based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the first PUSCH or the second PUSCH is smaller than a time threshold.

In some example embodiments, the terminal device 120 does not cancel the second PUSCH based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the first PUSCH or the second PUSCH is not smaller than a time threshold.

In some example embodiments, the terminal device 120 cancels the second PUSCH based on: a predefined rule associated with a cancellation of the second PUSCH is met, and the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused.

In some example embodiments, the predefined rule comprises: a first priority of the first PUSCH is higher than a second priority of the second PUSCH.

In some example embodiments, if the first PUSCH is to be cancelled and a second UCI has been determined to be multiplexed in the first PUSCH, the terminal device 120 performs at least one of: multiplexing the second UCI in the second PUSCH, multiplexing the second UCI in a further PUSCH transmitted in a further CG PUSCH occasion in the first CG period, or dropping the second UCI.

In some example embodiments, if the first PUSCH is to be cancelled, the terminal device 120 determines the number of CG PUSCH occasions in the first CG period, wherein the number of CG PUSCH occasions do not comprise the first CG PUSCH occasion.

In some example embodiments, the terminal device 120 determines the number of CG PUSCH occasions in the first CG period, wherein the number of CG PUSCH occasions comprise the first CG PUSCH occasion.

In some example embodiments, the terminal device 120 receives, from the network device, downlink control information (DCI) in a physical downlink control channel (PDCCH) scheduling the second PUSCH.

In some example embodiments, the terminal device 120 cancels the second PUSCH based on at least one of: the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the PDCCH or the second PUSCH is smaller than a time threshold, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a start time (or an end time) of the first UCI is later than a reception of the PDCCH, the first CG PUSCH occasion is the earliest CG PUSCH occasion in the first CG period, or a second UCI has been determined to be multiplexed in the first PUSCH, wherein the second UCI is used to indicate at least one unused CG PUSCH occasion in the first period.

In some example embodiments, the terminal device 120 cancels the first PUSCH based on at least one of: a first priority of the first PUSCH and a second priority of the second PUSCH are the same or there are no priorities of the first PUSCH and the second PUSCH are configured, or the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the PDCCH or the second PUSCH is not smaller than a time threshold.

In some example embodiments, if the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, the terminal device 120 determines that a minimum time duration from an end time (or a start time) of the PDCCH to a start time (or an end time) of the second PUSCH is a first value based on a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the PDCCH is smaller than a first threshold, or the DCI is received before the end time of the first UCI.

In some example embodiments, if the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, the terminal device 120 determines that a minimum time duration from an end time (or a start time) of the PDCCH to a start time (or an end time) of the second PUSCH is a second value based on the gap from the end time (or a start time) of the first UCI to the start time (or an end time) of the PDCCH is not smaller than the first threshold, or the DCI is received after the end time of the first UCI.

In some example embodiments, the first value is associated with at least one of: a cancelling time for cancelling the first PUSCH, or a preparation time for preparing the second PUSCH associated with a capability of the terminal device.

In some example embodiments, the second value is associated with a preparation time for preparing the second PUSCH associated with a capability of the terminal device.

In some example embodiments, the first threshold is associated with at least one of: a processing time of the first UCI by the network device, or a preparation time for scheduling the second PUSCH by the network device.

FIG. 7 illustrates a flowchart of an example method 700 implemented at a network device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described from the perspective of the network device 110 with reference to FIG. 1.

At block 710, the network device 110 transmits, to a terminal device 120, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period. At block 720, the network device 110 determines a first CG PUSCH occasion in the first CG period for receiving a first PUSCH. At block 730, if the first CG PUSCH occasion is to be overlapped with a second transmission occasion for receiving a second PUSCH, the network device 110 determines that one of the first PUSCH or the second PUSCH is to be cancelled by the terminal device based on at least one of: a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether first uplink control information (UCI) has been received, a CG PUSCH occasion used for receiving the first UCI, whether the first CG PUSCH occasion is unused, a first priority of the first PUSCH, or a second priority of the second PUSCH.

In some example embodiments, the network device 110 transmits, to the terminal device, second CG PUSCH information indicating a second number of CG PUSCH occasions in a second CG period, where the second transmission occasion is a second CG PUSCH occasion in the second CG period for transmitting the second PUSCH.

In some example embodiments, the network device 110 determines that the first PUSCH is to be cancelled based on a determination that: the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused, and the transmission time of an earliest CG PUSCH occasion in the first CG period is started later than a further transmission time of an earliest CG PUSCH occasion in the second CG period.

In some example embodiments, the network device 110 determines that the first PUSCH is to be cancelled based on a determination that: the first index of the first CG PUSCH information is larger than a second index of the second CG PUSCH information, and the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused.

In some example embodiments, the network device 110 determines that the first PUSCH is to be cancelled based on a determination that: the first index of the first CG PUSCH information is smaller than a second index of the second CG PUSCH information, and the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused.

In some example embodiments, the network device 110 determines that the second PUSCH is to be cancelled based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been received and indicates that the first CG PUSCH occasion is unused, and a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the first PUSCH or the second PUSCH is smaller than a time threshold.

In some example embodiments, the network device 110 determines that the second PUSCH is not to be cancelled based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the first PUSCH or the second PUSCH is not smaller than a time threshold.

In some example embodiments, the network device 110 determines that the second PUSCH is to be cancelled based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, and the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused.

In some example embodiments, if the first PUSCH is to be cancelled and a second UCI has been determined to be multiplexed in the first PUSCH, the network device 110 performs at least one of: receiving the second UCI being multiplexed in the second PUSCH, receiving the second UCI being multiplexed in a further PUSCH transmitted in a further CG PUSCH occasion in the first CG period, or determining that the second UCI is dropped.

In some example embodiments, if the first PUSCH is to be cancelled, the network device 110 determines the number of CG PUSCH occasions in the first CG period, wherein the number of CG PUSCH occasions do not comprise the first CG PUSCH occasion.

In some example embodiments, the network device 110 determines the number of CG PUSCH occasions in the first CG period, wherein the number of CG PUSCH occasions comprise the first CG PUSCH occasion.

In some example embodiments, the network device 110 transmits, to the terminal device, downlink control information (DCI) in a physical downlink control channel (PDCCH) scheduling the second PUSCH.

In some example embodiments, the network device 110 determines that the second PUSCH is to be cancelled based on at least one of: the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused, the first UCI has been received and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time (or an end time) of the PDCCH or the second PUSCH is smaller than a time threshold, the first UCI has been received and indicates that the first CG PUSCH occasion is unused, and a start time (or an end time) of the first UCI is later than a reception of the PDCCH, the first CG PUSCH occasion is the earliest CG PUSCH occasion in the first CG period, or a second UCI has been determined to be multiplexed in the first PUSCH, wherein the second UCI is used to indicate at least one unused CG PUSCH occasion in the first period.

In some example embodiments, the network device 110 determines that the first PUSCH is to be cancelled based on at least one of: a first priority of the first PUSCH and a second priority of the second PUSCH are the same or there are no priorities of the first PUSCH and the second PUSCH are configured, or the first UCI has been received and indicates that the first CG PUSCH occasion is unused, and a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the PDCCH or the second PUSCH is not smaller than a time threshold.

In some example embodiments, if the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, the network device 110 determines that a minimum time duration from an end time (or a start time) of the PDCCH to a start time (or an end time) of the second PUSCH is a first value based on a gap from an end time (or a start time) of the first UCI to a start time (or an end time) of the PDCCH is smaller than a first threshold, or the DCI is received before the end time of the first UCI.

In some example embodiments, if the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, the network device 110 determines that a minimum time duration from an end time (or a start time) of the PDCCH to a start time (or an end time) of the second PUSCH is a second value based on the gap from the end time (or a start time) of the first UCI to the start time (or an end time) of the PDCCH is not smaller than the first threshold, or the DCI is received after the end time of the first UCI.

Details of some embodiments according to the present disclosure have been described with reference to FIGS. 1-7. Now an example implementation of the terminal device and the network device will be discussed below.

In some example embodiments, a terminal device comprises circuitry configured to: receive, from a network device, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period; determine a first CG PUSCH occasion in the first CG period for transmitting a first PUSCH; in accordance with a determination that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for transmitting a second PUSCH, perform the cancellation of the first PUSCH or the second PUSCH based on at least one of: a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether first uplink control information (UCI) has been transmitted, a CG PUSCH occasion used for transmitting the first UCI, whether the first CG PUSCH occasion is unused, a first priority of the first PUSCH, or a second priority of the second PUSCH.

In some example embodiments, the terminal device comprises circuitry configured to: receive, from the network device, second CG PUSCH information indicating a second number of CG PUSCH occasions in a second CG period, wherein the second transmission occasion is a second CG PUSCH occasion in the second CG period for transmitting the second PUSCH.

In some example embodiments, the terminal device comprises circuitry configured to: cancel the first PUSCH based on a determination that: the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused, and the transmission time of an earliest CG PUSCH occasion in the first CG period is started later than a further transmission time of an earliest CG PUSCH occasion in the second CG period.

In some example embodiments, the terminal device comprises circuitry configured to: cancel the first PUSCH based on a determination that: the first index of the first CG PUSCH information is larger than a second index of the second CG PUSCH information, and the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused.

In some example embodiments, the terminal device comprises circuitry configured to: cancel the first PUSCH based on a determination that: the first index of the first CG PUSCH information is smaller than a second index of the second CG PUSCH information, and the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused.

In some example embodiments, the terminal device comprises circuitry configured to: cancel the second PUSCH based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the first PUSCH or the second PUSCH is smaller than a time threshold.

In some example embodiments, the terminal device comprises circuitry configured to: not cancel the second PUSCH based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the first PUSCH or the second PUSCH is not smaller than a time threshold.

In some example embodiments, the terminal device comprises circuitry configured to: cancel the second PUSCH based on: a predefined rule associated with a cancellation of the second PUSCH is met, and the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused.

In some example embodiments, the terminal device comprises circuitry configured to: in accordance with a determination that the first PUSCH is to be cancelled and a second UCI has been determined to be multiplexed in the first PUSCH, perform at least one of: multiplexing the second UCI in the second PUSCH, multiplexing the second UCI in a further PUSCH transmitted in a further CG PUSCH occasion in the first CG period, or dropping the second UCI.

In some example embodiments, the terminal device comprises circuitry configured to: in accordance with a determination that the first PUSCH is to be cancelled, determine the number of CG PUSCH occasions in the first CG period, where the number of CG PUSCH occasions do not comprise the first CG PUSCH occasion.

In some example embodiments, the terminal device comprises circuitry configured to: determine the number of CG PUSCH occasions in the first CG period, wherein the number of CG PUSCH occasions comprise the first CG PUSCH occasion.

In some example embodiments, the terminal device comprises circuitry configured to: receive, from the network device, downlink control information (DCI) in a physical downlink control channel (PDCCH) scheduling the second PUSCH.

In some example embodiments, the terminal device comprises circuitry configured to: cancel the second PUSCH based on at least one of: the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the PDCCH or the second PUSCH is smaller than a time threshold, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a start time of the first UCI is later than a reception of the PDCCH, the first CG PUSCH occasion is the earliest CG PUSCH occasion in the first CG period, or a second UCI has been determined to be multiplexed in the first PUSCH, wherein the second UCI is used to indicate at least one unused CG PUSCH occasion in the first period.

In some example embodiments, the terminal device comprises circuitry configured to: cancel the first PUSCH based on at least one of: a first priority of the first PUSCH and a second priority of the second PUSCH are the same or there are no priorities of the first PUSCH and the second PUSCH are configured, or the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the PDCCH or the second PUSCH is not smaller than a time threshold.

In some example embodiments, the terminal device comprises circuitry configured to: in accordance with a determination that the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, determine that a minimum time duration from an end time of the PDCCH to a start time of the second PUSCH is a first value based on a gap from an end time of the first UCI to a start time of the PDCCH is smaller than a first threshold, or the DCI is received before the end time of the first UCI; or in accordance with a determination that the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, determine that a minimum time duration from an end time of the PDCCH to a start time of the second PUSCH is a second value based on the gap from the end time of the first UCI to the start time of the PDCCH is not smaller than the first threshold, or the DCI is received after the end time of the first UCI.

In some example embodiments, the second value is associated with: a preparation time for preparing the second PUSCH associated with a capability of the terminal device.

In some example embodiments, a network device comprises circuitry configured to: transmit, to a terminal device, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period; determine a first CG PUSCH occasion in the first CG period for receiving a first PUSCH; in accordance with a determination that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for receiving a second PUSCH, determine that one of the first PUSCH or the second PUSCH is to be cancelled by the terminal device based on at least one of: a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether first uplink control information (UCI) has been received, a CG PUSCH occasion used for receiving the first UCI, whether the first CG PUSCH occasion is unused, a first priority of the first PUSCH, or a second priority of the second PUSCH.

In some example embodiments, the network device comprises circuitry configured to: transmit, to the terminal device, second CG PUSCH information indicating a second number of CG PUSCH occasions in a second CG period, wherein the second transmission occasion is a second CG PUSCH occasion in the second CG period for transmitting the second PUSCH.

In some example embodiments, the network device comprises circuitry configured to: determine that the first PUSCH is to be cancelled based on a determination that: the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused, and the transmission time of an earliest CG PUSCH occasion in the first CG period is started later than a further transmission time of an earliest CG PUSCH occasion in the second CG period.

In some example embodiments, the network device comprises circuitry configured to: determine that the first PUSCH is to be cancelled based on a determination that: the first index of the first CG PUSCH information is larger than a second index of the second CG PUSCH information, and the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused.

In some example embodiments, the network device comprises circuitry configured to: determine that the first PUSCH is to be cancelled based on a determination that: the first index of the first CG PUSCH information is smaller than a second index of the second CG PUSCH information, and the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused.

In some example embodiments, the network device comprises circuitry configured to: determine that the second PUSCH is to be cancelled based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been received and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the first PUSCH or the second PUSCH is smaller than a time threshold.

In some example embodiments, the network device comprises circuitry configured to: determine that the second PUSCH is not to be cancelled based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the first PUSCH or the second PUSCH is not smaller than a time threshold.

In some example embodiments, the network device comprises circuitry configured to: determine that the second PUSCH is to be cancelled based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, and the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused.

In some example embodiments, the network device comprises circuitry configured to: in accordance with a determination that the first PUSCH is to be cancelled and a second UCI has been determined to be multiplexed in the first PUSCH, perform at least one of: receiving the second UCI being multiplexed in the second PUSCH, receiving the second UCI being multiplexed in a further PUSCH transmitted in a further CG PUSCH occasion in the first CG period, or determining that the second UCI is dropped.

In some example embodiments, the network device comprises circuitry configured to: in accordance with a determination that the first PUSCH is to be cancelled, determine the number of CG PUSCH occasions in the first CG period, wherein the number of CG PUSCH occasions do not comprise the first CG PUSCH occasion.

In some example embodiments, the network device comprises circuitry configured to: determine the number of CG PUSCH occasions in the first CG period, wherein the number of CG PUSCH occasions comprise the first CG PUSCH occasion.

In some example embodiments, the network device comprises circuitry configured to: transmit, to the terminal device, downlink control information (DCI) in a physical downlink control channel (PDCCH) scheduling the second PUSCH.

In some example embodiments, the network device comprises circuitry configured to: determine that the second PUSCH is to be cancelled based on at least one of: the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused, the first UCI has been received and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the PDCCH or the second PUSCH is smaller than a time threshold, the first UCI has been received and indicates that the first CG PUSCH occasion is unused, and a start time of the first UCI is later than a reception of the PDCCH, the first CG PUSCH occasion is the earliest CG PUSCH occasion in the first CG period, or a second UCI has been determined to be multiplexed in the first PUSCH, wherein the second UCI is used to indicate at least one unused CG PUSCH occasion in the first period.

In some example embodiments, the network device comprises circuitry configured to: determine that the first PUSCH is to be cancelled based on at least one of: a first priority of the first PUSCH and a second priority of the second PUSCH are the same or there are no priorities of the first PUSCH and the second PUSCH are configured, or the first UCI has been received and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the PDCCH or the second PUSCH is not smaller than a time threshold.

In some example embodiments, the network device comprises circuitry configured to: in accordance with a determination that the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, determine that a minimum time duration from an end time of the PDCCH to a start time of the second PUSCH is a first value based on a gap from an end time of the first UCI to a start time of the PDCCH is smaller than a first threshold, or the DCI is received before the end time of the first UCI; or in accordance with a determination that the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, determine that a minimum time duration from an end time of the PDCCH to a start time of the second PUSCH is a second value based on the gap from the end time of the first UCI to the start time of the PDCCH is not smaller than the first threshold, or the DCI is received after the end time of the first UCI.

FIG. 8 illustrates a simplified block diagram of a device 800 that is suitable for implementing embodiments of the present disclosure. The device 800 can be considered as a further example implementation of the terminal device and the network device as described above. Accordingly, the device 800 can be implemented at or as at least a part of the terminal device or the network device.

As shown, the device 800 includes a processor 810, a memory 820 coupled to the processor 810, a suitable transceiver 840 coupled to the processor 810, and a communication interface coupled to the transceiver 840. The memory 820 stores at least a part of a program 830. The transceiver 840 may be for bidirectional communications or a unidirectional communication based on requirements. The transceiver 840 may include at least one of a transmitter and a receiver. The transmitter and the receiver may be functional modules or physical entities. The transceiver840 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones. The communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /serving gateway (SGW) /user plane function (UPF) and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.

The program 830 is assumed to include program instructions that, when executed by the associated processor 810, enable the device 800 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGS. 2A-12. The embodiments herein may be implemented by computer software executable by the processor 810 of the device 800, or by hardware, or by a combination of software and hardware. The processor 810 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 810 and memory 820 may form processing means 850 adapted to implement various embodiments of the present disclosure.

The memory 820 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 820 is shown in the device 800, there may be several physically distinct memory modules in the device 800. The processor 810 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

In summary, embodiments of the present disclosure may provide the following solutions.

The present disclosure provides a terminal device, comprising at least one processor configured to cause the terminal device at least to: receive, from a network device, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period; determine a first CG PUSCH occasion in the first CG period for transmitting a first PUSCH; in accordance with a determination that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for transmitting a second PUSCH, perform the cancellation of the first PUSCH or the second PUSCH based on at least one of: a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether first uplink control information (UCI) has been transmitted, a CG PUSCH occasion used for transmitting the first UCI, whether the first CG PUSCH occasion is unused, a first priority of the first PUSCH, or a second priority of the second PUSCH.

In one embodiment, the terminal device as above, the terminal device is further caused to: receive, from the network device, second CG PUSCH information indicating a second number of CG PUSCH occasions in a second CG period, wherein the second transmission occasion is a second CG PUSCH occasion in the second CG period for transmitting the second PUSCH.

In one embodiment, the terminal device as above, the terminal device is caused to perform the cancellation by: cancelling the first PUSCH based on a determination that: the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused, and the transmission time of an earliest CG PUSCH occasion in the first CG period is started later than a further transmission time of an earliest CG PUSCH occasion in the second CG period.

In one embodiment, the terminal device as above, the terminal device is caused to perform the cancellation by: cancelling the first PUSCH based on a determination that: the first index of the first CG PUSCH information is larger than a second index of the second CG PUSCH information, and the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused.

In one embodiment, the terminal device as above, the terminal device is caused to perform the cancellation by: cancelling the first PUSCH based on a determination that: the first index of the first CG PUSCH information is smaller than a second index of the second CG PUSCH information, and the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused.

In one embodiment, the terminal device as above, the transmission time of an earliest CG PUSCH occasion in the first CG period and a further transmission time of an earliest CG PUSCH occasion in the second CG period are started in a same symbol.

In one embodiment, the terminal device as above, the terminal device is caused to perform the cancellation by: cancelling the second PUSCH based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the first PUSCH or the second PUSCH is smaller than a time threshold.

In one embodiment, the terminal device as above, the terminal device is caused to perform the cancellation by: not cancelling the second PUSCH based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the first PUSCH or the second PUSCH is not smaller than a time threshold.

In one embodiment, the terminal device as above, the terminal device is caused to perform the cancellation by: cancelling the second PUSCH based on: a predefined rule associated with a cancellation of the second PUSCH is met, and the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused.

In one embodiment, the terminal device as above, the predefined rule comprises: a first priority of the first PUSCH is higher than a second priority of the second PUSCH.

In one embodiment, the terminal device as above, the terminal device is further caused to: in accordance with a determination that the first PUSCH is to be cancelled and a second UCI has been determined to be multiplexed in the first PUSCH, perform at least one of: multiplexing the second UCI in the second PUSCH, multiplexing the second UCI in a further PUSCH transmitted in a further CG PUSCH occasion in the first CG period, or dropping the second UCI.

In one embodiment, the terminal device as above, the terminal device is further caused to: in accordance with a determination that the first PUSCH is to be cancelled, determine the number of CG PUSCH occasions in the first CG period, wherein the number of CG PUSCH occasions do not comprise the first CG PUSCH occasion.

In one embodiment, the terminal device as above, the terminal device is further caused to: determine the number of CG PUSCH occasions in the first CG period, wherein the number of CG PUSCH occasions comprise the first CG PUSCH occasion.

In one embodiment, the terminal device as above, the terminal device is further caused to: receive, from the network device, downlink control information (DCI) in a physical downlink control channel (PDCCH) scheduling the second PUSCH.

In one embodiment, the terminal device as above, the terminal device is caused to perform the cancellation by: cancelling the second PUSCH based on at least one of: the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the PDCCH or the second PUSCH is smaller than a time threshold, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a start time of the first UCI is later than a reception of the PDCCH, the first CG PUSCH occasion is the earliest CG PUSCH occasion in the first CG period, or a second UCI has been determined to be multiplexed in the first PUSCH, wherein the second UCI is used to indicate at least one unused CG PUSCH occasion in the first period.

In one embodiment, the terminal device as above, the terminal device is caused to perform the cancellation by: cancelling the first PUSCH based on at least one of: a first priority of the first PUSCH and a second priority of the second PUSCH are the same or there are no priorities of the first PUSCH and the second PUSCH are configured, or the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the PDCCH or the second PUSCH is not smaller than a time threshold.

In one embodiment, the terminal device as above, the terminal device is further caused to: in accordance with a determination that the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, determine that a minimum time duration from an end time of the PDCCH to a start time of the second PUSCH is a first value based on a gap from an end time of the first UCI to a start time of the PDCCH is smaller than a first threshold, or the DCI is received before the end time of the first UCI; or in accordance with a determination that the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, determine that a minimum time duration from an end time of the PDCCH to a start time of the second PUSCH is a second value based on the gap from the end time of the first UCI to the start time of the PDCCH is not smaller than the first threshold, or the DCI is received after the end time of the first UCI.

In one embodiment, the terminal device as above, the first value is associated with at least one of: a cancelling time for cancelling the first PUSCH, or a preparation time for preparing the second PUSCH associated with a capability of the terminal device.

In one embodiment, the terminal device as above, the second value is associated with at least one of: a preparation time for preparing the second PUSCH associated with a capability of the terminal device.

In one embodiment, the terminal device as above, the first threshold is associated with at least one of: a processing time of the first UCI by the network device, or a preparation time for scheduling the second PUSCH by the network device.

The present disclosure provides a network device, comprising at least one processor configured to cause the network device at least to: transmit, to a terminal device, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period; determine a first CG PUSCH occasion in the first CG period for receiving a first PUSCH; in accordance with a determination that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for receiving a second PUSCH, determine that one of the first PUSCH or the second PUSCH is to be cancelled by the terminal device based on at least one of: a transmission time of an earliest CG PUSCH occasion in the first CG period, a first index of the first CG PUSCH information, whether first uplink control information (UCI) has been received, a CG PUSCH occasion used for receiving the first UCI, whether the first CG PUSCH occasion is unused, a first priority of the first PUSCH, or a second priority of the second PUSCH.

In one embodiment, the network device as above, the network device is further caused to: transmit, to the terminal device, second CG PUSCH information indicating a second number of CG PUSCH occasions in a second CG period, wherein the second transmission occasion is a second CG PUSCH occasion in the second CG period for transmitting the second PUSCH.

In one embodiment, the network device as above, the network device is caused to determine that one of the first PUSCH or the second PUSCH is to be cancelled by: determining that the first PUSCH is to be cancelled based on a determination that: the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused, and the transmission time of an earliest CG PUSCH occasion in the first CG period is started later than a further transmission time of an earliest CG PUSCH occasion in the second CG period.

In one embodiment, the network device as above, the network device is caused to determine that one of the first PUSCH or the second PUSCH is to be cancelled by: determining that the first PUSCH is to be cancelled based on a determination that: the first index of the first CG PUSCH information is larger than a second index of the second CG PUSCH information, and the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused.

In one embodiment, the network device as above, the network device is caused to determine that one of the first PUSCH or the second PUSCH is to be cancelled by: determining that the first PUSCH is to be cancelled based on a determination that: the first index of the first CG PUSCH information is smaller than a second index of the second CG PUSCH information, and the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused.

In one embodiment, the network device as above, the transmission time of an earliest CG PUSCH occasion in the first CG period and a further transmission time of an earliest CG PUSCH occasion in the second CG period are started in a same symbol.

In one embodiment, the network device as above, the network device is caused to determine that one of the first PUSCH or the second PUSCH is to be cancelled by: determining that the second PUSCH is to be cancelled based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been received and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the first PUSCH or the second PUSCH is smaller than a time threshold.

In one embodiment, the network device as above, the network device is caused to determine that one of the first PUSCH or the second PUSCH is to be cancelled by: determining that the second PUSCH is not to be cancelled based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the first PUSCH or the second PUSCH is not smaller than a time threshold.

In one embodiment, the network device as above, the network device is caused to determine that one of the first PUSCH or the second PUSCH is to be cancelled by: determining that the second PUSCH is to be cancelled based on a determination that: a predefined rule associated with a cancellation of the second PUSCH is met, and the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused.

In one embodiment, the network device as above, the predefined rule comprises: a first priority of the first PUSCH is higher than a second priority of the second PUSCH.

In one embodiment, the network device as above, the network device is further caused to: in accordance with a determination that the first PUSCH is to be cancelled and a second UCI has been determined to be multiplexed in the first PUSCH, perform at least one of: receiving the second UCI being multiplexed in the second PUSCH, receiving the second UCI being multiplexed in a further PUSCH transmitted in a further CG PUSCH occasion in the first CG period, or determining that the second UCI is dropped.

In one embodiment, the network device as above, the network device is further caused to: in accordance with a determination that the first PUSCH is to be cancelled, determine the number of CG PUSCH occasions in the first CG period, wherein the number of CG PUSCH occasions do not comprise the first CG PUSCH occasion.

In one embodiment, the network device as above, the network device is further caused to: determine the number of CG PUSCH occasions in the first CG period, wherein the number of CG PUSCH occasions comprise the first CG PUSCH occasion.

In one embodiment, the network device as above, the network device is further caused to: transmit, to the terminal device, downlink control information (DCI) in a physical downlink control channel (PDCCH) scheduling the second PUSCH.

In one embodiment, the network device as above, the network device is caused to determine that one of the first PUSCH or the second PUSCH is to be cancelled by: determining that the second PUSCH is to be cancelled based on at least one of: the first UCI has not been received or the first UCI has been received and does not indicate that the first CG PUSCH occasion is unused, the first UCI has been received and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the PDCCH or the second PUSCH is smaller than a time threshold, the first UCI has been received and indicates that the first CG PUSCH occasion is unused, and a start time of the first UCI is later than a reception of the PDCCH, the first CG PUSCH occasion is the earliest CG PUSCH occasion in the first CG period, or a second UCI has been determined to be multiplexed in the first PUSCH, wherein the second UCI is used to indicate at least one unused CG PUSCH occasion in the first period.

In one embodiment, the network device as above, the network device is caused to determine that one of the first PUSCH or the second PUSCH is to be cancelled by: determining that the first PUSCH is to be cancelled based on at least one of: a first priority of the first PUSCH and a second priority of the second PUSCH are the same or there are no priorities of the first PUSCH and the second PUSCH are configured, or the first UCI has been received and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the PDCCH or the second PUSCH is not smaller than a time threshold.

In one embodiment, the network device as above, the network device is further caused to: in accordance with a determination that the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, determine that a minimum time duration from an end time of the PDCCH to a start time of the second PUSCH is a first value based on a gap from an end time of the first UCI to a start time of the PDCCH is smaller than a first threshold, or the DCI is received before the end time of the first UCI; or in accordance with a determination that the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, determine that a minimum time duration from an end time of the PDCCH to a start time of the second PUSCH is a second value based on the gap from the end time of the first UCI to the start time of the PDCCH is not smaller than the first threshold, or the DCI is received after the end time of the first UCI.

In one embodiment, the network device as above, the first value is associated with at least one of: a cancelling time for cancelling the first PUSCH, or a preparation time for preparing the second PUSCH associated with a capability of the terminal device.

In one embodiment, the network device as above, the second value is associated with a preparation time for preparing the second PUSCH associated with a capability of the terminal device.

In one embodiment, the network device as above, the first threshold is associated with at least one of: a processing time of the first UCI by the network device, or a preparation time for scheduling the second PUSCH by the network device.

The present disclosure provides a method of communication, comprising the operations implemented at the terminal device discussed above.

The present disclosure provides a method of communication, comprising the operations implemented at the network device discussed above.

The present disclosure provides a terminal device, comprising: a processor; and a memory storing computer program codes; the memory and the computer program codes configured to, with the processor, cause the terminal device to perform the method implemented at the terminal device discussed above.

The present disclosure provides a network device, comprising: a processor; and a memory storing computer program codes; the memory and the computer program codes configured to, with the processor, cause the network device to perform the method implemented at the network device discussed above.

The present disclosure provides a computer readable medium having instructions stored thereon, the instructions, when executed by a processor of an apparatus, causing the apparatus to perform the method implemented at a terminal device or a network device discussed above.

Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGS. 2-7. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

The above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

Although the present disclosure has been described in language specific to structural features and/or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

A terminal device comprising at least one processor configured to cause the terminal device at least to:

receive, from a network device, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period;

determine a first CG PUSCH occasion in the first CG period for transmitting a first PUSCH; and

in accordance with a determination that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for transmitting a second PUSCH, perform the cancellation of the first PUSCH or the second PUSCH based on at least one of:

a transmission time of an earliest CG PUSCH occasion in the first CG period,

a first index of the first CG PUSCH information,

whether first uplink control information (UCI) has been transmitted,

a CG PUSCH occasion used for transmitting the first UCI, or

whether the first CG PUSCH occasion is unused.
The terminal device of claim 1, wherein the terminal device is further caused to:

receive, from the network device, second CG PUSCH information indicating a second number of CG PUSCH occasions in a second CG period,

wherein the second transmission occasion is a second CG PUSCH occasion in the second CG period for transmitting the second PUSCH.
The terminal device of claim 2, wherein the terminal device is caused to perform the cancellation by:

cancelling the first PUSCH based on a determination that:

the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused, and

the transmission time of an earliest CG PUSCH occasion in the first CG period is started later than a further transmission time of an earliest CG PUSCH occasion in the second CG period.
The terminal device of claim 2, wherein the terminal device is caused to perform the cancellation by:

cancelling the first PUSCH based on a determination that:

the first index of the first CG PUSCH information is larger than a second index of the second CG PUSCH information, and

the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused.
The terminal device of claim 2, wherein the terminal device is caused to perform the cancellation by:

cancelling the first PUSCH based on a determination that:

the first index of the first CG PUSCH information is smaller than a second index of the second CG PUSCH information, and

the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused.
The terminal device of claim 2, wherein the terminal device is caused to perform the cancellation by:

cancelling the second PUSCH based on a determination that:

a predefined rule associated with a cancellation of the second PUSCH is met,

the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and

a gap from an end time of the first UCI to a start time of the first PUSCH or the second PUSCH is smaller than a time threshold.
The terminal device of claim 2, wherein the terminal device is caused to perform the cancellation by:

not cancelling the second PUSCH based on a determination that:

a predefined rule associated with a cancellation of the second PUSCH is met,

the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and

a gap from an end time of the first UCI to a start time of the first PUSCH or the second PUSCH is not smaller than a time threshold.
The terminal device of claim 2, wherein the terminal device is caused to perform the cancellation by:

cancelling the second PUSCH based on:

a predefined rule associated with a cancellation of the second PUSCH is met, and

the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused.
The terminal device of any of claims 6-8, wherein the predefined rule comprises:

a first priority of the first PUSCH is higher than a second priority of the second PUSCH.
The terminal device of claim 2, wherein the terminal device is further caused to:

in accordance with a determination that the first PUSCH is to be cancelled and a second UCI has been determined to be multiplexed in the first PUSCH, perform at least one of:

multiplexing the second UCI in the second PUSCH,

multiplexing the second UCI in a further PUSCH transmitted in a further CG PUSCH occasion in the first CG period, or

dropping the second UCI.
The terminal device of claim 1, wherein the terminal device is further caused to:

in accordance with a determination that the first PUSCH is to be cancelled, determine the number of CG PUSCH occasions in the first CG period, wherein the number of CG PUSCH occasions do not comprise the first CG PUSCH occasion.
The terminal device of claim 1, wherein the terminal device is further caused to:

receive, from the network device, downlink control information (DCI) in a physical downlink control channel (PDCCH) scheduling the second PUSCH.
The terminal device of claim 12, wherein the terminal device is caused to perform the cancellation by:

cancelling the second PUSCH based on at least one of:

the first UCI has not been transmitted or the first UCI has been transmitted and does not indicate that the first CG PUSCH occasion is unused,

the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the PDCCH or the second PUSCH is smaller than a time threshold,

the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a start time of the first UCI is later than a reception of the PDCCH,

the first CG PUSCH occasion is the earliest CG PUSCH occasion in the first CG period, or

a second UCI has been determined to be multiplexed in the first PUSCH, wherein the second UCI is used to indicate at least one unused CG PUSCH occasion in the first period.
The terminal device of claim 12, wherein the terminal device is caused to perform the cancellation by:

cancelling the first PUSCH based on at least one of:

a first priority of the first PUSCH and a second priority of the second PUSCH are the same or there are no priorities of the first PUSCH and the second PUSCH are configured, or

the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, and a gap from an end time of the first UCI to a start time of the PDCCH or the second PUSCH is not smaller than a time threshold.
The terminal device of claim 12, wherein the terminal device is further caused to:

in accordance with a determination that the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, determine that a minimum time duration from an end time of the PDCCH to a start time of the second PUSCH is a first value based on a gap from an end time of the first UCI to a start time of the PDCCH is smaller than a first threshold, or the DCI is received before the end time of the first UCI; or

in accordance with a determination that the first UCI has been transmitted and indicates that the first CG PUSCH occasion is unused, determine that a minimum time duration from an end time of the PDCCH to a start time of the second PUSCH is a second value based on the gap from the end time of the first UCI to the start time of the PDCCH is not smaller than the first threshold, or the DCI is received after the end time of the first UCI.
The terminal device of claim 15, wherein the first value is associated with at least one of:

a cancelling time for cancelling the first PUSCH, or

a preparation time for preparing the second PUSCH associated with a capability of the terminal device.
A network device comprising at least one processor configured to cause the network device at least to:

transmit, to a terminal device, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period;

determine a first CG PUSCH occasion in the first CG period for receiving a first PUSCH; and

in accordance with a determination that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for receiving a second PUSCH, determine that one of the first PUSCH or the second PUSCH is to be cancelled by the terminal device based on at least one of:

a transmission time of an earliest CG PUSCH occasion in the first CG period,

a first index of the first CG PUSCH information,

whether first uplink control information (UCI) has been received,

a CG PUSCH occasion used for receiving the first UCI, or

whether the first CG PUSCH occasion is unused.
A method of communication, comprising:

receiving, at a terminal device from a network device, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period;

determining a first CG PUSCH occasion in the first CG period for transmitting a first PUSCH; and

in accordance with a determination that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for transmitting a second PUSCH, performing the cancellation of the first PUSCH or the second PUSCH based on at least one of:

a transmission time of an earliest CG PUSCH occasion in the first CG period,

a first index of the first CG PUSCH information,

whether first uplink control information (UCI) has been transmitted,

a CG PUSCH occasion used for transmitting the first UCI, or

whether the first CG PUSCH occasion is unused.
A method of communication, comprising:

transmitting, at a network device to a terminal device, first configured grant (CG) physical uplink shared channel (PUSCH) information indicating a first number of CG PUSCH occasions in a first CG period;

determining a first CG PUSCH occasion in the first CG period for receiving a first PUSCH; and

in accordance with a determination that the first CG PUSCH occasion is to be overlapped with a second transmission occasion for receiving a second PUSCH, determining that one of the first PUSCH or the second PUSCH is to be cancelled by the terminal device based on at least one of:

a transmission time of an earliest CG PUSCH occasion in the first CG period,

a first index of the first CG PUSCH information,

whether first uplink control information (UCI) has been received,

a CG PUSCH occasion used for receiving the first UCI, or

whether the first CG PUSCH occasion is unused.
A computer readable medium having instructions stored thereon, the instructions, when executed by a processor of an apparatus, causing the apparatus to perform the method according to any of claims 18-19.