Uplink collision handling for multi-transmission reception point operation

Abstract

This application relates to devices and components, including apparatus, systems, and methods for providing a collision resolution procedure in a wireless communication system.

Description

Background Technology

[0001] The 3GPP (3rd Generation Partnership Project) network specification allows a gNB to use multiple Transmit / Receive Points (TRPs) to send or receive information from a User Equipment (UE). The UE may have multiple antenna panels configured to send or receive the information. 3GPP Releases 15 and 16 introduced reliability enhancements for Physical Uplink Control Channel (PUCCH) and Physical Uplink Shared Channel (PUSCH) transmissions to multiple TRPs. Attached Figure Description

[0002] Figure 1 A network environment according to some implementation schemes is shown.

[0003] Figure 2 The conflict resolution process is illustrated according to some implementation schemes.

[0004] Figure 3 Another conflict resolution process is shown according to some implementation schemes.

[0005] Figure 4 Another conflict resolution process is shown according to some implementation schemes.

[0006] Figure 5 Another conflict resolution process is shown according to some implementation schemes.

[0007] Figure 6 Another conflict resolution process is shown according to some implementation schemes.

[0008] Figure 7 Another conflict resolution process is shown according to some implementation schemes.

[0009] Figure 8 The operational flow / algorithm structure according to some implementation schemes is shown.

[0010] Figure 9 Another operational flow / algorithm structure according to some implementation schemes is shown.

[0011] Figure 10 Another operational flow / algorithm structure according to some implementation schemes is shown.

[0012] Figure 11 A beamforming component of a user equipment according to some embodiments is shown.

[0013] Figure 12 User equipment according to some implementation schemes is shown. Detailed Implementation

[0014] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0015] The following is a glossary of terms that may be used in this disclosure.

[0016] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-a-chip (SoCs)), digital signal processors (DSPs), etc. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the said functions. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functions (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0017] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0018] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, etc.

[0019] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" can be considered synonymous and can be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0020] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0021] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that computer equipment / systems can access via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0022] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0023] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0024] The term "connection" can mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0025] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0026] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0027] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include UE 104 and gNB 108. gNB 108 may be a base station providing one or more radio access cells, for example, UE 104 may communicate with gNB 108 via a 3GPP New Radio “NR” cell. UE 104 and gNB 108 may communicate via an air interface compatible with 3GPP technical specifications, such as those defining the fifth-generation (5G) NR system standard.

[0028] gNB 108 may include a gNB controller 112 coupled to one or more TRPs (e.g., TRP 116 and TRP 120). Generally, gNB controller 112 performs most of the operations of the communication protocol stack, including scheduling, while TRP 116 and TRP 120 act as distributed antennas. In some embodiments, TRP 116 and 120 may perform some low-level operations of the communication protocol stack (e.g., simulating physical (PHY) layer operations).

[0029] The gNB 108 can use TRP 116 and TRP 122 to geographically separate points that can transmit or receive signals to or from the UE 104. This increases the flexibility of communicating with the UE 104 using multiple-input multiple-output (MIMO) and beamforming enhancements. TRP 116 and TRP 120 can be used to transmit downlink transmissions to and receive uplink transmissions from the UE 104. In some implementations, the distributed transmit / receive capabilities provided by TRP 116 and TRP 120 can be used in cooperative multipoint or carrier aggregation systems.

[0030] The gNB 108 can transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels to transport channels and transport channels to physical channels. Logical channels can transmit data between the Radio Link Control (RLC) layer and the Media Access Control (MAC) layer; transport channels can transmit data between the MAC and PHY layers; and physical channels can transmit information across the air interface.

[0031] UE 104 and TRP 116 may include an array of antenna elements in one or more antenna panels that allow for receive or transmit beamforming. Beamforming improves uplink and downlink budgets by identifying and using uplink and downlink beams that increase antenna gain and overall system performance. UE 104 and gNB 108 may use beam management operations to determine desired uplink-downlink beam pairs based on reference signal measurements and channel reciprocity assumptions.

[0032] In the downlink direction, TRP 116 and TRP 120 may transmit synchronization signal blocks (SSBs) and channel state information-reference signals (CSI-RS) measured by UE 104 to determine the desired downlink beam pairs for transmitting / receiving physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH) transmissions. In some implementations, network elements may assume uplink / downlink beam correspondences and use the desired downlink beam pairs as the desired uplink beam pairs for PUSCH and PUCCH transmissions. In some implementations, beam pairs may be determined independently for the uplink direction based on sounding reference signals (SRS) transmitted by UE 104. In various implementations, beam management may include different phases, such as initial acquisition of uplink and downlink beams and subsequent refinement of uplink and downlink beams.

[0033] In addition to beam management, SRS can be used for uplink channel-aware scheduling and link adaptation, estimation of downlink propagation channels when channel reciprocity exists, and transmission based on both codebook and non-codebook methods.

[0034] PUCCH can be used to transmit uplink control information (UCI), which includes, for example, Hybrid Automatic Repeat Request (HARQ) acknowledgments, scheduling requests, and periodic and semi-persistent channel state information (CSI) reports. PUSCH can be used to transmit user data in the user plane and signaling radio bearer (SRB) messages in the control plane. PUSCH can also be used to transmit various control information, such as buffer status reports, cell radio network temporary identifiers (C-RNTI), configured authorization settings, and power headroom reports.

[0035] As briefly discussed above, 3GPP Releases 15 and 16 provide PUCCH and PUSCH repetition in some cases to increase reliability. For example, for longer PUCCH formats (e.g., PUCCH formats 1, 3, and 4), the gNB can configure the UE to repeatedly transmit PUCCH resources in one or more time slots. For PUSCH, the gNB can configure the UE to repeatedly transmit PUSCH with repetition type A or repetition type B. In PUSCH repetition type A, each PUSCH repetition can be mapped to consecutive time slots. For example, the first PUSCH repetition can be mapped to the first time slot, the second PUSCH repetition can be mapped to the second time slot immediately following the first time slot, and so on. In PUSCH repetition type B, each PUSCH repetition can be mapped to consecutive symbols. Consecutive symbols can be in one or more time slots. In Releases 15 and 16, all repetitions of PUCCH or PUSCH are transmitted from the same beam.

[0036] Release 17 of 3GPP introduced further enhancements for PUCCH and PUSCH. For example, PUCCH / PUSCH can be transmitted repeatedly within or across time slots, with different beams available for different repetitions. Repetitions of different beams can be transmitted to the same or different TRPs.

