WO2023084720A1 - Terminal and radio communication method - Google Patents

Abstract

An aspect of the present disclosure provides a terminal comprising a control unit that holds capability information about whether to repeatedly transmit an uplink message in response to a response message in the steps of random access, and a transmitting unit that transmits, to a base station, the capability information about whether to repeatedly transmit the uplink message.

Description

Terminal and wireless communication method

The present disclosure relates to terminals and wireless communication methods.

The 3rd Generation Partnership Project (3GPP) has specified the 5th generation mobile communication system (also called 5G, New Radio (NR) or Next Generation (NG)), and the next generation specification called Beyond 5G, 5G Evolution or 6G We are also proceeding with

For example, in 3GPP Release-17, a work item on coverage enhancement (CE: Coverage Enhancement) in NR was agreed (Non-Patent Document 1).

Specifically, specifications for repeated transmission of PUSCH scheduled based on RAR UL grant or DCI scrambled with TC-RNTI (DCI scrambled with TC-RNTI) are being studied. RAR stands for Random Access Response. DCI stands for Downlink Control Information. TC-RNTI is an abbreviation for Temporary Cell Radio Network Temporary Identifier. PUSCH stands for Physical Uplink Shared Channel.

　There is room for further study regarding the implementation of repeated transmission (also called Msg3 repetition) of uplink messages (Msg3, etc.) for random access procedures.

According to one aspect of the present disclosure, a control unit holding capability information regarding whether to repeatedly transmit an uplink message for a response message in a random access procedure, and transmitting the capability information regarding whether to repeatedly transmit the uplink message to a base station A terminal is provided having a transmitter for transmitting.

1 is a schematic diagram illustrating a wireless communication system according to one embodiment of the disclosure; FIG. 1 is a diagram illustrating an example of frequency ranges used in a wireless communication system according to one embodiment of the present disclosure; FIG. FIG. 2 is a diagram showing a configuration example of radio frames, subframes and slots used in a radio communication system according to an embodiment of the present disclosure; FIG. 10 illustrates a case regarding the propriety of Msg3 repetition according to an embodiment of the present disclosure; FIG. 10 is a sequence diagram illustrating a random access procedure according to one embodiment of the present disclosure; FIG. 4 is a block diagram showing the functional configuration of a base station (gNB) according to one embodiment of the present disclosure; FIG. 2 is a block diagram showing a functional configuration of a terminal (UE) according to one embodiment of the present disclosure; FIG. FIG. 2 is a block diagram showing hardware configurations of a base station and a terminal according to an embodiment of the present disclosure; FIG. 1 is a block diagram showing a hardware configuration of a vehicle according to one embodiment of the present disclosure; FIG.

Embodiments of the present disclosure will be described below with reference to the drawings.

<Wireless communication system>
FIG. 1 is a diagram showing an example of a wireless communication system 10 according to one embodiment. The radio communication system 10 is a radio communication system according to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter NG-RAN 20) and a terminal 200 (hereinafter UE 200).

Note that the wireless communication system 10 may be a wireless communication system that conforms to a scheme called Beyond 5G, 5G Evolution, or 6G.

NG-RAN 20 includes a base station 100A (hereinafter gNB100A) and a base station 100B (hereinafter gNB100B). Note that gNB100A, gNB100B, etc. are collectively referred to as gNB100 when there is no need to distinguish between them. Also, the number of gNBs and UEs is not limited to the example shown in FIG.

NG-RAN 20 actually includes multiple NG-RAN nodes, specifically gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). Note that NG-RAN 20 and 5GC may simply be referred to as a "network".

gNB100A and gNB100B are 5G-compliant base stations and perform 5G-compliant wireless communication with UE200. The gNB100A, gNB100B and UE200 generate more highly directional beams BM by controlling radio signals transmitted from multiple antenna elements Massive Multiple-Input Multiple-Output (MIMO), multiple component carriers (CC ), and dual connectivity (DC) that performs communication between the UE and each of the two NG-RAN nodes.

Also, the wireless communication system 10 supports multiple frequency ranges (FR).

FIG. 2 is a diagram showing an example of frequency ranges used in the wireless communication system 10. As shown in FIG. As shown in FIG. 2, the wireless communication system 10 supports FR1 and FR2. For example, the frequency band of each FR is as follows.
・FR1: 410MHz to 7.125GHz
・FR2: 24.25 GHz to 52.6 GHz

In FR1, Sub-Carrier Spacing (SCS) of 15kHz, 30kHz or 60kHz may be used, and a bandwidth (BW) of 5-100MHz may be used. FR2 is higher frequency than FR1 and may use an SCS of 60 kHz or 120 kHz (240 kHz may be included) and a bandwidth (BW) of 50-400 MHz.

　Subcarrier Spacing (SCS) may be interpreted as numerology. numerology is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

Furthermore, the wireless communication system 10 may support a higher frequency band than the FR2 frequency band. Specifically, the wireless communication system 10 may support frequency bands above 52.6 GHz and up to 114.25 GHz. Such high frequency bands may be conveniently referred to as "FR2x". Cyclic Prefix - Orthogonal Frequency Division Multiplexing (CP-OFDM)/Discrete Fourier Transform - Spread - Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with larger SCS may be applied when using bands above 52.6 GHz .

FIG. 3 is a diagram showing a configuration example of radio frames, subframes and slots used in the radio communication system 10. FIG. As shown in FIG. 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and the slot period). The SCS is not limited to the intervals (frequencies) shown in FIG. For example, 480 kHz, 960 kHz, etc. may be used as the SCS.

Also, the number of symbols constituting one slot does not necessarily have to be 14 symbols (for example, 28 or 56 symbols). Furthermore, the number of slots per subframe may vary between SCSs.

Note that the time direction (t) shown in FIG. 3 may be called the time domain, symbol period, symbol time, or the like. Also, the frequency direction may be called a frequency domain, resource block, subcarrier, bandwidth part (BWP), or the like.

　Demodulation Reference Signal (DMRS) is a type of reference signal and is prepared for various channels. Here, unless otherwise specified, it may mean DMRS for downlink data channels (specifically, Physical Downlink Shared Channel (PDSCH)). However, DMRS for uplink data channels (specifically, PUSCH) may be interpreted similarly to DMRS for PDSCH.

DMRS may be used for channel estimation in devices (eg, UE 200) as part of coherent demodulation. A DMRS may exist only in a resource block (RB: Resource Block) used for PDSCH transmission.

A DMRS may have multiple mapping types. Specifically, the DMRS may have mapping type A and mapping type B. For mapping type A, the first DMRS may be placed in the 2nd or 3rd symbol of the slot. In mapping type A, the DMRS may be mapped relative to slot boundaries, regardless of where in the slot the actual data transmission begins. The reason the first DMRS is placed in the second or third symbol of the slot may be interpreted as to place the first DMRS after the control resource sets (CORESET).

