Terminal and wireless communication method

Abstract

A terminal includes: a reception unit for receiving configuration information related to a physical uplink control channel for a contention resolution message in a random access procedure; and a control unit for identifying a number of resources for the physical uplink control channel on the basis of the configuration information, the number of resources being greater than 16. The configuration information is at least one of first configuration information for a terminal reduced in capability or second configuration information for a terminal other than the terminal.

Description

Terminal and wireless communication method

[0001] The present disclosure relates to a terminal and a wireless communication method for transmitting a physical uplink control channel for a contention resolution message in a random access procedure.

[0002] The 3rd Generation Partnership Project (3GPP) is developing 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 of mobile communication systems, known as Beyond 5G, 5G Evolution, or 6G.

[0003] 3GPP is currently discussing ways to improve the coverage of non-terrestrial networks (NTNs). NTNs are networks that include relay stations such as satellites, and terminals (User Equipment, UE) can communicate with base stations (next generation NodeB, gNB) via the relay stations.

[0004] In the above discussion, repeated transmission of a physical uplink control channel (PUCCH) for a contention resolution message (Msg4) in a random access procedure is specified. Specifically, when there is one candidate for the number of repetitions (repetition factor) configured via a system information block (SIB), the candidate repetition factor is used. When there are multiple candidates for the repetition factor configured via the SIB, one of the candidates is dynamically indicated via downlink control information (DCI) (Non-Patent Document 1).

[0005] "Chair's notes RAN1", 3GPP TSG RAN WG1 #111, 3GPP, November 14th - 18th, 2022

[0006] The number of PUCCH resources for Msg4 (the number of available resources in each slot, the number of resource candidates) is 16. However, in wide-area cells such as NTN, many users attempt to connect to one cell and repeated transmissions are sometimes required, so the PUCCH capacity for Msg4 is insufficient. In other words, with 16 resources, there is a problem that resource allocation and transmission wait times occur, and the random access procedure takes a long time to complete. Furthermore, even if resources for PUCCH for Msg4 are added, there is a problem of how the UE should identify the additional resources.

[0007] Furthermore, UE includes not only terminals such as smartphones, but also terminals with simplified specifications compared to terminals such as smartphones, such as Internet of Things (IoT) terminals (hereinafter also referred to as Reduced Capacity (RedCap) UE). Hereinafter, for the sake of convenience, terminals other than RedCap UE will also be referred to as non-RedCap UE. The same applies to non-RedCap UE, but since the number of RedCap UEs is expected to increase in the future, it is urgent to address the insufficient number of PUCCH resources for Msg4 mentioned above.

[0008] Therefore, the present disclosure has been made in consideration of such circumstances, and aims to provide a terminal that can identify more than 16 resources for PUCCH for Msg4, regardless of whether it is a RedCap UE or a non-RedCap UE.

[0009] One aspect of the disclosure is a terminal comprising: a receiving unit (radio signal transceiver unit 210) that receives configuration information related to a physical uplink control channel in response to a contention resolution message in a random access procedure; and a control unit (control unit 270) that identifies more than 16 resources for the physical uplink control channel based on the configuration information, wherein the configuration information is at least one of first configuration information for a terminal whose capabilities are reduced and second configuration information for terminals other than the terminal.

[0010] One aspect of the disclosure is a wireless communication method comprising: receiving configuration information for a physical uplink control channel for a contention resolution message in a random access procedure; and identifying, based on the configuration information, a number of resources for the physical uplink control channel that is greater than 16, wherein the configuration information is at least one of first configuration information for a terminal whose capabilities are reduced and second configuration information for a terminal other than the terminal.

[0011] FIG. 1 is a diagram illustrating an overall schematic configuration of a wireless communication system. FIG. 2 is a diagram illustrating a frequency range used in the wireless communication system. FIG. 3 is a diagram illustrating an example configuration of radio frames, subframes, slots, and symbols used in the wireless communication system. FIG. 4 is a functional block diagram of a terminal. FIG. 5 is a functional block diagram of a base station. FIG. 6 is a diagram illustrating a PUCCH resource set for non-RedCap UE. FIG. 7 is a diagram illustrating a PUCCH resource set for RedCap UE. FIG. 8 is a diagram illustrating a positional relationship between a PUCCH resource set for RedCap UE and a PUCCH resource set for non-RedCap UE. FIG. 9 is a diagram illustrating an example of multiple PUCCH resource sets. FIG. 10 is a diagram illustrating a positional relationship between multiple PUCCH resource sets for RedCap UE and multiple PUCCH resource sets for non-RedCap UE. FIG. 11 is a diagram illustrating an example configuration of a PUCCH resource set for RedCap UE and a PUCCH resource set for non-RedCap UE. FIG. 12 is a diagram illustrating an example configuration of a PUCCH resource set for RedCap UE and a PUCCH resource set for non-RedCap UE. Fig. 13 is a diagram showing an example of the configuration of a PUCCH resource set for RedCap UE and a PUCCH resource set for non-RedCap UE. Fig. 14 is a diagram showing an example of the hardware configuration of a base station and a terminal. Fig. 15 is a diagram showing an example of the configuration of a vehicle.

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

[0013] (1) Overall Schematic Configuration of Wireless Communication System The wireless communication system 10 shown in Fig. 1 is a wireless communication system conforming to a method called 5G. Alternatively, the wireless communication system 10 may be a wireless communication system conforming to a method called Beyond 5G, 5G Evolution, or 6G.

[0014] The wireless communication system 10 can support Massive Multiple-Input Multiple-Output (Massive MIMO), which generates more directional beams by controlling wireless signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses multiple component carriers (CCs) as a bundle, and Dual Connectivity (DC), which enables simultaneous communication with two base stations.

[0015] As shown in FIG. 1 , the wireless communication system 10 includes a Next Generation-Radio Access Network (NG-RAN) 20, a base station (next generation NodeB, gNB) 100 connected to the NG-RAN 20, and a terminal (user equipment, UE) 200 that performs wireless communication with the gNB 100. The NG-RAN 20 is connected to a core network (CN) (not shown). The NG-RAN 20 and the CN may be simply referred to as a "network." The gNB 100 may also be considered to be included in the network. Note that the specific configuration of the wireless communication system 10, for example, the number of gNBs 100 and UEs 200, is not limited to the example shown in FIG. 1 .

