Sounding reference signal (SRS) configuration in subband full duplex (SBFD)

Abstract

A method performed by a user equipment, UE (112), includes: receiving information indicating a configuration of a pair of sounding reference signal, SRS, resource sets, the pair including a first SRS resource set and a second SRS resource set, the first SRS resource set including one or more SRS resources associated with a symbol type corresponding to SBFD symbols and the second SRS resource set including one or more SRS resources associated with a symbol type corresponding to non-SBFD symbols; receiving information for a physical uplink shared channel, PUSCH, transmission; selecting a selected SRS resource based on a symbol type associated with the symbols for the PUSCH transmission; and transmitting the PUSCH transmission according to the selected SRS resource.

Description

SOUNDING REFERENCE SIGNAL (SRS) CONFIGURATION IN SUBBAND FULL DUPLEX (SBFD)BACKGROUND

[0001] The Third Generation Partnership Project (3GPP) is designing the New Radio (NR) standard to provide service for multiple use cases, such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), and machine type communication (MTC). Each of these services has different technical requirements. For example, the general requirement for eMBB is high data rate with moderate latency and moderate coverage, while URLLC service requires a low latency and high reliability transmission but perhaps for moderate data rates.

[0002] One of the solutions for low latency data transmission is shorter transmission time intervals (TTIs). In NR, in addition to transmission in a slot, a mini-slot transmission is also allowed to reduce latency. A mini-slot may consist of any number of 1 to 14 orthogonal frequency-division multiplexing (OFDM) symbols. It should be noted that the concepts of slot and mini-slot are not specific to a specific service, meaning that a minislot may be used for either eMBB or URLLC (or for other services).

[0003] Figure 1 illustrates an example radio resource in NR. In Release 15 (Rel-15) NR, a user equipment (UE) can be configured with up to four carrier bandwidth parts in the downlink (DL) with a single downlink carrier bandwidth part being active at a given time. A UE can be configured with up to four carrier bandwidth parts in the uplink (UL) with a single uplink carrier bandwidth part being active at a given time.

[0004] An NR slot consists of several OFDM symbols, according to current agreements either 7 or 14 symbols (OFDM subcarrier spacing < 60 kHz) and 14 symbols (OFDM subcarrier spacing > 60 kHz). Figure 2 illustrates an example NR slot where a subframe has 14 OFDM symbols. In Figure 2, Tsdenotes the slot duration and Tsymbdenotes the OFDM symbol duration.FDD and TDD systems

[0005] Figure 3 illustrates examples of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). Transmission and reception from a node (e.g., a terminal in a cellular system) can be multiplexed in the frequency domain or in the time domain (or combinations thereof). FDD, as illustrated to the left in Figure 3, implies that downlink and uplink transmission take place in different, sufficiently separated, frequency bands. TDD, as illustrated to the right in Figure 3, implies that downlink and uplink transmissiontake place in different, non-overlapping time slots. Thus, TDD can operate in unpaired spectrum, whereas FDD requires paired spectrum.

[0006] Typically, the structure of the transmitted signal in a communication system is organized in the form of a frame structure. For example, NR uses ten equally sized slots per radio frame as illustrated in Figure 4 for the case of 15 kHz subcarrier spacing.

[0007] Figure 4 illustrates an example of uplink / downlink time / frequency structure in the case of FDD or TDD operation. In the case of FDD operation (upper part of Figure 4), there are two carrier frequencies, one for uplink transmission (fUL) and one for downlink transmission (fDL). At least with respect to the terminal in a cellular communication system, FDD can be either full duplex or half duplex. In the full duplex case, a terminal can transmit and receive simultaneously, while in half-duplex operation, the terminal cannot transmit and receive simultaneously (the base station is capable of simultaneous reception / transmission though, e.g., receiving from one terminal while simultaneously transmitting to another terminal). In Long Term Evolution (LTE), a half-duplex terminal monitors / receives in the downlink except when explicitly instructed to transmit in a certain subframe.

[0008] In the case of TDD operation (lower part of Figure 4), there is only a single carrier frequency and uplink and downlink transmissions are always separated in time also on a cell basis. As the same carrier frequency is used for uplink and downlink transmission, both the base station and the mobile terminals need to switch from transmission to reception and vice versa. An essential aspect of any TDD system is to provide the possibility for a sufficiently large guard time where neither downlink nor uplink transmissions occur. This is required to avoid interference between uplink and downlink transmissions. For NR, this guard time is provided by special subframes, which are split into three parts: symbols for DL, a guard period (GP), and symbols for uplink. The remaining subframes are either allocated to uplink or downlink transmission.

[0009] In more detail, the following two information elements (IES) are defined in current specifications. The TDD pattern is typically configured with at least the first IE and optionally the 2ndIE:• TDD-DL-UL-ConfigCommon (cell-specific)• TDD-DL-UL-ConfigDedicated (UE-specific)

[0010] The first IE is cell specific (common to all UEs) and is provided by broadcast signaling. It provides the number of slots in the TDD pattern via a reference subcarrierspacing and a periodicity such that the S-slot pattern repeats every S slots. This IE allows for very flexible configuration of the pattern characterized as follows:• A number of full downlink slots at the beginning of the pattern configured by the parameter nDownlinkSlots• A number of full uplink slots at the end of the pattern configured by the parameter nUplinkSlots• A number of downlink ('D') symbols following the full downlink slots configured by the parameter nDownlinkSymbols• A number of uplink ('U') symbols preceding the full downlink slots configured by the parameter nUplinkSlots• If there is a gap between the last downlink symbol and the first uplink symbol, then all symbols in the gap are characterized as flexible ('F'). A symbol classified as 'F' can be used for downlink or uplink. A UE determines the direction in one of the following two ways: o Detecting a downlink control information (DCI) that schedules / triggers a DL signal / channel, e.g., physical downlink shared channel (PDSCH), channel state information reference signal (CSI-RS) or schedules / triggers an UL signal / channel, e.g., physical uplink shared channel (PUSCH), sounding reference signal (SRS), etc. o By dedicated (UE-specific) signaling of the IE TDD-DL-UL- ConfigDedicated. This parameter overrides some or all of the 'F' symbols in the pattern, thus providing a semi-static indication of whether a symbol is classified as 'D' or 'U'.• Optionally, a 2ndpattern that is concatenated to the first pattern can be configured as above. If a 2ndpattern is configured, the constraint is that the sum of the periodicities of the two patterns must evenly divide 20 ms.

[0011] Figure 5 shows an exemplary TDD DL / UL pattern configured by TDD-DL- UL-ConfigCommon. It consists of five slots total, with 3 full D' slots, 1 full 'U' slot, and a mixed slot in between consisting of 4 'D' symbols and 3 'U' symbols. The remaining 7 symbols in the mixed slot are classified as 'F.'

[0012] If a UE is not configured with TDD-DL-UL-ConfigDedicated, then the pattern at the top of the diagram is what it assumes. As stated above, the network can make use of the 'F' symbols flexibly, by scheduling / triggering either an uplink or a downlink signal / channel in a UE specific manner. This allows for very dynamic behavior: thedirection is not known to the UE a priori; rather, the direction becomes known once the UE detects a DCI scheduling / triggering a particular DL or UL signal / channel.

[0013] In contrast, the DL / UL direction for some or all of the 'F' symbols in a particular slot can be provided to the UE in a semi-static manner by radio resource control (RRC) configuring the UE with TDD-DL-UL-ConfigDedicated. The lower part of Figure 5 shows 3 exemplary configurations for overriding 'F' symbols in Slot 3. If the IE indicates 'allDownlink' or 'allUplink' for a particular slot (or slots), then all 'F' symbols in the slot are converted to either 'D' or 'U,' respectively. If the IE indicates 'explicit,' then a number of symbols at the beginning of the slot and / or a number of symbols at the end of the slot are indicated as 'D' and 'U,' respectively. In the example below, the first 7 and the last 5 are indicated as 'D' and 'U', which converts some of the 'F' symbols (but not all in this example) to 'D' and 'U.'

[0014] The key behavior in the above is that the UE-specific IE TDD-DL-UL- ConfigDedicated can only override (i.e., specify 'D' or 'U') for symbols that are configured as 'F' by the cell-specific IE TDD-DL-UL-ConfigCommon. In other words, a UE does not expect to have a 'D' symbol converted to 'U' or vice versa.

[0015] Figure 6 shows three additional exemplary TDD DL / UL patterns configured by TDD-DL-UL-ConfigCommon. In the first and second patterns, there are no 'F' symbols, hence according to current behavior in the Rel-17 specifications, the UE would not expect to be configured with TDD-DL-UL-ConfigDedicated. In the second pattern, all symbols in Slots 1, 2, and 3 are configured as 'F;' hence, the UE could be configured with TDD-DL- UL-ConfigDedicated to provide a direction ('D' or 'U') for any or all symbols in these 3 slots. Note that the current (Rel-17) specifications allow the dedicated configuration of the TDD pattern on a slot-specific basis. In other words, TDD-DL-UL-ConfigDedicated is not restricted to be the same in each slot where 'F' symbols are overridden.Subband full duplex

[0016] As described in the last section, in a conventional TDD system, entire carrier bandwidth (BW) or all carriers in the same frequency band need to use the same DL transmission or UL reception directions. This is further illustrated in Figure 7 (conventional TDD carrier or carrier systems).

[0017] For the Rel-18 evolution of the NR system, 3GPP has decided to study the technical feasibilities and potential benefits of subband full duplex (SBFD) systems, an example of which is shown in Figure 8.• In such a system, a portion of a wide bandwidth carrier may be used for a different direction than that of the rest of the carrier. This is illustrated in the left-hand side of Figure 8. That is, unlike a conventional TDD system as shown on the left-hand side of Figure 7 where the entire bandwidth is used for DL transmission in the first three slots, the center portion of the SBFD carrier is used for UL reception while the rest of the carrier continues to be used for DL transmission as shown in the lefthand side of Figure 8.• Similarly, instead of utilizing all carriers for the same DL or UL directions in a conventional TDD system as shown in the right-hand side of Figure 7, some carriers in the SBFD system can be used for a different direction than that of the other carriers as shown in the right-hand side of Figure 8.

[0018] In the 3GPP Rel-18 study, the scope has been limited such that in SBFD operation, only gNodeBs (gNBs, e.g., a base station in NR) transmit DL and receive UL simultaneously. An individual UE is scheduled in only one direction (DL or UL) at a time.

[0019] One or more OFDM symbols of a slot may be configured with two or more "RB sets" (subbands) where each resource block (RB) set corresponds to a frequency domain subband and has a defined transmission direction ('D' or 'U'). The RB sets may have gaps between them that serve as guardbands where neither DL or UL transmission occurs. Figure 9 shows two example configurations of three RB sets in an SBFD symbol, one with D-U-D configuration (see example “(a)”) and the other with U-D-U configuration (see example “(b)”)- The RB sets are configured either by introduction of new RRC parameter(s) or enhancement of an existing RRC parameter, e.g., TDD-UL-DL- ConfigDedicated. In either case, the parameter(s) signal the size and frequency domain location of the RB sets as well as which symbols / slots in the TDD UL / DL pattern are configured with RB sets.Sounding Reference Signal (SRS)

[0020] SRS is an UL reference signal (RS), based on Zadoff-Chu sequences, used for providing CSI to the network (NW). The usage of SRS includes, e.g., deriving the appropriate transmission / reception beams and / or to perform link adaptation (i.e., setting the transmission rank and the modulation and coding scheme (MCS)), and for determining PDSCH and PUSCH precoding matrices.SRS configuration

[0021] The SRS is configured via RRC signaling, where parts of the configuration can be updated (for reduced latency) via Medium Access Control (MAC) Control Element (CE) signaling. When configuring SRS transmissions, the gNB configures, through the SRS-Config IE, a list of SRS resources and a list of SRS resource sets (see below snippet of ASN from 3GPP Technical Specification (TS) 38.331 version 17.2.0):SRS-Config ::= SEQUENCE ) srs-ResourceSetToReleaseList SEQUENCE (SIZE(l..maxNrofSRS- ResourceSets)) OF SRS-ResourceSetld OPTIONAL, — Need N srs-ResourceSetToAddModList SEQUENCE (SIZE(l..maxNrofSRS- ResourceSets)) OF SRS-ResourceSet OPTIONAL, — Need N srs-ResourceToReleaseList SEQUENCE (SIZE(L.maxNrofSRS-Resources)) OF SRS-Resourceld OPTIONAL, - Need N srs-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-Resource OPTIONAL, - Need N}

[0022] SRS resource(s) will be transmitted as part of an SRS resource set, where each SRS resource set contains one or more SRS resources, and where all SRS resources in an SRS resource set must share the same time-domain behavior.