In mapping type B, the first DMRS may be placed in the first symbol of data allocation. That is, the position of the DMRS may be given relative to where the data is located rather than relative to slot boundaries.

In addition, DMRS may have multiple types (Type). Specifically, DMRS may have Type 1 and Type 2. Type 1 and Type 2 differ in mapping in the frequency domain and the maximum number of orthogonal reference signals. Type 1 can output up to 4 orthogonal signals with single-symbol DMRS, and Type 2 can output up to 8 orthogonal signals with double-symbol DMRS.

The wireless communication system 10 may support coverage enhancement (CE: Coverage Enhancement) that expands the coverage of cells (or physical channels) formed by the gNB 100. Coverage extension may provide mechanisms to increase the success rate of reception of various physical channels, such as Msg3 repetition.

For example, UE 200 receives information related to the RACH procedure from gNB 100 as a DL signal. Also, for example, the UE 200 receives information on Msg3 repetition from the gNB 100 as a DL signal. Information about Msg3 repetition may include, for example, information indicating resources used for repeated transmission of Msg3, number of repeated transmissions, frequency hopping pattern, specified offset used for frequency hopping, and the like.

For example, the UE 200 transmits a special RACH occurrence (RO), preamble, etc. for requesting Msg3 repetition in the RACH procedure to the gNB 100 as UL signals. Also, for example, the UE 200 repeatedly transmits Msg3 to the gNB 100 as the UL signal based on the information regarding the Msg3 repetition received from the gNB 100 in response to the request for the Msg3 repetition.

　UL signals may include, for example, UL data signals and control information. For example, the UL signal may include information about the processing capability of UE 200 (eg, UE capability). Also, the UL signal may include a reference signal.

Channels used to transmit UL signals include, for example, data channels and control channels. For example, data channels may include PUSCH and control channels may include Physical Uplink Control Channel (PUCCH). For example, the UE 200 uses PUCCH to transmit control information, and uses PUSCH to transmit UL data signals. PUSCH is an example of an uplink shared channel, and PUCCH is an example of an uplink control channel. A shared channel may also be referred to as a data channel.

Reference signals included in UL signals include, for example, DMRS, Phase Tracking Reference Signal (PTRS), Channel State Information - Reference Signal (CSI-RS), Sounding Reference Signal (SRS) and Positioning Reference Signal (PRS ) may be included. For example, reference signals such as DMRS and PTRS are used for demodulation of UL data signals and transmitted using PUSCH.

Also, in the NR RA procedure, the UE 200 transmits a random access preamble (RA preamble) as the first message (Msg1) as the first step in the RACH procedure. Also, as the second step in the RACH procedure, UE 200 receives a second message (Msg2) as a response message (Random Access Response (RAR)) to Msg1. Also, as the third step in the RACH procedure, UE 200 transmits a third message (Msg3) via PUSCH after receiving Msg2. Also, as the fourth step in the RACH procedure, the UE 200 receives the fourth message (Msg4) as a response message to Msg3 (3GPP TS38.321 V16.5.0 Section 5.1 "Random Access procedure"). The RACH procedure consisting of the first to fourth steps above may also be called a type 1 RACH procedure, a 4-step RACH procedure, a type 1 RACH, a 4-step RACH, or the like.

For example, Msg1 may be sent via Physical RACH (PRACH). Msg1 may be called PRACH preamble or RA preamble. Msg2 may be transmitted via PDSCH. Msg2 may be called RAR. Msg3 may be called RRC Connection Request. Msg4 may be called RRC Connection Setup.

Also, for example, the UE 200 may control a RACH procedure consisting of a first step combining the first step and the third step and a second step combining the second step and the fourth step. . The RACH procedure may also be called a type 2 RACH procedure, a 2-step RACH procedure, a type 2 RACH, a 2-step RACH, or the like. Also, the combined message of Msg1 and Msg3 above in the first step of the RACH procedure may be called MsgA.

Note that Msg3 may be called an uplink signal or a second uplink signal. Also, Msg1 may be called a first uplink signal. Also, the number of repeated transmissions may be read as the number of repetitions, the number of repeated transmissions, the number of repetitions, the number of repeated transmissions, the number of repetitions, the number of repetitions, or the like.

Also, the channels used for DL signal transmission and the channels used for UL signal transmission are not limited to the above examples. For example, channels used to transmit DL signals and channels used to transmit UL signals may include RACH and Physical Broadcast Channel (PBCH). RACH may be used, for example, to transmit DCI including Random Access Radio Network Temporary Identifier (RA-RNTI).

In addition, multiple types of repeated transmission of PUSCH may be defined. Specifically, Repetition type A and Repetition type B may be defined. Repetition type A may be interpreted as a form in which the PUSCH allocated within the slot is repeatedly transmitted. In other words, PUSCH is 14 symbols or less, and is unlikely to be allocated across multiple slots (adjacent slots).

On the other hand, Repetition type B may be interpreted as repeated transmission of PUSCH to which 15 or more PUSCH symbols may be allocated. In the present embodiment, allocation of such PUSCH across multiple slots may be allowed.

Also, in the radio communication system 10, multiple types of UE 200 may be used. For example, the UE 200 may include multiple types of terminals that differ in function or performance, or that support different 3GPP releases. The terminal (UE) may be called a type 1 terminal and a type 2 terminal. Also, the type may be replaced with other terms such as generation and release. A type 1 terminal and a type 2 terminal may be called an enhanced UE and a legacy UE, respectively. For example, an enhanced UE may be interpreted as a UE that supports Msg3 repetition, and a legacy UE may be interpreted as a UE that does not support Msg3 repetition.

［Proposal 1］
<Consideration>
Regarding Msg3 repetition, since the gNB 100 determines whether Msg3 repetition is necessary at the time of initial connection, it is agreed that it is determined whether or not the UE 200 requests Msg3 repetition with Msg1. Currently, it is agreed that the UE 200 determines whether to request Msg3 repetition based on the Reference Signal Received Power (RSRP) of the downlink reference signal. Whether UE 200 requests Msg3 repetition can be determined by gNB 100 based on the preamble of Msg1 or RACH Occasion (RO).

Regarding the propriety of Msg3 repetition, for example, the case shown in Fig. 4 is assumed. If the UE 200 supports Msg3 repetition (S101: YES), it is determined in step S102 whether the UE 200 requests Msg3 repetition. On the other hand, if UE 200 does not support Msg3 repetition (S101: NO), UE 200 does not request Msg3 repetition and Msg3 repetition is not applied in step S103.

