WO2022032158A1 - Mechanisms for pusch and for pucch multi trp repetition - Google Patents

Abstract

The apparatus of gNodeB, a system, a method and a machine-readable medium. The apparatus includes one or more processors to: encode a message to indicate physical uplink shared channel (PUSCH) repetitions associated with two different TCI states, TCI 1 and TCI 2, respectively; and send the message to communication resources of the gNodeB for the communication resources to cause a transmission of the message to the UE. The one or more processors are to: encode another message to indicate physical uplink shared channel (PUCCH) repetitions, the repetitions being associated with two different TCI states, TCI 1 and TCI 2, respectively, the repetitions further including slot-wise repetitions or subslot-wise repetitions; and send the second message to communication resources of the gNodeB for the communication resources to cause a second transmission of the second message to the UE.

Description

MECHANISMS FOR PUSCH AND FOR PUCCH MULTI TRP REPETITION

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This Application claims the benefit of, and priority from, U.S. Provisional Patent Application No. 63/063,091, entitled “Mechanisms For PUCHH Multi Trp Repetition” and filed August 7, 2021, and U.S. Provisional Patent Application No. 63/063,042, entitled “Mechanisms for PUSCH multi TRP repetition” and filed August 7, 2021. The disclosures of the prior Applications are considered part of and are incorporated by reference in the disclosure of this Application.

BACKGROUND

[0002] Various embodiments generally may relate to the field of wireless communications, and in particular, to the field of communication in a cellular network compliant with one of more Third Generation Partnership Project (3GPP) specifications.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

[0004] Fig. 1 illustrates signaling diagrams for PUSCH repetitions for Type A and for Type

B.

[0005] Fig. 2 is a signaling diagrams showing TCI state to PUSCH repetition mapping before PUSCH segmentation takes place and after PUSCH takes place.

[0006] Fig. 3 is a signaling diagrams showing TCI state to PUSCH repetition mapping before PUSCH segmentation takes place and after PUSCH takes place.

[0007] Figs. 4A and 4B illustrate radio transmissions, showing respective examples of HARQ-ACK feedback for multiple physical downlink shared channels (PDSCHs) Rel. 15 and Rel. 16, respectively.

[0008] Figs. 5A and 5B illustrate radio transmissions similar to those in Figs. 4A and 5B, and showing respective examples of HARQ-ACK feedback for multiple PDSCH in PUCCH repetitions on a slot-wise and subslot-wise level, respectively. [0009] Figs. 6A and 6B show respective radio transmissions each with PUCCH repetition for TCI 1 and TCI 2 within a same PUCCH resource instance for a PUCCH format 1, without and with frequency hopping, respectively.

[0010] Figs. 7A and 7B show respective radio transmissions each with PUCCH repetition for TCI 1 and TCI 2 within a same PUCCH resource instance for a PUCCH format 3/4, without and with frequency hopping, respectively.

[0011] Fig. 8 illustrates a wireless network in accordance with various embodiments.

[0012] Fig. 9 illustrates a User Equipment (UE) and a Radio Access Node (RAN) in wireless communication according to various embodiments.

[0013] Fig. 10 illustrates components according to some example embodiments, the components able to read instructions from a machine-readable or computer-readable medium and perform any one or more of the methodologies discussed herein.

[0014] Fig. 11 illustrates a flow chart for a process according to a first embodiment.

[0015] Fig. 12 illustrates a flow chart for a process according to a second embodiment.

DETAILED DESCRIPTION

[0016] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

[0017] This disclosure is related to the 5G New Radio (NR) Release 17 Multiple-Input Multiple-Output (MIMO) enhancements work item on Enhancements on physical uplink shared channel (PUSCH) and for physical uplink control channel (PUCCH). In this disclosure, we propose methods to determine PUSCH repetitions and methods to determine PUCCH repetitions for reliability. [0018] PUSCH repetitions from different transmission reception points (TRPs) (different transmission configuration indicator TCI states) considering TCI state mapping to different repetitions for Type B PUSCH, dynamic indication of 1 TRP or 2 TRP repetitions and precoder cycling will now be described below.

[0019] Embodiments herein enable the network to allocate PUSCH repetitions targeted to different TRPs (different TCI states) building on the signaling framework that is existing in Release 15 (Rel. 15) and Release 16 (Release 16) of 3GPP’s New Radio (NR) or 5G technical specifications.

[0020] Embodiments further enable the network to allocate PUCCH repetitions targeted to different TRPs (different TCI states) building on the signaling framework that is existing in Release 15 (Rel. 15) and Release 16 (Release 16) of 3GPP’s New Radio (NR) or 5G technical specifications.

[0021] PUSCH Repetitions

[0022] Reference is now made to Fig. 1, which shows signaling diagrams 100 for PUSCH repetitions for Type A (Rel. 15) at diagram 100A and for Type B (Rel. 16) at diagram 100B. Referring to diagram 100A, in LTE, slot-based transmission (Physical downlink shared channel (PDSCH)ZPUSCH mapping Type A) is used where one slot (such as slot n or slot n+1 as shown) is a transmission time interval. The transmission, such as a PUSCH repetition as shown, could therefore include repetition of a PUSCH where each PUSCH starts or ends only at the beginning or end of a slot, respectively. Therefore, a PUSCH repetition scheme involving a repeated PUSCH scheduled by downlink control information (DCI) after a prior PUSCH that ends at the end of a prior slot can only be scheduled to end at the end of the current slot, which can result, as seen in diagram 100A, in the repeated PUSCH being received in full after a latency deadline. For example, this alignment time based on a slot-based transmission interval is harmful to ultrareliable low latency communication (URLLC) with low latency requirement.

[0023] Referring now to diagram 100B, in 5G, to further reduce latency, the transmission time interval is shortened from one slot to subslots for Type B transmissions. Subslot-based transmission (PDSCH/PUSCH mapping Type B) has been introduced where a packet is scheduled in a transmission time interval subslot of a number of orthogonal frequency multiplexing (OFDM) symbols, such as 2, 4 or 7 OFDM symbols. A transmission can start or end, in a Type B mapping of a transmission according to 5G, at the beginning or end, respectively, of the subslot transmission time interval, and, as a result, has more occasions to start in one slot instead of only one occasion in a slot as compared with the case in LTE. Thus, for a Type B PUSCH repetition, a repeated PUSCH can occur without ensuring, as would have been required for a Type A PUSCH repetition, that a between a beginning of a prior PUSCH and a beginning of its repeated PUSCH be on slot. As suggested by diagrams 100A and 100B, a Type B regime reduces the waiting time before an arriving packet is transmitted, by making it possible that a distance between same points in a time domain of a prior PUSCH and of its repeated PUSCH can be less than one slot.

[0024] PUSCH repetitions for both Type A and Type B mapping

