Terminal and communication method

Abstract

To provide a terminal and a communication method for early indicating to a base station (gNB) a function newly introduced in repetition of Msg3 of an SBFD (subband non-overlapping full duplex) symbol.SOLUTION: In a mobile communication system, a terminal 200 that performs communication with a base station using a first time unit in which downlink and uplink can be simultaneously used by a plurality of subbands constituting a time division duplex band and a second time unit in which one of downlink and uplink can be used by applying a time division duplex band includes: a control part that sets a random access opportunity in the first time unit; and a transmission part configured to transmit a first message and a third message of a random access procedure using a random access opportunity. The control part generates control information indicating whether to support repetition of the third message in the first time unit, and the transmission part transmits the control information to the base station.SELECTED DRAWING: Figure 20

Description

[Technical Field]

[0001] The present disclosure relates to a terminal and a communication method. [Background technology]

[0002] 3GPP (registered trademark) has established specifications for the 5th generation mobile communication system (also known as 5G, New Radio (NR) or Next Generation (NG)), and is also working on specifications for the next generation mobile communication system, known as Beyond 5G, 5G Evolution, or 6G.

[0003] Release 18 discusses a duplexing scheme that enables simultaneous use of the downlink (DL) and uplink (UL) by utilizing multiple subbands that make up a time division duplexing (TDD) band. This duplexing scheme is called subband non-overlapping full duplex (SBFD). Note that symbols to which SBFD is applied may also be called SBFD symbols. In addition, in SBFD symbols, subbands used for DL ​​may also be called DL subbands, and subbands used for UL may also be called UL subbands.

[0004] Furthermore, support for random access (RA) in SBFD is being considered for Release 19 (Non-Patent Document 1). Specifically, it is being considered to extend communication related to a random access channel (RACH) (hereinafter referred to as "RACH communication") to SBFD symbols.

[0005] In addition, the terminal (hereinafter also referred to as "user equipment (UE)") determines a random access opportunity (RO) for transmitting a preamble that starts an RA based on RACH communication from the base station (hereinafter also referred to as "gNodeB (gNB)"), and further determines a valid RO from among the ROs.

[0006] There are two types of UE: "SBFD-aware UE" that supports SBFD operation and "legacy UE" that does not. There are also two types of RO: "legacy-RO" and "additional-RO". SBFD-aware UE can send preambles using both legacy-RO and additional-RO. On the other hand, legacy UE cannot use additional-RO and can only send preambles using legacy-RO. [Prior art documents] [Non-patent literature]

[0007] [Non-Patent Document 1] “New WID: Evolution of NR duplex operation: Sub-band full duplex (SBFD)”, RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 11-15, 2023 [Non-patent document 2] 3GPP TS 38.321 V18.6.0 (2025-06) [Non-patent document 3] 3GPP TS 38.300 V18.6.0 (2025-06) [Non-patent document 4] 3GPP TS 38.213 V19.0.0 (2025-06) [Non-Patent Document 5] 3GPP TS 38.331 V18.6.0 (2025-06) Summary of the Invention

[0008] At the 3GPP meeting, there was discussion about whether to introduce a new FG (Future Group) to the repetition of Msg3 (third message) of the random access procedure in the SBFD symbol.

[0009] If a new feature for Msg3 repetition in SBFD symbols is introduced, the UE needs to indicate this new feature to the gNB early on. Without notification of this new feature, the gNB cannot distinguish between UEs that support Msg3 repetition in SBFD symbols and UEs that only support Msg3 repetition in non-SBFD symbols.

[0010] This may result in the gNB not being able to schedule the repetition of Msg3 with the correct symbol type, and the gNB and the UE may have different understanding of the slots available for the repetition of Msg3.

[0011] One aspect of the present disclosure contributes to providing a terminal that can quickly indicate to a gNB the newly introduced functionality of repetition of Msg3 in the SBFD symbol.

[0012] A terminal according to one embodiment of the present disclosure communicates with a base station using a first time unit in which the downlink and the uplink can be used simultaneously using multiple subbands that make up a time division duplex band, and a second time unit in which either the downlink or the uplink can be used by applying the time division duplex band, and includes: a control unit that sets a random access opportunity in the first time unit; and a transmission unit that uses the random access opportunity to transmit a first message and a third message of a random access procedure, wherein the control unit generates control information indicating whether or not to support repetition of the third message in the first time unit, and the transmission unit transmits the control information to the base station. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a diagram illustrating an overall schematic configuration of a wireless communication system. [Figure 2] FIG. 1 illustrates frequency ranges used in wireless communication systems. [Figure 3] 1A to 1C are diagrams illustrating examples of the configuration of radio frames, subframes, slots, and symbols used in a radio communication system. [Figure 4A] FIG. 1 is a diagram illustrating an example of TDD settings defined up to Rel-16. [Figure 4B] FIG. 1 is a diagram illustrating an example of the configuration of SBFD. [Figure 5] FIG. 10 is a diagram illustrating an example of SBFD operation. [Figure 6A] FIG. 1 illustrates an example of an existing TDD configuration. [Figure 6B] A diagram showing an example of TDD including SBFD configuration. [Figure 7] FIG. 10 is a sequence diagram illustrating an example of a CBRA procedure. [Figure 8] FIG. 10 is a sequence diagram illustrating another example of the CBRA procedure. [Figure 9] FIG. 10 is a sequence diagram illustrating an example of a CFRA procedure. [Figure 10] A diagram showing examples of RACH configuration options. [Figure 11A] FIG. 1 is a diagram illustrating Configuration 1. [Figure 11B] FIG. 10 is a diagram illustrating configuration 2. [Figure 12] Diagram showing IE RACH-ConfigCommon [Figure 13] Diagram showing IE FeatureCombinationPreambles [Figure 14] Diagram showing IE featureCombination [Figure 15] Table showing PRACH Mask index values [Figure 16] FIG. 1 shows an example of Proposal 1 in the present disclosure. [Figure 17] FIG. 1 shows an example of Proposal 2 in the present disclosure. [Figure 18] FIG. 10 is a diagram showing an example of Proposal 3 in the present disclosure. [Figure 19] FIG. 2 is a block diagram showing an example of the configuration of a base station according to the present embodiment. [Figure 20] FIG. 2 is a block diagram showing an example of the configuration of a UE according to the present embodiment. [Figure 21] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0015] <Wireless communication system configuration> 1 is a wireless communication system conforming to a scheme called 5G. Alternatively, the wireless communication system 10 may be a wireless communication system conforming to a scheme called Beyond 5G, 5G Evolution, or 6G.

[0016] The wireless communication system 10 can support Massive Multiple-Input Multiple-Output (Massive MIMO), which generates more directional beams by controlling wireless signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses multiple component carriers (CCs) by bundling them together, and Dual Connectivity (DC), which communicates with two base stations simultaneously. In this specification, "and / or" may be simply written as " / ".

[0017] As shown in FIG. 1, a wireless communication system 10 includes a base station 100 (hereinafter also referred to as a gNodeB (gNB) 100) constituting a Next Generation-Radio Access Network (NG-RAN) 20, and a terminal 200 (hereinafter also referred to as a user equipment (UE) 200) that performs wireless communication with the gNB 100. The NG-RAN 20 is connected to a core network (CN) (not shown). The CN is composed of multiple network functions (NFs). The NFs are, for example, an access and mobility management function (AMF) and a network data analytics function (NWDAF). The AMF performs, for example, registration of the UE 200. The NWDAF performs, for example, optimization of the CN. Note that the specific configuration of the wireless communication system 10, for example, the number of gNBs 100 and UEs 200, is not limited to the example shown in FIG. 1. The NG-RAN 20 and the CN may be simply referred to as a "network."

[0018] The gNB100 may be a base station in a Centralized-Radio Access Network (C-RAN) configuration having a distributed unit (DU) having a function for connecting to the UE200 and a central unit (CU) having a function for connecting to the network. In this case, the gNB100 may be read as a DU, a CU, or a DU and a CU. When read as a DU, the gNB100 may be called a gNB-DU. When read as a CU, the gNB100 may be called a gNB-CU. When read as a DU and a CU, the DU portion may be called a gNB-DU and the CU portion may be called a gNB-CU.

[0019] Furthermore, the wireless communication system 10 may support a plurality of frequency ranges (FRs). That is, as shown in FIG. 2, the wireless communication system 10 may support the following FRs: FR1: 410MHz~7.125GHz FR3: 7.125GHz~24.25GHz FR2-1: 24.25GHz~52.6GHz FR2-2: 52.6GHz~71GHz

[0020] In FR1, a subcarrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz may be used, and in FR2-1, an SCS of 60 or 120 kHz (or 240 kHz) and a BW of 50 to 400 MHz may be used.

[0021] Note that SCS may be interpreted as numerology, which is defined in §5.1 of Non-Patent Document 3 and corresponds to one subcarrier interval in the frequency domain.

[0022] In FR2-2, to avoid an increase in phase noise, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) or Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with a larger SCS may be applied.