In step S102, if the UE 200 requests Msg3 repetition (S102: YES), in step S104, the gNB 100 determines whether to instruct Msg3 repetition. Specifically, if UE 200 that supports Msg3 repetition sends Msg1 to gNB 100 with a preamble or RO associated with the request for Msg3 repetition, gNB 100 receives Msg1 preamble or RO, based on which UE 200 receives Msg3 It may be determined that repetition is required. On the other hand, if UE 200 does not request Msg3 repetition (S102: NO), UE 200 does not request Msg3 repetition in step S105, and gNB 100 does not apply Msg3 repetition. Specifically, if UE 200 sends Msg1 to gNB 100 with a preamble or RO that is not associated with a request for Msg3 repetition, gNB 100 determines whether UE 200 requests Msg3 repetition based on the received Msg1 preamble or RO. It may be determined that it is not.

　In step S104, if the gNB 100 instructs Msg3 repetition (S104: YES), in step S106, the UE 200 applies Msg3 repetition. Specifically, when gNB100 notifies an uplink grant by Msg3 repetition in Msg2, UE200 repeatedly transmits Msg3 to gNB100 according to the Msg3 repetition instruction of Msg2. On the other hand, if gNB 100 does not instruct Msg3 repetition (S104: NO), UE 200 does not apply Msg3 repetition in step S107. Specifically, when gNB100 notifies an uplink grant without Msg3 repetition instruction in Msg2, UE200 transmits Msg3 to gNB100 without repeating transmission according to the uplink grant of Msg2.

As can be understood from the above description, when UE 200 requests Msg3 repetition in step S102, gNB 100 can determine that UE 200 supports Msg3 repetition. On the other hand, if UE 200 does not request Msg3 repetition in step S102, gNB 100 cannot determine whether UE 200 supports Msg3 repetition. Therefore, after establishing a communication connection with gNB100 in a certain cell by initial connection, gNB100 determines whether Msg3 repetition can be applied to UE200 when connecting to another cell of gNB100 by handover, for example. handover to the transition destination cell may not be realized satisfactorily.

<Reporting UE capability for support of Msg3 repetition>
According to Proposal 1, UE 200 transmits capability information regarding support for Msg3 repetition to gNB 200. That is, UE 200 holds capability information regarding whether or not to repeatedly transmit an uplink message such as Msg3 in response to a response message such as Random Access Response (RAR) in a random access procedure, and transmits the capability information to gNB 100. Specifically, in Contention Based Random Access (CBRA) of NR, UE 200 schedules with PUSCH (hereinafter referred to as Msg3 initial transmission) scheduled with RAR UL grant and DCI scrambled with DCI scrambled by TC-RNTI UE capability indicating whether or not repeated transmission with the received PUSCH (hereinafter referred to as Msg3 retransmission) is supported may be reported to gNB 100.

For example, after establishing a communication connection with gNB100, UE200 may transmit UE capability indicating that Msg3 repetition is supported or not supported to gNB100. In the NR CBRA procedure, in step S201, the UE 200 transmits a Random Access Request (Msg1) to the gNB 100, as shown in FIG. Msg1 here does not include, without limitation, a request for Msg3 repetition, and may be, for example, a preamble for requesting Msg3 repetition or unrelated to the RO.

In step S202, gNB100 transmits RAR (Msg2) including UL grant to UE200. In step S203, UE200 transmits PUSCH (Msg3) granted by UL grant to gNB100. In step S204, gNB100 transmits Contention Resolution (Msg4) to UE200. Thereby, an RRC connection is established between the gNB 100 and the UE 200 in step S205. Then, in step S206, UE200 transmits UE capability regarding support of Msg3 repetition to gNB100.

According to the solution of Proposal 1 mentioned above, gNB100 can grasp whether UE200 supports Msg3 repetition after communication connection is established. That is, when receiving a request for Msg3 repetition from UE 200 in Msg1, gNB 100 can determine that UE 200 supports Msg3 repetition when receiving Msg1. On the other hand, if no request for Msg3 repetition is received from UE200 in Msg1, gNB100 can grasp whether or not UE200 supports Msg3 repetition when receiving UE capability after RRC connection establishment. Therefore, gNB 100 can more appropriately control handover to another cell by UE 200 after RRC connection establishment, based on whether UE 200 supports Msg3 repetition.

In one embodiment, UE 200 may transmit UE capability regarding support for Msg3 repetition to gNB 100 only if UE 200 does not request Msg3 repetition during initial connection by the random access procedure. For example, as described above with reference to FIG. 4, in the case of step S105, even if UE 200 supports Msg3 repetition, gNB 100 cannot determine whether UE 200 supports Msg3 repetition. . On the other hand, in the case of steps S106 and S107, gNB 100 can implicitly know that UE 200 supports Msg3 repetition based on the request for Msg3 repetition from UE 200, and the UE capability for supporting Msg3 repetition does not require explicit notification by Therefore, only in the case of step S105 where the UE 200 does not request Msg3 repetition at the time of initial connection, the UE 200 may transmit the UE capability regarding support for Msg3 repetition to the gNB 100. This can reduce the signaling overhead required for UE capability.

Also, in one embodiment, the UE capability regarding support for Msg3 repetition may be reported for each UE 200, for each supported frequency band, or for each supported duplex scheme. That is, UE capability indicating whether or not UE200 supports Msg3 repetition as a mobile station may be reported to gNB100. In addition, UE capability indicating whether UE 200 supports Msg3 repetition for each frequency band such as FR1, FR2, FR1, FR2-1, FR2-2, and SCS may be reported to gNB 100. . Also, UE capability indicating whether UE 200 supports Msg3 repetition for each Time Division Duplex (TDD) and Frequency Division Duplex (FDD) may be reported to gNB 100. As a result, even if the UE 200 is equipped with Msg3 repetition support for any granularity, it is possible to appropriately notify the gNB 100 of the Msg3 repetition support state corresponding to that granularity.

［Proposal 2］
<Consideration>
For Msg3 repetition, gNB 100 notifies UE 200 of the number of times of Msg3 repetition in any field of UL grant (for example, Modulation and Coding Scheme (MCS) field or Time Domain Resource Allocation (TDRA) field), and UE 200 receives Msg3 If repetition is applied, it is agreed that the value of this field determines the number of Msg3 repetitions. That is, the value of a given field of the UL grant is used to specify the number of times of Msg3 repetition in addition to or instead of the original role of the field, and the UE 200, if Msg3 repetition is applied , interpret the value of this field as the number of Msg3 repetitions (hereinafter referred to as UL grant interpretation).

