Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure is characterized by comprising: a transmission unit that transmits capability information indicating whether to support Sounding Reference Signal (SRS) using eight ports when Time Division Multiplexing (TDM) is applied or when TDM is not applied, for each codebook type; and a control unit that controls transmission of the SRS using the eight ports. According to this one aspect of the present disclosure, it is possible to appropriately execute SRS transmission using more than four SRS ports.

Description

Terminal, wireless communication method and base station

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.

[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later, etc.) are also being considered.

[0004] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010

[0005] In 3GPP Rel. 15 / 16, the maximum number of UL layers is 4, and the maximum number of Sounding Reference Signal (SRS) ports is also 4. Therefore, UL transmission is realized by a simple relationship between layers and uplink (UL) channel / signal (PUSCH / SRS) ports.

[0006] In future wireless communication systems (e.g., 3GPP Rel. 18 and later), support for more than four layers in UL transmission from a terminal (user terminal, User Equipment (UE)) is being considered. However, the operation of signaling UE capability information regarding SRS ports greater than four ports has not been clarified. This may result in inappropriate transmission of SRS using more than four SRS ports.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately transmit SRS using more than four SRS ports.

[0008] A terminal according to one aspect of the present disclosure is characterized in that it has a transmitting unit that transmits capability information indicating whether a Sounding Reference Signal (SRS) using eight ports is supported when Time Division Multiplexing (TDM) is applied or when TDM is not applied, for each codebook type, and a control unit that controls the transmission of the SRS using the eight ports.

[0009] According to one aspect of the present disclosure, SRS transmission using more than four SRS ports can be appropriately performed.

[0010] Fig. 1 shows an example of port distribution using TDM. Fig. 2 is a diagram showing an overview of UE capability inquiry (UECapabilityEnquiry). Fig. 3 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Fig. 4 is a diagram showing an example of a configuration of a base station according to an embodiment. Fig. 5 is a diagram showing an example of a configuration of a user terminal according to an embodiment. Fig. 6 is a diagram showing an example of hardware configurations of a base station and a user terminal according to an embodiment. Fig. 7 is a diagram showing an example of a vehicle according to an embodiment.

[0011] (Control of Transmission of SRS and PUSCH) In Rel. 15 NR, a terminal (user terminal, User Equipment (UE)) may receive information (SRS configuration information, for example, parameters in the RRC control element "SRS-Config") used for transmitting a measurement reference signal (for example, a sounding reference signal (SRS)).

[0012] Specifically, the UE may receive at least one of information regarding one or more SRS resource sets (SRS resource set information, e.g., the RRC control element "SRS-ResourceSet") and information regarding one or more SRS resources (SRS resource information, e.g., the RRC control element "SRS-Resource").

[0013] An SRS resource set may be associated with (or group together) a predetermined number of SRS resources, each of which may be identified by an SRS Resource Indicator (SRI) or SRS Resource Identifier (ID).

[0014] The SRS resource set information may include an SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, an SRS resource type, and information on SRS usage.

[0015] Here, the SRS resource type may indicate any one of periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and aperiodic CSI (Aperiodic SRS (A-SRS)). Note that the UE may transmit P-SRS and SP-SRS periodically (or periodically after activation), and transmit A-SRS based on an SRS request in the DCI.

[0016] Furthermore, the use ("usage" of the RRC parameter, "SRS-SetUse" of the L1 (Layer-1) parameter) may be, for example, beam management (BM), codebook (CB), non-codebook (NCB), antenna switching (AS), etc. The SRS for codebook or non-codebook use may be used to determine a precoder for codebook-based or non-codebook-based uplink shared channel (PUSCH) transmission based on the SRI.

[0017] For example, in the case of codebook-based transmission, the UE may determine a precoder (precoding matrix) for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), and a Transmitted Precoding Matrix Indicator (TPMI). In the case of non-codebook-based transmission, the UE may determine a precoder for PUSCH transmission based on the SRI.

[0018] The SRS resource information may include an SRS resource ID (SRS-ResourceId), the number of SRS ports, the SRS port number, a transmission comb, an SRS resource mapping (e.g., time and / or frequency resource position, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hopping-related information, an SRS resource type, a sequence ID, spatial relationship information of the SRS, etc.

[0019] The spatial relationship information of the SRS (e.g., the RRC information element "spatialRelationInfo") may indicate spatial relationship information between a predetermined reference signal and the SRS. The predetermined reference signal may be at least one of a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, a Channel State Information Reference Signal (CSI-RS), and an SRS (e.g., another SRS). The SS / PBCH block may be referred to as a Synchronization Signal Block (SSB).

[0020] The spatial relationship information of the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index of the predetermined reference signal.

[0021] In the present disclosure, the SSB index, SSB resource ID, and SSB Resource Indicator (SSBRI) may be interchangeable. Furthermore, the CSI-RS index, CSI-RS resource ID, and CSI-RS Resource Indicator (CRI) may be interchangeable. Furthermore, the SRS index, SRS resource ID, and SRI may be interchangeable.

[0022] The spatial relationship information of the SRS may include a serving cell index, a BWP index (BWP ID), etc. corresponding to the predetermined reference signal.

[0023] When the UE is configured with spatial relationship information regarding the SRS and an SSB or CSI-RS for a certain SRS resource, the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter for receiving the SSB or CSI-RS (spatial domain receive filter). In this case, the UE may assume that the UE receive beam for the SSB or CSI-RS and the UE transmit beam for the SRS are the same.

[0024] When the UE is configured with spatial relationship information between another SRS (reference SRS) and the target SRS for a certain SRS (target SRS), the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain transmit filter) for transmitting the reference SRS. That is, in this case, the UE may assume that the UE transmit beam of the reference SRS and the UE transmit beam of the target SRS are the same.

