Beam management for shared physical uplink channels in high-density deployments

Abstract

A user equipment (UE) in a wireless network may receive downlink control information (DCI) scheduling a physical uplink shared channel (PUSCH) for non-codebook-based and / or codebook-based PUSCH operation. The UE may be configured with sounding reference signal (SRS) resources set for each codebook-based operation and non-codebook-based operation. The UE may transmit using codebook-based operation in a first set of PUSCH opportunities and transmit using non-codebook-based operation in a second set of PUSCH opportunities. The DCI may include multiple SRS resource indicator (SRI) fields associated with different sets of PUSCH opportunities. Similarly, the DCI may include information related to several layers for precoding for the set of PUSCH opportunities.

Description

[Technical Field]

[0001] [Cross-reference of related applications] This application claims the interests of U.S. Provisional Patent Application No. 63 / 038,174, filed on 12 June 2020, entitled "Beam management for physical uplink shared channels in dense deployments," the contents of which are incorporated herein by reference. [Background technology]

[0002] This disclosure relates to mobile device communications as described in version 16 of the March 2020 release of 3GPP TS38.211, TS38.212, TS38.213, TS38.214, TS38.321, TS38.331, and TS38.306, but is not limited to these. [Overview of the Initiative] [Problems that the invention aims to solve]

[0003] For example, dynamically switching between codebook-based and non-codebook-based UL transmissions for SRS and PUSCH can be beneficial in various scenarios. An exemplary scenario is a cell with ULs served by a TRP and RP. UL transmissions to the TRP may operate most efficiently using non-codebook-based operation, while UL transmissions to the RP may operate most efficiently using codebook-based operation. [Means for solving the problem]

[0004] Various solutions have been proposed to efficiently operate the dynamic switching between codebook-based and non-codebook-based UL in the UL bandwidth portion of a serving cell.

[0005] In some cases, the UE may be configured with one set of SRS resources for codebook-based behavior and one set of SRS resources for non-codebook-based behavior. In other cases, the UE may be configured with a set of SRS resources for mixed behavior, for example, an enhanced SRS resource set for codebook-based behavior.

[0006] Solutions have been proposed for DCI-based dynamic switching between codebook-based and non-codebook-based operation, including solutions that do not require any additional or modified DCI fields compared to legacy codebook-based operation modes. The DCI may include SRS resource indicator fields. In some solutions, the indicated SRS resource may also indicate the operation mode.

[0007] For example, if a multi-port SRS resource is specified, legacy codebook-based operation is assumed, and the precoder information and layer count fields are interpreted as they are. On the other hand, if a single-port SRS resource is specified, non-codebook-based operation is assumed, and the precoder information and layer count fields are reinterpreted as SRS resource indicators that support non-codebook-based operation.

[0008] PUSCH repetition is an important tool for improving reliability. Various solutions for codebook-based and non-codebook-based submissions across PUSCH opportunities are discussed.

[0009] In scenarios where a UE operates both DL-based UL, e.g., non-codebook-based operation, and SRS-based UL for beam management, e.g., codebook-based operation, it may be possible to reduce the amount of SRS required for beam management. This can improve UL resource efficiency and reduce UL interference and UE power consumption. Various solutions propose concentrating SRS transmissions for beam management on directions / panels / beams not covered by DL-based UL operation.

Advantages of the Invention

[0010] This summary is provided to introduce, in a simplified form, a selection of concepts that are further described in the following detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Further, the claimed subject matter is not limited to embodiments that solve any or all disadvantages noted in any part of this disclosure.

[0011] A more detailed understanding can be obtained from the following description, given by way of example in conjunction with the accompanying drawings.

Brief Description of the Drawings

[0012] [Figure 1A] FIG. 1A illustrates exemplary points in the context of TRP and RP. [Figure 1B] FIG. 1B illustrates exemplary points in the context of TRP and RP. [Figure 1C] FIG. 1C illustrates exemplary points in the context of TRP and RP. [Figure 2] FIG. 2 illustrates an exemplary cell having DL transmission at one TRP and UL reception at three points. [Figure 3] FIG. 3 illustrates two exemplary cells each served by a plurality of points. [Figure 4] FIG. 4 illustrates an example of two cells, where cell A is served by a plurality of points and cell B is served by a single TRP. [Figure 5] FIG. 5 illustrates an example of a site serving two cells in two frequency layers. [Figure 6] FIG. 6 illustrates an example where TPR1 serves cell A on frequency layer f1 and RP1 serves cell B on frequency layer f2. [Figure 7A]Figure 7A illustrates an example of DL-based UL beam management for NCBB PUSCH. [Figure 7B] Figure 7B illustrates an example of DL-based UL beam management for NCBB PUSCH. [Figure 8] Figure 8 illustrates an example of a partially DL-based UL operation that uses CBB operation. [Figure 9] Figure 9 illustrates an example of a method for obtaining Z. [Figure 10] Figure 10 is a flowchart of the procedure for dynamically selecting CBB or NCBB operation using the DCI field in legacy DCI for PUSCH scheduling. [Figure 11] Figure 11 is an illustrative repetition timing diagram for PUSCH. [Figure 12] Figure 12 illustrates an example of a panel ID indicator P within MAC CE for, in this case, aperiodic or semi-permanent SRS activation / deactivation. [Figure 13] Figure 13 illustrates an example of a negative spatial relationship. [Figure 14] Figure 14 illustrates an exemplary scenario in which an SRS for a BM transmitted from one panel is present, in the direction of the RP in this case. [Figure 15A] Figure 15A illustrates an exemplary communication system in which the methods and apparatus described and claimed herein may be embodied. [Figure 15B] Figure 15B is a block diagram of an exemplary apparatus or device configured for wireless communication. [Figure 15C] Figure 15C is an illustrative system diagram of a radio access network (RAN) and core network. [Figure 15D] Figure 15D is a system diagram of another exemplary RAN and core network. [Figure 15E] Figure 15E is a system diagram of another exemplary RAN and core network. [Figure 15F]Figure 15F is a block diagram of an exemplary computing system. [Figure 15G] Figure 15G is a block diagram of another exemplary communication system. [Modes for carrying out the invention]

[0013] For explanations of many of the abbreviations used in this specification, please refer to Table 7 in Appendix 2.

[0014] [Rx / Tx beam compatible - DL-based UL] Consider UEs with Rx / Tx beam compatibility (simply put, beam compatibility), such as UEs that can derive a UL Tx beam from a DL Rx beam.

[0015] In such a UE, an efficient mode of UL beam management is to have the UE derive the UL Tx beam for UL transmission from the DL Rx beam used to receive DL RS. Such a mode of operation is referred to herein as “DL-based UL”.

[0016] DL-based UL can avoid UE transmissions of SRS for beam management, such as beam sweeping transmissions of SRS.

[0017] A further requirement for beam-compatible DL-based UL is, for example, radio channel reciprocity, meaning that the radio propagation in DL and UL is sufficiently similar. This is often achieved in TDD systems where DL and UL use (at least almost) the same frequencies but are time-multiplexed. Some effects induced by transmitter and / or receiver hardware, such as antennas, cables, filters, etc., may be included in the radio channel in the context of reciprocity. Sufficient radio channel reciprocity may also be possible if DL and UL transmissions occur at different frequencies, provided that the frequency separation is not too great. For example, channel reciprocity within a frequency band may be achievable.

[0018] [Scenario with transmitting and receiving points (TRP) and receiving point (RP)] This specification considers wireless communication between one or more UEs and a network. For example, a network in the vicinity of a particular UE may include transmit and receive points (TRPs) and / or receive points (RPs). TRPs / RPs may be referred to as “distributed antenna systems” (DAS) or “remote radio heads” (RRHs) in various contexts.

[0019] A TRP transmits signals and / or channels to one or more UEs, commonly referred to as downlinks (DLs), and receives signals and / or channels from one or more UEs, commonly referred to as uplinks (ULs). In some cases, a TRP may act as a UE, for example, when acting as a relay, where the TRP acts as a UE and interacts with another node that receives DL data to be relayed to the UE, or the TRP may act as a UE and relay UL data received from the UE to a base station.

[0020] The RP receives signals and / or channels from one or more UEs (ULs). In the context of TRP and RP, different points can be geographically separated (see Figure 1(a) below). In some cases, different points may be located in nearly the same geographical location but separated in some other way, for example, the boresight of the antenna (or antenna element) at point 1 may be significantly different from the boresight of the antenna at point 2.

[0021] The latter example is a cellular communications site that uses different antenna sets to serve multiple sectors in different directions. In this case, different sets of antennas serving different sectors in different directions from the site can be considered different points. This is illustrated in Figure 1(b).

[0022] In some cases, the antennas are arranged on one or more panels, and the panels comprise rectangular panels having N × M antennas, as illustrated in Figure 1(c) below. In some cases, all or a subset of the antennas on a panel are connected to the same transmitter-and-receiver (TRX) chain or the same receiver (RX) chain. In some cases, the antennas on different panels are connected to different transmitter-and-receiver (TRX) chains or different receiver (RX) chains. In some cases, different panels, which may or may not be located at the same geographical location, may correspond to different points. In other cases, different panels may correspond to the same point.

[0023] Figures 1A to 1C illustrate exemplary points in the context of TRP and RP. (a) shows two geographically separated points, a TRP and an RP, near a UE. (b) shows two TRPs at nearly the same geographical location, in the form of two antennas (indicated as "Ant" in the figure) mounted on the same site, but with significantly different primary transmit / receive directions (boresights). (c) shows two panels, each associated with a point, each comprising a rectangular array of cross-polarized antenna elements (in the form of "X" in the figure). In this example, each panel is connected to a different TRX chain.

[0024] In some cases, a point may operate on multiple frequencies, for example, two frequencies. However, in some cases, a site located at a geographical location with specific transmit / receive directions at multiple frequencies (e.g., including one antenna, antenna array, panel, or subset of antennas per frequency) may be counted as multiple points, at least from the perspective of the UE. One reason may be that radio signal propagation characteristics differ at different frequencies. Another reason may be that network-side hardware, such as different oscillators, calibration hardware for beam alignment, or phase shifters for beamforming, may result in signal transmission and / or reception differences at different frequencies.

[0025] Signals / channels received at the TRP / RP may undergo further processing, such as filtering, amplification, downconversion, analog-to-digital conversion (sampling), digital signal processing, demodulation, and channel decoding. Signals / channels transmitted at the TRP may have undergone various processing before transmission, such as filtering, amplification, peak-to-average power reduction, upconversion, D / A conversion, digital signal processing, modulation, and channel coding. A subset of these operations for reception / transmission (e.g., none, some, or all) may be performed at the TRP / RP, while other operations may be performed at one or more other locations connected to the TRP / RP via fronthaul or backhaul links, such as optical fiber, copper wire, or over-the-air. In a centralized RAN (CRAN) implementation, signal processing at multiple points is performed at a centralized location.

[0026] [TRP and RP operating in the same frequency layer] In some scenarios, the TRP and / or RP operate on the same frequency layer, which may correspond to the carrier frequency and bandwidth, frequency band, or frequency range. This could mean that signals transmitted by the UE on the frequency layer can be received by these points (e.g., TRP and / or RP), provided that these points are in the vicinity of the UE.

[0027] In a cellular system, a point can service one or more cells on the frequency layer. A TRP serving a cell may mean that the TRP transmits signals associated with the cell, such as SSB, system information, etc. A point serving a cell, such as an RP, may mean that the point receives signals associated with the cell. In some cases, a point serves a single cell on the frequency layer. In some cases, a point serves multiple cells on the frequency layer. In some cases, as illustrated in Figure 4, a point may serve as a TRP for a first cell and also serve as an RP for a second cell on the same frequency layer.

[0028] In some cases, multiple points serve a first cell, and in some cases, one or more of these points also serve a second cell on the same frequency layer.

[0029] Figure 2 illustrates multiple points servicing a cell. The cell has more points receiving ULs than points sending DLs. This "high-density UL deployment" can be beneficial for UL coverage and performance in the cell.

[0030] Figure 2 illustrates an exemplary cell with DL transmission at one TRP and UL reception at three points (one TRP and two RPs).

[0031] Figure 3 illustrates two nearby cells, each served by multiple points. In this example, RP3 serves both cell A and cell B. UL transmissions from several UEs in cell A and UL transmissions from UEs in cell B are received by RP3 at least occasionally.

[0032] Figure 3 illustrates two exemplary cells, each served by multiple points. In this example, RP3 serves both cells.

[0033] Figure 4 illustrates an example of two cells, where cell A is served by multiple points and cell B is served by a single TRP. In this example, TRP2 serves cell B as a TRP and serves cell A as an RP.

[0034] [Cell containing only UL (ultralight)] In some scenarios, the TRP and / or RP operate on different frequency layers or sets of frequency layers, which may be in the same or different frequency bands. The UE can be serviced simultaneously by cells on multiple different frequency layers, for example, using carrier aggregation (CA) and / or duplication (DC).

[0035] In a cellular system, a site may service one or more cells on one or more frequency layers. In some cases, a site may include a TRP on each frequency layer. However, in some cases, a site may provide a TRP to a first cell on a first frequency layer and a RP to a second cell on a second frequency layer. This scenario is illustrated in Figure 5, where a site services cell A on frequency layer f1 and cell B on frequency layer f2. For cell A, the site provides a TRP, and for cell B, the site provides an RP. One reason why the site does not provide transmission on cell B may be that the site lacks such capability, for example, the ability to transmit on frequency layer f2. Another reason may be that cell B does not include DL transmission, for example, it may be a UL-only SCell. It should be noted that being a UL-only SCell may be a configuration issue, meaning that the cell may be reconfigured to be UL-only for one period while including DL for another period. This may mean that the site could act as a TRP on cell B during such periods, if it has such capability.

[0036] In some cases, a cell may be constructed using supplemental UL carriers in addition to the normal UL carriers. These supplemental UL carriers may be in a different frequency band than both the cell's DL and normal UL. Only RPs may be present on the supplemental UL carriers, while TRPs may not.

[0037] Figure 5 illustrates an example of a site serving two cells (Cell A and Cell B) with two frequency layers (f1 and f2). In Cell A, the site provides TRP, and in Cell B, the site provides RP. Cell B may be a UL-only SCell.

[0038] As illustrated in Figure 6, points serving different cells may not be located in the same place.

[0039] Figure 6 illustrates an example where TPR1 serves cell A on frequency layer f1 and RP1 serves cell B on frequency layer f2. Cell B may be a SCell consisting only of UL.

[0040] Different frequencies, such as f1 and f2, may be close to each other, for example, in the same frequency band, or they may be not close to each other, for example, in different frequency bands.

[0041] If the frequencies are sufficiently close, the beamforming characteristics will be similar at different frequencies. Otherwise, the beamforming characteristics can be completely different.

[0042] For example, consider the scenario in Figure 5. If f1 and f2 are close enough, the good UL beam pair on cell A (UE Tx beam and TRP / RP Rx beam) is likely to be the good UL beam pair on cell B. However, if f1 and f2 are too far apart, this may not be the case.

[0043] In the scenario shown in Figure 6, it should be noted that the beam derived for communication on cell A may not be suitable for communication on cell B, even if f1 and f2 are close together, because the points serving the cell are geographically separated.

[0044] [Non-codebook-based (NCBB) PUSCH and SRS in NR] Non-codebook-based beam management for PUSCH and SRS can be used to operate DL-based UL for UEs that support beam compatibility.

[0045] In the case of SRS and PUSCH in NR, DL-based UL may be configured using non-codebook-based (NCBB) PUSCH, thereby the PUSCH configuration (PUSCH-Config) includes a non-codebook-configured mode configuration (txConfig).

[0046] In the case of SRS and PUSCH in NR, DL-based UL can also be configured using non-codebook-based (NCBB) PUSCH, where an SRS resource set with usage "nonCodebook" is configured, and an associated CSI-RS (e.g., "associatedCSI-RS" or "csi-RS") is configured for the SRS resource set with usage "nonCodebook", or a spatial relationship ("spatialRelationInfo") is configured for the SRS resources within the SRS resource set, or a default spatial relationship is applied.

[0047] DL-based UL beam management for NCBB PUSCH is illustrated in Figures 7A and 7B.

[0048] Figure 7A illustrates DL-based UL based on the default beam. For example, SRS uses DL RS in a TCI state activated for CORESET as a spatial relationship. If another TCI state with a different DL RS is activated for CORESET, SRS uses the new DL RS as a spatial relationship without requiring reconfiguration or other actions.

[0049] Figure 7A illustrates operation with the default beam, which means that multiple SRSs do not need to be transmitted and DCI does not need to direct the SRS.

[0050] Figure 7B illustrates operation without using the default beam.

[0051] Figure 7B illustrates a DL-based UL based on spatial relationships configured and activated for SRS based on DL RS. In this example, the SRS resource set for non-codebook includes four SRS resources for different DL RS as spatial relationships. In this example, the network directs two SRS resources for non-codebook-based PUSCH transmissions, meaning that a two-layer PUSCH is transmitted by the UE, with the first layer transmitted using the same precoder and spatial domain transmit filter as the first directed SRS, and the second layer transmitted using the same precoder and spatial domain transmit filter as the second directed SRS.

[0052] Note that different DL RSs may correspond to different DL transmit beams. On the UE side, these may correspond to different DL receive beams, and therefore different UL transmit beams, based on beam mapping.

