Terminal and wireless communication method

Abstract

To provide a terminal and a wireless communication method that appropriately perform repeated transmission of a message (Msg3) in a random access channel procedure.SOLUTION: In a wireless communication system, a terminal 200 includes: a receiving unit that receives setting information including the index and number of preambles requesting repeated transmission of a physical uplink shared channel in a random access channel procedure via a wireless resource control layer; a control unit that determines transmission of the preambles on the basis of the index and the number of preambles; and a transmitting unit that performs repeated transmission of the physical uplink shared channel. The control unit determines a threshold for RSRP (Reference Signal Received Power) on the basis of the setting of the wireless resource control layer, and determines the transmission of the preambles on the basis of the threshold for the RSRP.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to a terminal and a wireless communication method that support message repetition in a random access channel procedure. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has developed specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] For example, in 3GPP Release-17, a work item on Coverage Enhancement (CE) in NR has been agreed upon (Non-Patent Document 1).

[0004] Specifically, studies are underway on the specifications for repetition of an uplink data channel (Physical Uplink Shared Channel: PUSCH) used to transmit a message (Msg3) in a random access channel (Random Access Channel: RACH) procedure. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] "New WID on NR coverage enhancements", RP-202928, 3GPP TSG RAN meeting #90e, 3GPP, December 2020 Summary of the Invention

[0006] When repetition of the message (Msg3) of the RACH procedure is supported, there is thought to be room for improvement in the specific operation of the terminal (User Equipment, UE) regarding repetition.

[0007] The following disclosure has been made in light of the above circumstances, and aims to provide a terminal and a wireless communication method that can perform more appropriate operations regarding the repetition of the message (Msg3) of the RACH procedure.

[0008] One aspect of the present disclosure is a terminal (UE200) that includes a transmitting unit (radio signal transmitting / receiving unit 210) that repeatedly transmits a message in a random access channel procedure, and a control unit (control unit 270) that sets resources for random access depending on whether or not the repeated transmission is to be performed based on the setting of a radio resource control layer.

[0009] One aspect of the present disclosure is a terminal (UE200) that includes a transmitter (radio signal transmitter / receiver 210) that repeatedly transmits a message in a random access channel procedure, and a control unit (control unit 270) that uses demodulation reference signals assigned to multiple slots to report to a network whether channel estimation of an uplink channel assigned to the multiple slots is applicable to the message.

[0010] One aspect of the present disclosure is a terminal (UE200) that includes a transmitting unit (radio signal transmitting / receiving unit 210) that repeatedly transmits a message in a random access channel procedure, and a control unit (control unit 270) that requests the repeated transmission based on whether or not certain conditions related to random access are met.

[0011] One aspect of the present disclosure is a terminal (UE200) comprising a transmitter (radio signal transceiver 210) that repeatedly transmits a message in a random access channel procedure, and a control unit (control unit 270) that sets a redundancy version of an automatic repeat request to be applied to the transmission of the message based on a setting in a radio resource control layer or a specific criterion.

[0012] One aspect of the present disclosure is a wireless communication method including a step of repeatedly transmitting a message in a random access channel procedure, and a step of setting a random access resource depending on whether or not the repeated transmission is to be performed based on a setting of a radio resource control layer.

[0013] One aspect of the present disclosure is a wireless communication method including: repeatedly transmitting a message in a random access channel procedure; and reporting to a network, using demodulation reference signals assigned to a plurality of slots, whether channel estimation of an uplink channel assigned to the plurality of slots is applicable to the message. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10. As shown in FIG. [Figure 2] FIG. 2 is a diagram showing an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. As shown in FIG. [Figure 3] Figure 3 is a functional block diagram of gNB100 and UE200. [Figure 4] FIG. 4 is a diagram showing an example of a random access sequence including a repetition of Msg3. [Figure 5] FIG. 5 is a diagram showing an example of a random access sequence including an initial transmission and a retransmission of Msg3. [Figure 6] FIG. 6 is a diagram showing an example of correspondence between RACH Occasion and whether Msg3 Repetition is required / supported according to the first operation example. [Figure 7] FIG. 7 is a diagram showing an example of correspondence between the RACH preamble and whether or not Msg3 Repetition is required / supported according to the first operation example. [Figure 8]FIG. 8 is a diagram illustrating a configuration example (part 1) of a PRACH preamble according to the first operation example. [Figure 9] FIG. 9 is a diagram illustrating a configuration example (part 2) of a PRACH preamble according to the first operation example. [Figure 10] FIG. 10 is a diagram illustrating a configuration example (part 3) of a PRACH preamble according to the first operation example. [Figure 11] FIG. 11 is a diagram illustrating a configuration example (part 4) of a PRACH preamble according to the first operation example. [Figure 12] FIG. 12 is a diagram illustrating an example of the configuration of a Random Access Preamble Group according to the first operation example. [Figure 13] FIG. 13 is a diagram illustrating a configuration example (part 1) of PRACH resources in the frequency direction according to the first operation example. [Figure 14] FIG. 14 is a diagram illustrating a configuration example (part 2) of PRACH resources in the frequency direction according to the first operation example. [Figure 15] FIG. 15 is a diagram illustrating a setting example (part 1) of the PRACH Configuration for Msg3 Repetition according to the first operation example. [Figure 16] FIG. 16 is a diagram illustrating a setting example (part 2) of the PRACH Configuration for Msg3 Repetition according to the first operation example. [Figure 17] FIG. 17 is a diagram illustrating an example of power ramping according to the third operation example. [Figure 18] FIG. 18 is a diagram showing an application example (part 1) of RV id in a transmission occasion according to the fourth operation example. [Figure 19] FIG. 19 is a diagram showing an application example (part 2) of RV id in a transmission occasion according to the fourth operation example. [Figure 20] FIG. 20 is a diagram showing an example of the hardware configuration of gNB100 and UE200. DETAILED DESCRIPTION OF THE INVENTION

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