[0023] Fig. 3 is a diagram showing an example of the configuration of a radio frame (system frame), subframe, and slot used in the radio communication system 10. As shown in Fig. 3, one slot is made up of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). However, the SCS is not limited to the interval (frequency) shown in Fig. 3. For example, 480 kHz, 960 kHz, etc. may be used as the SCS.

[0024] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, it may be 28 or 56 symbols, etc.) Furthermore, the number of slots per subframe may differ depending on the SCS.

[0025] The time direction (t) shown in Fig. 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.

[0026] The wireless communication system 10 may support coverage enhancement (CE) that expands the coverage of a cell (or physical channel) formed by the gNB 100. In coverage enhancement, a mechanism may be provided to increase the success rate of reception of various physical channels.

[0027] For example, UE200 receives information related to the random access procedure from gNB100 as a downlink (DL) signal (e.g., SIB1 (System Information Block Type 1) etc.).

[0028] Furthermore, for example, the UE 200 transmits a PRACH (physical random access channel) as an UL signal to the gNB 100 using a RACH (transmission) opportunity (RO: RACH Occasion), which is a resource for transmitting a random access preamble. For example, the UE 200 transmits the PRACH as an UL signal to the gNB 100.

[0029] The UL signal may include, for example, a UL data signal and control information. For example, the UL signal may include information related to the processing capability of the UE 200 (e.g., UE capability). The UL signal may also include a reference signal.

[0030] Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channels may include a Physical Uplink Shared Channel (PUSCH), and the control channels may include a Physical Uplink Control Channel (PUCCH). For example, the UE 200 transmits control information using the PUCCH and transmits UL data signals using the PUSCH. Note that the PUSCH is an example of an uplink shared channel, and the PUCCH is an example of an uplink control channel. The shared channels may also be called data channels.

[0031] The reference signal included in the UL signal may include at least one of, for example, a Demodulation Reference Signal (DMRS), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for positioning information. For example, reference signals such as the DMRS and PTRS are used to demodulate the UL data signal and are transmitted using the PUSCH.

[0032] Meanwhile, in response to the operation of UE200, gNB100 transmits information related to the RACH procedure to UE200 as a DL signal (e.g., SIB1, etc.).

[0033] Furthermore, for example, the gNB 100 receives a PRACH as an UL signal from the UE 200. For example, the gNB 100 receives a PRACH as an UL signal from the UE 200.

[0034] The channels used for transmitting DL signals include, for example, data channels and control channels. For example, the data channel may include a Physical Downlink Shared Channel (PDSCH), and the control channel may include a Physical Downlink Control Channel (PDCCH). For example, gNB100 transmits control information to UE200 using PDCCH and transmits DL data signals using PDSCH. Note that PDSCH is an example of a downlink shared channel, and PDCCH is an example of a downlink control channel. Note that PDCCH may be rewritten with downlink control information (DCI) transmitted in PDCCH, control information, etc.

[0035] The reference signals included in the DL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRSRS, and PRS for position information. For example, reference signals such as DMRS and PTRS are used for demodulating DL data signals and are transmitted using PDSCH.

[0036] Next, SBFD, CG (Configured Grant), codebook-based uplink transmission, non-codebook-based uplink transmission, and mTRP will be described.

[0037] <SBFD operation> Considering the time ratio of transmission and reception (e.g., DL:UL=4:1) using Time Division Duplex (TDD) up to Rel-16, there may be cases where the number of transmission opportunities for UL signals / channels is fewer than the number of reception opportunities for DL ​​signals / channels. In such cases, UE 200 cannot transmit UL signals / channels frequently, which raises concerns about transmission delays of important UL signals / channels. Furthermore, since there are fewer UL transmission opportunities compared to DL reception opportunities, there is also concern about signal / channel congestion during UL transmission opportunities. Furthermore, with TDD, the time resources available for transmitting UL signals / channels are limited, which limits the application of UL coverage extension techniques, for example, through transmission.

[0038] In future wireless communication systems (for example, Rel-18 and later), the introduction of a time-frequency division duplexing method that combines TDD and frequency division duplexing (FDD) for UL and DL is being considered.

[0039] Examples of the time-frequency division duplexing method include XDD (Cross Division Duplex) and Subband Non-Overlapping Full Duplex (SBFD). XDD or SBFD may refer to a duplexing method that frequency-division multiplexes DL and UL within one component carrier (CC) in the TDD band (allowing DL and UL to be used simultaneously).

[0040] Figure 4A is a diagram showing an example of the TDD configuration defined up to Rel-16. In the example shown in Figure 4A, TDD slots or symbols are configured for a UE in a bandwidth such as one component carrier (CC) (which may also be called a cell or serving cell) or bandwidth portion (BWP).

[0041] In the example shown in Figure 4A, the time ratio of DL slots to UL slots is 4:1. This conventional TDD slot or symbol configuration does not ensure sufficient UL time resources, which can result in UL transmission delays and reduced coverage performance.

[0042] Fig. 4B is a diagram showing an example of the configuration of SBFD. In the example shown in Fig. 4B, within one component carrier (CC), resources used for DL ​​reception and resources used for UL transmission overlap in time. With such a resource configuration, more UL resources can be secured, thereby improving resource utilization efficiency.

[0043] For example, as shown in the example of Figure 4B, both ends of the frequency domain may be set as DL resources, and UL resources may be sandwiched between these DL resources. This may prevent or mitigate cross link interference (CLI) with neighboring carriers. Also, a guard region may be set at the boundary between the DL resources and the UL resources.

[0044] Considering the complexity of handling self-interference, it may be considered that only the gNB 100 uses the DL resource and the UL resource simultaneously. That is, in radio resources where the DL and UL overlap in time, one UE 200 may use the DL resource and another UE 200 may use the UL resource.

[0045] Fig. 5 is a diagram showing an example of SBFD operation. In the example shown in Fig. 5, some of the DL resources of the TDD band are configured as UL resources, and the DL and UL are configured to partially overlap in the time domain.

[0046] In the example shown in FIG. 5, during the DL-only period, each of the multiple UEs 200 (UE1 and UE2 in FIG. 5) receives the DL channel / signal.

[0047] Furthermore, during a period in which DL and UL overlap in time, one UE 200 (UE1 in the example of FIG. 5) receives a DL channel / signal, and another UE 200 (UE2 in the example of FIG. 5) transmits a UL channel / signal. During this period, the gNB 100 performs simultaneous transmission and reception of DL and UL.

[0048] Furthermore, during the UL-only period, each of the multiple UEs 200 (UE1 and UE2 in FIG. 5) transmits a UL channel / signal.

[0049] In existing NR (e.g., those defined up to Rel-15 / 16 / 17), DL frequency resources and UL frequency resources in a UE carrier are configured as DL BWP and UL BWP, respectively. To switch DL / UL frequency resources to other DL / UL frequency resources, multiple BWP configurations and a BWP adaptation mechanism are required.

[0050] Figure 6A is a diagram showing an example of an existing TDD configuration. In Figure 6A, slots / symbols marked with "D" are DL slots / symbols, slots / symbols marked with "U" are UL slots / symbols, and slots / symbols marked with "F" are flexible (hereinafter also referred to as FL) slots / symbols. Note that similar notations may be used in the following figures.

[0051] In the existing NR, as shown in FIG. 6A, time resources (time units such as symbols and slots) in the TDD carrier for UE 200 are configured as at least one of DL, UL, and flexible (FL) in the TDD configuration.

[0052] Figure 6B is a diagram showing an example of an existing TDD configuration. In Figure 6B, slots / symbols or subbands marked with "D" are DL slots / symbols or DL ​​subbands, and slots / symbols or subbands marked with "U" are UL slots / symbols or UL subbands. Note that similar notations may be used in the following figures.

[0053] As shown in FIG. 6B , the SBFD symbol may be a symbol that is signaled or configured as UL (or DL) or for UL transmission (or DL ​​reception) on some frequency resources (subbands), and signaled or configured as DL (or UL) or for DL ​​reception (or UL transmission) on other frequency resources (subbands). Alternatively, the SBFD symbol may be a symbol that is signaled or configured as UL (or DL) or for UL transmission (or DL ​​reception) on a portion of frequency resources. Alternatively, the SBFD symbol may be a symbol that is signaled or configured as DL (or UL) or for DL ​​reception (or UL transmission) on a portion of frequency resources.

[0054] Here, the time unit may be at the symbol level, slot / subslot level, or a group of symbols / slots / subslots, i.e., the SBFD time unit may be an SBFD symbol, a slot / subslot containing or overlapping an SBFD symbol, or a group of symbols / slots / subslots containing or overlapping an SBFD symbol.

[0055] A pure time unit may be a non-SBFD symbol (i.e., a symbol that is not an SBFD symbol, also called a non-SBFD symbol), a slot / sub-slot that does not contain or overlap an SBFD symbol, or a group of symbols / slots / sub-slots that do not contain or overlap an SBFD symbol, and may also be called a non-SBFD time unit.

[0056] As described above, SBFD may be applied to each slot / symbol. Note that each slot / symbol may be set to DL, UL, or Flexible (FL) that can be used as DL or UL, and then SBFD may be applied.