[0016] The wireless communication system 10 of the embodiment includes a relay station 150 that relays communication between the gNB 100 and the UE 200. The relay station 150 is a satellite such as a Geostationary Earth Orbit (GEO) satellite, a Middle Earth Orbit (MEO) satellite, or a Low Earth Orbit (LEO) satellite. The relay station 150 may also be a High Altitude Platform Station (HAPS) mounted on an airship, a balloon, or the like, or a commercial aircraft (Air to Ground, ATG). The relay station 150 of the embodiment is assumed to be an air vehicle as described above, but is not limited thereto.

[0017] The wireless communication system 10 may also support multiple frequency ranges (FR). That is, as shown in Fig. 2, the wireless communication system 10 may support the following FRs: FR1: 410 MHz to 7.125 GHz FR2-1: 24.25 GHz to 52.6 GHz FR2-2: Over 52.6 GHz to 71 GHz

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

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

[0020] 3, one slot in the wireless communication system 10 is composed of 14 symbols. If this configuration is maintained, the larger (wider) the SCS, the shorter the symbol period (and slot period). Note that the SCS is not limited to the frequencies shown in FIG. 3 and may be, for example, 480 kHz, 960 kHz, or other frequencies.

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

[0022] As described above, UE200 includes not only non-RedCap UE but also RedCap UE. RedCap UE may also include eRedCap UE, which has terminal functions further simplified than RedCap UE. RedCap UE may be called First RedCap UE and eRedCap UE may be called Second RedCap UE, but for convenience of explanation, when there is no need to distinguish between the two in the following description, both will be collectively referred to as RedCap UE. RedCap UE may also be called a terminal with reduced capabilities.

[0023] A RedCap UE may be defined as a UE that notifies the gNB that it is a RedCap UE by early indication via at least one of Msg1, Msg3, or MsgA in the random access procedure. For example, a RedCap UE may transmit Msg1 or MsgA on resources defined / configured for RedCap UEs. Also, a RedCap UE may transmit Msg3 or MsgA on fields defined / configured for RedCap UEs.

[0024] A RedCap UE may be defined as a UE that reports supporting at least one of the following Feature Groups (FG):

[0025] ・FG28-1: As described in 3GPP TR 38.822 V17.0.0 (2023-03), specifically, it consists of the following components. 1. The maximum FR1 RedCap UE bandwidth is 20 MHz. 2. The maximum FR2 RedCap UE bandwidth is 100 MHz. 3. Early indication of RedCap UE in Msg.1 for 4-step RACH 4. Separate initial UL BWP for RedCap UEs - It includes the configuration(s) needed for RedCap UE to perform random access. - Enabling / disabling of frequency hopping for common PUCCH resources. 5. Separate initial DL BWP for RedCap UEs - It includes Common Search Space (CSS) / Control Resource Set (CORESET) for random access. - For separate initial DL BWP used for paging, Cell Defining (CD)-SSB is included. - For separate initial DL BWP only used for RACH, SSB may or may not be included. - For separate initial DL BWP used in connected mode as BWP#0 configuration option 1, CD-SSB is included. 6. 1 UE-specific RRC configured DL BWP per carrier 7. 1 UE-specific RRC configured UL BWP per carrier 8. RRC reconfiguration of any parameters related to BWP 9.UE-specific RRC configured DL BWP with CD-SSB or Non Cell Defining (NCD)-SSB 10. NCD-SSB based measurements in RRC-configured DL BWP.

[0026] ・FG48-1: As described in 3GPP TSG RAN WG1 #113 R1-2306223, specifically, the components are as follows. The following components are the same as for supportOfRedCap-r17 (28-1): 1. The maximum FR1 RedCap UE bandwidth is 20 MHz. 3. Early indication of RedCap UE in Msg.1 for 4-step RACH 4. Separate initial UL BWP for RedCap UEs - It includes the configuration(s) needed for RedCap UE to perform random access - Enabling / disabling of frequency hopping for common PUCCH resources 5. Separate initial DL BWP for RedCap UEs - It includes CSS / CORESET for random access - For separate initial DL BWP used for paging, CD-SSB is included - For separate initial DL BWP only used for RACH, SSB may or may not be included - For separate initial DL BWP used in connected mode as BWP#0 configuration option 1, CD-SSB is included 6. 1 UE-specific RRC configured DL BWP per carrier 7. 1 UE-specific RRC configured UL BWP per carrier 8. RRC reconfiguration of any parameters related to BWP 9.UE-specific RRC configured DL BWP with CD-SSB or NCD-SSB 10. NCD-SSB based measurements in RRC-configured DL BWP The following components are new compared to supportOfRedCap-r17 (28-1): 11. DL / UL peak data rate target of 10 Mbps 12. Maximum number of PDSCH / PUSCH PRBs that can be scheduled for unicast per slot of 25 PRBs for 15 kHz SCS and 12 PRBs for 30 kHz SCS 13. Relaxed RAR-PDSCH processing timeline.

[0027] FG48-2: As described in 3GPP TSG RAN WG1 #113 R1-2306223, specifically, the following components. The capabilities of FG 48-2 are the same as for FG 48-1 except that the following restrictions do not apply: 12. Maximum number of PDSCH / PUSCH PRBs that can be scheduled for unicast per slot of 25 PRBs for 15 kHz SCS and 12 PRBs for 30 kHz SCS 13. Relaxed RAR-PDSCH processing timeline

[0028] A RedCap UE may be defined as a UE that reports via a UE capability report that it supports (does not support) at least one of the following UE capabilities: Supports up to 20 MHz BW for FR1 and up to 100 MHz BW for FR2 Supports up to 5 MHz for PDSCH and PUSCH in FR1 Supports a relaxed UE processing timeline for PDSCH and / or PUSCH Supports reduced UE peak data rate in FR1 Supports one or two receive branches (receive antennas) and the corresponding maximum number of DL MIMO layers Supports FD-FDD or Type A HD-FDD operation for the FR1 FDD band Supports DL up to 64 QAM or up to 256 QAM for FR1 Does not support CA or DC