[0053] [PUSCH and SRS in codebook-based (CBB) systems in NR] Codebook-based beam management for PUSCH and SRS can be used to partially operate DL-based UL for UEs that support beam compatibility.

[0054] In the case of SRS and PUSCH in NR, DL-based UL may be configured using codebook-based (CBB) PUSCH, thereby the PUSCH configuration (PUSCH-Config) includes the codebook-configured mode configuration (txConfig).

[0055] DL-based ULs can also be configured using a Codebook-Based (CBB) PUSCH, which configures an SRS resource set where usage is "codebook," and either configures spatial relationships ("spatialRelationInfo") for the SRS resources within the SRS resource set, or applies default spatial relationships.

[0056] Figure 8 illustrates partially DL-based UL beam management for CBB PUSCH. SRS resources within the SRS resource set for the codebook may have DL RS as an activated spatial relationship (e.g., as SRS8) or as another SRS resource (e.g., as SRS9). The spatial domain transmit filter for SRS8 is based on the spatial domain receive filter used to receive the DL RS, but the corresponding PUSCH precoder must be computed in the network and instructed to the UE. Therefore, since a highly quantized precoder (not DL-based) is also applied to PUSCH transmissions, there is no complete correspondence between the DL receive beam used to receive the DL RS and the corresponding transmit beam for PUSCH.

[0057] Figure 8 illustrates an example of a partially DL-based UL operation that uses CBB operation.

[0058] [Operation of NCBB, CBB SRS, and PUSCH in BWP] In state-of-the-art systems, the UE operates in either NCBB or CBB mode for SRS and / or PUSCH in the UL BWP of the serving cell. UE-specific parameters for the UL BWP may be configured in IE BWP-UplinkDedicated. IE BWP-UplinkDedicated may include the setup (configuration) of IE PUSCH-Config, which configures various parameters for PUSCH in the UL BWP.

[0059] Furthermore, IE BWP-UplinkDedicated may include setting up IE SRS-Config, which configures various parameters for SRS in BWP. In IE PUSCH-Config, the UE may be configured using the parameter txConfig, which has a codebook or noncodebook value, as per version 16.0.0 of the March 2020 release of 3GPP TS 38.331. These values ​​correspond to the configuration of CBB and NCBB operation for PUSCH, respectively.

[0060] In IE SRS-Config, a UE may be configured with a set of SRS resources for a UL BWP in the form of a list of elements of IE type SRS-Resource. The configuration of an SRS resource (in IE SRS-Resource) includes an ID configured by the parameter SRS-ResourceId. In IE SRS-Config, a UE may also be configured with a set of SRS resource sets (SRSRS) for a UL BWP by including a list of elements of IE type SRS-ResourceSet to be added to the set, and / or including a list of elements of IE type SRS-ResourceSetId to be removed (released) from the set.

[0061] An SRS resource set configured by IE SRS-ResourceSet contains a set of SRS resources. Technically, an SRS resource set contains references to a list of elements of the form SRS resource ID, e.g., IE type SRS-ResourceId. An SRS resource set can be configured to be aperiodic (AP), semi-persistent (SP), or periodic. The usage of an SRS resource set is configured by a parameter `usage`, which can take one of the following values: `beamManagement` (BM), `codebook` (CB or CBB), `noncodebook` (NCB or NCBB), or `antennaSwitching`.

[0062] In this disclosure, the terms “beam management,” “codebook,” and “non-codebook” are taken into consideration.

[0063] 〔term〕 In this specification, the term “procedure” generally refers to a method of performing an action to achieve a particular objective. The term “procedure” is often used instead of “method” to avoid confusion with the special meaning of “method” in the context of M2M and IoT applications. The steps described in a procedure are often optional and can potentially be performed in various ways and in various orders. Therefore, in this specification, the term “procedure” should not be interpreted as referring to a rigid set and sequence of steps, but rather as referring to a general methodology for achieving a result that can be adapted in various ways.

[0064] In this disclosure, the terms spatial filter and spatial domain filter are equivalent and used interchangeably. A spatial domain transmit filter is a corresponding filter used for transmission, and a spatial domain receive filter is a corresponding filter used for reception. Spatial domain filters may correspond to flexible analog beamforming, such as phase shift, and / or more static antenna system characteristics, such as antenna radiation patterns. Spatial domain filters may also correspond to panels, such as a two-dimensional antenna array, and for example, two different spatial filters may simply correspond to two different panels. In some cases, a particular spatial domain filter may correspond to a particular beam, possibly in combination with a particular precoding.

[0065] The term spatial relationship is used frequently herein. It can refer to parameters (e.g., called spatial relationship information) to which the RRC is configured and / or directed by MAC CE and / or DCI for a target SRS resource, a PUCCH resource, and / or one or more PUCCH transmissions. A spatial relationship may include an SRS and / or one or more reference RSs, which may be DL RSs such as SSB and / or CSI-RS. In some cases, these DL RSs may belong to a different cell, in which case the spatial relationship may also include a cell ID and any other parameters necessary to identify DL RSs in a different cell. Spatial relationships are primarily used by UEs to determine the spatial domain transmit filter used for UL signals / channels such as SRS or PUCCH. If the reference RS in a spatial relationship is an SRS, then the target SRS or PUCCH may be transmitted with the same spatial domain transmit filter as the reference SRS. If the reference RS is a DL RS, then the UE may use the spatial domain receive filter for receiving the DL RS as the spatial domain transmit filter for the target SRS or PUCCH.

[0066] In this specification, the term (of a UL signal / channel) spatial relationship may, in some cases, refer to an active spatial relationship, e.g., a spatial relationship applied to the transmission of a corresponding UL signal / channel. A set of spatial relationships may be configured for a UE, and subsets of these may become active, for example, based on indications of spatial relationship IDs in MAC CE and / or DCI. A configured spatial relationship that is not active may be inactive. In some cases, there are no inactive spatial relationships.

[0067] [Default spatial relationships for PUSCH] For a PUSCH scheduled on a cell by DCI format 0_0, the UE shall, if applicable, transmit the PUSCH according to the spatial relationship corresponding to the dedicated PUSCH resource with the lowest ID within the active UL BWP of the cell, as described in clause 9.2.1 of TS 38.213.

[0068] For a PUSCH scheduled on a cell by DCI format 0_0, if the upper layer parameter enableDefaultBeamPlForPUSCH0_0 is set to "enabled", the UE will not be configured with a PUSCH resource on an active UL BWP, the UE will be in RRC connection mode, and the UE will transmit the PUSCH according to spatial relationships, referencing an RS with "QCL-Type-D" corresponding to the QCL assumption of the CORESET with the lowest ID, if applicable.

[0069] For a PUSCH scheduled on a cell by DCI format 0_0, if the upper layer parameter enableDefaultBeamPlForPUSCH0_0 is set to "enabled", the UE shall be configured with PUCCH resources on the active UL BWP, all PUCCH resources shall not be configured using any spatial relationships, the UE shall be in RRC connection mode, and the UE shall, if applicable, refer to an RS with "QCL-Type-D" corresponding to the QCL assumption of the CORESET having the lowest ID when the CORESET is configured on the CC, and transmit the PUSCH according to the spatial relationships.

[0070] [Default spatial relationships for SRS] If the upper-level parameter enableDefaultBeamPlForSRS is set to "enabled", then, except for SRS resources in SRS-ResourceSet where the upper-level parameter usage is set to "beamManagement", or SRS resources with associatedCSI-RS configuration where the upper-level parameter usage is set to noncodebook, or SRS resources configured by an upper-level parameter (e.g., SRS-for-positioning), if the upper-level parameter spatialRelationInfo for an SRS resource is not configured with FR2 and the UE is not configured with the upper-level parameter pathlossReferenceRS, the UE shall send the target SRS resource using the default spatial relationship.

[0071] The default spatial relationship may have the same spatial domain transmit filter used to receive a CORESET with the lowest controlResourceSetId in an active DL BWP within the CC, for example. The default spatial relationship may also have the same spatial domain transmit filter used to receive an activated TCI state with the lowest ID applicable to a PDSCH in an active DL BWP within the CC, if the UE is not configured using any CORESETs within the CC.

[0072] [Examples of problems] A typical mode of operation for UL beam management is DL-based UL (e.g., deriving the UL Tx beam based on the DL Rx beam). This can avoid the costly UE transmission of SRS for beam management in terms of radio resource usage, UL interference, and UE power consumption. In the case of PUSCH and SRS in NR, this mode of operation is achieved by the non-codebook-based use of the SRS resource set. However, in scenarios using RP, the UE cannot use DL-based UL for UL transmission to the RP because there is no DL RS transmitted from the RP.

[0073] [Challenge 1] In scenarios involving both TRP and RP, such as high-density UL deployment and beam-compatible UEs, how can UL beam management be efficiently operated so that DL-based UL beam management is used for TRP and / or SRS-based UL beam management is used for RP?

[0074] [Challenge 2] How are UL beam management operations based on Problem 1 reflected in PUSCH's scheduling and transmission, for example, in terms of instructions such as transmission method, beam selection, and TRP / RP selection?

[0075] In particular, what is needed to support both DL-based, non-codebook-based PUSCH to TRP, and SRS-based, codebook-based PUSCH to RP, without requiring RRC reconfiguration between the two?

[0076] For tasks 1 and 2, consider the following PUSCH "transmission methods": dynamic point selection between TRP and RP; semi-persistent selection of TRP and RP; and joint transmission to TRP and RP (e.g., from one PUSCH layer to TRP and from one PUSCH layer to RP).

[0077] Both single-panel and multi-panel UEs are considered. Transparent multi-panel operation (such as 3GPP NR Rel-15 and 3GPP NR Rel-16) and more explicit multi-panel operation (such as 3GPP NR Rel-17 and later) are also considered.

[0078] Generally, no specific assumptions are made regarding the backhaul links connecting points and nodes. However, some schemes may require that points be connected to an ideal backhaul, for example, with negligible latency and high throughput. Since backhaul assumptions are part of the network implementation, we will not discuss them further.

[0079] [Configuration of CBB and NCBB operation] The UE may be configured for the CBB and NCBB operation of SRS and PUSCH in the UL BWP of the serving cell. For example, there may be RRC parameters that enable one or more of the functions described below, for example, to enable this type of operation.

[0080] [A single SRS resource set where usage is "mixed" or usage is "codebook"] To enable both CBB and NCBB pushes in BWP, one approach is to introduce a usage from a different SRS resource set (SRSRS) other than those listed above, such as "mixed" or "cbAndNcbb". For simplicity, we will use the term "mixed" below. Configuration Example 1 in Appendix 1 shows a configuration where the usage is "mixed". If IE mixed_usage-r 17 is configured, the usage is "mixed".

[0081] Example 1 of the configuration in Appendix 1 is an example of an SRS-Config information element using a configuration where the usage of the SRS resource set is "mixed". The conditional presence of "Cond Codebook" may indicate that the field is optionally present (Need M) in the case of codebook-based submissions, and otherwise the field does not exist.

[0082] Another approach involves adding `usage "mixed"` as an option for the same parameter used to select other usages, as illustrated in Configuration Example 2 of Appendix 1.

[0083] Example 2 of the configuration in Appendix 1 is an example of an SRS-Config information element with a configuration in which the usage of the SRS resource set is "mixed".

[0084] Another approach involves enabling mixed operation, and consequently mixed SRSRS, in PUSCH-Config, as illustrated in Configuration Example 3 of Appendix 1.

[0085] Example 3 in Appendix 1 is an example of a PUSCH-Config information element that has a configuration for CBB and NCBB operation ("mixed").

[0086] Another approach involves configuring an SRSRS with usage set to codebook to enable NCBB and CBB behavior. For example, NCBB and CBB behavior may be enabled when the UE is configured with an SRSRS for codebooks and txConfig is set to noncodebook. For example, NCBB and CBB behavior may be enabled when the UE is configured with an SRSRS for noncodebooks and txConfig is set to codebook.

[0087] For brevity, the term CB-SRSRS is used to represent SRSRS whose usage is codebook or "mixed," including one or more multiport SRS resources used for CBB operation, and one or more single-port or multiport SRS resources used for any form of NCBB operation, as described below. In some cases, the number of ports of a multiport SRS resource used for any form of NCBB operation is less than the number of ports of a multiport SRS resource used for CBB operation. In some cases, the number of ports used for CBB operation is configured to be equal to the number of SRS ports, for example, via the SRS-Config IE parameter nrofSRS-Ports.

[0088] Various approaches to using single-port or multi-port SRS resources for any form of NCBB operation, i.e., as SRS resources corresponding to NCBB operation, may include, for example, any combination of the following five approaches:

[0089] The first case is when a port on a single-port or multi-port SRS resource supports multiple antennas. In some cases, multiple antennas support one or more ports on another SRS resource that has more antenna ports. In other cases, multiple antennas do not support one or more ports on another SRS resource that has more antenna ports.

[0090] For example, an antenna port, such as a logical antenna port, can be obtained through so-called antenna (or antenna port) virtualization, for example, by combining multiple antennas, such as physical antennas, to obtain an antenna port. In some cases, for example, an antenna port of a single-port SRS can be obtained by virtualizing / combining antennas corresponding to multiple other antenna ports of a multi-port SRS. The combination may involve adding the signals corresponding to multiple antennas and, in some cases, applying phase shift and / or amplitude scaling to one or more of these signals. This may be equivalent to the dot product of a complex vector containing these phase shift and / or amplitude scaling values ​​and a complex vector containing the signals. In some cases, how antenna port virtualization is implemented is up to the UE.

[0091] In some cases, each port of a multi-port SRS resource may be acquired through virtualization, for example, by virtualizing an SRS resource with more ports. For example, each port of a 2-port SRS resource may be acquired by virtualizing two different ports of a 4-port SRS resource. In some examples, different ports are acquired by virtualizing separate sets of antennas (or antenna ports), while in others, different ports are acquired by virtualizing overlapping or partially overlapping sets of antennas (or antenna ports), for example, by applying different combinations / precodings to different antenna ports.

[0092] Virtualization may include combining it with the digital domain, such as digital baseband and / or the analog domain, for example, with phase shifters and / or switches in RF.

[0093] In some cases, virtualization, such as precoding and / or spatial domain filtering, may be calculated by the UE based on one or more DL RS measurements.

[0094] The second case is when the network can constitute associated NZP CSI-RS, which are used as spatial relationships between single-port and / or multi-port SRS resources within the SRSRS. Based on measurements of the associated NZP CSI-RS resources, the UE can calculate the precoder used to transmit the SRS resources within the SRSRS.

[0095] The third case is when the network can configure and / or direct a reference DL-RS as a spatial relationship of a single-port SRS, thereby the UE shall transmit the single-port SRS resource using the same spatial domain transmit filter used to receive the reference DL-RS.

[0096] The fourth case is when, in some instances, the network directs a single port SRS resource for single-layer push transmissions or multiple single-port SRS resources for multi-layer push transmissions. For example, this directing may be done by an SRS resource indicator (SRI) in the DCI, whose value corresponds to one or more single-port SRS resources.

[0097] Note that in the case of single-layer push transmission based on a single-port SRS resource, not applying precoding may be equivalent to precoding with a scalar "1", and therefore NCBB and CBB operation may be equivalent. Also note that the UE may generate a single-port SRS by applying precoding and / or spatial transmit filters to signals from multiple transmit chains, and that the precoding and / or spatial transmit filters are not explicitly indicated by the network (e.g., via TPMI values). In other words, the precoding and / or spatial transmit filters used to generate a single antenna port from multiple antenna ports (transmit chains) may be transparent to the network.

[0098] Fifth, in some cases, the network may instruct the UE to use a precoder (e.g., TPMI from a codebook) for transmitting a multiport SRS resource. One or more of the antenna ports of this SRS resource may be virtualized and / or subject to precoding / spatial filtering calculated by the UE (e.g., based on receiving DL RS). In other words, the network may instruct the UE to apply precoding (e.g., after) antenna port virtualization or precoding / spatial filtering determined by the UE. Thus, NCBB operation in the context of this disclosure may, to some extent, also include codebook-based precoding operation.

[0099] For example, consider a multi-port SRS resource having a first antenna port spatially related to a first DL RS and a second antenna port spatially related to a second DL RS. Each of these ports functions similarly to a single-port SRS resource in NCBB operation. However, the network may also dictate a precoder that the UE should apply to this multi-port SRS resource.

[0100] A CB-SRSRS can be configured to include SRS resources that support NCBB operation and / or SRS resources that support CBB operation. For example, such a CB-SRSRS may include single-port SRS resources and / or multi-port SRS resources. For instance, the single-port SRS resources included in the set may support NCBB operation, and the multi-port SRS resources may support CBB operation.

[0101] In some cases, a single-port SRS resource may support either NCBB or CBB operation. For example, CB-SRSRS includes a multi-port SRS resource that supports CBB operation and a single-port SRS resource that also supports CBB operation. For example, a single-port SRS resource that supports CBB operation may support full-power UL transmission, as further described below.