In an example UL grant interpretation method, the upper 2 bits of the MCS field are used to specify the number of Msg3 repetitions, and the UE 200 uses the value of the upper 2 bits of the MCS field when Msg3 repetition is applied. You may decide the number of Msg3 repetitions. In another example UL grant interpretation method, a given column in the TDRA table is used to specify the number of times for Msg3 repetition, and UE200 interprets the specified TDRA table row if Msg3 repetition is applied. The number of Msg3 repetitions may be determined based on the index.

Such UL grant interpretation can be performed when UE200 sends a request for Msg3 repetition to gNB100, or when UE200 receives an instruction to apply Msg3 repetition from gNB100. In the latter case, the application can be indicated based on the PDCCH, RAR, etc. that trigger the random access procedure with the UE 200 from the gNB 100. For example, CBRA is triggered when the Random Access Preamble index field of PDCCH is "0b000000", and Contention Free Random Access (CFRA) is triggered when the Random Access Preamble index field of PDCCH is not "0b000000". can be specified. In this way, when CBRA is triggered by PDCCH order to UE 200 after RRC connection establishment, gNB 100 can further determine whether Msg3 repetition needs to be set to UE 200 in the CBRA.

Thus, it is agreed that the value of a given field in UL grant will be used to indicate the number of Msg3 repetitions. However, at present, it is not clearly defined in what cases the UL grant interpretation method by Msg3 repetition instruction is applied.

<Application of Msg3 repetition when initial connection is started according to instructions from gNB>
According to Proposal 2, when UE200 starts initial connection based on the fact that the DCI format of PDCCH order from gNB100 is "1_0" (DCI 1_0), UE200 follows Msg3 mentioned above according to Option 1-4 below. A UL grant interpretation for the repetition indication may apply. Note that this embodiment focuses on the UE 200 starting an initial connection based on the PDCCH order (DCI 1_0) from the gNB 100, but the solution according to the present disclosure is not limited to this, and any instruction from the gNB 100 may be applied to the initiation of CBRA by the UE 200 based on

(Option 1)
If the UE capability indicating that UE200 supports Msg3 repetition has already been reported to gNB100, UE200, when starting the initial connection based on the PDCCH order (DCI 1_0) from gNB100, for Msg3 repetition indication UL grant interpretation of That is, if the UE capability indicating that UE200 supports Msg3 repetition has been reported to gNB100, UE200 will use Msg3 repetition when starting the initial connection based on the PDCCH order (DCI 1_0) from gNB100. and may determine the number of Msg3 repetitions based on the value of a given field in the UL grant.

(Option 2)
The UE 200 may determine whether to apply the UL grant interpretation for the Msg3 repetition indication based on the PDCCH (DCI 1_0) that triggers the RA procedure. For example, the UE 200 may use part or all of the reserved bits of DCI 1_0 to determine whether to apply the UL grant interpretation for the Msg3 repetition indication. If the UE 200 determines to apply the UL grant interpretation based on some or all of the reserved bits of DCI 1_0, the UE 200 uses Msg3 repetition when starting the initial connection according to the PDCCH order (DCI 1_0) from the gNB 100. and may determine the number of Msg3 repetitions based on the value of a given field in the UL grant. For example, when UE 200 starts initial connection based on the PDCCH order (DCI 1_0) from gNB 100, it may determine whether to apply the UL grant interpretation based on the bit corresponding to UL/SUL indicator. At this time, UE200 may select preamble or RO to send Msg1 regardless of whether the Msg3 repetition is based on the Msg3 repetition request from UE200. Since the RA procedure applies Msg3 repetition according to the instruction from gNB 100, the preamble or RO associated with Msg3 repetition need not be selected in Msg1. Also, the solution according to the present disclosure is not necessarily limited to the UL/SUL indicator, and other reserved bits of DCI 1_0 may be utilized.

(Option 3)
When RSRP measured based on the downlink reference signal is less than or equal to a predetermined threshold, UE 200 UL grant for Msg3 repetition instruction when starting initial connection based on PDCCH order (DCI 1_0) from gNB 100 Interpretation may apply. That is, when the RSRP for the downlink reference signal from gNB100 is less than or equal to a predetermined threshold, UE200 applies Msg3 repetition when starting the initial connection based on the PDCCH order (DCI 1_0) from gNB100, and UL The number of Msg3 repetitions may be determined based on the value of a given field in grant.

(Option 4)
When the number of Msg1 transmission attempts or the number of Msg3 transmission attempts exceeds a predetermined threshold, the UE 200, when starting the initial connection based on the PDCCH order (DCI 1_0) from gNB 100, UL for Msg3 repetition indication grant interpretation may be applied. That is, when the number of transmission attempts of Msg1 or the number of transmission attempts of Msg3 is equal to or greater than a predetermined threshold, UE 200, when starting an initial connection based on the PDCCH order (DCI 1_0) from gNB 100, the predetermined UL grant The number of Msg3 repetitions may be determined based on the value of the field.

(combination of Option 1-4)
Although Options 1-4 have been described individually, any combination of two or more of Options 1-4 may be applied. Also, the gNB 100 may use any information such as System Information Block 1 (SIB 1), Radio Resource Control (RRC) parameters, etc. to notify the UE 200 which of Options 1-4 should be applied. Alternatively, UE 200 may determine which of Options 1-4 to apply based on the PDCCH that triggers the RA procedure.

Also, the phrase "application of UL grant interpretation for Msg3 repetition indication" here may be used interchangeably with "request for Msg3 repetition". For example, UE 200 may send Msg1 with a preamble or RO requesting Msg3 repetition.

According to the solution of Proposal 2, it is possible to set the number of Msg3 repetitions that are applied when the initial connection is started according to the instructions from the gNB, etc., according to the UL grant interpretation.

［Proposal 3］
<Consideration>
Rel-15/16 specifies that the PUSCH of Msg3 is not transmitted if it overlaps the downlink symbol of tdd-UL-DL-ConfigurationDedicated (TS 38.213 Section 11.1). At the stage of scheduling Msg3 in CBRA, gNB 100 may not know that UE 200 is in RRC connected state and may not schedule Msg3 considering downlink symbols of tdd-UL-DL-ConfigurationDedicated. There is a possibility that Msg3 will not be transmitted on the relevant resource, but if the gNB 100 schedules another channel on the relevant resource, there is a high possibility of collision with Msg3 PUSCH, which makes efficient use of resources difficult. Especially when repetition type A is applied to Msg3, it is difficult to schedule so that the downlink symbol of tdd-UL-DL-ConfigurationDedicated and the resource of Msg3 do not overlap (hereinafter referred to as collision handling). Therefore, there may frequently occur cases where gNB 100 cannot determine whether UE 200 transmits PUSCH of Msg3 using this resource.