[0029] (2) Functional Block Configuration of Wireless Communication System (2.1) Functional Block Configuration of Terminal As shown in FIG. 4, the UE 200 includes a wireless 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.

[0030] The radio signal transmitting / receiving unit 210 transmits and receives radio signals to and from the gNB 100. The radio signal transmitting / receiving unit 210 may be configured as a transmitting unit that transmits radio signals to the gNB 100 and a receiving unit that receives radio signals from the gNB 100. The radio signals include control signals and reference signals / data.

[0031] The radio signal transmitting and receiving unit 210 executes a random access procedure with the gNB 100. Here, the random access procedure will be briefly described.

[0032] First, the UE 200 transmits a physical random access channel (PRACH) for the SS / PBCH block (SSB) received from the gNB 100. This PRACH may be referred to as Msg1. Second, the UE 200 receives a physical downlink shared channel (PDSCH) as a random access response (RAR). This PDSCH may be referred to as Msg2. Third, the UE 200 transmits a PUSCH as an RRC connection request message. This PUSCH may be referred to as Msg3. Fourth, the UE 200 receives the PDSCH as a contention resolution message. This PDSCH may be referred to as Msg4.

[0033] Finally, UE 200 transmits PUCCH as a Hybrid Automatic Repeat Request (HARQ)-ACK for Msg4. The PUCCH for Msg4 may be referred to as PUCCH for Msg4 HARQ-ACK. The PUCCH for Msg4 may also be referred to as PUCCH using common PUCCH resources when dedicated PUCCH resources are not configured. The PUCCH for Msg4 may also be referred to as PUCCH using PUCCH resources indicated in DCI format 1_0 with a Cyclic Redundancy Check (CRC) scrambled on a Temporary Cell-Radio Network Temporary Identifier (TC-RATI). Note that "PUCCH" may refer to PUCCH transmission, i.e., "PUCCH for Msg4" may refer to PUCCH transmission for Msg4.

[0034] The radio signal transmitting and receiving unit 210 of the embodiment can perform repeated transmission of the PUCCH for Msg4 to the gNB 100. Note that the radio signal transmitting and receiving unit 210 can also perform repeated transmission of the PRACH and Msg3.

[0035] The radio signal transmitting and receiving unit 210 of the embodiment receives configuration information related to the PUCCH for Msg4 from the gNB 100. The radio signal transmitting and receiving unit 210 may receive one or more pieces of configuration information. The configuration information includes, as instructions, the number of resources for the PUCCH for Msg4 and their location information.

[0036] The number of PUCCH resources for Msg4 may be 16 or may be a number greater than 16, for example, 32. A group of multiple resources may be referred to as a resource set. In the following description, 16 resources constitute one resource set. Therefore, if the number of PUCCH resources for Msg4 is, for example, 32, the number of PUCCH resource sets for Msg4 is two (two sets).

[0037] The location information of the PUCCH resource for Msg4 includes offset information. The offset information is, for example, a Physical Resource Block (PRB) offset, and indicates an offset value from a predetermined location in the frequency domain for the PUCCH resource or resource set for Msg4. The predetermined location is, for example, the lower end or upper end of the initial UL BWP (see FIG. 6 ).

[0038] The location information of the PUCCH resources for Msg4 may include additional offset information, such as an additional PRB offset, which indicates an additional offset value in the frequency domain for the PUCCH resources or resource sets for Msg4 from the locations offset by the offset information described above (see FIG. 7 ).

[0039] The location information of the PUCCH resource or resource set for Msg4 may include a cyclic shift (CS) index or a time-domain orthogonal cover code (TD-OCC). The CS index or TD-OCC distinguishes the resource or resource set (see FIG. 13). In other words, the CS index or TD-OCC is different for each resource or resource set.

[0040] The configuration information may be either first configuration information for RedCap UE or second configuration information for non-RedCap UE (or may include either one). Furthermore, the configuration information may be both the first configuration information and the second configuration information (or may include both). Both the first configuration information and the second configuration information include the number of PUCCH resources for the above-mentioned Msg4 and their location information. Meanwhile, the first configuration information includes additional offset information, but the second configuration information does not include additional offset information (see FIG. 8 ).

[0041] The setting information also includes various other information, which will be explained in the section on operational examples.

[0042] The amplifier unit 220 is configured by a power amplifier (PA) / low noise amplifier (LNA), etc. The amplifier unit 220 amplifies the radio signal output from the radio signal transmitting / receiving unit 210. The amplifier unit 220 also amplifies the radio signal output from the modulation / demodulation unit 230.

[0043] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB 100 or another gNB). CP-OFDM / DFT-S-OFDM may be applied to the modem unit 230. Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0044] The control signal / reference signal processing unit 240 performs processing related to control signals transmitted and received between the gNB 100, such as radio resource control (RRC) signaling.

[0045] The control signal / reference signal processing unit 240 performs processing related to reference signals transmitted and received between the gNB 100, such as Demodulation Reference Signal (DMRS), Phase Tracking Reference Signal (PTRS), Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS).

[0046] The channels include control channels and data channels. The control channels include a physical uplink control channel (PUCCH), a physical downlink control channel (PDCCH), a physical random access channel (PRACH), a physical broadcast channel (PBCH), etc. The data channels include a physical uplink shared channel (PUSCH), a physical downlink shared channel (PDSCH), etc.

[0047] The encoding / decoding unit 250 performs division / concatenation and coding / decoding of data contained in the radio signal for each predetermined communication destination (gNB100 or another gNB).

[0048] Specifically, the encoding / decoding unit 250 decodes the data output from the modem unit 230 and concatenates the decoded data. In addition, the encoding / decoding unit 250 divides the data output from the data transmitter / receiver 260 into pieces of a predetermined size and performs coding on the divided data.

[0049] The data transmitter / receiver 260 assembles and disassembles data units (Protocol Data Units (PDUs) / Service Data Units (SDUs)) that make up data between each layer. The multiple layers include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer. The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (HARQ).