[0016] (1) Overall configuration of wireless communication system 1 is a schematic diagram of the overall configuration of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (User Equipment 200, hereinafter, UE 200).

[0017] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.

[0018] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG.

[0019] The 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). The NG-RAN 20 and the 5GC may also be simply referred to as a "network."

[0020] The gNB 100 is a radio base station that complies with NR and performs NR-compliant radio communication with the UE 200. The gNB 100 and the UE 200 are capable of supporting Massive MIMO, which generates a more directional beam (BM) by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and multiple NG-RAN nodes.

[0021] The wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR (Frequency Range) are as follows:

[0022] FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz~52.6 GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 or 120 kHz (including 240 kHz) and a bandwidth (BW) of 50 to 400 MHz.

[0023] Furthermore, the wireless communication system 10 may also support frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 may support frequency bands above 52.6 GHz up to 114.25 GHz.

[0024] Alternatively, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) may be applied. Furthermore, DFT-S-OFDM may be applied not only to the uplink (UL) but also to the downlink (DL).

[0025] FIG. 2 shows an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. In FIG.

[0026] As shown in Figure 2, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). Note that the number of symbols constituting one slot does not necessarily have to be 14 symbols (e.g., 28 or 56 symbols). The number of slots per subframe may differ depending on the SCS. Furthermore, the SCS may be wider than 240 kHz (e.g., 480 kHz or 960 kHz as shown in Figure 2).

[0027] 2 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 BWP (Bandwidth part), etc.

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

[0029] For example, gNB100 can support repeated transmission of PDSCH (Physical Downlink Shared Channel), and UE200 can support repeated transmission of PUSCH (Physical Uplink Shared Channel).

[0030] Furthermore, multiple types of UEs 200 may be used in the wireless communication system 10. For example, the UEs 200 may be multiple types of terminals with different functions or performance, or that support different 3GPP releases. The terminals (UEs) may be referred to as a first type terminal and a second type terminal. Furthermore, the term "type" may be replaced with other terms such as generation or release. The first type terminal and the second type terminal may be referred to as an enhanced UE and a legacy UE, respectively. An enhanced UE may be interpreted as a UE that supports the latest release of 3GPP, and a legacy UE may be interpreted as a UE that does not support the latest release.