[0102] Full-power UL transmission may be configured for UL BWP of a UE configured for non-coherent or partially-coherent PUSCH CBB transmission (for example, ul-FullPowerTransmission-r16 in IE PUSCH-Config is set to "fullpower", "fullpowerMode1", or "fullpowerMode2", and codebookSubset in IE PUSCH-Config is set to "nonCoherent" or "partialCoherent"). Full-power mode 1 may mean that the UE can perform full-power PUSCH transmission for a particular pre-coded codebook subset, which may be instructed to the network as UE capability. Full-power mode 2 may mean that the UE can be configured with SRS resources having a different number of antenna ports within SRSRS for the codebooks (details and constraints may be part of UE capability), and that SRS resources within SRSRS having fewer antenna ports than the maximum number in the set may be capable of full-power PUSCH transmission. Full Power Mode 2, like Full Power Mode 1, can also mean full power push transmissions for a specific pre-coded codebook subset. The mode "fullpower" can mean that the UE can perform full power push transmissions regardless of the precoder or indicated SRS. Note that full power push transmissions may only occur if required by UL power control. Including a single-port SRS resource in the SRS resource set for a codebook may only be supported for a subset of full power UL transmission configurations, e.g., only for "fullpowerMode2". In some implementations, such a single-port SRS resource may be transmitted from one of the transmitter chains (e.g., including one PA) of a UE capable of full power transmission for a UE power class, e.g., from a transmitter chain capable of 23 dBm transmission for a UE in power class 3.In some implementations, such a single-port SRS resource may be transmitted from multiple UE transmitter chains (e.g., each containing one PA), where each transmitter chain is not capable of full-power transmission, but the combined power of multiple transmitter chains can reach the full power of a power class. For example, a UE may have two 20dBm transmitter chains with a combined maximum transmit power of 23dBm. The two 20dBm transmitter chains may correspond to a 2-port SRS resource in the SRS resource set for the codebook, for example, the first SRS antenna port transmits from the first transmitter chain and the second SRS antenna port transmits from the second transmitter chain. Then, a single-port SRS resource in the same SRS resource set for the codebook, corresponding to full-power transmission, may correspond to transmissions from both transmitter chains. As mentioned above, this may be called "virtualization" or "antenna port virtualization." In other examples, a UE may have three or more, for example, four, transmitter chains and / or antenna ports. In this case, these transmitter chains can be virtualized into single-port SRS resources and / or multi-port SRS resources. For example, a UE with four transmitter chains may be configured with a 2-port SRS resource where both ports are virtualized, for example, transmitted from two or more transmitter chains. In another example, a subset of ports may be virtualized, while the rest are not, for example, each of these ports may be transmitted from a single transmitter chain. For example, a first single-port SRS resource may be transmitted from a 23dBm transmitter chain, and a second single-port SRS resource may be transmitted from two 20dBm transmitter chains.

[0103] In some cases, the UE may report to the network the ability to perform NCBB operations based on one or more single-port SRS resources within the CB-SRSRS, and one or more single-port SRS resources also support full-power UL transmission. In some cases, the UE may report to the network the ability to perform NCBB operations based on one or more multi-port SRS resources within the CB-SRSRS, and one or more multi-port SRS resources also support full-power UL transmission.

[0104] In some cases, a UE may report that NCBB operation based on CB-SRSRS is supported, regardless of whether single-port and / or multi-port SRS resources are configured for full-power UL transmission. In some cases, a UE may report that NCBB operation based on CB-SRSRS is supported if single-port and / or multi-port SRS resources are not configured for full-power UL transmission. In some cases, a UE may report that NCBB operation based on CB-SRSRS is supported and that full, partial, and non-coherent codebooks are supported for push transmission. A UE with non-coherent codebook capability may not be able to guarantee phase coherence between antenna ports for UL transmission. A UE with partial coherent codebook capability may guarantee phase coherence between some pairs of antenna ports, but not between other pairs of antenna ports. A UE capable of full coherence may guarantee phase coherence across all of its antenna ports. Some precoders are only suitable for fully coherent UEs. Some precoders are suitable for fully coherent and partially coherent UEs. Some precoders, for example, those that select a single antenna port, are suitable for full, partial, and non-coherent UEs. Therefore, corresponding codebooks or subsets of codebooks are defined. A UE can instruct the network of its UL coherence capability, and the network can configure the UE accordingly. Note that a UE can be configured with a lower capability than the capability reported by the UE; for example, the network can configure the UE using a subset of codebooks for a non-coherent UE even if the UE reports a fully coherent codebook capability.

[0105] In this specification, UE capability reports for supported targets may be per UE, per bandwidth combination, per bandwidth, per feature set (per bandwidth for each bandwidth combination), and / or per feature set for each component carrier (per CC for each bandwidth for each bandwidth combination).

[0106] In some cases, CB-SRSRS may be configured to include a multi-port SRS resource that supports CBB operation and a single-port SRS resource that also supports CBB operation, even if the UE is not configured for full-power UL transmission by, for example, ul-FullPowerTransmission-r16. Note that the fact that the UE is not configured for full-power UL transmission does not mean that the UE is unable to perform full-power UL transmission, or that in some situations the UE will not transmit at full power (according to the UE power class). As mentioned above, an SRS resource that supports CBB operation, such as a single-port SRS resource, may also support NCBB operation in some form.

[0107] In some cases, the SRS resources within CB-SRSRS may be for either full-power transmission (UL) or non-compressive broadband (NCBB) operation. In some cases, the SRS resources within CB-SRSRS may be for both full-power transmission (UL) and NCBB operation.

[0108] For example, an SRS configuration may include an optional second list of SRS resource IDs that can correspond to SRS resources for NCBB operation, as illustrated in Configuration Example 4 of Appendix 1. The SRS resources indicated in the second list may be limited to single-port SRS resources. The conditional presence of "Cond Codebook" may indicate that, in the case of codebook-based transmissions, the field is optionally present (Need M), and otherwise the field is absent. "Need M" is used to enable delta signaling for (configuration) fields that are maintained by the UE when they are absent in subsequent configuration messages. In one example, the optional presence is conditional on the usage being "mixed". The codebook / mixed usage condition may also not be present in other examples, in which case simply required codes, such as "Need M", may be applied instead.

[0109] In one example, if the second list is configured, the usage of the SRS resource set is "mixed". In this case, as mentioned earlier, the UE may not need to be configured with the usage of SRSRS set to "mixed" and / or the txConfig set to "mixed". In another example, if the second list is configured, the usage of SRSRS is still codebook.

[0110] Example 4 in Appendix 1 is an exemplary SRS-Config information element having a second list of SRS resource IDs.

[0111] In some cases, for example, if the UE supports a single-port SRS being used for both full-power transmission and NCBB operation, the same SRS resource ID may be included in both the legacy SRS resource ID list (e.g., srs-ResourceIdList) and the second list. If so, this may mean that the SRS resource is used for both full-power UL transmission (e.g., if this is configured) and NCBB operation.

[0112] In some cases, for example, if the UE does not support a single-port SRS being used for both full-power transmission and NCBB operation, the same SRS resource ID may not be included in both the legacy SRS resource ID list (e.g., srs-ResourceIdList) and the second list.

[0113] The UE may report to the network the maximum number of SRS resources (A) within the CB-SRSRS, for example, the capacity of two or four SRS resources, using parameters such as the maxNumberSRS-ResourcePerSet UE capability parameter or the "UL Full Power Transmit Mode 2" UE capability IE or parameter. Furthermore, the UE may also report to the network the capacity of the maximum number of SRS resources (B) within the CB-SRSRS, corresponding to NCBB operation. For example, the maximum number B may be fixed or derived from the maximum number A, for example, if A=2, then B=1, if A=4, then B=2, and so on.

[0114] In some cases, the UE may report to the network the capacity of the maximum number (C) of single-port SRS resources within the CB-SRSRS, e.g., one or two single-port SRS resources, for full-power UL transmission. In some cases, the reported maximum number B should be less than or equal to C. In some cases, the maximum number B is derived from the maximum number C, for example, if C=2, then B=1. In some cases, the maximum number B is equal to the maximum number C.

[0115] In some cases, a UE may instruct the network to provide a group of precoders that support full-power UL transmissions. Such a group may be a subset of the codebook used for CBB PUSCH transmissions. For example, a UE supporting a 4-port SRS resource for CBB operation may instruct a subset of precoders from the 4-port codebook. Such precoders may be used when the network instructs a 4-port SRS resource in the SRI. In another example, a UE supporting a 4-port SRS resource for CBB operation may instruct a subset of precoders from the 2-port codebook. Such precoders may be used when the network instructs a 2-port SRS resource in the SRI.

[0116] Similarly, in some cases, a UE may instruct the network to provide a group of precoders that support NCBB operation. In some cases, such a group may be limited to precoders for fewer antenna ports than the number of SRS antenna ports that the UE supports for CBB operation. For example, a group of precoders for two antenna ports may be reported by a UE that supports a 4-port SRS resource for CBB operation. Supporting codebook-based precoding for NCBB operation may seem contradictory, but as mentioned above, NCBB operation can, in some cases, be combined with codebook-based precoding. For example, consider a UE that supports a 4-port SRS resource for CBB operation. CB-SRS includes a 2-port SRS resource in addition to the 4-port SRS resource. One or both antenna ports of the 2-port SRS resource are acquired by NCBB operation, and for example, the precoding and / or spatial domain transmit filter of the antenna ports is based on DL RS, e.g., the measurement of the associated NZP CSI-RS, or follows the spatial relationship. In some cases, the precoding and / or spatial domain transmit filters for two antenna ports are based on the measurement of two different DL RSs, e.g., two separately configured and associated NZP CSI-RSs or two separate spatial relationships. The precoding applied to the two-port SRS resource is a form of port selection without additional phase shift, e.g., a precoding vector for single-layer transmit

[0010] T ,

[0001] T , and / or

[0011] T , and for 2-layer transmission

number

[0117] Multiple different RSs, such as multiple DL RSs or multiple SRSs or a mixture thereof, used as the spatial relationship between multiple different antenna ports in a multiport SRS, can be configured and / or indicated in various ways.

[0118] For example, an SRS resource may be configured with an optional second spatial relationship (e.g., a second SRS-SpatialRelationInfo IE). The first spatial relationship may apply to a first set of SRS antenna ports, e.g., the lowest-indexed antenna port, and the second spatial relationship may apply to a second set of SRS antenna ports, e.g., the second lowest-indexed antenna port. In one example, the first spatial relationship may apply to antenna ports in a first CDM group, and the second spatial relationship may apply to antenna ports in a second CDM group, and so on.

[0119] In another example, a spatial relationship (e.g., a new SRS-SpatialRelationInfo-r17) involving multiple RSs may be configured / indicated. These multiple RSs may be ordered by the order / sequence of their configurations in the spatial relationship, for example, one of the RSs may be the first RS, one of the RSs may be the second RS, and so on. The first RS may function as the spatial relationship of the lowest numbered antenna port, the second RS may function as the spatial relationship of the second lowest numbered antenna port, and so on.

[0120] SRS spatial relationships can be updated via MAC CEs, such as the SP SRS activation / deactivation MAC CE, AP SRS spatial relationship instruction MAC CE, or CC list-based SRS activation / deactivation MAC CE, by allocating bits currently reserved to indicate whether a first or second spatial relationship is updated. In one example, for an SRS resource that does not use two spatial relationships, if a second spatial relationship is indicated by a MAC CE, that indication is ignored with respect to the SRS resource. In another example, the indicated second spatial relationship is added as a second spatial relationship to an SRS resource that previously contained only a single spatial relationship.

[0121] In some cases, the associated NZP CSI-RS may be configured for CB-SRSRS. In some cases, the NZP CSI-RS may be configured and then indicated by a DCI that triggers aperiodic SRSRS. An example of configuring an associated NZP CSI-RS for CB-SRSRS is shown in Configuration Example 5 of Appendix 1. The conditional existence "Cond XYZ" can be "Cond Codebook", for example, the field optionally exists (Need M) in the case of codebook-based transmission, and otherwise the field does not exist. It may also optionally exist if the UE is configured with NCBB operation, for example, if the second SRS resource list is configured as in Configuration Example 4 of Appendix 1, and / or if the mixed SRS resource set is enabled as in Configuration Example 1 of Appendix 1. In this example, the same parameters are used to configure the associated CSI-RS when the SRSRS are semi-permanent or periodic, and to configure the CSI-RS when the SRSRS are aperiodic. However, in the case of legacy CSI-RS / related CSI-RS, these have separate parameters within the resourceType CHOICE alternative.

[0122] Example 5 in Appendix 1 is an example of an SRS-Config information element for CB-SRSRS, having an associated NZP CSI-RS configuration.

[0123] In some cases, the associated NZP CSI-RS is applicable to all SRS resources within the CB-SRSRS. In some cases, the UE may be configured / directed by both the associated NZP CSI-RS for the CB-SRSRS and the spatial relationships of one or more SRS resources within the CB-SRSRS. In some cases, the associated NZP CSI-RS may be applicable to SRS resources within the CB-SRSRS that are not configured / directed using spatial relationships, such as a single-port SRS resource.

[0124] Consider the following example. Firstly, the UE reports that it supports NCBB operation within CB-SRSRS and supports up to 4 port SRS resources for CBB operation. For example, the UE may also report that it supports full, partial, and non-coherent codebooks, but it may not report its capability for full-power UL transmissions because, for example, full-power CBB UL transmissions are supported for UEs that are fully coherent in any case.

[0125] Secondly, the network configures one or more SRSRSs whose usage is "beamManagement" (BM). Thirdly, the network configures CB-SRSRSs using SRS resources, for example, For a 4-port SRS resource, it is SRS resource 0, and for a 1-port SRS resource, it is SRS resource 1. Fourthly, in the RP, the network measures the SRS resource from SRSRS for BM.

[0126] Fifth, for SRS resource 0, the network configures / directs the spatial relationship with the SRS resources within SRSRS for "beamManagement," which was best suited for reception at the RP.

[0127] For SRS resource 1, the network either configures / directs a spatial relationship with DL RS, configures / directs an associated NZP CSI-RS, or does not configure a spatial relationship so that the default spatial relationship applies.

[0128] Sixth, if the network schedules a PUSCH transmission to the RP, DCI directs SRS resource 0 via SRI. DCI directs a 4-port precoder. UE sends a PUSCH to RP using the spatial domain transmit filter of SRS resource 0 and the directed 4-port precoder.

[0129] Seventh, if the network schedules a PUSCH transmission to the TRP, the DCI directs SRS resource 1 via the SRI. The UE transmits the PUSCH to the TRP using the spatial domain transmit filter and precoder derived from the DL RS measurements. Two SRS resource sets

[0130] To enable both NCBB and CBB PUSCH in a BWP, the UE may be configured, for example, in a UL BWP, using SRS resource sets (SRSRS) where the usage is noncodebook and SRSRS where the usage is codebook. Such a configuration may enable various functions for the CBB and NCBB operations described herein.

[0131] The UE may report that it supports configurations using SRSRS where usage is noncodebook and SRSRS where usage is codebook in the UL BWP. If the UE is also configured with SRSRS for codebooks, the UE may report the maximum number of single-port SRS resources in the non-codebook SRSRS. If the UE is also configured with SRSRS for non-codebooks, the UE may report the maximum number of SRS resources in the codebook SRSRS, including, for example, both single-port and multi-port SRS resources. The UE may report the maximum number of combined SRS resources in the codebook SRSRS and non-codebook SRSRS, for example, unique SRS resources combined into two sets.

[0132] In some cases, if a UE is configured with SRSRS for a codebook, the UE may be configured with SRSRS for a non-codebook, but the SRS resource IDs of one or more single-port SRS resources in SRSRS for a non-codebook must be included in SRSRS for a codebook. In other words, SRSRS for a codebook may include SRS resources not included in SRSRS for a non-codebook, such as one or more multi-port SRS resources, but SRSRS for a non-codebook may not include single-port SRS resources not yet included in SRSRS for a codebook. In some cases, this is similar to having a second SRS resource list (see Configuration Example 4 in Appendix 1), where SRSRS for a non-codebook acts as the second list. Furthermore, the UE may expect that other parameters in SRSRS for a non-codebook, such as resourceType and p0 (e.g., power level for SRS power control), must be the same as those in SRSRS for a codebook. As an exception, SRSRS for non-codebook systems may be configured using CSI-RS or associated CSI-RS, while SRSRS for codebook systems may not be configured in this way. In this manner, associated CSI-RS may be applicable to a subset of SRS resources within SRSRS for codebook systems, i.e., single-port SRS resources also present within SRSRS for non-codebook systems. The technical specification may exclude the configuration of these single-port SRS resources using both associated CSI-RS and spatial relationships.

[0133] In some cases, an SRSRS for a codebook includes a single-port SRS resource following an associated CSI-RS (e.g., one configured for an SRSRS for a non-codebook), an SRS resource following a default spatial relationship (e.g., one that does not have a configured spatial relationship or associated CSI-RS, and the default spatial relationship is enabled), and an SRS resource following a configured / directed spatial relationship (e.g., for an SRS for a BM). Such a configuration may be useful in scenarios where a UE may send a UL to two TRPs and one RP. For example, the associated CSI-RS may be sent from the first TRP, the default spatial relationship may be based on a DL RS sent from the second TRP, and the configured / directed spatial relationship may be adjusted for transmission to the RP.

[0134] However, the number of different spatial relationships in an SRSRS for a codebook, for example, may be limited by, for example, UE capabilities. For example, at most two different spatial relationships may be active for an SRSRS, the default spatial relationship may be counted as one, an associated CSI-RS different from the default spatial relationship may be counted as another, and a spatial relationship containing an RS different from the previous two, for example an SRS for a BM, may be counted as yet another. In some cases, one or more SRS resources from two different SRSRSs may be indicated using the same SRI field in DCI. For example, the two different SRSRSs could be one SRSRS for a codebook and one SRSRS for a non-codebook.