It was agreed that further consideration would be made on whether to perform collision handling in consideration of tdd-UL-DL-ConfigurationDedicated when applying Msg3 repetition. For example, collision between the downlink symbol indicated by tdd-UL-DL-ConfigurationDedicated and PUSCH by Msg3 repetition is an exceptional case, i.e. Msg3 PUSCH repetition is the downlink symbol indicated by tdd-UL-DL-ConfigurationDedicated It was agreed that further consideration should be given as to whether cancellation by symbol is possible. It was also agreed that the application of the Rel-17 Msg3 PUSCH collision rule would be further considered.

<collision handling rule of Msg3>
According to Proposal 3, UE 200 schedules with DCI scrambled with tdd-UL-DL-ConfigurationDedicated downlink symbols and RAR UL grant or TC-RNTI when any of the following conditions 1 to 5 is satisfied: Even if the PUSCH overlaps, the corresponding PUSCH may be transmitted.

(Condition 1)
If UE 200 supports Msg3 repetition, UE 200 may transmit Msg3 even if it overlaps tdd-UL-DL-ConfigurationDedicated downlink symbols.

(Condition 2)
When UE200 requests Msg3 repetition when transmitting PRACH, UE200 may transmit Msg3 even if the downlink symbol of tdd-UL-DL-ConfigurationDedicated and Msg3 overlap.

(Condition 3)
If UE 200 applies Msg3 repetition (for example, by PUSCH repetition type A) and transmits Msg3, UE 200 will send Msg3 even if the downlink symbols of tdd-UL-DL-ConfigurationDedicated and Msg3 overlap. may be sent.

(Condition 4)
When UE 200 applies the UL grant interpretation for Msg3 repetition indication and transmits Msg3, UE 200 transmits Msg3 even if the downlink symbol of tdd-UL-DL-ConfigurationDedicated and Msg3 overlap. you can

(Condition 5)
When UE200 applies the information included in SIB1 or RAR and transmits Msg3, UE200 transmits Msg3 even if the downlink symbol of tdd-UL-DL-ConfigurationDedicated and Msg3 overlap. you can For example, the information may refer to or specify tdd-UL-DL-ConfigurationDedicated with 1 bit. Alternatively, the information may be a bitmap to cancel or notify the PUSCH of each slot.

(Combination of conditions 1 to 5)
Although Conditions 1 to 5 have been described individually, any combination of two or more of Conditions 1 to 5 may be applied. Also, the gNB 100 may use any information such as SIB1 and RRC parameters to notify the UE 200 which of the conditions 1 to 5 should be applied.

Here, the gNB 100 may determine whether or not to apply the collision handling rule depending on whether or not the UE 200 that has permitted the PUSCH scheduled with the RAR UL grant is in the RRC connected state. . For example, when UE200 transmits PRACH in CBRA, UE200 may transmit PUSCH by applying the collision handling rule. On the other hand, when UE 200 transmits PRACH in CFRA, UE 200 may not transmit PUSCH if downlink symbols of tdd-UL-DL-ConfigurationDedicated and PUSCH overlap.

According to the solution of Proposal 3, it is possible to define a rule (collision handling rule) for PUSCH by Msg3 repetition when PUSCH of Msg3 overlaps the downlink symbol of tdd-UL-DL-ConfigurationDedicated.

[Modification]
The solutions of Proposals 1-3 above may be similarly applied during TB processing over multi-slot PUSCH (TBoMS) processing transport blocks (TB) over PUSCH and/or repeated transmission of TBoMS. TBoMS is a technique of transmitting one transport block, in which TBS is calculated based on multiple slots, using multiple slots, and PUSCH is transmitted using multiple slots. For this PUSCH repetition, solutions in Proposal 1-3 may be applied.

(Device configuration)
Next, functional configuration examples of the gNB 100 and the UE 200 that implement the processes and operations described so far will be described. The gNB 100 and UE 200 contain functionality that implements the embodiments described above. However, the gNB 100 and the UE 200 may each have only part of the functions in the example.

<gNB100>
FIG. 6 is a diagram showing an example of the functional configuration of the gNB100. As shown in FIG. 6, gNB 100 has receiving section 101 , transmitting section 102 and control section 103 . The functional configuration shown in FIG. 6 is merely an example. As long as the operation according to the embodiment of the present invention can be performed, the functional division and the names of the functional units may be arbitrary.

The receiving section 101 includes a function of receiving various signals transmitted from the UE 200 and acquiring, for example, higher layer information from the received signals. The transmission unit 102 includes a function of generating a signal to be transmitted to the UE 200 and transmitting the signal by wire or wirelessly.

The control unit 103 stores preset setting information and various setting information to be transmitted to the UE 200 in a storage device, and reads them from the storage device as necessary. Also, the control unit 103 executes processing related to communication with the UE 200 . A functional unit related to signal transmission in control unit 103 may be included in transmitting unit 102 , and a functional unit related to signal reception in control unit 103 may be included in receiving unit 101 .

<UE200>
FIG. 7 is a diagram showing an example of the functional configuration of the UE200. As shown in FIG. 7, the UE 200 has a transmission section 201, a reception section 202 and a control section 203. The functional configuration shown in FIG. 7 is merely an example. As long as the operation according to the embodiment of the present invention can be performed, the functional division and the names of the functional units may be arbitrary.

The transmission unit 201 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal. The receiving unit 202 wirelessly receives various signals and acquires a higher layer signal from the received physical layer signal. The receiving section 202 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL control signals, reference signals, etc. transmitted from the gNB 100 .

The control unit 203 stores various setting information received from the gNB 100 by the receiving unit 202 in the storage device, and reads them from the storage device as necessary. Also, the control unit 203 executes processing related to communication with the gNB 100 . A functional unit related to signal transmission in control unit 203 may be included in transmitting unit 201 , and a functional unit related to signal reception in control unit 203 may be included in receiving unit 202 .