[0025] The UE may determine the spatial relationship of the PUSCH scheduled by the DCI (e.g., DCI format 0_1) based on the value of a predetermined field (e.g., an SRS resource identifier (SRI) field) in the DCI. Specifically, the UE may use spatial relationship information of the SRS resources (e.g., the RRC information element "spatialRelationInfo") determined based on the value of the predetermined field (e.g., the SRI) for PUSCH transmission.

[0026] In Rel. 15 / 16 NR, when codebook-based transmission is used for PUSCH, the UE is configured by RRC with an SRS resource set of a codebook usage having up to two SRS resources, and one of the up to two SRS resources may be indicated by DCI (a 1-bit SRI field). The transmission beam for PUSCH is specified by the SRI field.

[0027] The UE may determine the TPMI and the number of layers (transmission rank) for the PUSCH based on the precoding information and number of layers field (hereinafter also referred to as the precoding information field). The UE may select a precoder from an uplink codebook for the same number of SRS ports as the number of SRS ports indicated by the upper layer parameter "nrofSRS-Ports" configured for the SRS resource specified by the SRI field based on the TPMI, the number of layers, etc.

[0028] In Rel. 15 / 16 NR, when non-codebook-based transmission is used for PUSCH, a non-codebook-used SRS resource set having up to four SRS resources may be configured for the UE by RRC, and one or more of the up to four SRS resources may be indicated by DCI (a 2-bit SRI field).

[0029] The UE may determine the number of layers (transmission rank) for the PUSCH based on the SRI field. For example, the UE may determine that the number of SRS resources specified by the SRI field is the same as the number of layers for the PUSCH. The UE may also calculate a precoder for the SRS resources.

[0030] If a CSI-RS (which may be referred to as an associated CSI-RS) associated with the SRS resource (or an SRS resource set to which the SRS resource belongs) is configured by a higher layer, the transmission beam for the PUSCH may be calculated based on (measurements of) the configured associated CSI-RS. Otherwise, the transmission beam for the PUSCH may be specified by the SRI.

[0031] The UE may be configured to use codebook-based PUSCH transmission or non-codebook-based PUSCH transmission by a higher layer parameter "txConfig" indicating a transmission scheme. The parameter may indicate a value of "codebook" or "non-codebook."

[0032] In the present disclosure, a codebook-based PUSCH (codebook-based PUSCH transmission, codebook-based transmission) may refer to a PUSCH when a UE is configured with "codebook" as a transmission scheme. In the present disclosure, a non-codebook-based PUSCH (non-codebook-based PUSCH transmission, non-codebook-based transmission) may refer to a PUSCH when a UE is configured with "non-codebook" as a transmission scheme.

[0033] (Transmission of More Than Four Antenna Ports) Rel. 15 / 16 NR supports uplink (UL) multi-input multi-output (MIMO) transmission with up to four layers. For future wireless communication systems, support for UL transmission with more than four layers is being considered to achieve higher spectral efficiency. For example, for Rel. 18 NR, maximum six-rank transmission using six antenna ports and maximum six- or eight-rank transmission using eight antenna ports are being considered.

[0034] Also, precoding matrices for UL transmission using more than four antenna ports (a number of antenna ports greater than four) are being considered. For example, a codebook for 8-port transmission (which may be called an 8 Transmission (TX) UL codebook) is being considered.

[0035] In the antenna layout, Ng is the number of antenna groups. M is the number of antennas (or antenna elements) in the first dimension, and N is the number of antennas (or antenna elements) in the second dimension. The first and second dimensions are, for example, horizontal and vertical directions. P is the number of polarization planes. When P=2, it becomes a cross-polarized antenna.

[0036] An antenna group may be referred to as a coherent group. A coherent group may include one or more coherent ports. For example, a partially coherent UE may have multiple coherent groups. Antenna ports within a coherent group may be coherent. Antenna ports between different coherent groups may not be coherent.

[0037] Each coherent group may correspond to a different transmit panel / transmit chain / SRS resource set / RS resource set / spatial relation information / joint Transmission Configuration Indication state (joint TCI state) / UL TCI state / received TRP. Here, the SRS resource set may specifically correspond to an SRS resource set used for codebook or non-codebook. Each coherent group may also correspond to a different received TRP. A coherent group may also be referred to as a coherent antenna group, a port group, an antenna set, etc.

[0038] The UE may report supported antenna groups / antenna configuration information / coherent number as UE capability information. Also, the UE may be configured with coherent groups (e.g., the number of coherent groups and the number of ports included in each coherent group) by higher layer signaling.

[0039] The number of panels on which the antennas are arranged, the orientation of the panels, the coherency of each panel / antenna (fully coherent, partially coherent, non-coherent, etc.), the antenna arrangement in a particular direction (horizontal, vertical, etc.), and the polarization antenna configuration (single polarization, cross polarization, number of polarization planes, etc.) may differ from existing antenna layouts. dG-H and dG-V represent the horizontal and vertical spacings between the centers of adjacent antenna groups, respectively.

[0040] Furthermore, while Rel. 15 / 16 NR supported the transmission of one codeword (CW) in one PUSCH, Rel. 18 NR is considering allowing a UE to transmit more than one CW in one PUSCH. For example, support for two CW transmissions for ranks 5-8 and support for two CW (dual CW) transmissions for ranks 2-8 are being considered. One CW corresponds to one transport block (TB).