[0023] NR supports configuration of up to 16 SRS resource sets and 64 SRS resources per bandwidth part (BWP). Furthermore, NR supports periodic SRS (p-SRS), semi-persistent SRS (sp-SRS), or aperiodic SRS (ap-SRS) transmissions:• Periodic (p-SRS): SRS resource sets and SRS resources are RRC configured. SRS resource configuration includes slot periodicity and offset, which determines SRS transmission occasions.• Semi-persistent (sp-SRS): SRS resource sets and SRS resources are RRC configured. SRS resource configuration includes slot periodicity and offset, and SRS transmissions are activated / deactivated using MAC CE signaling.• Aperiodic (ap-SRS): SRS resource sets and SRS resources are RRC configured. SRS resource set configuration includes slot offset, and SRS transmissions are dynamically triggered via 2 -bit “SRS request” field in DCI.

[0024] In short, the SRS resource-set configuration determines, e.g., SRS usage, precoding (PC) parameters, and slot offset for ap-SRS. The SRS resource configurationdetermines, e.g., the SRS time-and-frequency allocation, the SRS sequence, the periodicity and offset for p-SRS / sp-SRS.SJiS resource set configuration

[0025] An SRS resource set is configured with the following in RRC (see ASN code in 3GPP TS 38.331 version 17.2.0):SRS-ResourceSet ::= SEQUENCE ) srs-ResourceSetld SRS-ResourceSetld, srs-ResourceldList SEQUENCE (SIZE(l..maxNrofSRS-ResourcesPerSet)) OF SRS-Resourceld OPTIONAL, — Cond Setup resourceType CHOICE { aperiodic SEQUENCE { aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates- 1), csi-RS NZP-CSI-RS-ResourceldOPTIONAL, — Cond NonCodebook slotOffset INTEGER (1..32)OPTIONAL, - Need S[[ aperiodicSRS-ResourceTriggerList SEQUENCE (SIZE(l..maxNrofSRS- TriggerStates-2))OF INTEGER (L.maxNrofSRS-TriggerStates-1) OPTIONAL - Need M]]}, semi-persistent SEQUENCE { associatedCSLRS NZP-CSI-RS-ResourceldOPTIONAL, — Cond NonCodebook}, periodic SEQUENCE { associatedCSLRS NZP-CSI-RS-ResourceldOPTIONAL, — Cond NonCodebook}}, usage ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching}, alpha Alpha OPTIONAL, -Need S pO INTEGER (-202..24)OPTIONAL, - Cond Setup pathlossReferenceRS PathlossReferenceRS-ConfigOPTIONAL, - Need M srs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2, separateClosedLoop} OPTIONAL, — Need S[[ pathlossReferenceRSList-rl6 SetupRelease { PathlossReferenceRSList-rl6}OPTIONAL - Need M]],[[ usagePDC-rl7 ENUMERATED {true}OPTIONAL, - Need R availableSlotOffsetList-rl7 SEQUENCE (SIZE(1..4)) OF AvailableSlotOffset- r 17 OPTIONAL, - Need R followUnifiedTCIstateSRS-rl7 ENUMERATED {enabled}OPTIONAL — Need R]]}

[0026] An SRS resource set is configurable with respect to, e.g.,• The resource type, which is configured by the higher-layer parameter resourceType determines whether the SRS resource set is periodic, semi-persistent, or aperiodic. For ap-SRS, the slot offset is configured by the higher-layer parameter slotOffset and sets the delay from the physical downlink control channel (PDCCH) trigger reception to the start of the SRS transmission.• The resource usage, which is configured by the higher-layer parameter usage determines constraints and assumptions on the resource properties (see 3 GPP TS38.214 for further details). SRS resource sets can be configured with one of four different usages: antennaSwitching, codebook, nonCodebook, or beamManagement. o An SRS resource set that is configured with usage antennaSwitching is used for reciprocity-based DL precoding (i.e., used to sound the channel in the UL so that the gNB can use reciprocity to set a suitable DL precoders). The UE is expected to transmit one SRS port per UE antenna port. o An SRS resource set that is configured with usage codebook (CB) is used for CB-based UL transmission (i.e., used to sound the different UE antennas and help the gNB to determine / signal a suitable UL precoder, transmission rank, and MCS for PUSCH transmission). There are up to two SRS resources in an SRS resource set with usage codebook. How SRS ports are mapped to UE antenna ports is, however, up to UE implementation and not known to the gNB. o An SRS resource set that is configured with usage nonCodebook (NCB) is used for NCB-based UL transmission. Specifically, the UE transmits one SRS resource per candidate beam (suitable candidate beams are determined by the UE based on CSI-RS measurements in the DL and, hence, reciprocity needs to hold). The gNB can then, by indicating a subset of these SRS resources, determine which UL beam(s) that the UE should apply for PUSCH transmission. One UL layer will be transmitted per indicated SRS resource. Note that how the UE maps SRS ports to antenna ports is up to UE implementation and not known to the gNB. o An SRS resource set that is configured with usage beamManagement is used (mainly for frequency bands above 6 GHz, that is, for frequency range 2 (FR2)) to evaluate different UE analog beams (e.g., panels). The UE transmits one SRS resource per analog beam, and the gNB will perform an RSRP measurement per transmitted SRS resource and, in this way, determine a suitable UE beam that is reported to the UE.• The associated CSI-RS (this configuration is only applicable for NCB-based UL transmission) for each of the possible resource types. o For ap-SRS, the associated CSI-RS resource is determined by the higher- layer parameter csi-RS.o For p-SRS / sp-SRS, the associated CSLRS resource is determined by the higher-layer parameter associatedCSI-RS .• The PC parameters, e.g., alpha and pO are used for setting the SRS transmission power. SRS has its own UL PC scheme in NR (see 3 GPP TS 38.213 for further details), which specifies how the UE should split the available output power between two or more SRS ports during one SRS transmit occasion (an SRS transmit occasion is a time window within a slot where SRS transmission is performed).

[0027] In NR Rel-17, dynamic / available SRS slot offset indication for ap-SRS was introduced and is configured by the higher-layer parameter availableSlotOffsetList-r 17, which lists (up to) 4 slot offsets measured from the legacy slot offset k configured by the higher-layer parameter slotOffset. The DCI triggering the ap-SRS includes a (up to) 2 -bit “SRS offset indicator” which indicates a value t from the list of slot offsets. If the DCI is transmitted in slot n, the ap-SRS is transmitted in the tthavailable slot after slot n + k, where an available slot is a slot that fits all SRS resources in the SRS resource set and that satisfies UE capability on minimum timing requirement.SRS resource configuration