[0031] A slot configuration pattern for time division duplexing (TDD) may be set in the wireless communication system 10. For example, DDDSU (D: downlink (DL symbol, S: DL / uplink (UL) or guard symbol, U: UL symbol) may be specified (see 3GPP TS38.101-4).

[0032] "D" indicates a slot containing all DL symbols, "S" indicates a slot containing a mixture of DL, UL, and guard symbols (G), and "U" indicates a slot containing all UL symbols.

[0033] (2) Functional block configuration of wireless communication system Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, a functional block configuration of the UE 200 will be described. FIG. 3 is a functional block configuration diagram of the gNB 100 and the UE 200.

[0034] As shown in FIG. 3, UE 200 includes a radio signal transmitting / receiving unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmitting / receiving unit 260, and a control unit 270.

[0035] It should be noted that Fig. 3 shows only the main functional blocks relevant to the description of the embodiment, and that the UE 200 (gNB 100) has other functional blocks (e.g., a power supply unit, etc.). Fig. 3 shows the functional block configuration of the UE 200, and for the hardware configuration, please refer to Fig. 20.

[0036] The radio signal transmitting and receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting and receiving unit 210 can support Massive MIMO, which generates a more directional beam by controlling radio (RF) signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between a UE and two NG-RAN nodes.

[0037] Furthermore, the radio signal transceiver 210 may transmit a physical uplink shared channel. Specifically, the radio signal transceiver 210 may transmit a PUSCH to the network (gNB 100). The radio signal transceiver 210 may support repetitive transmission of the PUSCH.

[0038] A plurality of types of repeated transmission of the 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 a slot is repeatedly transmitted. In other words, the PUSCH is 14 symbols or less and is not likely to be allocated across multiple slots (adjacent slots).

[0039] On the other hand, Repetition type B may be interpreted as repeated transmission of a PUSCH in which a PUSCH of 15 symbols or more may be allocated. In this embodiment, it may be permitted to allocate such a PUSCH across multiple slots.

[0040] Furthermore, the radio signal transmitting and receiving unit 210 may transmit a random access preamble as a first message (hereinafter, Msg1) in a random access channel procedure (hereinafter, RACH (Random Access Channel) procedure).

[0041] The radio signal transmitting and receiving unit 210 may receive a second message (hereinafter, Msg2) as a response message (random access response (RAR)) to Msg1 in the RACH procedure.

[0042] After receiving Msg2, the radio signal transmitting and receiving unit 210 may transmit a third message (hereinafter, Msg3) via the PUSCH in the RACH procedure.

[0043] The radio signal transceiver 210 may receive a fourth message (hereinafter, Msg4) as a response message to Msg3 in the RACH procedure (3GPP TS38.321 V16.2.1 §5.1 "Random Access procedure").

[0044] For example, Msg1 may be transmitted via a PRACH (Physical Random Access Channel). Msg1 may be referred to as a PRACH Preamble. Msg2 may be transmitted via a PDSCH. Msg2 may be referred to as a RAR (Random Access Response). Msg3 may be referred to as an RRC Connection Request. Msg4 may be referred to as an RRC Connection Setup.

[0045] Msg3 may also be referred to as a PUSCH scheduled by an RAR UL grant or a PUSCH scheduled by a DCI scrambled by a Temporary Cell - Radio Network Temporary Identifier (TC-RNTI).

[0046] The radio signal transmitting / receiving unit 210 executes repeated transmission of Msg3. In this embodiment, the radio signal transmitting / receiving unit 210 may constitute a transmitting unit that repeatedly transmits a message in the random access channel procedure. The repeated transmission of Msg3 will be described in detail later.

[0047] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0048] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (e.g., gNB 100). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for uplink (UL) but also for downlink (DL).

[0049] The control signal / reference signal processor 240 performs processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0050] Specifically, the control signal / reference signal processor 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. The control signal / reference signal processor 240 also transmits various control signals to the gNB 100 via a predetermined control channel.

[0051] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0052] DMRS (Demodulation Reference Signal) is a reference signal (pilot signal) known between the base station and the terminal for estimating the fading channel used for data demodulation. PTRS is a terminal-specific reference signal for estimating phase noise, which is an issue in high frequency bands.

[0053] In addition to the DMRS and PTRS, the reference signals may include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0054] The channels include a control channel and a data channel. The control channels may include a PDCCH (Physical Downlink Control Channel), a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel, Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI)), a Physical Broadcast Channel (PBCH), etc.

[0055] Furthermore, the data channel includes a PDSCH (Physical Downlink Shared Channel), a PUSCH (Physical Uplink Shared Channel), etc. Data may refer to data transmitted via a data channel.

[0056] Furthermore, the control signal and reference signal processor 240 may transmit capability information of the UE 200 regarding allocation of the Physical Uplink Shared Channel (PUSCH) to the network.

[0057] Specifically, the control signal and reference signal processing unit 240 can transmit UE capability information related to PUSCH allocation (which may include repetition) to the gNB 100. Details of the UE capability information will be described later.

[0058] Furthermore, control signal and reference signal processing unit 240 may transmit a DMRS so that joint channel estimation (described later) can be performed between specific PUSCHs, between PUCCHs, or between a PUSCH and a PUCCH. This period may be called a time domain window.

[0059] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or another gNB).

[0060] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0061] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (Hybrid ARQ).

[0062] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 executes control related to the repetition of the PUSCH for Msg3 (hereinafter, appropriately abbreviated as Msg3 PUSCH).