[0025] As noted previously, Type A PUSCH repetition is at slot-level and limited to 1 layer (specified in Rel-15) which is further enhanced in Rel-16 to Type B to back-to-back repetitions for the purposes of latency. According to some embodiments, multi -TRP repetitions may be employed for both Type A and Type B repetitions and at least enable up to rank-2 transmissions. [0026] The rank indication or the RI in LTE corresponds to control information that a UE will report to a Node B (or NodeB) in an uplink transmission. For example, for a two antenna case, RANK1 means the UE is seeing a good signal to interference and noise ratio (SINR) on only one of its receive antennas, and, as a result, the NodeB is to bring down the transmission mode to single antenna or transmit diversity. A RANK2 from the UE means good SINR on both the antenna ports, which means that the Node B can schedule MIMO for transmission to both antennas of the UE.

[0027] Thus, according to some embodiments, a New Radio or 5GNode B (gNodeB) is to indicate to a UE a PUSCH repetition targeting two different TCI states (two different TRPs), that is, a first PUSCH repetition associated with a first TCI state and a second PUSCH repetition associated with a second TCI state.

[0028] TCI state mapping for Type B PUSCH repetition

[0029] In PUSCH Type B mapping, the nominal PUSCH allocations are segmented due to conflicts with slot boundary and semi-statically configured downlink (DL) symbols. The association according to some embodiments of PUSCH repetition to TCI-state may be done before or after the segmentation of PUSCH allocations. According to some embodiments, transport block size (TBS) determination may be based on indicated L value before segmentation while encoding, rate-matching, redundancy version (RV) assignment may be performed after segmentation based on actual repetitions.

[0030] Mapping of TCI states to repetitions can be performed before or after segmentation for Type B PUSCH as shown in Fig. 2.

[0031] Figs. 2 and 3 are respective signaling diagrams 200 and 300 showing TCI state to PUSCH repetition mapping before PUSCH segmentation takes place and after PUSCH takes plane. In Figs. 2 and 3, S represents the starting symbol number in each slot, L represents the length of each nominal repetition per slot in OFDM symbols, and K represents the number of nominal repetitions.

[0032] Diagrams 200A and 300A of Figs. 2 and 3 pertain to an example where S is at 8, L is at 6 and K is at 4, where “Rep #” designates a repetition number up to K repetitions, with no conflicting transmissions in a consecutive first, second and third slot. In the example of diagrams 200A and 300A, TCI assignments as between TCI 1 and TCI 2 toggle between consecutive PUSCH repetitions (back to back symbols including PUSCH repetitions) at the end of L = 6 symbols or at the end of a slot, whichever comes first. Thus, in diagrams 200A and 300A, in a first slot, TCI 1 assigned to Rep #1 (which starts at symbol 9 after S = 8 symbols in the first slot) and stretches to the end of the first slot completing L = 6 symbols. In a second slot, we thus toggle to TCI 2 at Rep #2 for L = 6 symbols, then toggle to TCI 1 at Rep #3 for L = 6 symbols, then toggle to TCI 2 assigned to Rep #4-1 for only 2 symbols (since two symbols represent as many symbols for the TCI 2 PUSCH repetition as would fit within remaining symbols of the second slot, in this case, 14 total symbols - 6 symbols for TCI 2 at Rep #2 - 6 symbols for TCI 1 at Rep #3= 2 symbols for TCI 2 at Rep #4-1). Since Rep #4-1 ends at a slot boundary, in the third slot, we toggle to TCI 1 at Rep #4-2 for 4 remaining symbols (that is, L of 6 symbols - 2 symbols for Rep #4-1 = 4 symbols left in the third slot for Rep #4-2).

[0033] Diagrams 200B and 300B of Figs. 2 and 3 pertain to an example where S is at 8, L is at 6 and K is at 4, where “Rep #” designates a repetition number up to K repetitions, with repeating DL transmissions at a fixed location of consecutive first, second and third slots. In the shown example, the DL transmission is a 4 symbol DL transmission in the beginning of each of the shown slots. In the example of diagrams 200B and 300B, TCI assignments as between TCI 1 and TCI 2 toggle between consecutive PUSCH repetitions at the end of L = 6 symbols that include the DL transmission, or at the end of a slot, whichever comes first. Thus, in diagrams 200B and 300B, in a first slot, TCI 1 assigned to Rep #1 (which starts at symbol 9 after S = 8 symbols in the first slot) and stretches to the end of the first slot completing L = 6 symbols. In a second slot, we thus toggle to TCI 2 at Rep #2 for L = 6 symbols, then toggle to TCI 1 at Rep #3 for L = 6 symbols, then toggle to TCI 2 assigned to Rep #4-1 for only 2 symbols (since two symbols represent as many symbols for the TCI 2 PUSCH repetition as would fit within remaining symbols of the second slot, in this case, 14 total symbols - 6 symbols for TCI 2 at Rep #2 - 6 symbols for TCI 1 at Rep #3= 2 symbols for TCI 2 at Rep #4-1). Since Rep #4-1 ends at a slot boundary, in the third slot, we toggle to TCI 1 at Rep #4-2 for 4 remaining symbols (that is, L of 6 symbols - 2 symbols for Rep #4-1 = 4 symbols left in the third slot for Rep #4-2). [0034] Diagrams 200C and 300C of Figs. 2 and 3 pertain to an example where S is at 8, L is at 14 and K is at 2, where “Rep #” designates a repetition number up to K repetitions, with occasional invalid symbols at random locations in the first through third slots. In the example of diagrams 200C and 300C, TCI assignments as between TCI 1 and TCI 2 toggle within a same PUSCH repetition until the end of L = 14 symbols that include the invalid symbols and switch to a next PUSCH repetition at that time regardless of slot boundaries, where the switch to the next PUSCH repletion continues with the next TCI toggle. Thus, in diagrams 200C and 300C, in a first slot, TCI 1 assigned to Rep #1-1 (which starts at symbol 9 after S = 8 symbols in the first slot) and stretches to the 2 invalid symbols ending at the slot boundary between the first and second slots. In the second slot, repetition #1 continues and we toggle to TCI 2 at Rep #1-2 until an invalid symbol, at which time we toggle back to TCI 1 at Rep #1-3 until Rep#l reaches L = 14 symbols. At that time, we toggle to TCI 2 assigned to Rep #2-1 until two invalid symbols, at which time we toggle back to TCI 1 at Rep #2-2 until Rep#2 reaches L = 14 symbols.

[0035] Dynamic switchins between no PUSCH repetition, 1-TRP PUSCH repetition and 2- TRP PUSCH repetition

[0036] PUSCH Uplink DCI may indicate any of the following:

• 2 sounding reference signal (SRS) resource indicators (SRIs) for non-codebook based (NCB) transmission corresponding to two TRPs (where the UE may assume max layer =1 when configured for repetition);

• 2 SRS resource sets of usage NCB associated with 2 channel state information reference signals (CSI-RS’) from TRP-1 and TRP-2, indication of 2 SRI in DCI one for each SRS resource set;

• If CSI-RS is not associated, then 2 SRI points to 2 SRS resources configured with spatial-relation-info (each corresponding to a TRP);

• 2 SRS resources or 2 TCI-states for codebook based (CB) transmission and 2 Transmitted Precoding Matrix Indicators (TPMIs);

