Terminal, wireless communication method and system
By configuring SRS resources with multiple ports and adjusting the SRI field size, the method addresses the excessive overhead in non-codebook PUSCH transmissions, improving communication efficiency with multiple antenna ports.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- NTT DOCOMO INC
- Filing Date
- 2022-07-07
- Publication Date
- 2026-06-19
AI Technical Summary
The communication overhead in non-codebook uplink shared channel (PUSCH) transmissions with 8 ports is excessive due to the fixed size of the SRS Resource Indicator (SRI) field, which hinders flexible control of UL transmission using more than 4 antenna ports, limiting communication throughput.
A method where the UE configures SRS resources with multiple ports and maps them using a table to reduce the number of SRS resources, allowing the SRI field size to be adjusted, thereby reducing communication overhead.
This approach enables efficient control of UL transmission with more than 4 antenna ports, minimizing communication overhead and enhancing throughput.
Smart Images

Figure 0007876614000001 
Figure 0007876614000002 
Figure 0007876614000003
Abstract
Description
[Technical Field]
[0001] This disclosure relates to terminals, wireless communication methods, and in next-generation mobile communication systems. system Regarding. [Background technology]
[0002] Long Term Evolution (LTE) was specified for Universal Mobile Telecommunications System (UMTS) networks with the aim of achieving even higher data rates and lower latency (Non-Patent Literature 1). Furthermore, LTE-Advanced (3GPP Rel.10-14) was specified for the aim of further increasing capacity and sophistication of LTE (Third Generation Partnership Project (3GPP®) Release (Rel.) 8, 9).
[0003] Successor systems to LTE (for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.) are also being considered. [Prior art documents] [Non-patent literature]
[0004] [Non-Patent Document 1] 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 [Overview of the project] [Problems that the invention aims to solve]
[0005] Rel.15 NR supports uplink (UL) Multi-Input Multi-Output (MIMO) transmission up to 4 layers. For future NRs, support for UL transmission with more than 4 layers is being considered to achieve higher spectral efficiency. For example, for Rel.18 NR, up to 6 ranks of transmission using 6 antenna ports, and up to 6 or 8 ranks of transmission using 8 antenna ports are being considered.
[0006] For non-code book uplink shared channel (Physical Uplink Shared Channel (PUSCH)) transmissions with 8 ports up to 8 layers, when 8 1-port Sounding Reference Signal (SRS) resources are configured for the non-code book, the size of the SRS Resource Indicator (SRI) field included in the Downlink Control Information (DCI) format that schedules the PUSCH will be 8 bits.
[0007] However, constantly and flexibly directing eight SRS resources means that the size of the SRI field for the non-codebook PUSCH (e.g., the number of SRS resources) becomes a communication overhead. It is preferable to be able to appropriately adjust (control) the size of the DCI. Otherwise, the increase in communication throughput may be suppressed.
[0008] Therefore, this disclosure provides a terminal, wireless communication method, and a terminal capable of appropriately controlling UL transmission using more than 4 antenna ports. system One of the objectives is to provide [this]. [Means for solving the problem]
[0009] A terminal according to one aspect of the present disclosure includes a sounding reference signal (SRS) resource indicator (SRI) field, and a receiving unit that receives downlink control information (DCI) for scheduling non-codebook physical uplink shared channel (PUSCH) transmission, and the SRI field value specified by ruS and a control unit that controls the PUSCH transmission based on the RS resource. Each of the SRS resources has multiple SRS ports associated with it, and if the value of the SRI field is a specific value, the control unit applies the SRS port with the smallest index among the multiple SRS ports associated with the SRS resource specified by the specific value to the PUSCH transmission. It is characterized by having
Advantages of the Invention
[0010] According to one aspect of the present disclosure, UL transmission using more than 4 antenna ports can be appropriately controlled.
Brief Description of the Drawings
[0011] [Figure 1] FIG. 1 is a diagram showing an example of the association between the SRI field index and one or more SRIs when Lmax = 1. [Figure 2] FIG. 2 is a diagram showing an example of the association between the SRI field index and one or more SRIs when Lmax = 2. [Figure 3] FIG. 3 is a diagram showing an example of the association between the SRI field index and one or more SRIs when Lmax = 3. [Figure 4] FIG. 4 is a diagram showing an example of the association between the SRI field index and one or more SRIs when Lmax = 4. [Figure 5] FIGS. 5A and 5B are diagrams showing an example of an antenna layout of 8 antenna ports. [Figure 6] FIGS. 6A - 6C are diagrams showing an example of an antenna layout of 8 antenna ports for explaining coherent information. [Figure 7] FIG. 7 shows an example of the mapping of the SRS resource indicated by SRI. [Figure 8] FIG. 8 is a diagram showing an example of the association between the SRS resource ID and the number of SRS ports according to the first embodiment. [Figure 9] FIG. 9 shows an example of the mapping of the SRS resource indicated by SRI according to the first embodiment. [Figure 10] FIG. 10 shows another example of the mapping of the SRS resource indicated by SRI according to the first embodiment. [Figure 11] FIG. 11 is a diagram showing an example of the association between the SRS resource ID and the number of SRS ports according to Embodiment 2.1. [Figure 12] FIG. 12 is a diagram showing an example of the association between the SRS resource ID and the number of SRS ports according to Embodiment 2.3. [Figure 13] FIG. 13 is a diagram showing an example of the schematic configuration of a wireless communication system according to an embodiment. [Figure 14] FIG. 14 is a diagram showing an example of the configuration of a base station according to an embodiment. [Figure 15] FIG. 15 is a diagram showing an example of the configuration of a user terminal according to an embodiment. [Figure 16] FIG. 16 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 17] FIG. 17 is a diagram showing an example of a vehicle according to an embodiment.
MODE FOR CARRYING OUT THE INVENTION
[0012] (Control of Transmission of SRS and PUSCH) In Rel.15 NR, a terminal (user terminal, User Equipment (UE)) may receive information used to transmit a measurement reference signal (e.g., a Sounding Reference Signal (SRS)) (e.g., SRS configuration information, for example, parameters in the "SRS-Config" of the RRC control element).
[0013] Specifically, the UE may receive at least one of the following: information about one or more SRS resource sets (SRS resource set information, e.g., "SRS-ResourceSet" of the RRC control element) and information about one or more SRS resources (SRS resource information, e.g., "SRS-Resource" of the RRC control element).
[0014] A single SRS resource set may be associated with a predetermined number of SRS resources (a predetermined number of SRS resources may be grouped together). Each SRS resource may be identified by an SRS Resource Indicator (SRI) or an SRS Resource Identifier.
[0015] SRS resource set information may include the SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, the SRS resource type, and information on the SRS usage.
[0016] Here, the SRS resource type may be one of the following: Periodic SRS (P-SRS), Semi-Persistent SRS (SP-SRS), or Aperiodic CSI (A-SRS). The UE may send P-SRS and SP-SRS periodically (or periodically after activation), and A-SRS based on DCI's SRS request.
[0017] Furthermore, the application (RRC parameter "usage", L1 (Layer-1) parameter "SRS-SetUse") may be, for example, beam management, codebook (CB), noncodebook (NCB), antenna switching, etc. SRS for codebook or noncodebook applications may be used to determine the precoder for SRI-based codebook-based or noncodebook-based uplink shared channel (PUSCH) transmission.
[0018] For example, in the case of codebook-based transmission, the UE may determine the precoder (precoding matrix) for PUSCH transmission based on the SRI, Transmitted Rank Indicator (TRI), and Transmitted Precoding Matrix Indicator (TPMI). In the case of non-codebook-based transmission, the UE may determine the precoder for PUSCH transmission based on the SRI.
[0019] SRS resource information may include SRS resource ID (SRS-ResourceId), number of SRS ports, SRS port number, transmit comb, SRS resource mapping (e.g., time and / or frequency resource location, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hopping-related information, SRS resource type, sequence ID, SRS spatial relationship information, etc.
[0020] The spatial relationship information of the SRS (for example, the "spatialRelationInfo" element of the RRC information element) 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 (for example, another SRS). The SS / PBCH block may be called a Synchronization Signal Block (SSB).
[0021] The spatial relationship information of the SRS may include at least one of the following as an index for the predetermined reference signal: the SSB index, the CSI-RS resource ID, and the SRS resource ID.
[0022] In this disclosure, the terms SSB index, SSB resource ID, and SSB Resource Indicator (SSBRI) may be interpreted interchangeably. Similarly, the terms CSI-RS index, CSI-RS resource ID, and CSI-RS Resource Indicator (CRI) may be interpreted interchangeably. Furthermore, the terms SRS index, SRS resource ID, and SRI may be interpreted interchangeably.
[0023] The spatial relationship information of the SRS may include a serving cell index, BWP index (BWP ID), etc., corresponding to the predetermined reference signal mentioned above.
[0024] If a UE configures spatial relationship information regarding an SSB or CSI-RS and an SRS resource, it may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain receive filter) used for receiving the SSB or CSI-RS. 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.
[0025] If a UE sets spatial relationship information regarding a target SRS resource and another SRS (reference SRS), it may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the one used for transmitting the reference SRS. In other words, in this case, the UE may assume that the UE transmit beam for the reference SRS and the UE transmit beam for the target SRS are the same.
[0026] The UE may determine the spatial relationships of the PUSCH scheduled by the DCI (e.g., DCI format 0_1) based on the value of a predetermined field (e.g., the SRS resource identifier (SRI) field). Specifically, the UE may use spatial relationship information of the SRS resource (e.g., "spatialRelationInfo" of the RRC information element) determined based on the value of the predetermined field (e.g., SRI) for the PUSCH transmission.
[0027] In Rel.15 / 16 NR, when using codebook-based transmission for PUSCH, the UE may have up to two SRS resources, with the codebook's SRS resource set configured by the RRC, and one of those up to two SRS resources indicated by the DCI (1-bit SRI field). The PUSCH transmit beam will be specified by the SRI field.
[0028] The UE may determine the TPMI and layer number (transmit rank) for PUSCH based on the precoding information and layer number field (hereinafter also referred to as the precoding information field). The UE may select a precoder from the uplink codebook for the same number of ports as the number of SRS ports indicated by the higher layer parameter "nrofSRS-Ports" set for the SRS resource specified by the SRI field, based on the TPMI, layer number, etc.
[0029] In Rel.15 / 16 NR, when using non-codebook-based transmission for PUSCH, the UE may have up to four SRS resources, with the non-codebook SRS resource set configured by the RRC, and one or more of these up to four SRS resources may be indicated by the DCI (2-bit SRI field).
[0030] The UE may determine the number of layers (transmission rank) for PUSCH based on the above SRI field. For example, the UE may determine that the number of SRS resources specified by the above SRI field is the same as the number of layers for PUSCH. The UE may also calculate the precoder for the above SRS resources.
[0031] If a CSI-RS (which may also be called an associated CSI-RS) associated with the SRS resource (or the SRS resource set to which the SRS resource belongs) is configured at a higher layer, the PUSCH transmit beam may be calculated based on the configured associated CSI-RS (measurements). Otherwise, the PUSCH transmit beam may be specified by the SRI.
[0032] Furthermore, the UE may be configured to use either codebook-based or non-codebook-based push transmission via a higher-layer parameter "txConfig" that indicates the transmission scheme. This parameter may represent the values "codebook" or "noncodebook".
[0033] In this disclosure, codebook-based PUSCH (codebook-based PUSCH transmission, codebook-based transmission, codebook MIMO) may mean PUSCH when “codebook” is set as the transmission scheme for the UE. In this disclosure, non-codebook-based PUSCH (non-codebook-based PUSCH transmission, non-codebook-based transmission, non-codebook MIMO) may mean PUSCH when “non-codebook” is set as the transmission scheme for the UE.
[0034] (Determination of the PUSCH precoder in codebook (CB) based transmission) As mentioned above, in the case of codebook (CB) based transmission, the UE may determine the precoder for PUSCH transmission based on SRI, TRI, TPMI, etc.
[0035] SRI, TRI, TPMI, etc., may be notified to the UE using Downlink Control Information (DCI). SRI may be specified by the SRS Resource Indicator field (SRI field) of the DCI, or by the parameter "srs-ResourceIndicator" included in the RRC information element "ConfiguredGrantConfig" of the configured grant PUSCH.
[0036] TRI and TPMI may also be specified by the DCI's "Precoding information and number of layers" field. For simplicity, the "Precoding information and number of layers" field is also referred to as the "Precoding information field."
[0037] The UE may report UE capability information regarding the precoder type, and the base station may set the precoder type based on this UE capability information via upper-layer signaling. This UE capability information may also be information about the precoder type that the UE uses in PUSCH transmission (for example, it may be represented by the RRC parameter "pusch-TransCoherence").
[0038] The UE may determine which precoder to use for PUSCH transmission based on precoder type information (e.g., the RRC parameter "codebookSubset") contained in PUSCH configuration information (e.g., the "PUSCH-Config" information element of the RRC signaling) notified by higher-layer signaling. The UE may also set a subset of the PMI specified by TPMI using codebookSubset.
[0039] The precoder type may be specified by fully coherent, partially coherent, or non-coherent, or by a combination of at least two of these (for example, they may be represented by parameters such as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent").
[0040] For example, the RRC parameter "pusch-TransCoherence" indicating UE capability may indicate full coherent, partial coherent, or noncoherent. Similarly, the RRC parameter "codebookSubset" may indicate "fullyAndPartialAndNonCoherent," "partialAndNonCoherent," or "noncoherent."
[0041] Fully coherent may mean that all antenna ports used for transmission are synchronized (this may also be expressed as being able to align phases, being able to control phase for each coherent antenna port, or being able to apply a precoder appropriately to each coherent antenna port). Partially coherent may mean that some of the antenna ports used for transmission are synchronized, but those ports are not synchronized with the others. Non-coherent may mean that the individual antenna ports used for transmission are not synchronized.
[0042] Furthermore, a UE that supports fully coherent precoder types may be assumed to support partially coherent and noncoherent precoder types. A UE that supports partially coherent precoder types may be assumed to support noncoherent precoder types.
[0043] In this disclosure, precoder type, coherency, push transmission coherence, coherent type, coherence type, codebook type, codebook subset, codebook subset type, etc., may be interpreted interchangeably.
[0044] The UE may determine a precoding matrix from multiple precoders (which may also be called precoding matrices, codebooks, etc.) for CB-based transmissions that corresponds to the TPMI index obtained from the DCI (e.g., DCI format 0_1; hereafter the same) for scheduling UL transmissions.
[0045] A precoding matrix in which each column has exactly one non-zero element may be called a non-coherent codebook. A precoding matrix in which each column has a specific number of non-zero elements (greater than one, but not the total number of elements in the column) may be called a partially coherent codebook. A precoding matrix in which all elements in each column are non-zero may be called a fully coherent codebook.
[0046] Non-coherent codebooks and partially coherent codebooks may also be called antenna selection precoders, antenna port selection precoders, etc. For example, a non-coherent codebook (non-coherent precoder) may also be called a one-port selection precoder, a one-port port selection precoder, etc. A partially coherent codebook (partially coherent precoder) may also be called an x-port (x is an integer greater than 1) selection precoder, a port selection precoder for x ports, etc. A fully coherent codebook may also be called a non-antenna selection precoder, an all-port precoder, etc.
[0047] In this disclosure, a partially coherent codebook may refer to a subset of codebooks (precoding matrices) corresponding to TPMIs specified by DCI for codebook-based transmission, obtained by a UE with a partially coherent codebook subset (e.g., RRC parameter "codebookSubset" = "partialAndNonCoherent") set, excluding the codebooks corresponding to TPMIs specified by a UE with a noncoherent codebook subset (e.g., RRC parameter "codebookSubset" = "nonCoherent") set (i.e., for single-layer transmission with 4 antenna ports, the codebooks for TPMIs 4 through 11).
[0048] In this disclosure, a fully coherent codebook may refer to a subset of fully coherent codebooks (e.g., RRC parameter "codebookSubset" = "fullyAndPartialAndNonCoherent") set to a UE that corresponds to a TPMI specified by DCI for codebook-based transmission, excluding the codebooks corresponding to TPMIs specified by a UE that has a partially coherent codebook subset (e.g., RRC parameter "codebookSubset" = "partialAndNonCoherent") set to a UE (i.e., for single-layer transmission with 4 antenna ports, the codebooks for TPMIs 12 to 27).
[0049] Hereinafter, for simplicity, non-coherent precoders, partially coherent precoders, and fully coherent precoders will also be referred to simply as NC (non-coherent) precoders, PC (partial coherent) precoders, and FC (full coherent) precoders, respectively.
[0050] Furthermore, in this disclosure, for simplicity, an NC / PC / FC precoder for i-layer (i is an integer; i=1 for single-layer) transmission of n antenna ports (n is an integer) will also simply be referred to as an n-port i-layer NC / PC / FC precoder.
[0051] (Size of the pre-coding information field) As described above, the UE may determine the TPMI and layer number (transmission rank) for a PUSCH based on the precoding information field of the DCI (e.g., DCI format 0_1 / 0_2) that schedules the PUSCH.
[0052] For codebook-based PUSCH, the number of bits in the precoding information field may be determined (and may vary) based on settings such as enabling or disabling the transform precoder for PUSCH (e.g., upper layer parameter transformPrecoder), setting the codebook subset for PUSCH (e.g., upper layer parameter codebookSubset), setting the maximum number of layers for PUSCH (e.g., upper layer parameter maxRank), setting uplink full power transmission for PUSCH (e.g., upper layer parameter ul-FullPowerTransmission), and the number of antenna ports for PUSCH.
[0053] The number of layers and TPMI corresponding to a value in a certain precoding information field may be the same (common) regardless of the codebook subset set in the UE.
[0054] Note that the precoding information field may be 0 bits for non-codebook-based pushers. Also, the precoding information field may be 0 bits for codebook-based pushers with one antenna port.
[0055] (Size of the SRI field for non-codebook-based PUSCH) In Rel.15 / 16 NR, when the transmission configuration (txConfig) is NCB (PUSCH transmission is based on NCB), the size (number of bits) of the SRI field in DCI format 0_1 / 0_2 is represented by Equation 1 below. (Equation 1) ceil(log2(Σ SRS min{Lmax,NSRS} C(N SRS ,k))) Here, C(N SRS ,k) is the number of combinations of choosing k from N, also called binomial coefficients. Also, min(X,Y) is a function that returns the minimum value of X and Y. Also, ceil(x) is the ceiling function of x.
[0056] Here, N SRS is set by the list of SRS resource sets (srs-ResourceSetToAddModList) and is the number of SRS resources in the SRS resource set associated with the use of the non-codebook. If the UE supports the operation using the upper layer parameter maxMIMO-Layers indicating the maximum number of Multi Input Multi Output (MIMO) layers and the upper layer parameter maxMIMO-Layers is set, L max is given by that parameter. Otherwise, L max is given by the maximum number of layers for PUSCH supported by the UE.
[0057] For NCB-based PUSCH transmission, the association between the index indicated by the SRI field (the bit field mapped to the index / SRI field index / SRI index), and one or more SRIs (SRS resource IDs) is shown in Figure 1 (when L max = 1) / Figure 2 (when L max (If =2) / Figure 3 (L max (If =3) / Figure 4 (L max (If = 4)
[0058] (Transmission with more than 4 antenna ports) Rel.15 / 16 NR supports uplink (UL) Multi-Input Multi-Output (MIMO) transmission up to 4 layers. For future wireless communication systems, support for UL transmission with more than 4 layers is being considered to achieve higher spectral efficiency. For example, for Rel.18 NR, up to 6 ranks of transmission using 6 antenna ports, and up to 6 or 8 ranks of transmission using 8 antenna ports are being considered.
[0059] Figures 5A and 5B show examples of antenna layouts for an 8-antenna port. Figure 5A shows an example where the 8 antennas are arranged in one dimension (1D), and Figure 5B shows an example where the 8 antennas are arranged in two dimensions (2D). Figure 5A corresponds to an antenna configuration with four cross-polarized antennas arranged horizontally. Figure 5B corresponds to an antenna configuration with two cross-polarized antennas arranged horizontally and two vertically.
[0060] Note that the numbers shown in the diagram may indicate the numbers of the antenna ports corresponding to the antennas.
[0061] Note that the antenna layout is not limited to these. For example, the number of panels on which the antennas are placed, the orientation of the panels, the coherence of each panel / antenna (fully coherent, partially coherent, noncoherent, etc.), the antenna arrangement in a specific direction (horizontal, vertical, etc.), and the polarization antenna configuration (single polarization, cross polarization, number of polarization planes, etc.) may differ from the examples in Figures 5A and 5B.
[0062] Furthermore, while Rel.15 / 16 NR supported the transmission of one codeword (Codeword(CW)) per pusher, for Rel.18 NR, it is being considered that UEs will transmit more than one CW from a single pusher. For example, support for two CW transmissions for ranks 5-8 and two CW transmissions for ranks 2-8 are being considered.
[0063] Furthermore, while it is assumed that only one beam / panel is used for UL transmission at any given time in UEs of Rel.15 and Rel.16, in Rel.17 and later, simultaneous UL transmission of multiple beams / panels (e.g., PUSCH transmission) is being considered for one or more TRPs to improve UL throughput and reliability. Note that simultaneous PUSCH transmission of multiple beams / panels may correspond to PUSCH transmission with more than 4 layers, or to PUSCH transmission with 4 or fewer layers.
[0064] Furthermore, precoding matrices for UL transmissions using more than four antenna ports are being considered. For example, a codebook for 8-port transmissions (which may also be called an 8-transmission UL codebook (8 TX UL codebook)) is being considered.
[0065] (Settings / capabilities for transmission using 8 antenna ports) For an 8-transmit UL codebook, one or more UE coherent assumptions (UE coherent capabilities) and one or more codebook subset settings may be applied.
[0066] For the 8 ports, existing RRC parameters (or UE capabilities) such as "pusch-TransCoherence" and "codebookSubset" may be used. For example, for the 8 ports, the UE may determine the TPMI index for the 8 Transmit UL codebook based on nonCoherent, partialCoherent, fullCoherent, partialAndNonCoherent, fullyAndPartialAndNonCoherent, etc.
[0067] For the 8 ports, new RRC parameters (or UE capabilities) may be used. For example, the UE may report capability information to the network (e.g., base stations) indicating that it supports full / partial / noncoherent transmissions for a certain number of ports or less, or it may set RRC parameters indicating that it uses a subset of the full / partial / noncoherent codebook for transmissions for a certain number of ports or less.
[0068] Furthermore, information indicating which of the eight ports are coherent (or which ports will be used as coherent) may be reported by the UE or configured on the UE.
[0069] Furthermore, for the 8 ports, a UE that supports partial coherence (has partial coherence capability) may transmit information (included in capability information) about which antenna port combinations are coherent. This information may be called coherence information, coherence port information, etc.
[0070] The coherent port information may be a bitmap the size of the number of ports, and for example, a bit that is '1' (or '0') may mean that the ports are coherent with each other.
[0071] Coherent port information may also be information about a coherent group, where a coherent group may contain X coherent ports (where X is an integer greater than or equal to 1). Information about a coherent group may indicate that a coherent group contains X ports, or it may indicate the port number (port index) of each of the X coherent ports contained in a coherent group.
[0072] The UE may report UE capability information regarding one or more coherent groups to the network.
[0073] Figures 6A-6C show an example antenna layout for an 8-antenna port to illustrate coherence information. Figure 6A is similar to Figure 5A, but shows coherent group 1 consisting of antennas numbered 0, 1, 4, and 5 that are coherent with each other, and coherent group 2 consisting of antennas numbered 2, 3, 6, and 7 that are coherent with each other. The antennas in coherent group 1 and the antennas in coherent group 2 are not coherent with each other.
[0074] For example, with respect to Figure 6A, the UE may send capability information indicating that it supports full coherence for 4 or fewer ports and partial coherence for 5 or more ports.
[0075] With respect to Figure 6A, the UE may transmit at least one of the bitmaps “11001100” representing coherent group 1 and “11001100” representing coherent group 2 as coherent port information.
[0076] With respect to Figure 6A, the UE may report as coherent port information a value of 4, which is the number of ports included in the first coherent group (or that port numbers 0, 1, 4, and 5 are included in a coherent group), or it may report a value of 4, which is the number of ports included in the second coherent group (or that port numbers 2, 3, 6, and 7 are included in another coherent group).
[0077] Furthermore, one coherent group may be further divided into multiple coherent groups. Such classification of coherent groups is expected to enable flexible control.
[0078] Figure 6B shows coherent group 1, consisting of mutually coherent antennas numbered 0, 1, 4, and 5; coherent group 2, consisting of mutually coherent antennas numbered 2 and 6; and coherent group 3, consisting of mutually coherent antennas numbered 3 and 7.
[0079] Figure 6C shows coherent group 1, consisting of mutually coherent antennas numbered 0 and 4; coherent group 2, consisting of mutually coherent antennas numbered 1 and 5; coherent group 3, consisting of mutually coherent antennas numbered 2 and 6; and coherent group 4, consisting of mutually coherent antennas numbered 3 and 7.
[0080] In this disclosure, "having the capability of a coherent group" may be interpreted as "having the capability to support a coherent group," "having the capability to utilize a coherent group," etc.
[0081] The above-mentioned 8-transmit UL codebook for PUSCH may be used if at least one of the following conditions is met: If the transform precoder for PUSCH is disabled for UE, If the RRC configures more than 4 ports for PUSCH / SRS (for CB-based PUSCH) for the UE, If more than 4 ports are configured / activated / specified for PUSCH / SRS (for CB-based PUSCH) to the UE by RRC / MAC CE / DCI.
[0082] The number of ports in the precoding matrix used may be set quasi-statically by RRC. Furthermore, fallback (or switching) from using a precoding matrix with more than 4 ports to using one with 4 or fewer ports may be performed dynamically by MAC CE / DCI.
[0083] Furthermore, the UE may use (reference) a common 8-transmit UL codebook regardless of the antenna layout (antenna configuration). Alternatively, the UE may use (reference) a different 8-transmit UL codebook for each antenna layout (antenna configuration).
[0084] The UE may report UE capability information regarding the antenna layout. The base station may, for example, transmit to the UE information specifying / identifying / configuring the 8 Transmit UL codebook to be used by the UE, based on the said UE capability information. The UE may determine which 8 Transmit UL codebook to use based on the reported UE capability information and the received information specifying / identifying / configuring the 8 Transmit UL codebook.
[0085] In this disclosure, coherent port information, UE capability information relating to antenna layout, etc., may be referred to as antenna capability information.
[0086] (Analysis of the problem) By the way, NCB PUSCH transmission (L) for 8-port transmission up to 8 layers max Regarding =8), N for non-code books SRSIn the case where 8 1-port SRS resources are configured, according to Equation 1 above, the size of the SRI field included in the DCI format is ceil(log2(C(8,1)+…+C(8,8)))=8 bits.
[0087] However, constantly and flexibly directing eight SRS resources results in communication overhead due to the size of the SRI field for NCB PUSCH (e.g., the number of SRS resources). It is preferable to be able to appropriately adjust (control) the size of the DCI; otherwise, the increase in communication throughput may be suppressed.
[0088] In relation to the size of the SRI field mentioned above, we will consider the number of SRS resources. For example, Figure 7 shows an example of mapping SRS resources represented by SRI.
[0089] In Figure 7, eight SRS resources are shown by the DCI (DCI for scheduling PUSCH) in an NCB PUSCH transmission using eight ports. For example, the eight SRS resources are identified by the SRIs (SRS#0-#7) included in the DCI.
[0090] Thus, to enable NCB PUSCH transmission using 8 ports, the UE must transmit eight 1-port SRS resources for the non-codebook. These multiple SRS resources can be a source of communication overhead.
[0091] Therefore, the inventors devised a method for properly performing UL transmission using more than four antenna ports.
[0092] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.
[0093] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".
[0094] In this disclosure, terms such as activate, deactivate, indicate, select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operable may be interpreted interchangeably.
[0095] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Element (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.
[0096] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.
[0097] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).
[0098] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).
[0099] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, and subset may be interpreted interchangeably.
[0100] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, 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, transmit, port, antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relationship group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) groups, PUCCH resource groups, resources (e.g., reference signal resources, SRS resources), resource sets (e.g., reference signal resource sets), CORESET pools, 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 assumptions, etc., may be interpreted interchangeably.
[0101] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information" may be interpreted as mutually exclusive as "a set of spatial relationship information," "one or more spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive.
[0102] In the following embodiments, "multiple" and "two" may be interchangeable.
[0103] The number of layers for PUSCH transmission in the following embodiments may be greater than or equal to 4. For example, PUSCH transmission in this disclosure may be performed with a number of layers of 4 or less (e.g., 2). Furthermore, the maximum number of layers is not limited to 4 or more, but may be less than 4.
[0104] Furthermore, the PUSCH transmission in the following embodiments may or may not be based on the assumption of using multiple panels (it may be applied regardless of the number of panels).
[0105] In the following embodiments, the DCI may be a DCI format for scheduling PUSCH (for example, DCI format 0_1 / 0_2).
[0106] In this disclosure, SRS and SRS resources may be interpreted interchangeably. Also, in this disclosure, an SRS (or SRS resource) whose intended use is a non-code book may be interpreted interchangeably with an SRS (or SRS resource) associated with a set of SRS resources whose intended use is a non-code book.
[0107] (Wireless communication method) <First Embodiment> The first embodiment relates to SRS resources and the number of ports.
[0108] The UE may configure an SRS for a non-code book with more than one port. That is, for each SRS resource in a non-code book, the number of SRS ports may be greater than one.
[0109] If a UE has one or more SRS resources configured with one or more ports, the port index / antenna index (port number / antenna number) of each SRS resource may be mapped as shown in the table in Figure 8, for example.
[0110] In this disclosure, a table may be interpreted as information (or correspondences or lists) relating SRS resources to the number of SRS ports.
[0111] Figure 8 shows an example of the association between an SRS resource ID and the number of SRS ports according to the first embodiment. In the table shown in Figure 8, the SRS resource ID, the number of SRS ports, and the port index are associated with each other. As shown in Figure 8, each port index may be mapped in ascending order of the SRS resource ID (SRI).
[0112] For example, if the SRIs included in DCI represent SRS resources #1 and #3 in Figure 8, the number of ports associated with each resource is 2 and 2, for a total of 4 ports (4 layers). In other words, in this case, the scheduled PUSCH corresponds to 4 layers.
[0113] Note that in Figure 8, the number of ports associated with each SRS resource is the same at 2, but the number of ports for different SRS resources may be different. Also, although the table in Figure 8 shows a port index corresponding to the number of ports for each SRS resource, the port index does not have to be associated with the SRS resource and the number of ports. In other words, the table shown in Figure 8 only needs to associate (set) the SRS resource and the number of ports.
[0114] The table shown in Figure 8, namely the correspondence between SRS resources (SRS resource IDs) and the corresponding number of ports / port index / antenna index, may be configured by RRC signaling.
[0115] Figure 9 shows an example of the mapping of SRS resources indicated by the SRI according to the first embodiment. In this example, the UE understands the correspondence shown in Figure 8. The UE receives a DCI containing an SRI field indicating four SRS resources (SRS#0-#3) and performs an NCB PUSCH transmission using eight ports (ports #0-#7) based on the DCI.
[0116] Thus, in the first embodiment, in order to realize multi-layer push transmission in non-code book MIMO, one or more SRS resources may be specified by SRIs included in the DCI. According to the first embodiment, the number of SRS resources whose purpose is non-code book can be reduced to, for example, four. In addition, the size of the SRI field corresponding to these SRS resources can be reduced to, for example, four bits. Therefore, the communication overhead of the SRI field (SRS resource) can be reduced.
[0117] [Embodiment 1.1] Eight one-port SRS resources for the non-code book may be configured by RRC signaling. These SRS resources may be grouped, for example, as follows:
[0118] Figure 10 shows an example of mapping of SRS resources indicated by SRI according to the first embodiment (Embodiment 1.1). In Figure 10, eight SRS resources (SRS#0-#7) are mapped in ascending order of SRS resource ID (SRI). The eight SRS resources may be grouped, for example, in pairs of consecutive SRS resources.
[0119] In Figure 10, SRS resources #0 and #1 (SRS#0 and #1) are set to Group #0, SRS resources #2 and #3 (SRS#2 and #3) are set to Group #1, SRS resources #4 and #5 (SRS#4 and #5) are set to Group #2, and SRS resources #6 and #7 (SRS#6 and #7) are set to Group #3.
[0120] In this case, the SRIs included in the DCI can specify the eight SRS resources, which are grouped into four groups, as group#0-#3. That is, the DCI may include information indicating a group number (group index) that represents a predetermined group formed by grouping multiple SRS resources. Also, as shown in Figure 10, the SRS resources grouped into four groups (Group#0-#3) may be mapped in ascending order of SRS resource ID (SRI).
[0121] In this way, by specifying the SRS resource using a group number (group ID), the size of the SRI field can be reduced to 4 bits, thereby reducing communication overhead. Note that the group in Embodiment 1.1 may correspond to the coherent group described above.
[0122] According to the first embodiment described above, the communication overhead of the SRI field (SRS resource) can be reduced.
[0123] <Second Embodiment> The second embodiment relates to an SRI instruction table.
[0124] In the first embodiment described above, to enable NCB PUSCH transmission using 8 ports, up to 4 2-port SRS resources are required for non-codebooks, for example (i.e., N SRS =4). In this case, SRI is as shown in Figures 1-4 (L maxThe SRI fields may be mapped (or associated with) the SRI fields according to (1-4). Alternatively, the SRIs may be mapped based on rules different from those described in Figures 1-4 above.
[0125] For example, in Figure 4, L max The case of =4 is shown as an example, but Figure 4 is L max This may also apply to the case where =8. In this case, some interpretations of Figure 4 may differ. For example, UE is L max In the case of =8, if the SRI field included in DCI shows "0", it may be indicated that SRI=0 and the number of layers is 2. Also, UE is L max In the case where =8, if the SRI field included in DCI indicates "10", it may indicate that SRI=0,1,2 and the number of layers is 6 (Port#0-#5).
[0126] [Specify 1-port PUSCH] In the example in Figure 8, the number of ports associated with all four SRS resources is 2, and it is not possible to represent a PUSCH using 1 port. It is preferable to be able to specify a 1-port PUSCH using SRI. Below, several embodiments for realizing the specification of a 1-port PUSCH are described.
[0127] [[Embodiment 2.1]] Embodiment 2.1 allows the maximum number of SRS resources for a non-code book to be greater than 4. In other words, the UE may configure more than 4 SRS resources for a non-code book. Of these more than 4 SRS resources, at least one SRS resource may have a port count of 1.
[0128] Figure 11 shows an example of the association between SRS resource IDs and the number of SRS ports according to Embodiment 2.1. In the table shown in Figure 11, the SRS resource ID, the number of SRS ports, and the port index are associated with each other. As shown in Figure 11, each port index may be mapped in ascending order of SRS resource ID (SRI).
[0129] Figure 11 shows the case where the maximum number of SRS resources for a non-code book is greater than 4 (N SRS >4) will be explained. In Figure 11, N SRS Let's take the case of =5 (SRS#0-#4) as an example. Note that the number of SRS resources and the number of ports associated with each resource may be set in a different table than shown in Figure 11.
[0130] In Figure 11, for example, the number of ports for SRS resource #0 is set to 1 (Port #0), the number of ports for SRS resource #1 is set to 1 (Port #1), the number of ports for SRS resource #2 is set to 2 (Port #2, #3), the number of ports for SRS resource #3 is set to 2 (Port #4, #5), and the number of ports for SRS resource #4 is set to 2 (Port #6, #7).
[0131] For example, if the SRI included in a DCI represents all resources from SRS#0 to #4, the corresponding PUSCH transmission (scheduled by that DCI) means an NCB PUSCH transmission using 8 ports (1+1+2+2+2 ports). Also, if the SRI represents SRS#0 or SRS#1, the corresponding PUSCH transmission means an NCB PUSCH transmission using 1 port.
[0132] In this way, based on SRI, the predetermined number of SRS resources and ports can be flexibly (dynamically) specified.
[0133] [[Embodiment 2.2]] In Embodiment 2.2, a specific value in the SRI field may be used to specify one or more antenna ports (in other words, the restriction to use may apply). This specific value may be set by upper-layer signaling or may be predefined in a standard. For example, if the value of the SRI field included in the DCI is a specific value (e.g., 0 or 1), the UE may use only the port with the lowest index among the SRIs specified by that SRI field (as shown in the correspondence) for the corresponding PUSCH transmission.
[0134] More specifically, let's explain the case where SRS#0 is associated with Port#0 and #1, using the correspondence shown in Figure 4 as an example. We will assume that the specific value mentioned above is 0. If the SRI field of the DCI notified to the UE indicates 0, only Port#0 will be used for PUSCH transmission.
[0135] Note that the above specific values may also be values in SRI fields (which may be called reserved values) for which the corresponding SRI is not shown in the correspondence relationship (for example, the corresponding content is "Reserved"). For example, the above specific values may be the values corresponding to "Reserved" shown in Figures 1-4 above (for example, N in Figure 4). SRS "3" in =2, N SRS "7" in =3, N SRS This could be "15" in =4, for example. The UE may apply a specific port of a specific SRS resource to a PUSCH transmission when a reserved value is notified. For example, when a reserved value is notified, the UE may apply a PUSCH transmission to the port of the lowest index associated with the lowest index SRS resource among the SRS resources whose use is a non-codebook. The specific SRS resources, specific ports, etc. mentioned above may be set by higher-layer signaling.
[0136] [[Embodiment 2.3]] In Embodiment 2.3, the maximum number of SRS resources used for non-code books is 4, but at least one of these SRS resources may have a port count of 1.
[0137] Figure 12 shows an example of the association between SRS resource IDs and the number of SRS ports according to Embodiment 2.2. In the table shown in Figure 12, the SRS resource ID, the number of SRS ports, and the port index are associated with each other, similar to Figure 11 described above. Each port index may be mapped in ascending order of SRS resource ID (SRI).
[0138] Figure 12 shows the case where the maximum number of SRS resources for a non-code book is 4 (N SRS Let's explain =4(SRS#0-#3). In Figure 12, for example, the number of ports for SRS resource #0 is set to 1 (Port#0), the number of ports for SRS resource #1 is set to 3 (Port#1,#2,#3), the number of ports for SRS resource #2 is set to 2 (Port#4,#5), and the number of ports for SRS resource #3 is set to 2 (Port#6,#7).
[0139] For example, if the SRI included in a DCI represents all resources from SRS#0 to #3, the corresponding PUSCH transmission (scheduled by that DCI) means an NCB PUSCH transmission using 8 ports (ports 1+3+2+2). Also, if the SRI represents SRS#0, the corresponding PUSCH transmission means an NCB PUSCH transmission using port 1.
[0140] Thus, according to Embodiment 2.3, scheduling of NCB PUSCH transmissions using one port can be easily performed.
[0141] According to the second embodiment described above, it is possible to schedule PUSCH transmissions using not only two ports but also one port, and to appropriately control PUSCH transmissions according to the number of ports.
[0142] <Supplement> In this disclosure, the number "8" may be interpreted as any number greater than 4 (for example, 6, 10, 12, 16, ...) or any number less than or equal to 4 (for example, 1, 2, 3, 4). Furthermore, if such an interpretation is made, any number that presupposes 8 in the above embodiments may be interpreted as appropriate. Those skilled in the art will naturally understand that such interpretations are described in this disclosure.
[0143] At least one of the embodiments described above may apply only to a UE that has reported or supports a particular UE capability.
[0144] The specific UE capability may represent at least one of the following: • To support specific processing / operation / control / information for at least one of the above embodiments, • Supports push transmission using more than 4 antenna ports. Regarding NCB (NCB PUSCH transmission), support for more than 1 SRS ports. • Support for grouping SRS resources.
[0145] Furthermore, the above-mentioned specific UE capabilities may be capabilities that apply across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities per subcarrier spacing (SCS), or capabilities per feature set (FS) or feature set per component-carrier (FSPC).
[0146] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).
[0147] Furthermore, at least one of the embodiments described above may be applied when the UE is configured with specific information related to the embodiments described above by upper-layer signaling. For example, such specific information may be information indicating the activation of push transmits using more than four antenna ports (or more than four layers) / one or more NCB push transmits, or arbitrary RRC parameters for a particular release (e.g., Rel. 18).
[0148] If the UE does not support at least one of the above-mentioned specific UE capabilities or does not have the above-mentioned specific information configured, the behavior of, for example, Rel.15 / 16 may be applied.
[0149] (Note) The following invention is added with respect to one embodiment of this disclosure. [Note 1] A receiver unit that receives Downlink Control Information (DCI) which schedules the transmission of a Physical Uplink Shared Channel (PUSCH) in a noncode book, including a Sounding Reference Signal (SRS) Resource Indicator (SRI) field, A terminal having a control unit that controls the PUSCH transmission based on an SRS resource with a number of ports greater than 1 specified by the SRI field. [Note 2] The terminal as described in Appendix 1, wherein the SRI field specifies more than 4 SRS resources, and at least one of the more than 4 SRS resources has 1 port. [Note 3] The terminal as described in Appendix 1 or Appendix 2, wherein the control unit applies only the port with the lowest index among the SRIs specified by the SRI field to the corresponding PUSCH transmission when the value of the SRI field is a specific value. [Note 4] The terminal described in any of Appendix 1 to Appendix 3, wherein the SRI field specifies four SRS resources, and at least one of the four SRS resources has a port count of 1.
[0150] (Wireless communication system) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any or a combination thereof of the wireless communication methods according to the above embodiments of this disclosure.
[0151] Figure 13 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).
[0152] Furthermore, the wireless communication system 1 may 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)), and so on.
[0153] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the 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.
[0154] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity where both MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).
[0155] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement and number of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.
[0156] 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 (CC) and Dual Connectivity (DC).
[0157] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a 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 above 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 fall in a frequency band higher than FR2.
[0158] Furthermore, the user terminal 20 may communicate using at least one of the following methods at each CC: Time Division Duplex (TDD) and Frequency Division Duplex (FDD).
[0159] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, if NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.
[0160] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.
[0161] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.
[0162] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.
[0163] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. 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), etc., may be used in at least one of the downlink (DL) and uplink (UL).
[0164] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.
[0165] In the wireless communication system 1, a Physical Downlink Shared Channel (PDSCH), a Broadcast Channel (PBCH), or a Physical Downlink Control Channel (PDCCH) may be used as the downlink channel, shared by each user terminal 20.
[0166] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.
[0167] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.
[0168] Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH.
[0169] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.
[0170] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration.
[0171] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.
[0172] PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.
[0173] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.
[0174] 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 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.
[0175] 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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. SS, SSB, etc., may also be called reference signals.
[0176] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).
[0177] (base station) Figure 14 shows an example of the configuration of a base station according to one 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 one or more of the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.
[0178] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.
[0179] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the art relating to this disclosure.
[0180] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may also control transmission and reception, measurement, etc., using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transceiver unit 120. The control unit 110 may also perform call processing of communication channels (setting, releasing, etc.), status management of the base station 10, management of radio resources, etc.
[0181] The transmitting / receiving 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 transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.
[0182] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.
[0183] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.
[0184] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.
[0185] The transmitting / receiving unit 120 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.
[0186] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), etc., to generate a bit sequence to be transmitted.
[0187] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.
[0188] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.
[0189] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 130.
[0190] The transmitting / receiving unit 120 (receiving processing unit 1212) may apply reception processing to the acquired baseband signal, such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data, etc.
[0191] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to 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 also measure received power (e.g., Reference Signal Received Power (RSRP)), reception 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.
[0192] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes providing 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.
[0193] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.
[0194] The transmitting / receiving unit 120 may also include a Sounding Reference Signal (SRS) Resource Indicator (SRI) field and transmit Downlink Control Information (DCI) that schedules the transmission of a non-code book uplink shared channel (Physical Uplink Shared Channel (PUSCH)).
[0195] The control unit 110 may control the value of the SRI field to specify an SRS resource with a port number greater than 1.
[0196] (User terminal) Figure 15 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.
[0197] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.
[0198] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.
[0199] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 220 and the transmitting / receiving antenna 230. The control unit 210 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 220.
[0200] The transmitting / receiving 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 transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.
[0201] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.
[0202] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.
[0203] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.
[0204] The transmitting / receiving unit 220 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.
[0205] The transmitting / receiving 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 and control information acquired from the control unit 210, etc., to generate a bit sequence to be transmitted.
[0206] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.
[0207] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.
[0208] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.
[0209] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 230.
[0210] The transmitting / receiving unit 220 (receiving processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.
[0211] The transmitting / receiving unit 220 (measuring unit 223) may perform measurements related to the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measuring unit 223 may also 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.
[0212] In this disclosure, the transmitting and receiving units of the user terminal 20 may consist of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.
[0213] The transmitting / receiving unit 220 may also include a Sounding Reference Signal (SRS) Resource Indicator (SRI) field and receive Downlink Control Information (DCI) that schedules the transmission of a Physical Uplink Shared Channel (PUSCH) in the non-codebook.
[0214] The control unit 210 may control the PUSCH transmission based on the number of SRS resources with a port number greater than 1 specified by the SRI field. Alternatively, if the value of the SRI field is a specific value, the control unit 210 may apply only the port with the smallest index among the SRIs specified by the SRI field to the corresponding PUSCH transmission.
[0215] (Hardware configuration) The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.
[0216] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.
[0217] For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 16 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.
[0218] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.
[0219] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.
[0220] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or to control at least one of the reading and writing of data in the memory 1002 and storage 1003.
[0221] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.
[0222] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. 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 other functional blocks may be implemented similarly.
[0223] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. Memory 1002 may also be called a register, cache, or main memory. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of this disclosure.
[0224] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital multipurpose disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be called an auxiliary storage device.
[0225] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting / receiving unit 120 (220), transmitting / receiving antenna 130 (230), etc., may be implemented by the communication device 1004. The transmitting / receiving unit 120 (220) may be implemented with physically or logically separated implementations of a transmitting unit 120a (220a) and a receiving unit 120b (220b).
[0226] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).
[0227] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.
[0228] 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.
[0229] (modified version) In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.
[0230] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist 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.
[0231] Here, the neuralelogy may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neuralelogy may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, or specific windowing processes performed by the transceiver in the time domain.
[0232] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology.
[0233] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (PUSCH) mapping type B.
[0234] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.
[0235] For example, one subframe may be called TTI, multiple consecutive subframes may be called TTI, or one slot or one mini-slot may be called TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing TTI may be called a slot, mini-slot, etc., instead of a subframe.
[0236] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.
[0237] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.
[0238] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.
[0239] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.
[0240] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.
[0241] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.
[0242] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. Each TTI, subframe, etc., may consist of one or more resource blocks.
[0243] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.
[0244] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.
[0245] A Bandwidth Part (BWP) (also called a partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.
[0246] A BWP may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured within a single carrier for a UE.
[0247] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".
[0248] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.
[0249] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values from a predetermined value, or corresponding other information. For example, wireless resources may be indicated by a predetermined index.
[0250] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.
[0251] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0252] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.
[0253] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.
[0254] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof).
[0255] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Element (CE).
[0256] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).
[0257] The determination may be made based on a value represented by 1 bit (either 0 or 1), a boolean value represented by true or false, or a numerical comparison (e.g., comparison with a predetermined value).
[0258] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether called software, firmware, middleware, microcode, a hardware description language, or by some other name.
[0259] Also, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, when software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and wireless technologies (such as infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of the transmission medium.
[0260] The terms "system" and "network" used in this disclosure may be used interchangeably. "Network" may mean the devices (e.g., base stations) included in the network.
[0261] 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," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," and "panel" may be used interchangeably.
[0262] In this disclosure, terms such as "Base Station (BS)", "wireless 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", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.
[0263] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of the base station can be divided into several smaller areas, each of which may also be provided with communication services 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 at least one of the base station and / or base station subsystems that provide communication services in that coverage.
[0264] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.
[0265] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.
[0266] A mobile station may also be called 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 appropriate term.
[0267] 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. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.
[0268] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.
[0269] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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.
[0270] Figure 17 shows an example of a vehicle according to one 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, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic 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.
[0271] The drive unit 41 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. 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 the user.
[0272] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).
[0273] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression signal of accelerator pedal 43 acquired by accelerator pedal sensor 55, brake pedal depression signal of brake pedal 44 acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals for detecting obstacles, vehicles, pedestrians, etc., acquired by object detection sensor 58.
[0274] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, displays, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.
[0275] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).
[0276] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, 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 Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.
[0277] 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 sends and receives data (information) via the communication port 63 to 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, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.
[0278] 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 via wireless communication with the external device. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the above-described base station 10, user terminal 20, etc. Further, the communication module 60 may be, for example, at least one of the above-described base station 10 and user terminal 20 (it may function as at least one of the base station 10 and user terminal 20).
[0279] The communication module 60 may transmit at least one of the signals from the various sensors 50 - 58 described above input to the electronic control unit 49, the information obtained based on the signals, and the information based on the input from the external (user) obtained via the information service unit 59, to the 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 an input unit that receives an input. For example, the PUSCH transmitted by the communication module 60 may include the information based on the above input.
[0280] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from the external device and displays it on the information service unit 59 provided in the vehicle. The information service unit 59 may be referred to as an output unit that outputs information (for example, outputs information to devices such as a display and a speaker based on the PDSCH received by the communication module 60 (or the data / information decoded from the PDSCH)).
[0281] Further, the communication module 60 stores the various information received from the external device in the 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, axle 48, various sensors 50 - 58, etc. provided in the vehicle 40.
[0282] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this 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), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel and downlink channel may be interpreted as sidelink channel.
[0283] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.
[0284] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes with base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.
[0285] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to that specific order.
[0286] Each aspect / embodiment described in this disclosure includes 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 (where x is, for example, an integer or decimal)), 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may apply to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that are extended, modified, created, or defined based on these. It may also apply to combinations of multiple systems (e.g., a combination of LTE or LTE-A and 5G).
[0287] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."
[0288] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.
[0289] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to include judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in tables, databases, or other data structures), ascertaining, etc.
[0290] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).
[0291] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.
[0292] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."
[0293] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.
[0294] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”
[0295] In this disclosure, when two elements are connected, they can be considered to be “connected” or “coupled” to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).
[0296] In this 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 "combine" may be interpreted similarly to "different."
[0297] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.
[0298] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.
[0299] In this disclosure, terms such as "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. Furthermore, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").
[0300] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.
[0301] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.
Claims
1. A receiving unit that receives Downlink Control Information (DCI) which schedules the transmission of a noncodebook uplink shared channel (Physical Uplink Shared Channel (PUCH)), including a Sounding Reference Signal (SRS) Resource Indicator (SRI) field, The system includes a control unit that controls the PUSCH transmission based on the SRS resource specified by the value of the SRI field, Each of the aforementioned SRS resources has multiple SRS ports associated with it. The control unit, when the value of the SRI field is a specific value, applies the SRS port having the smallest index among a plurality of SRS ports associated with the SRS resource specified by the specific value to the PUSCH transmission.
2. The terminal according to claim 1, wherein the number of SRS resources that can be specified by the value of the SRI field is greater than 4.
3. The steps include receiving Downlink Control Information (DCI) which includes a Sounding Reference Signal (SRS) Resource Indicator (SRI) field and schedules a Physical Uplink Shared Channel (PUCH) transmission in the noncodebook, The process includes the step of controlling the PUSCH transmission based on the SRS resource specified by the value of the SRI field, Each of the aforementioned SRS resources has multiple SRS ports associated with it. A wireless communication method for a terminal, wherein, in the step of controlling the PUSCH transmission, if the value of the SRI field is a specific value, the SRS port having the smallest index among a plurality of SRS ports associated with the SRS resource specified by the specific value is applied to the PUSCH transmission.
4. A system comprising the terminal described in Claim 1 and a base station, The aforementioned base station is A transmitting unit that transmits the DCI, A system comprising a control unit for controlling the value of the SRI field.