[0063] Specifically, the control unit 270 can set random access resources depending on whether or not repeated transmission of Msg3 is performed, based on the configuration of the radio resource control layer (RRC). For example, the control unit 270 can use different PRACH resources / sequences depending on whether or not repeated transmission of Msg3 PUSCH (which may be read as Msg3 Repetition) is required or supported.

[0064] A request for repeated transmission of Msg3 PUSCH may mean that UE 200 is requested to perform repetition of Msg3 (PUSCH) or that UE 200 is instructed by the network to perform repetition of Msg3 (PUSCH).

[0065] Whether or not repeated transmission of Msg3 PUSCH is supported may mean whether or not UE 200 is capable of the repeated transmission, that is, whether or not UE 200 has the capability of the repeated transmission.

[0066] For example, the control unit 270 may set the PRACH preamble when Msg3 Repetition is requested / supported based on the RRC settings.

[0067] Furthermore, the control unit 270 may add a PRACH occasion (RO) when Msg3 Repetition is requested / supported based on the RRC configuration.

[0068] In this way, the control unit 270 may determine (decide) the PRACH resource / sequence corresponding to whether or not Msg3 Repetition is requested / supported based on the RRC configuration.

[0069] A specific example of the operation of UE 200 when requesting / supporting Msg3 Repetition will be described later.

[0070] Furthermore, the control unit 270 may report to the network (gNB 100) whether or not joint channel estimation is applicable, via Msg3. Joint channel estimation may be interpreted as a technique for performing channel estimation based on DMRSs present (allocated) in multiple slots.

[0071] That is, the control unit 270 may use a DMRS (demodulation reference signal) allocated to multiple slots to report to the network whether channel estimation of an uplink channel allocated to multiple slots can be applied to a specific message such as Msg3.

[0072] Furthermore, the control unit 270 may request repeated transmission of Msg3 based on whether a specific condition related to random access is satisfied. Specifically, the control unit 270 may determine the condition for requesting Msg3 Repetition based on a specific condition (which may be a rule) or a parameter set by RRC.

[0073] The specific condition may be set based on parameters such as the reception quality of a synchronization signal block (SSB (Synchronization Signal) / PBCH (Physical Broadcast CHannel) Block) (e.g., RSRP (Reference Signal Received Power), the number of transmission attempts of Msg 1, the total power value after power ramping, etc.). Note that the specific condition is not limited to the parameters, and may be any parameter related to the random access procedure, such as quality, power value, number of transmissions, etc.

[0074] Furthermore, the control unit 270 may set a redundancy version of an automatic repeat request to be applied to transmission of a message related to a random access procedure such as Msg3 based on a setting of a radio resource control layer (RRC) or a specific criterion.

[0075] Specifically, the control unit 270 may apply identification information (id) of a redundancy version (RV) of HARQ (Hybrid Automatic Repeat Request) at each transmission occasion based on a predetermined rule applied to Msg3 repetition or a parameter set by RRC, and transmit the message. RV id may be set to, for example, RV0, RV1, RV2, or RV3. RVs may be associated with different starting positions of the circular buffer.

[0076] In this case, control section 270 may apply (set) an RV that is the same as or different from that of the PUSCH scheduled by the RAR UL grant or the PUSCH scheduled by the DCI scrambled by TC-RNTI.

[0077] (3) Operation of the wireless communication system Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of the operation relating to the repetition of the message (Msg3) of the RACH procedure.

[0078] (3.1) Premise Figure 4 shows an example of a random access sequence including a repetition of Msg3. As shown in Figure 4, the UE 200 first transmits Msg1 to the NG-RAN 20 (gNB 100) according to the RACH procedure. Msg1 may be referred to as a random access preamble, as described above.

[0079] The UE 200 receives Msg2 corresponding to Msg1 from the NG-RAN 20. The UE 200 transmits Msg3 corresponding to Msg2 to the NG-RAN 20. As shown in Fig. 4, Msg3 may be transmitted repeatedly. Although not shown, Msg1 and the like may also be transmitted repeatedly.

[0080] The UE 200 may receive Msg4 in response to any one of Msg3 from the NG-RAN 20. The UE 200 may transmit an acknowledgement (HARQ (Hybrid Automatic repeat request)-ACK) in response to Msg4 to the NG-RAN 20.

[0081] FIG. 5 shows an example of a random access sequence including an initial transmission and a re-transmission of Msg3.

[0082] The 3GPP specifications prescribe re-transmission of Msg3 as shown in Fig. 5. Re-transmission of Msg3 may be performed when the initial transmission of Msg3 fails (when the network side cannot receive it).

[0083] For the re-transmission of Msg3, resources may be allocated by DCI format 0_0 with CRC scrambled by TC-RNTI.