• Codepoints may be introduced where each codepoint is mapped to a pair of SRIs or TCIs or 1 SRI/TCI. This allows dynamic switching between 2-TRP repetition, 1-TRP repetition and no repetition;

• Association between a codepoint and SRI/TCI can be indicated by RRC or MAC-CE.

[0037] Precoder cycling

[0038] Some embodiments include precoder cycling across repetitions for CB based transmission - a testable method for multi-Tx UE (1-2 layers). [0039] Some embodiments involve configuring the UE using higher layer signaling for precoder cycling using a TP MI sub-set with an ordered sequence of TMPIs, where TPMI may be re-interpreted to indicate a sub-set of TPMIs. According to this embodiment, a UE may derive rank from DCI from the indicated TMPI, and precoder cycling pattern and UE rank may be TRP agnostic or dependent on TRP.

[0040] According to some embodiments, SRI may be re-interpreted to indicate a sub-set of TPMIs (implicitly indicating rank).

[0041] DMRS for PUSCH with Repetition

[0042] For PUSCH transmission with both Type A and Type B repetition, the demodulation reference signal (DM-RS) sequence may be different for each PUSCH repetition, wherein the sequence generation should correspond to one of the two configured virtual cell identifiers (VCIDs) for each repetition. For cyclic prefix OFDM (CP-OFDM) based PUSCH

transmission, the DM-RS sequence may be a Gold Sequence which is initialized according to the following equation:

where and

are given by: if the higher-layer parameter in the IE is

provided

where A is the CDM group defined in clause 6.4.1.1.3. otherwise

[0043] For the case of PUSCH with repetition, the UE uses the n_SCID configured by the scheduling DCI in the first repetition. In each of the following repetitions, the UE sets as

e.g., the value of n_SCID alternates for each repetition and the DM-RS

sequence generation of the repetition corresponds to the VCID .

[0044] For the case of PUSCH with transform precoding enabled, the CGS or Zadoff Chu sequences use the sequence group mod 30, where is given by

[0045] Furthermore, if neither group, nor sequence hopping is enabled

if group hopping is enabled and sequence hopping is disabled

where the pseudo-random sequence

is defined by clause 5.2.1 and shall be initialized with

at the beginning of each radio frame if sequence hopping is enabled and group hopping is disabled

wh . ere t ,h. e pseud .o-rand .om sequence i.s d .efi,ned . b.y cl .ause 5 ,.2,.1, and . sh . al „l

be initialized with at the beginning of each radio frame.

[0046] Similar to the case for CP-OFDM based PUSCH with repetition, the UE uses the ⁿsciD configured by the scheduling DCI, and then sets

each successive repetition e.g., the value of n_SCID alternates in each repetition.

[0047] Multi-TRP PUCCH Repetition

[0048] Some embodiments enable multi-TRP repetition for both slot-wise and subslot-wise PUCCH repetition as shown by way of example in Figs. 5A and 5B, which will be described in further detail below.

[0049] PUCCH repetition in Rel.15 can be configured by the gNodeB using the number of slots parameter nrofSlots for PF1, PF3 and PF4, where “PF” refers to “PUCCH format” as shown by way of example in Fig. 4A. PUCCH repetition is optimized in Rel.16 for latency by allowing more than one PUCCH transmission (for hybrid automatic repeat requestacknowledgment (HARQ-ACK)) within a slot, using a subslot-based procedure as shown in Fig. 4B.

[0050] Figs. 4A and 4B illustrate radio transmissions 400A and 400B within 8 slots in the time and frequency domain, showing respective examples of HARQ-ACK feedback for multiple physical downlink shared channels (PDSCHs) 402 for Rel. 15 and Rel. 16, respectively. In this example, a PUCCH resource 404 for carrying HARQ-ACK feedback is determined by DCI in a PDCCH transmission. As shown in Fig. 4A, in Rel. 15 NR systems, only one HARQ-ACK feedback or PUCCH resource is transmitted in one slot, which is slot n + 7. As shown in Fig. 4B, in Rel. 16 NR systems, PUCCH repetition, for example as shown for HARQ-ACK feedback, may be accommodated within one slot, slot n+7, and therefore transmitted on sub-slot basis.

[0051 ] Referring in particular to Fig. 4B, an explicit indication in DCI may trigger multiple

HARQ-ACK feedbacks 404a and 404b in a slot, such as slot n+7. In the illustrated example, bit “0” in the DCI for scheduling PDSCH in slots n and n+2 is used to indicate that PDSCH in slots n and n+2 and corresponding HARQ-ACK feedback 404a belong to subset A. In addition, bit “1” in the DCI for scheduling PDSCH in slots n+1 and n+3 is used to indicate that PDSCH in slots n+1 and n+3 and corresponding HARQ-ACK feedbacks 404b belong to subset B. Thus, HARQ-ACK feedbacks in subset A and subset B are transmitted in different PUCCH resources 404a and 404b, which are time division multiplexed in a slot. In some aspects, PUCCH resource for subset A is determined in accordance with the DCI and corresponding PDCCH in slot n+2 while PUCCH resource for subset B is determined in accordance with the DCI and corresponding PDCCH in slot n+3.

[0052] Reference is now made to Figs. 5 A and 5B, which, similar to Figs. 4A and 4B, illustrate radio transmissions 500A and 500B within 8 slots in the time and frequency domain, showing respective examples of HARQ-ACK feedback for multiple PDSCH, where sets of PDSCH and their associated HARQ-ACK belonging to subset A are allocated to TCI 1, and where sets of PDSCH and their associated HARQ-ACK belonging to subset B are allocated to TCI 2.

[0053] Referring in particular to Fig. 5 A, according to one embodiment, an explicit indication in DCI may trigger multiple HARQ-ACK feedbacks 504a and 504b repeated at a slot level, such as slot n+7. In the illustrated example, bit “0” in the DCI for scheduling PDSCH in slots n and n+2 is used to indicate that PDSCH in slots n and n+2 and corresponding HARQ-ACK feedback 504a belong to subset A. In addition, bit “1” in the DCI for scheduling PDSCH in slots n+1 and n+3 is used to indicate that PDSCH in slots n+1 and n+3 and corresponding HARQ-ACK feedbacks 504b belong to subset B. In addition, PUCCH resources for HARQ-ACK feedback are repeated for both subsets A and B as between slot n+6 and slot n+7. Similar to Fig. 4B, HARQ-ACK feedbacks for subset A and subset B are transmitted in different PUCCH resources 504a and 504b. PUCCH resources 504a and 504b in slot n+6 correspond to TCI 1, and PUCCH 504a and 504b in slot n+7 correspond to TCI 2. In some aspects, PUCCH resource for subset A is determined in accordance with the DCI and corresponding PDCCH in slot n+2 while PUCCH resource for subset B is determined in accordance with the DCI and corresponding PDCCH in slot n+3.