[0057] SBFD is a type of (full-duplex) duplexing scheme based on time division duplexing (TDD), enabling simultaneous use of multiple sub-bands that make up the TDD band. SBFD can be described as a duplexing scheme in which multiple sub-bands are specified within the TDD band, a duplexing scheme in which UL and DL are allocated non-overlapping in the frequency direction in the TDD time unit, or a duplexing scheme in which all two sub-bands are overlapped.

[0058] A symbol to which SBFD is applied is also called an SBFD symbol. "SBFD is applied" may be interpreted as SBFD being applied to at least a part of scheduling. In other words, a "symbol to which SBFD is applied" may be interpreted as a symbol to which SBFD is applied (SBFD symbol) in scheduling to which SBFD is applied. Also, a "time unit to which non-SBFD is applied" may be interpreted as a symbol to which SBFD is not applied (non-SBFD symbol) in scheduling to which SBFD is applied.

[0059] Furthermore, a UE that supports SBFD operation (SBFD-compatible UE) is referred to as an SBFD-aware UE or an SBFD-capable UE, and a UE that does not support SBFD operation is referred to as a legacy UE. For example, when SBFD is applied to a DL symbol, an SBFD-aware UE can recognize the UL subband (and DL subband) in this SBFD symbol. On the other hand, a legacy UE cannot recognize the UL subband in this SBFD symbol and recognizes it as a normal DL symbol.

[0060] <Random access procedure> NR random access procedures are performed for various purposes, such as initial access, recovery from beam interference, and handover. Random access procedures include a contention-based random access (CBRA) procedure, which is a contention-based random access procedure, and a contention-free random access (CFRA) procedure, which is a contention-free random access procedure. Since the CBRA procedure is initiated autonomously by the UE 200, collisions may occur when multiple UEs 200 simultaneously initiate the random access procedure. On the other hand, the CFRA procedure allows the gNB 100 to instruct the connected UE 200 to execute the random access procedure in a manner that prevents collisions from occurring among the multiple UEs 200.

[0061] In NR, a random access procedure may be performed by selecting an SSB (SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) Block) or by selecting a CSI-RS. The SSB may be referred to as a synchronization signal, and the CSI-RS may be referred to as a reference signal.

[0062] FIG. 7 is a sequence diagram illustrating an example of a CBRA procedure.

[0063] For example, the gNB100 transmits an SSB for each beam, and the UE200 monitors the SSB of each beam. The UE200 selects an SSB from the multiple SSBs whose received power (RSRP: Reference Signal Received Power) is greater than (or equal to or greater than) a threshold, and transmits a random access preamble to the gNB100 via a PRACH using an RO associated with (corresponding to) the selected SSB (step S101). The random access preamble (RA Preamble) may be referred to as a preamble, a PRACH preamble (RRACH Preamble), a message 1 (Message 1), Msg1, or the like, as appropriate.

[0064] The gNB 100 transmits a response message to the Msg1 as a second message to the UE 200 via the PDSCH (step S102). The response message (second message) may be appropriately referred to as a Random Access Response (RAR), an RA Response, Message 2, Msg2, or the like. After transmitting the Msg1, the UE 200 may monitor the PDCCH used for scheduling the PDSCH including the Msg2. The Msg2 may include an uplink grant (UL grant) (RAR uplink grant) used for scheduling the PUSCH including the third message transmitted by the UE 200.

[0065] The UE 200 transmits the PUSCH scheduled by the RAR uplink grant as a third message (step S103). For example, the UE 200 transmits a Radio Resource Control (RRC) connection request, an RRC connection re-establishment request, or the like to the gNB 100 via the PUSCH. The third message may be referred to as a Message 3, Msg 3, an RRC Connection Request, or the like, as appropriate.

[0066] The gNB 100 transmits a contention resolution message as a fourth message via the PDSCH (step S104). The contention resolution message (fourth message) may be referred to as Message 4, Msg4, or the like as appropriate. After transmitting Msg3, the UE 200 may monitor the PDCCH used for scheduling the PDSCH including Msg4. Msg4 may include a contention resolution ID (UE contention resolution ID). The contention resolution ID may be used to resolve contention between multiple UEs 200 transmitting signals using the same radio resources. If the contention resolution ID included in the Msg4 received by the UE 200 has the same value as an ID for identifying the UE 200, the UE 200 may determine that contention resolution is successful and set a value of a Temporary Cell-Radio Network Temporary Identifier (C-RNTI) in a Cell-Radio Network Temporary Identifier (C-RNTI) field. When the value of C-RNTI is set in the C-RNTI field, the UE 200 may consider the RRC connection to be completed. Msg4 may be referred to as RRC Connection Setup, etc.

[0067] After the RRC connection is completed, the UE 200 may transmit an Ack (Acknowledgement) via a PUCCH (PUCCH resource) indicated by a PUCCH resource indication field included in the PDCCH that scheduled the Msg4, in order to notify the gNB 100 that the RRC connection has been completed. After the RRC connection is established, the UE 200 may transmit UE capability to the gNB 100. The above-described random access procedure may be referred to as a Type 1 RACH procedure, a 4-step RACH procedure, Type 1 RACH, 4-step RACH, etc.

[0068] FIG. 8 is a sequence diagram illustrating another example of the CBRA procedure.

[0069] The UE 200 transmits a message including an RA preamble and data to the gNB 100 (step S201). As an example, the UE 200 selects an RO in the same manner as selecting an RO in a 4-step RACH procedure, and transmits an RA preamble on the RO and transmits data on a PUSCH resource associated with the RO. This message may be appropriately referred to as Message A, MsgA, etc. Note that the RA preamble and data here may correspond to Msg1 and Msg3 in the 4-step RACH procedure, respectively. MsgA includes one RA preamble (referred to as MsgA PRACH) and one piece of data (referred to as MsgA PUSCH), and the MsgA PRACH and MsgA PUSCH are time-division multiplexed and transmitted. More specifically, the MsgA PRACH is one preamble with one preamble index in an MsgA RACH occasion (RO: RACH occasion), and the MsgA PUSCH is one PUSCH with one PUSCH resource unit (PRU: PUSCH resource unit) in an MsgA PUSCH occasion (PO: PUSCH occasion) according to the MsgA PUSCH configuration. Note that in this procedure, resources for transmitting data are not limited to PUSCH resources, and may be resources of any channel for transmitting data (or control information).

[0070] The gNB 100 transmits the response message to the UE 200 as a second message (step S202). This response message (second message) may be referred to as Message B, MsgB, or the like as appropriate. The content included in Message B may correspond to Msg2 and Msg4 in a 4-step RACH procedure, for example. MsgB includes one PDSCH (and one PDCCH for scheduling the PDSCH). From the perspective of the physical layer, the content of Msg2 and Msg4 is simply integrated into MsgB.

[0071] The UE 200, whose RRC connection has been completed, may transmit an Ack via a PUCCH (PUCCH resource) to notify the gNB 100 that the RRC connection has been completed. After the RRC connection is established, the UE 200 may transmit UE capability to the gNB 100. The above-described random access procedure may be referred to as a Type 2 RACH procedure, a 2-step RACH procedure, a Type 2 RACH, a 2-step RACH, or the like. The 2-step RACH is supported to shorten the RACH delay.

[0072] FIG. 9 is a sequence diagram illustrating an example of the CFRA procedure.

[0073] The UE 200 is requested to transmit an RA preamble (Msg1) from the gNB 100. Here, the gNB 100 allocates the RA preamble (Msg1) via dedicated signaling (step S301). The PDCCH for such dedicated signaling may be referred to as a PDCCH order. The UE 200 may monitor the PDCCH (PDCCH order) to perform resource allocation for Msg1.

[0074] UE200 transmits the above-mentioned Msg1 to gNB100 (step S302).

[0075] The gNB100 transmits the above-mentioned Msg2 to the UE200 (step S303). After the RRC connection is completed, the UE200 may transmit an Ack via the PUCCH (PUCCH resource) to notify the gNB100 that the RRC connection has been completed. After the RRC connection is established, the UE200 may transmit a UE capability to the gNB100.

[0076] In this embodiment, in order to extend coverage in a random access procedure, UE 200 may repeatedly transmit Msg1 (and therefore PRACH) in, for example, the above-described 4-step RACH procedure shown in Fig. 7 and the CFRA procedure shown in Fig. 9. However, in the present disclosure, Msg1 (and therefore PRACH) may also be repeatedly transmitted in the above-described 2-step RACH procedure shown in Fig. 8.

[0077] In the above-described random access, the UE determines a random access opportunity for transmitting a preamble for starting the random access, and determines a valid RO (and an invalid RO) from the determined ROs. Note that the random access opportunity may also be referred to as a RACH Occasion.

[0078] Next, a description will be given of power control of PRACH and Msg3 transmitted by UE 200 in the random access procedure shown in Fig. 7, and of MsgA transmitted by UE 200 in the random access procedure shown in Fig. 8. Note that Msg3 and MsgA are transmitted in PUSCHs, respectively, and therefore may be referred to as Msg3 PUSCH and MsgA PUSCH.