[0084] The repetition of the PUSCH used for transmitting Msg3 (which may include retransmission) may be related to the Type A PUSCH repetition.

[0085] Existing PUSCH mapping types include Type A and Type B. Type A is used only for repetition Type A, while Type B may be used for both repetition Type A and repetition Type B. Existing Types A and B assume allocation in slot units, so the value of L does not need to exceed "14" (the number of symbols) (see §6.1.2 of 3GPP TS38.214 V16.2.0).

[0086] (3.2) Operation overview Below, operation examples 1 to 4 regarding the repetition of Msg3 (or PUSCH) will be explained.

[0087] (Operation example 1): UE 200 uses PRACH resources corresponding to whether Msg3 Repetition is required / supported based on the RRC configuration. (Operation Example 2): The UE 200 reports to Msg3 whether or not joint channel estimation is applicable.

[0088] (Operation Example 3): The UE 200 determines the condition for requesting Msg3Repetition based on a predetermined rule or a parameter set by the RRC. (Operation Example 4): During Msg3Repetition, the UE 200 transmits a message by applying the RV id for each transmission occasion based on a predetermined rule or parameters set by the RRC.

[0089] (3.3) Example 1 In this operation example, an operation will be described in which the UE 200 uses a PRACH resource corresponding to whether or not Msg3 Repetition is required / supported based on the RRC configuration.

[0090] Specifically, UE 200 may use different PRACH resources / sequences depending on whether Msg3Repetition is required / supported.

[0091] Fig. 6 shows an example of correspondence between RACH Occasion and whether Msg3 Repetition is requested / supported according to operation example 1. Fig. 7 shows an example of correspondence between RACH preamble and whether Msg3 Repetition is requested / supported according to operation example 1.

[0092] For example, the UE 200 may transmit the PRACH in different PRACH preambles and / or RACH occasions (ROs, time or frequency) depending on the requirement / support.

[0093] Furthermore, the UE 200 may specify the PRACH preamble and / or the RO depending on the presence or absence of the request / support based on a predetermined rule.

[0094] Alternatively, the UE 200 may specify the PRACH preamble and / or the RO depending on the presence or absence of the request / support based on the RRC configuration. Note that, if based on a predetermined rule, the same operation may be performed regardless of the presence or absence of the RRC parameter configuration.

[0095] When the UE 200 identifies the PRACH preamble and / or the RO depending on the presence / absence of the request / support based on the RRC configuration, the UE 200 may operate as follows.

[0096] (Opt1): Set PRACH preamble when Msg3 Repetition is required / supported (Opt1-1): Set the preamble index when Msg3 Repetition is required / supported Specifically, the number of PRACH preambles that request / support Msg3 Repetition may be specified. For example, UE 200 may set a parameter (e.g., CBForMsg3Repetition-PreamblesPerSSB-PerSharedRO (tentative name)) that indicates the number of PRACH preambles when Msg3 Repetition is requested / supported in RACH-ConfigCommon IE or the like. In this case, as shown in FIG. 8 (part 1) or FIG. 9 (part 2), the order in which preamble indexes are assigned may be determined by a predetermined rule or RRC configuration.

[0097] FIG. 8 shows a configuration example (part 1) of a PRACH preamble according to the first operation example, and FIG. 9 shows a configuration example (part 2) of a PRACH preamble according to the first operation example.

[0098] In this case, the number of PRACH preambles that require / support Msg3 Repetition may be specified. For example, an RRC parameter that specifies each SSB index and preamble index may be set.

[0099] As shown in FIG. 8, the start index of the PRACH preamble that requests / supports Msg3 Repetition may be determined from the number of preamble indexes in each case.

[0100] In the case of (Opt1), the preamble index applied when Msg3 Repetition is requested / supported may be a preamble that is part of the contention-based random access (CBRA) for 3GPP Releases 15 and 16. Alternatively, the preamble index when Msg3 Repetition is requested / supported may be a preamble that is allocated separately from the CBRA for 3GPP Releases 15 and 16.

[0101] FIG. 10 shows a third example of the configuration of the PRACH preamble according to the first operation example, and FIG. 11 shows a fourth example of the configuration of the PRACH preamble according to the first operation example.

[0102] In the example of FIG. 10, a portion of the CBRA RACH preamble specified by totalNumberOfRA-Preambles may be allocated for requesting / supporting Msg3 Repetition.

[0103] In the example of FIG. 11, a RACH preamble may be allocated for requesting / supporting Msg3 Repetition, apart from the CBRA RACH preamble specified by totalNumberOfRA-Preambles.

