# US 12,120,687 B2 · Transmission method for UCI performed by terminal > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,120,687 B2 - Document ID: US12120687B2 - Status: Granted - Kind: B2 - Application number: 17/431,174 - Filed: 2020-01-10 - Published: 2022-05-12 - Granted: 2024-10-15 - Earliest claimed: 2019-02-15 - Assignees: Datang Mobile Communications Equipment Co., Ltd. - Applicants: Datang Mobile Communications Equipment Co., Ltd. - Inventors: Xuejuan Gao; Ekpenyong Tony - Web page: https://patentgrep.com/patent/US12120687B2 ## CPC - H04L 5/0053: {Allocation of signalling, i.e. of overhead other than pilot signals} - H04W 72/21: in the uplink direction of a wireless link, i.e. towards the network - H04L 5/0078: {Timing of allocation} - H04W 72/1268: of uplink data flows - H04W 72/569: {of the traffic information} - H04W 72/0446: Resources in time domain, e.g. slots or frames - H04W 72/542: using measured or perceived quality - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Disclosed are a transmission method and device, for use in solving the problem in the prior art that no specific solution is available for dealing with how to transmit an SR and a PUSCH when the SR overlaps with the PUSCH in a time domain. If it is determined that a PUCCH bearing first type of DCI overlaps with the PUSCH in the time domain after a target node of the PUSCH, it is possible to select to discard the first type of DCI or delay the first type of DCI to the next transmission opportunity for transmitting. ## Claims ### Claim 1 A transmission method, performed by a terminal and comprising: in response to determining that a physical uplink control channel (PUCCH) carrying a first type of uplink control information (UCI) overlaps with a physical uplink shared channel (PUSCH) in a time domain after a target time node associated with the PUSCH, dropping the first type of UCI or delaying the first type of UCI to be transmitted in a next transmission occasion. ### Claim 2 (depends on 1) The method according to claim 1, further comprising: in response to determining that the PUCCH carrying the first type of UCI overlaps with the PUSCH in the time domain before the target time node of the PUSCH, dropping the PUSCH and transmitting the first type of UCI. ### Claim 3 (depends on 1) The method according to claim 1, wherein the target time node comprises: a transmission start instant or symbol of the PUSCH, or an instant or symbol corresponding to a time duration T1 after a transmission start instant or symbol of the PUSCH, or a first symbol satisfying a time duration T1 after a transmission start instant or symbol of the PUSCH, or an instant or symbol corresponding to a time duration T2 before a transmission start instant or symbol of the PUSCH, or a first symbol satisfying a time duration T2 before a transmission start instant or symbol of the PUSCH. ### Claim 4 (depends on 3) The method according to claim 3, wherein the time duration T1 or the time duration T2 is a predefined time length or a predefined symbol quantity, or the time duration T1 or the time duration T2 is a time length or a symbol quantity determined according to a predefined rule. ### Claim 5 (depends on 4) The method according to claim 4, wherein the time duration T1 is 1/N of a transmission length of the PUSCH, and N is a positive integer greater than 1; and/or the time duration T2 is a preparation duration of the PUSCH. ### Claim 6 (depends on 1) The method according to claim 1, wherein delaying the first type of UCI to be transmitted in the next transmission occasion comprises: not transmitting the first type of UCI in a transmission occasion overlapping with the PUSCH; and transmitting the first type of UCI in an earliest transmission occasion after the transmission occasion overlapping with the PUSCH. ### Claim 7 (depends on 6) The method according to claim 6, wherein transmitting the first type of UCI in the earliest transmission occasion after the transmission occasion overlapping with the PUSCH comprises: dropping the PUSCH overlapping with the PUCCH carrying the first type of UCI in response to that the PUSCH overlaps with the PUCCH carrying the first type of UCI in the earliest transmission occasion. ### Claim 8 (depends on 7) The method according to claim 7, wherein dropping the PUSCH overlapping with the PUCCH carrying the first type of UCI comprises: not preparing and transmitting the PUSCH overlapping with the PUCCH carrying the first type of UCI; or starting to not transmit the PUSCH overlapping with the PUCCH carrying the first type of UCI at a transmission start instant of the PUSCH overlapping with the PUCCH carrying the first type of UCI. ### Claim 9 (depends on 1) The method according to claim 1, wherein the first type of UCI is one of following information: a scheduling request (SR), UCI corresponding to a first type of service, or an SR corresponding to the first type of service; and/or, the PUSCH is a PUSCH corresponding to the first type of service or a second type of service; wherein: the first type of service comprises: a service with a high priority or importance, or, an ultra reliability and low latency communication (URLLC) service; and the second type of service comprises: a service with a low priority or importance, or an enhanced mobile broadband (eMBB) service, or, a non-URLLC service. ### Claim 10 (depends on 9) The method according to claim 9, wherein priorities or importance or service types are determined according to at least one of following corresponding information: downlink control information (DCI) formats; DCI sizes; radio network temporary identities (RNTIs); search spaces; control resource sets (CORESETs); beams; block error ratios (BLERs); channel quality indicator (CQI) tables; modulation and coding scheme (MCS) tables; priority flags; PUCCH resources; or SR configuration serial numbers. ### Claim 11 A terminal, comprising: a processor, a memory and a transceiver, wherein the processor is configured to read a program in the memory to: in response to determining that a physical uplink control channel (PUCCH) carrying a first type of uplink control information (UCI) overlaps with a physical uplink shared channel (PUSCH) in a time domain after a target time node associated with the PUSCH, drop the first type of UCI or delaying the first type of UCI to be transmitted in a next transmission occasion. ### Claim 12 (depends on 11) The terminal according to claim 11, wherein the processor is further configured to: in response to determining that the PUCCH carrying the first type of UCI overlaps with the PUSCH in the time domain before the target time node of the PUSCH, drop the PUSCH and transmit the first type of UCI. ### Claim 13 (depends on 11) The terminal according to claim 11, wherein the target time node comprises: a transmission start instant or symbol of the PUSCH, or an instant or symbol corresponding to a time duration T1 after a transmission start instant or symbol of the PUSCH, or a first symbol satisfying the time duration T1 after a transmission start instant or symbol of the PUSCH, or an instant or symbol corresponding to a time duration T2 before a transmission start instant or symbol of the PUSCH, or a first symbol satisfying a time duration T2 before a transmission start instant or symbol of the PUSCH. ### Claim 14 (depends on 13) The terminal according to claim 13, wherein the time duration T1 or the time duration T2 is a predefined time length or a predefined symbol quantity, or the time duration T1 or the time duration T2 is a time length or a symbol quantity determined according to a predefined rule. ### Claim 15 (depends on 14) The terminal according to claim 14, wherein the time duration T1 is 1/N of a transmission length of the PUSCH, and N is a positive integer greater than 1; and/or the time duration T2 is a preparation duration of the PUSCH. ### Claim 16 (depends on 11) The terminal according to claim 11, wherein when the first type of UCI is delayed to be transmitted in the next transmission occasion, the processor is further configured to: not transmit the first type of UCI in a transmission occasion overlapping with the PUSCH; and transmit the first type of UCI in an earliest transmission occasion after the transmission occasion overlapping with the PUSCH. ### Claim 17 (depends on 16) The terminal according to claim 16, wherein when the first type of UCI is transmitted in the earliest transmission occasion after the transmission occasion overlapping with the PUSCH, the processor is further configured to: drop the PUSCH overlapping with the PUCCH carrying the first type of UCI in response to that the PUSCH overlaps with the PUCCH carrying the first type of UCI in the earliest transmission occasion. ### Claim 18 (depends on 17) The terminal according to claim 17, wherein in the condition that the PUSCH overlapping with the PUCCH carrying the first type of UCI is dropped, the processor is further configured to: not prepare and transmit the PUSCH overlapping with the PUCCH carrying the first type of UCI; or start to not transmit the PUSCH overlapping with the PUCCH carrying the first type of UCI at a transmission start instant of the PUSCH overlapping with the PUCCH carrying the first type of UCI. ### Claim 19 (depends on 11) The terminal according to claim 11, wherein the first type of UCI is one of following information: a scheduling request (SR), UCI corresponding to a first type of service, or an SR corresponding to the first type of service; and/or, the PUSCH is a PUSCH corresponding to the first type of service or a second type of service; wherein the first type of service comprises: a service with a high priority or importance, or, an ultra reliability and low latency communication (URLLC) service; and the second type of service comprises: a service with a low priority or importance, or an enhanced mobile broadband (eMBB) service, or, a non-URLLC service. ### Claim 20 (depends on 19) The terminal according to claim 19, wherein priorities or importance or service types are determined according to at least one of following corresponding information: downlink control information (DCI) formats; DCI sizes; radio network temporary identities (RNTIs); search spaces; control resource sets (CORESETs); beams; block error ratios (BLERs); channel quality indicator (CQI) tables; modulation and coding scheme (MCS) tables; priority flags; PUCCH resources; or SR configuration serial numbers.