[0135] In some cases, the bit width of this SRI field is based on NCBB operation, for example, the number of bits

number

[0136] In some cases, the bit width of this SRI field is based on the NCBB operation for SRSs for NCBB operation and the CBB operation for SRSs for CBB operation. For example, the number of bits is

Number

[0137] 〔Improvement of Scheduling〕 If the SRS resources within the SRSs for non-codebook are also included in the SRSs for codebook, the DCI (e.g., DCI format 0_0, 0_1 or 0_2) carrying the UL grant may be based on, for example, the CBB operation, and for example, the bit width and interpretation of the DCI field are based on the CBB operation specified by, for example, "txConfig = codebook of upper layer parameters". Also, for SRSs with usage being "mixed", the bit width and interpretation of the DCI field may be related to the CBB operation. The following examples where SRSs for codebook are mentioned are also applicable to SRSs for mixing.

[0138] In the case of NCBB and CBB operations based on SRSRS where the usage is "codebook," the bit width and interpretation of the DCI field may follow the CBB operation. All these cases and examples can be applied to the following methods for selecting multiple SRS resources for NCBB operation, for example, based on the existing DCI field and bit width for CBB operation. Various solutions are based on the interpretation or reinterpretation of the field relating to "precoding and layer count" in DCI format 0_0, 0_1, or 0_2, for example.

[0139] In CBB operation, the number of bits in the SRI field within DCI can be determined based on the number of SRS resources within SRSRS for the codebook. The number of bits for "Precoding and Layer Count" in the DCI field can be determined based on the SRS resource with the most antenna ports within SRSRS for the codebook.

[0140] The SRI can indicate one of the SRS resources within SRSRS for a codebook. If the SRI indicates an SRS resource with fewer antenna ports than the SRS resource with the most antenna ports in the set, the number of bits required for the precoder and layer count fields will typically be fewer. For example, the precoder and layer count fields may be 6 bits for 4 antenna ports and full, partial, and noncoherent codebook subsets (e.g., the parameter codebookSubset is set to "fullyAndPartialAndNonCoherent"). For example, if the SRI indicates an SRS resource with 2 antenna ports, only 4 of those 6 bits are required for the precoder and layer count indication. For example, if the SRI indicates an SRS resource with 1 antenna port, 0 of those 6 bits are required for the precoder and layer count indication. This is because no precoding is performed for 1-port signals / channels, and only single-layer transmission is supported. Note that the fields for precoder (or precoder) and number of layers may, for example, be referred to as “precoder information and number of layers” in this specification.

[0141] Bits in the precoding and layer count fields that are not required for the precoding and layer count indication for the specified SRS resource can be handled in various ways, as described below, for example. The bits that are not required ("unnecessary" bits) may be, for example, the MSB or LSB of the field. For simplicity, let Z represent the "unnecessary" bits or a subset thereof, and S represent the SRS resource indicated by the SRI. This is illustrated in Figure 14.

[0142] Figure 9 illustrates an example of how Z can be obtained if, for example, S is a single port. In some cases, Z is zero-padded. In other cases, Z is reserved.

[0143] In some cases, Z may indicate zero, one, or more SRS resources. Note that not all bits of Z are required for this. The remaining bits may be zero-padded, reserved, or used for other purposes, for example. The SRS resources indicated by Z may be used for scheduled push transmissions. For example, a UE may determine its push precoder and layer count based on the SRS resources indicated by Z, and the indicated SRS resources may determine the push precoder and / or spatial domain transmit filter for the layers of the push, for example, according to NCBB operation.

[0144] In some cases, the SRS resource indicated by Z resides within SRSRS for the codebook. In some cases, the UE is also configured using SRSRS for non-codebook applications. The indicated SRS resource resides within SRSRS for non-codebook applications. Note that in some such cases, the SRS resource may reside both within SRSRS for the codebook and within SRSRS for non-codebook applications. There are four basic ways to address this: Z may indicate S and / or other SRS resources; Z may indicate SRS resources within SRSRS other than S; Z may be used to indicate a row in a table for SRS resource indication for NCBB operations; and S may be a multiport SRS resource. These four approaches and their variations are described below.

[0145] The first case is when Z may refer to S and / or other SRS resources. Here, in the first example of the first approach, For example, Z could be a bitmap of SRS resources, where, for example, "1" indicates an SRS resource and "0" means that no corresponding SRS resource is indicated. The bits in the bitmap correspond to single-port SRS resources within SRSRS (for the codebook or, in different examples, for non-codebook use), where, for example, S could be a single-port SRS. For example, if there are two single-port SRS resources within SRSRS, Z could contain a 2-bit bitmap, as illustrated below.

[0146] For example, if Z=''00'', no SRS resources are indicated. In some cases, this may be an invalid indication, for example, the UE may not expect this indication. In other cases, it may be valid, but the result is that the SRS within SRSRS is not used as a spatial relationship. Instead, the UE may follow the default spatial relationship, for example. If Z=''01'', the first single-port SRS resource within SRSRS, for example S, or another single-port SRS resource is indicated. If Z=''10'', the second single-port SRS resource within SRSRS is indicated. If Z=''11'', both single-port SRS resources within SRSRS, including S, are indicated.

[0147] In the second example of the first approach, Z may represent an integer value used to select a row from a table, for example, as follows: In Table 2 of Appendix 2, "N" may correspond to the number of single-port SRS resources in SRSRS (for the codebook or, in different examples, for the non-codebook), and "SRI" may correspond to an SRS index in SRSRS, or an index between single-port SRS resources in SRSRS. For example, S may correspond to SRS index 1, and other single-port SRS resources may correspond to SRS index 0.

[0148] The second approach is when Z refers to an SRS resource other than S, (for a codebook or, in a different example, a non-codebook).

[0149] For example, Z could be a bitmap of SRS resources other than S, where, for example, "1" indicates an SRS resource and "0" does not indicate an SRS resource. The bits in the bitmap correspond to single-port SRS resources within SRSRS other than S. However, S can also be a single-port SRS resource, or possibly a multi-port SRS resource. For example, consider an example where SRSRS has three single-port SRS resources, e.g., S, a first other SRS resource S', and a second other SRS resource S''.

[0150] In this example, Z may contain a 2-bit bitmap. For example, if Z=''00'', no other single-port SRS resources are indicated. If Z=''01'', S' is indicated, and if Z=''10'', S'' is indicated. If Z=''11'', both S' and S'' are indicated.

[0151] In another example, Z represents an integer value used to select a row from a table, for example, as follows: Below, N may correspond to the number of single-port SRS resources in SRSRS other than S, and SRI may correspond to an SRS index in SRSRS or an index between single-port SRS resources in SRSRS other than S. See Table 3 in Appendix 2.

[0152] In one example, to determine the PUSCH precoder and / or spatial domain transmit filter and the number of layers, both S and SRS resources (e.g., their union) indicated by Z, if they exist, are used, and the number of layers, for example, is the number of SRS resources indicated by Z plus 1.

[0153] In one example, to determine the PUSCH precoder and / or spatial domain transmit filter and the number of layers, only the SRS resources indicated by Z, if they exist, are used, and the number of layers, for example, is the number of SRS resources indicated by Z.

[0154] A third approach is when Z is used to indicate a row in a table for SRS resource indication for NCBB operation. The table may be a legacy table for SRI indication for NCBB operation. Let M represent the number of antenna ports of the SRS resource with the most antenna ports in SRSRS. For CBB operation and codebook subset restriction (CBSR), the UE consists of either a full, partial, and noncoherent codebook subset (fpnc); a partial and noncoherent codebook subset (pnc); or a noncoherent codebook subset (nc).

[0155] In the third approach, P represents the number of bits in the DCI field "Precoder and Layer Number" within the DCI that schedules PUSCH, for example, DCI format 0_0, 0_1, or 0_2.

[0156] For brevity, we assume that the maximum rank of PUSCH(CBB) is equal to M. In other examples not described here, the maximum rank of PUSCH(CBB) may be less than M, which may or may not result in a different value P. For brevity, we assume that full-power UL transmission (ULFPTxModes) is not set or configured in Mode 2. Depending on the configuration of Mode 1, this may result in a different value. We also assume that conversion precoding is disabled, as only single-layer transmission is supported if conversion precoding is enabled. For single-layer transmission, it may not be useful to specify an additional single-port SRS resource greater than S.

[0157] N represents the number of single-port SRS resources in SRSRS (for the codebook or, in different examples, for the non-codebook), and N may or may not include S. K represents the number of bits required for NCBB SRI, for example, according to the assumption that a normal NCBB operation, such as a single-port SRS resource, can be used for NCBB operation.

[0158] Table 4 in Appendix 2 summarizes examples of the use of Z in various cases. Table 4 illustrates the number of bits available in the DCI field for “Precoding and Layer Count” and the number of bits required in the legacy NCBB SRI DCI field (K). Although this may not be generally true, the number of bits required for K is equal to N.

[0159] Z uses a portion of the P bits from the "Precoding and Layer Count" field. In this example, since a single-port SRS is selected in the SRI (for CBB), bit 0 of the allocated P bits is used. Therefore, Z could potentially use all of the P bits. Note that P is determined by the number of antenna ports of the SRS resource with the most antenna ports, not the number of antenna ports of the SRS resource indicated by the SRI (for CBB).

[0160] The "Table in TS 38.212" column refers to version 16.1.0 of the March 2020 release of Table 3GPP TS 38.212, which defines different SRS resource combinations that can be selected by the SRI for NCBB operation. K represents the number of bits required to represent these different SRS resource combinations for a particular combination of M and N in a row. Different tables may be used for different maximum ranks of NCBB operation, and the maximum rank may be determined by the upper-layer parameter maxMIMO-Layers or by the maximum number of supported layers instructed to the network by the UE.

[0161] The final column (K≦P?) evaluates whether K≦P, for example, whether Z (in this case, P bits) has enough bits to indicate any of the relevant SRS resource combinations in the corresponding table. In this example, Z has enough bits in all cases.

[0162] A fourth approach is when S is a multi-port SRS resource and has fewer antenna ports than the maximum number of antenna ports in the SRSRS. For example, consider an SRSRS with a 4-port SRS resource, a 2-port SRS resource, and two single-port SRS resources. Since there are four SRS resources, the SRI field may be 2 bits. The precoding and layer count fields may be 6 bits for the 4-port SRS resource, maximum rank, codebook subset, etc.

[0163] SRI indicates a 2-port SRS resource. In this example, a 2-port SRS resource requires 4 bits for precoding and layer number indication. Therefore, 2 bits remain in Z.

[0164] Z may indicate zero, one, or both of the single-port SRS resources. If one or both of the single-port SRS resources are indicated, PUSCH can consist of up to four layers. This can occur when the precoding and layer count indicate two layers based on a two-port SRS resource, and Z indicates two single-port SRS resources. The first two antenna ports of the PUSCH DMRS may correspond to two-layer SRS, and the next two DMRS antenna ports may correspond to two single-port SRS resources, or vice versa. PUSCH DMRS antenna ports 0 and 1 may use spatial-domain transmit filters based on the two-port SRS resource, and the precoder is applied based on the precoder indicated in the precoding information and layer count fields. PUSCH DMRS antenna port 2 may use spatial-domain transmit filters and precoders based on the first single-port SRS resource. PUSCH DMRS antenna port 3 may use spatial-domain transmit filters and precoders based on the second single-port SRS resource.

[0165] In various examples, a single-port SRS resource within SRSRS can be indexed in a similar manner to how any SRS resource within SRSRS is indexed, for example, based on the SRS resource ID within the single-port SRS resource, or according to its ordered position within the single-port SRS resource in the list of SRS resources configured for SRSRS.

[0166] In the various examples described above, the set of SRS resources is indicated by a combination of the SRI for CBB and some form of additional SRS resource indicator for NCBB operation, which can be embedded in unused bits (e.g., Z in the above examples) in the DCI field of the precoder and layer number. Using the SRI for CBB, the SRS resources indicated in the first step were represented by S. SRS resources indicated by the additional SRS resource indicators were represented by S', S'', etc., if they exist. In some cases, S is mapped to the PUSCH antenna port with the lowest antenna port index, S' is mapped to the next lowest, and so on. This allows for some flexibility in mapping SRS resources to PUSCH layers.

[0167] Figure 10 illustrates a high-level procedure covering the various examples described above. The UE may be configured, for example, for CBB PUSCH operation. Various other UE capability reports and configurations / instructions may be performed prior to step 1, for example, as described herein.

[0168] Figure 10 is a flowchart of the procedure for dynamically selecting CBB or NCBB operation using DCI fields within legacy DCI for PUSCH scheduling.

[0169] In step 1, the UE successfully decodes the DCI carrying, for example, a UL grant in format 0_0, 0_1, or 0_2.

[0170] In step 2, the UE reads the SRI field assuming CBB operation. The number of bits in the SRI field may depend on the number of SRS resources in SRSRS (e.g., codebook or "mixed").

[0171] In step 3, the UE determines whether the SRS resource S indicated by the SRI is a single-port SRS resource or a multi-port SRS resource. If S is a multi-port SRS resource, the UE proceeds to step 4 and performs a legacy CBB operation. If it is a single-port SRS resource, the UE proceeds to step 6, which corresponds to an NCBB operation.

[0172] In step 4, the UE reads the precoder and layer count fields within the DCI, for example, as in legacy CBB operation.

[0173] In step 5, the UE applies the specified precoder and number of layers to the PUSCH being transmitted. The spatial domain transmit filter for the PUSCH is configured to follow the spatial relationship configured for the specified multiport SRS, or, for example, the default spatial relationship if no spatial relationship is configured.

[0174] If the SRI selects a single-port SRS resource in step 3, the UE extracts Z from the DCI field for the precoder and layer count in step 6. The UE may assume that the number of bits in this field is the same as when a multi-port SRS was selected in step 3.

[0175] In step 7, the UE uses Z to select zero, one, or more single-port SRS resources, for example, as in the case of SRS resource instruction for NCBB operation. The single-port SRS resources may be selected from the same SRSRS used in steps 2 and 3, e.g., from the SRSRS for codebooks, or from different SRSRS, e.g., from the SRSRS for non-codebooks. If S is not selected by Z, S may, in some cases, be included in the set anyway. In other cases, if S is not selected by Z, S is not included in the set.

[0176] In step 8, the UE applies one or more sets of single-port SRS resources to the PUSCH, for example, according to NCBB operation, to determine, for example, the number of PUSCH layers and precoders and / or spatial domain transmit filters to apply to each PUSCH layer. In step 9, PUSCH is sent based on the result of step 5 or step 8.

[0177] Consider the following examples: The UE is configured with one or more SRSRS for the BM. The UE is configured with a txConfig in IE PUSCH-Config set in the codebook. The UE is configured with "full, partial, and noncoherent" codebook subsets, for example, the parameter codebookSubset is set to "fullyAndPartialAndNonCoherent" in IE PUSCH-Config. The UE is configured with a maximum rank = 4 for PUSCH. The UE is configured with SRSRS for the codebook, having three SRS resources: one 4-port SRS resource and two single-port SRS resources.

[0178] A 4-port SRS resource has a spatial relationship configured and / or directed to the SRS resource for the BM. In a TRP-RP scenario, the spatial domain transmit filter used for the SRS for the BM may be suitable for UL reception at the RP. The network can perform measurements regarding the SRS for the BM at the RP and conclude that the configured / directed SRS resource is appropriate, for example, by comparing RSRP or SINR.

[0179] The precoders and spatial domain transmit filters for the two single-port SRS resources are based on DL RS, for example, their spatial relationship, associated CSI-RS, and / or default spatial relationship. In a TRP-RP scenario, the precoders and spatial domain transmit filters used for these two single-port SRS resources may be suitable for UL transmits to one or more TRPs.

[0180] The UE successfully decodes the DCI carrying the UL grant. The UE reads the SRI field in the DCI based on the assumption of CBB operation (e.g., txConfig=codebook). In this example, the SRI field is 2 bits = ceil(log2(N SRS )) and here, N SRS =3 is the number of SRS resources in SRSRS for the codebook. If the SRI field indicates a 4-port SRS resource, the UE uses the precoder and layer count in the field to operate a legacy CBB push transmit. In this example, the precoder and layer count field is 6 bits.

[0181] If the SRI field instead indicates one of the single-port SRS resources, the UE uses the precoder and layer number of the field to operate the NCBB PUSCH transmission. The same bit width can be assumed. The UE extracts Z from the field, where Z is the two LSBs of the field, e.g., two bits, precoder and layer number, in this example. Since SRSRS has two single-port SRS resources, Z is used to select a row in table 7.3.1.1.2-31 of 3GPP TS38.212, and N SRS = 2. Paste the relevant section of the table into Table 5 in Appendix 2. Z is used to select a row. The right column indicates which of the two single-port SRS resources will be selected.

[0182] Based on the previous step, a PUSCH is sent. If a 4-port SRS resource was specified, the PUSCH is sent using legacy CBB mode based on the specified precoding and number of layers. If a single-port SRS resource was specified, the PUSCH is sent using NCBB operation based on the single-port SRS resource specified by Z.