[0104] (Opt1-2): Set the Random access preamble group that requires / supports Msg3 Repetition 12 shows an example of the configuration of a random access preamble group according to operation example 1. As shown in FIG. 12, in addition to Groups A and B, a new random access preamble group (Group C) may be added.

[0105] Alternatively, a parameter (tentative name: numberOfRA-PreamblesGroupC) that specifies the number of preambles in Group C may be set, and it may be determined which preamble index corresponds to that group.

[0106] When adding a new random access preamble group (Group C), for example, Group A or Group B may not be used. The index of Group C or B may be specified by setting the number of preamble indexes of Group B or C.

[0107] Also, the preamble of Group A or B may be used for a random access preamble group that requests / supports Msg3 Repetition. For example, Group A or B may be set as a random access preamble group that requests / supports Msg3 Repetition by an RRC parameter.

[0108] (Opt2): Add PRACH transmission occasions when Msg3 Repetition is required / supported (Opt2-1): Add PRACH resources when requesting / supporting Msg3 Repetition in the frequency direction 13 shows a configuration example (part 1) of PRACH resources in the frequency direction according to operation example 1. As shown in FIG. 13, for example, UE 200 may set a parameter (e.g., msg1-FDMForMsg3Repetition ENUMERATED {one, two, four, eight}) representing the number of time division multiplexed (FDM) PRACH transmission occasions when Msg3 Repetition is requested / supported, in a RACH-ConfigGeneric IE or the like. In this case, the number of SSBs for each added PRACH transmission occasion may be set.

[0109] In this case, Msg1-FDM may refer to the FDM number of all PRACH transmission occasions that do not require / support Msg3 Repetition.

[0110] Furthermore, as shown in FIG. 13, it may be determined that resources requiring / supporting Msg3 Repetition exist above, below, and above and below resources requiring / not supporting Msg3 Repetition in the frequency direction.

[0111] (Opt2-2): In the frequency direction, divide the PRACH resources depending on whether Msg3 Repetition is required / supported Fig. 14 illustrates a configuration example (part 2) of PRACH resources in the frequency direction according to operation example 1. As illustrated in Fig. 14, for example, UE 200 may set, in RACH-ConfigGeneric IE or the like, a parameter indicating the number of FDM-modulated PRACH transmission occasions when Msg3 Repetition is requested / supported, and a parameter indicating the total number of FDM-modulated PRACH transmission occasions.

[0112] In this case, Msg1-FDM may refer to the number of FDMs for all PRACH transmission occasions.

[0113] Furthermore, as shown in FIG. 14, it may be determined that resources requiring / supporting Msg3 Repetition exist above, below, or above and below the resource requiring / not supporting Msg3 Repetition.

[0114] (Opt2-3): Add PRACH resources when requesting / supporting Msg3 Repetition in the time direction (Alt1): Set a different PRACH Configuration for PRACH when Msg3 Repetition is required / supported Fig. 15 shows a setting example (part 1) of the PRACH configuration for Msg3 Repetition according to operation example 1. As shown in Fig. 15, a unique PRACH configuration may be set for the PRACH when Msg3 Repetition is requested / supported.

[0115] For example, the UE 200 may set a parameter (e.g., prachForMsg3Reptition-ConfigurationIndex INTEGER (0..255), (tentative name)) that specifies a PRACH Configuration when requesting / supporting Msg3 Repetition in the RACH-ConfigGeneric IE. In this case, some parameters (such as formats) may be shared with other PRACH Configurations.

[0116] (Alt2): Set the PRACH time resource to 4-step CBRA, 2-step CBRA, or contention-free random access (CFRA) PRACH configuration when Msg3 Repetition is requested / supported. FIG. 16 shows a second example of setting the PRACH Configuration for Msg3 Repetition according to the first operation example.

[0117] For example, the UE 200 may add the PRACH time resource when Msg3 Repetition is requested / supported to the RACH-ConfigGeneric IE, or may implicitly determine the resource. Specifically, as shown in Fig. 16, the PRACH time resource when Msg3 Repetition is requested / supported (Starting symbol and / or subframe number for Msg3 Repetition) may be added.

[0118] (3.4) Example 2 In this operation example, an operation in which the UE 200 reports to Msg3 whether or not joint channel estimation is applicable will be described.

[0119] When transmitting Msg3Repetition, UE 200 may transmit the DMRS so that joint channel estimation between slots can be performed (for example, the DMRS may be transmitted so that the power / phase of the DMRS is constant).