[0054] Referring in particular to Fig. 5B, according to one embodiment, an explicit indication in DCI may trigger multiple HARQ-ACK feedbacks 504a and 504b repeated on a subslot level, such as subslots of slot n+7. In the illustrated example, bit “0” in the DCI for scheduling PDSCH in slots n and n+2 is used to indicate that PDSCH in slots n and n+2 and corresponding HARQ-ACK feedback 504a belong to subset A. In addition, bit “1” in the DCI for scheduling PDSCH in slots n+1 and n+3 is used to indicate that PDSCH in slots n+1 and n+3 and corresponding HARQ-ACK feedbacks 504b belong to subset B. In addition, PUCCH resources for HARQ-ACK feedback are repeated for both subsets A and B as between subslots of slot n+7. Similar to Fig. 4B, HARQ-ACK feedbacks for subset A and subset B are transmitted in different PUCCH resources 504a and 504b. PUCCH resources 504a and 504b in a first set of subslots of slot n+7 correspond to TCI 1, and PUCCH 504a and 504b in a second set of subslots of slot n+7 correspond to TCI 2. In some aspects, PUCCH resource for subset A is determined in accordance with the DCI and corresponding PDCCH in slot n+2 while PUCCH resource for subset B is determined in accordance with the DCI and corresponding PDCCH in slot n+3.

[0055] Dynamic control of PUCCH repetition

[0056] Currently PUCCH repetition is configured via RRC for each PUCCH format. Dynamic control of repetition factor and switching between 1-TRP repetition and 2-TRP repetitions is beneficial even when the same PUCCH format is used. Indeed, the network can use early termination to reduce latency. However, disadvantageous^, unnecessary repetition can cause interference, and RRC reconfiguration overhead can be quite high.

[0057] PU CCH resource ID associated with 2 PU CCH-SpatialRelationlnfoI d using MA C-

CE

[0058] A medium access control (MAC) control element (CE) (MAC-CE) may be used according to one embodiment to associate 2 PUCCH-SpatialRelationlnfoId to a PUCCH resource ID or a group of PUCCH resource IDs.

• Dynamic indication of the number of repetition can be achieved by configuring a PUCCH resource ID with an associated repetition number. The repetition number (or repetition#) may also be associated with PDSCH time domain resource assignment (TDRA).

• The association of PUCCH with one or multiple TCI-state-ID may be indicated by DCI. As an example, the PRI (PUCCH resource ID) field in DCI can be re-interpreted as codepoints for selection between one or multiple TCI-state-IDs. The order of TCI states to be used for PUCCH repetition is also indicated by the choice of codepoints indicated in the DCI. As an example repetition could be ordered as {TCI-1, TCI-2, TCI-1, TCI- 2...} or {TCI-1, TCI-1, TCI-2, TCI-2...}. In the same way, instead of TCI-state-ID, PUCCH-SpatialRelationlnfoId can be used and can be indicated by the PRI in DCI.

• The DM-RS sequence generation for PUCCH transmission is associated with each PUCCH TCI-state-ID or PUCCH-SpatialRelationlnfoId. The DM-RS sequence

is generated such that the values of u, v are generated based on one of two configured . The selection of the

is based on the order of the TCI-State-IDs

or the PUCCH-SpatialRelationlnfoId, wherein the is associated with the first TCI- State-ID or PUCCH-spatialRelationlnfoId and is associated with the second TCI-

State-ID or PUCCH-spatialRelationlnfoId. Based on this association the sequence group u and sequence number v may be determined according to some embodiments as follows: o The sequence group u =

mod 30 and the sequence number v within the group depends on the higher-layer parameter pucch-GroupHopping.

■ if pucch-GroupHopping equals 'neither'

where

is given depending on the order of TCI-state-ID or PUCCH-

SpatialRelationlnfoId, otherwise

■ if pucch-GroupHopping equals 'enable'

where the pseudo-random sequence

is defined by clause 5.2.1 and shall be initialized at the beginning of each radio frame with where

depending on the order of TCI-state-ID or PUCCH- SpatialRelationlnfoId, otherwise .

If pucch-GroupHopping equals 'disable'

where the pseudo-random sequence is defined by clause 5.2.1 and shall be initialized at the beginning of each radio frame with where

j_s gi_ven depending on the order of TCI-state-ID or PUCCH-

SpatialRelationlnfoId, otherwise

[0059] Figs. 6A and 6B show respective radio transmissions 600A and 600B each with PUCCH repetition for TCI 1 and TCI 2 within a same PUCCH resource instance for a PUCCH format 1 (Fig. 6A) without and with frequency hopping (Fig. 6B) respectively. Fig. 6A shows a PUCCH format 1 with 7 symbols without frequency hopping, where DM-RS and uplink control information (UCI) are encoded for transmission in a same frequency band. Fig. 6B shows a PUCCH format 1 with 7 symbols with frequency hopping, where DM-RS and UCI for TCI 1 are transmitted at a first frequency, and where DM-RS and UCI for TCI 2 are transmitted at a second frequency different from the first frequency.

[0060] Figs. 7A and 7B show respective radio transmissions 700A and 700B each with PUCCH repetition for TCI 1 and TCI 2 within a same PUCCH resource instance for a PUCCH format 1 (Fig. 7A) without and with frequency hopping (Fig. 7B) respectively. Fig. 7A shows a PUCCH format 3/4 with 9 or 11 symbols with frequency hopping, where DM-RS and UCI for TCI 1 are transmitted at a first frequency, and where DM-RS and UCI for TCI 2 are transmitted at a second frequency different from the first frequency. Fig. 7B shows a PUCCH format 1 with 9 or 11 symbols without frequency hopping, where DM-RS and uplink control information (UCI) are encoded for transmission in a same frequency band.

[0061] Fig. 11 shows a process 1100 according to an embodiment. At operation 1102, the process includes encoding, at an apparatus of a New Radio (NR) Node B (gNodeB), a message to indicate physical uplink shared channel (PUSCH) repetitions associated with two different TCI states, TCI 1 and TCI 2, respectively. At operation 1104, the process includes sending the message to communication resources of the gNodeB for the communication resources to cause a transmission of the message to the UE.

[0062] Fig. 12 shows a process 1200 according to an embodiment. At operation 1202, the process includes decoding, at an apparatus of a New Radio User Equipment (UE) a message from a NR Node B (gNodeB) to indicate physical uplink shared channel (PUSCH) repetitions associated with two different TCI states, TCI 1 and TCI 2, respectively. At operation 1204, the process includes encoding, for transmission to the gNodeB, PUSCH repetitions based on the message.

[0063] Systems And Implementations

[0064] Figs. 8-10 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

[0065] Fig. 8 illustrates a network 800 in accordance with various embodiments. The network 800 may operate in a manner consistent with 3 GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.

[0066] The network 800 may include a UE 802, which may include any mobile or non- mobile computing device designed to communicate with a RAN 804 via an over-the-air connection. The UE 802 may be communicatively coupled with the RAN 804 by a Uu interface. The UE 802 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electron! c/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

[0067] In some embodiments, the network 800 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0068] In some embodiments, the UE 802 may additionally communicate with an AP 806 via an over-the-air connection. The AP 806 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 804. The connection between the UE 802 and the AP 806 may be consistent with any IEEE 802.11 protocol, wherein the AP 806 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 802, RAN 804, and AP 806 may utilize cellular- WLAN aggregation (for example, LWA/LWIP). Cellular- WLAN aggregation may involve the UE 802 being configured by the RAN 804 to utilize both cellular radio resources and WLAN resources.