[0028] Each SRS resource is configured with the following in RRC (see below ASN code from 3GPP TS 38.331 version 17.2.0):SRS-Resource ::= SEQUENCE { srs-Resourceld SRS-Resourceld, nrof SRS -Ports ENUMERATED {portl, ports2, ports4}, ptrs-Portlndex ENUMERATED {n0, nl }OPTIONAL, — Need R transmissionComb CHOICE { n2 SEQUENCE { combOffset-n2 INTEGER (0..1), cyclicShift-n2 INTEGER (0..7) }, n4 SEQUENCE { combOffset-n4 INTEGER (0 .3), cyclicShift-n4 INTEGER (0 .11) }},re sourceMapping SEQUENCE { startPosition INTEGER (0 .5), nrofSymbols ENUMERATED {nl, n2, n4{, repetitionF actor ENUMERATED {nl, n2, n4{}, freqDomainPosition INTEGER (0..67), freqDomainShift INTEGER (0..268), freqHopping SEQUENCE { c-SRS INTEGER (0 .63), b-SRS INTEGER (0 .3), b-hop INTEGER (0 .3) groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping }, resourceType CHOICE { aperiodic SEQUENCE { semi-persistent SEQUENCE { periodi city AndOff set- sp SRS-PeriodicityAndOffset,}, periodic SEQUENCE { periodicity AndOffset-p SRS-PeriodicityAndOffset,}}, sequenceld INTEGER (0..1023), spatialRelationlnfo SRS-SpatialRelationlnfoOPTIONAL, — Need R[[ resourceMapping-r 16 SEQUENCE { startPosition-rl6 INTEGER (0 .13),nrofSymbols-rl6 ENUMERATED {nl, n2, n4}, repetitionF actor-r 16 ENUMERATED {nl, n2, n4}OPTIONAL - Need]],[[ spatialRelationlnfo-PDC-r 17 SetupRelease { SpatialRelationInfo-PDC-rl7 }OPTIONAL, - Need M resourceMapping-r 17 SEQUENCE { startPosition-rl7 INTEGER (0 .13), nrofSymbols-rl7 ENUMERATED {nl, n2, n4, n8, nlO, nl2, nl4}, repetitionF actor-r 17 ENUMERATED {nl, n2, n4, n5, n6, n7, n8, nlO, nl2, nl4}OPTIONAL, -- Need partialFreqSounding-rl7 SEQUENCE { startRBIndexF Scaling-r 17 CHOICE} startRBIndexAndFreqScalingFactor2-rl7 INTEGER (0..1), startRBIndexAndFreqScalingFactor4-rl7 INTEGER (0..3) enableStartRBHopping-r 17 ENUMERATED {enable}OPTIONAL - Need ROPTIONAL, -- Need transmissionComb-n8-rl7 SEQUENCE { combOffset-n8-rl7 INTEGER (0..7), cyclicShift-n8-rl7 INTEGER (0 .5)OPTIONAL, -- Need srs-TCIState-rl7 CHOICE { srs-UL-T CIState-r 17 TCI-UL-State-Id-rl7, srs-DLor J oint-TCIState-r 17 TCI-StateldOPTIONAL -- Need]]}[Note that TCI refers to Transmission Configuration Indicator.]

[0029] An SRS resource is configurable with respect to, e.g.,• The number of SRS ports (1, 2, or 4), configured by the higher-layer parameter nrofSRS-Ports.• The transmission comb, i.e., mapping to every 2nd, 4th, or 8th(in NR Rel-17) subcarrier, configured by the higher-layer parameter transmissionComb, which includes: o The higher-layer parameter combOffset determines the comb offset(s), i.e., which subcarriers that should be used for the SRS resource. For four-port SRS resource it is possible for an SRS resource occupy two comb offsets, with two SRS ports per SRS resource. Configuring different comb offsets over SRS resources enables multiplexing of multiple SRS resources on a same SRS bandwidth. o The higher-layer parameter cyclicShift determines the CS(s) for the SRS resource. For multi-port SRS resources, different SRS ports use different CSs, where the CSs are equidistantly spaced. Configuring different CSs over SRS resources enables multiplexing of multiple SRS resources on a same comb offset, but there is a limit on how many CSs that can be used per comb offset: 8 CSs for comb 2, 12 CSs for comb 4, and 6 CSs for comb 8.• The time-domain position within a given slot, configured with the higher-layer parameter resourceMapping, which includes: o The time-domain start position that (in NR Rel-15) is limited to be one of the last 6 symbols, configured by the higher-layer parameter startPosition. In NR Rel-16, the start position was extended to any of the symbols in a slot. o The number of symbols that (in NR Rel-15) can be set to 1, 2 or 4, configured by the higher-layer parameter nrofSymbols. In NR Rel-17, the number of symbols was extended to include also 8, 10, 12, and 14. o The repetition factor that (in NR Rel-15) can be set to 1, 2 or 4, configured by the higher-layer parameter repetitionFactor . When the repetition factoris larger than 1, the same frequency resources are used multiple times across symbols, used to improve the coverage as this allows more energy to be collected by the receiver. The repetition factor must be integer divisible by the number of symbols. In NR Rel-17, the repetition factor was extended to include also 5, 6, 7, 8, 10, 12, and 14.• The SRS frequency-hopping pattern, frequency-domain position, and frequencydomain position shift of an SRS resource (i.e., which part of the BWP that is occupied by the SRS resource) is set through the following: o The higher-layer parameter the freqHopping which contains parameters c- SRS, b-SRS, and b-hop which determines the SRS bandwidth (the smallest possible sounding bandwidth is 4 RBs):■ c-SRS, which determines “configured bandwidth” (see Figure 10).■ b-hop, which determines the “hopping bandwidth” (see Figure 10).■ b-SRS, which determines the “per-hop bandwidth” (see Figure 10). o The higher-layer parameter freqDomainPosition, which determines the start of the SRS hopping bandwidth relative to the SRS configured bandwidth (see Figure 10). o The higher-layer parameter freqDomainShift, which determines the start of the SRS configured bandwidth relative to the start of the BWP (see Figure 10).• The higher-layer parameter resourceType determines whether the SRS resource is periodic, semi-persistent, or aperiodic. For sp-SRS and p-SRS, the slot offset and periodicity is configured by the higher-layer parameter periodicityAndOffset.• The higher-layer parameter sequenceld specifies how the SRS sequence is initialized.• The higher-layer parameter spatialRelationlnfo configures the spatial relation for the SRS beam with respect to another RS (which could be another SRS, an SSB, or a CSI-RS). If an SRS resource has a spatial relation to another SRS resource, it should be transmitted using the same virtualization as for the other SRS resource.

[0030] Note that Figure 10 illustrates an example of how an SRS resource could be allocated in time and frequency within a slot in NR Rel-15 / Rel-16 / Rel-17 (note that semi- persistent / periodic SRS resources typically span several slots). In NR Rel-15, SRS can occupy up to 4 of the last 6 symbols in a slot. In NR Rel-16, SRS can occupy up to 4 of all symbols in a slot. In NR Rel-17, SRS can occupy up to 14 of all symbols in a slot.Rel-17 multi-transmission and reception point (TRP) PUSCH repetition

[0031] Single-DCI, multi-TRP PUSCH repetition was introduced in NR Rel-17. With this scheme, a PUSCH is transmitted, in two or more different slots in a time division multiplexing (TDM) fashion, to two different TRPs. Both CB-based and NCB-based operation is supported and the same number of PUSCH layers (up to four) will be transmitted in a separate beam in each of the slots. To enable such PUSCH repetition, a UE can be configured with up to two SRS resource sets (with the same number of SRS resources and SRS ports) with the same usage. Here, each SRS resource set is associated with a different TRP (and, hence, a different beam). The two beams are mapped to different slots with either a cyclical mapping pattern (see Figure 11, PUSCH multi-TRP repetition with cyclic mapping pattern) or a sequential mapping pattern (see Figure 12, PUSCH multi-TRP repetition with sequential mapping pattern). As the path loss to different TRPs may be significantly different, per- TRP power control can be configured (i.e., separate power control for each SRS resource set).

[0032] Dynamic switching between PUSCH single-TRP transmission and multi-TRP repetition is supported. To enable such dynamic switching, a new 2 -bit “SRS resource set indicator” field is introduced in DCI format 0 1 / 0 2. The following excerpt from 3GPP TS 38.212 describes this new field:• SRS resource set indicator - 0 or 2 bits o 2 bits according to Table 7.3.1.1.2-36 if■ txConfig = nonCodebook, and there are two SRS resource sets configured by srs-ResourceSetToAddModList and associated with the usage of value 'nonCodebook' , or■ txConfig=codebook, and there are two SRS resource sets configured by srs-ResourceSetToAddModList and associated with usage of value 'codebook,' o 0 bit otherwise.

[0033] Table 1 shows the codepoints (indices) of the new, in NR Rel-17, “SRS resource set indicator” field. Here, the first two indices correspond to single PUSCH transmission to a first and second TRP (i.e., to a first and second SRS resource set) and the last two indices correspond to PUSCH repetition to both TRPs. The difference between the last two states is the mapping from, SRS resource sets to a first and a second “SRS resource indicator” field and / or a first and second “Precoding information and number of layers“ field, i.e., in which order the SRS resource sets should be transmitted. The SRSresource set with lower ID is the first SRS resource set, and the other SRS resource set is the second SRS resource set.Table 1: SRS resource set indication(reproduced from Table 7.3.1.1.2-36 in 3GPP TS 38.212 Rel-17)CB-based multi-TRP PUSCH repetition

[0034] For CB-based operation, different Transmission Precoding Matrix Indicators (TPMIs) may be indicated for PUSCH transmission towards different TRPs. Indeed, it is unlikely that a same precoder is suitable for transmission to different TRPs.

[0035] For single-TRP PUSCH, the precoding information and number of layers is indicated via a single “Precoding information and number of layers” field in DCI.

[0036] For multi-TRP PUSCH repetition, since the number of layers towards each TRP must be the same, it is sufficient to indicate the number of layers only for one of the SRS resource sets:• For one of the SRS resource sets, the legacy “Precoding information and number of layers field” will be used.• For the other SRS resource set, it is sufficient to indicate only the precoder for a given number of layers, which reduces overhead. A new “Second precoding information” field is introduced for this purpose. The size of this field varies between 0 — 5 bits depending on the number of antenna ports, UE coherency, etc.NCB-based multi-TRP PUSCH repetition

[0037] For NCB, different SRS resources may be indicated for PUSCH transmission towards different TRPs. For this reason, a “Second SRS resource indicator” (SRI) field is added to the DCI. Since the number of layers must be the same for the second SRS resource set and for the first SRS resource set, the second SRI field may be shorter thanthe first SRI field. Indeed, the number of indicated SRS resources can be inferred from the first SRI.Rel-18 Simultaneous Transmission from Multiple Panel (STxMP)

[0038] In NR up to Rel-17, the discussions regarding UL transmission for FR2 has mainly been for a UE with single-panel transmission in each symbol (transmission from a single UE panel at each time instance, but from two panels at different time instances). In NR-Rel 18, up to two simultaneously transmitting UE panels are supported, where the transmissions on the panels can be controlled using control information in a single PDCCH (‘single-DCI STxMP’) or two PDCCHs (‘multi-DCI STxMP’). An SDM mode (for which different layers of a same transmission are transmitted from different panels) and an SFN mode (for which same layers are transmitted from different panels) are supported for single-DCI STxMP (a single DCI can schedule simultaneous transmission from both UE panels to both TRPs). For multi-DCI STxMP, the UE transmits one or multiple PUSCHs, each of which corresponds to a panel.

[0039] Two SRS resource sets (one per panel) can be configured for both single-DCI and multi-DCI STxMP. Furthermore, a TPMI and / or an SRI field can be indicated for each SRS resource set, depending on whether CB-based PUSCH (which may be with or without an SRI, but which always has a TPMI) or NCB-based PUSCH (with an SRI but not a TPMI) is configured. This holds for both SDM and SFN. For SFN, the transmission rank is conveyed only by the first SRI / TPMI field.

[0040] Dynamic switching via an updated, in NR Rel-18, “SRS resource set indicator” field in DCI between SDM transmission and single TRP (sTRP) transmission as well as between SFN transmission and sTRP transmission is supported. This implies that UE does not know when transmitting SRS whether the SRS ports belonging to one or both SRS resource sets will be used to carry the PUSCH. Table 2 shows the codepoints (indices) of the “SRS resource set indicator” field (in NR Rel-18). Note that compared to Rel-17 multiple TRP (mTRP) repetition, the last codepoint is reserved, as ordering of the SRS resource sets becomes irrelevant if they are transmitted at the same time.Table 2: SRS resource set indication(reproduced from Table 7.3.1.1.2-36 in 3GPP TS 38.212 Rel-18)SUMMARY

[0041] There currently exist certain challenge(s). In an SBFD system, separate SRS resource sets and SRS resources might need to be configured for SRS transmission in non- SBFD and SBFD symbols, which correspond to UL channel sounding and are used as reference signal for PUSCH and physical uplink control channel (PUCCH) transmissions in the respective types of symbols. However, in the current specifications there are certain restrictions for configuration of SRS resources and SRS resource sets for a given usage, reflecting the underlying network and UE modelling assumptions and the design principles for the corresponding application.

[0042] For example, as specified in the latest 3 GPP release, a UE can be configured with one or two SRS resource sets with usage set to "codebook", wherein each set is associated to a TRP. Moreover, the UE can be configured with one or two multi-port SRS resources in each SRS resource set, implicitly connected to one or two antenna panels at the UE. The sizes and the implications of the relevant fields in a DCI that schedules a codebook based PUSCH transmission, such as SRS Resource Set Indicator (SRSI), SRS Resource Indicator (SRI) and TPMI, are all dependent on the configuration restrictions. If separate SRS resources and SRS resource sets were configured to a SBFD-aware UE to support SRS transmission in non-SBFD and SBFD symbols, the configuration rules for SRS resource sets and SRS resources per set would need to be changed, so as the sizes and the implications of the relevant fields in the relevant DCI formats.

[0043] Therefore there needs to be a solution to enhance the legacy SRS configuration to support separate SRS resource sets or SRS resources for non-SBFD and SBFD symbols in a SBFD system while with minimal impact on the existing SRS configuration framework.

[0044] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Embodiments of the present disclosure provide various options for configuration of separate SRS resource sets and / or separate SRS resources to SBFD-aware UE for SRS transmission in non-SBFD and SBFD symbols. The proposed solutions involve pairing of SRS resource sets or SRS resources so that the current schemes of configuration and indication of SRS resource and resource set for PUSCH transmission can be reused with minimal changes.

[0045] Certain embodiments pair SRS units (e.g., an SRS resource is paired with another SRS resource and / or an SRS resource set is paired with another SRS resource set). Each SRS unit of the pair is associated with one symbol type (e.g., SBFD or non-SBFD) based on the symbols where SRS would be transmitted. SRSs of the pairs are selected according to the symbols types where PUSCH is transmitted, and PUSCH is transmitted according to the symbol types as well as the SRS.

[0046] As an example, from a UE perspective, in certain embodiments the UE receives information from a network node indicating the pair of SRS units, and the UE transmits uplink transmissions based on the pair of SRS units. For example, the UE transmits the uplink transmission according to the SRS unit of the pair of SRS units that corresponds to the symbol type (e.g., SBFD or non-SBFD) where the uplink transmissionis to be transmitted. The uplink transmission may be a PUSCH transmission or transmission of an SRS.

[0047] As another example, from a network node perspective, in certain embodiments the network node transmits to the UE information indicating the pair of SRS units, and the network node receives from the UE uplink transmissions based on the pair of SRS units. For example, the network node receives the uplink transmission according to the SRS unit of the pair of SRS units that corresponds to the symbol type (e.g., SBFD or non-SBFD) where the uplink transmission is transmitted. The uplink transmission may be a PUSCH transmission or transmission of an SRS.

[0048] In an embodiment (A), a method in a UE of transmitting in a subband full duplex mode of operation, comprises:• Receiving a configuration of one or more sounding reference signal, SRS unit pairs, wherein: o for each of the SRS units in a pair, one or more OFDM symbols are associated with the SRS unit and are non-overlapping with all of the OFDM symbols associated with the other SRS unit; and o each SRS unit of the pair is associated with symbols of a first or second symbol type, wherein a first symbol type comprises a symbol for which at least one uplink and one downlink subband is configured to the UE and a second symbol type comprises a symbol for which an uplink transmission without a downlink subband is configured to the UE;• Determining a symbol type to be used for a PUSCH transmission as the first or second symbol type according to if it will be transmitted in symbols of the first or the second symbol type;• Selecting an SRS unit of each of the SRS unit pairs corresponding to the first or second symbol type when the symbol type for the PUSCH transmission is the first or second symbol type, respectively; and• Transmitting the PUSCH according to its determined symbol type and to each of the selected SRS units.

[0049] In certain embodiments of the method (A), TPMI and / or SRI are used. For example, in an embodiment (B), the method of embodiment (A) further comprises transmitting the PUSCH according to at least one of a TPMI and an SRI associated with each of the selected SRS units.

[0050] In an embodiment (C), the method of embodiment (A) or (B), wherein an SRS unit comprises an SRS resource set.

[0051] In an embodiment (D), SRSI is used. For example, the method of embodiment (C), wherein the SRS resource set pair indication is carried in an SRS resource set indicator field in DCI, and the UE determines the one or more SRS resource set pairs according to the value of the SRS resource set indicator field.

[0052] In an embodiment (E), the method of embodiment (A) or (B), wherein an SRS unit comprises an SRS resource.

[0053] In an embodiment (F), SRI is used. For example, the method of embodiment (E), wherein the SRS resource pair indication is carried in an SRS resource indicator, SRI, field in DCI, and the UE determines the one or more SRS resource pairs according to the value of the SRI.

[0054] In other embodiments, a network node performs reciprocal operations to support the above method in the UE, e.g., by transmitting the configuration of the one or more SRS unit pairs and receiving the PUSCH according to the one or more SRS unit pairs (e.g., the SRS unit of the one or more SRS unit pairs determined for the PUSCH depends on the symbol type of the received PUSCH).

[0055] Certain embodiments may provide one or more of the following technical advantage(s). Certain embodiments configure SRS for UL transmissions (i.e., codebookbased and non-codebook-based PUSCH) in an SBFD system with minimal specificatiosn changes. The proposed solutions leverage the existing multi-TRP PUSCH transmission framework to support SBFD operation in a single-TRP and multi-TRP scenario.

[0056] According to one aspect of the present disclosure, a method performed by aUE for communicating with a network node in a wireless communication system employing SBFD is provided. The method includes receiving information indicating a configuration of a pair of SRS resource sets, the pair of SRS resource sets comprising a first SRS resource set and a second SRS resource set, the first SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to SBFD symbols and the second SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to non-SBFD symbols. The method includes receiving information for a PUSCH transmission, the information for the PUSCH transmission indicating symbols for the PUSCH transmission. The method includes selecting a selected SRS resource based on a symbol type associated with the symbols for the PUSCH transmission, the selected SRS resource selected from the first SRS resourceset when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for SBFD, the selected SRS resource selected from the second SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for non-SBFD. The method includes transmitting the PUSCH transmission according to the selected SRS resource.

[0057] According to another aspect of the present disclosure, a UE configured for communicating with a network node in a wireless communication system employing SBFD is provided. The UE is configured to receive information indicating a configuration of a pair of SRS resource sets, the pair of SRS resource sets comprising a first SRS resource set and a second SRS resource set, the first SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to SBFD symbols and the second SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to non-SBFD symbols. The UE is configured to receive information for a PUSCH transmission, the information for the PUSCH transmission indicating symbols for the PUSCH transmission. The UE is configured to select a selected SRS resource based on a symbol type associated with the symbols for the PUSCH transmission, the selected SRS resource selected from the first SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for SBFD, the selected SRS resource selected from the second SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for non-SBFD. The UE is configured to transmit the PUSCH transmission according to the selected SRS resource.

[0058] According to another aspect of the present disclosure, a method performed by a network node for communicating with a UE in a wireless communication system employing SBFD operation is provided. The method includes transmitting, to the UE, information indicating a configuration of a pair of SRS resource sets, the pair of SRS resource sets comprising a first SRS resource set and a second SRS resource set, the first SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to SBFD symbols and the second SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to non-SBFD symbols. The method includes transmitting, to the UE, information for a PUSCH transmission, the information for the PUSCH transmission indicating symbols for the PUSCH transmission. The method includes receiving the PUSCH transmission according to a selected SRS resource, the selected SRS resource selected from the first SRS resource set when asymbol type associated with symbols for the PUSCH transmission corresponds to symbols for SBFD, the selected SRS resource selected from the second SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for non-SBFD.

[0059] According to another aspect of the present disclosure, a network node configured for communicating with a UE in a wireless communication system employing SBFD operation is provided. The network node is configured to transmit, to the UE, information indicating a configuration of a pair of SRS resource sets, the pair of SRS resource sets comprising a first SRS resource set and a second SRS resource set, the first SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to SBFD symbols and the second SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to non-SBFD symbols. The network node is configured to transmit, to the UE, information for a PUSCH transmission, the information for the PUSCH transmission indicating symbols for the PUSCH transmission. The network node is configured to receive the PUSCH transmission according to a selected SRS resource, the selected SRS resource selected from the first SRS resource set when a symbol type associated with symbols for the PUSCH transmission corresponds to symbols for SBFD, the selected SRS resource selected from the second SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for non-SBFD.BRIEF DESCRIPTION OF THE DRAWINGS

[0060] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0061] Figure l is a schematic diagram of an example radio resource in New Radio (NR);

[0062] Figure 2 is a diagram of an example NR slot;

[0063] Figure 3 is a schematic diagram of an example of frequency division duplex(FDD) and time division duplex (TDD);

[0064] Figure 4 is a diagram of an example uplink / downlink time / frequency structure in case of FDD or TDD;

[0065] Figure 5 is a diagram of an example TDD downlink (DL) / uplink (UL) pattern consisting of S = 5 slots;

[0066] Figure 6 is a diagram of three additional examples of cell-specific TDD DL / UL patterns (a), (b), and (c);

[0067] Figure 7 is a diagram of an example of conventional TDD carrier or carrier systems;

[0068] Figure 8 is a diagram of an example of subband full duplex systems;

[0069] Figure 9 is a diagram of example configurations of 3 resource block (RB) sets in a subband full duplex (SBFD) symbol configured as (a) D-U-D, and (b) U-D-U;

[0070] Figure 10 is a diagram of an example of how a sounding reference signal (SRS) resource could be allocated in time and frequency within a slot in various NR releases;

[0071] Figure 11 is a diagram of an example physical uplink shared channel (PUSCH) multi- transmission and reception point (TRP) repetition with cyclic mapping pattern;

[0072] Figure 12 is a diagram of an example PUSCH multi-TRP repetition with sequential mapping pattern;

[0073] Figure 13 is a diagram of an example SRS resource set pairing according to one or more embodiments;

[0074] Figure 14 is a diagram of an example SRS resource pairing according to one or more embodiments;

[0075] Figure 15 is a diagram of an example method in a UE according to one or more embodiments;

[0076] Figure 16 is a diagram of an example method in a network node according to one or more embodiments;

[0077] Figure 17 is another diagram of an example method in a UE according to one or more embodiments;

[0078] Figure 18 is another diagram of an example method in a network node according to one or more embodiments;

[0079] Figure 19 is a schematic diagram of an example communication system according to one or more embodiments;

[0080] Figure 20 is a schematic diagram of an example user equipment (UE) according to one or more embodiments;

[0081] Figure 21 is a schematic diagram of an example network node according to one or more embodiments; and

[0082] Figure 22 is a schematic diagram of an example virtualization environment according to one or more embodiments.DETAILED DESCRIPTION

[0083] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0084] Embodiments herein support separate SRS units, where one of the separate SRS units corresponds to a non-SBFD symbol type and another of the separate SRS units corresponds to an SBFD symbol type. A given SRS unit is associated with only one symbol type. In some embodiments, an SBFD symbol is a symbol for which at least one uplink and one downlink subband is configured to the UE. In some embodiments, a non- SBFD symbol is a symbol for which an uplink transmission without a downlink subband is configured to the UE. In certain embodiments, an SRS unit corresponds to an SRS resource. In other embodiments, an SRS unit corresponds to an SRS resource set. In other words, certain embodiments support separate SRS resources (one of the SRS resources corresponding to a non-SBFD symbol type and another of the SRS resources corresponding to an SBFD symbol type) and certain embodiments support separate SRS resource sets (one of the SRS resource sets corresponding to a non-SBFD symbol type and another of the SRS resource sets corresponding to an SBFD symbol type).

[0085] Pairs of SRS units (e.g., pairs of SRS resources or pairs of SRS resource sets) are constructed, where each SRS unit in the pair is associated with symbol(s) that are nonoverlapping with the symbol(s) associated with the other SRS unit in the pair. The UE determines the symbol type associated with a unit (resource / resource set) pair through separate signaling. In one non-limiting example, the signaling is via RRC which provides semi-static cell-specific time domain pattern of SBFD and non-SBFD symbols. The signaling can be broadcast (e.g., via a system information block, such as SIB 1) or provided by dedicated (per-UE) signaling.

[0086] The UE transmits at least one of SRS and PUSCH according to the SBFD or non-SBFD symbol type of the corresponding SRS resource or SRS resource set it determined according to the symbol type, as discussed in the following embodiments. The determination of the symbol type is based on the signaling described above.

[0087] Throughout the disclosure, examples described as applicable to SRS resources or SRS resource sets (e.g., examples for which either option is possible) can interchangeably be described as applicable to SRS resource units.Embodiment 1: SRS resource set pairing

[0088] According to the teaching of this embodiment, separate SRS resource sets can be configured to an SBFD-aware UE for SRS transmission in non-SBFD and SBFD symbols for a given usage. A non-SBFD SRS resource set contains one or multiple SRS resources to be transmitted in non-SBFD symbols and an SBFD SRS resource set contains one or multiple SRS resources to be transmitted in SBFD symbols. Pairing between a non- SBFD and an SBFD SRS resource set can be implicitly or explicitly indicated to the UE, wherein an SRS resource set pair comprises of a non-SBFD and an SBFD SRS resource set.

[0089] Figure 13 demonstrates an example for SRS resource set pairing. In the figure, two non-SBFD SRS resource sets (0 and 1) and two SBFD SRS resource sets (2 and 3) are configured to the UE for a given usage. The SRS resource sets are further paired into SRS resource set pair 0 and 1, where each SRS resource set pair comprises of a non-SBFD and an SBFD SRS resource set.Pairing of SRS resource sets for CB or NCB based PUSCH transmission

[0090] When SRS resource sets with pairing is configured to the UE, for example in a single-TRP scenario, a single pair of SRS resource sets is configured with the usage set to 'codebook or 'noncodebook' . The UE should associate PUSCH transmissions in non- SBFD and SBFD symbols with the non-SBFD and SBFD SRS resource set in the pair respectively.

[0091] When SRS resource sets with pairing is configured to the UE, e.g., in a multi- TRP scenario, two pairs of SRS resource sets are configured with the usage set to 'codebook or 'noncodebook . For determination of the association between PUSCH transmission occasions or PUSCH antenna port(s) with the SRS resource set pairs, the schemes in the legacy specification for association between PUSCH transmission occasions or PUSCH antenna port(s) and SRS resource sets (see Clause 6.1 in Reference [2]) can be reused, by applying the specifications to SRS resource set pairs instead of SRS resources sets. For particular PUSCH transmissions associated with an SRS resource set pair, the UE should apply the non-SBFD and the SBFD SRS resource sets in the pair to PUSCH transmission in non-SBFD and SBFD symbols respectively.

[0092] In some specific embodiments where the UE is configured with two SRS resource set pairs, the UE receives an SRS resource set pair indication. The UE determines one or more SRS resource set pairs to be used from the SRS resource set pair indication, and selects an SRS resource set from each of the one or more SRS resource set pairs according to whether a PUSCH transmission is to be within the time domain resources associated with the selected SRS resource set in the pair, wherein the time domain resources are associated with one of an SBFD and a non-SBFD symbol type. The UE then transmits PUSCH according to at least one of a TPMI and an SRI associated with each of the selected SRS resource sets. In some such embodiments, the SRS resource set pair indication may be carried in an SRS resource set indicator field in DCI, and the UE determines the one or more SRS resource set pairs according to the value of the SRS resource set indicator field.

[0093] In some specific embodiments, if UE receives configuration or indication to transmit multi-slot PUSCH transmission across non-SBFD and SBFD symbols, the UE determines 1) based on an SRS resource set pair configuration consisting of a single SRS resource set pair (e.g., for single-TRP PUSCH repetition type A or B) or 2) based on a SRS resource set pair indication of one or two SRS resource set pairs (e.g., for multi-TRP PUSCH repetition type A or type B), both SRS resource sets to be used from each of the one or more SRS resource set pairs. The UE then transmits PUSCH according to at least one of a TPMI and an SRI associated with both SRS resource sets in each of the selected SRS resource set pairs. In other words, the UE applies the same UL precoding in both SBFD and non-SBFD symbols for the multi-slot PUSCH transmission. In this way, for PUSCH scheduled by dynamic grant (DG), the existing Precoding information and number of layers, Second precoding information, SRS resource indicator, and Second SRS resource indicator field in DCI 0 1 / 0 2 can be reused for indicating UL precoding in both SBFD and non-SBFD symbols. This, however, requires that, at least, the number of SRS resources, the number of SRS ports per each SRS resource, and the TCI state configuration is the same across all SRS resource sets in a same SRS resource set pair. In some other specific embodiments, the UE is indicated with two SRIs and / or two TPMIs for each SRS resource set pair, wherein each SRI and / or TMPI are associated with each SRS resource set of the SRS resource set pair respectively. The UE then transmits PUSCH according to at least one of an SRI and a TPMI associated with each SRS resource set in each of the selected SRS resource set pairs. In other words, the UE applies different UL precoding in SBFD and non-SBFD symbols for the multi-slot PUSCH transmission. Thiseffectively requires the current DCI 0 1 / 0 2 to be extended with two more SRI fields and / or two more TPMI fields to support multi-slot PUSCH transmission across non-SBFD and SBFD symbols associated with two SRS resource set pairs. In a variant of the specific embodiments, two TMPIs but only one SRI is indicated to the UE for each SRS resource set pair, implying that the same SRI is applied to both SRS resource sets in the SRS resource set pair.

[0094] In some specific embodiments, for multi-TRP operation, for PUSCH scheduled by a DG, UE receives SRS resource set pair indication via DCI and the existing SRS resource set indicator field in DCI 0_l / 0_2 (see Table 7.3.1.1.2-36 in TS 38.212) is repurposed for the SRS resource set pair indication. For example, in one embodiment, the SRS resource set indicator field in DCI 0 1 / 0 2 indicates SRS resource set pairs (as described in the above) or SRS resource sets (as in legacy NR) depending on whether UE is configured with SBFD operation or not. In one embodiment, for PUSCH scheduled by configured grant (CG), the UE receives the SRS resource set pair indication via RRC signaling.Methods for SRS resource set lists configuration

[0095] In a variant of the embodiment, the SRS resource sets for SRS transmission in non-SBFD and SBFD and symbols are configured in the same SRS resource set lists (i.e., srs-ResourceSetToAddModList or srs-ResoiirceSelToAddModI.isd)CI-0-2 . In this case a new parameter can be introduced to an SRS resource set configuration explicitly indicating what symbol type the SRS resource set is associated with. If this parameter is not present, the UE can assume the SRS resource set is for non-SBFD symbols. In another variant of the embodiment, the SRS resource sets for SRS transmission in non-SBFD and SBFD symbols are configured in separate SRS resource set lists, wherein the non-SBFD SRS resource sets are in the legacy SRS resource set lists (i.e., srs- ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 while the SBFD SRS resource sets are in one or multiple new SRS resource set lists (e.g., srs- ResourceSetToAddModList-SBFD or srs-ResourceSetToAddModListDCI-0-2-SBFDMethods for pairing of two SRS resource sets

[0096] In a variant the of the embodiment, the pairing of the SRS resource sets follows the order of the SRS resource set IDs. That is, among the configured SRS resource sets for the given usage of ‘ codebook" or 'noncodebook'. the non-SBFD SRS resource set with the lowest ID value is paired with the SBFD SRS resource set with the lowest ID value, the non-SBFD SRS resource set with the second lowest ID value is paired with theSBFD SRS resource set with the second lowest ID value, and so on. This embodiment, applies, for example, to the case above where there are two SRS resource set lists. For example, in Figure 13, if resource set 0 and 1 are in one list and resource set 2 and 3 are in a second list, then the pairs are formed in ascending order of the list elements as {0,2} and { 1,3}. The first pair is implicitly associated with pair ID 0 and the 2ndpair with pair ID 1. The UE can determine which pair ID (0 or 1) is associated with an SRS resource set by separate configuration, either inside or outside an SRS resource set.

[0097] In another variant of the embodiment, the pairing of the SRS resource sets is explicitly indicated by introducing a pairing ID in an SRS resource set configuration. A pair of SRS resource sets comprises of two SRS resource sets with the same usage and the same pairing ID and are indicated with different symbol types (i.e., a first SRS resource set in the pair is associated with SBFD symbols and the other SRS resource set in the pair is associated with non-SBFD symbols) or from different lists of SRS resource sets. This embodiment applies, for example, to the case above where there is a single SRS resource set list. For example, in Figure 13, the pair ID 0, 1, 0, 1 would be associated with SRS resource sets 0, 1, 2, 3, respectively. The UE can determine which pair ID (0 or 1) is associated with an SRS resource set by separate configuration, either inside or outside an SRS resource set.

[0098] In yet another variant of the embodiment, the pairing of the SRS resource sets is explicitly indicated by introducing a paired SRS resource set ID to the SRS resource set configuration, which provides the ID of another SRS resource set that is paired with the SRS resource set. The two SRS resource sets being paired need to be configured with the same usage. In a non-liming example, the paired SRS resource set ID can be present only in a non-SBFD SRS resource set, pointing to a paired SBFD SRS resource set.

[0099] In yet another variant of the embodiment, the pairing of the SRS resource sets is explicitly configured by one or multiple instances of a new IE for SRS resource set pair configuration (e.g., " RS-ResourceSetPair" IE). The SRS resource set pair configuration IE includes at least a pairing ID and two SRS resource set IDs of a non-SBFD and an SBFD SRS resource set configured to the UE with the same usage. In a non-limiting realization, the SRS resource set pair IE can further include some other parameters shared by the two SRS resource sets in the pair, such as associated TCI state, power control parameters, etc.Configuration restrictions on SRS resource set pairing

[0100] In a non-limiting realization of the embodiment, the UE is configured with the same number of non-SBFD and SBFD SRS resource sets for a given usage of "codebook" or ' noncode hook" , so that each non-SBFD SRS resource set can be paired with an SBFD SRS resource set.

[0101] In a non-limiting realization of the embodiment, both SRS resource sets within a pair need to be configured with the same number of SRS resources. This is to enable multi-slot PUSCH transmission across non-SBFD and SBFD symbols, where the same SRI are applied to the non-SBFD and the SBFD SRS resource set for PUSCH transmission in non-SBFD and SBFD symbols respectively.

[0102] In a non-limiting realization of the embodiment, the SRS resources in a pair of SRS resource sets need to be configured with the same number of SRS ports. This is to enable multi-slot PUSCH transmission across non-SBFD and SBFD symbols, where the same TPMI are applied to the non-SBFD and the SBFD SRS resource set for PUSCH transmission in non-SBFD and SBFD symbols respectively.

[0103] In a non-limiting realization of the embodiment, the two SRS resource sets of an SRS resource set pair are associated with the same indicated TCI-State or TCI-UL- State. If unified TCI framework is configured, the SRS resource sets of the first and second SRS resource set pair are associated with first and second indicated TCI-state or TCIdJL-State, respectively. Specifically, both SRS resource sets in an SRS resoruce set pair should be configured with a same value (‘first’ or ‘second’) of zpplylndicatedTCI- State-rl8.Embodiment 2: SRS resource pairing

[0104] According to the teaching of this embodiment, separate SRS resources can be configured to an SBFD-aware UE for SRS transmission in non-SBFD and SBFD symbols. A non-SBFD SRS resource configuration specifies parameters for SRS transmission in non-SBFD symbols, a SBFD SRS resource configuration specifies parameters for SRS transmission in SBFD symbols. A UE can be configured with one or two SRS resource sets with the usage set to 'codebook or 'noncodebook\ wherein each SRS resource set consists of one or multiple non-SBFD SRS resources and zero, one or mutiple SBFD SRS resources. Pairing between a non-SBFD and a SBFD SRS resource in an SRS resource set can be implicitly or explicitly indicated to the UE, wherein an SRS resource pair comprises of a non-SBFD and an SBFD SRS resource.

[0105] Figure 14 demonstrates an example for SRS resource pairing. In the figure, two non-SBFD SRS resources (0 and 1) and two SBFD SRS resources (2 and 3) are configured to the UE in an SRS resource set for a given usage. The SRS resources are paired into SRS resource pair 0 and 1, where each SRS resource pair comprises of a non- SBFD and an SBFD SRS resource.

[0106] In some specific embodiments where SRS resource pairing is configured to the UE and where there is only one pair of SRS resources in an SRS resource set, for a dynamic grant or configured grant based PUSCH transmission, the UE should determine its PUSCH transmission precoder in non-SBFD symbols based on the non-SBFD SRS resource in the pair and its PUSCH transmission precoder in SBFD symbols based on the SBFD SRS resource in the pair.

[0107] In some other specific embodiments where SRS resource pairing is configured to the UE and where there are multiple pairs of SRS resources configured in an SRS resource set, the UE is indicated or configured with an SRS Resource Indicator (SRI) associated with the SRS resource set for a PUSCH transmission. The UE uses the indicated / configured SRI to select one of the configured SRS resource pairs for the PUSCH transmission. Then the UE should determine its PUSCH transmission precoder in non-SBFD symbols based on the non-SBFD SRS resource in the pair and its PUSCH transmission precoder in SBFD symbols based on the SBFD SRS resource in the pair.Methods for SRS resources configuration

[0108] In a variant of the embodiment, the SRS resource for SRS transmission in non- SBFD and SBFD symbols are configured in the same SRS resource lists (i.e., srs- ResourceToAddModLisf). In this case a new parameter can be introduced to an SRS resource configuration indicating what symbol type the SRS resource is associated with. If this parameter is not present, the UE can assume the SRS resource is associated with non- SBFD symbols.

[0109] In another variant of the embodiment, the SRS resources for SRS transmission in non-SBFD and SBFD symbols are configured in separate SRS resource lists, wherein the non-SBFD SRS resources are in the legacy SRS resource list (i.e., srs- ResoiirceToAddModl.isl). while the SBFD SRS resources are in a new SRS resource list (e . g . , srs-Resource ToAddModList-SBFD) .Methods for pairing of two SRS resources

[0110] In a variant the of the embodiment, the pairing of the SRS resources follows the order of the SRS resource IDs. That is, among the configured SRS resources in an SRS resource set with usage set to ‘ codebook" or 'noncodebook' the non-SBFD SRS resource with the lowest ID value is paired with the SBFD SRS resource with the lowest ID value, the non-SBFD SRS resource with the second lowest ID value is paired with the SBFD SRS resource with the second lowest ID value, and so on. For example, in Figure 14, there are 4 SRS resources (0-3) in the SRS resource set. The SRS resource pairs are formed in ascending order of the SRS resources as {0,2} and { 1,3}. The first pair is implicitly associated with pair ID 0 and the 2nd pair with pair ID 1.[oni] In another variant of the embodiment, the pairing of the SRS resources is explicitly indicated by introducing a pairing ID in an SRS resource configuration. A pair of SRS resources in an SRS resource set with usage set to 'codebook" or 'noncodebook" comprises of two SRS resources in the set with the same pairing ID and are indicated with different SBFD symbol types or from different lists of SRS resources. For example, in Figure 14, the pair ID 0, 1, 0, 1 would be associated with SRS resource 0, 1, 2, 3, respectively, forming two SRS resource pairs as {0,2} and { 1,3}.

[0112] In yet another variant of the embodiment, the pairing of the SRS resources is explicitly indicated by introducing a paired SRS resource ID to the SRS resource configuration, which provides the ID of another SRS resource in the same SRS resource set that is paired with the SRS resource. In a non-liming example, the paired SRS resourceID can be present only in a non-SBFD SRS resource, pointing to a paired SBFD SRS resource in the same SRS resource set.

[0113] In yet another variant of the embodiment, the pairing of the SRS resources is explicitly configured by one or multiple instances of a new IE for SRS resource pair configuration (e.g., " RS-ResourcePair" IE). The SRS resource pair configuration IE includes at least a pairing ID and two SRS resource IDs of a non-SBFD and an SBFD SRS resource in the same SRS resource set.Configuration restrictions on SRS resource pairing

[0114] In a non-limiting realization of the embodiment, the two SRS resources in a pair need to be configured with the same number of SRS ports. This is to enable multi-slot PUSCH transmission across non-SBFD and SBFD symbols, where the same TPMI are applied to the non-SBFD and the SBFD SRS resource for PUSCH transmission in non- SBFD and SBFD symbols respectively.

[0115] In a non-limiting realization of the embodiment, if spatial relation is configured per SRS resource, the two SRS resources in the pair are either associated with the same SRS-SpatialRelationlnfo or the spatialRelationlnfo of a second SRS resource in a pair is associated with (points to) the first SRS resource in the pair. In another non-limiting realization of the embodiment, if TCI state is configured per SRS resource, the two SRS resources in a pair are associated with the same indicated TCI-State or TCI-UL-State . If unified TCI framework is configured, all SRS resources of an SRS resource set are associated with a same TCI state, and, hence, if both SRS resources in a pair belongs to the same SRS resource set, it follows that they are configured with the same unified TCI state.

[0116] Figure 15 illustrates an example of a method that may be performed by a UE, such as UE 112 of Figure 19 or UE 200 of Figure 20. As an example, in certain embodiments, the UE comprises at least one processor (such as processing circuitry 202) configured to perform one or more steps of the method. In certain embodiments, the UE comprises a computer-readable medium (such as memory 210) comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform any of the steps of the method.

[0117] The method begins at step 1502 with receiving an indication indicating a configuration of an SRS unit pair. The SRS unit pair comprises a first SRS unit associated with symbols of a first symbol type and a second SRS unit associated with symbols of a second symbol type. The method proceeds to step 1504 with transmitting an uplinktransmission. The uplink transmission is transmitted according to the first SRS unit when the uplink transmission occurs in one or more of the symbols associated with the first symbol type. Or, the uplink transmission is transmitted according to the second SRS unit when the uplink transmission occurs in one or more of the symbols associated with the second symbol type. See, e.g., the “Group A” embodiments below for examples of further options for implementing the method.

[0118] Figure 16 illustrates an example of a method that may be performed by a network node, such as network node 110 of Figure 19 or network node 300 of Figure 21. As an example, in certain embodiments, the network node comprises at least one processor (such as processing circuitry 302) configured to perform one or more steps of the method. In certain embodiments, the network node comprises a computer-readable medium (such as memory 304) comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform any of the steps of the method.

[0119] The method shown in Figure 16 begins at step 1602 with sending, to a UE, an indication indicating a configuration of an SRS unit pair. The SRS unit pair comprises a first SRS unit associated with symbols of a first symbol type and a second SRS unit associated with symbols of a second symbol type. The method proceeds to step 1604 with receiving an uplink transmission from the UE. The uplink transmission is received according to the first SRS unit when the uplink transmission occurs in one or more of the symbols associated with the first symbol type. Or, the uplink transmission is received according to the second SRS unit when the uplink transmission occurs in one or more of the symbols associated with the second symbol type. See, e.g., the “Group B” embodiments below for examples of further options for implementing the method.

[0120] Figure 17 illustrates another example of a method that may be performed by a UE, such as UE 112 of Figure 19 or UE 200 of Figure 20. As an example, in certain embodiments, the UE comprises at least one processor (such as processing circuitry 202) configured to perform one or more steps of the method. In certain embodiments, the UE comprises a computer-readable medium (such as memory 210) comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform any of the steps of the method. UE is configured to receive (1702) information indicating a configuration of a pair of sounding reference signal, SRS, resource sets, the pair of SRS resource sets comprising a first SRS resource set and a second SRS resource set, the first SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to SBFD symbols and the second SRS resource set comprisingone or more SRS resources associated with a symbol type corresponding to non-SBFD symbols. UE is configured to receive (1704) information for a physical uplink shared channel, PUSCH, transmission, the information for the PUSCH transmission indicating symbols for the PUSCH transmission. UE is configured to select (1706) a selected SRS resource based on a symbol type associated with the symbols for the PUSCH transmission, the selected SRS resource selected from the first SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for SBFD, the selected SRS resource selected from the second SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for non-SBFD. UE is configured to transmit (1708) the PUSCH transmission according to the selected SRS resource.

[0121] In some embodiments, the selecting of the selected SRS resource in the first SRS resource set or the second SRS resource set further based on an SRS resource identifier, SRI, received in the information for the PUSCH transmission.

[0122] In some embodiments, the information for the PUSCH transmission received at least in part via downlink control information, DCI.

[0123] In some embodiments, the information for the PUSCH transmission received at least in part via radio resource control, RRC, signaling.

[0124] In some embodiments, the SBFD symbols associated with the one or more SRS resources of the first SRS resource set are non-overlapping with the non-SBFD symbols associated with the one or more SRS resources of the second SRS resource set.

[0125] In some embodiments, transmitting the PUSCH transmission according to the selected SRS resource is further based on a transmission precoding matrix indicator, TPMI, received in the information for the PUSCH transmission.

[0126] In some embodiments, the configuration of the pair of SRS resource sets comprises a symbol type parameter configured to SBFD for the one or more SRS resources of the first SRS resource set and a symbol type parameter configured to non- SBFD for the one or more SRS resources of the second resource set.

[0127] In some embodiments, the first SRS resource set includes a same number of SRS resources and a same number of SRS ports as the second SRS resource set.

[0128] In some embodiments, the pair of SRS resource sets configured for either codebook usage or non-codebook usage.

[0129] In some embodiments, the information for the PUSCH transmission indicates a multi-slot PUSCH transmission.

[0130] In some embodiments, the selecting of the selected SRS resource comprises one or more of: selecting from the first SRS resource set for a transmission occasion of the multi-slot PUSCH transmission for which an associated symbol type corresponds to the symbols for SBFD; and selecting from the second SRS resource set for a transmission occasion of the multi-slot PUSCH transmission for which an associated symbol type corresponds to the symbols for non-SBFD.

[0131] In some embodiments, a same SRI received in the information for the PUSCH transmission applies for: transmitting the multi-slot PUSCH transmission in the transmission occasion for which the associated symbol type corresponds to the symbols for SBFD; and transmitting the multi-slot PUSCH transmission in the transmission occasion for which the associated symbol type corresponds to the symbols for non-SBFD.

[0132] In some embodiments, a same TPMI received in the information for the PUSCH transmission applies for: transmitting the multi-slot PUSCH transmission in the transmission occasion for which the associated symbol type corresponds to the symbols for SBFD; and transmitting the multi-slot PUSCH transmission in the transmission occasion for which the associated symbol type corresponds to the symbols for non-SBFD.

[0133] In some embodiments, UE 112 is further configured to: receive information indicating a configuration of another pair of SRS resource sets.

[0134] In some embodiments, a Transmission Configuration Indicator, TCI, state configuration is the same across all SRS resource sets in a same SRS resource set pair.

[0135] In some embodiments, the pair of SRS resource sets being configured for communicating with a first transmission and reception point, TRP, and another pair of SRS resource sets being configured for communicating with a second TRP.

[0136] In some embodiments, the UE 112 is further configured to determine to select one or more SRS resources for the PUSCH transmission from the pair of SRS resource sets, another pair of SRS resource sets, or both according to an SRS resource set indicator, SRSI, received in the information for the PUSCH transmission.

[0137] In some embodiments, in response to determining to select from both pairs of SRS resource sets, the transmitting of the PUSCH transmission comprises transmitting according to SRS resources from both pairs of SRS resource sets.

[0138] Figure 18 illustrates an example of a method that may be performed by a network node, such as network node 110 of Figure 19 or network node 300 of Figure 21. As an example, in certain embodiments, the network node comprises at least one processor (such as processing circuitry 302) configured to perform one or more steps of the method.In certain embodiments, the network node comprises a computer-readable medium (such as memory 304) comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform any of the steps of the method. Network node is configured to transmit (1802), to the UE, information indicating a configuration of a pair of sounding reference signal, SRS, resource sets, the pair of SRS resource sets comprising a first SRS resource set and a second SRS resource set, the first SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to SBFD symbols and the second SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to non-SBFD symbols. Network node is configured to transmit (1804), to the UE, information for a physical uplink shared channel, PUSCH, transmission, the information for the PUSCH transmission indicating symbols for the PUSCH transmission. Network node is configured to receive (1806) the PUSCH transmission according to a selected SRS resource, the selected SRS resource selected from the first SRS resource set when a symbol type associated with symbols for the PUSCH transmission corresponds to symbols for SBFD, the selected SRS resource selected from the second SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for non-SBFD.

[0139] In some embodiments, the information for the PUSCH transmission comprises an SRS resource identifier, SRI, used in selecting the selected SRS resource in the first SRS resource set or the second SRS resource set.

[0140] In some embodiments, the information for the PUSCH transmission transmitted at least in part via downlink control information, DCI.

[0141] In some embodiments, the information for the PUSCH transmission transmitted at least in part via radio resource control, RRC, signaling.

[0142] In some embodiments, the SBFD symbols associated with the one or more SRS resources of the first SRS resource set are non-overlapping with the non-SBFD symbols associated with the one or more SRS resources of the second SRS resource set.

[0143] In some embodiments, the information for the PUSCH transmission further comprises a transmission precoding matrix indicator, TPMI.

[0144] In some embodiments, the configuration of the pair of SRS resource sets comprises a symbol type parameter configured to SBFD for the one or more SRS resources of the first SRS resource set and a symbol type parameter configured to non- SBFD for the one or more SRS resources of the second resource set.

[0145] In some embodiments, the first SRS resource set includes a same number of SRS resources and a same number of SRS ports as the second SRS resource set.

[0146] In some embodiments, the pair of SRS resource sets configured for either codebook usage or non-codebook usage.

[0147] In some embodiments, the information for the PUSCH transmission indicates a multi-slot PUSCH transmission.

[0148] In some embodiments, selecting of the selected SRS resource comprises one or more of selecting from the first SRS resource set for a transmission occasion of the multislot PUSCH transmission for which an associated symbol type corresponds to the symbols for SBFD; and selecting from the second SRS resource set for a transmission occasion of the multi-slot PUSCH transmission for which an associated symbol type corresponds to the symbols for non-SBFD.

[0149] In some embodiments, a same SRI sent in the information for the PUSCH transmission applies for: the transmission occasion of the multi-slot PUSCH transmission for which the associated symbol type corresponds to the symbols for SBFD; and the transmission occasion of the multi-slot PUSCH transmission for which the associated symbol type corresponds to the symbols for non-SBFD.

[0150] In some embodiments, a same TPMI sent in the information for the PUSCH transmission applies for: the transmission occasion of the multi-slot PUSCH transmission for which the associated symbol type corresponds to the symbols for SBFD; and the transmission occasion of the multi-slot PUSCH transmission for which the associated symbol type corresponds to the symbols for non-SBFD.

[0151] In some embodiments, The network node 110 is further configured to: transmit information indicating a configuration of another pair of SRS resource sets.

[0152] In some embodiments, a Transmission Configuration Indicator, TCI, state configuration is the same across all SRS resource sets in a same SRS resource set pair.

[0153] In some embodiments, the pair of SRS resource sets being configured for communicating with a first transmission and reception point, TRP, and another pair of SRS resource sets being configured for communicating with a second TRP.

[0154] In some embodiments, the information for the PUSCH transmission further comprises an SRS resource set indicator, SRSI, based on which the UE determines the pair of SRS resource sets, another pair of SRS resource sets, or both.

[0155] In certain embodiments, a UE and a network node may perform reciprocal operations. For example, a message sent from a UE to a network node may be received bythe network node from the UE, and vice versa. Thus, methods performed by the UE (e.g., such as the method of Figure 15) may include any suitable steps or features to support the network node performing its methods (e.g., such as the method of Figure 16), and vice versa.

[0156] EXAMPLE EMBODIMENTS

[0157] Group A Embodiments

[0158] 1. A method of Sounding Reference Signal (SRS) configuration in a UE 112, the method comprising: receiving (1502) an indication indicating a configuration of an SRS unit pair, the SRS unit pair comprising a first SRS unit associated with symbols of a first symbol type and a second SRS unit associated with symbols of a second symbol type; and transmitting (1504) an uplink transmission, wherein the uplink transmission is transmitted according to the first SRS unit when the uplink transmission occurs in one or more of the symbols associated with the first symbol type, and wherein the uplink transmission is transmitted according to the second SRS unit when the uplink transmission occurs in one or more of the symbols associated with the second symbol type.

[0159] 2 The method of example 1, wherein the symbols of the second symbol type associated with the second SRS unit are non-overlapping with the symbols of the first symbol type associated with the first SRS unit.

[0160] 3 The method of any of examples 1-2, wherein the symbols of the first symbol type and the symbols of the second symbol type are each OFDM symbols.

[0161] 4. The method of any of examples 1-3, wherein: the first symbol type comprises a symbol for which at least one uplink and one downlink subband is configured to the UE 112; and the second symbol type comprises a symbol for which an uplink transmission without a downlink subband is configured to the UE 112.

[0162] 5 The method of any of examples 1-4, wherein the first symbol type corresponds to SBFD and the second symbol type corresponds to non-SBFD.

[0163] 6. The method of any of examples 1-5, wherein the uplink transmission comprises an SRS and / or a PUSCH.

[0164] 7 The method of any of examples 1-6, wherein: transmitting the uplink transmission according to the first SRS unit comprises transmitting the uplink transmission according to a TPMI associated with the first SRS unit; and / or transmitting the uplink transmission according to the second SRS unit comprises transmitting the uplink transmission according to a TPMI associated with the second SRS unit.

[0165] 8. The method of any of examples 1-8, wherein: transmitting the uplink transmission according to the first SRS unit comprises transmitting the uplink transmission according to an SRI associated with the first SRS unit; and / or transmitting the uplink transmission according to the second SRS unit comprises transmitting the uplink transmission according to an SRI associated with the second SRS unit.

[0166] 9. The method of any of examples 1-8, wherein the first SRS unit comprises a first SRS resource set and the second SRS unit comprises a second SRS resource set.(E.g., the SRS unit pair corresponds to an SRS resource set pair).

[0167] 10. The method of example 9, wherein the indication indicating the configuration of the SRS unit pair (e.g., the SRS resource set pair) is received in an SRSI field in DCI.

[0168] 11. The method of example 10, further comprising determining the SRS unit pair (e.g., SRS resource set pair) according to a value of the SRSI field.

[0169] 12. The method of any of examples 1-8, wherein the first SRS unit comprise a first SRS resource and the second SRS unit comprises a second SRS resource. (E.g., the SRS unit pair corresponds to an SRS resource pair).

[0170] 13. The method of example 12, wherein the indication indicating the configuration of the SRS unit pair (e.g., the SRS resource pair) is received in an SRS resource indicator (SRI) field in DCI.

[0171] 14. The method of example 13, further comprising determining the SRS unit pair (e.g., SRS resource pair) according to a value of the SRI field.

[0172] 15. The method of any of examples 1-14, further comprising: receiving signaling based on which the UE 112 determines the first symbol type to associate with the first SRS unit and / or the second symbol type to associate with the second SRS unit.

[0173] 16. The method of any of examples 1-15, wherein prior to transmitting the uplink transmission, the method further comprises selecting an SRS unit of the SRS unit pair for the uplink transmission, wherein: the first SRS unit is selected when the uplink transmission corresponds to the first symbol type; and the second SRS unit selected when the uplink transmission corresponds to the second symbol type.

[0174] 17. The method of any of examples 1-16, wherein prior to transmitting the uplink transmission, the method further comprises determining a symbol type to use for an uplink transmission, wherein: the first symbol type is determined as the symbol type for the uplink transmission when the uplink transmission occurs in one or more of the symbols associated with the first symbol type; and the second symbol type is determinedas the symbol type for the uplink transmission when the uplink transmission occurs in one or more of the symbols associated with the second symbol type.

[0175] 18. The method of any of examples 1-17, wherein the indication indicates the configuration of multiple SRS unit pairs.

[0176] 19. The method of any of examples 1-18, wherein the indication implicitly indicates the pairing of the SRS unit pair.

[0177] 20. The method of any of examples 1-18, wherein the indication explicitly indicates the pairing of the SRS unit pair.

[0178] 21. The method of any of examples 1-20, wherein the uplink transmission comprises a codebook-based transmission.

[0179] 22. The method of any of examples 1-21, wherein the uplink transmission comprises a noncodebook-based transmission.

[0180] 23. The method of any of examples 1-22, wherein the indication is received from a network node. (The indication may be received in any suitable signaling, such as RRC, MAC CE, DCI, dedicated signaling, broadcast signaling (e.g., SIB), etc.)

[0181] 24. The method of any of examples 1-23, further comprising any of the additional features of the described solution. (Including, e.g., any of the features described in paragraphs

[0056] -

[0088] , Fig. 13, and / or Fig. 14.)

[0182] Group B Examples

[0183] 25. A method of SRS configuration by a network node 110, the method comprising: sending (1602), to a UE 112, an indication indicating a configuration of an SRS unit pair, the SRS unit pair comprising a first SRS unit associated with symbols of a first symbol type and a second SRS unit associated with symbols of a second symbol type; and receiving (1604) an uplink transmission from the UE 112, wherein the uplink transmission is received according to the first SRS unit when the uplink transmission occurs in one or more of the symbols associated with the first symbol type, and wherein the uplink transmission is received according to the second SRS unit when the uplink transmission occurs in one or more of the symbols associated with the second symbol type.

[0184] 26. The method of example 25, wherein the symbols of the second symbol type associated with the second SRS unit are non-overlapping with the symbols of the first symbol type associated with the first SRS unit.

[0185] 27. The method of any of examples 25-26, wherein the symbols of the first symbol type and the symbols of the second symbol type are each OFDM symbols.

[0186] 28. The method of any of examples 25-27, wherein: the first symbol type comprises a symbol for which at least one uplink and one downlink subband is configured to the UE 112; and the second symbol type comprises a symbol for which an uplink transmission without a downlink subband is configured to the UE 112.

[0187] 29. The method of any of examples 25-28, wherein the first symbol type corresponds to SBFD and the second symbol type corresponds to non-SBFD.

[0188] 30. The method of any of examples 25-29, wherein the uplink transmission comprises an SRS and / or a PUSCH.

[0189] 31. The method of any of examples 25-30, wherein: receiving the uplink transmission according to the first SRS unit comprises receiving the uplink transmission according to a TPMI associated with the first SRS unit; and / or receiving the uplink transmission according to the second SRS unit comprises receiving the uplink transmission according to a TPMI associated with the second SRS unit.

[0190] 32. The method of any of examples 25-31, wherein: receiving the uplink transmission according to the first SRS unit comprises receiving the uplink transmission according to an SRI associated with the first SRS unit; and / or receiving the uplink transmission according to the second SRS unit comprises receiving the uplink transmission according to an SRI associated with the second SRS unit.

[0191] 33. The method of any of examples 25-32, wherein the first SRS unit comprises a first SRS resource set and the second SRS unit comprises a second SRS resource set. (E.g., the SRS unit pair corresponds to an SRS resource set pair).

[0192] 34. The method of example 33, wherein the indication indicating the configuration of the SRS unit pair (e.g., the SRS resource set pair) is sent in an SRS resource set indicator (SRSI) field in DCI.

[0193] 35. The method of example 34, wherein a value of the SRSI field facilitates the UE in determining the SRS unit pair (e.g., SRS resource set pair).

[0194] 36. The method of any of examples 25-32, wherein the first SRS unit comprise a first SRS resource and the second SRS unit comprises a second SRS resource. (E.g., the SRS unit pair corresponds to an SRS resource pair).

[0195] 37. The method of example 36, wherein the indication indicating the configuration of the SRS unit pair (e.g., the SRS resource pair) is sent in an SRS resource indicator (SRI) field in DCI.

[0196] 38. The method of example 37, wherein a value of the SRI field facilitates theUE in determining the SRS unit pair (e.g., SRS resource pair).

[0197] 39. The method of any of examples 25-38, further comprising: sending signaling based on which the UE determines the first symbol type to associate with the first SRS unit and / or the second symbol type to associate with the second SRS unit.

[0198] 40. The method of any of examples 25-39, wherein prior to sending the indication, the method further comprises determining to pair the first SRS unit and the second SRS unit in the SRS unit pair.

[0199] 41. The method of any of examples 25-40, the method comprising sending one or more of the following to the UE 112: a TPMI associated with the first SRS unit; a TPMI associated with the second SRS unit; an SRI associated with the first SRS unit; an SRI associated with the second SRS unit; an SRSI associated with the first SRS unit; and / or an SRSI associated with the second SRS unit;

[0200] 42. The method of any of examples 25-41, wherein the indication indicates the configuration of multiple SRS unit pairs.

[0201] 43. The method of any of examples 25-42, wherein the indication implicitly indicates the pairing of the SRS unit pair.

[0202] 44. The method of any of examples 25-42, wherein the indication explicitly indicates the pairing of the SRS unit pair.

[0203] 45. The method of any of examples 25-44, wherein the uplink transmission comprises a codebook-based transmission.

[0204] 46. The method of any of examples 25-45, wherein the uplink transmission comprises a noncodebook-based transmission.

[0205] 47. The method of any of examples 25-46, wherein the indication is sent in signaling, comprising RRC signaling, MAC CE signaling, DCI, dedicated signaling, and / or broadcast signaling.

[0206] 48. The method of any of examples 25-47, further comprising any of the additional features of the described solution. (Including, e.g., any of the features described in paragraphs

[0056] -

[0088] , Fig. 13, and / or Fig. 14.)

[0207] Group C Embodiments

[0208] 49. A UE 112, comprising: processing circuitry configured to perform any of the steps of any of the Group A examples; and power supply circuitry configured to supply power to the processing circuitry.

[0209] 50. A network node 110, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B examples; power supply circuitry configured to supply power to the processing circuitry.

[0210] 51. A UE 112 comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A examples; an input interface connected to the processing circuitry and configured to allow input of information into the UE 112 to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE 112 that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

[0211] Figure 19 shows an example of a communication system 100 in accordance with some embodiments.

[0212] In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 102, including one or more network nodes 110 and / or core network nodes 108.

[0213] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near- real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or anycombination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O- RAN Alliance or comparable technologies. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0214] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0215] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0216] In the depicted example, the core network 106 connects the network nodes 110 to one or more host computing systems, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples,network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Deconcealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0217] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0218] As a whole, the communication system 100 of Figure 19 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0219] In some examples, the telecommunication network 102 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to differentdevices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0220] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi -RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0221] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0222] The hub 114 may have a constant / persi stent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication schemeand / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In other embodiments, the hub 114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0223] Figure 20 shows a UE 200 in accordance with some embodiments. The UE 200 presents additional details of some embodiments of the UE 112 of Figure 1. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0224] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehi cl e-to- vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is notintended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0225] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 20. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0226] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0227] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0228] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0229] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0230] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual inline memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.