[0079] <Terminology> The following explains the definitions of terms related to SBFD.

[0080] SBFD symbol: Symbol set in SBFD sub-band Non-SBFD symbols: Symbols that are not configured in the SBFD sub-bands DL (or semi-static D) symbol: A symbol indicated as DL by t-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigDedicated UL (or semi-static U) symbol: A symbol designated as UL by tdd-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigDedicated Flexible (or Semi-Static F, or Flexible) Symbol: A symbol designated as flexible by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigDedicated SBFD DL symbol: A symbol indicated as downlink (DL) by the tdd-UL-DL-Configuration Common and / or tdd-UL-DL-Configuration Dedicated, in which the SBFD subband is configured SBFD Flexible (FL) Symbol: A symbol indicated as flexible by the tdd-UL-DL-Configuration Common and / or tdd-UL-DL-Configuration Dedicated, in which SBFD sub-bands are configured.

[0081] <Notation> "Legacy-RO" represents a valid RO in a UL symbol or FL symbol set by the legacy RACH configuration based on the legacy-RO validation rules.

[0082] 「additional-RO」 represents the valid RO set by the legacy PRACH configuration within the SBFD DL symbol, or the valid RO set across the entire SBFD DL symbol and SBFD FL symbol, when the additional PRACH configuration for SBFD is not set. When the additional PRACH configuration for SBFD is set, it represents the valid RO within the SBFD symbol set by the additional PRACH configuration for SBFD.

[0083] <Random Access Procedure in SBFD Symbol> Clause 8 of Non-Patent Document 4 stipulates the random access procedure in the SBFD symbol.

[0084] (8. Random Access Procedure) Before the start of the physical random access procedure, Layer 1 receives a set of SS / PBCH block indexes from the upper layer and provides the upper layer with a set of corresponding RSRP (Reference Signal Received Power) measurement results.

[0085] Before the start of the physical random access procedure, Layer 1 may receive an instruction from the upper layer to execute the Type-1 random access procedure described in Sections 8.1 to 8.4, or the Type-2 random access procedure described in Sections 8.1 to 8.2A.

[0086] In the remaining descriptions of this section, if a symbol is not explicitly stated to be an SBFD symbol, then that symbol is a non-SBFD symbol.

[0087] Before the start of the physical random access procedure, Layer 1 may receive an instruction from the upper layer to execute the random access procedure using any of the following: First PRACH occasions: Each occasion is indicated as uplink or flexible by tdd-UL-DL-ConfigurationCommon and contains only symbols considered to be uplink for the random access procedure. - second PRACH occasions: located on Resource Blocks (RBs) within the active UL BWP and within the UL subband, and associated with either: (case 1) only SBFD symbols with at least one SBFD symbol indicated as downlink by tdd-UL-DL-ConfigurationCommon, if the UE is provided with sbfd-RACHSingleConfig or sbfd-RACHDualConfig, or (case 2) starting with an SBFD symbol and ending with a non-SBFD symbol, if the UE is provided with sbfd-RACHDualConfig and sbfd-RACHDualConfig-ValidROAcrossSymbolTypes.

[0088] The procedures specified in section 8.1 are applied separately for the first and second PRACH occasions, with only the Type-1 random access procedure applicable to the second PRACH occasion.

[0089] It should be noted that "legacy-RO" corresponds to "first PRACH occasions" in §8 of Non-Patent Document 4.

[0090] The "additional-RO" in the present disclosure corresponds to "second PRACH occasions" in section 8 of Non-Patent Document 4.

[0091] The above-mentioned specifications may be further updated by a Change Request (CR).

[0092] <Agreement 1> At the 3GPP RAN1#116 meeting, two options (Option 1 and Option 2) were considered for determining valid ROs within SBFD symbols for random access operations of SBFD-aware UEs in the RRC CONNECTED state. Option 1: Use one single PRACH configuration with possible extensions. Option 2: Use two separate RACH configurations, including one legacy RACH configuration and one additional PRACH configuration.

[0093] In Option 1, RO in the UL subband within the SBFD symbol may be valid for SBFD-aware UEs.

[0094] In Option 2, RO in UL subbands within SBFD symbols configured by the additional PRACH configuration may be valid for SBFD-aware UEs.

[0095] Fig. 10 is a diagram showing examples of RACH configuration options. Fig. 10 shows examples of RACH configurations for each of two options. The horizontal axis of each option in Fig. 10 indicates the time axis, and the vertical axis indicates the frequency axis. Each option in Fig. 10 indicates the RO set for SBFD symbols and non-SBFD symbols. In Fig. 10, "DL" indicates the DL subband of an SBFD DL symbol or the DL symbol of a non-SBFD symbol, "UL" indicates the UL subband of an SBFD DL symbol or the UL symbol of a non-SBFD symbol, and "F" indicates the FL symbol of a non-SBFD symbol.

[0096] As shown in Fig. 10, the ROs for SBFD symbols and non-SBFD symbols are both configured according to the legacy RACH configuration in Option 1. As shown in Fig. 10, in Option 2, the ROs for SBFD symbols are configured as additional-ROs according to the additional RACH configuration, and the ROs for non-SBFD symbols are configured as legacy-ROs according to the legacy RACH configuration.

[0097] <Agreement 2> At the 3GPP RAN1#118 meeting, it was agreed that the above Option 1 (with Alt 1-1) and Option 2 would be supported.

[0098] Specifically, for an SBFD-aware UE in RRC CONNECTED state, both RACH configuration Option 1 and Alt 1-1 (i.e., using one RACH configuration and based only on the existing parameters of that single RACH configuration) and RACH configuration Option 2 (i.e., using two separate RACH configurations, including one legacy RACH configuration and one additional RACH configuration) are supported.

[0099] Note that it is not supported to have both options enabled for a UE at the same time, and a UE is not required to support both options.

[0100] For the purposes of the RAN1 discussion, "additional-RO" is defined as follows: For RACH configuration Option 1, additional-RO includes RO within SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon and RO across SBFD symbols configured as downlink and flexible by tdd-UL-DL-ConfigurationCommon. For RACH configuration Option 2, additional-RO is the RO configured by the additional RACH configuration.

[0101] Regarding RO validation for RACH configuration Option 1 using Alt 1-1, RO between SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon and SBFD symbols configured as flexible is treated the same as RO within SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon. ·RO contains at least one DL symbol configured according to tdd-UL-DL-ConfigurationCommon.

[0102] That is, for each option of the RACH configuration, "legacy-RO" and "additional-RO" are defined as follows:

[0103] [RACH configuration Option 1 with Alt 1-1 (i.e., single RACH configuration)] · legacy-RO: RO that is valid as a legacy (including RO in a UL symbol or an FL symbol) additional-RO: RO within the SBFD DL symbol, or RO spanning the SBFD DL symbol and the SBFD FL symbol

[0104] [RACH configuration Option 2 (i.e., additional RACH configuration for SBFD)] legacy-RO: Valid RO set by legacy RACH configuration additional-RO: RO in SBFD symbols set by additional RACH configuration

[0105] <Agreement 3> At the 3GPP RAN1#120 meeting, RO mask index configuration was discussed and the following agreement was reached:

[0106] For RACH configuration Option 1, the RO mask index configuration is selected from the following two alternatives: · Alt-1: The ssb-SharedRO-MaskIndex configuration is common to additional-RO and legacy-RO. · Alt-2: Separate ssb-SharedRO-MaskIndex configurations are used for additional-RO and legacy-RO.

[0107] <Agreement 4> At the 3GPP RAN1#117 meeting, it was agreed that whether transmission / reception in different slots is limited to one symbol type or is allowed in two symbol types is determined based on the configuration as follows:

[0108] For an SBFD-capable UE with UL transmissions and DL receptions spanning SBFD and non-SBFD symbols in different slots (each transmission / reception in a slot having either all SBFD symbols or all non-SBFD symbols), the SBFD-capable UE is provided with one of the following configurations: Configuration 1: Transmission / reception is restricted to either SBFD symbols only or non-SBFD symbols only (see Figure 11A). Configuration 2: Transmission / reception can occur in both SBFD and non-SBFD symbols (see Figure 11B).

[0109] The granularity of the settings (for example, per UE, per channel / signal, etc.) has not yet been determined. It is also unclear whether support for setting 2 depends on the UE capability.

[0110] In UL transmission / DL reception for one slot, SBFD symbols and non-SBFD symbols are never mixed in one occasion, and one of the symbol types is always used for each transmission / reception within the slot. However, in the case of UL transmission / DL reception where resources are periodically allocated in repetition spanning multiple slots or SPS or CG, an event may occur where some slots are transmitted using the SBFD symbol type and other slots are transmitted using non-SBFD symbols. In such cases, two options are supported: one option (Configuration 1) in which only one of the symbol types is enabled for the entire transmission / reception spanning multiple slots, and another option (Configuration 2) in which both symbol types can be mixed. Either configuration is configured for the terminal.