[0069] The RAN 804 may include one or more access nodes, for example, AN 808. AN 808 may terminate air-interface protocols for the UE 802 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 808 may enable data/voice connectivity between CN 820 and the UE 802. In some embodiments, the AN 808 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 808 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 808 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0070] In embodiments in which the RAN 804 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 804 is an LTE RAN) or an Xn interface (if the RAN 804 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

[0071] The ANs of the RAN 804 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 802 with an air interface for network access. The UE 802 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 804. For example, the UE 802 and RAN 804 may use carrier aggregation to allow the UE 802 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.

[0072] The RAN 804 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

[0073] In V2X scenarios the UE 802 or AN 808 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

[0074] In some embodiments, the RAN 804 may be an LTE RAN 810 with eNBs, for example, eNB 812. The LTE RAN 810 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands.

[0075] In some embodiments, the RAN 804 may be an NG-RAN 814 with gNBs, for example, gNB 816, or ng-eNBs, for example, ng-eNB 818. The gNB 816 may connect with 5G- enabled UEs using a 5GNR interface. The gNB 816 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 818 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 816 and the ng-eNB 818 may connect with each other over an Xn interface. [0076] In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 814 and a UPF 848 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN814 and an AMF 844 (e.g., N2 interface).

[0077] The NG-RAN 814 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G- NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.

[0078] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 802 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 802, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 802 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 802 and in some cases at the gNB 816. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

[0079] The RAN 804 is communicatively coupled to CN 820 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 802). The components of the CN 820 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 820 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 820 may be referred to as a network slice, and a logical instantiation of a portion of the CN 820 may be referred to as a network sub-slice.

[0080] In some embodiments, the CN 820 may be an LTE CN 822, which may also be referred to as an EPC. The LTE CN 822 may include MME 824, SGW 826, SGSN 828, HSS 830, PGW 832, and PCRF 834 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 822 may be briefly introduced as follows. [0081] The MME 824 may implement mobility management functions to track a current location of the UE 802 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

[0082] The SGW 826 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 822. The SGW 826 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0083] The SGSN 828 may track a location of the UE 802 and perform security functions and access control. In addition, the SGSN 828 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 824; MME selection for handovers; etc. The S3 reference point between the MME 824 and the SGSN 828 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/ active states.

[0084] The HSS 830 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 830 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 830 and the MME 824 may enable transfer of subscription and authentication data for authenticating/ authorizing user access to the LTE CN 820.

[0085 [ The PGW 832 may terminate an SGi interface toward a data network (DN) 836 that may include an application/content server 838. The PGW 832 may route data packets between the LTE CN 822 and the data network 836. The PGW 832 may be coupled with the SGW 826 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 832 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 832 and the data network YX 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 832 may be coupled with a PCRF 834 via a Gx reference point.

[0086] The PCRF 834 is the policy and charging control element of the LTE CN 822. The PCRF 834 may be communicatively coupled to the app/content server 838 to determine appropriate QoS and charging parameters for service flows. The PCRF 832 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

[0087] In some embodiments, the CN 820 may be a 5GC 840. The 5GC 840 may include an AUSF 842, AMF 844, SMF 846, UPF 848, NSSF 850, NEF 852, NRF 854, PCF 856, UDM 858, and AF 860 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 840 may be briefly introduced as follows.

[0088] The AUSF 842 may store data for authentication of UE 802 and handle authentication-related functionality. The AUSF 842 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 840 over reference points as shown, the AUSF 842 may exhibit an Nausf service-based interface.

[0089] The AMF 844 may allow other functions of the 5GC 840 to communicate with the UE 802 and the RAN 804 and to subscribe to notifications about mobility events with respect to the UE 802. The AMF 844 may be responsible for registration management (for example, for registering UE 802), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 844 may provide transport for SM messages between the UE 802 and the SMF 846, and act as a transparent proxy for routing SM messages. AMF 844 may also provide transport for SMS messages between UE 802 and an SMSF. AMF 844 may interact with the AUSF 842 and the UE 802 to perform various security anchor and context management functions. Furthermore, AMF 844 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 804 and the AMF 844; and the AMF 844 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 844 may also support NAS signaling with the UE 802 over an N3 IWF interface.

[0090] The SMF 846 may be responsible for SM (for example, session establishment, tunnel management between UPF 848 and AN 808); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 848 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 844 over N2 to AN 808; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 802 and the data network 836.

[0091] The UPF 848 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 836, and a branching point to support multi-homed PDU session. The UPF 848 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 848 may include an uplink classifier to support routing traffic flows to a data network. [0092] The NSSF 850 may select a set of network slice instances serving the UE 802. The NSSF 850 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 850 may also determine the AMF set to be used to serve the UE 802, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 854. The selection of a set of network slice instances for the UE 802 may be triggered by the AMF 844 with which the UE 802 is registered by interacting with the NSSF 850, which may lead to a change of AMF. The NSSF 850 may interact with the AMF 844 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 850 may exhibit an Nnssf service-based interface.

[0093] The NEF 852 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 860), edge computing or fog computing systems, etc. In such embodiments, the NEF 852 may authenticate, authorize, or throttle the AFs. NEF 852 may also translate information exchanged with the AF 860 and information exchanged with internal network functions. For example, the NEF 852 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 852 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 852 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 852 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 852 may exhibit an Nnef service-based interface.

[0094] The NRF 854 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 854 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 854 may exhibit the Nnrf service-based interface.

[0095] The PCF 856 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 856 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 858. In addition to communicating with functions over reference points as shown, the PCF 856 exhibit an Npcf service-based interface.

[0096] The UDM 858 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 802. For example, subscription data may be communicated via an N8 reference point between the UDM 858 and the AMF 844. The UDM 858 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 858 and the PCF 856, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 802) for the NEF 852. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 858, PCF 856, and NEF 852 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 858 may exhibit the Nudm servicebased interface.

[0097] The AF 860 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

[0098] In some embodiments, the 5GC 840 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 802 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 840 may select a UPF 848 close to the UE 802 and execute traffic steering from the UPF 848 to data network 836 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 860. In this way, the AF 860 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 860 is considered to be a trusted entity, the network operator may permit AF 860 to interact directly with relevant NFs. Additionally, the AF 860 may exhibit an Naf service-based interface. [0099] The data network 836 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 838.

[0100] Fig. 9 schematically illustrates a wireless network 900 in accordance with various embodiments. The wireless network 900 may include a UE 902 in wireless communication with an AN 904. The UE 902 and AN 904 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

[0101] The UE 902 may be communicatively coupled with the AN 904 via connection 906. The connection 906 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5GNR protocol operating at mmWave or sub-6GHz frequencies.