[0037] PUCCH repetition transmitted on different beams can use different PUCCH resources to transmit the same UCI. Resources configured for PUCCH repetition can be in one or more time slots. Alternatively, PUCCH repetition transmitted on different beams can use PUCCH resources configured with more than one beam. Therefore, there are two ways to implement PUCCH repetition. First, more than one PUCCH resource can be configured to transmit UCI. Second, more than one beam can be configured for a PUCCH resource used to transmit UCI. Different beams used for PUCCH repetition can be defined by different spatial relationships, Transmission Configuration Indicators (TCIs), or power control parameters.

[0038] PUSCH repetitions transmitted on different beams can use different time / frequency resources configured by RRC or authorized by a single downlink control information (DCI) or multiple DCIs to transmit the same PUSCH payload. Resources configured for PUSCH repetitions can be in one or more time slots. Different beams used for transmitting PUSCH repetitions can be defined by different SRS source indicators (SRI), transmission precoder matrix indicators (TPMI), or power control parameters.

[0039] In some cases, uplink transmissions may conflict with each other. For example, the mapping function in UE 104 can map a first uplink transmission and a second uplink transmission to the same or at least partially overlapping uplink resources. In these cases, UE 104 may need to perform a conflict resolution procedure to determine which transmission to send on the uplink resource. Conflict resolution procedures can be defined for various uplink conflicts including the following seven specific cases: Case 1 includes a conflict between a non-duplicate PUCCH and a PUSCH with duplication type A. Case 2 includes a conflict between a non-duplicate PUCCH and a PUSCH with duplication type B. Case 3 includes a conflict between a duplicate PUCCH and a duplicate PUSCH with type A or B. Case 4 includes a conflict between a duplicate PUCCH and another duplicate PUCCH. Case 5 includes a conflict between a duplicate PUCCH and a non-duplicate PUSCH. Case 6 includes a conflict between a duplicate PUCCH and an SRS. Case 7 includes a conflict between a duplicate PUSCH and an SRS.

[0040] The collision resolution process for uplink transmissions from multiple beams may follow one or more of the following principles. First, it may be desirable to maintain multi-beam operation for UCI transmission to improve reliability. Second, UCI priority may be based on the target receiving TRP. Third, it may be desirable to transmit UCI to the corresponding receiving TRP based on the correct beam target. Various implementations describe collision resolution processes influenced by these principles.

[0041] The conflict resolution process for case 1 - a conflict between a non-repeating PUCCH and a PUSCH with repeating type A - can be resolved as follows.

[0042] The first option, driven by the second and third principles described above, can determine uplink transmissions based on the target TRPs of the PUCCH and PUSCH. For example, if the PUCCH and PUSCH are associated with the same TRP (e.g., they will be transmitted to the same TRP), then the UCI from the PUCCH can be multiplexed into all of the PUSCH duplicates. If the PUCCH in the PUSCH is not associated with the same TRP, then UE 104 can discard the PUCCH, the PUSCH duplicates in the overlapping symbols, or all PUSCH duplicates. The transmissions to be discarded can be based on the priority determined by the associated TRP index. Figure 2 A conflict resolution process 200 describing these concepts according to some implementation schemes is shown.

[0043] like Figure 2 As shown, UE 104 can receive PUCCH 204 for transmission on a first beam, such as beam X, and can also receive PUSCH repeats 208. The first two PUSCH repeats (e.g., PUSCH repeats #1 and #2) can be scheduled for transmission on beam X, and the latter two PUSCH repeats (e.g., PUSCH repeats #3 and #4) can be scheduled for transmission on beam Y.

[0044] In the conflict resolution process 200, UE 104 may determine that PUCCH 204 will conflict with PUSCH repeat #1 of PUSCH repeat 208. UE 104 may determine the uplink transmission based on the target TRP of PUCCH 204 and PUSCH repeat 208. In some implementations, the target TRP may be determined based on the control resource set (CORESET) information corresponding to the PDCCH that schedules PUCCH 204 and PUSCH repeat 208.

[0045] The gNB 108 can use resource elements belonging to a CORESET to transmit scheduled PDCCHs. Search space configuration can specify a particular CORESET to define the search space; for example, a specific set of resource blocks and symbols that the UE 104 attempts to decode the PDCCH. The gNB 108 can configure up to three CORESETs for the active downlink bandwidth portion of the serving cell. A CORESET can be configured by a ControlResourceSet information element, which defines frequency domain resources to indicate the resource blocks allocated to the CORESET, defines a duration (which can be 1, 2, or 3 Orthogonal Frequency Division Multiplexing (OFDM) symbols) to indicate the number of symbols allocated to the CORESET, and defines quasi-co-location (QCL) information to support successful PDCCH reception. In some implementations, the gNB 108 can configure one or more CORESET pools to allow TRP 116 and TRP 120 to transmit PDCCHs that can potentially schedule PUSCH / PUCCHs that are fully or partially time-overlapping. To configure a CORESET pool, the gNB 108 can include a CORESET pool index in the ControlResourceSet IE to associate a CORESET with a corresponding CORESET pool. The CORESET pool index may correspond to a TRP index as described herein. In some implementations, the gNB 108 can configure up to two distinct CORESET pools.

[0046] If the PDCCHs scheduling PUCCH and PUSCH are associated with the same CORESET pool—for example, they are both associated with the same CORESET pool index—then they can be transmitted from the same TRP. Therefore, the target TRP (TRP) used for PUCCH... PUCCH It can be used with the target TRP (TRP) for PUSCH. PUSCH The same applies. In this case, UE 104 can multiplex the UCI from PUCCH 204 to all PUSCH repeats 208, resulting in PUSCH repeats in transmission sequence 212. The PUSCH repeats in transmission sequence 212 can then be transmitted to TRP.

[0047] If TRP PUCCH Unlike TRP PUSCH Then UE 104 can determine the transmission based on the priority of the associated TRP index, such as the CORESET pool index. In some implementations, a CORESET pool index with a lower value may be considered to have a relatively higher priority.

[0048] In some implementations, if TRP PUCCH Priority (Pri(TRP)) PUCCH ()) Greater than TRPPUSCH Priority (Pri(TRP)) PUSCH If so, UE 104 can select one of two sub-options. In the first sub-option, UE 104 can discard PUSCH duplicates that conflict with PUCCH 204, for example, PUSCH duplicate #1, and transmit the remaining duplicates. This is shown as Figure 2 Transmission sequence 216. In the second sub-option, UE 104 may discard all PUSCH duplicates, resulting in transmission sequence 220 that includes only PUCCH. UE 104 may use this option when the probability of successful transmission of the remaining PUSCH duplicates is less than a predetermined threshold. In this case, the use of transmission resources required to transmit only some of these duplicates may not be justified by the probability of success.

[0049] In some implementations, if Pri(TRP) PUSCH )) greater than Pri(TRP PUCCH If ), then UE 104 can discard PUCCH 204. The resulting transmission sequence 224 can then correspond to PUSCH repeat 208.