[0231] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0232] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0233] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0234] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node viaa wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0235] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 200 shown in Figure 20.

[0236] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0237] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling anactuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0238] Figure 21 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, 0-DU, O-CU).

[0239] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an 0-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0240] Other examples of network nodes include multiple transmission point (multi- TRP) 5G access nodes, multi -standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0241] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0242] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0243] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0244] The memory 304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device- readable and / or computer-executable memory devices that store information, data, and / orinstructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0245] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio frontend circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0246] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0247] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0248] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0249] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0250] Embodiments of the network node 300 may include additional components beyond those shown in Figure 21 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300. In some embodiments providing a core network node, such as corenetwork node 108 of Figure 19, some components, such as the radio front-end circuitry 318 and the RF transceiver circuitry 312 may be omitted.

[0251] Figure 22 is a block diagram illustrating a virtualization environment 400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0252] Applications 402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0253] Hardware 404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 408a and 408b (one or more of which may be generally referred to as VMs 408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 406 may present a virtual operating platform that appears like networking hardware to the VMs 408.

[0254] The VMs 408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 406. Different embodiments of the instance of a virtual appliance 402 may be implemented on one or more of VMs 408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0255] In the context of NFV, a VM 408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine. Each of the VMs 408, and that part of hardware 404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 408 on top of the hardware 404 and corresponds to the application 402.