[0111] For example, when configuration 1 is set for a terminal, if repetition is set for SBFD symbols, repetition is valid only for SBFD symbols in that terminal, and when repetition is set for non-SBFD symbols, repetition is valid only for non-SBFD symbols in that terminal. When configuration 2 is set for a terminal, it becomes possible to use both SBFD symbols and non-SBFD symbols in repetition.

[0112] <Agreement 5> At the 3GPP RAN2#130 meeting, the following was agreed upon:

[0113] (MAC Open Project Agreement) In the case of L3 Handover (HO) and Beam Failure Recovery (BFR), CSI-RS based CFRA with SBFD RO is supported from the RAN2 perspective. A Liaison Statement (LS) is sent to RAN1 / 4 to inform this conclusion.

[0114] Fallback for the number of repetitions of Msg1 may be supported within the SBFD RO.

[0115] If both the RO type fallback and Msg1 repetition count fallback conditions are met, the UE should switch the RO type. In this case, the Msg1 repetition count after the RO type switch is unspecified (FFS).

[0116] In RACH fallback, when switching from one RO type to another, the UE is only allowed to switch to an RO type configured with the same capability combination.

[0117] The UE is allowed to switch to the configured RO type with the same Msg1 repetition count. The use of a larger Msg1 repetition count in case the same count is not available is unspecified.

[0118] (Other Agreements) When a fallback from CFRA to CBRA is performed, an SBFD-capable UE shall use the CBRA resource with the same RO type as indicated in the CFRA resource if a RACH resource for the same RO type is provided for the CBRA.

[0119] In PRACH configuration option 1, if a combination of features is configured using preamble splitting in RACH-ConfigCommon, a shared ssb-SharedRO-MaskIndex setting is used for additional-RO and legacy-RO.

[0120] In PRACH configuration option 1, the same featureCombinationPreamblesList configuration is used for both additional-RO and legacy-RO.

[0121] For RACH configuration option 1: Use a common featureCombinationPreamblesList for legacy-RO and additional-RO. -Apply the shared ssb-SharedRO-MaskIndex setting to additional-ROs and legacy-ROs.

[0122] <RA feature combination> Non-Patent Document 5 shows that FeatureCombinationPreambleList is included in the information element (IE) RACH-ConfigCommon (FIG. 12). Non-Patent Document 5 also shows that parameters such as featureCombination, startPreambleForThisPartition, and ssb-SharedRO-MaskIndex are set in FeatureCombinationPreambles in featureCombinationPreamblesList (FIG. 13).

[0123] The featureCombinationPreamble is an information element for a function that uses the RA preamble or random access opportunity (RO) to let the network know whether the UE supports a specific function before reporting the UE capability to the gNB.

[0124] As shown in Fig. 14, featureCombination indicates whether the UE can report whether it supports each function such as RedCap by transmitting a RACH based on the setting of featureCombinationPreamble. When transmitting a RACH, the UE transmits a RACH to the gNB based on the setting of featureCombinationPreamble, and the gNB can grasp the UE's capabilities (supported functions) set in featureCombination.

[0125] When a UE reports whether it supports a specific function by distinguishing preambles, the startPreambleForThisPartition parameter specifies the first preamble number that a UE that supports the specific function can use in a sequence of 64 preambles. For example, if startPreambleForThisPartition is set to "32", a UE that supports the specific function will use preambles from 32 to 63, and a UE that does not support the specific function will use preambles from 0 to 31.

[0126] When reporting whether a UE supports a specific function by distinguishing ROs, assuming that there are multiple ROs associated with a specific SSB, the ROs (Allowed PRACH occasion(s) of SSB) that a UE supporting the specific function can use to transmit a preamble are set in ssb-SharedRO-MaskIndex.

[0127] The meaning of each index value X of ssb-SharedRO-MaskIndex is shown in Table 7.4-1 of Non-Patent Document 2 (FIG. 15). · If X=0, a UE supporting the specific feature can use all ROs for transmitting preambles. · If X=1 to 8, UEs supporting the specific feature can use the RO with index X for transmitting the preamble. · If X=9, UEs supporting the specific feature can use ROs with even indices for preamble transmission. · When X=10, UEs supporting specific features can use ROs with odd indices for preamble transmission.

[0128] <Analysis> At the 3GPP meeting, there was discussion about whether to introduce a new FG to the repetition of Msg3 (third message) of the random access procedure in the SBFD symbol.

[0129] If a new feature for Msg3 repetition in SBFD symbols is introduced, the UE needs to indicate this new feature to the gNB early on. Without notification of this new feature, the gNB cannot distinguish between UEs that support Msg3 repetition in SBFD symbols and UEs that only support Msg3 repetition in non-SBFD symbols.

[0130] This may result in the gNB not being able to schedule the repetition of Msg3 with the correct symbol type, and the gNB and the UE may have different understanding of the slots available for the repetition of Msg3.

[0131] Therefore, in the <proposal> in this embodiment, we will explain a specific proposal for quickly indicating to the gNB the newly introduced function in the repetition of Msg3 of the SBFD symbol.

[0132] <Proposal 1> Proposal 1 proposes support for new functional combinations of repeating Msg3 in the SBFD symbol.

[0133] New possible values ​​are introduced for FeatureCombination to indicate whether the UE supports / is capable of or requires repetition of Msg3 on SBFD symbols (see Figure 16).

[0134] The UE uses FeatureCombination to notify the gNB of its support / capability or request for new features regarding the repetition of Msg3 of the SBFD symbol.

[0135] <Proposal 2> In Proposal 2, we propose the setting of RO masks corresponding to new function combinations.

[0136] (Case 1: RACH configuration option 1 (based on legacy-RO)) The RO mask setting for the new function combination is applied only to the additional-RO and not to the legacy-RO (see Figure 17).

[0137] (Case 2: RACH configuration option 2 (additional RACH configuration for SBFD)) The new function combination can only be configured in the additional RACH configuration for SBFD.

[0138] <Proposal 3> Proposal 3 proposes the selection of PRACH resources corresponding to new combinations of functions.

[0139] (Proposal 3-1) If the UE only supports Msg3 repetition in non-SBFD symbols and the RSRP of the downlink path loss reference is lower than the RSRP threshold for Msg3 repetition, the UE transmits the PRACH using the PRACH resources (including preamble and / or RO resources) indicated by the combination of legacy Msg3 repetition capabilities.

[0140] (Proposal 3-2) If the UE only supports Msg3 repetition in SBFD symbols and the RSRP of the downlink path loss reference is lower than the RSRP threshold for Msg3 repetition, the UE transmits PRACH using the PRACH resources indicated by the new feature combination.

[0141] (Proposal 3-3) If the UE supports Msg3 repetition in SBFD symbols and Msg3 repetition in both non-SBFD symbols and the RSRP of the downlink path loss reference is lower than the RSRP threshold for Msg3 repetition, one of the following options 1, 2 or 3 shall be applied.

[0142] (Option 1) If a repetition of Msg3 is required, the UE shall give priority to the PRACH resources indicated by the new feature combination for PRACH transmission.

[0143] (Example of option 1) If an additional-RO type is indicated by the network or selected based on the RSRP of SSB / CSI-RS, and the RSRP of the downlink path loss reference is lower than the RSRP threshold for Msg3 repetition, the UE transmits PRACH using the PRACH resources indicated by the new feature combination.

[0144] (Option 2) If Msg3 repetition is required, the UE determines the PRACH resource to use based on the symbol type preferred for Msg3 repetition indicated by the network.

[0145] For this reason, a new parameter is introduced to indicate the "symbol type preferred for Msg3 repetition" depending on the type of RACH configuration (i.e., RACH configuration option 1 (based on legacy-RO) or RACH configuration option 2 (additional RACH configuration for SBFD) as shown in Proposal 2).

[0146] (Example of option 2) If an additional-RO type is indicated by the network or selected based on the RSRP of SSB / CSI-RS, and the RSRP of the downlink path loss reference is lower than the RSRP threshold for Msg3 repetition, the UE may do one of the following: (1) If the network indicates that the SBFD symbol type should be prioritized over Msg3 repetition, the UE may transmit the PRACH using the PRACH resources (including preamble and / or RO resources) indicated by the new feature combination. (2) In cases other than (1) above, the UE may transmit PRACH on additional-RO using the PRACH resources indicated by the combination of the repetition function of the conventional Msg3, or option 3 below may be applied.

[0147] (Option 3) The UE determines whether to request repetition of Msg3 and the symbol type of repetition of Msg3 based on the RSRP threshold.

[0148] To select the symbol type for repeating Msg3, a new RSRP threshold is set depending on the type of RACH configuration (i.e., RACH configuration option 1 (based on legacy-RO) as shown in Proposal 2).

[0149] The UE may determine whether to request repetition and symbol type of Msg3 according to the new RSRP threshold (e.g., RSRP-2) and the conventional RSRP threshold for repetition of Msg3 (e.g., RSRP-1) as follows (see FIG. 18):

[0150] If the RSRP of SSB / CSI-RS is higher than (or not lower than) RSRP-1 and RSRP-2, the UE does not request a repetition of Msg3.

