Terminal, wireless communication method, and base station
By integrating AI indicators and adjusting processing times for PDSCH and PUSCH, the method addresses increased computational complexity from AI processing, enhancing communication performance and quality in wireless systems.
Patent Information
- Application Number
- PCT/JP2024/004371
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-02-08
- Publication Date
- 2025-08-14
AI Technical Summary
Existing wireless communication technologies face challenges in managing increased computational complexity due to AI processing, particularly in user equipment (UE), leading to unaccounted processing time that hinders improvements in communication throughput and quality.
A terminal and wireless communication method that incorporates AI indicators and adjusted processing times for PDSCH and PUSCH, including extended or new tables and formulas to account for AI conversion functions, ensuring appropriate UE processing times.
Enhances communication performance by addressing nonlinearity issues in power amplifiers and optimizing UE processing times, thereby improving communication throughput and quality.
Smart Images

Figure JP2024004371_14082025_PF_FP_ABST
Abstract
Description
Terminal, wireless communication method and base station
[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.
[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).
[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later, etc.) are also being considered.
[0004] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010
[0005] Regarding future wireless communication technologies, the use of artificial intelligence (AI) technologies such as machine learning (ML) for network / device control, management, etc. is being considered. For example, AI technologies that convert signal waveforms for communication (which may also be called AI transformation) are being considered for the purpose of compensating for nonlinear distortion of signal waveforms.
[0006] AI conversion is expected to improve spectral efficiency and system performance, but it is thought that AI conversion increases the computational complexity compared to existing NR signal waveform generation methods.
[0007] However, there has been no progress in studying how to perform settings / controls that can take into account the additional processing time in a terminal (user terminal, User Equipment (UE)) due to such increased computational complexity. Unless these are clearly defined, it may not be possible to perform suitable waveform conversion, which may hinder improvements in communication throughput / communication quality.
[0008] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately take into account the increase in UE processing time due to AI processing such as AI conversion.
[0009] A terminal according to one aspect of the present disclosure has a receiving unit that receives first information indicating a waveform conversion-related function and second information regarding a time for a downlink channel associated with the first information, and a control unit that determines the time for the downlink channel based on the first information and the second information.
[0010] According to one aspect of the present disclosure, the increase in UE processing time due to AI processing such as AI conversion can be appropriately taken into account.
[0011] 1A is a diagram showing an example of PDSCH decoding time for PDSCH processing capability 1 specified in the existing NR standard. FIG. 1B is a diagram showing an example of PDSCH decoding time for PDSCH processing capability 2 specified in the existing NR standard. FIG. 2 is a diagram showing an example of PDSCH decoding time for PDSCH processing capability 1 specified in the existing NR standard. pdschFIG. 3A is a diagram showing an example of a PUSCH preparation time for PUSCH processing capability 1 specified in the existing NR standard. FIG. 3B is a diagram showing an example of a PUSCH preparation time for PUSCH processing capability 2 specified in the existing NR standard. FIG. 4 is a diagram showing a portion of RRC information elements related to PDSCH TDRA information in the existing 3GPP standard. FIG. 5 is a diagram showing a portion of RRC information elements related to PUSCH TDRA information in the existing 3GPP standard. FIG. 6 is a diagram showing a portion of RRC information elements related to HARQ-ACK timing information in the existing 3GPP standard. FIG. 7 is a diagram showing an example of input / output characteristics of a PA. FIG. 8 is a diagram showing an example of nonlinear distortion caused by the nonlinear characteristics of a PA. FIG. 9 is a diagram showing an example of compensation for nonlinear distortion caused by the nonlinear characteristics of a PA. FIG. 10 is a diagram showing an example of an extension table of PDSCH decoding times for PDSCH processing capability 1 in embodiment 2.1. FIG. 11 is a diagram showing an example of a table of PDSCH decoding times for PDSCH processing capability 1 in embodiment 2.2. 12 is a diagram showing an example of a table of PDSCH decoding times for PDSCH processing capability 3 in embodiment 2.3. pdschFIG. 14 is a diagram showing an example of an extension table of PUSCH preparation times for PUSCH timing capability 1 according to embodiment 4.1. FIG. 15 is a diagram showing an example of a table of PUSCH preparation times for PUSCH timing capability 1 according to embodiment 4.2. FIG. 16 is a diagram showing an example of a table of PUSCH preparation times for PUSCH timing capability 3 according to embodiment 4.3. FIG. 17 is a diagram showing part of RRC information elements related to TDRA information of the PDSCH according to embodiment 5.1. FIG. 18 is a diagram showing part of RRC information elements related to TDRA information of the PDSCH according to embodiment 5.2. FIG. 19 is a diagram showing part of RRC information elements related to TDRA information of the PDSCH according to embodiment 5.3. FIG. 20 is a diagram showing part of RRC information elements related to HARQ-ACK timing information according to embodiment 6.1. FIG. 21 is a diagram showing part of RRC information elements related to HARQ-ACK timing information according to embodiment 6.2. FIG. 22 is a diagram showing a portion of RRC information elements related to HARQ-ACK timing information in embodiment 6.3. FIG. 23 is a diagram showing a portion of RRC information elements related to TDRA information of a PUSCH in embodiment 7.1. FIG. 24 is a diagram showing a portion of RRC information elements related to TDRA information of a PUSCH in embodiment 7.2. FIG. 25 is a diagram showing a portion of RRC information elements related to TDRA information of a PUSCH in embodiment 7.3. FIG. 26 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 27 is a diagram showing an example of a configuration of a base station according to an embodiment. FIG. 28 is a diagram showing an example of a configuration of a user terminal according to an embodiment. FIG. 29 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 30 is a diagram showing an example of a vehicle according to an embodiment.
[0012] (Time-related factors for UE processing in NR) In NR, there are several time-related factors (parameters, constraints) for UE processing. These are outlined below.
[0013] <UE Physical Downlink Shared Channel (PDSCH) Processing Time> In NR, when a UE completes reception of a PDSCH, it takes time to process the PDSCH, so it is not possible to immediately transmit delivery confirmation information (retransmission control information, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.) corresponding to the PDSCH. In NR, the PDSCH processing time, which is the time required to process the received PDSCH, is specified.
[0014] The PDSCH processing time may be interchangeably read as UE PDSCH processing time, [UE] PDSCH processing procedure time, [UE] PDSCH decoding time, and the like.
[0015] In the existing standard, the UE determines whether the first uplink symbol of the PUCCH carrying HARQ-ACK information is the symbol L. 1 If it does not start earlier than , it must provide a valid HARQ-ACK message.
[0016] Here, the first uplink symbol is assigned HARQ-ACK timing K 1 and K offset (if configured) and the PUCCH resource utilized, and may include the effect / impact of the timing advance.
[0017] K 1 K may be a higher layer parameter related to the HARQ-ACK timing (HARQ-ACK timing information, described later). offset may be a scheduling offset based on a higher layer parameter for a cell-specific scheduling offset (cellSpecificKoffset).
[0018] The above-mentioned L 1is the time from the end of the last symbol of the PDSCH carrying the identified transport block (TB) to T proc,1 T is defined as the next uplink symbol after which the Cyclic Prefix (CP) starts. proc,1 corresponds to the PDSCH processing time described above and is calculated by Equation 1. (Equation 1) T proc,1 = (N 1 +d 1,1 +d 2 +d 3 )(2048+144)・κ2 -μ ・T C +T ext
[0019] Here, N 1 may be determined based on μ in Figure 1A (when the UE has / is configured to process PDSCH processing capability 1) and Figure 1B (when the UE has / is configured to process PDSCH processing capability 2). Figure 1A is a diagram showing an example of PDSCH decoding time for PDSCH processing capability 1 specified in the existing NR standard. Figure 1B is a diagram showing an example of PDSCH decoding time for PDSCH processing capability 2 specified in the existing NR standard.
[0020] 1A and 1B are Tables 5.3-1 and 5.3-2 of 3GPP TS 38.214 V18.1.0, respectively.
[0021] μ in Equation 1 is the maximum T proc,1 μ PDCCH , μ PDSCH , μ UL For example, μ PDCCH μ corresponds to the subcarrier spacing (SCS) of the PDCCH that schedules the PDSCH. PDSCH μ corresponds to the SCS of the scheduled PDSCH. UL corresponds to the subcarrier spacing of a certain uplink channel. Note that the SCS corresponding to μ is 2 μ ・It may be calculated at 15 [kHz].
[0022] Here, the certain uplink channel is the uplink channel on which HARQ-ACK is assumed to be transmitted, regardless of whether PDSCH reception provides a transport block of a HARQ process with disabled HARQ-ACK information, as indicated by HARQ-feedbackEnabling-disablingperHARQprocess (if set).
[0023] HARQ-feedbackEnabling-disablingperHARQprocess may be a higher layer parameter related to the setting indicating whether or not HARQ feedback is enabled in the HARQ process.
[0024] In Equation 1, κ is T S and T C κ is a constant that indicates the ratio between S / T C = 64, where T S denotes the basic time unit for LTE, and T C indicates the basic time for NR.
[0025] d in Equation 1 1,1 , d 2 may be a value determined based on the PDSCH processing capability, the PDSCH mapping type, the number of symbols of the scheduling PDCCH, the number of symbols of the PDSCH, etc.
[0026] d in Equation 1 2 may be a value determined based on the priority of PUCCH, PUSCH, etc., or may be 0.
[0027] d in Equation 1 3The value of d may be determined based on the higher layer parameter (processingType2Enabled) for enabling processing of PDSCH processing capability 2 for UE processing capability 2, the higher layer parameter (enhanced-dmrs-Type_r18) for the enhanced demodulation reference signal (DMRS) type [specified in Rel. 18], or may be 0 if neither of these parameters is set. Also, for UE processing capability 1 (excluding UE processing capability 2), 3 = 0.
[0028] It should be noted that the term "processing capability" may be interchangeably read as "timing capability."
[0029] T in Equation 1 ext T may be calculated according to a predetermined rule in the case of shared spectrum channel access operation in FR1, and may be 0 otherwise. ext may be, for example, the value applied to the first UL transmission scheduled by the scheduling DCI.
[0030] <UE PDSCH reception preparation time> In NR, in the case of cross-carrier scheduling with different SCSs for PDCCH and PDSCH (in other words, the OFDM SCS (μ PDCCH ) and the PDSCH scheduled to be received by the DCI is received on a carrier in another OFDM SCS (μ PDSCH ) in the PDSCH reception preparation period (N pdsch ) is stipulated.
[0031] μ PDCCH <μ PDSCHIf the first symbol in a scheduled PDSCH allocation (including DMRS) is at least N symbols from the end of the PDCCH that schedules the PDSCH, pdsch The UE is expected to receive the scheduled PDSCH no earlier than the first symbol of the slot for that PDSCH reception, which starts after the PDCCH symbol.
[0032] μ PDCCH >μ PDSCH If the first symbol in the scheduled PDSCH allocation (including DMRS) is N symbols from the end of the PDCCH that schedules the PDSCH, pdsch The UE is expected to receive the scheduled PDSCH if it starts no sooner after the PDCCH symbol.
[0033] Here, the first symbol in the scheduled PDSCH allocation (including DMRS) is at slot offset K of the scheduling DCI. 0 and Start and Length Indicator Value (SLIV). Note that these symbols (conditions / comparisons) do not take into account the effect of the reception timing difference between the scheduling cell and the scheduled cell.
[0034] FIG. 2 shows the N defined in the existing NR standard. pdsch FIG. 2 is a diagram showing an example of Table 5.5-1 of 3GPP TS 38.214 V18.1.0. As shown in this example, pdsch is μ PDCCH may depend on
[0035] <Physical Uplink Shared Channel (PUSCH) Preparation Time> In NR, when a UE receives a DCI format for scheduling a PUSCH, it takes time to prepare the data for the PUSCH, so the PUSCH cannot be transmitted immediately. In NR, a PUSCH preparation time, which is the time required to prepare the PUSCH, is specified.
[0036] Note that the PUSCH preparation time may be interchangeably read as UE PUSCH preparation time, [UE] PUSCH preparation procedure time, [UE] PUSCH processing time, and the like.
[0037] In existing standards, the UE is required to ensure that the first uplink symbol in the PUSCH allocation (including DMRS) for a TB is the symbol L 2 If the TB does not start earlier than , the UE shall transmit the TB. Otherwise, the UE may ignore the scheduling DCI.
[0038] Here, the first uplink symbol is at slot offset K indicated by the time domain resource allocation field of the scheduling DCI. 2 and K. offset (if configured), and the starting symbol S and length L of said PUSCH allocation, and may include the effect / impact of timing advance.
[0039] K 2 K may be a higher layer parameter related to the transmission slot (offset of) of the PUSCH. offset may be a scheduling offset based on a higher layer parameter for a cell-specific scheduling offset (cellSpecificKoffset).
[0040] The above-mentioned L 2 is the time T from the end of reception of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH.proc,2 T is defined as the next uplink symbol after which the CP starts. proc,2 corresponds to the PUSCH preparation time described above and is calculated by Equation 2. (Equation 2) T proc,2 = max ((N 2 +d 2,1 +d 2 )(2048+144)・κ2 -μ ・T C +T ext +T switch, d 2,2 )
[0041] Here, N 2 3A (when the UE has / is configured to process PUSCH processing capability 1) and FIG. 3B (when the UE has / is configured to process PUSCH processing capability 2). 3A is a diagram showing an example of a PUSCH preparation time for PUSCH processing capability 1 defined in the existing NR standard. 3B is a diagram showing an example of a PUSCH preparation time for PUSCH processing capability 2 defined in the existing NR standard.
[0042] 3A and 3B are Tables 6.4-1 and 6.4-2 of 3GPP TS 38.214 V18.1.0, respectively.
[0043] μ in Equation 2 is the maximum T proc,2 μ DL , μ UL For example, μ PDCCH μ corresponds to the downlink SCS in which the PDCCH carrying the DCI scheduling the PUSCH is transmitted. UL corresponds to the SCS of the uplink channel on which the PUSCH is to be transmitted. Note that the SCS corresponding to μ is μ ・It may be calculated at 15 [kHz].
[0044] κ and T in Equation 2 ext may be the same as Equation 1. Furthermore, max(X, Y) may be a function that finds the maximum value of X and Y.
[0045] d in Equation 2 2,1may be a value determined based on whether the first symbol of the PUSCH allocation is DMRS only.
[0046] d in Equation 2 2 may be a value determined based on the priority of PUCCH, PUSCH, etc., or may be 0.
[0047] d in Equation 2 2,2 may be the BWP switching time if the scheduling DCI triggers a switch of the BWP, or may be 0 otherwise.
[0048] T in Equation 2 switch may be the switching gap time or may be 0.
[0049] <Time Domain Resource Allocation> In NR, in order to set the time domain relationship between the PDCCH and the physical shared channel (PDSCH, PUSCH), time domain resource allocation (TDRA) information may be configured in the UE by higher layer parameters. The TDRA information of the PDSCH may be, for example, the RRC control element "PDSCH-TimeDomainResourceAllocation". The TDRA information of the PUSCH may be, for example, the RRC control element "PUSCH-TimeDomainResourceAllocation".
[0050] One piece of TDRA information may include parameters such as a slot offset between [a PDCCH carrying] a DCI and a physical shared channel scheduled [by the DCI or the PDCCH], a mapping type of the physical shared channel, a start symbol of the physical shared channel, a length of the physical shared channel, etc. Note that the terms TDRA information and TDRA may be interchangeable.
[0051] The slot offset between the DCI (PDCCH) and the PDSCH scheduled by the DCI (PDCCH) is K0, K 0 , k0, k 0In addition, the slot offset between the DCI (PDCCH) and the PUSCH scheduled by the DCI (PDCCH) is K2, K 2 , k2, k 2 It may also be called, for example.
[0052] A time domain resource allocation list containing one or more TDRA information may be configured for the UE. For the PDSCH, a PDSCH time domain resource allocation list (e.g., RRC control element "PDSCH-TimeDomainResourceAllocationList") may be configured. For the PUSCH, a PUSCH time domain resource allocation list (e.g., RRC control element "PUSCH-TimeDomainResourceAllocationList") may be configured.
[0053] In the information signaled by DCI / RRC, the UE is informed which of the configured TDRA information (contained in the time domain resource allocation list) to apply for the information. The information may be a DL assignment (DL scheduling information) for DL and a UL grant (UL scheduling information) for UL. The TDRA information to apply may be indicated, for example, by a TDRA field included in the DCI.
[0054] 4 is a diagram showing some of the RRC information elements related to TDRA information of PDSCH in the existing 3GPP standard. This example is described using Abstract Syntax Notation One (ASN.1) notation. Note that, since this is merely an example, it is acceptable that the description is not complete. This also applies to subsequent similar drawings.
[0055] The RRC control element "PDSCH-TimeDomainResourceAllocation" may include k0, which is an integer value between 0 and 32. The RRC control element "PDSCH-TimeDomainResourceAllocation-r16" that can be used in Rel. 16 NR and later may include k0-r16, which is an integer value between 0 and 32, and k0-v1710, which is an integer value between 33 and 128. Note that k0-v1710 may only be applied to PDSCHs with an SCS of 480 kHz or 960 kHz.
[0056] FIG. 5 is a diagram showing some of the RRC information elements related to TDRA information of the PUSCH in the existing 3GPP standard.
[0057] The RRC control element "PUSCH-TimeDomainResourceAllocation" may include k2, which is an integer value between 0 and 32. The RRC control element "PUSCH-TimeDomainResourceAllocation-r16", which may be used in Rel. 16 NR and later, may include k0-r16, which is an integer value between 0 and 32.
[0058] <HARQ-ACK timing> In NR, the timing from the slot for receiving a PDSCH to transmitting a HARQ-ACK corresponding to the PDSCH (which may also be referred to as HARQ-ACK timing, ACK / NACK (A / N) feedback timing, etc.) may be set in the UE by a higher layer parameter.
[0059] The slot offset between the PDSCH and the HARQ-ACK corresponding to the PDSCH is K1, K2, K3, K4, K5, K6, K7, K8, K9, K10, K11, K12, K13, K14, K15, K16, K17, K18, K19, K20, K21, K22, K23, K24, K25, K26, K27, K28, K2 1 , k1, k 1 It may also be called, for example.
[0060] 6 is a diagram illustrating some of the RRC information elements related to HARQ-ACK timing information in the existing 3GPP standard. As shown in the figure, the RRC parameter "dl-DataToUL-ACK" and the RRC control element "DL-DataToUL-ACK-r16" which are HARQ-ACK timing information may be included in the RRC control element "PUCCH-Config" which is PUCCH configuration information.
[0061] The RRC parameter "dl-DataToUL-ACK" indicates a sequence containing 1 to 8 integer values between 0 and 15, inclusive, indicating k1. The RRC control element "DL-DataToUL-ACK-r16", which can be used in Rel. 16 NR and later, indicates a sequence containing 1 to 8 integer values between -1 and 15, inclusive, indicating k1. Note that the value "-1" corresponds to a "not applicable value" when HARQ-ACK timing is not explicitly included in PDSCH scheduling.
[0062] A value in the above sequence may be specified by the PDSCH-to-HARQ feedback timing indication field included in the DCI scheduling the PDSCH. The transmission timing of the HARQ-ACK corresponding to the PDSCH may be determined based on the reception timing of the PDSCH and a specified integer value included in the dl-DataToUL-ACK or DL-DataToUL-ACK-r16.
[0063] (Nonlinear Problems of Power Amplifiers (PAs)) In wireless communication, transmission signals are generally amplified by a power amplifier (PA) in a transmitter. However, it is known that PAs can cause nonlinear distortion, interference, and the like when the input power is large.
[0064] 7 is a diagram showing an example of the input / output characteristics of a PA. In an ideal PA, the output voltage is amplified linearly relative to the input voltage. However, in a real PA, the input voltage has a nearly linear characteristic when it is below a certain value, but when it exceeds that value, the output voltage has a nonlinear characteristic, and the amplification of the output voltage relative to the input voltage becomes saturated.
[0065] FIG. 8 is a diagram showing an example of nonlinear distortion caused by the nonlinear characteristics of a PA. This diagram, also known as a constellation diagram, has the horizontal axis representing in-phase and the vertical axis representing quadrature. This example shows an example of nonlinear distortion experienced by modulation symbols based on 256 Quadrature Amplitude Modulation (QAM). For example, complex numbers corresponding to baseband signals obtained at the receiving end from signals output / transmitted through a PA are plotted. The 256 signal points corresponding to the original modulation symbols are blurred due to nonlinear distortion.
[0066] In addition to PAs, nonlinear distortion can also be caused by oscillators, active elements, passive elements, etc. Only the receiver side can observe the complete nonlinear distortion of the transmitted signal. Because many transmitter and receiver modules are provided by various vendors, there are a huge number of transmitter and receiver combinations, and the nonlinear distortion in DL and UL communications varies greatly.
[0067] As the signal-to-noise ratio (SNR) at the receiver improves, nonlinear distortion interference (e.g., increasing Peak-to-Average Power Ratio (PAPR)) can limit the receiver performance and become a major factor in detected errors.
[0068] (Application of Artificial Intelligence (AI) Technology to Wireless Communications) With regard to future wireless communications technologies, the use of AI technology such as machine learning (ML) for network / device control and management is being considered.
[0069] For example, it is being considered that terminals (user terminals, user equipment (UE)) / base stations (BSs) will utilize AI technology to improve Channel State Information (CSI) feedback (e.g., reduced overhead, improved accuracy, prediction), improve beam management (e.g., improved accuracy, prediction in the time / space domain), and improve position measurement (e.g., improved position estimation / prediction).
[0070] Based on the input information, the AI model may output at least one information such as an estimate, a prediction, a selected action, a classification, etc. The UE / BS may input channel state information, reference signal measurements, etc. to the AI model and output highly accurate channel state information / measurements / beam selection / location, future channel state information / radio link quality, etc.
[0071] In the present disclosure, AI may be interpreted as an object (also called a subject, object, data, function, program, etc.) that has (performs) at least one of the following characteristics: - Estimation based on observed or collected information; - Selection based on observed or collected information; - Prediction based on observed or collected information.
[0072] In the present disclosure, estimation, prediction, and inference may be used interchangeably. Also, in the present disclosure, estimate, predict, and infer may be used interchangeably.
[0073] In the present disclosure, an object may be, for example, an apparatus, device, etc., such as a UE or a BS. Also, in the present disclosure, an object may correspond to a program / model / entity that operates in the apparatus.
[0074] For future wireless communication technologies (e.g., 3GPP Rel. 19, 20, 21), the use of AI technology to compensate for the above-mentioned nonlinear distortion is being considered.
[0075] Figure 9 is a diagram showing an example of compensation for nonlinear distortion caused by the nonlinear characteristics of a PA. This example shows an example in which the nonlinear distortion in Figure 8 is compensated for using a certain AI technology. Points close to the original 256 signal points are plotted, demonstrating that the impact of nonlinear distortion can be reduced by AI technology.
[0076] The compensation of the nonlinear distortion may be performed at the transmitter side / receiver side. For example, in one scenario of adopting AI, a one-sided model for either the transmitter or the receiver may be adopted, and in another scenario, a two-sided model for both the transmitter and the receiver may be adopted.
[0077] AI techniques for transforming signal waveforms for communications (which may also be referred to as AI transformation, AI-based transformation, AI waveform transformation, waveform conversion, etc.) are being considered to compensate for nonlinear distortion, reduce additional CP, etc. AI transformation may include, for example, at least one of the following using AI techniques: signal constellation compensation, modulation scheme selection, modulation, sequence generation, selective mapping of complex-valued [modulation] symbols, tone reservation (TR), resource [element] mapping, and transformation (e.g., shift / scale) of complex-valued / time-continuous signals.
[0078] For example, signal constellation compensation may correspond to a technique for mitigating nonlinear effects and reducing Peak-to-Average Power Ratio (PAPR) problems by shifting / scaling / rotating a signal constellation at the transmitter / receiver side.
[0079] AI conversion is expected to improve spectral efficiency and system performance, but it is thought that AI conversion increases the computational complexity compared to existing NR signal waveform generation methods.
[0080] The inventors have found that, considering the processing capabilities of the UE, the increased computational complexity due to AI conversion results in additional processing time in the UE. Therefore, it is preferable to adjust the time-related elements of the UE processing described above with respect to AI conversion, but the relevant settings / controls have not yet been studied. Unless these are clearly defined, it may be impossible to perform suitable waveform conversion, which may hinder improvements in communication throughput / communication quality.
[0081] Therefore, the present inventors have conceived a suitable setting / control method for waveform conversion. According to one aspect of the present disclosure, performance can be improved (for example, nonlinearity problems in PA can be reduced) by using a waveform conversion function that takes into account the interaction between a UE and a network (NW).
[0082] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.
[0083] (Various Reinterpretations) In the present disclosure, a word enclosed in "( )" in a sentence may indicate an explanation of the word immediately preceding it (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Furthermore, in the present disclosure, a word enclosed in "[ ]" in a sentence may be interpreted including the word in the meaning of the entire sentence, or may be interpreted excluding (ignoring) the word in the meaning of the entire sentence. Note that "( )" and "[ ]" may also be used for purposes / meanings other than those mentioned above.
[0084] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."
[0085] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.
[0086] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.
[0087] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.
[0088] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.
[0089] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.
[0090] In this disclosure, "functionality" may refer to a set of parameters / features (e.g., a set of parameters for waveform transformation techniques, CSI prediction, beam prediction, CSI compression, etc.) that are supported based on conditions specified by the UE capabilities.
[0091] In this disclosure, a "model identifier (ID)" may refer to an ID associated with a functionality / additional condition (or a model corresponding to that ID). Note that a model ID may be interchangeably read as an AI ID, a dataset ID, a pairing ID, etc.
[0092] In the present disclosure, function / functionality may be read as any of feature, function, and functionality.
[0093] In the present disclosure, the terms model, function, functionality, model ID, function ID, functionality ID, etc. may be read interchangeably.
[0094] In the following embodiments, AI conversion may be interchangeably read as any AI processing.
[0095] (Wireless Communication Method) First Embodiment The first embodiment relates to an AI indicator (which may also be called AI specific information) and AI granularity.
[0096] The AI indicator / AI granularity may be set / confirmed for the UE or may be reported by the UE to the NW. In the present disclosure, the AI indicator / AI granularity may be set / confirmed / reported for the above-mentioned AI transformations (e.g., one or more of AI-based waveform, AI-based resource element mapping, AI-based sequence handling, AI-based tone handling, AI-based modulation / demodulation, etc.), or may be set / confirmed / reported in association with an AI function / model.
[0097] The AI indicator may indicate the selected AI transformation function. The AI indicator may be expressed in (or associated with) any of the following units or combinations thereof: Parts separated by AI granularity; Some combination of parts separated by AI granularity.
[0098] The AI granularity may be at least one of the following (may be set in at least one of the following units): - per model or fine granularity, - per function or [first] medium granularity, - per model information or [second] medium granularity, - per complexity or coarse granularity.
[0099] The model information may be at least one of information about the AI model, such as the number of layers, the size of input / output, model structure, etc. The complexity may be, for example, UE capability.
[0100] As an example, if the AI indicator is determined for each portion divided by the AI granularity, the AI indicator may indicate a model if the AI granularity is fine, or may indicate a function if the AI granularity is [first] medium.
[0101] One or more AI indicators / AI granularities may be specified to the UE by DCI / MAC CE / RRC in association with one or more PDCCH / PUCCH / PDSCH / PUSCH.
[0102] For example, from multiple AI indicators configured in RRC, some AI indicators may be activated by the MAC CE, and one or more AI indicators from the activated AI indicators may be assigned to the UE by a specific field (e.g., AI indicator field) of the DCI. For example, one or more AI indicators may assign only an AI-based waveform function, a combination of an AI-based waveform function and an AI-based modulation function, or the entire AI-based conversion function.
[0103] The available AI indicators may be different for one or more of the PDCCH, PUCCH, PDSCH, and PUSCH. For example, the multiple AI indicators configured in the RRC described above may be different for one or more of the PDCCH, PUCCH, PDSCH, and PUSCH.
[0104] Note that a specific AI indicator [specifying a model / function] may be set as a default setting. For example, if a certain AI process is to be performed but the corresponding AI indicator is not specified, the UE may use the specific AI indicator as the default setting for the AI process.
[0105] According to the first embodiment described above, for example, it is possible to appropriately specify the AI conversion function for the UE, and appropriately report the AI conversion function supported by the UE to the NW.
[0106] Second Embodiment The second embodiment relates to the PDSCH processing time.
[0107] In association with the AI indicator, the PDSCH processing time may be configured / confirmed for the UE or reported by the UE to the NW. In other words, the UE may determine the PDSCH processing time based on the AI indicator.
[0108] The AI indicator in the description of the second embodiment may correspond to an AI indicator associated with at least one of the PDCCH (which schedules the PDSCH), the PDSCH, and the PUCCH which transmits the HARQ-ACK corresponding to the PDSCH.
[0109] The second embodiment is broadly divided into the following three embodiments: - Embodiment 2.1: Extending the existing table of PDSCH processing time settings; - Embodiment 2.2: Introducing additional PDSCH processing time settings; - Embodiment 2.3: Introducing a new table of PDSCH processing time settings.
[0110] <<Embodiment 2.1>> In embodiment 2.1, the existing table regarding the PDSCH processing time may be extended. In other words, in embodiment 2.1, the PDSCH decoding time N 1 may be associated with the AI indicator using a table that extends an existing table.
[0111] FIG. 10 is a diagram showing an example of an extension table of PDSCH decoding times for PDSCH processing capability 1 in embodiment 2.1.
[0112] In this example, the "Normal" column indicates the normal PDSCH decoding time N1 regardless of the AI indicator. The "AI Indicator i" column (i is an integer) indicates the PDSCH decoding time N for the PDSCH associated with the AI indicator i. 1 Shows.
[0113] Note that the column names such as "Normal" and "AI Indicator i" and the values in the table are merely examples, and may be replaced with any column names and values.
[0114] Any value in the table may be predefined or may be determined based on at least one of parameters set / indicated to the UE by higher layer signaling / physical layer signaling, UE capabilities, associated functionality / model, etc.
[0115] The values in the table may depend on the SCS (the values may be different for each SCS), and as shown, the example table may be extended for μ>6 (e.g. μ=7, 8, ...).
[0116] It should be noted that the table format is not necessarily used. For example, the PDSCH decoding time N for the PDSCH related to the AI indicator i for μ is 1、μ is the function f(N 1、0 , μ), the UE is configured 1、0 and a function f whose parameters are set or defined, 1、μ You may ask for:
[0117] These may be similar to other table examples below, so they will not be described again.
[0118] Similar to the above-described extended table of PDSCH decoding times for PDSCH processing capability 1, an extended table of PDSCH decoding times for PDSCH processing capability 2 may be defined based on the existing table of PDSCH decoding times for PDSCH processing capability 2. When a UE has / is configured to process PDSCH processing capability 2, the PDSCH decoding time N is set based on the extended table of PDSCH decoding times for PDSCH processing capability 2. 1 may be determined.
[0119] <<Embodiment 2.2>> In embodiment 2.2, the existing calculation formula for the PDSCH processing time may be extended or a variable may be added. In other words, in embodiment 2.2, the PDSCH decoding time N 1 Variables other than may be associated with the AI indicator.
[0120] For example, instead of Equation 1 above, T proc,1may be calculated by Equation 3. (Equation 3) T proc,1 = (N 1 +N ai +d 1,1 +d 2 +d 3 )(2048+144)・κ2 -μ ・T C +T ext
[0121] Here, N ai may be determined by the PDSCH decode [addition] time relative to the AI indicator. For example, N ai is the PDSCH decoding time N of the selected AI indicator [i] ai_indicator[_i] may be equal to (N ai = N ai_indicator[_i] ).
[0122] Also, N ai is the PDSCH decoding time of one or more selected AI indicators (e.g., N for AI indicator i). ai_indicator_i ) (e.g., if AI indicators 1 and 3 are selected, N ai = max (N ai_indicator_1 , N ai_indicator_3 )).
[0123] Also, N ai may be calculated based on the sum of the PDSCH decoding times of one or more selected AI indicators (e.g., if AI indicators 1 and 3 are selected, N ai = N ai_indicator_1 +N ai_indicator_3 ).
[0124] In addition, N ai is a different name (e.g., d 4 , d ai ) or T ext and similar time unit parameters (e.g., T ai For example, instead of the above equation 1, T proc,1 may be calculated by Equation 4. (Equation 4) T proc,1 = (N 1 +d 1,1 +d2 +d 3 )(2048+144)・κ2 -μ ・T C +T ext +T ai
[0125] Also, T proc,1 remains as in Equation 1, and the above-mentioned L 1 T in the definition of proc,1 T proc,1 +T ai (which can be said to be equivalent to Equation 4).
[0126] 11 is a diagram showing an example of a table of PDSCH decoding times for PDSCH processing capability 1 in embodiment 2.2. In this example, the PDSCH decoding time N ai_indicator_1 The PDSCH decoding time N for another AI indicator i is ai_indicator_i A table for may be defined separately.
[0127] The PDSCH decoding time N of the AI indicator [i] for the PDSCH processing capability 1 ai_indicator[_i] Similarly to the table for PDSCH processing capability 2, the PDSCH decoding time N ai_indicator[_i] If a UE has PDSCH processing capability 2 and is configured to process / has PDSCH decoding time N ai_indicator[_i] Based on the table [and equation 3 / 4] for T proc,1 may be determined.
[0128] <<Embodiment 2.3>> In embodiment 2.3, a new table for PDSCH processing times associated with AI granularity / specified by AI indicators may be defined. For example, in embodiment 2.3, the PDSCH decoding time N 1 may be associated with the AI indicator using a new table rather than an existing table.
[0129] A new table may be defined for each AI granularity (e.g., model, function, UE capability), for example, a table of PDSCH decoding times for UE capabilities related to AI processing (e.g., may be referred to as UE capability 3, PDSCH processing capability 3, etc.) may be defined.
[0130] 12 is a diagram showing an example of a table of PDSCH decoding times for PDSCH processing capability 3 in embodiment 2.3. 1 may be used for Equation 1 when the UE reports to the network that it supports PDSCH processing capability 3 or is configured by the network to process PDSCH processing capability 3. The table in Figure 12 may be specified, for example, as Table 5.3-3 (PDSCH processing time for PDSCH processing capability 3) in 3GPP TS 38.214 V18.1.0.
[0131] According to the second embodiment described above, it is possible to appropriately set the PDSCH processing time that can accommodate an increase in UE processing time due to AI conversion.
[0132] <Third Embodiment> The third embodiment relates to a PDSCH reception preparation time.
[0133] In association with the AI indicator, the PDSCH reception preparation time may be configured / confirmed for the UE or reported by the UE to the NW. In other words, the UE may determine the PDSCH reception preparation time based on the AI indicator.
[0134] The AI indicator in the description of the third embodiment may correspond to an AI indicator associated with at least one of a PDCCH (which schedules a PDSCH) and a PDSCH scheduled by the PDCCH.
[0135] The third embodiment is roughly divided into the following two: Embodiment 3.1: Extending the existing table for PDSCH reception preparation time setting; and Embodiment 3.2: Introducing an additional PDSCH reception preparation time setting.
[0136] <<Embodiment 3.1>> In embodiment 3.1, an existing table relating to the PDSCH reception preparation time may be extended. In other words, in embodiment 3.1, the PDSCH reception preparation time N pdsch may be associated with the AI indicator using a table that extends an existing table.
[0137] FIG. 13 shows the N pdsch FIG. 10 is a diagram illustrating an example of an extension table.
[0138] In this example, the "Normal" column indicates the normal PDSCH reception preparation time N pdsch The column "AI Indicator i" (i is an integer) indicates the PDSCH reception preparation time N for the PDCCH / PDSCH related to the AI indicator i. pdsch Shows.
[0139] <<Embodiment 3.2>> In embodiment 3.2, the PDSCH reception preparation time N pdsch Variables other than may be associated with the AI indicator.
[0140] For example, N shown in FIG. pdsch and N ai The sum of (N pdsch +N ai ) may be used as the PDSCH reception preparation time. ai may be determined by the PDSCH reception preparation [additional] time for the AI indicator. For example, N ai is the PDSCH reception preparation time N of the selected AI indicator [i] ai_indicator[_i] may be equal to (N ai = N ai_indicator[_i] ).
[0141] Also, N ai is the PDSCH reception preparation time of one or more selected AI indicators (e.g., N for AI indicator i). ai_indicator_i ) (for example, if AI indicators 1 and 3 are selected, N ai = max (Nai_indicator_1 , N ai_indicator_3 )).
[0142] Also, N ai may be calculated based on the sum of the PDSCH reception preparation times of one or more selected AI indicators (e.g., if AI indicators 1 and 3 are selected, N ai = N ai_indicator_1 +N ai_indicator_3 ).
[0143] In addition, N ai is a different name (e.g., d ai ) may also be called.
[0144] N ai_indicator_i may be represented by a separate table for each AI indicator i, as shown in FIG.
[0145] According to the third embodiment described above, it is possible to appropriately set the PDSCH reception preparation time that can accommodate the increase in UE processing time due to AI conversion.
[0146] <Fourth Embodiment> The fourth embodiment relates to a PUSCH preparation time.
[0147] In association with the AI indicator, the PUSCH preparation time may be configured / confirmed for the UE or reported by the UE to the NW. In other words, the UE may determine the PUSCH preparation time based on the AI indicator.
[0148] The AI indicator in the description of the fourth embodiment may correspond to an AI indicator associated with at least one of the PDCCH and the PUSCH (which schedules the PUSCH).
[0149] The fourth embodiment can be broadly divided into the following three embodiments: - Embodiment 4.1: Extending the existing table for PUSCH preparation time settings; - Embodiment 4.2: Introducing additional PUSCH preparation time settings; - Embodiment 4.3: Introducing a new table for PUSCH preparation time settings.
[0150] <<Embodiment 4.1>> In embodiment 4.1, an existing table regarding the PUSCH preparation time may be extended. In other words, in embodiment 4.1, the PUSCH preparation time N 2 may be associated with the AI indicator using a table that extends an existing table.
[0151] FIG. 14 is a diagram showing an example of an extended table of PUSCH preparation times for PUSCH timing capability 1 in embodiment 4.1.
[0152] In this example, the "Normal" column indicates the normal PUSCH preparation time N 2 The column "AI Indicator i" (i is an integer) indicates the PUSCH preparation time N for the PUSCH related to AI indicator i. 2 Shows.
[0153] Similar to the above-mentioned extended table of PUSCH preparation times for PUSCH timing capability 1, an extended table of PUSCH preparation times for PUSCH timing capability 2 may be defined based on the existing table of PUSCH preparation times for PUSCH timing capability 2. When a UE has / is configured to process PUSCH timing capability 2, the PUSCH preparation time N is set based on the extended table of PUSCH preparation times for PUSCH timing capability 2. 2 may be determined.
[0154] <<Embodiment 4.2>> In embodiment 4.2, the existing calculation formula for the PUSCH preparation time may be extended or a variable may be added. In other words, in embodiment 4.2, the PUSCH preparation time N 2 Variables other than may be associated with the AI indicator.
[0155] For example, instead of Equation 2 above, T proc,2 may be calculated by Equation 5. (Equation 5) T proc,2 = max ((N 2 +N ai +d 2,1 +d 2 )(2048+144)・κ2 -μ・T C +T ext +T switch, d 2,2 )
[0156] Here, N ai may be determined by the PUSCH preparation [addition] time for the AI indicator. For example, N ai is the PUSCH preparation time N of the selected AI indicator [i] ai_indicator[_i] may be equal to (N ai = N ai_indicator[_i] ).
[0157] Also, N ai is the PUSCH preparation time of one or more selected AI indicators (e.g., N for AI indicator i). ai_indicator_i ) (for example, if AI indicators 1 and 3 are selected, N ai = max (N ai_indicator_1 , N ai_indicator_3 )).
[0158] Also, N ai may be calculated based on the sum of the PUSCH preparation times of one or more selected AI indicators (e.g., if AI indicators 1 and 3 are selected, N ai = N ai_indicator_1 +N ai_indicator_3 ).
[0159] In addition, N ai is a different name (e.g., d 4 , d ai ) may also be called N ai Is T ext and similar time unit parameters (e.g., T ai For example, instead of Equation 2 above, T proc,2 may be calculated by Equation 6. (Equation 6) T proc,2 = max ((N 2 +N ai +d 2,1 +d 2 )(2048+144)・κ2 -μ ・T C +T ext +Tswitch +T ai, d 2,2 )
[0160] Also, T proc,2 remains as in Equation 2, and the above-mentioned L 2 T in the definition of proc,2 T proc,2 +T ai (which can be said to be equivalent to Equation 6).
[0161] 15 is a diagram showing an example of a table of PUSCH preparation times for PUSCH timing capability 1 in embodiment 4.2. In this example, the PUSCH preparation time N ai_indicator_1 The PUSCH preparation time N ai_indicator_i A table for may be defined separately.
[0162] The PUSCH preparation time N of the AI indicator [i] for the PUSCH timing capability 1 ai_indicator[_i] Similarly to the table for PUSCH timing capability 2, the PUSCH preparation time N ai_indicator[_i] If a UE has PUSCH timing capability 2 and is configured to process PUSCH timing capability 2, a table for PUSCH preparation time N ai_indicator[_i] Based on the table [and equations 5 / 6] for T proc,2 may be determined.
[0163] <<Embodiment 4.3>> In embodiment 4.3, a new table for PUSCH preparation times associated with AI granularity / specified by AI indicators may be defined. For example, in embodiment 4.3, the PUSCH preparation time N 2 may be associated with the AI indicator using a new table rather than an existing table.
[0164] A new table may be defined for each AI granularity (e.g., model, function, UE capability). For example, a table of PUSCH preparation times for UE capabilities related to AI processing (e.g., may be referred to as UE capability 3, PUSCH timing capability 3, etc.) may be defined.
[0165] 16 is a diagram showing an example of a table of PUSCH preparation times for PUSCH timing capability 3 in embodiment 4.3. 2 may be used for Equation 2 when the UE reports to the network that it supports PUSCH timing capability 3 or is configured by the network to process PUSCH timing capability 3. The table in Figure 16 may be specified, for example, as Table 6.4-3 (PUSCH preparation time for PUSCH timing capability 3) in 3GPP TS 38.214 V18.1.0.
[0166] According to the fifth embodiment described above, it is possible to appropriately set the PUSCH preparation time that can accommodate the increase in UE processing time due to AI conversion.
[0167] Fifth Embodiment The fifth embodiment relates to k0 of TDRA information of PDSCH.
[0168] In the fifth embodiment, control may be performed to accommodate a wider range of k0 than the existing range of k0, taking into account, for example, the PDCCH demodulation / decoding time added by AI conversion.
[0169] In association with the AI indicator, k may be configured / confirmed for the UE. In other words, the UE may determine k based on the AI indicator. The AI indicator in the description of the fifth embodiment may correspond to the AI indicator associated with the PDCCH / PDSCH (which schedules the PDSCH).
[0170] The fifth embodiment can be broadly divided into the following three: - Embodiment 5.1: Extending the existing range (domain) of k0; - Embodiment 5.2: Introducing a new parameter for k0; - Embodiment 5.3: Introducing a new parameter that complements (constitutes) k0.
[0171] In the fifth embodiment, k0 may be interchangeably read as other parameters related to k0, such as k0-r16 and k0-v1710 (the fifth embodiment may be applied to these).
[0172] Furthermore, the RRC information elements / parameters / fields described hereinafter regarding the fifth embodiment may be given notations such as "-rXX (or -VXXXX)" corresponding to 3GPP release numbers (e.g., 3GPP Rel. 19) or existing notations may be overwritten. However, for simplicity, the following description will be given without any notations.
[0173] <<Embodiment 5.1>> In embodiment 5.1, the existing range (domain) of k0 may be extended. When instructing a UE of an AI indicator related to a PDCCH, the base station may control to use k0 indicated by the PDCCH in a range extended from the existing range.
[0174] k0 may be set in the UE according to existing rules, or may be set according to (or associated with) the AI indicator for AI conversion.
[0175] 17 is a diagram showing some of the RRC information elements related to TDRA information of the PDSCH in embodiment 5.1. In this example, k0 is an integer value between 0 and 64, and can take a value in a wider range than the existing k0 (in FIG. 4).
[0176] Note that this number "64" is merely an example and may be another number [larger than the upper limit of the existing k0 range (e.g., 32)]. This number may be predefined, or may be determined based on parameters configured / instructed to the UE by higher layer signaling / physical layer signaling, or may be determined based on UE capabilities, or may be determined based on functionality / model / AI indicators associated with the PDCCH / PDSCH.
[0177] <<Embodiment 5.2>> In embodiment 5.2, in addition to k0, k0 (for each AI indicator) for the case where an AI conversion is applied (e.g., k0 for AI indicator i may be referred to as k0-AI-Indicator-i) may be set. In this embodiment, k0 not related to an AI indicator (e.g., when an AI indicator is not set) may be referred to as an existing [defined in the standard] k0, a normal k0, a base k0, a default k0, etc.
[0178] Which setting of the configured base k0 and each k0-AI-Indicator-i is valid (which setting is actually used to determine the timing of the PDSCH) may depend on the configured AI indicator. For example, when AI indicator 1 is configured, k0-AI-Indicator-1 may be selected.
[0179] 18 is a diagram showing some of the RRC information elements related to the TDRA information of the PDSCH in embodiment 5.2. In this example, in addition to the base k0, k0-AI-Indicator-1 and k0-AI-Indicator-2, which are integer values between 0 and 64 and can take on a wider range of values than the existing k0 (in FIG. 4), can be set.
[0180] Note that this number "64" is merely an example and may be another number [larger than the upper limit of the existing k0 range (e.g., 32)]. This number may be predefined, or may be determined based on parameters configured / instructed to the UE by higher layer signaling / physical layer signaling, or may be determined based on UE capabilities, or may be determined based on functionality / model / AI indicators associated with the PDCCH / PDSCH.
[0181] <<Embodiment 5.3>> In embodiment 5.3, k0 actually used to determine the timing of PDSCH is calculated based on k0 not associated with the AI indicator (e.g., when the AI indicator is not set) and k0 (for each AI indicator) for the case where an AI conversion is applied (e.g., k0 for AI indicator i may be referred to as k0-AI-Indicator-i). In this embodiment, k0 not associated with the AI indicator may be referred to as an existing [standard-defined] k0, a normal k0, a base k0, a default k0, or the like.
[0182] The k0 actually used to determine the timing of the PDSCH may be calculated by Equation 7. (Equation 7) k0 = base k0 + Σ(e i *k0-AI-Indicator-i)
[0183] Here, e i is a value that depends on whether AI indicator i is set or not. For example, if AI indicator i is set, e i = 1, otherwise e i = 0. In other words, Equation 7 means that the value obtained by adding all the k0 values for the set AI indicator i to the base k0 is used as k0.
[0184] 19 is a diagram showing some of the RRC information elements related to the TDRA information of the PDSCH in embodiment 5.3. In this example, in addition to the base k0, k0-AI-Indicator-1 and k0-AI-Indicator-2, which are integer values between 0 and 32, can be set. k0-AI-Indicator-1 and k0-AI-Indicator-2 do not have to be able to take values in a wider range than the existing k0 (in FIG. 4).
[0185] Note that this number "32" is merely an example and may be another number [less than (or greater than) the upper limit of the existing k0 range (e.g., 32)]. This number may be predefined, or may be determined based on parameters configured / instructed to the UE by higher layer signaling / physical layer signaling, or may be determined based on UE capabilities, or may be determined based on functionality / model / AI indicators associated with the PDCCH / PDSCH.
[0186] <<Modifications>> In Embodiments 5.1 to 5.3, information on k0 is included in the RRC control element "PDSCH-TimeDomainResourceAllocation." However, the information may be set by an RRC control element other than the RRC control element "PDSCH-TimeDomainResourceAllocation," or may be specified in advance in a standard. Furthermore, the RRC control element "PDSCH-TimeDomainResourceAllocationList" including information on k0 may be set in association with an AI indicator (e.g., for each AI indicator).
[0187] According to the fifth embodiment described above, k0 can be appropriately set to accommodate an increase in UE processing time due to AI conversion.
[0188] Sixth Embodiment The sixth embodiment relates to k1 indicating HARQ-ACK timing for PDSCH.
[0189] In the sixth embodiment, control may be performed to accommodate a wider range of k1 than the existing range of k1, taking into account, for example, the PDSCH processing time [ / processing time for PUCCH (UCI)] added by AI conversion. Note that in the present disclosure, k1 may be interchangeably read as the value of each entry of the HARQ-ACK timing information (for example, the value of an individual entry in the sequence of "dl-DataToUL-ACK" or "DL-DataToUL-ACK-r16").
[0190] In association with the AI indicator, k1 may be configured / confirmed for the UE. In other words, the UE may determine k1 based on the AI indicator. The AI indicator in the description of the sixth embodiment may correspond to the AI indicator associated with the PDSCH / PUCCH.
[0191] The sixth embodiment can be broadly divided into the following three: - Embodiment 6.1: Extending the existing range (domain) of k1; - Embodiment 6.2: Introducing a new parameter for k1; - Embodiment 6.3: Introducing a new parameter that complements (constitutes) k1.
[0192] In addition, in the sixth embodiment, "dl-DataToUL-ACK" may be interchangeably read as other k1-related parameters such as "DL-DataToUL-ACK-r16", "DL-DataToUL-ACK-r17", "DL-DataToUL-ACK-v1700", "DL-DataToUL-ACK-DCI-1-2-r16", and "DL-DataToUL-ACK-DCI-1-2-r17" (the sixth embodiment may be applied to these).
[0193] Furthermore, the RRC information elements / parameters / fields described hereinafter in relation to the sixth embodiment may be given a notation such as "-rXX (or -VXXXX)" corresponding to a 3GPP release number (e.g., 3GPP Rel. 19) or may have an existing notation overwritten. However, for simplicity, the description will be given without any notation.
[0194] <<Embodiment 6.1>> In embodiment 6.1, the existing range (domain) of k1 may be extended. When instructing a UE of an AI indicator related to a PDSCH / PUCCH, the base station may control k1 for the PDSCH / PUCCH to use a range of k1 that is extended from the existing range.
[0195] k1 may be set in the UE according to existing rules, or may be set according to (or associated with) an AI indicator for AI conversion.
[0196] 20 is a diagram illustrating a part of an RRC information element related to HARQ-ACK timing information in embodiment 6.1. In this example, k1 is an integer value between 0 and 31, and can take a value in a wider range than the existing k1 (in FIG. 6).
[0197] Note that the number "31" is merely an example and may be another number [larger than the upper limit of the existing k1 range (e.g., 15)]. This number may be predefined, or may be determined based on parameters configured / instructed to the UE by higher layer signaling / physical layer signaling, or may be determined based on UE capabilities, or may be determined based on functionality / model / AI indicators associated with the PDCCH.
[0198] <<Embodiment 6.2>> In embodiment 6.2, in addition to k1, k1 (for each AI indicator) for the case where an AI conversion is applied (e.g., k1 for AI indicator i may be referred to as k1-AI-Indicator-i) may be set. In this embodiment, k1 not related to an AI indicator (e.g., when an AI indicator is not set) may be referred to as an existing [defined in the standard] k1, a normal k1, a base k1, a default k1, etc.
[0199] Which setting of the configured base k1 and each k1-AI-Indicator-i is valid (which setting is actually used to determine the HARQ-ACK timing) may depend on the configured AI indicator. For example, when AI indicator 1 is configured, k1-AI-Indicator-1 may be selected.
[0200] 21 is a diagram illustrating a part of RRC information elements related to HARQ-ACK timing information in embodiment 6.2. In this example, in addition to the base k1, k1-AI-Indicator-1 and k1-AI-Indicator-2, which are integer values between 0 and 31 and can take a wider range of values than the existing k1 (in FIG. 6), can be set.
[0201] Note that the number "31" is merely an example and may be another number [larger than the upper limit of the existing k1 range (e.g., 15)]. This number may be predefined, or may be determined based on parameters configured / instructed to the UE by higher layer signaling / physical layer signaling, or may be determined based on UE capabilities, or may be determined based on functionality / model / AI indicators associated with the PDCCH.
[0202] <<Embodiment 6.3>> In embodiment 6.3, k1 actually used to determine the HARQ-ACK timing is calculated based on k1 not related to the AI indicator (e.g., when the AI indicator is not set) and k1 (for each AI indicator) for the case where an AI conversion is applied (e.g., k1 for AI indicator i may be referred to as k1-AI-Indicator-i). In this embodiment, k1 not related to the AI indicator may be referred to as an existing [standard-defined] k1, a normal k1, a base k1, a default k1, etc.
[0203] The k1 actually used to determine the timing of the PDSCH may be calculated by Equation 8. (Equation 8) k1 = base k1 + Σ(e i *k1-AI-Indicator-i)
[0204] Here, e i is a value that depends on whether AI indicator i is set or not. For example, if AI indicator i is set, e i = 1, otherwise e i = 0. In other words, Equation 8 means that the value obtained by adding all the k1s for the set AI indicator i to the base k1 is used as k1.
[0205] 22 is a diagram showing some of the RRC information elements related to HARQ-ACK timing information in embodiment 6.3. In this example, in addition to the base k1, k1-AI-Indicator-1 and k1-AI-Indicator-2, which are integer values between 0 and 15, can be set. k1-AI-Indicator-1 and k1-AI-Indicator-2 do not have to be able to take values in a wider range than the existing k1 (in FIG. 6).
[0206] Note that this number "15" is merely an example and may be another number [less than (or greater than) the upper limit of the existing k1 range (e.g., 15)]. This number may be predefined, or may be determined based on parameters configured / instructed to the UE by higher layer signaling / physical layer signaling, or may be determined based on UE capabilities, or may be determined based on functionality / model / AI indicators associated with the PDCCH.
[0207] <<Modifications>> In Embodiments 6.1 to 6.3, information on k1 is included in the RRC control element "PUCCH-Config." However, it may be configured by an RRC control element other than the RRC control element "PUCCH-Config," or may be defined in advance in a standard. Also, an RRC control element (e.g., dl-DataToUL-ACK-AI-Indicator) that is a list including information on k1 [for one or more AI indicators] may be configured in association with an AI indicator.
[0208] According to the sixth embodiment described above, k1 can be appropriately set to accommodate an increase in UE processing time due to AI conversion.
[0209] Seventh Embodiment The seventh embodiment relates to k2 of TDRA information of PUSCH.
[0210] In the seventh embodiment, control may be implemented to accommodate a wider range of k2 than the existing range of k2, taking into account, for example, the PDCCH demodulation / decoding time and PUSCH preparation time added by AI conversion.
[0211] In association with the AI indicator, k2 may be configured / confirmed for the UE. In other words, the UE may determine k2 based on the AI indicator. The AI indicator in the description of the fifth embodiment may correspond to an AI indicator associated with a PDCCH (scheduling a PUSCH) or a PUSCH scheduled by the PDCCH.
[0212] The seventh embodiment can be broadly divided into the following three: - Embodiment 7.1: Extending the existing range (domain) of k2; - Embodiment 7.2: Introducing a new parameter for k2; - Embodiment 7.3: Introducing a new parameter that complements (constitutes) k2.
[0213] In the seventh embodiment, k2 may be interchangeably read as other parameters related to k2, such as k2-r16 (the seventh embodiment may be applied to these).
[0214] Furthermore, the RRC information elements / parameters / fields described hereinafter regarding the seventh embodiment may be given notations such as "-rXX (or -VXXXX)" corresponding to 3GPP release numbers (e.g., 3GPP Rel. 19) or existing notations may be overwritten. However, for simplicity, the following description will be given without any notations.
[0215] <<Embodiment 7.1>> In embodiment 7.1, the existing range (domain) of k2 may be extended. When instructing a UE of an AI indicator related to a PDCCH / PUSCH, the base station may control to use k2 indicated by the PDCCH (or a PDCCH corresponding to the PUSCH) in a range extended from the existing range.
[0216] k2 may be set in the UE according to existing rules, or may be set according to (or associated with) the AI indicator for AI conversion.
[0217] 23 is a diagram illustrating a part of RRC information elements related to TDRA information of a PUSCH in embodiment 7.1. In this example, k2 is an integer value between 0 and 64, and can take a value in a wider range than the existing k2 (in FIG. 5).
[0218] Note that this number "64" is merely an example and may be another number [larger than the upper limit of the existing k2 range (e.g., 32)]. This number may be predefined, or may be determined based on parameters configured / instructed to the UE by higher layer signaling / physical layer signaling, or may be determined based on UE capabilities, or may be determined based on functionality / model / AI indicators associated with the PDCCH / PUSCH.
[0219] <<Embodiment 7.2>> In embodiment 7.2, in addition to k2, k2 (for each AI indicator) for the case where an AI conversion is applied (e.g., k2 for AI indicator i may be referred to as k2-AI-Indicator-i) may be set. In this embodiment, k2 not related to an AI indicator (e.g., when an AI indicator is not set) may be referred to as an existing [defined in the standard] k2, a normal k2, a base k2, a default k2, etc.
[0220] Which setting of the configured base k2 and each k2-AI-Indicator-i is valid (which setting is actually used to determine the timing of the PUSCH) may depend on the configured AI indicator. For example, when AI indicator 1 is configured, k2-AI-Indicator-1 may be selected.
[0221] 24 is a diagram showing some of the RRC information elements related to TDRA information of the PUSCH in embodiment 7.2. In this example, in addition to the base k2, k2-AI-Indicator-1 and k2-AI-Indicator-2, which are integer values between 0 and 64 and can take a wider range of values than the existing k2 (in FIG. 5), can be set.
[0222] Note that this number "64" is merely an example and may be another number [larger than the upper limit of the existing k2 range (e.g., 32)]. This number may be predefined, or may be determined based on parameters configured / instructed to the UE by higher layer signaling / physical layer signaling, or may be determined based on UE capabilities, or may be determined based on functionality / model / AI indicators associated with the PDCCH / PUSCH.
[0223] <<Embodiment 7.3>> In embodiment 7.3, k2 actually used to determine the timing of PUSCH is calculated based on k2 not related to the AI indicator (e.g., when the AI indicator is not set) and k2 (for each AI indicator) for the case where an AI conversion is applied (e.g., k2 for AI indicator i may be referred to as k2-AI-Indicator-i). In this embodiment, k2 not related to the AI indicator may be referred to as an existing [standard-defined] k2, a normal k2, a base k2, a default k2, etc.
[0224] The k2 actually used to determine the timing of the PUSCH may be calculated by Equation 9. (Equation 9) k2 = base k2 + Σ(e i *k2-AI-Indicator-i)
[0225] Here, ei is a value that depends on whether AI indicator i is set or not. For example, if AI indicator i is set, e i = 1, otherwise e i= 0. In other words, Equation 9 means that the value obtained by adding all the k2 values for the set AI indicator i to the base k2 is used as k2.
[0226] 25 is a diagram showing some of the RRC information elements related to TDRA information of PUSCH in embodiment 7.3. In this example, in addition to the base k2, k2-AI-Indicator-1 and k2-AI-Indicator-2, which are integer values between 0 and 32, can be set. k2-AI-Indicator-1 and k2-AI-Indicator-2 do not need to be able to take values in a wider range than the existing k2 (in FIG. 5).
[0227] Note that this number "32" is merely an example and may be another number [less than (or greater than) the upper limit of the existing k2 range (e.g., 32)]. This number may be predefined, or may be determined based on parameters configured / instructed to the UE by higher layer signaling / physical layer signaling, or may be determined based on UE capabilities, or may be determined based on functionality / model / AI indicators associated with the PDCCH / PUSCH.
[0228] <<Modifications>> In Embodiments 7.1 to 7.3, information on k2 is included in the RRC control element "PUSCH-TimeDomainResourceAllocation." However, the information may be set by an RRC control element other than the RRC control element "PUSCH-TimeDomainResourceAllocation," or may be specified in advance in a standard. Furthermore, the RRC control element "PUSCH-TimeDomainResourceAllocationList" including information on k2 may be set in association with an AI indicator (e.g., for each AI indicator).
[0229] According to the seventh embodiment described above, k2 can be appropriately set to accommodate an increase in UE processing time due to AI conversion.
[0230] <Supplementary Information> <<Notification of Information to UE>> In the above-described embodiments, notification of any information to the UE [from a Network (NW) (e.g., a Base Station (BS))] (in other words, reception of any information from the BS by the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.
[0231] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.
[0232] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.
[0233] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.
[0234] <<Notification of Information from UE>> In the above-described embodiments, notification of any information from the UE [to the NW] (in other words, transmission / report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.
[0235] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.
[0236] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.
[0237] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.
[0238] <<Regarding Application of Each Embodiment>> In a UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the above-mentioned embodiments may be applied (used) when one or more of the following conditions are met: - a higher layer parameter indicating the specific processes / operations / controls / assumptions / information is configured; - the specific processes / operations / controls / assumptions / information is determined based on related higher layer parameters; - the specific processes / operations / controls / assumptions / information is specified / activated / triggered by a MAC CE / DCI / UCI / resource / channel / RS; - a specific UE capability indicating (or related to) the specific processes / operations / controls / assumptions / information is reported or supported; - the application of the specific processes / operations / controls / assumptions / information is determined based on specific conditions.
[0239] The specific UE capability may indicate at least one of the following: - Supporting the specific process / operation / control / assumption / information; - Supporting AI conversion [for a specific feature / functionality / model]; - Supported AI indicator / AI granularity; - Supported PDSCH processing time associated with [specific] AI indicator / AI granularity; - Supported PDSCH receive preparation time associated with [specific] AI indicator / AI granularity; - Supported PUSCH preparation time associated with [specific] AI indicator / AI granularity; - Supported k0 [value] associated with [specific] AI indicator / AI granularity; - Supported k1 [value] associated with [specific] AI indicator / AI granularity; - Supported k2 [value] associated with [specific] AI indicator / AI granularity.
[0240] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, a band, a band combination, a BWP, a component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC), or may be a capability for each functionality / model.
[0241] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).
[0242] If the above conditions are not met, the UE / BS may follow the behavior specified in existing 3GPP releases.
[0243] (Supplementary Note) The following invention is supplementary note regarding one embodiment of the present disclosure. [Supplementary Note 1] First information indicating a waveform conversion-related function (e.g., AI indicator) and second information regarding a time for a downlink channel associated with the first information (e.g., N 1 , N ai_indicator[_i] , N pdsch , k0, k1 (e.g., higher layer parameters), and a control unit that determines a time for the downlink channel based on the first information and the second information. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the time for the downlink channel is a physical downlink shared channel processing time. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the time for the downlink channel is a physical downlink shared channel reception preparation time. [Supplementary Note 4] The terminal according to any of Supplements 1 to 3, wherein the time for the downlink channel is a slot offset between a physical downlink control channel and a physical downlink shared channel. [Supplementary Note 5] The terminal according to any of Supplements 1 to 4, wherein the time for the downlink channel is a slot offset between a physical downlink shared channel and acknowledgement information corresponding to the physical downlink shared channel.
[0244] (Supplementary Note) The following invention is supplementary note regarding one embodiment of the present disclosure. [Supplementary Note 1] First information indicating a waveform conversion-related function (e.g., AI indicator) and second information regarding a time for an uplink channel associated with the first information (e.g., N 2 , N ai_indicator[_i], k2 (e.g., higher layer parameters), and a control unit that determines a time for the uplink channel based on the first information and the second information. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the time for the uplink channel is a physical uplink shared channel preparation time. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the time for the uplink channel is a slot offset between a physical downlink control channel and a physical uplink shared channel.
[0245] (Wireless Communication System) The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof.
[0246] 26 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 (which may be simply referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).
[0247] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.
[0248] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.
[0249] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).
[0250] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The location, number, shape, size, etc. of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as the base station 10.
[0251] The wireless communication system 1 may utilize multi-input multi-output (MIMO). For example, one cell may be formed by one antenna / base station 10, or may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a supercell) may be composed of multiple [virtual] cells (which may be called, for example, subcells). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell with a quasi-static / dynamically variable physical range. In this case, the wireless communication system 1 may be called a cell-free system.
[0252] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).
[0253] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.
[0254] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.
[0255] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 / Xn interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.
[0256] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.
[0257] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.
[0258] The user terminal 20 may be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.
[0259] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).
[0260] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.
[0261] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.
[0262] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), or the like may be used as an uplink channel.
[0263] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).
[0264] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.
[0265] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.
[0266] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.
[0267] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.
[0268] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.
[0269] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.
[0270] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.
[0271] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.
[0272] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).
[0273] 27 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.
[0274] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.
[0275] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.
[0276] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.
[0277] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.
[0278] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, the RF unit 122, and a measurement unit 123.
[0279] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.
[0280] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.
[0281] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.
[0282] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.
[0283] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
[0284] The transceiver unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.
[0285] On the other hand, the transceiver unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 130.
[0286] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.
[0287] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.
[0288] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.
[0289] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.
[0290] The base station 10 may be separated into three elements: a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may implement higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement the functions of the PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer.
[0291] In the present disclosure, the base station 10 may include a single device that realizes all of the functions of the RU, DU, and CU, or may include multiple devices that each realize some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.
[0292] The transceiver 120 may transmit first information indicating a waveform conversion-related function and second information relating to a time for a downlink channel associated with the first information to the user terminal 20. The control unit 110 may control scheduling for the user terminal 20, taking into consideration the time for the downlink channel determined based on the first information and the second information.
[0293] Furthermore, the transceiver unit 120 may transmit first information indicating a waveform conversion-related function and second information related to a time for an uplink channel associated with the first information to the user terminal 20. The control unit 110 may control scheduling for the user terminal 20, taking into consideration the time for the uplink channel determined based on the first information and the second information.
[0294] (User terminal) Fig. 28 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.
[0295] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.
[0296] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.
[0297] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals and transfer them to the transceiver unit 220.
[0298] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.
[0299] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.
[0300] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.
[0301] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.
[0302] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.
[0303] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.
[0304] The transmitter / receiver unit 220 (transmission processing unit 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
[0305] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.
[0306] The transceiver unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.
[0307] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 230.
[0308] The transceiver unit 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.
[0309] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.
[0310] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.
[0311] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.
[0312] The transceiver 220 receives first information (e.g., AI indicator) indicating a waveform conversion-related function and second information (e.g., N 1 , N ai_indicator[_i] , N pdsch , k0, k1, etc. (higher layer parameters, etc.), and the control unit 210 may determine the time for the downlink channel based on the first information and the second information.
[0313] The time for the downlink channel may be a physical downlink shared channel processing time.
[0314] The time for the downlink channel may be a physical downlink shared channel reception preparation time.
[0315] The time for the downlink channel may be a slot offset between the physical downlink control channel and the physical downlink shared channel.
[0316] The time for the downlink channel may be a slot offset between a physical downlink shared channel and an acknowledgement message corresponding to the physical downlink shared channel.
[0317] The transceiver 220 also receives first information indicating a waveform conversion-related function (e.g., an AI indicator) and second information relating to a time for an uplink channel associated with the first information (e.g., N 2 , N ai_indicator[_i] , k2, etc. (higher layer parameters, etc.), and the control unit 210 may determine the time for the uplink channel based on the first information and the second information.
[0318] The time for the uplink channel may be a physical uplink shared channel preparation time.
[0319] The time for the uplink channel may be a slot offset between the physical downlink control channel and the physical uplink shared channel.
[0320] (Hardware Configuration) Note that the block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.
[0321] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.
[0322] For example, a base station, a user terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 29 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
[0323] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.
[0324] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.
[0325] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading specified software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.
[0326] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.
[0327] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.
[0328] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.
[0329] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.
[0330] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.
[0331] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).
[0332] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
[0333] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.
[0334] In addition, the devices included in the core network 30 (for example, network nodes that provide NF) may also be realized by the above-mentioned functional block / hardware configuration.
[0335] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.
[0336] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.
[0337] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.
[0338] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may also be a time unit based on numerology.
[0339] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.
[0340] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.
[0341] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.
[0342] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.
[0343] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
[0344] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.
[0345] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
[0346] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.
[0347] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.
[0348] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.
[0349] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.
[0350] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.
[0351] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.
[0352] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). One or more BWPs may be configured for a UE within one carrier.
[0353] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."
[0354] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.
[0355] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by a predetermined index.
[0356] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.
[0357] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0358] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.
[0359] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.
[0360] With respect to any information (e.g., variables, constants, parameters) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE / base station) may notify any second device (e.g., base station / UE) of information indicating / specifying (or relating to) the value of the any information.
[0361] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.
[0362] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).
[0363] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).
[0364] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values (e.g., comparison with a predetermined value).
[0365] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0366] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.
[0367] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).
[0368] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.
[0369] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.
[0370] The group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.
[0371] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.
[0372] In addition, in the present disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.
[0373] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.
[0374] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.
[0375] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.
[0376] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.
[0377] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of a base station and / or base station subsystem that provides communication service within that coverage.
[0378] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.
[0379] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.
[0380] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
[0381] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.
[0382] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.
[0383] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.
[0384] 30 is a diagram showing an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.
[0385] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by a user.
[0386] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).
[0387] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.
[0388] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.
[0389] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.
[0390] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.
[0391] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.
[0392] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).
[0393] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.
[0394] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).
[0395] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided in the vehicle 40.
[0396] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as an uplink channel and a downlink channel may be read as a sidelink channel.
[0397] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.
[0398] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.
[0399] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.
[0400] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).
[0401] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
[0402] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.
[0403] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.
[0404] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.
[0405] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.
[0406] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."
[0407] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ..." or "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ..." or "does not ... (if the above "..." is a to-infinitive, a verb with "to")," etc. Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).
[0408] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.
[0409] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."
[0410] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.
[0411] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."
[0412] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.
[0413] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0414] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").
[0415] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.
[0416] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.
[0417] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.
[0418] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.
Claims
1. A terminal having a receiver that receives first information indicating a waveform conversion-related function and second information regarding a time for a downlink channel associated with the first information; and a controller that determines the time for the downlink channel based on the first information and the second information.
2. The terminal according to claim 1, wherein the time for the downlink channel is a physical downlink shared channel processing time.
3. The terminal according to claim 1, wherein the time for the downlink channel is a physical downlink shared channel reception preparation time.
4. The terminal of claim 1, wherein the time for the downlink channel is a slot offset between a physical downlink control channel and a physical downlink shared channel.
5. The terminal according to claim 1, wherein the time for the downlink channel is a slot offset between a physical downlink shared channel and acknowledgement information corresponding to the physical downlink shared channel.
6. A wireless communication method for a terminal, comprising: receiving first information indicating a waveform conversion-related function and second information relating to a time for a downlink channel associated with the first information; and determining the time for the downlink channel based on the first information and the second information.
7. A base station having: a transmitting unit that transmits to a terminal first information indicating a waveform conversion-related function and second information regarding a time for a downlink channel associated with the first information; and a control unit that controls scheduling for the terminal, taking into account the time for the downlink channel determined based on the first information and the second information.
Citation Information
Patent Citations
Method and device for transmitting / receiving signal in wireless communication system
US20220353879A1
Terminal, wireless communication method and base station
WO2023012954A1