[0183] In another example, if the UE is configured with NCBB and CBB operation on the BWP, the UE expects bits in the DCI scheduling PUSCH (e.g., DCI format 0_0, 0_1, or 0_2) that indicate whether the NCBB or CBB operation applies to the field bit width, field interpretation, and / or scheduled PUSCH transmission. The bit field may be represented, for example, as PUSCHMode.

[0184] If PUSCHMode indicates CBB operation, DCI may select SRS resources from the SRSRS configured for the codebook (based on the SRI field for CBB operation), as well as the corresponding precoder and layer count (based on the precoder and layer count field for CBB operation). If PUSCHMode instructs NCBB operation, DCI may select one or more SRS resources from the SRSRS configured for non-codebook operation (based on the SRI field for NCBB operation).

[0185] [Improvements for the PUSCH Repetition] In some cases, a transport block may be repeatedly transmitted over a PUSCH, for example, to improve reliability and / or coverage. To further improve reliability, various repetitions, e.g., PUSCH opportunities, may be transmitted to different points, e.g., a TRP and / or an RP. For example, a first repetition may be transmitted to a TRP and a second repetition to an RP, or vice versa. Figure 16 illustrates four repetitions across four PUSCH opportunities in four consecutive slots. In this example, the first and third repetitions are based on NCBB operation, with precoding and spatial domain transmit filters based on DL RS from the TRP. These may constitute a first set of PUSCH opportunities. The second and fourth repetitions are based on CBB operation, with precoding indicated by DCI and spatial domain transmit filters based on SRS for BM. This allows these PUSCH repetitions to target RPs that do not transmit DL RS. These may include a second set of PUSCH opportunities, separate from the first set.

[0186] In some cases, the UE may first transmit N1 repetitions using a first transmission mode, e.g., NCBB, and then transmit N2 repetitions using a second transmission mode, e.g., CBB.

[0187] Figure 11 shows an exemplary repetition timing diagram for PUSCH, where NCBB PUSCH is intended for reception at TRP and CBB is intended for reception at RP.

[0188] In various cases, a PUSCH opportunity repeats in consecutive slots. In various cases, a PUSCH opportunity repeats in non-consecutive slots, for example, every N slots, where N is an integer greater than 1. In various cases, a PUSCH opportunity repeats within a slot, for example, back to back, or between opportunities using one or more symbols. In various cases, PUSCH opportunities partially or completely overlap in time. In various cases, repeated PUSCHs are non-overlapping, partially overlapping, or completely overlapping in frequency. That is, repeated PUSCH opportunities can be FDM-ified. In some cases, different spatial relationships apply to different separate sets of resource blocks within the same PUSCH opportunity carrying TBs.

[0189] In some cases, different spatial relationships apply to different layers (or sets of layers) of PUSCH.

[0190] [Multi-DCI approach] In some cases, multiple push repetitions are scheduled by multiple DCIs, for example, DCI formats 0_0, 0_1, or 0_2. For example, the number of DCIs is equal to the number of different precoding and spatial domain transmit filters used for the repeated push opportunities.

[0191] In various cases, the first DCI directs the time-frequency resources for the first PUSCH repetition.

[0192] In some cases, the second DCI directs the time-frequency resources for the second Push repetition. In some cases, if the UE is configured with multi-DCI scheduling for Push repetition, the UE determines that the second DCI directs or can direct the repetition. The UE may determine that the second DCI schedules the repetition based on various fields within the DCI.

[0193] To determine whether a second DCI schedules a PUSCH repetition, one or a combination of the following three conditions may be used, possibly in conjunction with other conditions: First, the "HARQ process count" is the same as that of the first DCI. Second, the "new data indicator" does not show new data compared to the first DCI, for example, it is not toggled. Third, a new DCI field, for example, a bit, indicates that the DCI is scheduling a PUSCH repetition. The second DCI may need to be sent within a specific time after the first DCI.

[0194] Each of the DCIs may carry an SRI field. Each or a subset of the DCIs may carry precoding and layer count fields. According to various examples described herein, a subset of DCIs, for example, one DCI, may schedule push transmissions based on NCBB operation by, for example, indicating one or more single-port SRS resources. A subset of DCIs, for example, one DCI, may schedule push transmissions based on CBB operation by, for example, indicating multi-port SRS resources, precoders, and layer counts.

[0195] While a multi-DCI approach may require a higher PDCCH load, it offers the advantage of more flexible control of PUSCH at different points, such as different time and frequency resource allocations, MCS, power control, and precoding.

[0196] [Single DCI approach] In some cases, multiple push repetitions may be scheduled by a single DCI, for example, DCI format 0_0, 0_1, or 0_2.

[0197] In some cases, the UE may be configured to perform multiple PUSCH repetitions, for example, using uplink bundling or aggregation.

[0198] In some cases, the PUSCH repetition and its pattern are configured by higher-layer signaling (e.g., RRC signaling, MAC CE signaling, etc.). The configuration and pattern of the PUSCH repetition may include a set of spatial relationships used for PUSCH opportunities and an uplink pattern following the first PUSCH transmission. Once configured, the UE may be activated by a DCI to begin operating in PUSCH repetition mode, and may also be deactivated by another DCI.

[0199] For a single DCI to schedule push transmissions to multiple points, such as TPR and RP, the DCI may need to specify multiple values ​​for one or more of several parameters, such as the following four items: First, SRI, for example, to enable different precoding and / or spatial domain transmit filters to different points. Second, precoding and layer count, for example, to enable different precoding and / or spatial domain transmit filters to different points. Third, time and frequency resources. Fourth, frequency hopping. This may require a new DCI format.

[0200] In legacy operation without multipoint repetition, the SRI can indicate either one SRS resource for CBB operation or one or more SRS resources for NCBB operation. One approach is for the network to configure and / or indicate an SRI value (indicated by the SRI field in the DCI) corresponding to one or more SRS resources, even for CBB operation, via MAC CE. In other words, if the UE is configured for such operation, the SRI value may be configured / indicated by the network to correspond to two SRS resources, rather than the SRS resource directly corresponding to the SRI value. In some cases, if the UE is configured for such operation, even if the UE is operating in CBB mode, the SRI is interpreted according to a table for NCBB operation, which can select one or more SRS resources. However, if multiple SRS resources are indicated, it may not support multilayer transmission based on those multiple SRS resources, as in NCBB operation. Instead, the multiple indicated SRS resources may be applied to different PUSCH opportunities, for example, one SRS resource per opportunity. In some cases, a subset of multiple SRS resources, such as a single-port SRS resource, may be applied to the same PUSCH opportunity, thereby providing a multi-layer NCBB PUSCH, while another subset of multiple SRS resources, such as a multi-port SRS resource, may be applied to a different PUSCH opportunity, thereby providing a single-layer or multi-layer CBB PUSCH.

[0201] In some cases, DCI may include multiple fields, for example two, for precoding and layer count. These may be used to support CBB push transmissions to multiple points, for example, two different RPs that may require different precoders and / or layer counts.

[0202] For example, if the SRI for CBB operation is enhanced to support the instruction of multiple SRS resources, as described above, the SRI may instruction two different SRS resources, for example, two different multiport SRS resources within SRSRS for a codebook. In this case, the first precoder and layer count, based on the first precoder and layer count field in the DCI, may apply to a first set of PUSCH opportunities. The second precoder and layer count, based on the second precoder and layer count field in the DCI, may apply to a second set of PUSCH opportunities, separate from the first set, for example.

[0203] In some cases, DCI includes only one field for precoding and layer count, which may limit the number of different RPs to which a UE can send a PUSCH within a repeated PUSCH transmission. PUSCH transmissions to different RPs may require different precoders and layer counts. Conversely, since NCBB PUSCH typically does not require precoder and layer count indications, CBB PUSCH transmissions combined with NCBB PUSCH transmissions can be combined for multipoint PUSCH transmissions.

[0204] In one example, the SRI field in the DCI indicates a multiport SRS resource and one or more, for example, two, singleport SRS resources. A multiport SRS may have a spatial relationship with an SRS for a BM, which may be selected for transmission to the RP. One or more singleport SRS resources may have a DL RS or an associated CSI-RS as a spatial relationship. The UE may apply the precoder and layer count from the first precoder and layer count field in the DCI to a CBB PUSCH transmitted on a first set of PUSCH opportunities. In one example, the UE may apply, for example, an NCBB PUSCH transmitted on a second set of PUSCH opportunities, separate from the first set, based on the set of singleport SRS indicated by the SRI field.

[0205] In another example, each indicated SRS resource is assigned to a set of push opportunities, and these sets may be separate. For example, if the SRI field indicates four SRS resources, one of which is a multi-port SRS resource and three are single-port SRS resources, the UE may assign one set of push opportunities to the multi-port SRS resource and apply the precoder and layer numbers from the first precoder and layer number field in the DCI for CBB push transmissions. The UE may assign one set of push opportunities to each single-port SRS resource, so that, for example, the corresponding push transmissions may be limited to a single layer.

[0206] In some cases, the number of repetitions and / or the number of repetitions corresponding to different SRS resources are configured by the RRC or indicated by MAC CE or DCI. This information can be used by the UE to assign SRS resources to a set of PUSCH opportunities. For example, the UE is informed that a PUSCH will be repeated in a PUSCH based on two different sets of SRS resources. The SRI field may indicate three SRS resources, namely one multiport SRS and two single-port SRS resources. The multiport SRS resource may be restricted to being assigned to a first set of PUSCH opportunities. Since the UE knows there is only one other set of SRS resources for a second set of PUSCH opportunities, the UE may infer that both single-port SRS resources should be mapped to the same PUSCH, e.g., a 2-layer NCBB PUSCH, based on the fact that the two single-port SRS resources should be transmitted in the second set of PUSCH opportunities. On the other hand, if the UE is notified that a PUSCH will be repeated with PUSCH based on three different sets of SRS resources, the UE will assign two single-port SRS resources to one set of PUSCH opportunities, for example, a single-layer PUSCH based on a single-port SRS resource will be sent in a different set of PUSCH opportunities.

[0207] In some cases, for example, if the UE is configured with multiple SRSRSs, such as two SRSRSs, separate DCI fields are used for SRSRS selection that can correspond to TRP selection.

[0208] For example, the SRSRS selection field may select between SRSRS, such as one of two configured SRSRS (e.g., an NCBB set and a CBB set). For example, the SRSRS selection field may select between a push transmission based on one SRSRS that can correspond to a single TRP and a push transmission based on multiple SRSRS, such as two SRSRS, that can correspond to transmissions to multiple TRPs. For example, the SRSRS selection field may select the mapping between SRSRS and push opportunities, for example, which SRSRS is mapped to which push opportunity when a push is repeated. For example, the SRSRS selection field may select one or both SRSRS, and if two SRSRS are selected, it may also indicate the mapping to transmission opportunities.

[0209] For example, a 2-bit SRSRS selection field could indicate the following for code point values ​​from 0 to 3:

[0210] Code point 0 may instruct the selection of a first SRSRS. In some cases, the first SRI field is used to indicate the SRS resources within the selected SRSRS, and the second SRI field is unused. In some cases, the second SRI field is used to indicate the SRS resources within the selected SRSRS, and the first SRI field is unused.

[0211] Code point 1 may instruct the selection of a second SRSRS. In some cases, the first SRI field is used to indicate the SRS resources within the selected SRSRS, and the second SRI field is unused. In some cases, the second SRI field is used to indicate the SRS resources within the selected SRSRS, and the first SRI field is unused.

[0212] Code point 2 may instruct the mapping sequence from the first SRSRS to the PUSCH opportunity to select both SRSRS. In some cases, the first SRI field is used to indicate the SRS resources in the first SRSRS, and the second SRI field is used to indicate the SRS resources in the second SRSRS. In some cases, the first SRI field is used to indicate the SRS resources in the second SRSRS, and the second SRI field is used to indicate the SRS resources in the first SRSRS.

[0213] Code point 3 may instruct the mapping sequence from the second SRSRS to the PUSCH opportunity to select both SRSRS. In some cases, the first SRI field is used to indicate the SRS resources in the first SRSRS, and the second SRI field is used to indicate the SRS resources in the second SRSRS. In some cases, the first SRI field is used to indicate the SRS resources in the second SRSRS, and the second SRI field is used to indicate the SRS resources in the first SRSRS.

[0214] In some cases, the SRSRS with the lower ID is the first SRSRS, and the other SRSRS is the second SRSRS. In other cases, with one SRSRS configured for NCBB and one for CBB, regardless of ID, the NCBB SRSRS is the first SRSRS and the CBB SRSRS is the second SRSRS. In other cases, the CBB set is the first and the NCBB set is the second.

[0215] In some cases, a PUSCH may be repeated, for example, if a single SRSRS is selected by applying the same SRSRS to each PUSCH opportunity. For example, repetition (including the number of repetitions) or no repetition may be indicated via the time domain resource allocation field.

[0216] In some cases, if the SRSRS indicator field indicates CBB SRSRS, the DCI field for precoding (e.g., TPMI in abbreviated form) and layer count is applicable to the PUSCH opportunities to which CBB SRSRS is mapped, including cases where CBB SRSRS is mapped to a subset or all of the scheduled PUSCH opportunities. In some cases, if the SRSRS indicator field does not indicate CBB SRSRS, the DCI field for precoding (e.g., TPMI in abbreviated form) and layer count may be unused.

[0217] In some cases, for example, in push repetitions based on NCBB and CBB push, the number of layers (i.e., rank) may be constrained to be the same for NCBB push opportunities and CBB push opportunities. This may be used to limit the size of DCI fields, e.g., SRI fields and / or fields for precoding and the number of layers.