[0050] The second option of Case 1, driven by the first principle described above, can determine uplink transmission based on timeline constraints used for transmitting the UCI. The timeline constraints can be based on configuration information provided by gNB 108 or the processing capabilities of UE 104. For example, if the UCI includes HARQ-ACK information related to the reception of PDSCH, UE 104 may require a certain amount of time to process the PDSCH and generate the corresponding HARQ-ACK information. Therefore, UE 104 may not be able to multiplex the UCI onto PUSCH repetitions that occur before the time required for these operations. In some implementations, the timeline constraints may be consistent with those described in 3GPP Technical Specification (TS) 38.213 v16.2.0 (2020-06).

[0051] Figure 3 A conflict resolution process 300, according to some embodiments, is shown as a second option available in case 1. Similar to conflict resolution process 200, conflict resolution process 300 includes a PUCCH 304 that conflicts with a first repetition of PUSCH repetition 308. In this embodiment, UE 104 may determine that: PUSCH repetition #1 is the first PUSCH repetition for a transmission beam X that satisfies the timeline constraint; and PUSCH repetition #2 is the first PUSCH repetition for a transmission beam Y that satisfies the timeline constraint. Therefore, UE 104 may generate a sequence 312 in which UCI is multiplexed to PUSCH repetition #1 and PUSCH repetition #3.

[0052] In some implementations, the second option of Case 1 can be used regardless of the associated TRP index. Alternatively, the second option of Case 1 can be used when both PUSCH and PUCCH point to the same TRP. Therefore, it can be used as an alternative scheme for transmission sequence 212.

[0053] The conflict resolution process for Case 2 – a conflict between a non-repeating PUCCH and a PUSCH with repeating type B – may include a first option and a second option, which may be similar to those options described above for Case 1. Case 2 may also include a third option as discussed herein.

[0054] Figure 4 This includes a conflict resolution process 400 according to some implementation schemes. Conflict resolution process 400 may correspond to the first option for case 2, where no repeating PUCCH conflicts with a PUSCH having repeat type B. Specifically, PUCCH 404 may conflict with the first two repeats of PUSCH repeat 408. Assuming PUSCH repeat 408 is repeat type B, a time slot may include more than one repeat. As shown, a time slot may include two repeats.

[0055] If PUCCH 404 and PUSCH 408 are associated with the same TRP, for example, TRP PUSCH Equal to TRP PUCCH Then UE 104 can multiplex the UCI from PUCCH 404 to all PUSCH repeats 408, resulting in PUSCH repeats in transmission sequence 412. The PUSCH repeats in transmission sequence 412 can then be transmitted to TRP.

[0056] If PUCCH 404 and PUSCH 408 are associated with different TRPs, for example if TRP PUCCH Unlike TRP PUSCH Then UE 104 can determine the transmission based on the priority of the associated TRP index, such as the CORESET pool index. In some implementations, a CORESET pool index with a lower value may be considered to have a relatively higher priority.

[0057] In some implementations, if Pri(TRP) PUCCH ) greater than Pri(TRP PUSCH If UE 104 can select one of two sub-options, then UE 104 can discard PUSCH duplicates that conflict with PUCCH 404, such as PUSCH duplicates #1 and #2, and transmit the remaining duplicates. This is shown as Figure 4Transmission sequence 416. In the second option, UE104 may discard all PUSCH duplicates, resulting in transmission sequence 420 that includes only PUCCH.

[0058] In some implementations, if Pri(TRP) PUSCH )) greater than Pri(TRP PUCCH If ), then UE 104 can discard PUCCH 204. The resulting transmission sequence 424 can then correspond to PUSCH repeat 208.

[0059] Figure 5 A conflict resolution process 500, which may be used as a second option in case 2 according to some embodiments, is illustrated. The conflict resolution process 500 includes a PUCCH 504 that conflicts with a first and second repetition of PUSCH repetition 508. In this embodiment, UE 104 may multiplex the UCI to a first actual PUSCH repetition among repetitions having the same beam that satisfy (e.g., as defined in part 9.2.5 of TS 38.214) timeline constraints. As used herein, the first “actual PUSCH” may refer to the first PUSCH transmission that is actually to be transmitted. UE 104 may determine that: PUSCH repetition #1 is the first PUSCH repetition for a transmission beam X that satisfies the timeline constraints; and PUSCH repetition #3 is the first PUSCH repetition for a transmission beam Y that satisfies the timeline constraints. Therefore, UE 104 may generate a sequence 512 in which the UCI is multiplexed to PUSCH repetition #1 and PUSCH repetition #3.

[0060] The conflict resolution process 500 can be independent of the TRP index associated with the PUSCH / PUCCH transmission. Alternatively, when the TRP indices are the same, the conflict resolution process 500 can be used as an alternative scheme, such as transmission sequence 412.

[0061] In some implementations, a third option, which may also be based on the conflict resolution process of Principle 1, Case 2, can be used. In this option, the UCI can be multiplexed across all PUSCH repetitions. In various implementations, this can be based on or independent of considerations of the target TRP associated with the PUCCH or PUSCH transmission.

[0062] In some implementations, for example, case 3 – where a repeating PUCCH conflicts with a PUSCH of repeating type A or B – may include options 1 through 3, which are similar to the options described above with respect to case 2.

[0063] Figure 6 This includes a conflict resolution process 600 based on some implementation schemes. The conflict resolution process 600 may be based on principles 2 and 3.

[0064] The conflict resolution process 600 may correspond to the first option for case 3, where a repeating PUCCH conflicts with a PUSCH having repeat type A or B. Specifically, a PUCCH repeat 604 may conflict with the first two repeats of a PUSCH repeat 608. A PUSCH repeat 608 is shown as having repeat type A, with one repeat per time slot; however, a similar concept also applies to PUSCH repeats of type B.

[0065] If PUCCH repeat 604 and PUSCH repeat 608 are associated with the same TRP, for example, TRP PUSCH Equal to TRP PUCCH Then UE 104 can multiplex the UCI from PUCCH repeat 604 to all PUSCH repeats 608, resulting in PUSCH repeats of transmission sequence 612. The PUSCH repeats of transmission sequence 612 can then be transmitted to TRP.

[0066] If PUCCH repeat 604 and PUSCH repeat 608 are associated with different TRPs, for example, if TRP PUCCH Unlike TRP PUSCH Then UE 104 can determine the transmission based on the priority of the associated TRP index, such as the CORESET pool index. In some implementations, a CORESET pool index with a lower value may be considered to have a relatively higher priority.