[0151] If the RSRP of SSB / CSI-RS is higher (or not lower) than either RSRP-1 or RSRP-2 and lower (or not higher) than the other, the UE requests repetition of Msg3 in an SBFD symbol (or non-SBFD symbol).

[0152] If the RSRP of SSB / CSI-RS is lower than (or not higher than) RSRP-1 and RSRP-2, the UE requests repetition of Msg3 in a non-SBFD symbol (or SBFD symbol).

[0153] (Example of option 3) If the additional-RO type is indicated by the network or selected based on the RSRP of SSB / CSI-RS, the UE may perform one of the following operations. (1) If the SBFD symbol type is determined by repeating Msg3 as described above, the UE may transmit the PRACH using the PRACH resources (including preamble and / or RO resources) indicated by the new capability combination. (2) In cases other than (1) above, the UE may transmit the PRACH in additional-RO using the PRACH resource indicated by the combination of the repetition function of the conventional Msg3.

[0154] <Suggestion 4> Proposal 4 proposes how to determine the slot in which Msg3 is repeated.

[0155] When the UE transmits PRACH with additional-RO using the PRACH resources (preamble and / or RO resources) indicated by the new feature combination and the number of repetitions of Msg3 indicated by RAR UL grant / DCI 0_0 is greater than 1, the UE may determine the slot in which to repeat Msg3 using one of the following Alts:

[0156] (Alt 1) The repetition of Msg3 can occur in either SBFD or non-SBFD symbols.

[0157] The symbol type of the repetition of Msg3 is determined to be the same symbol type as the originally scheduled repetition of Msg3.

[0158] (Alt 2) The repetition of Msg3 is done with SBFD symbols.

[0159] (Alt 2-1) UE is a slot

number

[0160] (Alt 2-2) The UE determines the available slots for repetition of Msg3 regardless of the symbol type of the originally scheduled repetition of Msg3.

[0161] In this case, the UE must select the slot in which the PUSCH transmission repetition occurs within the SBFD symbol.

number

number

number

[0162] (analysis) In Alt 1, the new feature combination indicates UE support / capability of repetition of Msg3 in SBFD symbols, and in Alt 2, the new feature combination indicates UE request of repetition of Msg3 in SBFD symbols.

[0163] When the UE transmits PRACH in additional-RO using PRACH resources indicated by a combination of the conventional Msg3 repetition functions and the number of Msg3 repetitions indicated by RAR UL grant / DCI 0_0 is greater than 1, the Msg3 repetitions must be in non-SBFD symbols, and the UE may determine the slot in which to repeat Msg3 using one of the following Alts:

[0164] (Alt-a) UE is a slot

number

[0165] (Alt-b) The UE determines the available slots for repetition of Msg3 regardless of the symbol type of the originally scheduled repetition of Msg3.

[0166] In this case, the UE shall select slots where the repetition of PUSCH transmission is within a non-SBFD symbol.

number

number

number

[0167] (effect) As explained above, this proposal allows the UE to indicate to the gNB at an early stage the newly introduced functionality of the repetition of Msg3 in the SBFD symbol.

[0168] <UE capability> The UE capability indicating the capability of the terminal may include the following information indicating the capability of the terminal. For example, the following new UE capability and report signaling (and RRC configuration) may be defined. Note that the information indicating the capability of the terminal may correspond to information defining the capability of the terminal. The UE may report the following information indicating the capabilities of the terminal to the gNB: ·Device capabilities for each proposal ·Ability to implement each option or combination of options in each proposal · Capabilities for each alternative or combination of alternatives in each proposal The UE may report information indicating the above-mentioned terminal capabilities for each frequency to the gNB. · Capabilities for UE / FR1 / FR2 / FR2-1 / FR2-2 / FR3 / SCS / band / BC / FC / FSPC etc. The UE may report information indicating the above terminal capabilities for each cell to the gNB. Capabilities for each UE / cell / TDD / FDD, etc.

[0169] The above UE capabilities and the configuration of this proposal are closely related, and if the functions related to each option in each proposal depend on the UE capabilities, the gNB may select or enable the functions related to each option based on the capabilities reported by the UE.

[0170] <Notes> (Combined with options) In the proposals of the present disclosure, which proposals are applied or which options or alternatives are used may be determined by the following: - Set by parameters of upper layer Determined by related higher level parameters -Indicated in MAC CE or DCI Determined based on UE capabilities - Listed in the specifications - Determined based on the conditions stated in the specifications Determined by higher layer parameters / MAC CE / DCI configuration and reported UE capabilities (combination of the above decisions)

[0171] In the proposals of this disclosure, multiple options and alternatives may be combined into one option / alternative, and throughout the proposals, the measured reference signal (RS) will be the QCL source RS in the active / indicated TCI state.

[0172] (Signal from NW to UE) In this disclosure, the UE may receive the following types of information from the network (NW): Also, throughout the proposal, the network (NW) may be referred to as a gNB. Information via higher layer signaling (e.g., RRC messages / LPP (LTE propositioning protocol) messages) MAC CE Subheader with new LCID in the subheader Extending an existing MAC CE (e.g., introducing a new octet) DCI DCI Field: Existing DCI field or newly introduced DCI field RNTI: DCI with CRC scrambled by the existing RNTI or the newly introduced RNTI DCI Format: Existing DCI format or newly introduced DCI format Combination of the above information

[0173] In the present disclosure, the UE may receive information from the network (NW) in the following periodic format: Option 1: Receive periodic updates Option 2: Semi-persistent reception of information (triggered by UE or gNB instructions) Option 3: Aperiodically receive information (triggered by UE or gNB instructions)

[0174] In the present disclosure, the UE may receive information from the network (NW) as the following QCL rules: QCL Type A QCL Type B QCL Type C QCL Type D

[0175] In this disclosure, the QCL resource RS for each QCL type may be configured as follows: SSB (SS / PBCH Block) CSI-RS with / without repetition ·TRS(tracking reference signal) PDCCH / PDSCH DMRS

[0176] In the present disclosure, information from the network (NW) is set / indicated as follows: ·UE common / UE only Cell specific / Cell common Per UE / CC / BWP / band / cell / CG

[0177] (Signal from UE to NW) In this disclosure, the UE may report the following types of information to the network (NW): Also, throughout the proposal, the network (NW) may be referred to as a gNB. Information via higher layer signaling (e.g. RRC messages / LPP messages) MAC CE Subheader with new LCID in the subheader Extending an existing MAC CE (e.g., introducing a new octet) UCI UCI on PUCCH or PUSCH Combination of the above information

[0178] In the present disclosure, the UE may report information to the network (NW) in a periodic manner as follows: Option 1: Send information periodically Option 2: Semi-persistent information transmission (triggered by UE or gNB instruction) Option 3: Send information aperiodically (triggered by UE or gNB instruction)

[0179] <Base station configuration> Fig. 19 is a block diagram showing an example of the configuration of a base station 100 (gNodeB (gNB) 100) according to this embodiment. The gNB 100 includes, for example, a transmitter 101, a receiver 102, and a controller 103. The gNB 100 communicates with a UE 200 (see Fig. 20) wirelessly.

[0180] The configurations of the gNB 100 and the UE 200 described below are examples of functions related to the present embodiment. The gNB 100 and the UE 200 may have functions not shown. Furthermore, the functional divisions and / or names of the functional units are not limited as long as the functions perform the operations related to the present embodiment.

[0181] The transmitter 101 transmits a downlink (DL) signal to the UE 200. For example, under the control of the controller 103, the transmitter 101 transmits a DL signal (for example, the above-mentioned RRC, SIB, MAC CE, DCI, notification, confirmation, etc.).

[0182] The DL signal may include, for example, a downlink data signal and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating scheduling related to signal transmission by the UE 200 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., control information of Radio Resource Control (RRC)). The DL signal may also include a reference signal.

[0183] The channels used for transmitting DL signals include, for example, a downlink data channel and a downlink control channel. For example, the downlink data channel may include a PDSCH (Physical Downlink Shared Channel), and the downlink control channel may include a PDCCH (Physical Downlink Control Channel). For example, the gNB 100 transmits downlink control information to the UE 200 using the PDCCH and transmits downlink data signals using the PDSCH.

[0184] The reference signal included in the DL signal may include at least one of a demodulation reference signal (Demodulation Reference Signal (DMRS)), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information. For example, reference signals such as DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.

[0185] The receiver 102 receives an uplink (UL) signal transmitted from the UE 200. For example, under the control of the controller 103, the receiver 102 receives an UL signal (for example, the above-mentioned request, notification, etc.).

[0186] The transmitting unit 101 and the receiving unit 102 may be collectively referred to as a communication unit.

[0187] The control unit 103 controls the communication operations of the gNB 100, including the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102.

[0188] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.

[0189] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or resources used for transmitting and receiving UL signals based on a signal (e.g., data and control information, etc.) received from the UE 200 and / or data and control information, etc. acquired from an upper layer. Information on the allocated resources may be included in control information transmitted to the UE 200.