[0218] In some cases, the SRI field used to indicate an SRS resource within NCBB SRSRS, which may be the first or second SRI field in various examples herein, may be used to determine the entries (e.g., TPMI) in the fields for precoding and layer number, which may include only combinations of precoding (e.g., TPMI) corresponding to the indicated layer number of the SRI field used to indicate an SRS resource within NCBB SRSRS. For example, if the SRI field used to indicate an SRS resource within NCBB SRSRS indicates a single-layer push transmission, then the fields for precoding and layer number may indicate a single-layer precoding (e.g., TPMI) entry. In some cases, this field may be considered a precoding field, such as the TPMI field. The number of bits N2 in the precoding (e.g., TPMI) field may be determined by the maximum number of precoding and layer number (e.g., TPMI) code points per rank among all ranks associated with the SRI field used to indicate an SRS resource within NCBB SRSRS. For each rank x, the first K x The code point is a K of rank x associated with the SRI field. x It is mapped to a precoder (e.g., TPMI), and the rest (2 N2 -K x Code points are reserved. The maximum number of precoding and layer count (e.g., TPMI) code points per rank may depend on configured codebook subset limits, e.g., noncoherent, partial and noncoherent, or full, partial and noncoherent subsets. In some cases, when determining the maximum number of code points per rank, precoding (e.g., TPMI) ranks that are greater than the number of SRS resources in NCBB SRSRS are not considered.

[0219] For example, consider a case where there are four SRS resources within SRSRS for NCBB operation, and the maximum rank is 4. Further considering a codebook (e.g., a non-coherent subset) with four single-layer TPMIs, six two-layer TPMIs, one three-layer TPMI, and one four-layer TPMI, the maximum number of TPMI code points per rank is 6 (corresponding to rank x=1), which means that the number of bits (N2) in the pre-coding (e.g., TPMI) field can be 3. Thus, K1=4, K2=6, K3=1, K4=1.

[0220] In some cases, fields for precoding and layer count (e.g., TPMI) may be used to determine the entries in the SRI field used to indicate an SRS resource within NCBB SRSRS, which may be the first or second SRI field in the various examples herein. In some cases, the SRI field may contain only the SRI combinations of the fields for precoding and layer count that correspond to the indicated layer count. For example, if the fields for precoding and layer count indicate a single-layer push transmission, the SRI field used to indicate an SRS resource within NCBB SRSRS may indicate a single-layer entry. The number of bits N3 in the SRI field (for NCBB) may be determined by the maximum number of SRI code points per rank among all ranks associated with the fields for precoding and layer count. For each rank x, the first K x Code points are K of rank x associated with the pre-coding and layer count fields. x Mapped to SRI, the remaining (2 N3 -K x The code points will be reserved.

[0221] [Joint transmission] In some cases, joint multipoint push transmission can be beneficial, for example, to improve spectral efficiency and / or reliability. For example, different layers of a push transmission may target different points, e.g., one layer to a target relay point (TRP) and another to a relay point (RP). This may be feasible for a UE having multiple panels for UL transmission, for example, where a first layer is transmitted from a first panel and a second layer is transmitted from a second panel.

[0222] To enable such joint transmissions, a single DCI approach may be employed. Instead of assigning multiport SRS resources to a first PUSCH transmission and assigning one or more singleport SRS resources to one or more PUSCH transmissions different from the first, the multiport SRS resources are assigned to a set of layers of PUSCH, and one or more singleport SRS resources are assigned to a separate set of layers, distinct from the first set of PUSCH.

[0223] The number of layers in a scheduled PUSCH may be the sum of the specified number of layers and the number of specified single-port SRS resources. The specified number of layers may come from the precoder and layer count fields in the DCI of the specified multi-port SRS resource.

[0224] SRS resources can be indicated by the scheduling DCI, for example, by the SRI field.

[0225] [Multi-panel configuration] In the case of push repetition, one panel may suddenly be blocked, so it may be beneficial for reliability for a UE to send different pushes on different UE panels. If an SRS resource or SRSRS is already associated with a panel, push repetition transmissions from different panels can be achieved by directing the SRS resource in DCI, which is associated with a different panel for different push opportunities.

[0226] [Improvements for SRS beam sweeping] A UE may be configured with one or more SRSRSs (SRSRS for BMs) whose usage is "beamManagement". Generally, if no spatial relationships are configured and / or indicated for an SRS resource, it may be up to the UE to choose which precoder and / or spatial domain transmit filter to use for that SRS resource. SRS for BMs are typically not configured / indicated by spatial relationships so that a UE may implement UL beam sweeping using SRS for BMs. However, it should be noted that how UL beam sweeping is implemented, if any, may be up to the UE.

[0227] However, while SRS resources from different SRSRSs for BM can be transmitted with the same symbol, simultaneous transmission of different SRS resources from the same SRSRS for BM may be prohibited. This characteristic can be used to transmit different SRS resources within an SRSRS for BM from the same UE panel. In some UE implementations, for example, if analog Tx beamforming is used, it may be impossible to transmit multiple different beams simultaneously from the same panel. However, it may be possible to transmit a first beam from a first panel and a second beam from a second panel simultaneously. In these examples, different beams can be used to transmit different SRS resources.

[0228] A physical panel may be an antenna system, for example, a rectangular arrangement of cross-polarized antenna elements or another arrangement of antennas. In various cases, the panel's antennas are connected to a TRX or multiple trees. In various cases, the same panel is used for both transmission and reception at the UE. In some cases, different sets of panels may be used for transmission and reception. In some cases, for example, to conserve power, panels containing the corresponding TRX may be switched on and off.

[0229] In some cases, logical panels may be defined. The mapping of logical panels to physical panels may depend on the UE. For example, a logical panel may be mapped to a physical panel. In another example, a logical panel may be mapped to multiple physical panels. In yet another example, multiple logical panels may be mapped to physical panels. Some implementations may not use physical panels. In such cases, a logical panel may be mapped to a set of antennas.

[0230] In some cases, the UE reports its capacity to the network in terms of the number of panels (e.g., physical and / or logical) for transmission and / or reception.

[0231] In some cases, a UE panel ID (or index or pool ID) is defined. Such a panel ID may correspond to a physical panel and / or a logical panel.

[0232] In some cases, the UE may be configured to provide a panel ID along with the measurement results for DL ​​RS, e.g., L1-RSRP. The panel ID may indicate which panel the reported DL RS was measured on. If DL measurements were performed on multiple panels, the panel ID may represent the dominant panel, e.g., the panel with the highest individual measurement, e.g., the panel with the highest L1-RSRP per panel.

[0233] In some cases, an SRSRS can be configured using panel IDs (RRC), as illustrated in Configuration Example 6 of Appendix 1. Such panel IDs can indicate from which panel (physical or logical) an SRS resource within the SRSRS should be transmitted. For example, an SRSRS for a BM can be configured using panel IDs that determine from which panel the corresponding SRS resource is transmitted.

[0234] Example 6 in Appendix 1 shows an example of an SRS-Config information element having a panel ID configuration in SRSRS.

[0235] In some cases, an SRSRS may be configured using multiple panel IDs (RRC), such as in the list exemplified in Configuration Example 7 of Appendix 1. These IDs may indicate from which (multiple) panels SRS resources within the SRSRS should be transmitted. In some cases, the number of SRS resources within an SRSRS must be greater than or equal to the number of panel IDs configured for the SRSRS.

[0236] Example 7 in Appendix 1 shows an example of an SRS-Config information element having a panel ID configuration for SRSRS.

[0237] In some cases, the UE may be configured with SRSRS for codebooks and SRSRS for "noncodebooks," as described above. Such a configuration may be constrained so that the SRSRS for codebooks are configured / directed to different panels than the SRSRS for "noncodebooks." In some cases, an association between SRSRS and panels is specified. For example, the SRSRS for codebooks is associated with the lowest panel ID, e.g., 0. In another example, the SRSRS for noncodebooks is associated with the lowest panel ID, e.g., 0. In some cases, one PUSCH transmit mode and corresponding SRSRS may be configured per UE panel, for example, using a configuration like Configuration Example 6 in Appendix 1. In some cases, up to one SRSRS may be configured for codebooks and up to one SRSRS for noncodebooks. In this case, such SRSRS may need to be associated with multiple panels, meaning that a configuration like the one illustrated in Configuration Example 7 in Appendix 1 may be appropriate.

[0238] In some cases, the panel ID may be indicated and / or activated and / or deactivated by the MAC CE, as illustrated in Figure 12, for example. This example is based on the use of one or more reserved bits in legacy MAC CEs, such as aperiodic and / or semi-persistent SRS activation / deactivation MAC CEs, as described in version 16.0.0 of the March 2020 release of 3GPP TS38.321. The following are 12 exemplary fields.

[0239] A / D - This field indicates whether to activate or deactivate the specified SRS resource set.

[0240] SRS Resource Set Cell ID - This field indicates the identification information of the serving cell containing the activated / deactivated SRS resource set.

[0241] SRS Resource Set BWP ID - This field indicates the UL BWP as the code point in the DCI Bandwidth Partial Indicator field.

[0242] C - This field indicates whether an octet exists that contains the Resource Serving Cell ID field and the Resource BWP ID field.

[0243] SUL - This field indicates whether MAC CE applies to a normal UL carrier or SUL carrier configuration.

[0244] SRS Resource Set ID - This field indicates the SRS resource set ID to be activated or deactivated.

[0245] Fi - This field indicates the type of resource used as the spatial relationship of SRS resources within the SRS resource set indicated by the SRS resource set ID field.

[0246] Resource ID i - This field contains the identifier of the resource used for the spatial relationship derivation of SRS resource i.

[0247] Resource serving cell ID i - This field indicates the identification information of the serving cell where the resource used for the spatial relationship derivation for SRS resource i is located.

[0248] - This field indicates the UL BWP as the code point of the DCI bandwidth part indicator field where the resource used for the spatial relationship derivation of SRS resource i is located.

[0249] R: Reserved bit.

[0250] P: Panel ID.

[0251] FIG. 12 illustrates an example of the panel ID indication P in the MAC CE for, for example, aperiodic or semi - persistent SRS activation / de - activation in this case.

[0252] In this example, the panel indication P is 2 bits. These bits can directly represent the panel ID indicated / activated / de - activated for this SRSRS. For example, "00" represents panel ID = 0, "01" represents panel ID = 1, etc. In some cases, P is used to indicate a row in a table, which in turn, for example, as in Table 6 of Appendix 2, if it exists, defines which panel ID to use for this SRSRS. The value "no panel is indicated" may mean that the UE can select a panel for SRSRS transmission.

[0253] In some cases, P is a bitmap, and each bit represents a panel. If a bit is set, the transmission of SRS resources from SRSRS becomes valid for the corresponding panel. If a bit is not set, SRSRS should not be transmitted from the panel. In some cases, for example, if P is a bitmap having a plurality of bits set to "1", a plurality of panels may be indicated for activation / deactivation by MAC CE, where the bits set to 1 indicate to the UE to activate the corresponding panel or to activate the SRS transmission (corresponding to the SRSRS indicated by MAC CE) on the corresponding panel. Similarly, the bits set to 0 indicate to the UE to deactivate the corresponding panel or to deactivate the SRS transmission (corresponding to the SRSRS indicated by MAC CE) on the corresponding panel.

[0254] In some cases, one or more panels may be indicated by P only when SRS is activated. For example, when deactivated, the bits in P may be fixed to 0.

[0255] In the case of aperiodic SRSRS, the panel ID may be indicated by DCI that triggers the aperiodic SRSRS, for example, within the SRS request field.

[0256] In some cases, for example, as in Configuration Example 7 of Appendix 1, the panel ID indicated by MAC CE (e.g., P) or by DCI corresponds to one of the panels configured for SRSRS.

[0257] In some cases, the DCI scheduling the PUSCH will specify a panel ID. For example, considering the NCBB PUSCH operation, an NCBB SRS resource uses DL RS to derive a precoder and spatial domain transmit filter. Such an SRS resource is received by multiple panels, and the UE may maintain a spatial domain receive filter for each panel to receive the DL RS. Thus, the UE may select a precoder and spatial domain transmit filter for the PUSCH that corresponds to the panel specified by the DCI scheduling the PUSCH.

[0258] In some cases, the configuration and / or designated panel IDs described above do not indicate which panel the UE should send SRSRS from. Instead, the configuration and / or designated panel IDs indicate the panel that the UE should avoid when sending SRSRS.

[0259] In an alternative approach, an SRS resource may be configured / directed to a reference RS, such as an SRS or DL ​​RS, using a negative spatial relationship. A negative spatial relationship may mean that the target SRS resource should not be transmitted / received using the same spatial domain filter as the reference RS in the negative spatial relationship. In another example, an SRSRS may be configured / directed to a reference RS, such as an SRS or DL ​​RS, or to a reference SRSRS. Such a negative spatial relationship may mean that an SRS resource within a target SRSRS should not be transmitted / received using the same spatial domain filter as the reference RS or any SRS within the reference SRSRS in the negative spatial relationship. In some cases, the UE should transmit the target SRS resource (or SRSRS) using a spatial domain filter that is spatially as far apart as possible from the spatial domain filters used to transmit / receive the reference RS (or reference SRSRS) in the negative spatial relationship. In some cases, the UE should (or may) send the target SRS resource (or target SRSRS) from the panel that is spatially as far apart as possible from the panel used to send / receive the reference RS (or reference SRSRS) in a negative spatial relationship.

[0260] Figure 13 illustrates an example of a negative spatial relationship. SRS9 is configured using a negative spatial relationship with respect to SRS2. For example, this means that the UE transmits (or can transmit) SRS9 using the spatial domain transmit filter that is most spatially separated from SRS2.

[0261] The normal (or positive) spatial relation of an SRS dictates how the UE should transmit the SRS with respect to precoding and spatial domain transmit filtering. Therefore, for an SRS with a positive spatial relation, the UE has no choice in selecting the SRS transmit beam. Thus, the spatial relation is not typically configured for an SRS for a beam-beam, since it is assumed that the UE may select the SRS transmit beam, for example, to implement UL Tx beam sweeping.

[0262] The purpose of negative spatial relationships is to maintain a high degree of flexibility for the UE in selecting SRS transmit beams. Negative spatial relationships instruct the UE which UL Tx beams and / or panels to avoid when selecting UL Tx beams for SRS. In addition to this restriction, the UE still has the flexibility to select UL Tx beams for SRS, for example, to perform restricted UL beam sweeping on a subset of UL Tx beams and / or a subset of UL transmit panels.

[0263] Please note that "UL Tx beams" can be used with precoding and / or spatial domain transmit filters.

[0264] In various cases, an SRS resource or SRSRS cannot be constructed using both positive and negative spatial relationships. Consider two examples.

[0265] In the first example, SRSRS (for example, for a codebook) is composed of a single-port SRS resource and a multi-port SRS resource. The single-port SRS resource is configured / indicated using DL RS as a spatial relationship. The multi-port SRS resource is configured / indicated using the single-port SRS resource as a negative spatial relationship. Since the multi-port SRS resource is not configured using a positive spatial relationship, it does not need to be transmitted using a specific spatial domain transmit filter.

[0266] However, due to negative spatial relationships, the (target) multiport SRS should use a different spatial domain transmit filter than the (reference) singleport SRS, or transmit from a different panel than the singleport SRS.

[0267] If the UE has two panels, a single-port SRS is transmitted on the first panel, and if, for example, the first panel is optimal for receiving the corresponding DL RS, then the (target) multi-port SRS is transmitted from the second panel due to the negative spatial relationship. If the UE rotates so that the DL RS is received on the second panel instead, then the (target) multi-port SRS is transmitted from the first panel without reconfiguration / instruction due to the negative spatial relationship.

[0268] In the second example, an SRSRS is configured for a BM. Here, none of the SRS resources within the SRSRS are configured using positive spatial relationships, meaning it is up to the UE to select the UL transmit beam for the SRS resources. The SRSRS is configured / directed using negative spatial relationships with (reference) SRSRS for non-codebook users or with (reference) SRS resources within an SRSRS for non-codebook users. For example, a single-port SRS resource within an SRSRS for non-codebook users has a DL RS configured / directed as a spatial relationship, which usually means the UE has little flexibility in selecting beams / panels for those SRS resources.

[0269] The UL transmit beam for the (target) SRS resource for the BM can be flexibly selected by the UE, subject to constraints imposed by negative spatial relationships. For example, the UE may perform UL beam sweeping over panels except for those used to transmit the reference SRS resource in a negative spatial relationship. Similarly, the UE may perform UL beam sweeping over any panel, as long as it avoids the spatial domain transmit filters used by any SRS resource within the reference SRS.

[0270] By allowing UEs to control which panel they use to transmit SRS for BM, the network can better utilize UL resources and reduce UL interference. Consider a scenario using a cell with a TRP and RP, as illustrated in Figure 14. The UEs in the cell have reported to the network that they have two panels. The network configures network-controlled UE panel operation (for the two UE panels). Furthermore, consider that the UEs use NCBB push transmissions to the TRP based on DL RS transmitted from the TRP. For push transmissions to the RP, the UEs use CBB transmissions, and the multiport SRSs have a spatial relationship to the SRSs for BM. NCBB and CBB operation may follow the various examples described above, e.g., UEs with CB-SRSRS, SRSRS for "non-Codebook", SRSRS for "codebook", and / or SRSRS for "mixed".

[0271] Figure 14 illustrates an exemplary scenario in which an SRS for a BM transmitted from one panel is present, in the direction of the RP in this case.

[0272] Since the UE uses one panel for receiving DL RS from the TRP and for transmitting UL signals and channels to the TRP, it may not need to transmit SRSRS for BM from that panel based on those DL RS. Instead, SRSRS for BM may be favorably transmitted from other panels so that the network can assess whether other panels are suitable for transmission to the RP.

[0273] If a UE reports a panel used to receive DL RS from a TRP and to transmit a single-port SRS for the purpose of sending an NCBB PUSCH to a TRP, the network may configure / instruct the UE to transmit SRSRS for BM from other panels. However, this may involve reconfiguration overhead and delays if circumstances change, for example, if the UE rotates.

[0274] In an alternative approach, the UE may be configured to transmit SRS for BM from one or more panels not used to transmit SRS resources, using DL RS as a spatial relationship, associated CSI-RS, or a default spatial relationship based on DL RS. In an alternative representation, the UE may be configured to avoid transmitting SRS for BM from panels used to transmit SRS resources, using DL RS as a spatial relationship, associated CSI-RS, or a default spatial relationship based on DL RS.

[0275] For example, a UE may be configured not to transmit any SRS resources within SRSRS for BM using the same spatial domain transmit filter used for receiving a particular DL RS or transmitting a particular SRS or SRSRS. Alternatively, a UE may be configured to avoid transmitting SRS resources within SRSRS for BM using the same spatial domain transmit filter used for receiving a particular DL RS or transmitting a particular SRS or SRSRS.

[0276] In other words, for example, if the UE rotates and the panel used by the UE for DL RS reception is changed, the UE can autonomously change the panel used for SRS transmission for the BM.

[0277] These techniques for panel or spatial region transmission filter avoidance can be configured, for example, in the SRS config, and thereby applied to all configured SRSs for the BM, as illustrated in Configuration Example 8 of Appendix 1. In some cases, this technique is applied only to periodic or semi-persistent SRSs.

[0278] Configuration Example 8 of Appendix 1 shows an exemplary SRS-Config information element having a configuration in the SRS-Config for panel selection for UL beam sweeping based on DL measurement.

[0279] In another example, the panel avoidance technique can be configured in the SRS resource set, as illustrated in Configuration Example 9. In this case, it is applied only to the configured SRSs. In this way, some SRSs for the BM can be configured to avoid the panel for transmitting DL-based UL, while other SRSs for the BM are still transmitted from any panel including any panel for transmitting DL-based UL. The code "-Cond beamManagement" may mean that "this field is optionally present (Need M) if the usage is beamManagement, and otherwise this field does not exist."

[0280] Configuration Example 9 of Appendix 1 shows an exemplary SRS-Config information element having a configuration in the SRS-ResourceSet for panel selection for UL beam sweeping based on DL measurement.

[0281] In some cases, panel avoidance can be based on the panel associated with the DL-based NCBB operation. The meaning of the association between the DL-based NCBB operation and the panel, or vice versa, can have multiple variations.

[0282] For example, a configuration and / or instruction may include one or more of the following: RRC configuration, instructions within a MAC CE, or instructions within a DCI. Instructions within a MAC CE may be in a semi-persistent SRS activation / deactivation MAC CE, aperiodic SRS spatial relation instruction MAC CE, SRS path loss reference RS activation / deactivation MAC CE, and / or CC list-based SRS activation / deactivation MAC CE. Instructions within a DCI may be, for example, a trigger for aperiodic SRS.

[0283] When a panel is associated with DL-based NCBB operation, for example, if an SRSRS with usage 'noncodebook / 'codebook / 'mixed' includes one or more SRS resources, e.g., a single port, then configuration and / or instruction can be achieved such that the active spatial relationship is DL RS and a spatial filter used to receive (and transmit) one or more DL RSs is associated with the panel. This can be achieved in several ways. Firstly, if a signal transmitted using a spatial filter, e.g., an SRS, is transmitted from the panel, then the spatial filter is associated with the panel, and / or if a signal received using a spatial filter, e.g., a DL RS, is received by the panel, then the spatial filter is associated with the panel.

[0284] In some cases, additional conditions may be added: for example, the measurement quality of DL RS received on the panel is sufficiently good, such as the measured values ​​of L1-RSRP, L1-RSRQ, and / or L1-SINR exceeding a configurable threshold.

[0285] In some cases, additional conditions may be added: The UE measures one, more, or all of the DL RS qualities (e.g., L1-RSRP, L1-RSRQ, L1-SINR) that function as spatial relationships in the SRSRS considered. These N DL RS quality measurements are x1, ..., x N It can be expressed as follows: Index p1, ..., pN Measurement values ​​were obtained from a panel having index a. For example, if all N measurements were obtained from the same panel having index a, then p1 = ... = p N = a. When DL RS i is measured on multiple panels, the highest quality measurement result and the corresponding panel are x. i and p i It is used for a set of quality measurements S, where a function f(S) is defined, which can be, for example, average(S), max(S), or min(S). The set of quality measurements obtained from panel i is S i It is represented as, for example, p k x = i (k=1, ..., N) k This is a set of SRSRS, for example, depending on the properties of f(), the highest f(S i ) or the lowest f(S i It is associated with panel i which has ).

[0286] [Example environment] The Third Generation Partnership Project (3GPP) develops technical standards for cellular communication network technologies, including radio access, core transport networks, and service capabilities, including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA® (commonly known as 3G), LTE (commonly known as 4G), and LTE Advanced standards. 3GPP is beginning to work on standardizing next-generation cellular technologies, referred to as New Radio (NR), also known as "5G." The development of 3GPP NR standards is expected to include a definition of next-generation radio access technology (new RAT), which is expected to include the provision of new flexible radio access below 6 GHz and new ultra-mobile broadband radio access above 6 GHz. Flexible radio access is expected to consist of new, backward-incompatible radio access in new spectrums below 6 GHz and is expected to include different operating modes that can be multiplexed together on the same spectrum to address a broad set of 3GPP NR use cases with diverse requirements. Ultra-mobile broadband is expected to include cmWave and mmWave spectrums, for example, providing opportunities for ultra-mobile broadband access for indoor applications and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with flexible sub-6GHz wireless access, utilizing cmWave and mmWave-specific design optimizations.

[0287] 3GPP has identified a variety of use cases that NR is expected to support, resulting in diverse user experience requirements for data rate, latency, and mobility. Use cases include the following common categories: high-speed mobile broadband (e.g., broadband access in high-density areas, ultra-high-speed indoor broadband access, broadband access in crowded areas, 50+Mbps everywhere, ultra-low-cost broadband access, mobile broadband in vehicles), critical communications, large-scale machine-type communications, network operations (e.g., network slicing, routing, migration and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communications, which may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network communication (V2N), vehicle-to-pedestrian communication (V2P), and communications between vehicles and other entities. Specific services and applications in these categories include, for example, surveillance and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based office, first responder connectivity, automotive ecall, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, haptic internet, and virtual reality. All of these use cases, as well as other use cases, are contemplated herein.

[0288] Figure 15A illustrates one embodiment of an exemplary communication system 100 in which the methods and apparatus described herein and claimed may be embodied. As shown in the figure, the exemplary communication system 100 may include radio transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g (which may be generally or collectively referred to as WTRUs 102), radio access networks (RANs) 103 / 104 / 105 / 103b / 104b / 105b, core networks 106 / 107 / 109, public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and a V2X server (or ProSe function and server) 113, but it will be understood that the disclosed embodiments intend any number of WTRUs, base stations, networks, and / or network elements. Each of WTRU102a, 102b, 102c, 102d, 102e, 102f, and 102g may be any type of device or apparatus configured to operate and / or communicate in a wireless environment. Each WTRU 102a, 102b, 102c, 102d, 102e, 102f, and 102g is depicted in Figures 15A to 1E as a handheld wireless communication device. However, in the diverse use cases envisioned for 5G wireless communication, each WTRU includes, or may be embodied by, any type of device or apparatus configured to transmit and / or receive radio signals. Examples of such devices or apparatus include user equipment (UEs), mobile stations, fixed or mobile subscriber units, pagers, mobile phones, personal digital assistants (PDAs), smartphones, laptops, tablets, netbooks, notebook computers, personal computers, wireless sensors, consumer electronics, wearable devices such as smartwatches or smart clothing, medical or eHealth devices, robots, industrial equipment, drones, and vehicles such as automobiles, trucks, trains or airplanes.

[0289] The communication system 100 may also include base stations 114a and 114b. Base station 114a may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, and 102c to facilitate access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and / or other networks 112. Base station 114b may be any type of device configured to wired and / or wirelessly interface with at least one of RRHs (remote radio heads) 118a, 118b, TRPs (transmit and receive points) 119a, 119b, and / or RSUs (roadside units) 120a and 120b to facilitate access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, other networks 112, and / or V2X servers (or ProSe functions and servers) 113. RRH118a, 118b may be any type of device configured to wirelessly interface with at least one of the WTRU102c to facilitate access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and / or other networks 112. TRP119a, 119b may be any type of device configured to wirelessly interface with at least one of the WTRU102d to facilitate access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, and / or other networks 112. RSU120a, 120b may be any type of device configured to wirelessly interface with at least one of the WTRU102e or 102f to facilitate access to one or more communication networks such as the core networks 106 / 107 / 109, the Internet 110, other networks 112, and / or V2X server (or ProSe function and server) 113.For example, base stations 114a and 114b could be a base transceiver base station (BTS), NodeB, eNodeB, Home NodeB, Home eNodeB, site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are described as single elements, it will be understood that base stations 114a and 114b can include any number of interconnected base stations and / or network elements.

[0290] Base station 114a may be part of RAN 103 / 104 / 105, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), and relay nodes. Base station 114b may be part of RAN 103b / 104b / 105b, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), and relay nodes. Base station 114a may be configured to transmit and / or receive radio signals within a specific geographic area that may be called a cell (not shown). Base station 114b may be configured to transmit and / or receive wired and / or radio signals within a specific geographic area that may be called a cell (not shown). A cell may be further divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, for example, one for each sector of the cell. In one embodiment, the base station 114a may employ multiple input multiple output (MIMO) technology and thus utilize multiple transceivers for each sector of the cell.

[0291] Base station 114a may communicate with one or more WTRUs 102a, 102b, and 102c via air interfaces 115 / 116 / 117, which may be any suitable radio communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). Air interfaces 115 / 116 / 117 may be established using any suitable radio access technology (RAT).

