Terminal device, method and computer readable medium for communication
Patent Information
- Application Number
- PCT/CN2025/084807
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-03-25
- Publication Date
- 2026-10-01
Smart Images

Figure CN2025084807_01102026_PF_FP_ABST
Abstract
Description
TERMINAL DEVICE, METHOD AND COMPUTER READABLE MEDIUM FOR COMMUNICATIONTECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to a terminal device, method and computer readable medium for communication.BACKGROUND
[0002] In the fifth generation (5G) systems, uplink control information (UCI) transmission, especially the UCI multiplexing / overlap procedure, is complexed. There is also an observation that in many deployments, majority UCI is transmitted on physical uplink shared channel (PUSCH) due to lots of uplink (UL) traffics. Therefore, it is necessary to simplify UCI transmission so as to reduce the UCI multiplexing / overlap procedure complexity in the sixth generation (6G) systems.SUMMARY
[0003] In general, example embodiments of the present disclosure provide a terminal device, method and computer readable medium for communication.
[0004] In a first aspect, there is provided a terminal device. The terminal device comprises a processor. The processor is configured to cause the terminal device to: determine one or more uplink control information (UCI) sets, wherein each of the one or more UCI sets comprises one or more UCI types, each of the one or more UCI types is assigned with a priority, physical uplink control channel (PUCCH) resources for the one or more UCI sets are overlapped in time domain; determine at least one non-overlapped PUCCH resource based on one or more priorities of the one or more UCI sets; and transmit at least one of the one or more UCI sets to a network device on the at least one non-overlapped PUCCH resource.
[0005] In a second aspect, there is provided a method for communication. The method comprises: determining one or more UCI sets, wherein each of the one or more UCI sets comprises one or more UCI types, each of the one or more UCI types is assigned with a priority, PUCCH resources for the one or more UCI sets are overlapped in time domain; determining at least one non-overlapped PUCCH resource based on one or more priorities of the one or more UCI sets; and transmitting at least one of the one or more UCI sets to a network device on the at least one non-overlapped PUCCH resource.
[0006] In a third aspect, there is provided a computer readable medium having instructions stored thereon. The instructions, when executed on at least one processor of a device, cause the device to perform the method according to the second aspect.
[0007] 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
[0008] Through the more detailed description of some 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:
[0009] Fig. 1 illustrate an example communication network in which embodiments of the present disclosure can be implemented;
[0010] Fig. 2 illustrates a flowchart of an example method in accordance with some embodiments of the present disclosure;
[0011] Fig. 3 illustrates an example of transmission of UCI sets in accordance with some embodiments of the present disclosure;
[0012] Fig. 4 illustrates an example of transmission of UCI sets in accordance with some embodiments of the present disclosure; and
[0013] Fig. 5 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
[0014] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0015] 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 limitations as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.
[0016] 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.
[0017] As used herein, the term “terminal device” refers to any device having wireless or wired communication capabilities. Examples of the 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) , Small Data Transmission (SDT) , mobility, Multicast and Broadcast Services (MBS) , positioning, dynamic / flexible duplex in commercial networks, reduced capability (RedCap) , 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 incorporate 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.
[0018] 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 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) , Network-controlled Repeaters, and the like.
[0019] 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.
[0020] The terminal 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 devices 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.
[0021] The network device may have the function of network energy saving, Self-Organizing Networks (SON) / Minimization of Drive Tests (MDT) . The terminal may have the function of power saving.
[0022] 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, channel emulator.
[0023] 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.
[0024] 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 ‘at least in part based on. ’ The term ‘some embodiments’ and ‘an embodiment’ are to be read as ‘at least some embodiments. ’ 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.
[0025] 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.
[0026] Fig. 1 illustrates a schematic diagram of an example communication network 100 in which embodiments of the present disclosure can be implemented. As shown in Fig. 1, the communication network 100 comprises a network device 120 and terminal devices 110-1, 110-2…, 110-N served by the network device 120. The serving area of the network device 120 is called as a cell 102. Hereinafter, the terminal devices 110-1, 110-2…, 110-N may be collectively referred to as “terminal devices 110” or individually referred to as “aterminal devices 110” .
[0027] It is to be understood that the number of network devices and terminal devices is only for the purpose of illustration without suggesting any limitations. The communication network 100 may comprise any suitable number of network devices and terminal devices adapted for implementing embodiments of the present disclosure.
[0028] As described above, in the 5G systems, UCI transmission, especially the UCI multiplexing / overlap procedure, is complexed. Hereinafter, some embodiments of UCI transmission will be described.
[0029] In some embodiments, if a UE would transmit multiple overlapping PUCCHs in a slot or overlapping PUCCH (s) and PUSCH (s) in a slot and, when applicable as described in clauses 9.2.5.1, 9.2.5.2, 9.2.5.3 and 18 of TS 38.213, the UE is configured to multiplex different UCI types or UCI of different priority indexes in one PUCCH, and at least one of the multiple overlapping PUCCHs or PUSCHs is in response to a DCI format detection by the UE, the UE multiplexes all corresponding UCI types or UCI of different priority indexes if the following conditions are met. If one of the PUCCH transmissions or PUSCH transmissions is in response to a DCI format detection by the UE, the UE expects that the first symbol S0 of the earliest PUCCH or PUSCH, among a group overlapping PUCCHs and PUSCHs in the slot, satisfies the following timeline conditions: - S0 is not before a symbol with CP starting after after a last symbol of any corresponding PDSCH, is given by maximum of where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, d1, 1 is selected for the i-th PDSCH following TS 38.214, N1 is selected based on the UE PDSCH processing capability of the i-th PDSCH and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH scheduling the i-th PDSCH if any, the i-th PDSCH, the PUCCH with corresponding HARQ-ACK transmission for the i-th PDSCH, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. - S0 is not before a symbol with CP starting after after a last symbol of a PDCCH reception providing a DCI format having associated HARQ-ACK information without scheduling a PDSCH reception. is given by maximum of where for the i-th PDCCH providing the DCI format with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, N as described in clause 10.2, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH, the PUCCH with corresponding HARQ-ACK information, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. - if there is no aperiodic CSI report multiplexed in a PUSCH in the group of overlapping PUCCHs and PUSCHs, S0 is not before a symbol with CP starting after after a last symbol of - any PDCCH with the DCI format scheduling an overlapping PUSCH, and - any PDCCH providing a DCI format with corresponding HARQ-ACK information in an overlapping PUCCH in the slot; - if there is at least one PUSCH in the group of overlapping PUCCHs and PUSCHs, is given by maximum of where for the i-th PUSCH which is in the group of overlapping PUCCHs and PUSCHs, d2, 1, d2, 2 and Tswitch are selected for the i-th PUSCH following TS 38.214, N2 is selected based on the UE PUSCH processing capability of the i-th PUSCH and SCS configuration μ, where μ corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH scheduling the i-th PUSCH, the PDCCHs scheduling the PDSCHs, or providing the DCI formats without scheduling PDSCHs, with corresponding HARQ-ACK information on a PUCCH which is in the group of overlapping PUCCHs / PUSCHs, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. - if there is no PUSCH in the group of overlapping PUCCHs and PUSCHs, is given by maximum of where for the i-th PDSCH, or the i-th PDCCH providing a DCI format without scheduling PDSCH, with corresponding HARQ-ACK information on a PUCCH which is in the group of overlapping PUCCHs, N2 is selected based on the UE PUSCH processing capability of the PUCCH serving cell if configured. N2 is selected based on the UE PUSCH processing capability 1, if PUSCH processing capability is not configured for the PUCCH serving cell. μ is selected based on the smallest SCS configuration between the SCS configuration used for the PDCCH scheduling the i-th PDSCH, or providing the i-th DCI format without scheduling PDSCH, with corresponding HARQ-ACK information on a PUCCH which is in the group of overlapping PUCCHs, and the SCS configuration for the PUCCH serving cell. - if there is an aperiodic CSI report multiplexed in a PUSCH in the group of overlapping PUCCHs and PUSCHs, S0 is not before a symbol with CP starting after after a last symbol of - any PDCCH with the DCI format scheduling an overlapping PUSCH, and - any PDCCH scheduling a PDSCH, or providing a DCI format, with corresponding HARQ-ACK information in an overlapping PUCCH in the slot, where μ corresponds to the smallest SCS configuration among the SCS configuration of the PDCCHs, the smallest SCS configuration for the group of the overlapping PUSCHs, and the smallest SCS configuration of CSI-RS associated with the DCI format scheduling the PUSCH with the multiplexed aperiodic CSI report, and d=2 for μ=0, 1, d=3 for μ=2, and d=4 for μ≥3. Tswitch is defined in TS 38.214 and it is applied only if Z1 of Table 5.4-1 in TS 38.214 is applied to the determination of Z. - N1, N2, d1, 1, d2, 1, d2, 2, and Z are defined in TS 38.214 and κ and TC are defined in TS 38.211.
[0030] If a UE would transmit multiple overlapping PUCCHs in a slot or overlapping PUCCH (s) and PUSCH (s) in a slot, one of the PUCCHs includes HARQ-ACK information in response to an SPS PDSCH reception, and any PUSCH is not in response to a DCI format detection, the UE expects that the first symbol S0 of the earliest PUCCH or PUSCH satisfies the first of the previous timeline conditions with the exception that components associated to a SCS configuration for a PDCCH scheduling a PDSCH or a PUSCH are absent from the timeline conditions.
[0031] A UE does not expect a PUCCH or a PUSCH that is in response to a DCI format detection to overlap with any other PUCCH or PUSCH that does not satisfy the above timing conditions.
[0032] Hereinafter, some embodiments of PUCCH Formats for UCI transmission will be described.
[0033] If a UE is not transmitting PUSCH, and the UE is transmitting UCI, the UE transmits UCI in a PUCCH using - PUCCH format 0 if - the transmission is over 1 symbol or 2 symbols, - the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is 1 or 2 - PUCCH format 1 if - the transmission is over 4 or more symbols, - the number of HARQ-ACK / SR bits is 1 or 2 - PUCCH format 2 if - the transmission is over 1 symbol or 2 symbols, - the number of UCI bits is more than 2 - PUCCH format 3 if - the transmission is over 4 or more symbols, - the number of UCI bits is more than 2, - the PUCCH resource does not include an orthogonal cover code, or the UE is provided useInterlacePUCCH-PUSCH in BWP-UplinkDedicated - PUCCH format 4 if - the transmission is over 4 or more symbols, - the number of UCI bits is more than 2, - the PUCCH resource includes an orthogonal cover code and the UE is not provided useInterlacePUCCH-PUSCH in BWP-UplinkDedicated.
[0034] In some embodiments, one or more overlapping rules for UCI transmissions may be applied.
[0035] When a UE determines overlapping for PUCCH and / or PUSCH transmissions of the same priority index other than PUCCH transmissions with SL HARQ-ACK reports before considering limitations for UE transmission due to cell DRX operation in TS 38.321 or as described in clauses 11.1, 11.1.1, 11.2A, 15 and 17.2 including repetitions if any, - first, the UE resolves the overlapping for PUCCHs with repetitions as described in clause 9.2.6, if any - second, the UE resolves the overlapping for PUCCHs without repetitions as described in clauses 9.2.5 - third, the UE resolves the overlapping for PUSCHs and PUCCHs with repetitions as described in clause 9.2.6 - fourth, the UE resolves the overlapping for PUSCHs and PUCCHs without repetitions as is subsequently described in this clause.
[0036] In some embodiments, regarding PUCCH repetition procedure, a UE does not multiplex different UCI types in a PUCCH transmission with repetitions over slots. If a UE would transmit a first PUCCH over more than one slot and at least a second PUCCH over one or more slots, and the transmissions of the first PUCCH and the second PUCCH would overlap in a number of slots then, for each slot of the number of slots and with UCI type priority of HARQ-ACK > SR > CSI with higher priority > CSI with lower priority, the UE determines an earliest first PUCCH in a slot with the order of earliest starting symbol followed by longest duration and the second PUCCHs overlapping with the earliest first PUCCH, and then performs the following - the UE does not expect more than one PUCCH from the first PUCCH and the second PUCCHs to start at a same slot and include a UCI type with same priority - if more than one PUCCH from the first PUCCH and the second PUCCHs include a UCI type with the same highest priority, the UE transmits the PUCCH with the highest priority starting at an earliest slot and does not transmit the other PUCCHs, otherwise, - the UE transmits the PUCCH that includes the UCI type with the highest priority and does not transmit the PUCCHs that include the UCI type with lower priority.
[0037] The UE repeats the above procedure until there is no PUCCH overlapping with any PUCCH with repetitions in the slot.
[0038] In some embodiments, regarding UE procedure for reporting multiple UCI types, This clause is applicable to the case that a UE has resources for PUCCH transmissions or for PUCCH and PUSCH transmissions that overlap in time and each PUCCH transmission is over a single slot without repetitions. Any case that a PUCCH transmission is with repetitions over multiple slots is described in clause 9.2.6. If a UE is configured with multiple PUCCH resources in a slot to transmit CSI reports - if the UE is not provided multi-CSI-PUCCH-ResourceList or if PUCCH resources for transmissions of CSI reports do not overlap in the slot, the UE determines a first resource corresponding to a CSI report with the highest priority as specified in TS 38.214 - if the first resource includes PUCCH format 2, and if there are remaining resources in the slot that do not overlap with the first resource, the UE determines a CSI report with the highest priority, among the CSI reports with corresponding resources from the remaining resources, and a corresponding second resource as an additional resource for CSI reporting - if the first resource includes PUCCH format 3 or PUCCH format 4, and if there are remaining resources in the slot that include PUCCH format 2 and do not overlap with the first resource, the UE determines a CSI report with the highest priority, among the CSI reports with corresponding resources from the remaining resources, and a corresponding second resource as an additional resource for CSI reporting - if the UE is provided multi-CSI-PUCCH-ResourceList and if any of the multiple PUCCH resources overlap, the UE multiplexes all CSI reports in a resource from the resources provided by multi-CSI-PUCCH-ResourceList, as described in clause 9.2.5.2 of TS 38.213.
[0039] In some embodiments, non-repetition PUCCH Q may be determined.
[0040] In some embodiments, set Q to the set of resources for transmission of corresponding PUCCHs in a single slot without repetitions where - a resource with earlier first symbol is placed before a resource with later first symbol - for two resources with same first symbol, the resource with longer duration is placed before the resource with shorter duration - for two resources with same first symbol and same duration, the placement is arbitrary - the above three steps for the set Q are according to a subsequent pseudo- code for a function order (Q) - a resource for negative SR transmission that does not overlap with a resource for HARQ-ACK or CSI transmission is excluded from set Q - if the UE is not provided simultaneousHARQ-ACK-CSI and resources for transmission of HARQ-ACK information include PUCCH format 0 or PUCCH format 2, resources that include PUCCH format 2, or PUCCH format 3, or PUCCH format 4 for transmission of CSI reports are excluded from the set Q if they overlap with any resource from the resources for transmission of HARQ-ACK information - if the UE is not provided simultaneousHARQ-ACK-CSI and at least one of the resources for transmission of HARQ-ACK information includes PUCCH format 1, PUCCH format 3, or PUCCH format 4 - resources that include PUCCH format 3 or PUCCH format 4 for transmission of CSI reports are excluded from the set Q - resources that include PUCCH format 2 for transmission of CSI reports are excluded from the set Q if they overlap with any resource from the resources for transmission of HARQ-ACK information.
[0041] In some embodiments, Set C (Q) to the cardinality of Q Set Q (j, 0) to be the first symbol of resource Q (j) in the slot Set L (Q (j) ) to be the number of symbols of resource Q (j) in the slot Set j=0 -index of first resource in set Q Set o=0 -counter of overlapped resources while j≤C (Q) -1
[0042] In some embodiments, a UE may handle PUCCH repetition overlapped with PUSCH as below.
[0043] If a UE would transmit a PUCCH over a first number of slots and the UE would transmit a PUSCH with repetition Type A or with TB processing over multiple slots over a second number of slots, and the PUCCH transmission would overlap with the PUSCH transmission in one or more slots, and the conditions in clause 9.2.5 for multiplexing the UCI in the PUSCH are satisfied in the overlapping slots, the UE transmits the PUCCH and does not transmit the PUSCH in the overlapping slots.
[0044] If a UE would transmit a PUCCH over a first number of slots and the UE would transmit a PUSCH with repetition Type B over a second number of slots, and the PUCCH transmission would overlap with actual PUSCH repetitions in one or more slots, and the conditions in clause 9.2.5 for multiplexing the UCI in the PUSCH are satisfied for the overlapping actual PUSCH repetitions, the UE transmits the PUCCH and does not transmit the overlapping actual PUSCH repetitions.
[0045] In some embodiments, a UE may determine PUSCH for UCI multiplexing as below.
[0046] When a UE transmits multiple PUSCHs on respective serving cells in a slot with reference to slots for PUCCH transmissions and the multiple PUSCHs overlap with a PUCCH carrying UCI in the slot, the UE selects all the PUSCHs overlapping with the PUCCH as the candidate PUSCHs for UCI multiplexing within the slot.
[0047] If a UE would transmit a single PUSCH scheduled by a DCI format that includes a DAI field on a serving cell in a slot with reference to slots for PUCCH transmissions without any other PUSCH that would be transmitted on any serving cell in the slot and the UE does not determine any PUCCH carrying HARQ-ACK information in the slot, or if the UE indicates the corresponding capability mux-HARQ-ACK-withoutPUCCH-onPUSCH and the UE transmits multiple PUSCHs on respective serving cells in a slot with reference to slots for PUCCH transmissions and the UE does not determine any PUCCH carrying HARQ-ACK information in the slot and at least one of the multiple PUSCHs is scheduled by a DCI format that includes a DAI field, the UE selects the single PUSCH or all the multiple PUSCHs in the slot as the candidate PUSCHs for HARQ-ACK multiplexing within the slot except for any PUSCH among the multiple PUSCHs that is scheduled by a DCI format that indicates a DAI value that is equal to 4 for each DAI value indicated by 2 bits, if any, and is equal to 0 for each DAI value indicated by 1 bit, if any.
[0048] The UE determines the PUSCH for UCI multiplexing by applying the following procedure on the candidate PUSCHs as described in this clause: - If the candidate PUSCHs that include first PUSCHs that are scheduled by DCI formats and second PUSCHs configured by respective ConfiguredGrantConfig or semiPersistentOnPUSCH, and the UE would multiplex UCI in one of the candidate PUSCHs, and the candidate PUSCHs fulfil the conditions in clause 9.2.5 for UCI multiplexing, the UE multiplexes the UCI in a PUSCH from the first PUSCHs. - If the UE would multiplex UCI in one of the candidate PUSCHs and the UE does not multiplex aperiodic CSI in any of the candidate PUSCHs, the UE multiplexes the UCI in a PUSCH of the serving cell with the smallest ServCellIndex subject to the conditions in clause 9.2.5 for UCI multiplexing being fulfilled. If the UE transmits more than one PUSCHs in the slot on the serving cell with the smallest ServCellIndex that fulfil the conditions in clause 9.2.5 for UCI multiplexing, the UE multiplexes the UCI in the earliest PUSCH that the UE transmits in the slot.
[0049] If a UE transmits a PUSCH over one or more slots or multiple PUSCHs over one or more slots that are scheduled by a DCI format, and the UE would transmit a PUCCH with HARQ-ACK and / or CSI information over a single slot that overlaps with the PUSCH transmission in the one or more slots, and the PUSCH transmission in the one or more slots fulfills the conditions in clause 9.2.5 for multiplexing the HARQ-ACK and / or CSI information, the UE multiplexes the HARQ-ACK and / or CSI information in the PUSCH transmission in the one or more slots. The UE does not multiplex HARQ-ACK and / or CSI information in the PUSCH transmission in a slot from the one or more slots if the UE would not transmit a single-slot PUCCH with HARQ-ACK and / or CSI information in the slot in case the PUSCH transmission was absent.
[0050] If a UE transmits a PUSCH with repetition Type B and the UE would transmit a PUCCH with HARQ-ACK and / or CSI information over a single slot that overlaps with the PUSCH transmission in one or more slots, the UE expects all actual repetitions of the PUSCH transmission as specified in TS 38.214 that would overlap with the PUCCH transmission to fulfill the conditions in clause 9.2.5 for multiplexing the HARQ-ACK and / or CSI information, and the UE multiplexes the HARQ-ACK and / or CSI information in the earliest actual PUSCH repetition of the PUSCH transmission that would overlap with the PUCCH transmission and includes more than one symbol. The UE does not expect that all actual repetitions that would overlap with the PUCCH transmission do not include more than one symbol.
[0051] If a UE would transmit on a serving cell a PUSCH without UL-SCH that overlaps with a PUCCH transmission on a serving cell that includes positive SR information, the UE does not transmit the PUSCH.
[0052] If a UE would transmit CSI reports on overlapping physical channels, the UE applies the priority rules described in [6, TS 38.214] for the multiplexing of CSI reports.
[0053] If a UE - would multiplex UCI in a PUCCH transmission that overlaps with a PUSCH transmission, and - the PUSCH and PUCCH transmissions fulfil the conditions in clause 9.2.5 for UCI multiplexing, the UE - multiplexes only HARQ-ACK information, if any, from the UCI in the PUSCH transmission and does not transmit the PUCCH if the UE multiplexes aperiodic or semi-persistent CSI reports in the PUSCH; - multiplexes only HARQ-ACK information and CSI reports, if any, from the UCI in the PUSCH transmission and does not transmit the PUCCH if the UE does not multiplex aperiodic or semi-persistent CSI reports in the PUSCH.
[0054] If a UE multiplexes aperiodic CSI in a PUSCH and the UE would multiplex UCI that includes HARQ-ACK information in a PUCCH that overlaps with the PUSCH and the timing conditions for overlapping PUCCHs and PUSCHs in clause 9.2.5 are fulfilled, the UE multiplexes only the HARQ-ACK information in the PUSCH and does not transmit the PUCCH.
[0055] Therefore, the UCI multiplexing / overlap procedure in 5G system is complexed.
[0056] In view of the above, embodiments of the present disclosure provide a solution for communication. In this solution, a terminal device determines one or more UCI sets. Each of the one or more UCI sets comprises one or more UCI types. Each of the one or more UCI types is assigned with a priority. PUCCH resources for the one or more UCI sets are overlapped in time domain. The terminal device determines at least one non-overlapped PUCCH resource based on one or more priorities of the one or more UCI sets. In turn, the terminal device transmits at least one of the one or more UCI sets to a network device on the at least one non-overlapped PUCCH resource. With this solution, one or more UCI types may be combined into one UCI set. Therefore, the overlapped occasions for PUCCH resources for one or more UCI sets may be reduced.
[0057] Hereinafter, principle of the present disclosure will be described with reference to Figs. 2 to 5.
[0058] Fig. 2 illustrates a flowchart of an example method 200 in accordance with some embodiments of the present disclosure. In some embodiments, the method 200 can be implemented at a terminal device, such as the terminal device 110 as shown in Fig. 1. For the purpose of discussion, the method 200 will be described with reference to Fig. 1 as performed by the terminal device 110 without loss of generality.
[0059] At block 210, the terminal device 110 determines one or more UCI sets. Each of the one or more UCI sets comprises one or more UCI types. Each of the one or more UCI types is assigned with a priority. PUCCH resources for the one or more UCI sets are overlapped in time domain.
[0060] At block 220, the terminal device 110 determines at least one non-overlapped PUCCH resource based on one or more priorities of the one or more UCI sets.
[0061] At block 230, the terminal device 110 transmits at least one of the one or more UCI sets to the network device 120 on the at least one non-overlapped PUCCH resource.
[0062] With the method 200, one or more UCI types may be combined into one UCI set. Therefore, the overlapped occasions for PUCCH resources for one or more UCI sets may be reduced.
[0063] In some embodiments, the one or more UCI types comprise one or more UCI types which are generated by artificial intelligence (AI) or machine learning (ML) functionality, or generated by AI or ML model at the side of the terminal device 110.
[0064] In some embodiments, the one or more UCI types which are generated by AI or ML functionality or generated by AI or ML model may comprise at least one of the following: ● AI / ML based hybrid automatic repeat request acknowledgment (HARQ-ACK) information, which may be one or more predicted HARQ-ACK information of future scheduling downlink (DL) transmissions, including dynamic (dynamic grant (DG) ) scheduling DL transmissions, semi-persistent (configured grant (CG) ) scheduling DL transmissions and periodic scheduling DL transmissions ● AI / ML based scheduling request (SR) or link recovery request (LRR) , which may be predicted SR of future UL transmissions or LRR of future beam / link failure's recovery request or other set of beams / links' recovery request ● AI / ML based channel state information (CSI) report ● AI / ML data collection request for an AI / ML functionality's model training and / or inference and / or monitoring ● AI / ML performance monitoring output for an AI / ML functionality / model ● Other proper AI / ML life cycle management (LCM) related information ● Other proper AI / ML service related UCI.
[0065] In some embodiments, the one or more UCI types comprise one or more UCI types which are generated by a sensing transmitter or sensing receiver.
[0066] In some embodiments, the one or more UCI types which are generated by the sensing transmitter or sensing receiver may comprise at least one of the following: ● sensing result needs to be informed to the network ● intermedium sensing output or assistant sensing data needs to be informed to network for final calculation of the sensing result at network ● sensing resource request which is used to request network to allocate sensing resources for sensing signal transmission of the sensing transmitter ● other proper sensing related measurements ● other proper sensing related information.
[0067] In some embodiments, the one or more UCI sets may be determined based on one or more features of the one or more UCI types.
[0068] For example, UCI set 0 may comprise all HARQ-ACK related information, e.g., {HARQ-ACK, AI / ML HARQ-ACK, etc. } ; UCI set 1 may comprise all SR related information, e.g., {SR, LRR, AL / ML data collection SR, ISAC resource SR, etc. } ; UCI set 2 may comprise all CSI related information, e.g., {CSI, AI / ML CSI, ISAC measurements, etc. } .
[0069] Alternatively or additionally, in some embodiments, the one or more UCI sets may be determined based on one or more priorities of the one or more UCI types. Some embodiments of determining a priority of a UCI type will be described later.
[0070] For example, UCI set 0 may comprise one or more UCI types with priority values {0, x} , UCI set 1 may comprise one or more UCI types with priority values {x+1, y} , UCI set 2 may comprise one or more UCI types with priority values {y+1, m} , and so on. For example, x and y may be equal to 0 and 1 respectively, or other proper values, m may be the largest priority value.
[0071] Alternatively or additionally, in some embodiments, the one or more UCI sets may be determined based on a payload size of the one or more UCI types.
[0072] For example, UCI set 0 may comprise one or more UCI types with a payload size of 1 to 2 bits, UCI set 1 may comprise one or more UCI types with a payload size greater than 2 bits, and so on.
[0073] Alternatively or additionally, in some embodiments, the one or more UCI sets may be determined based on predefinition or configuration.
[0074] For example, based on predefinition or radio resource control (RRC) configuration, UCI set 0 may comprise HARQ related information, LRR and SR; UCI set 1 may comprise CSI with higher priority; UCI set 2 may comprise CSI with lower priority; UCI set 3 may comprise AI / ML related UCI; UCI set 4 may comprise ISAC related UCI and so on.
[0075] In some embodiments, the terminal device 110 may be configured with non-overlapped PUCCH or PUSCH resources. In such embodiments, the terminal device 110 may transmit the one or more UCI sets on the non-overlapped PUCCH or PUSCH resources. This will be described with reference to Fig. 3.
[0076] Fig. 3 illustrates an example of transmission of UCI sets in accordance with some embodiments of the present disclosure. In the example of Fig. 3, a UCI set 0 comprises a UCI type 1, a UCI type 2 and a UCI type 3, and a UCI set 1 comprises one or more UCI types. The terminal device 110 may transmit the UCI set 0 on a PUCCH resource 0 in a slot and transmit the UCI set 1 on a PUCCH resource 1 in the slot. The PUCCH resource 0 and the PUCCH resource 1 are non-overlapped PUCCH resources.
[0077] In some embodiments, the terminal device 110 may be configured with PUCCH or PUSCH resources which satisfy a timeline condition or a payload condition. Alternatively, the terminal device 110 may select an earliest one of PUCCH or PUSCH resources which satisfy a timeline condition or a payload condition. In turn, the terminal device 110 may transmit a first UCI set among the one or more UCI sets on the earliest one of PUCCH or PUSCH resources which satisfy the timeline condition or the payload condition.
[0078] In some embodiments, all of the one or more UCI types in the first UCI set is prepared before at least one time offset before a starting symbol of the earliest one of PUCCH or PUSCH resources which satisfy the timeline condition.
[0079] In some embodiments, the at least one time offset may be determined from the maximum time offset from the multiple time offsets configured for different feature, service or UCI types respectively.
[0080] In some embodiments, in order to transmit the first UCI set, the terminal device 110 may multiplex one or more UCI types in the first UCI set. For example, the terminal device 110 may prepend or append one UCI type to another UCI type, or perform joint coding of the one or more UCI types in the first UCI set. Then, the terminal device 110 may transmit the multiplexed one or more UCI types in the first UCI set on the earliest one of PUCCH or PUSCH resources.
[0081] In some embodiments, if PUCCH resources for multiple UCI sets are overlapped in time domain, the terminal device 110 may transmit only one or more UCI sets among the multiple UCI sets for which PUCCH resources are non-overlapped in time domain. Hereinafter, if PUCCH resources for one or more UCI sets are non-overlapped in time domain, the one or more UCI sets are referred to as one or more non-overlapped UCI sets. If PUCCH resources for one or more UCI sets are overlapped in time domain, the one or more UCI sets are referred to as one or more overlapped UCI sets.
[0082] In some embodiments, the terminal device 110 may select, from the multiple UCI sets, the one or more UCI sets for transmission based on one or more priorities of the one or more UCI sets. The terminal device 110 may firstly select a UCI set with the highest priority, and then select another UCI set with the highest priority from the remaining non-overlapped UCI sets. The remaining non-overlapped UCI sets refer to remaining UCI sets for which PUCCH resources are not overlapped with a PUCCH resource for the firstly selected UCI set.
[0083] In some embodiments, the terminal device 110 may determine one or more priorities of the one or more UCI sets based on predefinition or configuration. For example, the predefinition may be that a UCI set has the highest priority if it contains a maximum number of UCI types based on following searching order: HARQ-ACK > SR > CSI > AIML UCI >=ISAC UCI. It shall be noted this is just an example of the searching order and other searching order among UCI types may be predefined.
[0084] In some embodiments, each of one or more UCI types in a UCI set may be assigned with a priority. The terminal device 110 may determine a priority of the UCI set as a highest one of the one or more priorities of the one or more UCI types in the UCI set. Some embodiments of determining a priority of a UCI type will be described later.
[0085] Alternatively or additionally, in some embodiments, the terminal device 110 may select, from the multiple UCI sets, the one or more UCI sets for transmission based on time when the one or more UCI sets are prepared for transmission. For example, the terminal device 110 may firstly select one earliest UCI set, and then select another earliest UCI set from the remaining non-overlapped UCI sets. The remaining non-overlapped UCI sets refer to remaining UCI sets for which PUCCH resources are not overlapped with a PUCCH resource for the firstly selected UCI set.
[0086] Alternatively or additionally, in some embodiments, the terminal device 110 may select, from the multiple UCI sets, the one or more UCI sets for transmission based on a starting symbol of an earliest UCI type in each of the one or more UCI sets. This will be described with reference to Fig. 4.
[0087] Fig. 4 illustrates an example of transmission of UCI sets in accordance with some embodiments of the present disclosure. In the example of Fig. 4, a UCI set 0 comprises a UCI type 1, a UCI type 2 and a UCI type 3, a UCI set 1 comprises a UCI type 4, and a UCI set 2 comprises a UCI type 5 and a UCI type 6. PUCCH resource 0 in a slot is for the UCI set 0, PUCCH resource 1 in the slot is for the UCI set 1, and PUCCH resource 2 in the slot is for the UCI set 2. The PUCCH resource 0, the PUCCH resource 1 and the PUCCH resource 2 are overlapped PUCCH resources.
[0088] In the example of Fig. 4, an earliest UCI type in the UCI set 0 is the UCI type 1, an earliest UCI type in the UCI set 1 is the UCI type 4, and an earliest UCI type in the UCI set 2 is the UCI type 5. Because a starting symbol of the earliest UCI type 4 is earlier than starting symbols of the earliest UCI types 1 and 5, the terminal device 110 may firstly select the UCI set 1 and transmit the UCI set 1 on the PUCCH resource 1.
[0089] Alternatively or additionally, in some embodiments, the terminal device 110 may select, from the multiple UCI sets, the one or more UCI sets for transmission based on time when the one or more UCI sets are prepared for transmission.
[0090] In the example of Fig. 4, because the time when the UCI set 2 is earlier than the UCI sets 0 and 1, the terminal device 110 may firstly select the UCI set 2 for transmission and transmit the UCI set 2 on the PUCCH resource 2.
[0091] Alternatively or additionally, in some embodiments, the terminal device 110 may select, from the multiple UCI sets, the one or more UCI sets for transmission based on the number of the one or more UCI types in each of the one or more UCI sets. For example, the terminal device 110 may firstly select a UCI set containing the largest number of UCI types, and then select a UCI set containing the largest number of UCI types from the remaining non-overlapped UCI sets. The remaining non-overlapped UCI sets refer to remaining UCI sets for which PUCCH resources are not overlapped with a PUCCH resource for the firstly selected UCI set.
[0092] Consider the example in Fig. 4. Because the number of UCI types in the UCI set 0 is larger than the numbers of UCI types in the UCI set 1 and the UCI set 2, the terminal device 110 may firstly select the UCI set 0 and transmit the UCI set 0 on the PUCCH resource 0.
[0093] In some embodiments, optionally, the terminal device 110 may preferably ensure the UCI transmission of legacy UCI types in LTE / NR, and / or the UCI types in a primary cell in case of cross-carrier overlap, and drop other overlapped UCI types.
[0094] Hereinafter, some embodiments of determining a priority of a UCI type will be described. Such embodiments may simplify handling of UCI overlap based on UCI priority.
[0095] In some embodiments, the terminal device 110 may determine a priority of a UCI type based on at least one of the following: ● a high layer configuration, ● an RRC configuration, ● an indication in downlink control information (DCI) from the network device 120, ● configured grant (CG) scheduling information ● traffic priority in higher layer of the terminal device 110, or ● predefinition.
[0096] In some embodiments, regarding a UCI type which is generated by AI / ML functionality or AI / ML model, the terminal device 110 may determine a priority of the UCI type based on an indication in an AI or ML LCM procedure. For example, the terminal device 110 may determine the priority of the UCI type based on an indication in an AI / ML model / functionality activation signaling from network.
[0097] In some embodiments, regarding a UCI type which is generated by a sensing transmitter or sensing receiver, a priority of the UCI type is related to an integrated sensing and communication (ISAC) scenario and may be inherited from high layer, e.g., access stratum (AS) layer. For example, the ISAC scenario may comprise intrusion detection, healthy monitoring and so on.
[0098] In some embodiments, a priority of a UCI type may take a value from [minus infinity, 0, 1, 2, 3, 4, 5, 6, 7, 8, …] and other proper value. Preferably, the smaller number indicates higher priority level. For example, HARQ-ACK information may be configured with a priority value of minus infinity or 0, and a UCI type which is generated by a sensing transmitter or sensing receiver may be configured with a relative higher priority. For example, a UCI type related to intrusion detection or healthy monitoring may be configured with a relative higher priority.
[0099] In some embodiments, if a payload size of a first UCI set among the one or more UCI sets is less than or equal to 2 bits, the terminal device 110 may transmit the first UCI set in a first PUCCH format.
[0100] In some embodiments, the terminal device 110 may transmit the first UCI set in the first PUCCH format by transmitting a predetermined sequence.
[0101] In some embodiments, the terminal device 110 may transmit the first UCI set in the first PUCCH format by transmitting a predetermined sequence on one physical resource block (PRB) with 1or 2 symbol length. In some embodiments, 12-bit sequences with different sequence cyclic shifts may be used to indicate that the payload size of the first UCI set is less than or equal to 2 bits.
[0102] In some embodiments, if the payload size of the first UCI set is greater than 2 bits, the terminal device 110 may transmit the first UCI set in a second PUCCH format. In some embodiments, the terminal device 110 may transmit the first UCI set in the second PUCCH format by multiplexing one or more coded UCI types in the first UCI set with demodulation reference signal (DMRS) in time and frequency domains. In such embodiments, the symbol length and PRB number are configured by RRC signaling to adapt various UCI payloads. RRC signaling may be used to additionally configure multiplexing, hopping, DMRS and any other necessary information.
[0103] In some embodiments, if the terminal device 110 would transmit one or more UCI types in a slot, the terminal device 110 may multiplex and transmit the one or more UCIs on PUSCH resources or media access control control element (MAC CE) or layer 2 (L2) message (i.e., skip the UCI overlap procedure) if a priority of each of the one or more UCI types is below a predefined threshold. That is, only UCI type with a lower priority may be transmitted on PUSCH resources or MAC CE or L2 message. Therefore, there is less UCI collision and a UCI type with higher priority will still be transmitted on PUCCH resource.
[0104] In some embodiments, if the terminal device 110 would transmit one or more UCI types in a slot, the terminal device 110 may multiplex and transmit the one or more UCIs on PUSCH resources or MAC CE or L2 message (i.e., skip the UCI overlap procedure) if latency requirement of the one or more UCI types is below a predefined threshold. That is, a UCI type related to latency sensitive traffic is still be transmitted on PUCCH resource, other UCI can be transmitted on PUSCH resources or MAC CE or L2 message.
[0105] In some embodiments, if PUCCH resources for multiple UCI types are overlapped in time domain and the terminal device 110 would transmit the multiple UCI types, in order to avoid complicated UCI collision handing and multiplexing procedure, the terminal device 110 may only transmit part of the multiple UCI types by using one of the following options.
[0106] In Option 1, with each slot, the terminal device 110 may only transmit at least one UCI type with highest priority among the multiple UCI types and drop all other overlapped UCI types with lower priority. For example, only HARQ-ACK information is transmitted if HARQ-ACK information is configured with highest priority.
[0107] In Option 2, with each slot, the terminal device 110 may only transmit at least one UCI type with a priority higher greater than a threshold, and drop the remaining UCI types. In this way, the number of UCI types to be multiplexed and collision may be reduced.
[0108] In Option 3, with each slot, the terminal device 110 may only transmit a first number of UCI types with higher priority. The first number is equal to or less than a configured number.
[0109] In Option 4, with each slot, the terminal device 110 may only transmit the configured number of UCI types.
[0110] In some embodiments, the terminal device 110 may reduce UCI multiplexing procedure complexity based on AIML's prediction or assistance. In this way, the terminal device 110 may avoid complicated UCI overlap based on AIML prediction.
[0111] In some embodiments, at the side of the terminal device 110, the terminal device 110 may obtain the UCI transmissions occasions or patterns within one or more future slots. In such embodiments, the UCI transmission prediction during future slots (i.e., model output) is based on AIML inference based on past or historical UCI transmission during an observation window, (i.e.., model input) .
[0112] In such embodiments, the model input may comprise the number, time domain resource (symbols) and frequency domain resource (e.g., physical resource blocks, PRBs) of the past or historical UCI transmission, payload size of the UCI, the dropped UCI transmission due to overlap, the eventual transmitted or multiplexed UCI.
[0113] In such embodiments, the model output may comprise the number, payload size, time domain resource (e.g., symbols) and frequency domain resource (e.g., PRBs) of the intended UCI transmission.
[0114] In such embodiments, the terminal device 110 signaled the model output to the network device 120 for a more proper PUCCH / PUSCH configuration to avoid collisions.
[0115] Alternatively, in some embodiments, at the side of the network device 120, the network device 120 may obtain the UCI transmissions occasions or patterns within one or more future slots based on model inference, and schedule downlink (DL) transmission, assign proper PUCCH / PUSCH for UCI transmission to avoid UCI collision.
[0116] In such embodiments, the above model inference may be derived based on one sided model at the terminal device 110 and / or the network device 120 respectively, or based on a two-sided model at both sides of the terminal device 110 and the network device 120.
[0117] Alternatively, the above UCI types may only comprise SR related UCI, e.g., SR, LRR, AIML related resource request, ISAC related resource request, and so on.
[0118] In some embodiments, the terminal device 110 may obtain a final UCI transmission pattern based on AIML inference.
[0119] In such embodiments, the model input may comprise the number, payload, time domain resource (e.g., symbols) and frequency domain resource (e.g., PRBs) of the intended multiple overlapped UCI transmissions.
[0120] In such embodiments, the model output may comprise the eventual suggested transmitted UCI (including dropped and multiplexing UCI) and PUCCH / PUSCH resources.
[0121] Fig. 5 is a simplified block diagram of a device 500 that is suitable for implementing embodiments of the present disclosure. The device 500 can be considered as a further example embodiment of the terminal device 110 as shown in Fig. 1. Accordingly, the device 500 can be implemented at or as at least a part of the terminal device 110.
[0122] As shown, the device 500 includes a processor 510, a memory 520 coupled to the processor 510, a suitable transceiver 540 coupled to the processor 510, and a communication interface coupled to the transceiver 540. The memory 510 stores at least a part of a program 530. The transceiver 540 may be for bidirectional communications or a unidirectional communication based on requirements. The transceiver 540 may include at least one of a transmitter 542 and a receiver 544. The transmitter 542 and the receiver 544 may be functional modules or physical entities. The transceiver 540 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) / SGW / 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.
[0123] The components included in the apparatuses and / or devices of the present disclosure may be implemented in various manners, including software, hardware, firmware, or any combination thereof. In one embodiment, one or more units may be implemented using software and / or firmware, for example, machine-executable instructions stored on the storage medium. In addition to or instead of machine-executable instructions, parts or all of the units in the apparatuses and / or devices may be implemented, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs) , Application-specific Integrated Circuits (ASICs) , Application-specific Standard Products (ASSPs) , System-on-a-chip systems (SOCs) , Complex Programmable Logic Devices (CPLDs) , and the like.
Claims
1.A terminal device, comprising:a processor configured to cause the terminal device to:determine one or more uplink control information (UCI) sets, wherein each of the one or more UCI sets comprises one or more UCI types, each of the one or more UCI types is assigned with a priority, physical uplink control channel (PUCCH) resources for the one or more UCI sets are overlapped in time domain;determine at least one non-overlapped PUCCH resource based on one or more priorities of the one or more UCI sets; andtransmit at least one of the one or more UCI sets to a network device on the at least one non-overlapped PUCCH resource.2.The terminal device of claim 1, wherein the one or more priorities of the one or more UCI sets are determined based on at least one of the following:one or more features of the one or more UCI types,one or more priorities of the one or more UCI types,a payload size of the one or more UCI types,predefinition, orconfiguration.3.The terminal device of claim 1, wherein the terminal device is configured with non-overlapped PUCCH resources; andwherein the terminal device is caused to transmit the at least one of the one or more UCI sets by:transmitting the one or more UCI sets on the non-overlapped PUCCH resources.4.The terminal device of claim 3, wherein the terminal device is caused to transmit the one or more UCI sets on non-overlapped PUCCH resources by:transmitting a first UCI set among the one or more UCI sets on an earliest one of PUCCH resources which satisfy a timeline condition or a payload condition.5.The terminal device of claim 4, wherein all of the one or more UCI types in the first UCI set is prepared before at least one time offset before a starting symbol of the earliest one of PUCCH resources which satisfy the timeline condition.6.The terminal device of claim 4, wherein the terminal device is caused to transmit the first UCI set by:multiplexing one or more UCI types in the first UCI set; andtransmitting the one or more UCI types in the first UCI set on the earliest one of PUCCH resources.7.The terminal device of claim 1, wherein the terminal device is further caused to:determine the one or more priorities of the one or more UCI sets based on predefinition or configuration.8.The terminal device of claim 1,wherein the terminal device is further caused to:determine a priority of each of the one or more UCI sets as a highest one of one or more priorities of the one or more UCI types in a respective one of the one or more UCI sets.9.The terminal device of claim 1, wherein the terminal device is further caused to:determine a priority of each of the one or more UCI types based on at least one of the following:a high layer configuration,a radio resource control (RRC) configuration,an indication in downlink control information (DCI) from the network device,configured grant (CG) scheduling informationtraffic priority in higher layer of the terminal device, orpredefinition.10.The terminal device of claim 1, wherein the one or more UCI types comprise one or more UCI types which are generated by artificial intelligence (AI) or machine learning (ML) functionality.11.The terminal device of claim 10, wherein the terminal device is further caused to:determine a priority of each of the one or more UCI types which are generated by AI or ML functionality based on an indication in an AI or ML life cycle management (LCM) procedure.12.The terminal device of claim 1, wherein the one or more UCI types comprise one or more UCI types which are generated by a sensing transmitter or sensing receiver.13.The terminal device of claim 12, wherein a priority of each of the one or more UCI types is related to an integrated sensing and communication (ISAC) scenario.14.The terminal device of claim 1, wherein the terminal device is caused to transmit the at least one of the one or more UCI sets by:based on determining that a payload size of a first UCI set among the one or more UCI sets is less than or equal to 2 bits, transmitting the first UCI set in a first PUCCH format; andbased on determining that the payload size of the first UCI set is greater than 2 bits, transmitting the first UCI set in a second PUCCH format.15.The terminal device of claim 14, wherein the terminal device is caused to transmit the first UCI set in the first PUCCH format by:transmitting a predetermined sequence.16.The terminal device of claim 14, wherein the terminal device is caused to transmit the first UCI set in the second PUCCH format by:multiplexing one or more coded UCI types in the first UCI set with demodulation reference signal (DMRS) in time and frequency domains.17.A method for communication, comprising:determining one or more UCI sets, wherein each of the one or more UCI sets comprises one or more UCI types, each of the one or more UCI types is assigned with a priority, PUCCH resources for the one or more UCI sets are overlapped in time domain;determining at least one non-overlapped PUCCH resource based on one or more priorities of the one or more UCI sets; andtransmitting at least one of the one or more UCI sets to a network device on the at least one non-overlapped PUCCH resource.