[0256] Hardware 404 may be implemented in a standalone network node with generic or specific components. Hardware 404 may implement some functions via virtualization. Alternatively, hardware 404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 410, which, among others, oversees lifecycle management of applications 402. In some embodiments, hardware 404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 412 which may alternatively be used for communication between hardware nodes and radio units.

[0257] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations describedherein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0258] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0259] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

1. What is claimed is:

1. A method performed by a user equipment, UE, (112) for communicating with a network node in a wireless communication system employing subband full duplex, SBFD, operation, the method comprising: receiving (1702) information indicating a configuration of a pair of sounding reference signal, SRS, resource sets, the pair of SRS resource sets comprising a first SRS resource set and a second SRS resource set, the first SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to SBFD symbols and the second SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to non-SBFD symbols; receiving (1704) information for a physical uplink shared channel, PUSCH, transmission, the information for the PUSCH transmission indicating symbols for the PUSCH transmission; selecting (1706) a selected SRS resource based on a symbol type associated with the symbols for the PUSCH transmission, the selected SRS resource selected from the first SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for SBFD, the selected SRS resource selected from the second SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for non-SBFD; and transmitting (1708) the PUSCH transmission according to the selected SRS resource.

2. The method of claim 1, the selecting of the selected SRS resource in the first SRS resource set or the second SRS resource set further based on an SRS resource identifier, SRI, received in the information for the PUSCH transmission.