[0067] In some implementations, if Pri(TRP) PUCCH ) greater than Pri(TRP PUSCH If UE 104 can select one of two sub-options, then UE 104 can discard PUSCH duplicates that conflict with PUCCH 604, such as PUSCH duplicates #1 and #2, and transmit the remaining duplicates. This is shown as Figure 6 Transmission sequence 616. In the second sub-option, UE104 may discard all PUSCH duplicates, resulting in transmission sequence 620 that includes only PUCCH duplicates.

[0068] In some implementations, if Pri(TRP) PUSCH )) greater than Pri(TRP PUCCHIf the UE 104 discards one or more of the PUCCH repeats 604, the resulting transmission sequence 624 can then correspond to the PUSCH repeat 608. In some embodiments, only PUCCH repeats with overlapping symbols can be discarded. For example, if one or more PUCCH repeats do not overlap with a PUSCH repeat, these repeats can be transmitted. In other embodiments, all PUCCH repeats can be discarded even if only some of the PUCCH repeats overlap with the PUSCH repeat.

[0069] Figure 7 A conflict resolution process 700, which is a second option available in scenario 3 according to some implementation schemes, is shown. The conflict resolution process 700 may be based on principle 1.

[0070] The conflict resolution process 700 includes a PUCCH repeat 704 that conflicts with the first and second repeats of the PUSCH repeat 708. In this embodiment, the UE 104 may multiplex the UCI to the first actual PUSCH repeat among repeats having the same beam that satisfy (e.g., as defined in part 9.2.5 of TS 38.214) timeline constraints. The UE 104 may determine that: PUSCH repeat #1 is the first PUSCH repeat for a transmission beam X that satisfies the timeline constraints; and PUSCH repeat #3 is the first PUSCH repeat for a transmission beam Y that satisfies the timeline constraints. Therefore, the UE 104 may generate a sequence 712 in which the UCI is multiplexed to PUSCH repeat #1 and PUSCH repeat #3.

[0071] The conflict resolution process 700 can be independent of the TRP index associated with the PUSCH / PUCCH transmission. Alternatively, when the TRP indices are the same, the conflict resolution process 700 can be used as an alternative scheme, such as transmission sequence 612.

[0072] In some implementations, a third option, which may also be based on the conflict process of Principle 1, Case 3, can be used. In this option, the UCI can be multiplexed across all PUSCH repetitions. In various implementations, this can be based on or independent of considerations of the target TRP associated with the PUCCH or PUSCH transmission.

[0073] In some implementations, different options can be used for PUCCHs that repeat within a time slot or across time slots. For example, option 1 can be used when a PUCCH repeats within a time slot, while option 2 can be used when a PUCCH repeats across time slots. In other implementations, other options can be used.

[0074] The conflict resolution process for scenario 4 – where a duplicate PUCCH conflicts with another duplicate PUCCH – can be based on the relative priority of the PUCCHs. A priority-based conflict resolution process based on principles 1 through 3 may include UE 104 discarding at least some of the duplicate PUCCHs with lower priority.

[0075] In various implementations, priority may be based on one or more of the following: UCI type, associated TRP index (e.g., CORESET pool index); number of beams across all repeat configurations used for PUCCH transmission; start slot index; or repeat type (e.g., intra-slot repeat or inter-slot repeat).

[0076] Regarding UCI types, some implementations may include HARQ-ACK, SR, CSI with high priority, and CSI with low priority, in descending order of priority.

[0077] Regarding the associated TRP index, some implementations may assign higher priority to a lower index, which may be a TRP index or a CORESET pool index.

[0078] Regarding the number of beams, some implementations may assign higher priority to PUCCHs that repeat across more beams. For example, if a first PUCCH has repeats across three beams and a second PUCCH has repeats across all beams, the first PUCCH may have a higher priority than the second PUCCH. In other implementations, the priorities may be reversed, with the second PUCCH having a relatively higher priority.

[0079] Regarding the start slot index, some implementations may assign a higher priority to PUCCHs that have an earlier start slot index.

[0080] Regarding repetition type, some implementations may assign higher priority to PUCCHs with intra-slot repetition. Other implementations may reverse the priority, and PUCCHs with inter-slot repetition may be given higher priority.

[0081] Various implementations may include nested prioritization based on the above PUCCH characteristics. A first example may include the following: first, determining the PUCCH priority by the number of beams to be used for transmitting PUCCH repetitions. If the number of beams is the same, priority is determined by the UCI type. If the UCI types are the same, priority is determined by the start slot index. A second example may include the following: first, determining the PUCCH priority by the associated TRP index. If the PUCCH is associated with the same TRP index, priority is determined by the UCI type. If the UCI types are the same, priority is determined by the start slot index. Other implementations may include other examples of nested prioritization.

[0082] The solution to Case 5 – a conflict between duplicate PUCCHs and non-duplicate PUSCHs – can be implemented as follows. UE 104 can determine whether to discard the PUSCH or the PUCCH based on Option 1 of Case 1. For example, see... Figure 2 The conflict resolution process 200.

[0083] The solution to scenario 6 – conflict between repeating PUCCHs and aperiodic SRS – can be implemented as follows: If the PUCCH priority is configured to 0, only repeating and overlapping symbols of the PUCCH can be discarded. This can be applied to PUCCHs that repeat within or across time slots.

[0084] For case 7, where there is a conflict between a duplicate PUSCH and SRS, if the PUSCH is configured to have a priority of 1, then UE 104 may not transmit the SRS and the overlapping symbols. Otherwise, the conflict is not allowed in the SRS transmission after the PUSCH.

[0085] In some implementations, the additional option may be considered as introducing higher-level signaling to determine which channels should be dropped. This higher-level signaling (which may be RRC signaling) can be used in any of cases 1 through 7. In various implementations, the default conflict resolution procedure may operate as described above in any of cases 1 through 7. This default procedure can be overridden by higher-level signaling.

[0086] In some implementations, scheduling restrictions may be introduced to avoid the specific conflicts described above with respect to cases 1 through 7.

[0087] Figure 8 It may include an operation flow / algorithm structure 800 according to some implementation schemes. The operation flow / algorithm structure 800 may be executed or implemented by a UE (such as, for example, UE 104 or 1200) or its components (such as baseband processor 1204A).

[0088] The operation flow / algorithm structure 800 may include, at 804, identifying a conflict between a first uplink channel transmission and a second uplink channel transmission. The first and second uplink channel transmissions may be PUSCH or PUCCH transmissions with or without repetition. If the physical uplink channel transmissions include repetition, these repetitions may occur in consecutive time slots (e.g., repetition type A) or in consecutive symbols within a time slot or across time slots (e.g., repetition type B).

[0089] In some implementations, collisions can be identified at the mapping function in the UE's physical layer processing. Collisions can occur based on at least partial overlap of transmissions in time or frequency. In various implementations, collisions can resemble any of the collisions described above with respect to cases 1 through 7. In various implementations, additional or alternative collision scenarios can be detected and resolved.

[0090] The operation flow / algorithm structure 800 may further include: at 808, determining the target TRP for the first physical uplink channel transmission and the second physical uplink channel transmission. In some embodiments, the target TRP may be determined based on a TRP index (e.g., a CORESET pool index) associated with each physical uplink channel transmission in the physical uplink channel transmission. In some embodiments, the association between the TRP index and the physical uplink channel transmission may be based on PDCCH scheduling or otherwise configured with resources for the physical uplink channel transmission.

[0091] The operation flow / algorithm structure 800 may further include: at 812, performing a conflict resolution process based on the target TRP. The conflict resolution process may be similar to any of the conflict resolution processes described above. For example, in some embodiments, the conflict resolution process may include determining the relative priority of the first physical uplink channel transmission and the second physical uplink channel transmission based on the target TRPs associated with each of the first and second physical uplink channel transmissions. In some embodiments, this can be accomplished by prioritizing transmissions associated with lower TRP indices. Other embodiments may include other prioritization methods.

[0092] In some implementations, if the target TRPs are the same, the UCI from the PUCCH transmission can be multiplexed to one or more PUSCH repetitions used for transmission. If the target TRPs are different, transmissions associated with relatively higher priority TRPs can be transmitted, and some or all of the transmissions associated with relatively lower priority TRPs can be discarded.

[0093] The operation flow / algorithm structure 800 may further include, at 816, transmitting a first physical uplink channel transmission or a second physical uplink channel transmission. In some embodiments, only the higher-priority physical uplink channel transmission may ultimately be transmitted. In other embodiments, portions of the lower-priority physical uplink channel transmission may also be transmitted. For example, in some embodiments, non-overlapping repetitions of the lower-priority physical uplink channel transmission may be transmitted. In other embodiments, information from the lower-priority physical uplink channel transmission may be multiplexed with the higher-priority physical uplink channel transmission, as described herein.

[0094] Figure 9 It may include an operation flow / algorithm structure 900 according to some implementation schemes. The operation flow / algorithm structure 900 may be executed or implemented by a UE (such as, for example, UE 104 or 1200) or its components (such as baseband processor 1204A).

[0095] The operation flow / algorithm structure 900 may include: at 904, detecting a conflict between the first PUCCH repetition and the second PUCCH repetition. The conflict detected at 904 may correspond to case 4 described herein.

[0096] The operation flow / algorithm structure 900 may further include: at 908, determining priority information associated with the first PUCCH repeat and the second PUCCH repeat. The priority information may include information related to parameters configured for the transmission of the respective PUCCH repeat. In some embodiments, these parameters may include information related to a target TRP (e.g., the associated TRP index), the number of beams on which the respective PUCCH repeat is to be transmitted, the start time slot on which the respective PUCCH repeat is to be transmitted, the repeat type of the respective PUCCH repeat, or the type of UCI carried in the respective PUCCH repeat.

[0097] The operation flow / algorithm structure 900 may also include: at 912, determining that the first PUCCH repetition has a relatively high priority. The relative priority can be determined by referring to one or more parameters in the priority information. As described elsewhere, nested priorities may include multiple parameters referenced in a defined order. For example, if the first parameter is equal among the corresponding PUCCH repetitions, the relative priority can be determined by referring to the second parameter, and so on.

[0098] The operation flow / algorithm structure 900 may further include: at 916, transmitting a first PUCCH repeat and discarding one or more second PUCCH repeats. In some embodiments, only repeats of the second PUCCH that overlap / conflict with the first PUCCH repeat may be discarded. Alternatively, all repeats of the second PUCCH may be discarded, regardless of whether they overlap / conflict with the first PUCCH repeat.

[0099] Figure 10 It may include an operation flow / algorithm structure 1000 according to some implementations. In some implementations, the operation flow / algorithm structure 1000 may be executed or implemented by a UE (e.g., UE 104 or 1200) or its components (e.g., baseband processor 1204A).

[0100] The operation flow / algorithm structure 1000 may include: at 1004, identifying conflicts between PUCCH and PUSCH transmissions. PUSCH transmissions may include multiple PUSCH repetitions to be transmitted on at least two beams.

[0101] The operation flow / algorithm structure 1000 may further include: at 1008, multiplexing the UCI transmitted from the PUCCH onto a PUSCH repeat in each of the multiple beams. In some implementations, the UCI may be transmitted only on one PUSCH repeat per beam. A specific PUSCH repeat may be selected based on timeline constraints. For example, the selected PUSCH repeat may be the earliest occurring PUSCH repeat capable of carrying the UCI. In various implementations, this may be determined based on configuration information provided by the gNB or the processing capability of the UE. In other implementations, the UCI may be multiplexed onto all PUSCH repeats.

[0102] The operation flow / algorithm structure 1000 may also include: at 1012, transmitting PUSCH repeat.

[0103] Figure 11 A beamforming circuit 1100 according to some embodiments is shown. The beamforming circuit 1100 may include a first antenna panel (i.e., panel 1 1004) and a second antenna panel (i.e., panel 2 1108). Each antenna panel may include multiple antenna elements. Other embodiments may include other numbers of antenna panels.

[0104] The digital beamforming (BF) component 1128 can be derived from, for example, a baseband processor (such as, for example...) Figure 12 The baseband processor 1204A receives the input baseband (BB) signal. The digital BF component 1128 can rely on complex weights to precode the BB signal and provide beamformed BB signals to the parallel radio frequency (RF) chains 1120 / 1124.

[0105] Each RF chain 1120 / 1124 may include a digital-to-analog converter that converts the BB signal into the analog domain; a mixer that mixes the baseband signal into an RF signal; and a power amplifier that amplifies the RF signal for transmission.

[0106] RF signals can be provided to analog beamforming components 1112 / 1116, which can further apply beamforming by providing a phase shift in the analog domain. The RF signals can then be provided to antenna panels 1104 / 1108 for transmission.

[0107] In some implementations, beamforming may be performed only in the digital domain or only in the analog domain, instead of the hybrid beamforming shown herein.

[0108] In various implementations, control circuitry residing in the baseband processor can provide BF weights to the analog / digital BF components to provide a transmission beam at the corresponding antenna panel. These BF weights can be determined by the control circuitry to provide directional assignment of the serving cell as described herein. In some implementations, the BF components and antenna panels can operate together to provide a dynamic phased array capable of guiding the beam in the desired direction.

[0109] Figure 12 A UE 1200 according to some implementation schemes is shown. UE 1200 may be similar to Figure 1 The UE 104 is essentially interchangeable with it.

[0110] The UE 1200 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, computer, tablet, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, stock sensors, voltmeters / ammeters, actuators, etc.), video surveillance / monitoring devices (e.g., cameras, camcorders, etc.), wearable devices (e.g., smartwatches), and loosely coupled IoT devices. In some implementations, the UE can be a RedCap UE or an NR-Light UE.