[0050] The control unit 270 controls the UE 200. The control unit 270 controls, for example, transmission and reception of radio signals by the radio signal transmission and reception unit 210, amplification by the amplifier unit 220, data modulation / demodulation by the modem unit 230, signal processing by the control signal and reference signal processing unit 240, coding / decoding by the encoding / decoding unit 250, and assembly / disassembly of data units by the data transmission and reception unit 260.

[0051] The control unit 270 of the embodiment can apply frequency hopping (FH) when the radio signal transmitting / receiving unit 210 transmits the PUCCH for Msg4. FH is a spread spectrum technique that transmits and receives radio signals while switching frequencies at regular intervals. FH may be intra-slot frequency hopping (intra-slot FH), which switches frequencies within a slot, or inter-slot frequency hopping (inter-slot FH), which switches frequencies between slots.

[0052] However, if UE 200 is a RedCap UE, application of FH may be disabled. Because RedCap UEs have a narrower initial UL BWP than non-RedCap UEs, applying FH to occupy the upper and lower resources of the initial UL BWP may hinder PUSCH transmission for non-RedCap UEs. Disabling application of FH can avoid this situation. Note that in the operation examples described below and the corresponding drawings (FIGS. 7, 8, 10 to 13), it is assumed that application of FH is disabled in resources for RedCap UEs.

[0053] The control unit 270 of the embodiment is not limited to identifying one piece of configuration information as the configuration information related to the PUCCH resources for Msg4, but can identify multiple pieces of configuration information. In other words, the control unit 270 can identify the resources indicated or notified in one piece of configuration information based on the one or more pieces of configuration information transmitted from the gNB 100. Furthermore, even if the number of resources indicated or notified in one piece of configuration information exceeds 16, for example, 32, the control unit 270 can identify this configuration information. Note that the radio signal transmission / reception unit 210 repeatedly transmits the PUCCH for Msg4 using the resources identified by the control unit 270.

[0054] The control unit 270 of the embodiment can identify whether the configuration information related to the PUCCH resource for Msg4 is the above-described first configuration information, the second configuration information, or both. In any case, the control unit 270 can appropriately select the first configuration information for RedCap UE or the second configuration information for non-RedCap UE depending on whether the control unit 270 itself (UE 200) is a RedCap UE or a non-RedCap UE.

[0055] (2.2) Functional block configuration of base station As shown in Figure 5, the gNB100 includes a radio signal transceiver unit 110 and a control unit 120.

[0056] The radio signal transmitting / receiving unit 110 transmits and receives radio signals to and from the UE 200. The radio signal transmitting / receiving unit 110 may include a transmitting unit that transmits radio signals to the UE 200 and a receiving unit that receives radio signals from the UE 200.

[0057] The radio signal transmitting / receiving unit 110 of the embodiment can transmit configuration information related to PUCCH resources for Msg4 to the UE 200. This configuration information may be one or more. When configuring / instructing one resource set using one piece of configuration information, the gNB 100 may configure / instruct the UE 200 to configure / instruct the UE 200 to configure one resource set using one piece of configuration information, or may configure / instruct the UE 200 to configure / instruct the UE 200 to configure multiple resource sets using multiple pieces of configuration information.

[0058] Furthermore, the number of resources configured / instructed by one piece of configuration information may be 16, or may be a number greater than 16, for example, 32. In this case, the gNB100 can configure / instruct the UE200 on a plurality of resource sets by one piece of configuration information. Furthermore, the gNB100 may transmit, as the configuration information to be transmitted to the UE200, first configuration information for RedCap UE, second configuration information for non-RedCap UE, or both the first configuration information and the second configuration information.

[0059] The control unit 120 controls the gNB 100. The control unit 120 controls, for example, the transmission and reception of radio signals by the radio signal transmission and reception unit 110.

[0060] (3) Operation of Wireless Communication System (3.1) Issues The number of PUCCH resources for Msg4 (the number of available resources in each slot, the number of resource candidates) is 16. However, in wide-area cells such as NTN, many users attempt to connect to one cell and repeated transmissions are sometimes required, so the PUCCH capacity for Msg4 is insufficient. In other words, with 16 resources, there is a problem that resource allocation and transmission wait times occur, and the random access procedure takes a long time to complete. In addition, even if resources for PUCCH for Msg4 are added, there is a problem of how the UE should identify the additional resources.

[0061] Furthermore, UE includes not only devices such as smartphones, but also RedCap UE, such as IoT devices, which have simpler specifications than devices such as smartphones. The same applies to non-RedCap UE, but as the number of RedCap UEs in particular is expected to increase in the future, there is an urgent need to address the insufficient number of PUCCH resources for Msg4 mentioned above.

[0062] (3.2) Prerequisites for Operational Example First, the prerequisites for the configuration of the resource set for PUCCH for Msg4 will be described. In the following description, "PUCCH resource set" means "resource set for PUCCH for Msg4." The PUCCH for Msg4 may be a PUCCH that transmits a HARQ-ACK corresponding to the Msg4 PDSCH. The HARQ-ACK corresponding to the Msg4 PDSCH may be transmitted on a PUSCH or another uplink channel instead of a PUCCH. That is, the PUCCH in this operational example may be replaced with a PUSCH or another uplink channel.

[0063] 6 is a diagram showing a PUCCH resource set for a non-RedCap UE. As shown in the left diagram of FIG. 6, the PUCCH resource set is indicated or notified by configuration information transmitted from the gNB 100 (for example, the configuration information in the line surrounded by a bold frame).

[0064] In Figure 6, one resource set consists of 16 resources. That is, one PUCCH resource set (16 resources) is configured by the configuration information shown in the left diagram of Figure 6. The right diagram of Figure 6 shows one PUCCH resource set (16 resources) recognized by UE 200. Note that the resource referred to here is defined by at least one of the time direction, frequency direction, code direction, and space direction, and is used as a unit of each transmission. Furthermore, a resource set refers to a collection of resources, and each UE 200 uses one resource from the resource set.

[0065] As shown in the left diagram of Fig. 6, the following information is set by 4 bits included in the SIB transmitted from the gNB 100. However, this does not have to be limited to this: PUCCH format First symbol index of PUCCH in each slot Number of PUCCH symbols per slot Common physical resource block (PRB) offset Set of initial CS index