[0292] Base station 114b may communicate with one or more of the RRH 118a, 118b, TRP 119a, 119b, and / or RSU 120a and 120b via wired or air interface 115b / 116b / 117b, which may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). Air interface 115b / 116b / 117b may be established using any suitable radio access technology (RAT).

[0293] RRH118a, 118b, TRP119a, 119b and / or RSU120a, 120b may communicate with one or more WTRU102c, 102d, 102e, 102f via air interface 115c / 116c / 117c, which may be any suitable radio communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). Air interface 115c / 116c / 117c may be established using any suitable radio access technology (RAT).

[0294] WTRU102a, 102b, 102c, 102d, 102e, 102f, and / or 102g may communicate with each other via an air interface 115d / 116d / 117d (not shown), which may be any suitable radio communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115d / 116d / 117d may be established using any suitable radio access technology (RAT).

[0295] More specifically, as described above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRU 102a, 102b, 102c in RAN 103 / 104 / 105, or RRH 118a, 118b, TRP 119a, 119b and RSU 120a, 120b and WTRU 102c, 102d, 102e, 102f in RAN 103b / 104b / 105b may implement radio technologies such as Universal Mobile Communications System (UMTS) Terrestrial Radio Access (UTRA), thereby enabling the establishment of air interfaces 115 / 116 / 117 or 115c / 116c / 117c, respectively, using broadband CDMA (WCDMA). WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Advanced HSPA (HSPA+). HSPA may include High Speed ​​Downlink Packet Access (HSDPA) and / or High Speed ​​Uplink Packet Access (HSUPA).

[0296] In one embodiment, base stations 114a and WTRUs 102a, 102b, 102c, or RRHs 118a, 118b, TRPs 119a, 119b and / or RSUs 120a, 120b and WTRUs 102c, 102d within RAN 103b / 104b / 105b may implement radio technologies such as Advanced UMTS Terrestrial Radio Access (E-UTRA), thereby enabling the establishment of air interfaces 115 / 116 / 117 or 115c / 116c / 117c, respectively, using Long-Term Evolution (LTE) and / or LTE Advanced (LTE-A). In the future, air interfaces 115 / 116 / 117 may implement 3GPP NR technology. LTE and LTE-A technologies include LTE D2D and V2X technologies and interfaces (e.g., sidelink communication). 3GPP NR technology includes NR V2X technology and interfaces (e.g., sidelink communication).

[0297] In one embodiment, base stations 114a and WTRU102a, 102b, 102c in RAN103 / 104 / 105, or RRH118a, 118b, TRP119a, 119b and / or RSU120a, 120b and WTRU102c, 102d, 102e, 102f in RAN103b / 104b / 105b, support IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 Wireless technologies such as EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Pan-European Digital Mobile Telephone System (GSM®), GSM Advanced High-Speed ​​Data Rate (EDGE), and GSM EDGE (GERAN) can be implemented.

[0298] The base station 114c in Figure 15A may be, for example, a wireless router, Home NodeB, Home eNodeB, or access point, and may utilize any suitable RAT to facilitate wireless connectivity in localized areas such as offices, homes, vehicles, or campuses. In one embodiment, the base station 114c and WTRU 102e may implement wireless technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114c and WTRU 102d may implement wireless technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114c and WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell. As shown in Figure 15A, the base station 114b may have a direct connection to the internet 110. Therefore, base station 114c may not need to access the internet 110 via the core network 106 / 107 / 109.

[0299] RAN103 / 104 / 105 and / or RAN103b / 104b / 105b may communicate with core networks 106 / 107 / 109, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU102a, 102b, 102c, and 102d. For example, core networks 106 / 107 / 109 may provide call control, billing services, mobile location-based services, prepaid calls, internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication.

[0300] Although not shown in Figure 15A, it will be understood that RAN103 / 104 / 105 and / or RAN103b / 104b / 105b and / or core networks 106 / 107 / 109 may communicate directly or indirectly with other RANs employing the same or different RATs as RAN103 / 104 / 105 and / or RAN103b / 104b / 105b. For example, core networks 106 / 107 / 109 may communicate with another RAN (not shown) employing GSM radio technology, in addition to connecting to RAN103 / 104 / 105 and / or RAN103b / 104b / 105b, which may utilize E-UTRA radio technology.

[0301] Core networks 106 / 107 / 109 may also function as gateways for WTRUs 102a, 102b, 102c, 102d, and 102e to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing basic telephone services (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as the Transmit Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) within the TCP / IP Internet Protocol suite. Network 112 may include wired or wireless networks owned and / or operated by other service providers. For example, network 112 may include another core network connected to one or more RANs, which may employ the same or different RAT as RANs 103 / 104 / 105 and / or RANs 103b / 104b / 105b.

[0302] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multimode capability, for example, WTRUs 102a, 102b, 102c, 102d, and 102e may include multiple transceivers for communicating with different radio networks via different radio links. For example, WTRU 102e shown in Figure 15A may be configured to communicate with base station 114a which may employ cellular-based radio technology and base station 114c which may employ IEEE 802 radio technology.

[0303] Figure 15B is a block diagram of an exemplary apparatus or device configured for wireless communication according to an embodiment illustrated herein, such as WTRU102. As shown in Figure 15B, the exemplary WTRU102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, fixed memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and other peripherals 138. It will be understood that WTRU102 may include any partial combination of the aforementioned elements while maintaining consistency with one embodiment. Furthermore, the embodiments are intended to include, but are not limited to, base stations 114a and 114b, and / or nodes that base stations 114a and 114b may represent, including, in particular, transceiver base stations (BTS), NodeBs, site controllers, access points (APs), Home NodeBs, advanced Home NodeBs (eNodeBs), Home advanced NodeBs (HeNBs), Home advanced NodeB gateways, and proxy nodes, which may include some or all of the elements depicted in Figure 15B and described herein.

[0304] The processor 118 may be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120, and the transceiver 120 may be coupled to a transmit / receive element 122. Although Figure 15B depicts the processor 118 and transceiver 120 as separate components, it will be understood that the processor 118 and transceiver 120 may be integrated into an electronic package or chip.

[0305] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interfaces 115 / 116 / 117. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In a further embodiment, the transmit / receive element 122 may be configured to transmit and receive both RF signals and optical signals. It will be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of radio signals.

[0306] Furthermore, although the transmit / receive element 122 is depicted as a single element in Figure 15B, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving radio signals via the air interfaces 115 / 116 / 117.

[0307] The transceiver 120 may be configured to modulate the signal transmitted by the transmit / receive element 122 and demodulate the signal received by the transmit / receive element 122. As described above, the WTRU 102 may have multimode capability. Therefore, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11.

[0308] The processor 118 of the WTRU102 is coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit) and can receive user input data from them. The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad / indicator 128. Furthermore, the processor 118 can access information from any type of suitable memory, such as fixed memory 130 and / or removable memory 132, and store data therein. Fixed memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a subscriber identification module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In one embodiment, the processor 118 may access information from memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown), and store data therein.

[0309] The processor 118 may be configured to receive power from the power supply 134 and distribute and / or control power to other components within the WTRU 102. The power supply 134 may be any suitable device for supplying power to the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0310] The processor 118 may also be coupled to a GPS chipset 136 which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via air interfaces 115 / 116 / 117 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that the WTRU 102 may acquire location information by any suitable location determination method while maintaining consistency with one embodiment.

[0311] The processor 118 may be further coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functions, and / or wired or wireless connectivity. For example, peripherals 138 may include various sensors such as an accelerometer, a biometrics (e.g., fingerprint) sensor, an e-compass, a satellite transceiver, a digital camera (for photography or video), a Universal Serial Bus (USB) port or other interconnection interface, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, and an internet browser.

[0312] WTRU102 may be embodied in sensors, consumer electronics, wearable devices such as smartwatches or smart clothing, medical or eHealth devices, robots, industrial equipment, drones, and other devices or equipment such as automobiles, trucks, trains, or airplanes. WTRU102 may be connected to other components, modules, or systems of such devices or equipment via one or more interconnect interfaces, such as an interconnect interface which may include one of the peripheral devices 138.

[0313] Figure 15C is a system diagram of RAN103 and core network 106 according to one embodiment. As described above, RAN103 can communicate with WTRU102a, 102b, and 102c via air interface 115 using UTRA radio technology. RAN103 can also communicate with core network 106. As shown in Figure 15C, RAN103 may include NodeB140a, 140b, and 140c, each containing one or more transceivers for communication with WTRU102a, 102b, and 102c via air interface 115. NodeB140a, 140b, and 140c may each be associated with a specific cell (not shown) within RAN103. RAN103 may also include RNC142a and 142b. It will be understood that RAN103 may include any number of NodeB and RNC while maintaining consistency with one embodiment.

[0314] As shown in Figure 15C, NodeB140a and 140b can communicate with RNC142a. Furthermore, NodeB140c can communicate with RNC142b. NodeB140a, 140b, and 140c can communicate with their respective RNC142a and 142b via the Iub interface. RNC142a and 142b can communicate with each other via the Iur interface. Each of RNC142a and 142b can be configured to control their respective connected NodeB140a, 140b, and 140c. Furthermore, each of RNC142a and 142b can be configured to perform or support other functions such as external loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, and data encryption.

[0315] The core network 106 shown in Figure 15C may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and / or a gateway GPRS support node (GGSN) 150. Although each of the aforementioned elements is depicted as part of the core network 106, it will be understood that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0316] RNC142a in RAN103 may be connected to MSC146 in core network 106 via the IuCS interface. MSC146 may be connected to MGW144. MSC146 and MGW144 may provide WTRU102a, 102b, and 102c with access to a circuit-switched network such as PSTN108 to facilitate communication between WTRU102a, 102b, and 102c and conventional terrestrial communication devices.

[0317] RNC142a within RAN103 may also be connected to SGSN148 within core network 106 via the IuPS interface. SGSN148 may be connected to GGSN150. SGSN148 and GGSN150 may provide WTRU102a, 102b, and 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices.

[0318] As described above, the core network 106 may also be connected to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0319] Figure 15D is a system diagram of RAN104 and core network 107 according to one embodiment. As described above, RAN104 can communicate with WTRU102a, 102b, and 102c via air interface 116 using E-UTRA wireless technology. RAN104 can also communicate with core network 107.

[0320] While RAN104 may include eNodeB160a, 160b, and 160c, it will be understood that RAN104 may include any number of eNodeB while maintaining consistency with one embodiment. Each of eNodeB160a, 160b, and 160c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. In one embodiment, eNodeB160a, 160b, and 160c may implement MIMO technology. Thus, eNodeB160a may, for example, use multiple antennas to transmit radio signals to WTRU102a and receive radio signals from WTRU102a.