[0111] UE 1200 may include a processor 1204, RF interface circuitry 1208, memory / storage device 1212, user interface 1216, sensor 1220, drive circuitry 1222, power management integrated circuit (PMIC) 1224, antenna structure 1226, and battery 1228. Components of UE 1200 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 12The block diagram is intended to show a high-level view of some of the components of the UE 1200. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0112] The components of UE 1200 can be coupled to various other components via one or more interconnects 1232, which can represent any type of interface, input / output, bus (local, system, or extended), transmission line, trace, optical connector, etc., that allows various circuit components (on common or different chips or chipsets) to interact with each other.

[0113] Processor 1204 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 1204A, central processing unit circuitry (CPU) 1204B, and graphics processing unit circuitry (GPU) 1204C. Processor 1204 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 1212) to cause UE 1200 to perform the operations described herein.

[0114] In some implementations, the baseband processor circuit 1204A can access the communication protocol stack 1236 in the memory / storage device 1212 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 1204A can access the communication protocol stack to perform user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access layers. In some implementations, PHY layer operation may additionally / optionally be performed by components of the RF interface circuit 1208.

[0115] The baseband processor circuit 1204A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR may be based on cyclic prefix OFDM (“CP-OFDM”) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (“DFT-S-OFDM”) in the uplink.