(Hardware configuration)
It should be noted that the block diagrams used in the description of the above embodiments show blocks in units of functions. These functional blocks (components) are implemented by any combination of at least one of hardware and software. Also, the method of realizing each functional block is not particularly limited. That is, each functional block may be implemented using one device physically or logically coupled, or directly or indirectly using two or more physically or logically separated devices (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices. A functional block may be implemented by combining software in the one device or the plurality of devices.

Functions include judging, determining, determining, calculating, calculating, processing, deriving, examining, searching, checking, receiving, transmitting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, assuming, Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. can't For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. In either case, as described above, the implementation method is not particularly limited.

For example, the gNB 100, UE 200, etc. in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 8 is a diagram showing an example of hardware configurations of gNB 100 and UE 200 according to an embodiment of the present disclosure. The gNB 100 and UE 200 described above may physically be 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, and the like.

In the following explanation, the term "apparatus" can be read as a circuit, device, unit, or the like. The hardware configuration of gNB 100 and UE 200 may be configured to include one or more of each device shown in the figure, or may be configured without some devices.

Each function of the gNB 100 and the UE 200 is performed by loading predetermined software (programs) on hardware such as the processor 1001 and the memory 1002. The processor 1001 performs calculations, controls communication by the communication device 1004, and by controlling at least one of reading and writing of data in the storage 1003 .

The processor 1001, for example, operates an operating system and controls the entire computer. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like. For example, the control units 103 and 203 described above may be implemented by the processor 1001 .

Also, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to them. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, the control units 103 and 203 of the gNB 100 and the UE 200 may be stored in the memory 1002 and implemented by a control program running on the processor 1001, and other functional blocks may be similarly implemented. Although it has been explained that the above-described various processes are executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. FIG. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via an electric communication line.

The memory 1002 is a computer-readable recording medium, and is composed of at least one of, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be The memory 1002 may also be called a register, cache, main memory (main storage device), or the like. The memory 1002 can store executable programs (program code), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disc, a magneto-optical disc (for example, a compact disc, a digital versatile disc, a Blu-ray disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, and/or the like. Storage 1003 may also be called an auxiliary storage device. The storage medium described above may be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003 .

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of, for example, frequency division duplex (FDD) and time division duplex (TDD). may consist of For example, antennas included in gNB 100 and UE 200 may be implemented by communication device 1004 .

The input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, display, speaker, LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).

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 devices.

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 devices. Devices such as the processor 1001 and the memory 1002 are 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 devices.

An example configuration of the vehicle 2001 is shown in FIG. As shown in FIG. 9, a vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029. , an information service unit 2012 and a communication module 2013 . Each aspect/embodiment described in the present disclosure may be applied to a communication device mounted on vehicle 2001, and may be applied to communication module 2013, for example.

The driving unit 2002 is configured by, for example, an engine, a motor, or a hybrid of the engine and the motor. The steering unit 2003 includes at least a steering wheel (also referred to as steering wheel), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

The electronic control unit 2010 is composed of a microprocessor 2031 , a memory (ROM, RAM) 2032 and a communication port (IO port) 2033 . Signals from various sensors 2021 to 2029 provided in the vehicle 2001 are input to the electronic control unit 2010 . The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

The signals from the various sensors 2021 to 2029 include the current signal from the current sensor 2021 that senses the current of the motor, the rotation speed signal of the front and rear wheels acquired by the rotation speed sensor 2022, and the front wheel acquired by the air pressure sensor 2023. and rear wheel air pressure signal, vehicle speed signal obtained by vehicle speed sensor 2024, acceleration signal obtained by acceleration sensor 2025, accelerator pedal depression amount signal obtained by accelerator pedal sensor 2029, brake pedal sensor 2026 obtained by There are a brake pedal depression amount signal, a shift lever operation signal acquired by the shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 2028, and the like.

The information service unit 2012 includes various devices such as car navigation systems, audio systems, speakers, televisions, and radios for providing various types of information such as driving information, traffic information, and entertainment information, and one or more devices for controlling these devices. ECU. The information service unit 2012 uses information acquired from an external device via the communication module 2013 or the like to provide passengers of the vehicle 2001 with various multimedia information and multimedia services.

Driving support system unit 2030 includes millimeter wave radar, LiDAR (Light Detection and Ranging), camera, positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, automatic driving vehicle (AV) map, etc. ), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, AI processors, etc., to prevent accidents and reduce the driver's driving load. and one or more ECUs for controlling these devices. In addition, the driving support system unit 2030 transmits and receives various information via the communication module 2013, and realizes a driving support function or an automatic driving function.

The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via communication ports. For example, the communication module 2013 communicates with the vehicle 2001 through the communication port 2033, the drive unit 2002, the steering unit 2003, the accelerator pedal 2004, the brake pedal 2005, the shift lever 2006, the front wheels 2007, the rear wheels 2008, the axle 2009, the electronic Data is transmitted and received between the microprocessor 2031 and memory (ROM, RAM) 2032 in the control unit 2010 and the sensors 2021-29.

The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from an external device via wireless communication. Communication module 2013 may be internal or external to electronic control unit 2010 . The external device may be, for example, a base station, a mobile station, or the like.

The communication module 2013 transmits the current signal from the current sensor input to the electronic control unit 2010 to an external device via wireless communication. In addition, the communication module 2013 receives the rotation speed signal of the front and rear wheels obtained by the rotation speed sensor 2022, the air pressure signal of the front and rear wheels obtained by the air pressure sensor 2023, and the vehicle speed sensor. 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, and a shift lever. A shift lever operation signal obtained by the sensor 2027 and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by the object detection sensor 2028 are also transmitted to an external device via wireless communication.

The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from external devices, and displays it on the information service unit 2012 provided in the vehicle 2001 . Communication module 2013 also stores various information received from external devices in memory 2032 available to microprocessor 2031 . Based on the information stored in the memory 2032, the microprocessor 2031 controls the drive unit 2002, the steering unit 2003, the accelerator pedal 2004, the brake pedal 2005, the shift lever 2006, the front wheels 2007, the rear wheels 2008, and the axle 2009 provided in the vehicle 2001. , sensors 2021 to 2029 and the like may be controlled.

(Summary of embodiment)
As described above, according to one aspect of the present disclosure, a control unit that holds capability information regarding whether to repeatedly transmit an uplink message for a response message in a random access procedure, and whether to repeatedly transmit the uplink message a transmitting unit for transmitting capability information regarding to the base station.

According to the above configuration, the base station can determine whether the terminal supports repeated transmission of an uplink message (eg, Msg3 repetition) for a response message in a random access procedure based on the capability information obtained from the terminal. . As a result, even if the terminal does not request repeated transmission of the uplink message in the random access request, the base station determines whether the terminal repeats the uplink message based on the terminal capability information acquired after the communication connection is established. It is possible to determine whether or not transmission is supported, and to notify the terminal of an appropriate connection request for subsequent handover or the like.

Also, according to one aspect of the present disclosure, there is provided a wireless communication method performed by a terminal, comprising transmitting to a base station capability information regarding whether to repeatedly transmit an uplink message for a response message in a random access procedure. be.

According to the above configuration, the base station can determine whether the terminal supports repeated transmission of an uplink message (eg, Msg3 repetition) for a response message in a random access procedure based on the capability information obtained from the terminal. . As a result, even if the terminal does not request repeated transmission of the uplink message in the random access request, the base station determines whether the terminal repeats the uplink message based on the terminal capability information acquired after the communication connection is established. It is possible to determine whether or not transmission is supported, and to notify the terminal of an appropriate connection request for subsequent handover or the like.