[0066] As shown in the right diagram of Fig. 6, the following information is notified by 3 bits included in the DCI received by the UE 200 and 1 bit derived from the Control Channel Element (CCE) index. However, this is not limited to these. FH direction UE-specific PRB offset Initial CS index

[0067] The PRB offset may be interpreted as location information of a resource in the frequency direction. Alternatively, the value obtained by adding the UE-specific PRB offset to the common PRB offset may be interpreted as location information of a resource (resource block) in the frequency direction. The location information of a resource in the frequency direction may refer to an index of a frequency resource.

[0068] 7 is a diagram showing a PUCCH resource set for RedCap UE. Although omitted in FIG. 7, the PUCCH resource set for RedCap UE is indicated or notified by configuration information transmitted from gNB 100, similar to the PUCCH resource set for non-RedCap UE. Recognition in UE 200 is also similar to that for the PUCCH resource set for non-RedCap UE.

[0069] On the other hand, the PUCCH resource set for RedCap UE may differ from the PUCCH resource set for non-RedCap UE in its location information. Specifically, an additional PRB offset is configured in the PUCCH resource set for RedCap UE by configuration information transmitted from the gNB 100. That is, as shown in FIG. 7, in the PUCCH resource set for RedCap UE, an additional PRB offset (Additional PRB offset in the figure) is configured in addition to the common PRB offset (Cell specific PRB offset in the figure) and UE-specific PRB offset (UE specific PRB offset in the figure) that are the same as those in the PUCCH resource set for non-RedCap UE. Note that candidates for the additional PRB offset value may be, for example, any of 2 / 3 / 4 / 6 / 8 / 9 / 10 / 12. Note that the PUCCH resource set for RedCap UE may not be configured, and in that case, the PUCCH resource set for non-RedCap UE may be applied to the RedCap UE.

[0070] Also, in FIG. 7, when an initial UL BWP for RedCap UE is configured, FH is disabled for the PUCCH resource set for RedCap UE. This is because, as described above, it may interfere with PUSCH transmission of non-RedCap UE. In the following description, it is assumed that FH is not applied to the PUCCH resource set for RedCap UE. In this case, whether the PUCCH resource set for RedCap UE is mapped to the lower end or the upper end of the initial UL BWP is configured via the SIB. Note that FH may be enabled.

[0071] Figure 8 is a diagram showing the coexistence of the PUCCH resource set for non-RedCap UEs and the PUCCH resource set for RedCap UEs shown in Figure 6. As shown in Figure 8, the additional PRB offset described above enables the coexistence of both despite the common PRB offset. Note that the common PRB offset for the PUCCH resource set for non-RedCap UEs and the common PRB offset for the PUCCH resource set for RedCap UEs do not need to be the same value.

[0072] (3.3) Operational Example In the operational example of the embodiment, more than 16 resources for the PUCCH for Msg4 are configured for each of RedCap UE and non-RedCap UE. Note that the operational example of the embodiment may be applied to a case where dedicated PUCCH resources are not configured for a UE, such as in the case of initial access. Note that the operational example of the embodiment may be interpreted as including the following modified examples.

[0073] The operation examples of the embodiments may be applied only when common PUCCH resources are configured separately for RedCap UE and non-RedCap UE. More than 16 resources may be available only to RedCap UE or non-RedCap UE. That is, whether more than 16 resources are available to both RedCap UE and non-RedCap UE, only to RedCap UE, or only to non-RedCap UE may be configured via an SIB (SIB1 or an NTN-specific SIB). Note that when only RedCap UE or non-RedCap UE is available, the operation examples described below apply only to either RedCap UE or non-RedCap UE. RedCap UE may include eRedCap UE or may be interpreted as eRedCap UE. Different operation examples described below may be applied to RedCap UE and non-RedCap UE. - When an individual initial BWP (different from that for non-RedCap UE) is configured / not configured for RedCap UE, each of the operation examples described below may be applied. - When application of intra-slot FH is disabled / not disabled (i.e., enabled) for RedCap UE, each of the operation examples described below may be applied. - When an additional PRB offset for common PUCCH resources is configured / not configured for RedCap UE, each of the operation examples described below may be applied.

[0074] (3.3.1) Operation Example 1: Configuring Resource Sets Using Multiple Configuration Information As shown in FIG. 9 , the gNB 100 transmits multiple pieces of configuration information, rather than one piece of configuration information, for the PUCCH for Msg4 in one cell / beam. That is, the gNB 100 configures / instructs multiple resource sets, rather than one resource set, for the PUCCH for Msg4. Based on the multiple pieces of configuration information transmitted from the gNB 100, the UE 200 can identify the resource set indicated or notified in each piece of configuration information for the PUCCH for Msg4. The configuration / instruction of multiple resource sets may be performed for both non-RedCap UEs and RedCap UEs.

[0075] In FIG. 9 , two pieces of configuration information (pucch-ResourceCommon and pucch-ResourceCommon2 in the figure) enclosed by thick lines are transmitted to configure / indicate a resource set for the PUCCH for Msg4, but this is not limited thereto, and three or more pieces of configuration information may be transmitted. As shown in FIG. 9 , each piece of configuration information indicates or notifies a different resource set. Also, in FIG. 9 , each piece of configuration information includes first configuration information for RedCap UE and second configuration information for non-RedCap UE, but it may include only one of them. Also, in FIG. 9 , the first configuration information for RedCap UE and the second configuration information for non-RedCap UE configure the same resource set, but this is not limited thereto, and each piece of configuration information may configure a different resource set. The multiple pieces of configuration information are configured / indicated as follows:

[0076] Example 1a: PUCCH-ConfigCommon (e.g., pucch-ResourceCommon and pucch-ResourceCommon2) containing two or more resource sets for PUCCH for Msg4 is transmitted via SIB 1. Example 1b: The first configuration information (PUCCH-ConfigCommon / pucch-ResourceCommon) is transmitted via SIB 1, and the second (or subsequent) configuration information (PUCCH-ConfigCommon / pucch-ResourceCommon2) is transmitted via an NTN-specific SIB (SIB19).