[0116] Memory / storage device 1212 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 1236) that can be executed by one or more processors in processor 1204 to cause UE 1200 to perform the various operations described herein. Memory / storage device 1212 includes any type of volatile or non-volatile memory that can be distributed throughout UE 1200. In some embodiments, some memory / storage devices in memory / storage device 1212 may be located on processor 1204 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 1212 may be located external to processor 1204 but accessible via a memory interface. Memory / storage device 1212 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0117] The RF interface circuit 1208 may include transceiver circuitry and a radio frequency front-end module (RFEM), which allows the UE 1200 to communicate with other devices via a radio access network. The RF interface circuit 1208 may include various components arranged in the transmission or reception path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0118] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 1226 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 1204.

[0119] In the transmission path, the transceiver's transmitter upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 1226.

[0120] In various implementations, the RF interface circuit 1208 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0121] Antenna 1226 may include antenna elements to convert electrical signals into radio waves for propagation through the air and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 1226 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input / multiple-output communication. Antenna 1226 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna 1226 may have one or more panels designed for a specific frequency band included in FR1 or FR2.

[0122] User interface circuitry 1216 includes various input / output (I / O) devices designed to enable users to interact with UE 1200. User interface circuitry 1216 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes "LEDs") and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays "LCDs," LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 1200.

[0123] Sensor 1220 may include devices, modules, or subsystems intended to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0124] The driving circuit 1222 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1200. The driving circuit 1222 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 1200. For example, the driving circuit 1222 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings of the sensor circuit 1220 and controlling and allowing access to the sensor circuit 1220; a driver for acquiring actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0125] The PMIC 1224 manages the power supplied to various components of the UE 1200. Specifically, relative to the processor 1204, the PMIC 1224 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0126] In some implementations, the PMIC 1224 can control or otherwise become part of various power-saving mechanisms of the UE 1200. For example, if the platform UE is in the RRC_Connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, it can enter a state known as Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, the UE 1200 can power down for short intervals to save power. If there is no data traffic activity over a longer period, the UE 1200 can transition to the RRC_Idle state, where it is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The UE 1200 enters a very low-power state and performs paging, in which it periodically wakes up again to listen to the network and then power down again. The UE 1200 may not receive data in this state; to receive data, the platform must transition back to the RRC_Connected state. Additional power-saving modes can allow the device to be unable to use the network for longer than the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will result in significant latency, which is assumed to be acceptable.

[0127] Battery 1228 can power UE 1200, but in some examples, UE 1200 may be mounted in a fixed location and may have a power source coupled to the mains. Battery 1228 may be a lithium-ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 1228 may be a typical lead-acid automotive battery.

[0128] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0129] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0130] Example

[0131] Further exemplary implementations are provided in the following sections.

[0132] Example 1 includes a method for operating a UE, the method comprising: identifying a conflict between a first physical uplink channel transmission and a second physical uplink channel transmission; determining a target transmit / receive point (TRP) for the first physical uplink channel transmission and the second physical uplink channel transmission; performing a conflict resolution process based on the target TRP; and transmitting the first physical uplink channel transmission or the second physical uplink channel transmission based on the conflict resolution process.

[0133] Example 2 includes the method according to Example 1 or some other embodiment herein, wherein the first physical uplink channel transmission is a non-repeating physical uplink control channel (PUCCH) transmission, the second physical uplink channel transmission includes multiple physical uplink shared channel (PUSCH) repetitions, the first TRP is the target TRP for both the PUCCH transmission and the multiple PUSCH repetitions, and performing the conflict resolution process includes: multiplexing uplink control information (UCI) from the PUCCH transmission into all of the multiple PUSCH repetitions; and transmitting the multiple PUSCH repetitions having the UCI.

[0134] Example 3 includes the method according to Example 1 or some other embodiment of this document, wherein the first physical uplink channel transmission is a non-repeating physical uplink control channel (PUCCH) transmission, the second physical uplink channel transmission includes multiple physical uplink shared channel (PUSCH) repetitions, the first TRP is the target TRP for the PUCCH transmission, the second TRP is the target TRP for the multiple PUSCH repetitions, and performing the conflict resolution process includes: determining a relative priority between the PUCCH transmission and the multiple PUSCH repetitions based on information corresponding to the first TRP and the second TRP; discarding the first PUCCH transmission or one or more repetitions of the multiple PUSCH repetitions based on the relative priority; and transmitting the second PUCCH transmission or the one or more repetitions of the multiple PUSCH repetitions based on the relative priority.

[0135] Example 4 includes the method according to Example 3 or some other embodiment of this document, wherein the information corresponding to the first TRP and the second TRP includes a first TRP index associated with the first TRP and a second TRP index associated with the second TRP, wherein a higher relative priority is associated with a lower value of the first TRP index and the second TRP index.

[0136] Example 5 includes the method according to Example 4 or some other embodiment herein, wherein the first TRP index and the second TRP index include a first control resource set pool index and a second control resource set pool index.