[0041] In Rel. 17 NR and earlier, transmission of two TBs (e.g., TB #1 and TB #2) is supported in DL transmission (e.g., PDSCH transmission). When two TBs (e.g., TB #2) are supported, a DCI (e.g., DCI format 1_1) used for scheduling the PDSCH may include a predetermined field for TB #1 and a predetermined field for TB #2. The predetermined field may be, for example, at least one of a modulation and coding scheme, a new data indicator, and a redundancy version.

[0042] The support (or enablement) of dual CWs in PUSCH transmission may be notified to the UE by a predetermined higher layer parameter. The predetermined higher layer parameter may be a higher layer parameter (e.g., maxNrofCodeWordsScheduledByDCI) related to the maximum number of CWs scheduled by DCI. The predetermined higher layer parameter (e.g., maxNrofCodeWordsScheduledByDCI) may be included in PUSCH configuration information (e.g., PUSCH-config).

[0043] For example, if a predetermined higher layer parameter is set to 2 (e.g., maxNrofCodeWordsScheduledByDCI equals 2), this may mean that a predetermined field for TB#2 is included in the DCI. That is, if a predetermined higher layer parameter indicates a predetermined value (e.g., 2) for PDSCH, this may mean that a field for TB#2 is present (or that two codeword transmission is enabled).

[0044] If a predetermined higher layer parameter (e.g., maxNrfCodeWordsScheduledByDCI) indicates that two codeword transmission is enabled, one of the two transport blocks may be disabled by the DCI format if a predetermined condition is met. For example, the predetermined condition may be a MCS index (e.g., I) for the corresponding transport block. ＭＣＳ ) and the RV index are respectively set to predetermined values ​​(for example, I ＭＣＳ = 26 and RV = 1).

[0045] Thus, a predetermined upper layer parameter is set to a predetermined value (e.g., maxNrofCodeWordsScheduledByDCI=2), and I ＭＣＳ If there is a TB with RV = 26 and RV = 1, the corresponding TB may be disabled to realize dynamic indication (or switching) between more than four layers and less than four layers for PDSCH.

[0046] In the present disclosure, the first TB and TB1 of the two TBs may be interchangeable. In the present disclosure, the second TB and TB2 of the two TBs may be interchangeable.

[0047] N SRS It is being considered that a method based on existing specifications will be supported for NCB-based 8Tx PUSCH transmission using >4, where N SRS is the number of single-port SRS resources configured in the SRS resource set. SRS =8 and L max Extend the existing SRI indication table to include L = 8, where L max is the maximum number of MIMO layers. In the SRI indication for the NCB-based PUSCH, a selection may be made between a bitmap indication and a method based on existing specifications.

[0048] To configure PUSCH transmission by an 8Tx UE, it is considered that the maximum number of MIMO layers is RRC configurable by extending the range of maxRank and maxMIMO-Layers up to 8. The maximum rank is configured by RRC signaling.

[0049] To support dual CW PUSCH transmission for ranks greater than four by an 8Tx UE, it is considered that a second MCS field (5 bits) be indicated for the second CW for MCS indication. To support dual CW PUSCH transmission for ranks greater than four by an 8Tx UE, it is considered that a second set of new data indicator (NDI, 1 bit) and redundancy version (RV, 2 bits) fields be indicated. That is, additional MCS / NDI / RV for the second CW are supported.

[0050] (Port allocation using Time Division Multiplexing (TDM)) For antenna switching / codebook usage, it is considered to support 8-port (8-layer) UL channel measurement by SRS and mapping different SRS ports to different OFDM symbols (i.e., TDM) (Fig. 1). It is also conceivable to map all 8 ports to one OFDM symbol.

[0051] When port allocation using TDM (TDM mapping) is applied, the number of cyclic shifts occupied by one OFDM symbol is small, which has the advantage of high robustness against delay. Also, the power per port can be increased. However, there may be a restriction that multiple OFDM symbols use the same frequency resource / transmission power.

[0052] For example, as a configuration of SRS resources, it is conceivable that four ports are assigned per OFDM symbol and eight-port SRS transmission is configured using two or more OFDM symbols.

[0053] The specification defines a transmission power associated with an SRS transmission opportunity i corresponding to an SRS transmission configured by an SRS resource, which means an SRS transmission in one or more OFDM symbols, and this transmission power is distributed evenly across the antenna ports configured for SRS (e.g., configured by the SRS resource configuration).

[0054] (8TX UE Antenna Layout) For an 8TX UE, different coherent UE antenna layouts are supported. Each antenna group Ng (Ng = 1, 2, 4, 8) is configured with coherent antennas. For example, when Ng = 1, two antenna configurations are supported: (N1, N2) = (4, 1) and (2, 2). N1 is the number of antennas (or antenna elements) in the first dimension, and N2 is the number of antennas (or antenna elements) in the second dimension. The first and second dimensions are, for example, horizontal and vertical directions. N1 and N2 may be replaced with M and N. P is the number of polarization planes. When P = 2, cross-polarized antennas are used. Antennas between groups can also be non-coherent.

[0055] The relationship between the codebooks and the coherent antenna groups (M, N, P) in this disclosure is as follows: Codebook 1: Ng=1, fully coherent, (1, 4, 2) or (2, 2, 2) per group. Codebook 2: Ng=2, partially coherent, (1, 2, 2) per group. Codebook 3: Ng=4, partially coherent, (1, 1, 2) per group. Codebook 4: Ng=8, noncoherent, (1, 1, 1) per group.

[0056] (UE Features for 8Tx) As UE features for Rel. 18 MIMO 8Tx, the function with index FG40-7-1 defines "SRS 8Tx port-codebook" as a component, and defines {noTDM, TDM, and noTDM} as candidate values ​​for the component.

[0057] Also, for codebook-based 8Tx PUSCH, an additional UE feature group (FG) is being considered as 40-7-1h in the 40-7-1 family. This new UE FG will signal the supported codebook type and SRS type with the following candidate values:

[0058] Candidate value 1: The UE supports coherent 8TxPUSCH (Codebook 1) with noTDMed SRS, but only partially coherent 8TxPUSCH (Codebook 2) with TDMed SRS.

[0059] Candidate value 2: The UE supports coherent 8Tx PUSCH (codebook 1) with no TDMed SRS, but only partially coherent 8Tx PUSCH (codebook 3) with TDMed SRS.