[0102] The UE 902 may include a host platform 908 coupled with a modem platform 910. The host platform 908 may include application processing circuitry 912, which may be coupled with protocol processing circuitry 914 of the modem platform 910. The application processing circuitry 912 may run various applications for the UE 902 that source/sink application data. The application processing circuitry 912 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

[0103] The protocol processing circuitry 914 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 906. The layer operations implemented by the protocol processing circuitry 914 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

[0104] The modem platform 910 may further include digital baseband circuitry 916 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 914 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

[0105] The modem platform 910 may further include transmit circuitry 918, receive circuitry 920, RF circuitry 922, and RF front end (RFFE) 924, which may include or connect to one or more antenna panels 926. Briefly, the transmit circuitry 918 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 920 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 922 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 924 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 918, receive circuitry 920, RF circuitry 922, RFFE 924, and antenna panels 926 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

[0106] In some embodiments, the protocol processing circuitry 914 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

[0107] A UE reception may be established by and via the antenna panels 926, RFFE 924, RF circuitry 922, receive circuitry 920, digital baseband circuitry 916, and protocol processing circuitry 914. In some embodiments, the antenna panels 926 may receive a transmission from the AN 904 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 926.

[0108] A UE transmission may be established by and via the protocol processing circuitry 914, digital baseband circuitry 916, transmit circuitry 918, RF circuitry 922, RFFE 924, and antenna panels 926. In some embodiments, the transmit components of the UE 904 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 926.

[0109] Similar to the UE 902, the AN 904 may include a host platform 928 coupled with a modem platform 930. The host platform 928 may include application processing circuitry 932 coupled with protocol processing circuitry 934 of the modem platform 930. The modem platform may further include digital baseband circuitry 936, transmit circuitry 938, receive circuitry 940, RF circuitry 942, RFFE circuitry 944, and antenna panels 946. The components of the AN 904 may be similar to and substantially interchangeable with like-named components of the UE 902. In addition to performing data transmission/reception as described above, the components of the AN 908 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0110] Fig. 10 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Fig. 10 shows a diagrammatic representation of hardware resources 1000 including one or more processors (or processor cores) 1010, one or more memory /storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1002 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1000.

[0111] The processors 1010 may include, for example, a processor 1012 and a processor 1014. The processors 1010 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0112] The memory/storage devices 1020 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1020 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as 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 storage, etc.

[0113] The communication resources 1030 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 or other network elements via a network 1008. For example, the communication resources 1030 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

[0114] Instructions 1050 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1010 to perform any one or more of the methodologies discussed herein. The instructions 1050 may reside, completely or partially, within at least one of the processors 1010 (e.g., within the processor’s cache memory), the memory/storage devices 1020, or any suitable combination thereof. Furthermore, any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral devices 1004 or the databases 1006. Accordingly, the memory of processors 1010, the memory/storage devices 1020, the peripheral devices 1004, and the databases 1006 are examples of computer-readable and machine-readable media.

[0115] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

[0116] Examples:

[0117] Example 1 includes an apparatus of a New Radio (NR) Node B (gNodeB), the apparatus including a memory, and one or more processors coupled to the memory, the memory storing instructions, and the one or more processors to implement the instructions to: encode a message to indicate physical uplink shared channel (PUSCH) repetitions associated with two different TCI states, TCI 1 and TCI 2, respectively; and send the message to communication resources of the gNodeB for the communication resources to cause a transmission of the message to the UE.

[0118] Example 2 includes the apparatus of Example 1, wherein the one or more processors are to map TCI 1 and TCI 2 to the PUSCH repetitions before segmentation or after segmentation.

[0119] Example 3 includes the apparatus of any one of Examples 1-2, wherein the message includes a downlink control information (DCI) to indicate a mapping of the PUSCH repetitions to respective configured precoders.

[0120] Example 4 includes the apparatus of Example 3, wherein the DCI is to indicate two sounding reference signal (SRS) resource indicators (SRIs) for non-codebook based (NCB) transmission corresponding to TCI 1 and TCI 2, respectively.

[0121] Example 5 includes the apparatus of Example 1, wherein the message is a first message and the transmission is a first transmissions, the one or more processors to further: encode a second message to indicate physical uplink shared channel (PUCCH) repetitions, the repetitions being associated with two different TCI states, TCI 1 and TCI 2, respectively, the repetitions further including slot-wise repetitions or subslot-wise repetitions; and send the second message to communication resources of the gNodeB for the communication resources to cause a second transmission of the second message to the UE.

[0122] Example 6 includes the apparatus of Example 5, wherein the second message is to indicate that a single instance of a PUCCH resource identification (PUCCH resource ID) is to be transmitted with TCI 1 in a first portion of the second transmission, and with TCI 2 in a second portion of the second transmission.

[0123] Example 7 includes the apparatus of Example 5, wherein a number of the PUCCH repetitions is associated with a PUCCH resource ID.

[0124] Example 8 includes the apparatus of Example 5, wherein a number of the PUCCH repetitions is associated with a physical downlink shared channel (PDSCH) time domain resource assignment (TDRA).

[0125] Example 9 includes the apparatus of Example 5, the one or more processors to further generate a demodulation reference signal (DM-RS) sequence for PUCCH transmission for each of TCI 1 and TCI 2, the DM-RS sequence associated with a corresponding one of a TCI-state-ID or a PUCCH-SpatialRelationlnfoId corresponding to said each of TCI 1 and TCI 2.

[0126] Example 10 includes the apparatus of any one of Examples 5-9, wherein the second message includes a medium access control control element (MAC-CE) message or a radio resource control (RRC) message.

[0127] Example 11 includes the apparatus of any one of Examples 1-2 and 5-9, further including the communication resources coupled to the one or more processors.

[0128] Example 12 includes the apparatus of Example 11, further including one or more antennas coupled to the communication resources.

[0129] Example 13 includes a method to be performed at an apparatus of a New Radio (NR) Node B (gNodeB), the method including: encoding a message to indicate physical uplink shared channel (PUSCH) repetitions associated with two different TCI states, TCI 1 and TCI 2, respectively; and sending the message to communication resources of the gNodeB for the communication resources to cause a transmission of the message to the UE.

[0130] Example 14 includes the method of Example 13, further including mapping TCI 1 and TCI 2 to the PUSCH repetitions before segmentation or after segmentation.

[0131] Example 15 includes the method of any one of Examples 13-14, wherein the message includes a downlink control information to indicate a mapping of the PUSCH repetitions to respective configured precoders.

[0132] Example 16 includes the method of Example 13, wherein the message is a first message and the transmission is a first transmissions, the method further including: encoding a second message to indicate physical uplink shared channel (PUCCH) repetitions, the repetitions being associated with two different TCI states, TCI 1 and TCI 2, respectively, the repetitions further including slot-wise repetitions or subslot-wise repetitions; and sending the second message to communication resources of the gNodeB for the communication resources to cause a second transmission of the second message to the UE.