[0137] Example 6 includes the method according to Example 3 or some other embodiment herein, wherein the plurality of PUSCHs are repeated in consecutive time slots or in consecutive symbols.

[0138] Example 7 includes the method according to Example 1 or some other embodiment of this document, wherein the first physical uplink channel transmission includes multiple physical uplink control channel (PUCCH) repeats, the second physical uplink channel transmission includes multiple physical uplink shared channel (PUSCH) repeats, the first TRP is the target TRP for the PUCCH transmission, the second TRP is the target TRP for the multiple PUSCH repeats, and performing the conflict resolution process includes: discarding at least some of the PUCCH repeats based on the determination that the multiple PUSCH repeats have a higher priority than the multiple PUCCH repeats; and transmitting the multiple PUSCH repeats and any of the multiple PUCCH repeats that were not discarded.

[0139] Example 8 includes the method according to Example 7 or some other embodiment herein, wherein discarding at least some of the PUCCH repeats includes discarding all of the PUCCH repeats or only discarding PUCCH repeats that overlap with the plurality of PUSCH repeats.

[0140] Example 9 includes the method according to Example 1 or some other embodiment herein, wherein the first physical uplink channel transmission includes multiple physical uplink control channel (PUCCH) repetitions, and the second physical uplink channel transmission is a physical uplink shared channel (PUSCH) transmission without repetitions.

[0141] Example 10 includes the method, which includes storing a first plurality of Physical Uplink Control Channel (PUCCH) repetitions and a second plurality of PUCCH repetitions; detecting a conflict between the first plurality of PUCCH repetitions and the second plurality of PUCCH repetitions; determining first priority information associated with the first plurality of PUCCH repetitions and second priority information associated with the second plurality of repetitions, wherein the first priority information and the second priority information include an associated Transmit Receive Point (TRP) index, a number of beams configured for transmission, a start time slot index, or a repetition type; determining, based on the first priority information and the second priority information, that the first plurality of PUCCH repetitions have a higher priority than the second plurality of repetitions; and, based on the determination that the first plurality of PUCCH repetitions have the higher priority, discarding one or more repetitions in the second plurality of PUCCH repetitions.

[0142] Example 11 includes the method according to Example 10 or some other embodiment of this document, wherein the first priority information includes a first TRP index, the second priority information includes a second TRP index, and the UE is used to determine that the first plurality of PUCCH repetitions have the higher priority based on the first TRP index having a value less than the second TRP index.

[0143] Example 12 includes the method according to Example 10 or some other embodiment herein, wherein the first priority information includes a first number of beams configured to transmit the first plurality of PUCCH repetitions, the second priority information includes a second number of beams configured to transmit the second plurality of PUCCH repetitions, and the method further includes determining that the first plurality of PUCCH repetitions have a higher priority based on the first number of beams being greater than the second number of beams.

[0144] Example 13 includes the method according to Example 10 or some other embodiment herein, wherein the first priority information and the second priority information further include the type of uplink control information carried by the first plurality of PUCCH repeats and the second plurality of PUCCH repeats.

[0145] Example 14 includes the method according to Example 13 or some other embodiment herein, wherein the first priority information includes a first number of beams configured to transmit the first plurality of PUCCH repetitions and a first type of UCI for the first plurality of PUCCH repetitions, the second priority information includes a second number of beams configured to transmit the second plurality of PUCCH repetitions and a second type of UCI for the first plurality of PUCCH repetitions, and the method further includes determining that the first plurality of PUCCH repetitions have the higher priority based on the determination that the first type of UCI has a higher priority than the second type of UCI.

[0146] Example 15 includes the method according to Example 13 or some other embodiment herein, wherein the first priority information includes a first TRP index for identifying a first TRP to which the first plurality of PUCCH repeats are to be transmitted and a first type of UCI for the first plurality of PUCCH repeats, the second priority information includes a second TRP index for identifying a second TRP to which the second plurality of PUCCH repeats are to be transmitted and a second type of UCI for the second plurality of PUCCH repeats, and the method further includes determining that the first plurality of PUCCH repeats have the higher priority based on the determination that the first type of UCI has a higher priority than the second type of UCI.

[0147] Example 16 includes a method of operating a UE, the method comprising: identifying a conflict between a Physical Uplink Control Channel (PUCCH) transmission and a Physical Uplink Shared Channel (PUSCH) transmission, wherein the PUSCH transmission includes multiple PUSCH repeats to be transmitted on at least two beams; multiplexing uplink control information (UCI) from the PUCCH transmission to a first PUSCH repeat to be transmitted on a first beam of the at least two beams and a second PUSCH repeat to be transmitted on a second beam of the at least two beams; and transmitting the multiple PUSCH repeats.

[0148] Example 17 includes the method according to Example 16 or some other embodiment herein, wherein the multiplexing includes multiplexing UCI transmitted from the PUCCH to each of the plurality of PUSCH repeats.

[0149] Example 18 includes the method according to Example 16 or some other embodiment herein, further comprising: selecting the earliest PUSCH repeat of the first beam that satisfies the timeline constraint associated with the UCI as the first PUSCH repeat; and selecting the earliest PUSCH repeat of the second beam that satisfies the timeline constraint associated with the UCI as the second PUSCH repeat.

[0150] Example 19 includes the method according to Example 18 or some other embodiment herein, wherein the first PUSCH repeat is the earliest PUSCH repeat of the first beam that satisfies the timeline constraint and is actually to be transmitted; and the second PUSCH repeat is the earliest PUSCH repeat of the second beam that satisfies the time constraint and is actually to be transmitted.

[0151] Example 20 includes the method according to Example 16 or some other embodiment herein, wherein the first beam in the second beam includes different probe reference signal resource indicators, transmission precoder matrix indicators, or power control parameters.

[0152] Example 21 may include an apparatus comprising one or more elements for performing the method described or associated with any of Examples 1 to 20 or any other method or process described herein.

[0153] Example 22 may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein, as described or associated with any of Examples 1 to 20.

[0154] Example 23 may include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of the method described or associated with any of Examples 1 to 20 or any other method or process described herein.

[0155] Example 24 may include a method, technique, or process, or a part or component thereof, described or associated with any of Examples 1 to 20.

[0156] Example 25 may include an apparatus comprising one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described or associated with any of Examples 1 to 20.

[0157] Example 26 may include a signal, or a portion thereof, described or associated with any of Examples 1 to 20.

[0158] Example 27 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or associated with any of Examples 1 to 20, or otherwise described in this disclosure.

[0159] Example 28 may include a signal encoded with data according to or associated with any of Examples 1 to 20, or a portion or component thereof, or otherwise described in this disclosure.

[0160] Example 29 may include a signal, or a portion or component thereof, encoded as a datagram, IE, packet, frame, segment, PDU, or message according to or in connection with any of Examples 1 to 64 described above, or otherwise described in this disclosure.