[0060] Candidate value 3: The UE supports coherent 8TxPUSCH (codebook 1) with no TDMed SRS, but only non-coherent 8TxPUSCH (codebook 4) with TDMed SRS.

[0061] Candidate value 4: The UE supports partially coherent 8Tx PUSCH (codebook 2) with no TDMed SRS, but only partially coherent 8Tx PUSCH (codebook 3) with TDMed SRS.

[0062] Candidate value 5: The UE supports partially coherent 8Tx PUSCH (codebook 2) with no TDMed SRS, but only non-coherent 8Tx PUSCH (codebook 4) with TDMed SRS.

[0063] Candidate value 6: The UE supports partially coherent 8Tx PUSCH (Codebook 3) with no TDMed SRS, but only non-coherent 8Tx PUSCH (Codebook 4) with TDMed SRS.

[0064] (Analysis) As described above, in future wireless communication systems (e.g., 3GPP Rel. 18 and later), support for more than four layers in UL transmission from a terminal (user terminal, User Equipment (UE)) is being considered. However, the operation of signaling UE capability information regarding SRS ports greater than four ports has not been clarified. This may result in inappropriate transmission of SRS using more than four SRS ports.

[0065] For example, current UE functionality does not allow separate configuration of support for {noTDM, TDM, and noTDM} for each codebook type (codebooks 1 to 4). For example, it is not possible for the same UE to indicate that it supports codebooks 2, 3, or 4 for TDM-enhanced SRS and codebook 1 for non-TDM-enhanced SRS. Therefore, it is preferable to enhance the UE functionality to support such cases.

[0066] Therefore, the present inventors have conceived a method that can appropriately transmit SRS using more than four SRS ports.

[0067] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0068] (Various Reinterpretations) In the present disclosure, a word enclosed in "( )" in a sentence may indicate an explanation of the word immediately preceding it (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Furthermore, in the present disclosure, a word enclosed in "[ ]" in a sentence may be interpreted including the word in the meaning of the entire sentence, or may be interpreted excluding (ignoring) the word in the meaning of the entire sentence. Note that "( )" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

[0069] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0070] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0071] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

[0072] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

[0073] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0074] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0075] In this disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna, antenna element, layer, transmission, port, antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

[0076] As the SRS in the present disclosure, at least one of P-SRS, SP-SRS, and AP-SRS may be used. In the present disclosure, P SRS and P-SRS may be interchangeable. In the present disclosure, SP SRS and SP-SRS may be interchangeable. In the present disclosure, AP SRS and AP-SRS may be interchangeable. In the present disclosure, resource set group and SRS resource set group may be interchangeable.

[0077] The number of layers for PUSCH transmission in the following embodiments may be greater than 4 or less than 4. For example, PUSCH transmission of two CWs in the present disclosure may be performed with a number of layers less than 4 (for example, 2). In addition, the maximum number of layers is not limited to 4 or more, and may be less than 4.

[0078] Furthermore, PUSCH transmission in the following embodiments may or may not be based on the premise that multiple panels are used (it may be applied regardless of the panels).

[0079] In the present disclosure, Tx, Tx port, transmit, port, SRS port, transmit port, SRS transmit port, antenna port, UE antenna port, receive port, antenna, UE antenna, and receive antenna may be read interchangeably.

[0080] In the present disclosure, FG, UE capability, capability information, UE capability information, capability signaling, UE capability signaling, FG support, and capability reporting may be read interchangeably.

[0081] (Wireless Communication Method) In the present disclosure, one FG may be defined as a row in a table. Items (1) to (14) in this embodiment are shown as follows. In the embodiments described later, the contents corresponding to these items are shown. For example, the description "(1) 40.NR_MIMO_evo_DL_UL" in each embodiment indicates that the feature is 40.NR_MIMO_evo_DL_UL. The same applies to other items. (1) Features. (2) Index. (3) FG (Feature group). (4) Component. (5) Prerequisite FG. (6) The need for the gNB to know whether the feature is supported. (7) Applicability to capability signaling exchange between multiple UEs (sidelink consideration items only). (8) Consequences if the FG is not supported by the UE. (9) Type ("Type" definition from UE capabilities is based on one of the following granularities: per UE, per band, per BC, per Feature Set (FS), or per Feature Set Per Component-carrier (FSPC)). (10) Necessity of FDD / TDD differentiation. (11) Necessity of FR1 / FR2 differentiation. (12) Interpretation of capabilities for mixed FDD / TDD and / or FR1 / FR2. (13) Notes. (14) Mandatory / Optional.

[0082] Regarding the functions of each embodiment described below, the contents of items (6), (7), (9), (10), (11), (12), and (14) may be, for example, as follows: (6) YES (7) n / a (9) Per FSPC (10) No (11) No (12) No (14) Optional function with capability signaling.

[0083] <First embodiment> A UE may transmit capability information indicating whether it supports 8-port SRS (SRS using 8 ports) when TDM is applied or when TDM is not applied for each codebook type, and may control transmission of the SRS using 8 ports. Note that in the present disclosure, the codebook type may refer to a distinction between codebooks 1 to 4.

[0084] For example, the component "SRS 8Tx ports - Codebook" and corresponding candidate values ​​in FG40-7-1 may not be included, and instead new components may be added to 40-7-1a / 1b / 1c / 1d to report 8-port SRS support for TDM / non-TDM for each codebook type.

[0085] In FG40-7-1b / 1c / 1d, a restriction (restriction A) that "the same candidate value as this component is reported from the UE" may or may not be added.

[0086] For each function, the contents of items (1) to (5), (8), and (13) may be, for example, as follows:

[0087] [Function 40-7-1] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1. (3) Basic functions of codebook-based 8Tx PUSCH. (4) 1. Maximum number of PUSCH MIMO layers for codebook-based PUSCH. 2. Maximum number of 8-port SRS resources per SRS resource set with usage set to "codebook" for codebook-based 8Tx PUSCH. (5)-(8) Codebook-based 8Tx PUSCH is not supported. (13) Candidate values ​​for component 1: {1, 2, 3, 4, 5, 6, 7, 8}. Candidate values ​​for component 2: {1, 2}. A UE that supports FG 40-7-1 must support at least one of FGs 40-7-1a / b / c / d.

[0088] [Function 40-7-1a] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1a. (3) Codebook-based 8Tx PUSCH - Codebook 1. (4) 1. Support for codebook-based 8Tx PUSCH - Codebook 1. 2. Support for (N1,N2) for codebook-based 8Tx PUSCH - Codebook 1. 3. SRS 8Tx port - Codebook (for Codebook 1). (5) 40-7-1. (8) Codebook-based 8Tx PUSCH - Codebook 1 is not supported. (13) Candidate values ​​for component 2: {(4,1), (2,2), both}. Candidate values ​​for component 3: {noTDM, TDM, and noTDM}.

[0089] [Feature 40-7-1b] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1b. (3) Codebook-based 8Tx PUSCH - Codebook 2. (4) 1. Support for codebook-based 8Tx PUSCH - Codebook 2. 2. SRS 8Tx port - Codebook (for Codebook 2). (5) 40-7-1. (8) Codebook-based 8Tx PUSCH - Codebook 2 is not supported. (13) Candidate values ​​for component 2: {noTDM, TDM, and noTDM}.

[0090] [Feature 40-7-1c] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1c. (3) Codebook-based 8Tx PUSCH - Codebook 3. (4) 1. Supports codebook-based 8Tx PUSCH - Codebook 3. 2. SRS 8Tx port - Codebook (for Codebook 3). (5) 40-7-1. (8) Codebook-based 8Tx PUSCH - Codebook 3 is not supported. (13) Candidate values ​​for component 2: {noTDM, TDM, and noTDM}.

[0091] [Feature 40-7-1d] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1d. (3) Codebook-based 8Tx PUSCH - Codebook 4. (4) 1. Support for codebook-based 8Tx PUSCH - Codebook 4. 2. SRS 8Tx port - Codebook (for Codebook 4). (5) 40-7-1. (8) Codebook-based 8Tx PUSCH - Codebook 4 is not supported. (13) Candidate values ​​for component 2: {noTDM, TDM, and noTDM}.

[0092] Variation 1: The component of FG40-7-1 may include "3. SRS 8Tx ports - Codebook" and the corresponding annotation "Component 3 candidate values: {noTDM, TDM and noTDM}" may not be included. While FG40-7-1 indicates support for 8-port SRS, whether TDM / noTDM 8-port SRS is supported for each codebook type may be further reported in FG40-7-1a / 1b / 1c / 1d.

[0093] Variation 2: The component of FG 40-7-1 may include "3. SRS 8Tx ports - codebook" and the corresponding annotation may include "Candidate values ​​for component 3: {noTDM, TDM and noTDM}". Component 3 of FG 40-7-1 indicates general capability, while component 3 of 40-7-1a / b / c / d indicates specific capability for a codebook that overrides component 3 of FG 40-7-1. The added component may also be applied to some codebooks. Examples of some codebooks include: - Codebooks other than codebook 4 (because if TDM is supported, there is no reason why the UE cannot support codebook 4); - Codebook 1 and codebook 2; - Codebook 1 only.

[0094] According to this embodiment, it is possible to flexibly inform the gNB for each codebook type whether to support 8-port SRS when TDM is applied or when TDM is not applied.

[0095] Second Embodiment A candidate value corresponding to the component "3. SRS 8 Tx ports - codebook" of FG 40-7-1 may not be included, and another corresponding FG may be included. For example, functions corresponding to the codebook of 8 Tx ports (8 ports) SRS (40-7-1, 40-7-1x, 40-7-1y, 40-7-1x1-x4) may be transmitted as capability information, separately from functions corresponding to the codebook-based 8 Tx (8 ports) PUSCH (40-7-1, 40-7-1a, b, c, d).

[0096] For each function described below, the contents of items (6), (7), (9), (10), (11), (12), and (14) may be, for example, as follows: (6) YES (7) n / a (9) Per FSPC (10) No (11) No (12) No (14) Optional function with capability signaling.

[0097] <<Option 1>> Two (or three) independent FGs may be added (40-7-1x, 40-7-1y), each corresponding to one or more codebook types. That is, each FG (one FG) may indicate support for an 8-port SRS for codebook-based PUSCH for one or more codebook types. For example, one FG may be for codebook 1 (precondition FG 40-7-1a), and another may be for codebooks 2 / 3 / 4 (precondition FGs 40-7-1b / 1c / 1d).

[0098] [Function 40-7-1] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1. (3) Basic functions of codebook-based 8Tx PUSCH. (4) 1. Maximum number of PUSCH MIMO layers for codebook-based PUSCH. 2. Maximum number of 8-port SRS resources per SRS resource set with usage set to "codebook" for codebook-based 8Tx PUSCH. (5)-(8) Codebook-based 8Tx PUSCH is not supported. (13) Candidate values ​​for component 1: {1, 2, 3, 4, 5, 6, 7, 8}. Candidate values ​​for component 2: {1, 2}. A UE that supports FG 40-7-1 must support at least one of FGs 40-7-1a / b / c / d.

[0099] [Function 40-7-1a] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1a. (3) Codebook-based 8Tx PUSCH - Codebook 1. (4) 1. Support for codebook-based 8Tx PUSCH - Codebook 1. 2. Support for (N1,N2) for codebook-based 8Tx PUSCH - Codebook 1. (5) 40-7-1. (8) Codebook-based 8Tx PUSCH - Codebook 1 is not supported. (13) Candidate values ​​for component 2: {(4,1), (2,2), both}.