[0077] Example 1c: An additional PRB offset may be commonly configured for multiple common PUCCH resources for RedCap UEs (PUCCH resource sets for Msg4). The additional PRB offset is applied as follows: Example 1c-1: For each PUCCH-ConfigCommon for RedCap UEs, the additional PRB offset is applied based on the PRB offset included in that PUCCH-ConfigCommon. Example 1c-2: For the Xth (X>=2) PUCCH-ConfigCommon for RedCap UEs, the additional PRB offset is applied based on the PRB offset included in the previous PUCCH-ConfigCommon. In other words, the additional PRB offset is applied cumulatively. Note that in this case, the conventional method, i.e., the method shown in Figures 7 and 8, is applied to the first PUCCH-ConfigCommon.

[0078] Example 1d: An additional PRB offset may be configured individually for multiple common PUCCH resources for RedCap UEs (PUCCH resource sets for Msg4). The additional PRB offset is applied as follows: Example 1d-1: As shown in FIG. 10 , the additional PRB offset is applied to each PUCCH-ConfigCommon for RedCap UEs based on the PRB offset included in that PUCCH-ConfigCommon. Example 1d-2: The additional PRB offset is applied to each PUCCH-ConfigCommon for RedCap UEs based on the PRB offset included in a specific PUCCH-ConfigCommon for non-RedCap UEs. The specific PUCCH-ConfigCommon for non-RedCap UEs may be, for example, the first PUCCH-ConfigCommon, the last PUCCH-ConfigCommon, the PUCCH-ConfigCommon with the largest PRB offset, or the PUCCH-ConfigCommon with the smallest PRB offset in the common PUCCH resource set for non-RedCap UEs. Alternatively, the specific PUCCH-ConfigCommon for non-RedCap UE may be different from the PUCCH-ConfigCommon for RedCap UE, for example, for the Xth PUCCH-ConfigCommon for RedCap UE, the Xth PUCCH-ConfigCommon for non-RedCap UE may be a specific PUCCH-ConfigCommon for non-RedCap UE. That is, for the first PUCCH-ConfigCommon for RedCap UE, the first PUCCH-ConfigCommon for non-RedCap UE is a specific PUCCH-ConfigCommon for non-RedCap UE, and for the second PUCCH-ConfigCommon for RedCap UE, the second PUCCH-ConfigCommon for non-RedCap UE is a specific PUCCH-ConfigCommon for non-RedCap UE.Example 1d-3: Applied to the Xth (X>=2)th PUCCH-ConfigCommon for RedCap UE based on the PRB offset included in a specific PUCCH-ConfigCommon for RedCap UE. The specific PUCCH-ConfigCommon for RedCap UE is, for example, the first PUCCH-ConfigCommon or the X-1th specific PUCCH-ConfigCommon. In this case, Example 1d-1, Example 1d-2, or the conventional method, i.e., the method shown in Figures 7 and 8 above, is applied to the first PUCCH-ConfigCommon.

[0079] Advantage: Multiple resource sets can be used from an existing table in one cell / beam, making implementation easier.

[0080] (3.3.2) Operation Example 2: Configuration Using One Configuration Information Indicating More Than 16 Resources In contrast to Operation Example 1, in which multiple pieces of configuration information indicating resource sets consisting of 16 resources are transmitted, in this operation example, one piece of configuration information indicating more than 16 resources is transmitted. The configuration information in the examples of Figures 11 to 13 indicates 32 resources, but this is not limited to this. Note that "New resources" in the figures indicates the 16 added resources. For convenience, the other 16 resources may also be referred to as the "conventional resource set." Transmission of one piece of configuration information indicating more than 16 resources may be performed for both non-RedCap UE and RedCap UE.

[0081] In the following, as configuration information indicating more than 16 resources, a newly available PRB offset and an additional PRB offset will be described, and further, a CS index and a TD-OCC will be described.

[0082] <PRB Offsets and Additional PRB Offsets> As shown in FIGS. 11 and 12, multiple PRB offsets and multiple additional PRB offsets are available.

[0083] Example 2a: As shown in Figure 11, adjacent PRB offsets and additional PRB offsets can be newly used in addition to the PRB offsets and additional PRB offsets used in the conventional resource set. For example, if the common PRB offset is 2, 2 and 3 may be signaled as UE-specific PRB offsets for non-RedCap UEs in addition to the conventional 0 and 1 (see the UE specific PRB offset in Figure 6). Similarly, if the additional PRB offset is 6, 4, 5, 6 and 7 may be signaled as UE-specific PRB offsets for RedCap UEs in addition to the conventional 0, 1, 2 and 3 (see the UE specific PRB offset in Figure 7).

[0084] Example 2b: As shown in Figure 12, in addition to the PRB offset used in the conventional resource set, non-adjacent PRB offsets can be used. Example 2b-1: Multiple offset values ​​(PRB offset and PRB offset2 in the figure) may be configured as a common PRB offset, and whether to apply one may be signaled to each UE. The multiple offset values ​​are defined as specific values ​​based on the edge of the initial active UL BWP. Note that the offset may be configured via an SIB (SIB1 or SIB19) or may be indicated via an Msg4-scheduling DCI. Example 2b-2: A new PRB offset value (PRB offset3 in the figure) may be configured based on the common PRB offset (PRB offset in the figure), and this new PRB offset value may be signaled to each UE, and whether to apply this new PRB offset value may be signaled to each UE. This new PRB offset value is defined as a specific value based on the location information of the conventional resource set (PRB offset in the figure). The offset may be set via an SIB (SIB1 or SIB19) or may be indicated via an Msg4-scheduling DCI.