[0321] Each of the eNodeB160a, 160b, and 160c may be associated with a specific cell (not shown) and configured to handle wireless resource management decisions, handover decisions, user scheduling on uplink and / or downlink, etc. As shown in Figure 15D, the eNodeB160a, 160b, and 160c may communicate with each other via the X2 interface.

[0322] The core network 107 shown in Figure 15D may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. Although each of the aforementioned elements is depicted as part of the core network 107, it will be understood that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0323] The MME162 can be connected to each of the eNodeB160a, 160b, and 160c within RAN104 via the S1 interface and can function as a control node. For example, the MME162 may be responsible for user authentication of WTRU102a, 102b, and 102c, activation / deactivation of bearers, and selection of a specific serving gateway during the initial attachment of WTRU102a, 102b, and 102c. The MME162 may also provide control plane functionality for switching between RAN104 and other RANs (not shown) employing other radio technologies such as GSM or WCDMA.

[0324] The serving gateway 164 may be connected to each of the eNodeB 160a, 160b, and 160c in the RAN 104 via the S1 interface. The serving gateway 164 can generally route and forward user data packets to and from WTRU 102a, 102b, and 102c. The serving gateway 164 may also perform other functions such as fixing the user plane during inter-eNodeB handover, triggering paging when downlink data is available to WTRU 102a, 102b, and 102c, and managing and remembering the context of WTRU 102a, 102b, and 102c.

[0325] Serving gateway 164 may also be connected to PDN gateway 166, which may provide WTRU 102a, 102b, 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0326] The core network 107 can facilitate communication with other networks. For example, the core network 107 may provide WTRU 102a, 102b, and 102c with access to a circuit-switched network such as PSTN 108 to facilitate communication between WTRU 102a, 102b, and 102c and conventional terrestrial communication devices. For example, the core network 107 may include or communicate with an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that functions as an interface between the core network 107 and PSTN 108. Furthermore, the core network 107 may provide WTRU 102a, 102b, and 102c with access to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0327] Figure 15E is a system diagram of RAN105 and core network 109 according to one embodiment. RAN105 may be an access service network (ASN) employing IEEE 802.16 wireless technology to communicate with WTRU102a, 102b, and 102c via air interface 117. As will be further described below, communication links between different functional entities of WTRU102a, 102b, 102c, RAN105, and core network 109 may be defined as reference points.

[0328] As shown in Figure 15E, RAN105 may include base stations 180a, 180b, 180c and an ASN gateway 182, although it will be understood that RAN105 may include any number of base stations and ASN gateways while maintaining consistency with one embodiment. Base stations 180a, 180b, and 180c may each be associated with a specific cell within RAN105 and may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via the air interface 117. In one embodiment, base stations 180a, 180b, and 180c may implement MIMO technology. Thus, base station 180a may, for example, use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a. Base stations 180a, 180b, and 180c may also provide mobility management functions such as handoff triggers, tunnel establishment, radio resource management, traffic classification, and quality of service (QoS) policy enforcement. ASN gateway 182 can function as a traffic aggregation point, and may be responsible for paging, caching subscriber profiles, and routing to core network 109.

[0329] The air interface 117 between WTRU102a, 102b, 102c and RAN105 may be defined as an R1 reference point implementing the IEEE 802.16 specification. Furthermore, each of WTRU102a, 102b, and 102c may establish a logical interface (not shown) with the core network 109. The logical interface between WTRU102a, 102b, 102c and the core network 109 may be defined as an R2 reference point that can be used for authentication, authorization, IP host configuration management, and / or mobility management.

[0330] The communication links between base stations 180a, 180b, and 180c may be defined as R8 reference points, which include protocols to facilitate WTRU handover and data transfer between base stations. The communication links between base stations 180a, 180b, and 180c and the ASN gateway 182 may be defined as R6 reference points. R6 reference points may include protocols to facilitate mobility management based on mobility events associated with each of WTRU 102a, 102b, and 102c.

[0331] As shown in Figure 15E, RAN 105 may be connected to core network 109. The communication link between RAN 105 and core network 109 may be defined as an R3 reference point, including, for example, protocols to facilitate data transfer and mobility management capabilities. Core network 109 may include a mobile IP home agent (MIP-HA) 184, an authentication, authorization, and accounting (AAA) server 186, and a gateway 188. Although each of the aforementioned elements is depicted as part of core network 109, it will be understood that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0332] The MIP-HA may be responsible for IP address management and may enable WTRU102a, 102b, and 102c to roam between different ASNs and / or different core networks. The MIP-HA184 may provide WTRU102a, 102b, and 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices. The AAA server 186 may be responsible for user authentication and support for user services. The gateway 188 may facilitate interworking with other networks. For example, the gateway 188 may provide WTRU102a, 102b, and 102c with access to a circuit-switched network such as the PSTN 108 to facilitate communication between WTRU102a, 102b, and 102c and conventional terrestrial communication devices. Furthermore, gateway 188 may provide WTRU 102a, 102b, and 102c with access to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0333] Although not shown in Figure 15E, it will be understood that RAN105 may be connected to other ASNs, and core network 109 may be connected to other core networks. The communication link between RAN105 and other ASNs may be defined as an R4 reference point that may include protocols for coordinating the mobility of WTRU102a, 102b, and 102c between RAN105 and other ASNs. The communication link between core network 109 and other core networks may be defined as an R5 reference that may include protocols for facilitating interworking between the home core network and the visited core network.

[0334] The core network entities described herein and illustrated in Figures 15A, 15C, 15D, and 15E are identified by the names given to them in certain existing 3GPP specifications, but it is understood that in the future, these entities and functions may be identified by other names, and that certain entities or functions may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Accordingly, it is understood that the specific network entities and functions described and illustrated in Figures 15A to 15E are provided for illustrative purposes only, and that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or hereafter defined.

[0335] Figure 15F is a block diagram of an exemplary computing system 90 in which one or more devices of the communication networks illustrated in Figures 15A, 15C, 15D, and 15E may be embodied, such as RAN 103 / 104 / 105, core networks 106 / 107 / 109, PSTN 108, the Internet 110, or other networks 112. The computing system 90 may comprise a computer or server and may be controlled primarily by computer-readable instructions, which may be in the form of software, regardless of where or by what means such software is stored or accessed. Such computer-readable instructions may be executed within a processor 91 to cause the computing system 90 to perform operations. The processor 91 may be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, and the like. The processor 91 may perform signal coding, data processing, power control, input / output processing, and / or any other functions that enable the computing system 90 to operate within a communication network. The coprocessor 81 is an optional processor distinct from the main processor 91 that may perform additional functions or assist the processor 91. The processor 91 and / or coprocessor 81 may receive, generate, and process data related to the methods and apparatus disclosed herein.

[0336] During operation, the processor 91 fetches, decodes, and executes instructions to transfer information to and from other resources via the system bus 80, which is the main data transfer path of the computing system. Such a system bus connects the components within the computing system 90 and defines the medium for data exchange. The system bus 80 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and operating the system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0337] The memory coupled to the system bus 80 includes random access memory (RAM) 82 and read-only memory (ROM) 93. Such memory includes circuitry that enables the storage and retrieval of information. ROM 93 generally contains stored data that cannot be easily altered. Data stored in RAM 82 can be read or modified by the processor 91 or other hardware devices. Access to RAM 82 and / or ROM 93 can be controlled by a memory controller 92. The memory controller 92 may provide address translation functionality that translates virtual addresses to physical addresses when instructions are executed. The memory controller 92 may also provide memory protection functionality that isolates processes within the system and separates system processes from user processes. Thus, a program operating in the first mode can only access memory mapped by its own process virtual address space and cannot access memory in the virtual address space of another process unless inter-process memory sharing is configured.

[0338] Furthermore, the computing system 90 may include a peripheral device controller 83 responsible for communicating commands from the processor 91 to peripheral devices such as a printer 94, keyboard 84, mouse 95, and disk drive 85.

[0339] The display 86, controlled by the display controller 96, is used to display visual output generated by the computing system 90. Such visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). The display 86 may be implemented as a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch panel. The display controller 96 includes the electronic components necessary to generate the video signal sent to the display 86.

[0340] Furthermore, the computing system 90 may include communication circuits, such as a network adapter 97, which can be used to connect the computing system 90 to an external communication network such as RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, the Internet 110, or other network 112 shown in Figures 15A to 1E, enabling the computing system 90 to communicate with other nodes or functional entities in those networks. The communication circuits may be used alone or in combination with the processor 91 to perform the transmission and reception steps of the specific devices, nodes, or functional entities described herein.

[0341] Figure 15G illustrates one embodiment of an exemplary communication system 111 in which the methods and apparatus described herein and claimed may be embodied. As shown in the figure, the exemplary communication system 111 may include radio transmit / receive units (WTRUs) A, B, C, D, E, F, base stations, V2X servers, and RSUs A and B, but it will be understood that the disclosed embodiments intend any number of WTRUs, base stations, networks, and / or network elements. One, some, or all of the WTRUs A, B, C, D, E may be outside the network range. In the example of Figure 15G, cell coverage boundaries are shown by dashed lines. WTRUs A, B, and C form a V2X group in which WTRU A is the group lead and WTRUs B and C are group members. WTRUs A, B, C, D, E, and F may communicate via a Uu interface or a Sidelink (PC5) interface.

[0342] Any or all of the devices, systems, methods, and processes described herein may be embodied in the form of computer-executable instructions (e.g., program code) stored in a computer-readable storage medium, which, when executed by a processor such as processor 118 or 91, cause the processor to execute and / or implement the systems, methods, and processes described herein. Specifically, any of the steps, operations, or functions described herein may be implemented in the form of such computer-executable instructions and executed on a processor of a device or computing system configured for wireless and / or wired network communication. Computer-readable storage mediums include volatile and non-volatile, removable and non-removable media implemented by any non-temporary (e.g., tangible or physical) method or technique for storing information, but such computer-readable storage mediums do not contain signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage devices, magnetic cassettes, magnetic tapes, magnetic disk storage devices or other magnetic storage devices, or any other tangible or physical media that can be used to store desired information and can be accessed by a computing system.

[0343] Appendix 1 - Example Configuration [Table 1] [Table 2] [Table 3] [Table 4-1] [Table 4-2] [Table 4-3] [Table 5-1] [Table 5-2] [Table 6-1] [Table 6-2] [Table 6-3] [Table 7-1] [Table 7-2] [Table 8-1] [Table 8-2] [Table 9-1] [Table 9-2] [Table 9-3]

[0344] Appendix 2 - Table [Table 10] [Table 11] [Table 12] [Table 13] Table 14 Table 15 Table 16

Claims

1. A user-defined equipment (UE) device, the device comprising a communication circuit capable of connecting to a wireless network, the device comprising a processor, memory, and instructions stored in the memory, which, when executed by the processor, result in the device, A radio resource control (RRC) signaling indicating two SRSRSs, including a first Sounding Reference Signal (SRS) resource set (SRSRS) and a second SRSRS, and indicating a physical uplink shared channel (PUSCH) repetition pattern, and a downlink control information (DCI) for scheduling one or more PUSCHs, which includes a two-bit SRSRS selection field, a first SRS resource indicator (SRI) field and a second SRI field, to receive one or more downlink transmissions. The aforementioned 2-bit SRSRS selection field indicates one of the code point values ​​from 0 to 3. The code point value 0 indicates the selection of the first SRSRS, in which case the code point value 0 is used to indicate the SRS resource within the first SRSRS, and the code point value 0 indicates that the second SRI field is unused. The code point value 1 indicates the selection of the second SRSRS, in which case the second SRI field is used to indicate an SRS resource within the second SRSRS, and the code point value 1 indicates that the first SRI field is unused. The code point value 2 indicates the selection of the first SRSRS and the second SRSRS, where, in the case of code point value 2, the first SRI field is used to indicate the SRS resource in the first SRSRS, and the second SRI field is used to indicate the SRS resource in the second SRSRS. The code point value 3 indicates the selection of the first SRSRS and the second SRSRS, where, in the case of code point value 3, the first SRI field is used to indicate the SRS resource in the first SRSRS, and the second SRI field is used to indicate the SRS resource in the second SRSRS. The first SRSS corresponds to an ID with a lower rank than the second SRSS, and Using the aforementioned PUSCH repetition pattern and the SRSRS selected based on the 2-bit SRSRS selection field, a PUSCH is transmitted on one or more PUSCH opportunities. A device equipped with commands.

2. The apparatus according to claim 1, wherein the first SRSRS is used for codebook-based operation and the second SRSRS is used for non-codebook-based operation.

3. The apparatus according to claim 1, wherein the DCI instructs the use of both non-codebook-based push operations and codebook-based push operations.

4. The aforementioned instruction further instructs the device, In the first set of PUSCH opportunities, a codebook-based operation is used to send a PUSCH, and In the second set of PUSCH opportunities, a non-codebook-based operation is used to send PUSCH. The apparatus according to claim 3.

5. The apparatus according to claim 4, wherein the DCI includes fields for precoding and layers relating to the number of PUSCH precodings and layers, the fields for precoding and layers relating to the first set of PUSCH opportunities but not to PUSCH transmissions in the second set of PUSCH opportunities.

6. The apparatus according to claim 4, wherein the DCI includes a plurality of SRI fields, including a first SRI field applicable to PUSCH transmissions in the first set of PUSCH opportunities and a second SRI field applicable to the second set of PUSCH opportunities.

7. The apparatus according to claim 6, wherein the instruction further causes the apparatus to determine the number of layers for PUSCH transmission in the first set of PUSCH opportunities and the second set of PUSCH opportunities based on the second SRI field.

8. The apparatus according to claim 7, wherein the DCI includes a precoding field related to precoding for PUSCH transmission in the first set of PUSCH opportunities based on the number of layers.

9. The apparatus according to claim 6, wherein the DCI includes fields for precoding and layers relating to the number of precodings and layers, the precoding relating to the first set of PUSCH machines but not to the second set of PUSCH machines, and the number of layers relating to both the first set and the second set of PUSCH machines.

10. The apparatus according to claim 9, wherein the second SRI field indicates a number of SRS resources equal to the number of layers indicated by the precoding and layer fields.

11. A method performed by a device on the network side, Sending a downlink transmission comprising: a radio resource control (RRC) signaling indicating two SRSRSs, including a first Sounding Reference Signal (SRS) resource set (SRSRS) and a second SRSRS, and indicating a physical uplink shared channel (PUSCH) repetition pattern; and downlink control information (DCI) for scheduling one or more PUSCHs, which includes a two-bit SRSRS selection field, a first SRS resource indicator (SRI) field and a second SRI field, supporting non-codebook-based and / or codebook-based PUSCH operation; The aforementioned 2-bit SRSRS selection field indicates one of the code point values ​​from 0 to 3. The code point value 0 indicates the selection of the first SRSRS, in which case the code point value 0 is used to indicate the SRS resource within the first SRSRS, and the code point value 0 indicates that the second SRI field is unused. The code point value 1 indicates the selection of the second SRSRS, in which case the second SRI field is used to indicate an SRS resource within the second SRSRS, and the code point value 1 indicates that the first SRI field is unused. The code point value 2 indicates the selection of the first SRSRS and the second SRSRS, where, in the case of code point value 2, the first SRI field is used to indicate the SRS resource in the first SRSRS, and the second SRI field is used to indicate the SRS resource in the second SRSRS. The code point value 3 indicates the selection of the first SRSRS and the second SRSRS, where, in the case of code point value 3, the first SRI field is used to indicate the SRS resource in the first SRSRS, and the second SRI field is used to indicate the SRS resource in the second SRSRS. The first SRSS corresponds to an ID with a lower rank than the second SRSS, A method comprising the steps of receiving a PUSCH on one or more PUSCH opportunities using the PUSCH repetition pattern and the SRSRS selected based on the two-bit SRSRS selection field.

12. The method according to claim 11, wherein the first SRSRS is used for codebook-based operation and the second SRSRS is used for non-codebook-based operation.

13. The method according to claim 11, wherein the DCI instructs the use of both non-codebook-based PUSCH operations and codebook-based PUSCH operations.

14. The steps include receiving a first transmission sent using codebook-based operation in a first set of PUSCH machines from a user device (UE), The method according to claim 13, further comprising the step of receiving from the UE a second transmission sent using non-codebook-based operation in a second set of PUSCH opportunities.

15. The method according to claim 14, wherein the DCI includes a plurality of SRI fields, the DCI including a first SRI field applicable to the first set of PUSCH opportunities and a second SRI field applicable to the second set of PUSCH opportunities.

16. The method according to claim 14, wherein the DCI includes a first field relating to precoding and the number of layers, the first field relating to the first set of PUSCH opportunities but not to the second set of PUSCH opportunities.

17. The method according to claim 15, wherein the second SRI field relates to a first number of layers for the first set of PUSCH opportunities and a second number of layers for the second set of PUSCH opportunities.

18. The method according to claim 17, wherein the DCI includes a precoding field related to precoding for PUSCH transmission in the first set of PUSCH opportunities based on the first number of layers.

19. The method according to claim 15, wherein the DCI includes fields for precoding and layers relating to the number of precodings and layers, the precoding relating to the first set of PUSCH opportunities but not to the second set of PUSCH opportunities, and the number of layers relating to both the first set and the second set of PUSCH opportunities.

20. The method according to claim 19, wherein the second SRI field indicates a number of SRS resources equal to the number of layers indicated by the precoding and layer fields.

Images