[0100] [Feature 40-7-1b] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1b. (3) Codebook-based 8Tx PUSCH - Codebook 2. (4) 1. Codebook-based 8Tx PUSCH - Codebook 2 support. (5) 40-7-1. (8) Codebook-based 8Tx PUSCH - Codebook 2 is not supported. (13)-

[0101] [Feature 40-7-1c] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1c. (3) Codebook-based 8Tx PUSCH - Codebook 3. (4) 1. Codebook-based 8Tx PUSCH - Codebook 3 support. (5) 40-7-1. (8) Codebook-based 8Tx PUSCH - Codebook 3 is not supported. (13)-

[0102] [Feature 40-7-1d] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1d. (3) Codebook-based 8Tx PUSCH - Codebook 4. (4) 1. Codebook-based 8Tx PUSCH - Codebook 4 support. (5) 40-7-1. (8) Codebook-based 8Tx PUSCH - Codebook 4 is not supported. (13)-

[0103] [Feature 40-7-1x] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1x. (3) SRS 8 Tx ports - Codebook, for Codebook 1. (4) Support for SRS with 8 Tx ports for Codebook-based PUSCH for Codebook 1. (5) 40-7-1a. (8)-(13) Candidate values ​​for Component 1: {noTDM, TDM, and noTDM}.

[0104] [Feature 40-7-1y] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1y. (3) SRS 8 Tx Ports - Codebook, for Codebooks 2, 3, and 4. (4) 1. Support for SRS with 8 Tx ports for codebook-based PUSCH for Codebooks 2, 3, and 4. (5) 40-7-1b, 40-7-1c, or 40-7-1d. (8)-(13) Candidate values ​​for Component 1: {noTDM, TDM, and noTDM}.

[0105] For example, three independent FGs may be added, one for codebook 1 (precondition FG is 40-7-1a), another for codebook 2 / 3 (precondition FG is 40-7-1b / 1c), and another for codebook 4 (precondition FG is 40-7-1d).

[0106] <<Option 2>> Separate FGs (prerequisite FGs 40-7-1a, 1b, 1c, and 1d) for codebook types 1 to 4 may be added. Specifically, in addition to 40-7-1 and 40-7-1a to 40-7-1d in option 1, the following functions may be added. Also, restriction A in the first embodiment may be applied.

[0107] [Feature 40-7-1x1] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1x1. (3) SRS 8 Tx ports - Codebook, for Codebook 1. (4) Support for SRS with 8 Tx ports for Codebook-based PUSCH for Codebook 1. (5) 40-7-1a. (8)-(13) Component 1 candidate values: {noTDM, TDM, and noTDM}.

[0108] [Feature 40-7-1x2] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1x2. (3) SRS 8 Tx ports - Codebook, for Codebook 2. (4) Support for SRS with 8 Tx ports for Codebook-based PUSCH for Codebook 2. (5) 40-7-1b. (8)-(13) Component 1 candidate values: {noTDM, TDM, and noTDM}.

[0109] [Feature 40-7-1x3] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1x3. (3) SRS 8 Tx ports - Codebook, for Codebook 3. (4) Support for SRS with 8 Tx ports for Codebook-based PUSCH for 1. Codebook 3. (5) 40-7-1c. (8)-(13) Component 1 candidate values: {noTDM, TDM, and noTDM}.

[0110] [Feature 40-7-1x4] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1x4. (3) SRS 8 Tx ports - Codebook, for Codebook 4. (4) 1. Support for SRS with 8 Tx ports for codebook-based PUSCH for Codebook 4. (5) 40-7-1d. (8)-(13) Candidate values ​​for Component 1: {noTDM, TDM, and noTDM}.

[0111] <<Option 3>> One independent FG (prerequisite FG is 40-7-1) may be added.

[0112] <<<Option 3a>>> An additional independent FG may include multiple (e.g., two or three) components, each corresponding to one or more codebook types. For example, each component may indicate support for an 8-port SRS for codebook-based PUSCH for one or more codebook types. For example, one component may be for codebook 1 and another for codebooks 2 / 3 / 4. Specifically, in addition to 40-7-1 and 40-7-1a to 40-7-1d of Option 1, the following functions may be added:

[0113] [Feature 40-7-1x] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1x. (3) SRS 8 Tx Ports - Codebook, for codebooks 1, 2, 3, and 4. (4) 1. Support for SRS with 8 Tx ports for codebook-based PUSCH for codebook 1. 2. Support for SRS with 8 Tx ports for codebook-based PUSCH for codebooks 2, 3, and 4. (5) 40-7-1a, 40-7-1b, 40-7-1c, or 40-7-1d. (8)-(13) Candidate values ​​for component 1: {noTDM, TDM, and noTDM}. Candidate values ​​for component 2: {noTDM, TDM, and noTDM}.

[0114] For example, there may be three components in one separate FG added, one for codebook 1, one for codebook 2 / 3, and one for codebook 4.

[0115] <<<Option 3b>>> One independent FG to be added includes multiple (e.g., four) components, each corresponding to codebooks 1 to 4. For example, one component may indicate support for an SRS with eight ports for a codebook-based PUSCH for one codebook type. Specifically, in addition to 40-7-1 and 40-7-1a to 40-7-1d in Option 1, the following functions may be added. Furthermore, Restriction A of the first embodiment may also be applied.