3. The method of any of claims 1-2, the information for the PUSCH transmission received at least in part via downlink control information, DCI.

4. The method of any of claims 1-3, the information for the PUSCH transmission received at least in part via radio resource control, RRC, signaling.

5. The method of any of claims 1-4, wherein the SBFD symbols associated withthe one or more SRS resources of the first SRS resource set are non-overlapping with the non-SBFD symbols associated with the one or more SRS resources of the second SRS resource set.

6. The method of any of claims 1-5, wherein transmitting the PUSCH transmission according to the selected SRS resource is further based on a transmission precoding matrix indicator, TPMI, received in the information for the PUSCH transmission.

7. The method of any of claims 1-6, wherein the configuration of the pair of SRS resource sets comprises a symbol type parameter configured to SBFD for the one or more SRS resources of the first SRS resource set and a symbol type parameter configured to non-SBFD for the one or more SRS resources of the second resource set.

8. The method of any of claims 1-7, wherein the first SRS resource set includes a same number of SRS resources and a same number of SRS ports as the second SRS resource set.

9. The method of any of claims 1-8, the pair of SRS resource sets configured for either codebook usage or non-codebook usage.

10. The method of any of claims 1-9, wherein the information for the PUSCH transmission indicates a multi-slot PUSCH transmission.