Further, according to one aspect of the present disclosure, for a random access procedure instructed by a base station, a control unit that determines that an application condition regarding repeated transmission of an uplink message for a response message is satisfied; a transmitting unit for repeatedly transmitting said uplink message according to an interpretation of said response message corresponding to fulfillment.

According to the above configuration, the terminal, for the random access procedure instructed by the base station, when it is determined that a predetermined application condition regarding repeated transmission of an uplink message for a response message (for example, Msg3 repetition) is satisfied, the response message corresponding to the satisfaction of the applicable condition, and based on the interpreted response message, repeated transmission of the uplink message can be performed.

Further, according to one aspect of the present disclosure, for a random access procedure instructed by a base station, determining that an application condition regarding repeated transmission of an uplink message for a response message is satisfied, and satisfying the application condition and repeatedly transmitting said uplink message according to an interpretation of said response message corresponding to a wireless communication method performed by a terminal.

According to the above configuration, the terminal, for the random access procedure instructed by the base station, when it is determined that a predetermined application condition regarding repeated transmission of an uplink message for a response message (for example, Msg3 repetition) is satisfied, the response message corresponding to the satisfaction of the applicable condition, and based on the interpreted response message, repeated transmission of the uplink message can be performed.

Further, according to one aspect of the present disclosure, a control unit that determines that the application condition regarding repeated transmission of an uplink message for a response message in a random access procedure is satisfied, and a radio designated for downlink transmission by configuration information a transmitting unit for repeatedly transmitting said uplink message on overlapping radio resources.

According to the above configuration, the terminal can appropriately handle collisions between the downlink transmission specified in the setting information and the repeated transmission of the uplink message in response to the response message in the random access procedure.

Further, according to one aspect of the present disclosure, determining that the application condition regarding repeated transmission of the uplink message for the response message in the random access procedure is satisfied, and the radio resource specified for downlink transmission by the configuration information and repeatedly transmitting said uplink message on radio resources overlapping with .

According to the above configuration, the terminal can appropriately handle collisions between the downlink transmission specified in the setting information and the repeated transmission of the uplink message in response to the response message in the random access procedure.

(Supplement to the embodiment)
Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art can understand various modifications, modifications, alternatives, replacements, and the like. be. Although specific numerical examples have been used to facilitate understanding of the invention, these numerical values are merely examples and any appropriate values may be used unless otherwise specified. The division of items in the above description is not essential to the present invention, and the items described in two or more items may be used in combination as necessary, and the items described in one item may be used in another item. may apply (unless inconsistent) to the matters set forth in Boundaries of functional or processing units in functional block diagrams do not necessarily correspond to boundaries of physical components. The operations of a plurality of functional units may be physically performed by one component, or the operations of one functional unit may be physically performed by a plurality of components. As for the processing procedures described in the embodiments, the processing order may be changed as long as there is no contradiction. Although the wireless communication node 10 and the terminal 20 have been described using functional block diagrams for convenience of explanation of processing, such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor possessed by the wireless communication node 10 according to the embodiment of the present invention and the software operated by the processor possessed by the terminal 20 according to the embodiment of the present invention are respectively a random access memory (RAM), a flash memory, and a read-only memory. It may be stored in memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

(notification of information, signaling)
Notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, notification of information includes physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. RRC signaling may also be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.

(Applicable system)
Each aspect/embodiment described in the present disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark) )), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, other suitable systems, and extended It may be applied to at least one of the next generation systems. Also, a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G, etc.).

(Processing procedure, etc.)
The processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.

(Operation of IAB node)
Certain operations identified in this disclosure as being performed by an IAB node may also be performed by its upper node in some cases. In a network consisting of one or more network nodes with an IAB node, various operations performed for communication with a terminal may be performed by the IAB node and other network nodes other than the IAB node (e.g. MME or S-GW, etc. (including but not limited to). Although the above example illustrates the case where there is one network node other than the IAB node, it may be a combination of a plurality of other network nodes (for example, MME and S-GW).

(input/output direction)
Information and the like (*see the item “information, signal”) can be output from the upper layer (or lower layer) to the lower layer (or higher layer). It may be input and output via multiple network nodes.

(Handling of input/output information, etc.)
Input/output information and the like may be stored in a specific location (for example, memory), or may be managed using a management table. Input/output information and the like can be overwritten, updated, or appended. The output information and the like may be deleted. The entered information and the like may be transmitted to another device.

(Determination method)
The determination may be made by a value represented by one bit (0 or 1), by a true/false value (Boolean: true or false), or by numerical comparison (for example, a predetermined value).

(software)
Software, whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.

In addition, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, the software uses at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.) to website, Wired and/or wireless technologies are included within the definition of transmission medium when sent from a server or other remote source.

(information, signal)
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 refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of

The 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, the channel and/or symbols may be signaling. A signal may also be a message. A component carrier (CC) may also be called a carrier frequency, a cell, a frequency carrier, or the like.

("system", "network")
As used in this disclosure, the terms "system" and "network" are used interchangeably.

(parameter, channel name)
In addition, 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. may be represented. For example, radio resources may be indexed.

The names used for the parameters described above are not restrictive names in any respect. Further, the formulas, etc., using these parameters may differ from those expressly disclosed in this disclosure. Since the various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable designation, the various designations assigned to these various channels and information elements are in no way restrictive designations. isn't it.

(Base station (wireless base station))
In this disclosure, an IAB node has the functionality of a base station. "Base Station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point")","transmissionpoint","receptionpoint","transmission/receptionpoint","cell","sector","cellgroup","carrier"," Terms such as "component carrier" may be used interchangeably. A base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.