[0116] [Feature 40-7-1x] (1) 40.NR_MIMO_evo_DL_UL. (2) 40-7-1x. (3) SRS 8 Tx Ports - For codebooks 1, 2, 3, and 4. (4) 1. Support for SRS with 8 Tx ports for codebook-based PUSCH for codebook 1. 2. Support for SRS with 8 Tx ports for codebook-based PUSCH for codebook 2. 3. Support for SRS with 8 Tx ports for codebook-based PUSCH for codebook 3. 4. Support for SRS with 8 Tx ports for codebook-based PUSCH for codebook 3. (5) 40-7-1a, 40-7-1b, 40-7-1c, or 40-7-1d. (8)-(13) Candidate values ​​for component 1: {noTDM, TDM, and noTDM}. Possible values ​​for component 2: {noTDM, TDM and noTDM}. Possible values ​​for component 3: {noTDM, TDM and noTDM}. Possible values ​​for component 4: {noTDM, TDM and noTDM}.

[0117] According to this embodiment, in addition to the function corresponding to the codebook-based 8-port PUSCH, it is possible to transmit the function corresponding to the codebook of SRS using 8 ports, so that the function corresponding to the codebook of SRS using 8 ports can be flexibly set.

[0118] <Third embodiment> It is necessary to consider both a UE / gNB to which at least a part of the first / second embodiment can be applied (new UE #2 / gNB #2) and a UE / gNB to which it cannot be applied (old UE #1 / gNB #1). Specific examples will be described below. Hereinafter, "new UE capability signaling" may mean at least a part of the functions of the first / second embodiment (transmission / reception of capability information including the functions). "Previous UE capability signaling" may mean functions excluding at least a part of the functions of the first / second embodiment (transmission / reception of capability information including the functions). In this embodiment, "understand" may be read as "send", "receive", "apply", "support", etc.

[0119] Old UE #1 / gNB #1 may only understand the previous UE capability signaling, and new UE #2 / gNB #2 may understand both the previous and new UE capability signaling.

[0120] The old UE #1 may report only the previous UE capability signaling. In this case, a predetermined rule may be defined. For example, when reporting the previous UE capability signaling, the "candidate values ​​for component 3: {noTDM, TDM and noTDM}" of FG40-7-1 may be applied to all codebooks 1, 2, 3 and 4.

[0121] New UE #2 may report both the previous UE capability signaling and the new UE capability signaling. In this case, old gNB #1 may read the previous UE capability signaling and ignore the new UE capability signaling. Also, new gNB #2 may read the new UE capability signaling and ignore the old UE capability signaling.

[0122] <<Variation 1>> The new UE #2 may only report the new UE capability signaling. The UE may not assume the existence of the old gNB #1. The new gNB #2 may read the new UE capability signaling.

[0123] <<Variation 2>> The gNB may notify the UE that the gNB can understand the new UE capability signaling before the UE reports the UE capability signaling. The new UE #2 may select the UE capability signaling to report in response to the notification. If the gNB can understand the new UE capability signaling, the new UE #2 may report the new UE capability signaling. The UE capability inquiry (UECapabilityEnquiry) may be used by the gNB to notify the above information.

[0124] Figure 2 is a diagram showing an overview of UE capability inquiry (UECapabilityEnquiry). Before UE capability signaling (transmission / reporting of UE capability information), the network (gNB) notifies the UE which UE capabilities it requests (UECapabilityEnquiry). In response to this notification, the UE transmits UE capability information to the network (gNB). The process of Figure 2 may be used to transmit the functions (included in the UE capability information) of the first and second embodiments.

[0125] The mechanism in Figure 2 is primarily used to inform the UE of the bands / band combos that the gNB supports. However, this mechanism is reused in Rel. 16 to limit the combinations of CSI codebook UE capability signaling to avoid a large number of UE capability signaling bits.

[0126] To reduce UE capability signaling, the network (gNB) may send a UE capability inquiry to the UE, which includes a request to specify the codebook that the UE will report.

[0127] <Supplementary Information> <<Notification of Information to UE>> In the above-described embodiments, notification of any information to the UE [from a Network (NW) (e.g., a Base Station (BS))] (in other words, reception of any information from the BS by the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0128] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0129] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0130] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

[0131] <<Notification of Information from UE>> In the above-described embodiments, notification of any information from the UE [to the NW] (in other words, transmission / report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0132] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

[0133] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0134] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0135] <<Regarding Application of Each Embodiment>> In a UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the above-mentioned embodiments may be applied (used) when one or more of the following conditions are met: - a higher layer parameter indicating the specific processes / operations / controls / assumptions / information is configured; - the specific processes / operations / controls / assumptions / information is determined based on related higher layer parameters; - the specific processes / operations / controls / assumptions / information is specified / activated / triggered by a MAC CE / DCI / UCI / resource / channel / RS; - a specific UE capability indicating (or related to) the specific processes / operations / controls / assumptions / information is reported or supported; - the application of the specific processes / operations / controls / assumptions / information is determined based on specific conditions.

[0136] The specific UE capability may indicate at least one of the following: - Supporting the specific process / operation / control / assumption / information; - Supporting SRS transmission via 8 ports.

[0137] Furthermore, the above-mentioned specific UE capabilities and the UE capabilities (each function) of each embodiment may be capabilities that are applied across all frequencies (commonly regardless of frequency), or may be capabilities for each frequency (e.g., one or a combination of a cell, band, band combination, BWP, component carrier, etc.), or may be capabilities for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be capabilities for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be capabilities for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0138] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0139] If the above conditions are not met, the UE / BS may follow the behavior specified in existing 3GPP releases.

[0140] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment of the present disclosure. [Supplementary Note 1] A terminal having: a transmitter that transmits capability information indicating whether a Sounding Reference Signal (SRS) using 8 ports is supported when Time Division Multiplexing (TDM) is applied or when TDM is not applied, for each codebook type; and a controller that controls transmission of the SRS using 8 ports. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the transmitter transmits, as the capability information, a capability corresponding to a codebook of the SRS using 8 ports, separately from a capability corresponding to a codebook-based 8-port PUSCH. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein one feature group (FG) indicates support of an SRS with 8 ports for a codebook-based PUSCH for one or more codebook types. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein one feature group (FG) includes multiple components, and each component indicates support for SRS with 8 ports for codebook-based PUSCH for one or more codebook types.