11. The method of claim 10, wherein the selecting of the selected SRS resource comprises one or more of: selecting from the first SRS resource set for a transmission occasion of the multislot PUSCH transmission for which an associated symbol type corresponds to the symbols for SBFD; and selecting from the second SRS resource set for a transmission occasion of the multi-slot PUSCH transmission for which an associated symbol type corresponds to the symbols for non-SBFD.

12. The method of claim 11, wherein a same SRI received in the information forthe PUSCH transmission applies for: transmitting the multi-slot PUSCH transmission in the transmission occasion for which the associated symbol type corresponds to the symbols for SBFD; and transmitting the multi-slot PUSCH transmission in the transmission occasion for which the associated symbol type corresponds to the symbols for non-SBFD.

13. The method of any of claims 11-12, wherein a same TPMI received in the information for the PUSCH transmission applies for: transmitting the multi-slot PUSCH transmission in the transmission occasion for which the associated symbol type corresponds to the symbols for SBFD; and transmitting the multi-slot PUSCH transmission in the transmission occasion for which the associated symbol type corresponds to the symbols for non-SBFD.

14. The method of any of claims 1-13, further comprising: receiving information indicating a configuration of another pair of SRS resource sets.

15. The method of claim 14, wherein a Transmission Configuration Indicator, TCI, state configuration is the same across all SRS resource sets in a same SRS resource set pair.

16. The method of any of claims 1-15, the pair of SRS resource sets being configured for communicating with a first transmission and reception point, TRP, and another pair of SRS resource sets being configured for communicating with a second TRP.

17. The method of any of claims 1-16, further comprising: determining to select one or more SRS resources for the PUSCH transmission from the pair of SRS resource sets, another pair of SRS resource sets, or both according to an SRS resource set indicator, SRSI, received in the information for the PUSCH transmission.

18. The method of claim 17, wherein, in response to determining to select from both pairs of SRS resource sets, the transmitting of the PUSCH transmission comprises transmitting according to SRS resources from both pairs of SRS resource sets.