[0190] The receiver 102 may receive an acknowledgement signal transmitted using an uplink physical shared channel (PSCCH) on periodic, quasi-persistent, or aperiodic resources. The uplink physical shared channel may be a PUSCH. The acknowledgement signal may be a HARQ-ACK.

[0191] The control unit 103 may determine whether the downlink signal has been properly received based on the acknowledgement signal. The downlink signal may be a PDCCH / PDSCH.

[0192] The transmitter 101 may transmit the resource information of the physical shared channel via radio resource control signaling.

[0193] The transmitter 101 may transmit resource information for the physical shared channel in association with the Configured Grant setting.

[0194] The transmitter 101 may transmit a control element of a medium access control for enabling and disabling transmission of an acknowledgement signal by a terminal. The control element may include information for enabling and disabling transmission of the acknowledgement signal. The acknowledgement signal may be transmitted using a physical shared channel in a quasi-persistent resource. The control element may be a MAC CE.

[0195] The transmitter 101 may transmit a downlink control signal for the terminal to transmit an acknowledgment signal. The downlink control signal may include information for triggering the transmission of the acknowledgment signal. The downlink control signal may be DCI.

[0196] <Device configuration> 20 is a block diagram showing an example of the configuration of UE 200 according to the present embodiment. UE 200 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. UE 200 communicates with gNB 100 by radio, for example.

[0197] The transmitter 202 transmits an UL signal to the gNB 100. For example, the transmitter 202 transmits the UL signal under the control of the controller 203. For example, the transmitter 202 may transmit an MsgA PRACH in a valid MsgA RO determined by the controller 203, and may transmit an MsgA PUSCH in a valid MsgA PO determined by the controller 203.

[0198] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, information related to the processing capability of the UE 200 (e.g., UE capability) may be included. The UL signal may also include a reference signal.

[0199] The channels used for transmitting UL signals include, for example, an uplink data channel and an uplink control channel. For example, the uplink data channel includes a PUSCH (Physical Uplink Shared Channel), and the uplink control channel includes a PUCCH (Physical Uplink Control Channel). For example, the UE 200 transmits uplink control information to the gNB 100 using the PUCCH and transmits an uplink data signal using the PUSCH.

[0200] The reference signals included in the UL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRS, and PRS. For example, the reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (for example, PUSCH).

[0201] The receiving unit 201 and the transmitting unit 202 may be collectively referred to as a communication unit.

[0202] The control unit 203 controls the communication operations of the UE 200, including the reception processing in the reception unit 201 and the transmission processing in the transmission unit 202.

[0203] For example, the control unit 203 acquires information such as data and control information from a higher layer and outputs it to the transmitting unit 202. Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the higher layer.

[0204] For example, the control unit 203 controls transmission of information to be fed back to the gNB 100. The information to be fed back to the gNB 100 may include, for example, HARQ-ACK, Channel State Information (CSI), or a Scheduling Request (SR). The information to be fed back to the gNB 100 may be included in UCI.

[0205] The control unit 203 may determine to transmit an acknowledgement signal for the downlink signal. The downlink signal may be a PDCCH / PDSCH. The acknowledgement signal may be a HARQ-ACK.

[0206] The transmitter 202 may transmit the acknowledgement signal using an uplink physical shared channel in periodic, quasi-persistent, or aperiodic resources. For example, periodic, quasi-persistent, or aperiodic resources are provided (configured), and the transmitter 202 may determine a physical shared channel for transmitting the acknowledgement signal in the periodic, quasi-persistent, or aperiodic resource, and transmit the acknowledgement signal. The uplink physical shared channel may be a PUSCH.

[0207] The receiver 201 may receive resource information of periodic, semi-permanent, or aperiodic resources via radio resource control signaling, and the transmitter 202 may transmit an acknowledgement signal using a physical shared channel on resources based on the resource information.

[0208] The transmitter 202 may transmit the acknowledgement signal based on periodic resource information for the physical shared channel associated with the Configured Grant setting.

[0209] The control unit 203 may determine whether to enable or disable the transmission of an acknowledgement signal to be transmitted using a physical shared channel in quasi-permanent resources based on a control element of a medium access control, which may be a MAC CE.

[0210] The transmitter 202 may determine whether to transmit an acknowledgment signal using the physical shared channel in the aperiodic resource based on a downlink control signal. The downlink control signal may be DCI.

[0211] The present disclosure has been described above. Note that the division of items in the above description is not essential to the present disclosure, and matters described in two or more items may be used in combination as needed, and matters described in one item may be applied to matters described in another item (as long as there is no contradiction).

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

[0213] For example, a base station, a terminal, a network node, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 21 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. The above-described base station 100 and terminal 200 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.

[0214] In the present disclosure, the term "apparatus" may be interchangeable with any two terms selected from a set of terms such as circuit, device, unit, module, chip, means, etc. The hardware configurations of base station 100 and terminal 200 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.

[0215] Each function in the base station 100 and the terminal 200 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, memory 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls the reading, writing, or both reading and writing of data in the memory 1002 and storage 1003.

[0216] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, registers, etc. Although only one processor 1001 is shown in the figure, there may be multiple processors.

[0217] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from the storage 1003, the communication device 1004, or both the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with the programs. 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 103 of the base station 100 and the control unit 203 of the terminal 200 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line, or may be provided to the computer via the communication device 1004, for example.

[0218] The present disclosure also provides a computer program product including a computer program, which may implement the steps of the methods described in the above embodiments when the computer program is executed by a computer (e.g., the processor 1001).

[0219] The memory 1002 is a computer-readable recording medium and may be configured, for example, as a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), or a combination of at least two of these. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), or the like. The memory 1002 can store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

[0220] Storage 1003 is a computer-readable recording medium, and may be, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, or a combination of at least two of these. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, memory 1002, storage 1003, or a database, server, or other appropriate medium including both memory 1002 and storage 1003.

[0221] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, or a combination of at least two of these.

[0222] The input device 1005 is an input device that accepts input from the outside (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or a combination of at least two of these). The output device 1006 is an output device that outputs to the outside (for example, a display, a speaker, an LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0223] 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.

[0224] Furthermore, base station 100 and terminal 200 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), a field programmable gate array (FPGA), a graphics processing unit (GPU), a neural processing unit (NPU), or a combination of at least two of these, and some or all of the functional blocks may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

[0225] <Information notification, signaling> 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 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, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB))), other signals, or a combination of at least two of these. Note that the physical layer signaling may be referred to as Layer 1 (L1) control information. The MAC signaling may be referred to as a MAC Control Element (CE) or a MAC Protocol Data Unit (PDU), for example. Furthermore, the RRC signaling may be referred to as an RRC message or an information element (IE) in the RRC message. The RRC message may be, for example, a message used for controlling an RRC connection (for example, setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, a measurement report, or notification of a terminal's capabilities, or may be an information element within the message. Furthermore, notification of information may be explicit or implicit. Note that explicit notification of certain information means notification of the certain information itself, and implicit notification of certain information may mean notification of information other than the certain information, or may mean that the certain information is considered to have been notified when a certain condition is satisfied.Furthermore, notification of information may include not only notification between the same layers of different devices (e.g., between a lower layer or an upper layer of the base station 10 and the terminal 20) but also notification between different layers in the same or different devices (e.g., between a lower layer and an upper layer in the base station 10 or the terminal 20). Furthermore, notification of information from one device to another device may be performed via one or more devices. Regarding any information (e.g., a variable, a constant, a parameter, a setting) described in the present disclosure, even if not specifically stated in the above embodiments, information indicating / specifying (or related to) the any information (value) may be notified from any first device (e.g., a terminal / base station) to any second device (e.g., a base station / terminal).

[0226] <Applicable systems> Each aspect / embodiment described in the present disclosure may be implemented using any of a wide variety of standards, including Long Term Evolution (LTE), LTE-Advanced (LTE-A), International Mobile Telecommunications-Advanced (IMT-Advanced), 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 5G-A (5G-Advanced), 6G (6th generation mobile communication system), xG (xth generation mobile communication system (x is, for example, an integer or a decimal), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), Open Radio Access Network (O-RAN), Wideband Code Division Multiple Access (W-CDMA, registered trademark), Global System for Mobile communications (GSM, registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), and Institute of Electrical and Electronics Engineers (IEEE). 802.11, IEEE802.11x (where x is any character string such as b, a, g, n, ac, ax, be, or bn, and when x=n it is called Wi-Fi4, when x=ac it is called Wi-Fi5, when x=ax it is called Wi-Fi6 or Wi-Fi6E, when x=be it is Wi-Fi7, and when x=bn it is called Wi-Fi8, etc. Wi-Fi is a registered trademark.), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), network virtualization technology (e.g., NFV (Network Function Virtualization), SFC (Service Function Chaining), SDN (Software Defined Networking)), or LPWA (Low Power Wide Area). Furthermore, each aspect / embodiment described in the present disclosure may be applied to a system based on a combination of at least two of these technologies. Furthermore, "based on" naturally refers not only to a system that uses the technology, but also to a system that uses an extension or modification of the technology.

[0227] <Processing procedures, etc.> The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. 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.