[0133] Example 17 includes the method of Example 16, wherein the second message is to indicate that a single instance of a PUCCH resource identification (PUCCH resource ID) is to be transmitted with TCI 1 in a first portion of the second transmission, and with TCI 2 in a second portion of the second transmission.

[0134] Example 18 includes the method of Example 16, wherein a number of the PUCCH repetitions is associated with a PUCCH resource ID.

[0135] Example 19 includes the method of Example 16, wherein a number of the PUCCH repetitions is associated with a physical downlink shared channel (PDSCH) time domain resource assignment (TDRA).

[0136] Example 20 includes the method of Example 13, further including generating a demodulation reference signal (DM-RS) sequence for PUCCH transmission for each of TCI 1 and TCI 2, the DM-RS sequence associated with a corresponding one of a TCI-state-ID or a PUCCH-SpatialRelationlnfoId corresponding to said each of TCI 1 and TCI 2.

[0137] Example 21 includes the method of any one of Examples 16-20, wherein the second message includes a medium access control control element (MAC-CE) message or a radio resource control (RRC) message.

[0138] Example 22 includes the method of Example 13, further including causing to transmit the message to the UE through a communication resources of the gNodeB.

[0139] Example 23 includes the method of Example 22, further including transmitting the message to the UE through one or more antennas coupled to the communication resources. [0140] Example 24 includes an apparatus of a New Radio User Equipment (UE), the apparatus including a memory, and one or more processors coupled to the memory, the memory storing instructions, and the one or more processors to implement the instructions to: decode a message from a NR Node B (gNodeB) to indicate physical uplink shared channel (PUSCH)

repetitions associated with two different TCI states, TCI 1 and TCI 2, respectively; and encode, for transmission to the gNodeB, PUSCH repetitions based on the message.

[0141] Example 25 includes the apparatus of Example 24, wherein TCI 1 and TCI 2 are mapped to the PUSCH repetitions before segmentation or after segmentation.

[0142] Example 26 includes the apparatus of any one of Examples 24-25, wherein the message includes a downlink control information (DCI) to indicate a mapping of the PUSCH repetitions to respective configured precoders.

[0143] Example 27 includes the apparatus of Example 26, wherein the DCI is to indicate two sounding reference signal (SRS) resource indicators (SRIs) for non-codebook based (NCB) transmission corresponding to TCI 1 and TCI 2, respectively.

[0144] Example 28 includes the apparatus of Example 24, wherein the message is a first message and the transmission is a first transmissions, the one or more processors to further: decode a second message to indicate physical uplink shared channel (PUCCH) repetitions, the repetitions being associated with two different TCI states, TCI 1 and TCI 2, respectively, the repetitions further including slot-wise repetitions or subslot-wise repetitions; and encode for transmission to the gNodeB PUCCH repetitions based on the second message.

[0145] Example 29 includes the apparatus of Example 28, wherein the second message is to indicate that a single instance of a PUCCH resource identification (PUCCH resource ID) is to be transmitted with TCI 1 in a first portion of the second transmission, and with TCI 2 in a second portion of the second transmission.

[0146] Example 30 includes the apparatus of Example 28, wherein a number of the PUCCH repetitions is associated with a PUCCH resource ID.

[0147] Example 31 includes the apparatus of Example 28, wherein a number of the PUCCH repetitions is associated with a physical downlink shared channel (PDSCH) time domain resource assignment (TDRA).

[0148] Example 32 includes the apparatus of Example 28, the one or more processors to further decode a demodulation reference signal (DM-RS) sequence for PUCCH transmission for each of TCI 1 and TCI 2, the DM-RS sequence associated with a corresponding one of a TCI- state-ID or a PUCCH-SpatialRelationlnfoId corresponding to said each of TCI 1 and TCI 2.

[0149] Example 33 includes the apparatus of any one of Examples 28-32, wherein the second message includes a medium access control control element (MAC-CE) message or a radio resource control (RRC) message.

[0150] Example 34 includes the apparatus of any one of Examples 24-25 and 28-32, further including communication resources coupled to the one or more processors.

[0151] Example 35 includes the apparatus of Example 34, further including one or more antennas coupled to the communication resources.

[0152] Example 36 includes method to be performed at an apparatus of a New Radio User Equipment (UE), the method including: decoding a message from a NR Node B (gNodeB) to indicate physical uplink shared channel (PUSCH) repetitions associated with two different TCI states, TCI 1 and TCI 2, respectively; and encoding, for transmission to the gNodeB, PUSCH repetitions based on the message.

[0153] Example 37 includes the method of Example 36, wherein TCI 1 and TCI 2 are mapped to the PUSCH repetitions before segmentation or after segmentation.

[0154] Example 38 includes the method of any one of Examples 36-37, wherein the message includes a downlink control information (DCI) to indicate a mapping of the PUSCH repetitions to respective configured precoders.

[0155] Example 39 includes the method of Example 38, wherein the DCI is to indicate two sounding reference signal (SRS) resource indicators (SRIs) for non-codebook based (NCB) transmission corresponding to TCI 1 and TCI 2, respectively.

[0156] Example 40 includes the method of Example 36, wherein the message is a first message and the transmission is a first transmissions, the method further including: decoding a second message to indicate physical uplink shared channel (PUCCH) repetitions, the repetitions being associated with two different TCI states, TCI 1 and TCI 2, respectively, the repetitions further including slot-wise repetitions or subslot-wise repetitions; and encoding for transmission to the gNodeB PUCCH repetitions based on the second message.

[0157] Example 41 includes the method of Example 40, wherein the second message is to indicate that a single instance of a PUCCH resource identification (PUCCH resource ID) is to be transmitted with TCI 1 in a first portion of the second transmission, and with TCI 2 in a second portion of the second transmission.

[0158] Example 42 includes the method of Example 40, wherein a number of the PUCCH repetitions is associated with a PUCCH resource ID.

[0159] Example 43 includes the method of Example 40, wherein a number of the PUCCH repetitions is associated with a physical downlink shared channel (PDSCH) time domain resource assignment (TDRA).

[0160] Example 44 includes the method of Example 40, the method further including decoding a demodulation reference signal (DM-RS) sequence for PUCCH transmission for each of TCI 1 and TCI 2, the DM-RS sequence associated with a corresponding one of a TCI-state-ID or a PUCCH-SpatialRelationlnfoId corresponding to said each of TCI 1 and TCI 2.

[0161] Example 45 includes the method of any one of Examples 40-44, wherein the second message includes a medium access control control element (MAC-CE) message or a radio resource control (RRC) message..

[0162] Example 46 includes a machine readable medium including code, when executed, to cause a machine to perform the method of any one of claims 12-23 and 36-45.

[0163] Example 47 includes an apparatus including means to perform the method of any one of claims 12-23 and 36-45.

[0164] Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 12-23 and 26-45, or any other method or process described herein.

[0165] Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 12-23 and 26-45, or any other method or process described herein.

[0166] Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 12-23 and 26-45, or any other method or process described herein.

[0167] Example Z04 may include a method, technique, or process as described in or related to any of the examples above, or portions or parts thereof.

[0168] Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of the example above, or portions thereof.