[0085] Example 2c: As shown in FIG. 12, in addition to the additional PRB offset used in the conventional resource set, non-adjacent additional PRB offsets can be used. That is, multiple additional PRB offsets (PRB offset 4-X in the figure) can be configured for the common PUCCH resource for RedCap UEs. A frequency resource may be determined based on at least one of the multiple additional PRB offsets. Note that the frequency resource referred to here may be replaced with a resource or a resource set. The multiple additional PRB offsets are applied in one of the following ways: Example 2c-1: For each PRB offset 4-X, the conventional method, i.e., the method shown in FIG. 7 and FIG. 8, is applied. Example 2c-2: For each PRB offset 4-X, a specific PRB offset for non-RedCap UEs is applied. The specific PRB offset for non-RedCap UEs is, for example, PRB offset, PRB offset2, and PRB offset+PRB offset3 in the figure. Example 2c-3: For the Xth (X>=2) additional PRB offset for RedCap UEs, a specific additional PRB offset for RedCap UEs is applied. A specific additional PRB offset for a RedCap UE is, for example, PRB offset4-1 or sum(PRB offset4-1, PRB offset4-2, ..., PRB offset4-(X-1)), i.e., the sum of the X-1st additional PRB offsets. In this case, for the first additional PRB offset, Example 2c-1, Example 2c-2, or the conventional method, i.e., the method shown in Figures 7 and 8 above, is applied.

[0086] Example 2d: More candidate values ​​are available for the additional PRB offset. For example: - Conventional additional PRB offset: ENUMERATED (n2, n3, n4, n6, n8, n9, n10, n12) - New additional PRB offset: ENUMERATED (n2, n3, n4, n6, n8, n9, n10, n12, n16)

[0087] Effect: Not only does it make more resources available, but it also avoids the risk of degradation in detection performance for transmissions that use the resources.

[0088] <CS Index> As shown in FIG. 13, the initial CS index candidates can include more values ​​than those in the existing specifications. That is, an initial CS index not included in the conventional resource set can be used as configuration information. For example, a specific value / offset may be defined as a new initial CS index. The new initial CS index may be configured via an SIB (SIB1 or SIB19) or indicated via an Msg4-scheduling DCI. The offset value may be an offset value from the initial CS index included in the conventional resource set. This offset value and whether or not it is applicable may be notified for each UE. An additional initial CS index may be available for both non-RedCap UEs and RedCap UEs.

[0089] In the upper diagram of Fig. 13, resources that use an initial CS index that is not included in the conventional resource set are depicted, but the resources that make up the conventional resource set and the resources that make up the newly configured resource set may be configured alternately in the CS direction, as shown in the lower diagram of Fig. 13. In any case, it is sufficient that the CS index is different for each resource or resource set.

[0090] <TD-OCC> Instead of or in addition to the CS index, the TD-OCC may be used to distinguish resources. That is, candidate values ​​of the orthogonal sequence index are defined in the standard / configured via SIB. The index may be indicated via Msg4-scheduling DCI.

[0091] Advantages: Not only do more resources become available, but additional resources in the frequency and time directions are not consumed.

[0092] (3.3.3) Instruction Method The following content may be applied to either Operation Example 1 or Operation Example 2.

[0093] (Method of indicating more than 16 resources) Example 1: Msg4-scheduling DCI - One or more bits in the MCS field - One or more bits in the HPN field - One or more bits in the RV field - One or more bits in the DAI field - One or more bits in the TPC command field

[0094] Example 2: RAR and RAR UL grant

[0095] Example 3: CCE index - More than 1 bit derived from the CCE index (e.g. 2 bits)

[0096] Example 4: Dynamic notification of repetition factor Which resource set to use or whether to use additional resources defined in the resource set may be associated with dynamic notification of the repetition factor. For example, if the repetition factor is 1, the existing resources included in the existing resource set may be notified, and if the repetition factor is greater than 1, the additionally defined resource set or resources may be notified. Note that the dynamic notification may be performed in the DCI scheduling the Msg4 PDSCH.

[0097] Effect: Dynamic scheduling can be applied to more than 16 resources.

[0098] The PUCCH resource newly defined by the above method may be assigned an index of 16 or more, and r_PUCCH in the specifications (TS38.213) may be a value of 16 or more.

[0099] Also, which resource set to use or whether or not to use a resource additionally defined in the resource set may be signaled in any of the above-described Examples 1, 2, 3, and 4, and one of 16 combinations may be signaled by the DCI and CCE index. Also, which of 32 combinations of resources to use may be signaled by any of the above-described Examples 1, 2, 3, and 4, and a combination of the DCI and CCE index.

[0100] (3.3.4) Capability Information of Terminal The following content may be applied to either Operation Example 1 or Operation Example 2, and may be applied to both non-RedCap UE and RedCap UE.

[0101] (Reporting capability information of a terminal that supports more than 16 resources) Example 1: Reported by Msg1 (PRACH) Preamble and / or occasion Example 2: Reported by Msg3 PUSCH Scrambling sequence, DMRS port, different CS for DMRS, LCID code point Effect: The network (gNB100) can instruct a UE200 that does not support more than 16 resources to select one resource from the conventional resource set.

[0102] (4) Other Embodiments The contents of the present invention have been described above in accordance with the embodiments, but it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0103] In the above disclosure, a resource and a resource set may be interchangeable. Also, a "setting" and an "instruction" in the setting information may be interchangeable.

[0104] In the above disclosure, the number of resources greater than 16 has been described as 32, but it may be 48, 64, or more. Also, while a resource set is described as being composed of 16 resources, it may be composed of 32 resources or more.

[0105] In the above disclosure, the additional PRB offset may be configured commonly for a plurality of resource sets or may be configured individually for each of the resource sets. Furthermore, when three or more resource sets are configured, the additional PRB offset may be configured commonly for some of the resource sets and individually for the remaining several resource sets.

[0106] In the above disclosure, it is assumed that the UE 200 of the embodiment is applied to an NTN, but this is not limiting, and the UE 200 may be applied to a TN (Terrestrial Network) as well as an NTN.

[0107] The above-described operation examples may be combined and applied in a composite manner, as long as no contradiction occurs.

[0108] In the above disclosure, 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 be interchangeable.

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

[0110] The block diagrams (FIGS. 4 and 5) used to explain the above-described embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., wired, wireless, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or multiple devices.

[0111] 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, regard, 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.

[0112] Furthermore, the above-described gNB 100 and UE 200 (the devices) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 14 is a diagram showing an example of the hardware configuration of the devices. As shown in Figure 14, the devices may be configured as a computer 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.

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