19. A user equipment, UE, (112) configured for communicating with a network node in a wireless communication system employing subband full duplex, SBFD, operation, the UE (112) comprising processing circuitry (202) configured to: receive information indicating a configuration of a pair of sounding reference signal, SRS, resource sets, the pair of SRS resource sets comprising a first SRS resource set and a second SRS resource set, the first SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to SBFD symbols and the second SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to non-SBFD symbols; receive information for a physical uplink shared channel, PUSCH, transmission, the information for the PUSCH transmission indicating symbols for the PUSCH transmission; select a selected SRS resource based on a symbol type associated with the symbols for the PUSCH transmission, the selected SRS resource selected from the first SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for SBFD, the selected SRS resource selected from the second SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for non-SBFD; and transmit the PUSCH transmission according to the selected SRS resource.

20. The UE (112) of claim 19, the selecting of the selected SRS resource in the first SRS resource set or the second SRS resource set further based on an SRS resource identifier, SRI, received in the information for the PUSCH transmission.

21. The UE (112) of any of claims 19-20, the information for the PUSCH transmission received at least in part via downlink control information, DCI.

22. The UE (112) of any of claims 19-21, the information for the PUSCH transmission received at least in part via radio resource control, RRC, signaling.

23. The UE (112) of any of claims 19-22, wherein the SBFD symbols associated with the one or more SRS resources of the first SRS resource set are non-overlapping with the non-SBFD symbols associated with the one or more SRS resources of the second SRSresource set.

24. The UE (112) of any of claims 19-23, wherein transmitting the PUSCH transmission according to the selected SRS resource is further based on a transmission precoding matrix indicator, TPMI, received in the information for the PUSCH transmission.

25. The UE (112) of any of claims 19-24, wherein the configuration of the pair of SRS resource sets comprises a symbol type parameter configured to SBFD for the one or more SRS resources of the first SRS resource set and a symbol type parameter configured to non- SBFD for the one or more SRS resources of the second resource set.

26. The UE (112) of any of claims 19-25, wherein the first SRS resource set includes a same number of SRS resources and a same number of SRS ports as the second SRS resource set.

27. The UE (112) of any of claims 19-26, the pair of SRS resource sets configured for either codebook usage or non-codebook usage.

28. The UE (112) of any of claims 19-27, wherein the information for the PUSCH transmission indicates a multi-slot PUSCH transmission.

29. The UE (112) of claim 28, wherein the selecting of the selected SRS resource comprises one or more of: selecting from the first SRS resource set for a transmission occasion of the multislot PUSCH transmission for which an associated symbol type corresponds to the symbols for SBFD; and selecting from the second SRS resource set for a transmission occasion of the multi-slot PUSCH transmission for which an associated symbol type corresponds to the symbols for non-SBFD.

30. The UE (112) of claim 29, wherein a same SRI received in the information for the PUSCH transmission applies for: transmitting the multi-slot PUSCH transmission in the transmission occasion forwhich the associated symbol type corresponds to the symbols for SBFD; and transmitting the multi-slot PUSCH transmission in the transmission occasion for which the associated symbol type corresponds to the symbols for non-SBFD.

31. The UE (112) of any of claims 29-30, wherein a same TPMI received in the information for the PUSCH transmission applies for: transmitting the multi-slot PUSCH transmission in the transmission occasion for which the associated symbol type corresponds to the symbols for SBFD; and transmitting the multi-slot PUSCH transmission in the transmission occasion for which the associated symbol type corresponds to the symbols for non-SBFD.

32. The UE (112) of any of claims 19-31, wherein the processing circuitry (202) is further configured to: receive information indicating a configuration of another pair of SRS resource sets.

33. The UE (112) of claim 32, wherein a Transmission Configuration Indicator, TCI, state configuration is the same across all SRS resource sets in a same SRS resource set pair.

34. The UE (112) of any of claims 19-33, the pair of SRS resource sets being configured for communicating with a first transmission and reception point, TRP, and another pair of SRS resource sets being configured for communicating with a second TRP.

35. The UE (112) of any of claims 19-34, wherein the processing circuitry (202) is further configured to determine to select one or more SRS resources for the PUSCH transmission from the pair of SRS resource sets, another pair of SRS resource sets, or both according to an SRS resource set indicator, SRSI, received in the information for the PUSCH transmission.

36. The UE (112) of claim 35, wherein, in response to determining to select from both pairs of SRS resource sets, the transmitting of the PUSCH transmission comprises transmitting according to SRS resources from both pairs of SRS resource sets.

37. A method performed by a network node (110) for communicating with a userequipment, UE, (112) in a wireless communication system employing subband full duplex, SBFD, operation, the method comprising: transmitting (1802), to the UE (112), information indicating a configuration of a pair of sounding reference signal, SRS, resource sets, the pair of SRS resource sets comprising a first SRS resource set and a second SRS resource set, the first SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to SBFD symbols and the second SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to non-SBFD symbols; transmitting (1804), to the UE (112), information for a physical uplink shared channel, PUSCH, transmission, the information for the PUSCH transmission indicating symbols for the PUSCH transmission; and receiving (1806) the PUSCH transmission according to a selected SRS resource, the selected SRS resource selected from the first SRS resource set when a symbol type associated with symbols for the PUSCH transmission corresponds to symbols for SBFD, the selected SRS resource selected from the second SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for non-SBFD.

38. The method of claim 37, wherein the information for the PUSCH transmission comprises an SRS resource identifier, SRI, used in selecting the selected SRS resource in the first SRS resource set or the second SRS resource set.

39. The method of any of claims 37-38, the information for the PUSCH transmission transmitted at least in part via downlink control information, DCI.

40. The method of any of claims 37-39, the information for the PUSCH transmission transmitted at least in part via radio resource control, RRC, signaling.

41. The method of any of claims 37-40, wherein the SBFD symbols associated with the one or more SRS resources of the first SRS resource set are non-overlapping with the non-SBFD symbols associated with the one or more SRS resources of the second SRS resource set.

42. The method of any of claims 37-41, wherein the information for the PUSCHtransmission further comprises a transmission precoding matrix indicator, TPMI.

43. The method of any of claims 37-42, wherein the configuration of the pair of SRS resource sets comprises a symbol type parameter configured to SBFD for the one or more SRS resources of the first SRS resource set and a symbol type parameter configured to non- SBFD for the one or more SRS resources of the second resource set.

44. The method of any of claims 37-43, wherein the first SRS resource set includes a same number of SRS resources and a same number of SRS ports as the second SRS resource set.

45. The method of any of claims 37-44, the pair of SRS resource sets configured for either codebook usage or non-codebook usage.

46. The method of any of claims 37-45, wherein the information for the PUSCH transmission indicates a multi-slot PUSCH transmission.

47. The method of claim 46, wherein selecting of the selected SRS resource comprises one or more of: selecting from the first SRS resource set for a transmission occasion of the multislot PUSCH transmission for which an associated symbol type corresponds to the symbols for SBFD; and selecting from the second SRS resource set for a transmission occasion of the multi-slot PUSCH transmission for which an associated symbol type corresponds to the symbols for non-SBFD.

48. The method of claim 47, wherein a same SRI sent in the information for the PUSCH transmission applies for: the transmission occasion of the multi-slot PUSCH transmission for which the associated symbol type corresponds to the symbols for SBFD; and the transmission occasion of the multi-slot PUSCH transmission for which the associated symbol type corresponds to the symbols for non-SBFD.

49. The method of any of claims 47-48, wherein a same TPMI sent in theinformation for the PUSCH transmission applies for: the transmission occasion of the multi-slot PUSCH transmission for which the associated symbol type corresponds to the symbols for SBFD; and the transmission occasion of the multi-slot PUSCH transmission for which the associated symbol type corresponds to the symbols for non-SBFD.

50. The method of any of claims 37-49, further comprising: transmitting information indicating a configuration of another pair of SRS resource sets.

51. The method of claim 50, wherein a Transmission Configuration Indicator, TCI, state configuration is the same across all SRS resource sets in a same SRS resource set pair.

52. The method of any of claims 37-51, the pair of SRS resource sets being configured for communicating with a first transmission and reception point, TRP, and another pair of SRS resource sets being configured for communicating with a second TRP.

53. The method of any of claims 37-52, wherein the information for the PUSCH transmission further comprises an SRS resource set indicator, SRSI, based on which the UE (112) determines to select one or more SRS resources for the PUSCH transmission from the pair of SRS resource sets, another pair of SRS resource sets, or both.

54. The method of claim 53, wherein, in response to the UE’s determining to select from both pairs of SRS resource sets, the receiving of the PUSCH transmission comprises receiving according to SRS resources from both pairs of SRS resource sets.

55. A network node (110) configured for communicating with a user equipment, UE, (112) in a wireless communication system employing subband full duplex, SBFD, operation, the network node (110) comprising processing circuitry (302) configured to: transmit, to the UE (112), information indicating a configuration of a pair of sounding reference signal, SRS, resource sets, the pair of SRS resource sets comprising a first SRS resource set and a second SRS resource set, the first SRS resource set comprising one or more SRS resources associated with a symbol type corresponding toSBFD symbols and the second SRS resource set comprising one or more SRS resources associated with a symbol type corresponding to non-SBFD symbols; transmit, to the UE (112), information for a physical uplink shared channel, PUSCH, transmission, the information for the PUSCH transmission indicating symbols for the PUSCH transmission; and receive the PUSCH transmission according to a selected SRS resource, the selected SRS resource selected from the first SRS resource set when a symbol type associated with symbols for the PUSCH transmission corresponds to symbols for SBFD, the selected SRS resource selected from the second SRS resource set when the symbol type associated with the symbols for the PUSCH transmission corresponds to symbols for non-SBFD.

56. The network node (110) of claim 55, wherein the information for the PUSCH transmission comprises an SRS resource identifier, SRI, used in selecting the selected SRS resource in the first SRS resource set or the second SRS resource set.

57. The network node (110) of any of claims 55-56, the information for the PUSCH transmission transmitted at least in part via downlink control information, DCI.

58. The network node (110) of any of claims 55-57, the information for the PUSCH transmission transmitted at least in part via radio resource control, RRC, signaling.

59. The network node (110) of any of claims 55-58, wherein the SBFD symbols associated with the one or more SRS resources of the first SRS resource set are nonoverlapping with the non-SBFD symbols associated with the one or more SRS resources of the second SRS resource set.

60. The network node (110) of any of claims 55-59, wherein the information for the PUSCH transmission further comprises a transmission precoding matrix indicator, TPMI.

61. The network node (110) of any of claims 55-60, wherein the configuration of the pair of SRS resource sets comprises a symbol type parameter configured to SBFD for the one or more SRS resources of the first SRS resource set and a symbol type parameterconfigured to non-SBFD for the one or more SRS resources of the second resource set.

62. The network node (110) of any of claims 55-61, wherein the first SRS resource set includes a same number of SRS resources and a same number of SRS ports as the second SRS resource set.

63. The network node (110) of any of claims 55-62, the pair of SRS resource sets configured for either codebook usage or non-codebook usage.

64. The network node (110) of any of claims 55-63, wherein the information for the PUSCH transmission indicates a multi-slot PUSCH transmission.

65. The network node (110) of claim 64, wherein selecting of the selected SRS resource comprises one or more of selecting from the first SRS resource set for a transmission occasion of the multislot PUSCH transmission for which an associated symbol type corresponds to the symbols for SBFD; and selecting from the second SRS resource set for a transmission occasion of the multi-slot PUSCH transmission for which an associated symbol type corresponds to the symbols for non-SBFD.

66. The network node (110) of claim 65, wherein a same SRI sent in the information for the PUSCH transmission applies for: the transmission occasion of the multi-slot PUSCH transmission for which the associated symbol type corresponds to the symbols for SBFD; and the transmission occasion of the multi-slot PUSCH transmission for which the associated symbol type corresponds to the symbols for non-SBFD.

67. The network node (110) of any of claims 65-66, wherein a same TPMI sent in the information for the PUSCH transmission applies for: the transmission occasion of the multi-slot PUSCH transmission for which the associated symbol type corresponds to the symbols for SBFD; and the transmission occasion of the multi-slot PUSCH transmission for which the associated symbol type corresponds to the symbols for non-SBFD.

68. The network node (110) of any of claims 55-67, wherein the processing circuitry (302) is further configured to: transmit information indicating a configuration of another pair of SRS resource sets.

69. The network node (110) of claim 68, wherein a Transmission Configuration Indicator, TCI, state configuration is the same across all SRS resource sets in a same SRS resource set pair.

70. The network node (110) of any of claims 55-69, the pair of SRS resource sets being configured for communicating with a first transmission and reception point, TRP, and another pair of SRS resource sets being configured for communicating with a second TRP.

71. The network node (110) of any of claims 55-70, wherein the information for the PUSCH transmission further comprises an SRS resource set indicator, SRSI, based on which the UE determines the pair of SRS resource sets, another pair of SRS resource sets, or both.

Images