[0120] The UE 200 may report whether or not joint channel estimation is applicable to the Msg 3 by the Msg 1. In this case, the UE 200 may identify a PRACH preamble and / or a RACH occasion according to whether or not the request / support is present based on a predetermined rule. If based on the predetermined rule, the UE 200 may identify a PRACH preamble and / or a RACH occasion by the same method as in the first operation example, regardless of whether or not the RRC parameters are configured.

[0121] In addition, UE200 may report whether joint channel estimation is applicable only when the network (gNB100) reports via SIB1 that gNB100 supports joint channel estimation.

[0122] The network (gNB100) may determine that joint channel estimation is also applicable if Msg3Repetition is supported. The UE 200 may identify a PRACH preamble and / or a RACH occasion depending on whether or not the Msg3Repetition is required / supported based on the RRC configuration (the UE 200 may configure a PRACH depending on whether or not joint channel estimation is required / supported, using the same method as in the first operation example).

[0123] Alternatively, whether or not joint channel estimation is applicable may be reported in Msg3. In this case, UE 200 may transmit DMRS using different DMRS ports depending on whether or not joint channel estimation is required / supported. UE 200 may also determine whether a DMRS port supports or requires joint channel estimation based on System Information Block (SIB) 1 or a predetermined rule.

[0124] The UE 200 may multiplex uplink control information (UCI) for determining whether or not the Joint Channel Estimation is required / supported into the Msg 3 and transmit the same. In this case, the UE 200 may determine whether or not to report the Joint Channel Estimation request / support by the UCI based on the SIB 1 or a predetermined rule.

[0125] (3.5) Example 3 In this operation example, an operation will be described in which the UE 200 determines the condition for requesting Msg3 Repetition based on a predetermined rule or a parameter set by the RRC.

[0126] For example, UE 200 may determine whether to request Msg3 Repetition based on the following conditions (which may be combined):

[0127] (Opt1): SSB RSRP (or distance attenuation calculated based on SSB) exceeds the threshold In this case, the threshold value of RSRP (or distance attenuation amount) may be determined based on a predetermined rule or RRC setting.

[0128] (Opt2): The number of attempts to send Msg1 exceeds the threshold. In this case, the threshold number of transmission attempts may be determined based on a predetermined rule or RRC setting.

[0129] (Opt3): Power ramp-up total power value exceeds the threshold In this case, the threshold value of the total power value for which power is ramped up may be determined based on a predetermined rule or RRC settings.

[0130] Fig. 17 shows an example of power ramping according to operation example 3. As shown in Fig. 17, an Msg related to the PRACH or PUSCH is retransmitted, and power is ramped for each retransmission, but if the amount of power ramp-up exceeds a threshold, Msg3 Repetition may be applied.

[0131] (3.6) Example 4 In this operation example, an operation will be described in which the UE 200 transmits a message by applying the RV id for each transmission occasion based on a predetermined rule or parameters set by RRC during Msg3 Repetition.

[0132] The UE 200 may apply the RV id for each transmission occasion and transmit the Msg3Repetition based on a predetermined rule or a parameter set by the RRC.

[0133] In this case, the UE 200 may apply (set) an RV that is the same as or different from the RV of the PUSCH scheduled by the RAR UL grant or the PUSCH scheduled by the DCI scrambled by TC-RNTI.

[0134] Fig. 18 shows an application example (part 1) of RV id in transmission occasions according to operation example 4. Fig. 18 shows examples of Opt1 to Opt4.

[0135] The UE 200 may apply any RV id to transmit in each transmission occasion (for example, initial transmission (PUSCH scheduled by an RAR UL grant)).

[0136] The RV id of any one of the tables (Opt1 to Opt4) to be applied may be set by RRC or a predetermined rule. In this case, different tables may be applied depending on the time division duplex (TDD) pattern.

[0137] Fig. 19 shows an application example (part 2) of RV id in transmission occasions according to operation example 4. Fig. 19 shows examples of Opt1 to Opt3.

[0138] The UE 200 may apply any RV id to transmission in each transmission occasion (for example, re-transmission (PUSCH scheduled with DCI scrambled by TC-RNTI)).

[0139] (4) Actions and Effects According to the above-described embodiment, the following advantageous effects can be obtained: Specifically, the UE 200 can set random access resources according to the presence or absence of Msg3 Repetition based on the RRC configuration.

[0140] Furthermore, the UE 200 can use the DMRSs allocated to a plurality of slots to report to the network whether or not joint channel estimation of the uplink channels allocated to the plurality of slots can be applied to the Msg3.

[0141] In addition, UE200 can request Msg3 Repetition based on whether certain conditions regarding random access are met, and can set the RV id to be applied to the transmission of Msg3 based on RRC settings or certain criteria.