[0114] Each functional block of the device (FIGS. 4 and 5) is realized by any hardware element of the computer device or a combination of the hardware elements.

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

[0116] 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, and registers.

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

[0118] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, 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 may store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

[0119] 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 suitable medium including at least one of memory 1002 and storage 1003.

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

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

[0122] The input device 1005 is an input device (e.g., 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 (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

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

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

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

[0126] 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 enhanced 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.

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

[0128] In the present disclosure, a specific operation described as being performed by a base station may 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.

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

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

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

[0132] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

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

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

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

[0136] Note that terms described 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.

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

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

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

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

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

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

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

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

[0145] At least one of the base station and the mobile station may be referred to as 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, the mobile object itself, etc. 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.

[0146] 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 terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

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

[0148] A radio frame may be made up of one or more frames in the time domain, each of which may be called a subframe.

[0149] A subframe may further be composed of one or more slots in the time domain, and may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0150] Numerology may be communication parameters that apply to the transmission and / or 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 the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

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

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

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

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

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

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

[0157] In addition, 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. Furthermore, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

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

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

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

[0161] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0162] 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, etc.

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

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

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

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

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

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

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

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

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

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

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

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

[0175] 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 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, all of which are considered to be "determining." "Determining" and "determining" may also include resolving, selecting, choosing, establishing, comparing, and the like, all of which are considered to be "determining." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Also, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

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

[0177] 15 shows an example of the configuration of a vehicle 2001. As shown in Fig. 15, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right 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.

[0178] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

[0179] The steering unit 2003 includes at least a steering wheel (also called a handle) 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.

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

[0181] The signals from the various sensors 2021 to 2028 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a 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, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0182] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

[0183] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

[0184] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from a driving unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, a microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028, which are provided in the vehicle 2001.

[0185] 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 the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

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

[0187] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The communication module 2013 also stores the various information received from the external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, sensors 2021 to 2028, and the like provided in the vehicle 2001.

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

[0189] (Additional Note) The above disclosure may be expressed as follows.

[0190] A first feature is a terminal including: a receiving unit that receives configuration information related to a physical uplink control channel in response to a contention resolution message in a random access procedure; and a control unit that identifies, based on the configuration information, a number of resources for the physical uplink control channel that exceeds 16, wherein the configuration information is at least one of first configuration information for a terminal whose capabilities are reduced and second configuration information for terminals other than the terminal.

[0191] A second feature is the terminal of the first feature, wherein the more than 16 resources include a resource set consisting of a plurality of resources, and the first configuration information includes offset information indicating an offset amount of each resource set in a frequency domain, and additional offset information indicating an additional offset value from an offset position of each resource set based on the offset value, and the additional offset information indicates the additional offset value commonly for a plurality of the resource sets.

[0192] A third feature is the terminal of the first feature, wherein the more than 16 resources include a resource set consisting of a plurality of resources, and the first configuration information includes offset information indicating an offset value of each resource set in a frequency domain, and additional offset information indicating an additional offset value from an offset position of each resource set based on the offset value, and the additional offset information indicates the additional offset value individually for each of the plurality of resource sets.

[0193] A fourth feature is the terminal of the first feature, wherein the more than 16 resources are configured by a resource set including a plurality of resources, and the first configuration information includes offset information indicating an offset value of the resource set in a frequency domain, and a plurality of pieces of additional offset information indicating additional offset values ​​from an offset position of the resource set based on the offset value, and the frequency resource is determined based on at least one of the plurality of pieces of additional offset information.

[0194] A fifth feature is the terminal according to any one of the first to fourth features, wherein the configuration information includes a cyclic shift index or a time-domain orthogonal cover code that differs for each of the resources.

[0195] A sixth feature is a wireless communication method including: receiving configuration information for a physical uplink control channel in response to a contention resolution message in a random access procedure; and identifying, based on the configuration information, resources for the physical uplink control channel that exceed 16, wherein the configuration information is at least one of first configuration information for a terminal whose capability is reduced and second configuration information for terminals other than the terminal.

[0196] 10 Wireless communication system 20 NG-RAN 100 gNB 110 Wireless signal transceiver 120 Control unit 150 Relay station 200 UE 210 Wireless signal transceiver 220 Amplifier 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / decoding unit 260 Data transceiver 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port

Claims

1. A terminal comprising: a receiving unit that receives configuration information related to a physical uplink control channel in response to a contention resolution message in a random access procedure; and a control unit that identifies a number of resources for the physical uplink control channel that exceeds 16 based on the configuration information, wherein the configuration information is at least one of first configuration information for a terminal whose capabilities are reduced and second configuration information for terminals other than the terminal.

2. The terminal according to claim 1, wherein the more than 16 resources include a resource set consisting of a plurality of resources, the first setting information includes offset information indicating an offset value of each resource set in the frequency domain, and additional offset information indicating an additional offset value from an offset position of each resource set based on the offset value, and the additional offset information indicates the additional offset value commonly for the plurality of resource sets.

3. The terminal according to claim 1, wherein the more than 16 resources include a resource set consisting of a plurality of resources, the first setting information includes offset information indicating an offset value of each resource set in the frequency domain, and additional offset information indicating an additional offset value from an offset position of each resource set based on the offset value, and the additional offset information indicates the additional offset value individually for each of the plurality of resource sets.

4. The terminal according to claim 1, wherein the more than 16 resources are configured by a resource set consisting of a plurality of resources, the first setting information includes offset information indicating an offset value of the resource set in the frequency domain, and a plurality of pieces of additional offset information indicating additional offset values ​​from an offset position of the resource set based on the offset value, and a frequency resource is determined based on at least one of the plurality of pieces of additional offset information.

5. The terminal according to claim 1, wherein the configuration information includes a different cyclic shift index or a time-domain orthogonal cover code for each of the resources.

6. A wireless communication method comprising: a step of receiving configuration information relating to a physical uplink control channel for a contention resolution message in a random access procedure; and a step of identifying a number of resources for the physical uplink control channel that exceeds 16 based on the configuration information, wherein the configuration information is at least one of first configuration information for a terminal whose capabilities are reduced and second configuration information for a terminal other than the terminal.

Images