[0141] (Wireless Communication System) The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof.

[0142] 3 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 (which may be simply referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0143] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0144] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0145] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0146] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The location, number, shape, size, etc. of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as the base station 10.

[0147] The wireless communication system 1 may utilize multi-input multi-output (MIMO). For example, one cell may be formed by one antenna / base station 10, or may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a supercell) may be composed of multiple [virtual] cells (which may be called, for example, subcells). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell with a quasi-static / dynamically variable physical range. In this case, the wireless communication system 1 may be called a cell-free system.

[0148] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).

[0149] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.

[0150] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0151] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 / Xn interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0152] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0153] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

[0154] The user terminal 20 may be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

[0155] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0156] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0157] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.

[0158] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), or the like may be used as an uplink channel.

[0159] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

[0160] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.

[0161] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

[0162] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

[0163] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

[0164] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0165] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0166] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.

[0167] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

[0168] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0169] (Base Station) Fig. 4 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0170] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0171] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0172] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0173] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0174] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, the RF unit 122, and a measurement unit 123.

[0175] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0176] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0177] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0178] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0179] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0180] The transceiver unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.

[0181] On the other hand, the transceiver unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 130.

[0182] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0183] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0184] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0185] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0186] The base station 10 may be separated into three elements: a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may implement higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement the functions of the PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer.

[0187] In the present disclosure, the base station 10 may include a single device that realizes all of the functions of the RU, DU, and CU, or may include multiple devices that each realize some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.

[0188] The transceiver 120 may receive capability information indicating whether it supports a Sounding Reference Signal (SRS) using 8 ports when Time Division Multiplexing (TDM) is applied or when TDM is not applied for each codebook type.

[0189] The control unit 110 may control reception of the SRS using eight ports.

[0190] (User Terminal) Fig. 5 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0191] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0192] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

[0193] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals and transfer them to the transceiver unit 220.

[0194] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0195] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0196] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0197] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0198] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0199] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0200] The transmitter / receiver unit 220 (transmission processing unit 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0201] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.

[0202] The transceiver unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.

[0203] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 230.

[0204] The transceiver unit 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.

[0205] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0206] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

[0207] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0208] The transceiver 220 may transmit capability information indicating whether it supports Sounding Reference Signal (SRS) using 8 ports when Time Division Multiplexing (TDM) is applied or when TDM is not applied, for each codebook type.

[0209] The control unit 210 may control the transmission of the SRS using eight ports.

[0210] (Hardware Configuration) Note that the block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0211] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

[0212] For example, a base station, a user terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 6 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0213] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0214] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0215] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading specified software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0216] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0217] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

[0218] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0219] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

[0220] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0221] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0222] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0223] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0224] In addition, the devices included in the core network 30 (for example, network nodes that provide NF) may also be realized by the above-mentioned functional block / hardware configuration.

[0225] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0226] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0227] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

[0228] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may also be a time unit based on numerology.

[0229] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0230] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0231] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0232] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0233] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0234] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0235] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0236] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0237] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0238] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.

[0239] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0240] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0241] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0242] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0243] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0244] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0245] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0246] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0247] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0248] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0249] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0250] With respect to any information (e.g., variables, constants, parameters) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE / base station) may notify any second device (e.g., base station / UE) of information indicating / specifying (or relating to) the value of the any information.

[0251] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0252] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0253] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0254] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0255] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0256] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.

[0257] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0258] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.

[0259] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0260] The group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0261] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0262] In addition, in the present disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0263] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0264] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0265] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

[0266] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0267] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0268] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

[0269] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0270] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0271] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0272] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0273] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0274] 7 is a diagram showing an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0275] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by a user.

[0276] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0277] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0278] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0279] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0280] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

[0281] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

[0282] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).

[0283] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.

[0284] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0285] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

[0286] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as an uplink channel and a downlink channel may be read as a sidelink channel.

[0287] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0288] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0289] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0290] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0291] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0292] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0293] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0294] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0295] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

[0296] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."

[0297] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ..." or "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ..." or "does not ... (if the above "..." is a to-infinitive, a verb with "to")," etc. Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

[0298] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0299] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0300] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0301] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0302] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0303] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0304] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

[0305] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

[0306] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0307] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0308] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A terminal having a transmitter that transmits capability information indicating whether a Sounding Reference Signal (SRS) using 8 ports is supported when Time Division Multiplexing (TDM) is applied or when TDM is not applied for each codebook type, and a control unit that controls the transmission of the SRS using the 8 ports.

2. The terminal according to claim 1, wherein the transmitting unit transmits, as the capability information, a function corresponding to a codebook of the SRS using 8 ports, separately from a function corresponding to a codebook-based 8-port PUSCH.

3. The terminal according to claim 1, wherein one feature group (FG) indicates support for an SRS with 8 ports for a codebook-based PUSCH for one or more codebook types.

4. The terminal according to claim 1, wherein one feature group (FG) includes multiple components, each component indicating support for SRS with 8 ports for codebook-based PUSCH for one or more codebook types.

5. A wireless communication method for a terminal, comprising: a step of transmitting capability information indicating whether a Sounding Reference Signal (SRS) using 8 ports is supported when Time Division Multiplexing (TDM) is applied or when TDM is not applied for each codebook type; and a step of controlling transmission of the SRS using the 8 ports.

6. A base station having a receiver that receives capability information indicating whether a Sounding Reference Signal (SRS) using 8 ports is supported when Time Division Multiplexing (TDM) is applied or when TDM is not applied for each codebook type, and a controller that controls reception of the SRS using 8 ports.

Images