[0169] Example Z06 may include a signal as described in or related to any of examples 1-8, or portions or parts thereof.

[0170] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-8, or portions or parts thereof, or otherwise described in the present disclosure.

[0171] Example Z08 may include a signal encoded with data as described in or related to any of examples 1-8, or portions or parts thereof, or otherwise described in the present disclosure.

[0172] Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-8, or portions or parts thereof, or otherwise described in the present disclosure.

[0173] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-8, or portions thereof.

[0174] Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-8, or portions thereof.

[0175] Example Z12 may include a signal in a wireless network as shown and described herein.

[0176] Example Z13 may include a method of communicating in a wireless network as shown and described herein.

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

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

[0179] Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0180] Any of the above-described Examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. Aspects described herein can also implement a hierarchical application of the scheme for example, by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g. with highest priority to tier-1 users, followed by tier- 2, then tier-3, etc. users, etc. Some of the features in the present disclosure are defined for network elements (or network equipment) such as Access Points (APs), eNBs, gNBs, core network elements (or network functions), application servers, application functions, etc. Any embodiment discussed herein as being performed by a network element may additionally or alternatively be performed by a UE, or the UE may take the role of the network element (e.g., some or all features defined for network equipment may be implemented by a UE).

[0181] Although these implementations have been described with reference to specific exemplary aspects, it will be evident that various modifications and changes may be made to these aspects without departing from the broader scope of the present disclosure. Many of the arrangements and processes described herein can be used in combination or in parallel implementations to provide greater bandwidth/throughput and to support edge services selections that can be made available to the edge systems being serviced. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific aspects in which the subject matter may be practiced. The aspects illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other aspects may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various aspects is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[0182] Such aspects of the inventive subject matter may be referred to herein, individually and/or collectively, merely for convenience and without intending to voluntarily limit the scope of this application to any single aspect or inventive concept if more than one is in fact disclosed. Thus, although specific aspects have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific aspects shown. This disclosure is intended to cover any and all adaptations or variations of various aspects. Combinations of the above aspects and other aspects not specifically described herein will be apparent to those of skill in the art upon reviewing the above description.

Claims

What is claimed is:

1. An apparatus of a New Radio (NR) Node B (gNodeB), the apparatus including a memory, and one or more processors coupled to the memory, the memory storing instructions, and the one or more processors to implement the instructions to: encode a message to indicate physical uplink shared channel (PUSCH) repetitions associated with two different TCI states, TCI 1 and TCI 2, respectively; and send the message to communication resources of the gNodeB for the communication resources to cause a transmission of the message to the UE.

2. The apparatus of claim 1, wherein the one or more processors are to map TCI 1 and TCI 2 to the PUSCH repetitions before segmentation or after segmentation.

3. The apparatus of any one of claims 1-2, wherein the message includes a downlink control information (DCI) to indicate a mapping of the PUSCH repetitions to respective configured precoders.

4. The apparatus of claim 3, wherein the DCI is to indicate two sounding reference signal (SRS) resource indicators (SRIs) for non-codebook based (NCB) transmission corresponding to TCI 1 and TCI 2, respectively.

5. The apparatus of claim 1, wherein the message is a first message and the transmission is a first transmissions, the one or more processors to further: encode a second message to indicate physical uplink shared channel (PUCCH) repetitions, the repetitions being associated with two different TCI states, TCI 1 and TCI 2, respectively, the repetitions further including slot-wise repetitions or subslot-wise repetitions; and send the second message to communication resources of the gNodeB for the communication resources to cause a second transmission of the second message to the UE.

6. The apparatus of claim 5, wherein the second message is to indicate that a single instance of a PUCCH resource identification (PUCCH resource ID) is to be transmitted with TCI 1 in a

34 first portion of the second transmission, and with TCI 2 in a second portion of the second transmission.

7. The apparatus of claim 5, wherein a number of the PUCCH repetitions is associated with a PUCCH resource ID.

8. The apparatus of claim 5, wherein a number of the PUCCH repetitions is associated with a physical downlink shared channel (PDSCH) time domain resource assignment (TDRA).

9. The apparatus of claim 5, the one or more processors to further generate a demodulation reference signal (DM-RS) sequence for PUCCH transmission for each of TCI 1 and TCI 2, the DM-RS sequence associated with a corresponding one of a TCI-state-ID or a PUCCH- SpatialRelationlnfoId corresponding to said each of TCI 1 and TCI 2.

10. The apparatus of any one of claims 5-9, wherein the second message includes a medium access control control element (MAC-CE) message or a radio resource control (RRC) message.

11. The apparatus of any one of claims 1-2 and 5-9, further including the communication resources coupled to the one or more processors.

12. The apparatus of claim 11, further including one or more antennas coupled to the communication resources.

13. A method to be performed at an apparatus of a New Radio (NR) Node B (gNodeB), the method including: encoding a message to indicate physical uplink shared channel (PUSCH) repetitions associated with two different TCI states, TCI 1 and TCI 2, respectively; and sending the message to communication resources of the gNodeB for the communication resources to cause a transmission of the message to the UE.

14. The method of claim 13, further including mapping TCI 1 and TCI 2 to the PUSCH repetitions before segmentation or after segmentation.

35

15. The method of any one of claims 13-14, wherein the message includes a downlink control information to indicate a mapping of the PUSCH repetitions to respective configured precoders.

16. The method of claim 13, wherein the message is a first message and the transmission is a first transmissions, the method further including: encoding a second message to indicate physical uplink shared channel (PUCCH) repetitions, the repetitions being associated with two different TCI states, TCI 1 and TCI 2, respectively, the repetitions further including slot-wise repetitions or subslot-wise repetitions; and sending the second message to communication resources of the gNodeB for the communication resources to cause a second transmission of the second message to the UE.

17. The method of claim 16, wherein the second message is to indicate that a single instance of a PUCCH resource identification (PUCCH resource ID) is to be transmitted with TCI 1 in a first portion of the second transmission, and with TCI 2 in a second portion of the second transmission.

18. The method of claim 16, wherein a number of the PUCCH repetitions is associated with a PUCCH resource ID.

19. The method of claim 16, wherein a number of the PUCCH repetitions is associated with a physical downlink shared channel (PDSCH) time domain resource assignment (TDRA).

20. The method of claim 13, further including generating a demodulation reference signal (DM-RS) sequence for PUCCH transmission for each of TCI 1 and TCI 2, the DM-RS sequence associated with a corresponding one of a TCI-state-ID or a PUCCH-SpatialRelationlnfoId corresponding to said each of TCI 1 and TCI 2.

21. The method of any one of claims 16-20, wherein the second message includes a medium access control control element (MAC-CE) message or a radio resource control (RRC) message.

22. The method of claim 13, further including causing to transmit the message to the UE through a communication resources of the gNodeB.

23. The method of claim 22, further including transmitting the message to the UE through one or more antennas coupled to the communication resources.

24. A machine readable medium including code, when executed, to cause a machine to perform the method of any one of claims 12-23.

25. An apparatus including means to perform the method of any one of claims 12-23.