A base station can accommodate one or more (eg, three) cells. When a base station serves multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area being a base station subsystem (e.g., an indoor small base station (RRH: Communication services can also be provided by Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of at least one of the base stations and base station subsystems that serve communication within such coverage.

(terminal)
In this disclosure, terms such as “Mobile Station (MS),” “user terminal,” “User Equipment (UE),” “terminal,” etc. may be used interchangeably. .

A mobile station is defined by those skilled in the art as 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 It may also be called a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

(IAB node/mobile station)
IAB nodes and/or mobile stations may also be referred to as transmitters, receivers, communication devices, and/or the like. At least one of the IAB node and the mobile station may be a device mounted on a mobile, the mobile itself, or the like. The mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ). Note that at least one of the IAB node and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the IAB node and the mobile station may be an IoT (Internet of Things) device such as a sensor.

Also, the IAB node in the present disclosure may be read as a user terminal. For example, the communication between the IAB node and the user terminal, communication between multiple user terminals (eg, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc. may also be called) replaced Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the terminal 20 may have the functions of the IAB node 10 described above. Also, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be read as side channels.

Similarly, a terminal in the present disclosure may be read as an IAB node. In this case, the IAB node 10 may have the functions of the terminal 20 described above.

(Term meaning and interpretation)
As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Judgement", "determining" are, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (eg, lookup in a table, database, or other data structure); Also, "judgment" and "determination" are used for receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access (accessing) (for example, accessing data in memory) may include deeming that a "judgment" or "decision" has been made. In addition, "judgment" and "decision" are considered to be "judgment" and "decision" by resolving, selecting, choosing, establishing, comparing, etc. can contain. In other words, "judgment" and "decision" may include considering that some action is "judgment" and "decision". Also, "judgment (decision)" may be read as "assuming", "expecting", "considering", or the like.

The terms "connected", "coupled", or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, It can include the presence of one or more intermediate elements between two elements being "connected" or "coupled." Couplings or connections between elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access". As used in this disclosure, two elements are in the radio frequency domain using at least one of one or more wires, cables and printed electrical connections, and as some non-limiting and non-exhaustive examples. , electromagnetic energy having wavelengths in the microwave and optical (both visible and invisible) regions, and the like.

(reference signal)
The reference signal may be abbreviated as RS (Reference Signal), or may be referred to as Pilot according to the applicable standard.

(meaning "based on")
As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly specified otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

("first", "second")
Any reference to elements using the "first,""second," etc. designations used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, reference to a first and second element does not imply that only two elements can be employed or that the first element must precede the second element in any way.

(means)
The "unit" in the configuration of each device described above may be replaced with "means", "circuit", "device", or the like.

(open format)
Where "include,""including," and variations thereof are used in this disclosure, these terms are inclusive, as is the term "comprising." is intended. Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive OR.

(Time unit such as TTI, frequency unit such as RB, radio frame configuration)
A radio frame may consist of one or more frames in the time domain. Each frame or frames in the time domain may be referred to as a subframe. A subframe may also consist of one or more slots in the time domain. A subframe may be a fixed time length (eg, 1 ms) independent of numerology.

A numerology may be a communication parameter that applies to the transmission and/or reception of a signal or channel. Numerology, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, transmission and reception specific filtering operations performed by the receiver in the frequency domain, specific windowing operations performed by the transceiver in the time domain, and/or the like.

A slot may consist of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbol, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbol, etc.) in the time domain. A slot may be a unit of time based on numerology.

A slot may contain multiple mini-slots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in time units larger than a minislot may be referred to as PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.

Radio frames, subframes, slots, minislots and symbols all represent time units when transmitting signals. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations.

For example, one subframe may be called a Transmission Time Interval (TTI), a plurality of consecutive subframes may be called a TTI, and one slot or one minislot may be called a TTI. may That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms may be Note that the unit representing the TTI may be called a slot, mini-slot, or the like instead of a subframe.

Here, TTI refers to, for example, the minimum scheduling time unit in wireless communication. For example, in the LTE system, an IAB node performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis. Note that the definition of TTI is not limited to this.

A TTI may be a transmission time unit such as a channel-encoded data packet (transport block), code block, or codeword, or may be a processing unit such as scheduling and link adaptation. Note that when a TTI is given, the time interval (for example, the number of symbols) in which transport blocks, code blocks, codewords, etc. are actually mapped may be shorter than the TTI.

When one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum scheduling time unit. Also, the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, or the like. A TTI that is shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.

Note that the long TTI (e.g., normal TTI, subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms, and the short TTI (e.g., shortened TTI, etc.) is less than the TTI length of the long TTI and 1 ms A TTI having the above TTI length may be read instead.

A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in the RB may be the same regardless of the neumerology, eg twelve. The number of subcarriers included in an RB may be determined based on neumerology.

Also, the time domain of an RB may include one or more symbols and may be 1 slot, 1 minislot, 1 subframe, or 1 TTI long. One TTI, one subframe, etc. may each consist of one or more resource blocks.

One or more RBs are physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc. may be called.

Also, a resource block may be composed of one or more resource elements (RE: Resource Element). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

A bandwidth part (BWP) (which may also be called a bandwidth part) represents a subset of contiguous common resource blocks (RBs) for a certain numerology in a certain carrier. good. Here, the common RB may be identified by an RB index based on the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be configured in one carrier for a terminal.

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

The above structures such as radio frames, subframes, slots, minislots and symbols are only examples. For example, the number of subframes contained in a radio frame, the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, the number of Configurations such as the number of subcarriers, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. can be varied.

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

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 that "A and B are different from C". Terms such as "separate," "coupled," etc. may also be interpreted in the same manner as "different."

(Variation of mode, etc.)
Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching according to execution. In addition, the notification of predetermined information (for example, notification of “being X”) is not limited to being performed explicitly, but may be performed implicitly (for example, not notifying the predetermined information). good too.

Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in this disclosure. The present disclosure can be practiced with modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Accordingly, the description of the present disclosure is for illustrative purposes and is not meant to be limiting in any way.

10 wireless communication system 100 base station (gNB)
200 terminal (UE)

Claims (6)

1. A control unit that holds capability information regarding whether to repeatedly transmit an uplink message for a response message in a random access procedure;
   a transmitting unit configured to transmit capability information regarding whether to repeatedly transmit the uplink message to a base station;
   terminal with
2. A wireless communication method performed by a terminal, comprising transmitting to a base station capability information regarding whether or not to repeatedly transmit an uplink message to a response message in a random access procedure.
3. A control unit that determines that an application condition regarding repeated transmission of an uplink message in response to a response message is satisfied for a random access procedure instructed by a base station;
   a transmitter for repeatedly transmitting the uplink message according to the interpretation of the response message corresponding to the satisfaction of the applicable condition;
   terminal with
4. Determining that an application condition regarding repeated transmission of an uplink message in response to a response message is satisfied for a random access procedure instructed by a base station;
   repeatedly sending the uplink message according to an interpretation of the response message corresponding to the satisfaction of the applicable condition;
   A wireless communication method performed by a terminal, comprising:
5. A control unit that determines that an application condition regarding repeated transmission of an uplink message to a response message in a random access procedure is satisfied;
   a transmitter for repeatedly transmitting the uplink message on radio resources that overlap with radio resources designated for downlink transmission by configuration information;
   terminal with
6. Determining that an application condition for repeated transmission of uplink messages to response messages in a random access procedure is satisfied;
   repeatedly transmitting the uplink message on radio resources that overlap with radio resources designated for downlink transmission by configuration information;
   A wireless communication method performed by a terminal, comprising:

Images