[0161] Example 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause one or more processors to perform the methods, techniques, or processes, or portions thereof, described or associated with any of Examples 1 to 20.

[0162] Example 31 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform, or in part with, the methods, techniques or processes described or associated with any of Examples 1 to 20.

[0163] Example 32 may include signals in a wireless network as shown and described herein.

[0164] Example 33 may include methods for communicating in a wireless network as shown and described herein.

[0165] Example 34 may include a system for providing wireless communication as shown and described herein.

[0166] Example 35 may include a device for providing wireless communication as shown and described herein.

[0167] Unless otherwise expressly stated, any of the examples above may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.

[0168] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed by one or more processors, cause a user-equipped UE to perform the following operations: Identify the conflict between a first physical uplink channel transmission and a second physical uplink channel transmission, wherein the first physical uplink channel transmission is a non-repeating physical uplink control channel (PUCCH) transmission, and the second physical uplink channel transmission includes multiple repetitions of the physical uplink shared channel (PUSCH). Determine the first target transmit / receive point (TRP) for transmission on the first physical uplink channel; Determine the second target TRP for transmission on the second physical uplink channel; Based on the target TRP, a conflict resolution process is executed, wherein, in order to execute the conflict resolution process, the execution of the instructions causes the UE to: The relative priority between the PUCCH transmission and the plurality of PUSCH repetitions is determined based on the information corresponding to the first TRP and the second TRP. The first PUCCH transmission in the PUCCH transmission or one or more repetitions in the plurality of PUSCH repetitions are discarded based on the relative priority. as well as Based on the relative priority, the second PUCCH transmission in the PUCCH transmission or one or more repetitions in the plurality of PUSCH repetitions are output for transmission.

2. One or more computer-readable media according to claim 1, wherein the information corresponding to the first TRP and the second TRP includes a first TRP index associated with the first TRP and a second TRP index associated with the second TRP, wherein a higher relative priority is associated with a lower value of the first TRP index and the second TRP index.

3. The computer-readable medium according to claim 2, wherein the first TRP index and the second TRP index comprise a first control resource set pool index and a second control resource set pool index.

4. One or more computer-readable media according to claim 1, wherein the plurality of PUSCHs are repeated in consecutive time slots or in consecutive symbols.

5. A user equipment (UE), the UE comprising: A memory for storing configuration information; as well as Processing circuitry, coupled to the memory, is used to: Identify the conflict between a first physical uplink channel transmission and a second physical uplink channel transmission, wherein the first physical uplink channel transmission is a non-repeating physical uplink control channel (PUCCH) transmission, and the second physical uplink channel transmission includes multiple repetitions of the physical uplink shared channel (PUSCH). Determine the first target transmit / receive point (TRP) for transmission on the first physical uplink channel; Determine a second target TRP for transmission on the second physical uplink channel; perform a conflict resolution process based on the first target TRP and the second target TRP, wherein, in order to perform the conflict resolution process, the processing circuitry is configured to: The relative priority between the PUCCH transmission and the plurality of PUSCH repetitions is determined based on the information corresponding to the first TRP and the second TRP. The first PUCCH transmission in the PUCCH transmission or one or more repetitions in the plurality of PUSCH repetitions are discarded based on the relative priority. The second PUCCH transmission in the PUCCH transmission or one or more repetitions in the plurality of PUSCH repetitions are transmitted based on the relative priority. as well as Based on the relative priority, the second PUCCH transmission in the PUCCH transmission or one or more repetitions in the plurality of PUSCH repetitions are output for transmission.

6. The UE of claim 5, wherein the information corresponding to the first TRP and the second TRP includes a first TRP index associated with the first TRP and a second TRP index associated with the second TRP, wherein a higher relative priority is associated with a lower value of the first TRP index and the second TRP index.

7. The UE according to claim 6, wherein the first TRP index and the second TRP index include a first control resource set pool index and a second control resource set pool index.

8. The UE of claim 5, wherein the plurality of PUSCHs are repeated in consecutive time slots or in consecutive symbols.

9. A method for operating a user equipment (UE), the method comprising: Identify conflicts between Physical Uplink Control Channel (PUCCH) transmissions and Physical Uplink Shared Channel (PUSCH) transmissions, wherein the PUSCH transmissions include multiple PUSCH repetitions to be transmitted on at least two beams; The earliest PUSCH repetition to be transmitted on the first beam that satisfies the timeline constraints associated with the uplink control information (UCI) is selected as the first PUSCH repetition; and The earliest PUSCH repeat to be transmitted on the second beam of the at least two beams that satisfies the timeline constraint associated with the UCI is selected as the second PUSCH repeat. The UCI transmitted from the PUCCH is multiplexed to the first PUSCH repeat to be transmitted on the first beam of the at least two beams and the second PUSCH repeat to be transmitted on the second beam of the at least two beams; and The multiple PUSCH outputs are repeated for transmission.

10. The method of claim 9, wherein the first PUSCH repeat is the earliest PUSCH repeat of the first beam that satisfies the timeline constraint and is actually to be transmitted; and the second PUSCH repeat is the earliest PUSCH repeat of the second beam that satisfies the time constraint and is actually to be transmitted.

11. The method of claim 9, wherein the first beam in the second beam includes different probe reference signal resource indicators, transmission precoder matrix indicators, or power control parameters.

12. A user equipment (UE), the UE comprising: Memory circuits; as well as The processing circuit, coupled to the memory circuit, is used to: Identify conflicts between Physical Uplink Control Channel (PUCCH) transmissions and Physical Uplink Shared Channel (PUSCH) transmissions, wherein the PUSCH transmissions include multiple PUSCH repetitions to be transmitted on at least two beams; The earliest PUSCH repetition to be transmitted on the first beam that satisfies the timeline constraints associated with the uplink control information (UCI) is selected as the first PUSCH repetition; and The earliest PUSCH repetition to be transmitted on the second beam of the at least two beams that satisfy the timeline constraints associated with the UCI is selected as the second PUSCH repetition. The UCI transmitted from the PUCCH is multiplexed by the first PUSCH repeat and the second PUSCH repeat; and The multiple PUSCH outputs are repeated for transmission.

13. The UE of claim 12, wherein the first PUSCH repeat is the earliest PUSCH repeat of the first beam that satisfies the timeline constraint and is actually to be transmitted; and the second PUSCH repeat is the earliest PUSCH repeat of the second beam that satisfies the time constraint and is actually to be transmitted.

14. The UE of claim 12, wherein the first beam in the second beam includes different probe reference signal resource indicators, transmission precoder matrix indicators, or power control parameters.

Images