[0228] <Base station operation> In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node or by some of its upper nodes (e.g., CU, RU, or DU, etc.) in some cases. It is clear that various operations performed for communication with a terminal in a RAN or core network may be performed by at least some of the base station and other network nodes other than the base station. The other network node may be one node or a combination of multiple nodes. The network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) and 5GC (5G Core Network), and provides one or more network functions (NF: Network Functions), but is not limited to this.

[0229] Furthermore, in the present disclosure, the operation of "a terminal receives information from a base station" accompanies the operation of "the base station transmits the information to the terminal," "the base station generates the information," or both. Similarly, the operation of "a terminal transmits information to a base station" accompanies the operation of "the base station receives the information from the terminal." Furthermore, the operation of "a terminal is configured to ..." or "configure UE to ..." may include the operation of "a base station transmits configuration information regarding the configuration of the terminal" and the operation of "a terminal configures a predetermined operation based on the configuration information."

[0230] <Input / output direction> Information, etc. (see the section on information and signals) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input and output via multiple network nodes.

[0231] <Handling of input and output information> Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0232] <Judgment method> The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0233] <Variations of form, etc.> Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation.

[0234] The present disclosure has been described above, but it is for illustrative purposes only, and the present invention is not limited to the aspects / embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit of the invention. The present disclosure and its modifications and alterations are included in the scope of the present invention and its equivalents.

[0235] <Software> 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.

[0236] 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), then these wired and / or wireless technologies are included within the definition of transmission media.

[0237] <Information, Signals> 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.

[0238] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0239] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0240] <Parameter, channel name> 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 an index.

[0241] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., 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.

[0242] <Base station> In the present disclosure, any two terms selected from a set of terms such as "base station (BS)", "radio base station", "fixed station (fixed station)", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point (AP)", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "radio unit (RU)", "remote unit (RU)", "control unit (CU)", "distributed unit (DU)", "remote radio head (RRH)", "node", "gateway", "terrestrial base station", "stratospheric base station", "unmanned aerial vehicle", "high altitude platform station (HAPS)", "airborne platform", "panel", "cell", "radio access network (RAN)", and "network" may be used interchangeably. Each cell accommodated by a base station may be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, a serving cell, or a super cell. In the present disclosure, any two terms selected from a set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.

[0243] 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 divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., an indoor small base station (RRH)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

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

[0245] <terminal> In the present disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "Module" and "Terminal" may be used interchangeably.

[0246] A terminal may 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, router (e.g., home router, mobile router, etc.), TCU (Telematics Control Unit), or some other suitable terminology.

[0247] <Base station / terminal> The base station and the terminal may each be composed of one or more devices. The devices constituting at least a portion of the base station and the terminal may be called a transmitting device, a receiving device, a communication device, etc. Note that the devices constituting at least a portion of the base station and the terminal may be, for example, an object itself, such as a vehicle, a transport vehicle, an automobile, a motorcycle, a bicycle, a connected car, an excavator, a bulldozer, a wheel loader, a dump truck, a forklift, a train, a bus, a handcar, a rickshaw, a ship and other watercraft, an airplane, a rocket, an unmanned aerial vehicle, a stratospheric base station (e.g., a High Altitude Platform Station (HAPS)), an artificial satellite (e.g., a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, a Geostationary Earth Orbit (GEO) satellite), a drone (registered trademark), a multicopter, a quadcopter, a balloon, or an Internet of Things (IoT) device (e.g., a smart meter, a sensor), or may include, but are not limited to, an object or device mounted on the object. Furthermore, the object may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the case where the moving object is in a stationary state where it is not moving), or may be a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0248] Furthermore, a base station in the present disclosure may be read as a 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 terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)) or communication of a non-terrestrial network (NTN). In this case, the terminal 20 may be configured to have at least some of the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "sidelink") or terms corresponding to NTN (for example, feeder link or service link). For example, an uplink channel or a downlink channel may be read as a sidelink channel.

[0249] The present disclosure is also applicable to cases where at least some of the devices constituting the base station and the terminal operate outside the earth (for example, in the atmosphere or outer space).

[0250] In addition, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station 100 may be configured to have the functions of the terminal 200 described above.

[0251] <Terminology and interpretation> As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0252] 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." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0253] <Reference signal> The reference signal may be abbreviated as RS (Reference Signal), and may also be called a pilot or pilot signal depending on the applicable standard.

[0254] <The meaning of "based on"> 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."

[0255] <"First", "Second"> 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.

[0256] <Means> In the configuration of each of the above devices, the "means" may be replaced with a "section", "circuit", "device", etc.

[0257] <Open format> In the present disclosure, when the terms "include", "including" and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.

[0258] <Time units such as TTI, frequency units such as RB, radio frame configuration> The radio resources can be defined, for example, by a combination of units of resources in one or more of the time domain, frequency domain, spatial domain, code domain, and power domain, etc.

[0259] For example, resources in the time domain may be defined by one or more time units. The one or more time units may include, but are not limited to, a radio frame, a subframe, a slot, a symbol, a transmission time interval (TTI), or a combination of at least two of these. The time unit may be a fixed-length time unit independent of numerology, a variable-length time unit dependent on numerology, or both. Examples of fixed-length time units include, but are not limited to, a subframe consisting of one or more slots and a radio frame including multiple subframes. Examples of variable-length time units include, but are not limited to, a symbol and a slot including a fixed number of symbols. A certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, a minislot consisting of fewer symbols than the number of symbols constituting a slot. The above-described time units may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in the present disclosure may be read as another time unit.

[0260] Numerology is a parameter that defines the physical layer structure, and may be a parameter based on at least one of subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time, for example.

[0261] Resources in the frequency domain may be defined, for example, by one or more frequency units. The one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or a combination of at least two of these, but the terminology of the frequency units is not limited to these. The number of subcarriers included in a frequency unit may be a fixed number regardless of numerology, or may be a variable number that changes depending on numerology. For example, an RB is composed of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of numerology, for example, 12, but is not limited to this. A BWP may be composed of, for example, one or more consecutive RBs within a certain carrier bandwidth, but is not limited to this. One or more BWPs may be configured within one carrier for terminal 20, and at least one of the BWPs may be activated. Any frequency unit in the present disclosure may be interchangeable with another frequency unit.

[0262] Furthermore, resources in both the time domain and the frequency domain may be defined by one or more time / frequency units each consisting of a time unit and a frequency unit, such as, but not limited to, a resource element (RE) consisting of one symbol and one subcarrier, a resource element group (REG) consisting of a predetermined number of REs, or a control resource set (CORESET) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0263] Furthermore, resources in the spatial domain may be defined, for example, in terms of one or more spatial units, including, but not limited to, a beam, a layer of MIMO (Multi-Input Multi-Output), an antenna port, or a combination of at least two of these.

[0264] Furthermore, the resources in the code domain may be defined by one or more code units, such as, but not limited to, a cyclic shift (CS), an orthogonal cover code (OCC), or a combination thereof.

[0265] <Maximum transmission power> 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.

[0266] <Article> 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.

[0267] <"Different"> 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." [Industrial Applicability]

[0268] One aspect of the present disclosure is useful in wireless communication systems. [Explanation of symbols]

[0269] 10. Wireless communication systems 20 NG-RAN 100 base stations (gNB) 200 User Equipment (UE) 101,202 Transmitter 102,201 Receiver 103,203 Control unit

Claims

1. A terminal that communicates with a base station using a first time unit in which a downlink and an uplink can be simultaneously used by a plurality of sub-bands that constitute a time division duplex band, and a second time unit in which one of the downlink and the uplink can be used by applying the time division duplex band, a control unit that sets a random access opportunity in the first time unit; a transmitter for transmitting a first message and a third message of a random access procedure using the random access opportunity; Equipped with the control unit generates control information indicating whether to support repetition of the third message in the first time unit; The transmitter transmits the control information to the base station. Terminal.

2. When the random access opportunity of the first time unit and the random access opportunity of the second time unit are both configured by a legacy random access configuration, a mask configuration of the random access opportunity related to the repetition of the third message in the first time unit is applied only to the additional random access opportunity. The terminal of claim 1.

3. When the random access opportunity of the first time unit is configured as an additional random access opportunity by an additional random access configuration and the random access opportunity of the second time unit is configured as a legacy random access configuration, the repetition of the third message in the first time unit is configured as an additional random access opportunity only. The terminal of claim 1.

4. When only repetition of the third message in the second time unit is supported and downlink reception quality is lower than a threshold for repetition of the third message, the control unit controls to transmit the third message using resources indicated by the legacy repetition of the third message. The terminal of claim 1.

5. a terminal that communicates with a base station using a first time unit in which downlink and uplink can be used simultaneously by a plurality of sub-bands that constitute a time division duplex band, and a second time unit in which one of the downlink and the uplink can be used by applying the time division duplex band, setting a random access opportunity in the first time unit; Using the random access opportunity, transmit a first message and a third message of a random access procedure; generating control information indicating whether repetition of the third message in the first time unit is supported; transmitting the control information to the base station; Communication method.

Images