[0142] This makes it possible to make the operation of the UE 200 more efficient and rational during Msg3 Repetition, i.e., the UE 200 can perform more appropriate operations regarding the repetition of the message (Msg3) of the RACH procedure.

[0143] (5) Other embodiments Although the embodiments have been described above, it will be obvious to those skilled in the art that the present invention is not limited to the description of the embodiments and that various modifications and improvements are possible.

[0144] For example, in the above-described embodiment, an embodiment regarding the repetition of Msg3 and PUSCH has been described, but the above-described operation regarding repetition may be applied to messages in the RACH procedure or other uplink channels.

[0145] Furthermore, the PUSCH may be called a physical uplink shared channel, and may not necessarily be a PUSCH as long as it is a channel (physical channel) shared by a plurality of UEs 200 (users) in the UL.

[0146] Also, in the above description, "configure," "activate," "update," "indicate," "enable," "specify," and "select" may be interchangeable. Similarly, "link," "associate," "correspond," and "map" may be interchangeable, and "allocate," "assign," "monitor," and "map" may also be interchangeable.

[0147] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0148] The block diagram (FIG. 3) used in the description of the above-described embodiment shows functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. The method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or multiple devices with software.

[0149] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0150] Furthermore, the above-described gNB100 and UE200 (the device) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 20 is a diagram showing an example of the hardware configuration of the device. As shown in Figure 20, the device may 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, etc.

[0151] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0152] Each functional block of the device (see FIG. 3) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0153] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0154] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.

[0155] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments. Furthermore, the various processes described above may be executed by one processor 1001, or may 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.

[0156] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc., that can execute a method according to an embodiment of the present disclosure.

[0157] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-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, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0158] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0159] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

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

[0161] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to 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.

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

[0163] Furthermore, 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), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0164] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G) may also be applied.

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

[0166] In the present disclosure, a specific operation described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, an MME or an S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

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

[0168] The input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added to. The output information may be deleted. The input information may be sent to another device.

[0169] 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).

[0170] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

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

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

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

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

[0175] As used in this disclosure, the terms "system" and "network" are used interchangeably.

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

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

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

[0179] A base station can accommodate one or more (e.g., three) cells (also called sectors). 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 services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0180] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

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

[0182] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

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

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

[0185] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station. A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0186] Numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by a transceiver in the frequency domain, and specific windowing operations performed by a transceiver in the time domain.

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

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

[0189] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

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

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

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

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

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

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

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

[0197] The time domain of an RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. Each TTI, subframe, etc. may be composed of one or more resource blocks.

[0198] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

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

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

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

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

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

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

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

[0206] 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."

[0207] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0208] 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 therein or that the first element must precede the second element in some way.

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

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

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

[0212] 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."

[0213] 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 herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0214] 10. Wireless communication systems 20 NG-RAN 100 gNB 200 UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and Demodulation Unit 240 Control signal / reference signal processing section 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 processor 1002 memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output Device 1007 Bus

Claims

1. a receiving unit that receives, via a radio resource control layer, configuration information including an index of a preamble requesting repeated transmission of a physical uplink shared channel in a random access procedure and the number of the preambles; a control unit that determines transmission of the preamble based on the index and the number of preambles; a transmitter that repeatedly transmits the physical uplink shared channel; Equipped with The control unit determining an RSRP threshold based on the configuration of the radio resource control layer; determining transmission of the preamble based on the RSRP threshold; Terminal.

2. The index is the start index of the preamble. The terminal according to claim 1 .

3. A wireless communication system including a base station and a terminal, the base station comprises a transmitter configured to transmit, via a radio resource control layer, configuration information including an index of a preamble requesting repeated transmission of a physical uplink shared channel in a random access procedure and the number of the preambles; The terminal a receiving unit that receives the setting information; a control unit that determines transmission of the preamble based on the index and the number of preambles; a transmitter that repeatedly transmits the physical uplink shared channel; Equipped with The control unit determining an RSRP threshold based on the configuration of the radio resource control layer; determining transmission of the preamble based on the RSRP threshold; Wireless communication system.

4. A wireless communication method performed by a terminal, receiving, via a radio resource control layer, configuration information including an index of a preamble requesting repeated transmission of a physical uplink shared channel in a random access procedure and the number of the preambles; determining transmission of the preamble based on the index and the number of preambles; determining an RSRP threshold based on the configuration of the radio resource control layer; determining whether to transmit the preamble based on the RSRP threshold; performing repeated transmission of the physical uplink shared channel; Wireless communication method.

Images