Terminals, base stations, and communication methods.

Abstract

This terminal comprises: a control circuit that, on the basis of information related to the setting of a first resource to a terminal of a first type, sets a second resource which is different from the first resource to a terminal of a second type; and a transmission circuit that transmits a signal in the second resource.

Description

Terminal, base station, and communication method

[0001] The present disclosure relates to a terminal, a base station, and a communication method.

[0002] A communication system known as the fifth-generation mobile communication system (5G) is currently under consideration. The 3rd Generation Partnership Project (3GPP), an international standardization organization, is studying the advancement of the 5G communication system from the perspectives of both the advancement of the LTE / LTE-Advanced system and New Radio Access Technology (also referred to as New RAT or NR), a new method that is not necessarily backward compatible with the LTE / LTE-Advanced system (see, for example, Non-Patent Document 1).

[0003] RP-181726, “Revised WID on New Radio Access Technology”, NTT DOCOMO, September 2018RP-193238, “New SID on Support of Reduced Capability NR Devices”, Ericsson, December 20193GPP TS 38.213 V16.6.0, “NR; Physical layer procedures for control (Release 16)”, 2021-06

[0004] However, there is room for further study on how to improve the efficiency of resource allocation to terminals.

[0005] Non-limiting examples of the present disclosure contribute to providing a terminal, a base station, and a communication method that can improve the efficiency of resource allocation to terminals.

[0006] A terminal according to one embodiment of the present disclosure includes a control circuit that sets a second resource, which is different from the first resource, for a second type of terminal based on information regarding the setting of a first resource for a first type of terminal, and a transmission circuit that transmits a signal using the second resource.

[0007] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

[0008] According to an embodiment of the present disclosure, it is possible to improve the efficiency of resource allocation to terminals.

[0009] Further advantages and benefits of one embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features.

[0010] 3GPP NR system architecture: Schematic diagram showing functional separation between NG-RAN and 5GC; Sequence diagram of Radio Resource Control (RRC) connection setup / reconfiguration procedures; Supports enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC). Schematic diagram illustrating a 5G Communications usage scenario. Block diagram illustrating an exemplary 5G system architecture for a non-roaming scenario.

[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

[0012] In the following description, for example, a radio frame, a slot, and a symbol are units of physical resources in the time domain. For example, the length of one frame may be 10 milliseconds. For example, one frame may be composed of multiple slots (e.g., 10, 20, or other values). Furthermore, the number of slots constituting one frame may be variable depending on the slot length. Furthermore, one slot may be composed of multiple symbols (e.g., 14 or 12). For example, one symbol is the smallest physical resource unit in the time domain, and the symbol length may vary depending on the subcarrier spacing (SCS).

[0013] Furthermore, a subcarrier and a resource block (RB) are units of physical resources in the frequency domain. For example, one resource block may consist of 12 subcarriers. For example, one subcarrier may be the smallest physical resource unit in the frequency domain. The subcarrier spacing is variable and may be, for example, 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or other values.

[0014] [Regarding Cell-Specific PUCCH] For example, if a dedicated (or individual or UE-specific) configuration is not provided for an NR terminal (e.g., a mobile station, or also referred to as User Equipment (UE)), the terminal may use an uplink control channel (e.g., PUCCH) resource set based on a cell-specific configuration (see, for example, Non-Patent Document 3).

[0015] For example, after receiving a signal (e.g., contention resolution identity (Message 4)) transmitted in a downlink shared channel (e.g., a Physical Downlink Shared Channel (PDSCH) or a downlink data channel) resource, a terminal in an initial connection stage may transmit to the base station, using a PUCCH resource, information indicating whether the signal was received successfully (Hybrid Automatic Retransmission Request-Acknowledgement (HARQ-ACK) or Negative ACK, NACK). At this time, if a dedicated PUCCH configuration is not provided to the terminal, the terminal may transmit the HARQ-ACK using, for example, a PUCCH resource included in a cell-specific PUCCH resource set configured by system information.

[0016] Note that the cell-specific PUCCH resource set may also be referred to as "PUCCH resource sets before dedicated PUCCH resource configuration."

[0017] Fig. 1 shows an example of parameters related to a cell-specific PUCCH resource set based on cell-specific configuration. In Fig. 1, index values ​​(index) ranging from 0 to 15 are associated with combinations of parameters related to the PUCCH resource set, such as the PUCCH format, first symbol, number of symbols (e.g., duration), PRB offset, and set of initial Cyclic Shift (CS) indexes.

[0018] For example, the terminal acquires information about any of the indices in the range of 0 to 15 according to the cell-specific setting. For example, the terminal identifies the index based on the acquired information and selects the PUCCH resource set associated with the index shown in FIG. 1 (for example, the PUCCH format, first symbol, number of symbols, and PRB offset (RB) specified by the row corresponding to the index). BWP offset ), set of initial CS indexes).

[0019] 2 is a diagram illustrating an example of a cell-specific PUCCH resource set when a terminal acquires index=8 through cell-specific configuration. For example, as shown in FIG. 1, the terminal may configure PUCCH format 1, first symbol=4, number of symbols=10, PRB offset=0, and set of initial CS indexes={0, 3, 6, 9} as parameters associated with index=8.

[0020] As shown in FIG. 2 , the time resource of the cell-specific PUCCH is set to the "Number of symbols" number of symbols excluding the "first symbol" number of symbols from the beginning of one slot. Also, as shown in FIG. 2 , the frequency resource of the cell-specific PUCCH may span multiple Physical Resource Blocks (PRBs). Furthermore, each PRB is set to a "PRB offset (RB)" from both ends of the band included in the uplink Bandwidth Part (BWP). BWP offset ) PRBs are spaced apart in frequency.

[0021] As shown in FIG. 2, the method of switching and transmitting PRBs at each time is sometimes called "frequency hopping."

[0022] Also, as shown in Figure 2,PUCCH A parameter called " may be set to a value (for example, a different value) individually for each terminal. PUCCH For example, multiple terminals may use different PUCCH resources. For example, r PUCCH If PUCCH resource 0 is notified as 0, 1, 2, or 3, the terminal may use PUCCH resources "0-3" shown in Fig. 2. Note that if the same resources are allocated in the time-frequency domain, the PUCCH may be multiplexed by cyclic shifting (CS) of the transmission sequence.

[0023] In addition, r PUCCH The value of may be determined, for example, by the number of Control Channel Elements (CCEs) included in a downlink control channel (e.g., a Physical Downlink Control Channel (PDCCH) or a Control Resource Set (CORESET)) received by the terminal before transmitting the PUCCH, the index of the CCE (e.g., the index of the first CCE), and information included in the downlink control information (e.g., Downlink Control Information (DCI)).

[0024] As described above, one of the features of the cell-specific PUCCH resources is that they are frequency hopped within a slot (for example, called intra-slot hopping) using PRBs near both ends of the uplink BWP.

[0025] [Regarding Reduced Capability NR Devices] In Release 17 (hereinafter referred to as Rel-17 NR), specifications (e.g., Reduced Capability (RedCap)) are expected to be formulated to realize terminals (e.g., NR terminals) that support a variety of use cases by limiting some functions or performance compared to, for example, Release 15 or 16 (hereinafter referred to as Rel-15 / 16 NR) (e.g., initial releases of NR) (see, for example, Non-Patent Document 2).

[0026] Such terminals may be referred to as, for example, Reduced Capability NR Devices, RedCap, RedCap Terminals, NR-Lite, or NR-Light.

[0027] To reduce power consumption or costs, for example, reducing the amount of calculation in a terminal is being considered. One method for reducing the amount of calculation in a terminal is to set the bandwidth supported by the terminal to be narrower than the bandwidth supported by existing terminals. For example, the maximum frequency bandwidth supported by a terminal other than a RedCap terminal (hereinafter, for convenience, also referred to as a "non-RedCap" or "non-RedCap terminal") may be 100 MHz in FR1 (frequency range 1) and 200 MHz in FR2 (frequency range 2). On the other hand, the maximum frequency bandwidth supported by a RedCap terminal may be 20 MHz in FR1 and 100 MHz in FR2.

[0028] Here, as described above, a non-RedCap terminal may use, for example, a PUCCH resource included in a cell-specific PUCCH resource set. In this case, the frequency resource of the PUCCH may be set to, for example, a PRB near both ends of a bandwidth (for example, a BWP) for a non-RedCap terminal. Therefore, for example, if a BWP for a non-RedCap terminal supports a bandwidth of 100 MHz, a RedCap terminal that supports a bandwidth of 20 MHz may not be able to use the PUCCH resource for a non-RedCap terminal.

[0029] For example, as shown in Fig. 3, a base station (e.g., also referred to as a gNB) may configure a PUCCH resource set for RedCap separately from a PUCCH resource set for non-RedCap terminals. This may increase the amount of signals (signaling overhead) for configuring a PUCCH resource set for RedCap for RedCap terminals.

[0030] Furthermore, for example, as shown in FIG. 4, PUCCH resources for RedCap terminals may divide uplink shared channel (e.g., Physical Uplink Shared Channel (PUSCH) or uplink data channel) resources for non-RedCap terminals. For example, as shown in FIG. 4, if PUCCH resources for RedCap terminals (PUCCH for RedCap) are set to PRBs near the center of the BWP for non-RedCap terminals, the non-RedCap terminals cannot use these PRBs for PUSCH transmission. In this case, for example, for non-RedCap terminals that do not support PUSCH transmission of non-contiguous PRBs, the number of consecutive PRBs available for PUSCH transmission may be limited, which may result in a degradation of the peak data rate.

[0031] Therefore, in a non-limiting example of the present disclosure, for example, a method for improving the efficiency of resource allocation in a terminal will be described.

[0032] For example, in a non-limiting embodiment of the present disclosure, a terminal (e.g., a RedCap terminal) may configure PUCCH resources used by a RedCap mobile station that differ from PUCCH resources used by non-RedCap terminals based on a cell-specific PUCCH resource configuration. As an example, the RedCap terminal may be provided with information regarding a difference in at least one of the time domain and the frequency domain between the PUCCH resources used by the RedCap terminal and the cell-specific PUCCH resources. This can reduce the amount of signaling required for PUCCH resource configuration for RedCap terminals. Furthermore, for example, it can suppress fragmentation of PUSCH resources for non-RedCap terminals. Therefore, according to a non-limiting embodiment of the present disclosure, it is possible to improve the utilization efficiency of PUCCH resources.

[0033] [Overview of Communication System] The communication system according to this embodiment includes a base station 100 and a terminal 200 .

[0034] Fig. 5 is a block diagram showing an example of the configuration of a portion of base station 100 according to this embodiment. In base station 100 shown in Fig. 5, control unit 101 (e.g., corresponding to a control circuit) configures second resources different from the first resources for a second type of terminal (e.g., a RedCap terminal) based on information (e.g., a cell-specific PUCCH resource set) regarding the configuration of first resources for a first type of terminal (e.g., a non-RedCap terminal). Receiving unit 108 (e.g., corresponding to a receiving circuit) receives a signal (e.g., a PUCCH) in the second resource.

[0035] Fig. 6 is a block diagram showing an example configuration of a portion of terminal 200 according to this embodiment. In terminal 200 shown in Fig. 6, control unit 206 (e.g., corresponding to a control circuit) configures second resources different from the first resources for a second type of terminal (e.g., a RedCap terminal) based on information (e.g., a cell-specific PUCCH resource set) regarding configuration of first resources for a first type of terminal (e.g., a non-RedCap terminal). Transmitting unit 210 (e.g., corresponding to a transmitting circuit) transmits a signal (e.g., a PUCCH) in the second resources.

[0036] [Configuration of Base Station] Fig. 7 is a block diagram showing an example configuration of base station 100 according to this embodiment. In Fig. 7, base station 100 has control section 101, DCI generation section 102, upper layer signal generation section 103, coding and modulation section 104, signal mapping section 105, transmission section 106, antenna 107, reception section 108, signal separation section 109, and demodulation and decoding section 110.

[0037] The control unit 101 may, for example, determine a configuration of a cell-specific PUCCH resource set. Based on the determined configuration, the control unit 101 may instruct the upper layer signal generation unit 103 to generate an upper layer signal such as system information (e.g., also referred to as an upper layer parameter or upper layer signaling). Furthermore, the control unit 101 may, for example, determine a configuration of a downlink control channel (e.g., PDCCH) or control information (e.g., DCI) included in the downlink control channel. Based on the determined information, the control unit 101 may instruct the DCI generation unit 102 to generate downlink control information (e.g., DCI).

[0038] Furthermore, the control unit 101 may set PUCCH resources to be used by RedCap terminals that are different from PUCCH resources to be used by non-RedCap terminals, for example, based on the setting of a cell-specific PUCCH resource set.

[0039] Furthermore, the control unit 101 may control transmission processing (for example, transmission processing of downlink data) based on the PUCCH sequence input from the signal separation unit 109 .

[0040] The DCI generating unit 102 may generate DCI based on an instruction from the control unit 101 , for example, and output the generated DCI to the signal mapping unit 105 .

[0041] The upper layer signal generating unit 103 may generate an upper layer signal such as system information based on instructions from the control unit 101, for example, and output the generated upper layer signal to the coding and modulation unit 104.

[0042] The coding / modulation unit 104 may, for example, perform error correction coding and modulation on downlink data (e.g., PDSCH) and the upper layer signal input from the upper layer signal generation unit 103, and output the modulated signal to the signal mapping unit 105.

[0043] Signal mapping section 105 may, for example, map the DCI input from DCI generation section 102 and the signal input from coding and modulation section 104 to resources. For example, signal mapping section 105 may map the signal input from coding and modulation section 104 to PDSCH resources and map DCI to PDCCH resources. Signal mapping section 105 outputs the signals mapped to each resource to transmitting section 106.

[0044] The transmitting unit 106 performs radio transmission processing, including frequency conversion (e.g., up-conversion) using a carrier wave, on the signal input from the signal placement unit 105, and outputs the signal after the radio transmission processing to the antenna 107.

[0045] The antenna 107, for example, emits a signal (for example, a downlink signal) input from the transmitting unit 106 toward the terminal 200. The antenna 107 also receives an uplink signal transmitted from the terminal 200, for example, and outputs the signal to the receiving unit 108.

[0046] The uplink signal may be a signal of a channel such as an uplink data channel (e.g., PUSCH), an uplink control channel (e.g., PUCCH), or a random access channel (e.g., Physical Random Access Channel (PRACH)).

[0047] Receiving section 108 performs radio reception processing including frequency conversion (for example, down-conversion) on the signal input from antenna 107 , and outputs the signal after radio reception processing to signal separating section 109 .

[0048] For example, signal separation section 109 extracts (in other words, separates) signals on PUCCH resources (for example, PUCCH sequences) from the signals input from receiving section 108, and outputs the extracted signals to control section 101. Furthermore, signal separation section 109 outputs, for example, signals on PUSCH resources from the signals input from receiving section 108 to demodulation and decoding section 110.

[0049] The demodulation and decoding unit 110 demodulates and decodes the signal input from the signal separation unit 109, for example, and outputs uplink data.

[0050] [Configuration of Terminal] FIG. 8 is a block diagram showing an example of the configuration of terminal 200 according to this embodiment.

[0051] In FIG. 8 , terminal 200 includes antenna 201, receiving section 202, signal separating section 203, DCI detecting section 204, demodulating and decoding section 205, control section 206, PUCCH sequence generating section 207, coding and modulating section 208, signal mapping section 209, and transmitting section 210.

[0052] The antenna 201 receives, for example, a downlink signal transmitted by the base station 100 and outputs the signal to the receiving unit 202. The antenna 201 also radiates, for example, an uplink signal input from the transmitting unit 210 to the base station 100.

[0053] The receiving unit 202 performs radio reception processing including frequency conversion (for example, down-conversion) on the signal input from the antenna 201 , and outputs the signal after radio reception processing to the signal separating unit 203 .

[0054] For example, signal separation section 203 extracts (in other words, separates) signals on PDCCH resources from the signals input from receiving section 202, and outputs the extracted signals to DCI detection section 204. Furthermore, signal separation section 203 outputs, for example, signals on PDSCH resources from the signals input from receiving section 202 to demodulation and decoding section 205.

[0055] For example, the DCI detection unit 204 may detect DCI from the signal (for example, the signal on the PDCCH resource) input from the signal separation unit 203. The DCI detection unit 204 may output the detected DCI to the control unit 206, for example.

[0056] The demodulation / decoding unit 205, for example, demodulates and performs error correction decoding on a signal (for example, a signal on a PDSCH resource) input from the signal separation unit 203 to obtain at least one of an upper layer signal such as downlink data and system information. The demodulation / decoding unit 205 may output the upper layer signal obtained by decoding to the control unit 206, for example.

[0057] The control unit 206 may determine (or identify) the configuration of the cell-specific PUCCH resource set based on, for example, an upper layer signal (for example, system information) input from the demodulation and decoding unit 205. Furthermore, for example, the control unit 206 may determine the PUCCH resource set to be used by the terminal 200 (for example, a RedCap terminal) based on the identified cell-specific PUCCH resource set and a preset parameter.

[0058] Furthermore, the control unit 206 determines r based on, for example, the PDCCH setting and the DCI input from the DCI detection unit 204. PUCCH The control unit 206 may determine the value of the determined r PUCCH The control section 206 outputs information about the PUCCH resource corresponding to the PUCCH sequence to the signal mapping section 209. Furthermore, the control section 206 may instruct the PUCCH sequence generation section 207 to generate a PUCCH sequence.

[0059] The PUCCH sequence generating section 207 generates a PUCCH sequence according to, for example, an instruction from the control section 206 and outputs the generated PUCCH sequence to the signal mapping section 209 .

[0060] The coding and modulation unit 208 may, for example, perform coding and modulation on uplink data (for example, PUSCH) and output the modulated signal to the signal mapping unit 209 .

[0061] For example, signal mapping section 209 may map the PUCCH sequence input from PUCCH sequence generation section 207 to the PUCCH resource based on information about the PUCCH resource input from control section 206. Furthermore, signal mapping section 209 may map the signal input from coding and modulation section 208 to the PUSCH resource. Signal mapping section 209 outputs the signal mapped to each resource to transmission section 210.

[0062] The transmitting section 210 performs radio transmission processing including frequency conversion (for example, up-conversion) on the signal input from the signal mapping section 209 , and outputs the signal after the radio transmission processing to the antenna 201 .

[0063] [Example of Operation of Base Station 100 and Terminal 200] Next, an example of operation of the base station 100 and terminal 200 described above will be described.

[0064] <Operation Example 1> In operation example 1, for example, with respect to a PUCCH time resource (e.g., represented as "T1") for a RedCap terminal, base station 100 and terminal 200 may set one slot based on information regarding the setting of a PUCCH time resource for a non-RedCap terminal.

[0065] Also, for example, with respect to a PUCCH frequency resource (e.g., represented as "F1") for a RedCap terminal, base station 100 and terminal 200 may configure one PRB based on information regarding the configuration of PUCCH frequency resources for non-RedCap terminals.

[0066] FIG. 9 is a sequence diagram showing an example of processing by base station 100 and terminal 200.

[0067] <S101> Base station 100 may, for example, determine a cell-specific PUCCH resource set to be configured in a terminal (for example, a non-RedCap terminal) and notify terminal 200 of information on the determined cell-specific PUCCH resource set using system information. Furthermore, base station 100 may, for example, notify terminal 200 of DCI using a PDCCH.

[0068] <S102> Terminal 200 may identify a cell-specific PUCCH resource set based on, for example, received system information. PUCCH You may specify a value for

[0069] <S103> Terminal 200 may, for example, determine a PUCCH resource set to be used by terminal 200. For example, terminal 200 may determine the PUCCH resource set based on the notified cell-specific PUCCH resource set and parameters related to the PUCCH resource set to be used by terminal 200.

[0070] For example, in terminal 200, with respect to the time resource (T1) of the PUCCH, a parameter "t1" (e.g., an integer value) may be configured which relates to the relative position (e.g., difference or offset) between the time resource (e.g., slot) in the cell-specific PUCCH resource set and the time resource (e.g., slot) in the PUCCH resource set used by terminal 200.

[0071] For example, when a cell-specific PUCCH resource set is arranged in slot n, terminal 200 may set slot n+t1 as the PUCCH resource to be used by terminal 200 (e.g., RedCap terminal).

[0072] Note that parameter t1 may be configured in advance in terminal 200, may be notified from base station 100 to terminal 200 using at least one of higher layer signaling and DCI, or may be defined in a standard. Also, t1 does not have to be configured in terminal 200. In this case, terminal 200 may configure, for example, the same slots as the cell-specific PUCCH resource set as the PUCCH resources used by terminal 200.

[0073] In this way, the PUCCH resources used by terminal 200 (e.g., a RedCap terminal) may include one slot that is set based on slots included in the PUCCH resources of the cell-specific PUCCH resource set and parameter t1 (e.g., information regarding the difference in time resources).

[0074] Furthermore, for example, the terminal 200 may be configured with a parameter "f1" (e.g., an integer value) relating to the relative position (e.g., difference or offset) between a frequency resource (e.g., PRB) in a cell-specific PUCCH resource set and a frequency resource (e.g., PRB) in a PUCCH resource set used by the terminal 200, with respect to the PUCCH frequency resource (F1).

[0075] For example, terminal 200 determines parameter f1 and offset RBs included in the cell-specific PUCCH resource set. BWP offset Based on this, the PRB to RB at both ends of the band included in the uplink BWP of the non-RedCap terminal BWP offset A PRB that is +f1 away may be set as a candidate for a PUCCH resource to be used by terminal 200 (for example, a RedCap terminal).

[0076] Furthermore, regarding the frequency resource (F1) of the PUCCH, for example, a parameter "fl1" that can take two values, "lower" and "higher", may be configured in terminal 200.

[0077] For example, the terminal 200 may select, based on the parameter fl1, the PRBs to RBs at both ends of the band included in the uplink BWP of the non-RedCap terminal. BWP offset Either one of the PRBs that are +f1 apart (for example, the PRB corresponding to the lower or the PRB corresponding to the higher) may be set as the PUCCH resource used by terminal 200 (for example, a RedCap terminal).

[0078] Note that parameters f1 and fl1 may each be configured in advance in terminal 200, may be notified from base station 100 to terminal 200 using at least one of higher layer signaling and DCI, or may be defined in a standard. Also, f1 does not have to be configured in terminal 200. In this case, terminal 200 may configure, for example, the same PRB as the cell-specific PUCCH resource set as the PUCCH resource used by terminal 200.

[0079] For example, as shown in FIG. 10, when fl1 is "lower", terminal 200 may set the PRB to be used by terminal 200 based on the PRB set at the lower frequency end of the band in the uplink BWP for non-RedCap terminals and parameter f1.

[0080] Similarly, for example, as shown in FIG. 10, when fl1 is "higher", terminal 200 may set the PRB to be used by terminal 200 based on the PRB set at the higher frequency end of the band in the uplink BWP for non-RedCap terminals and parameter f1.

[0081] In this way, the PUCCH resources used by terminal 200 (e.g., a RedCap terminal) may include one PRB set based on the difference f1 and a PRB set at either end (e.g., the lower frequency or the higher frequency) of the UL BWP assigned to a non-RedCap terminal.

[0082] <S104> In FIG. 9, terminal 200 determines the PUCCH resource set r identified in the process of S103 from among the PUCCH resource sets determined in the process of S103.PUCCH The PUCCH (for example, a PUCCH sequence) is transmitted to the base station 100 using the PUCCH resource corresponding to the PUCCH.

[0083] Thus, in operation example 1, terminal 200 sets a PUCCH resource set to be used by terminal 200 (e.g., a RedCap terminal) based on information regarding the cell-specific PUCCH resource set and parameters set in terminal 200 (e.g., information regarding the difference between the cell-specific PUCCH resource and the PUCCH resource used by terminal 200).

[0084] Therefore, when determining the PUCCH resources to be used by the RedCap terminal, it is possible to use (in other words, reuse) the PUCCH resource configuration for non-RedCap terminals (e.g., information on a cell-specific PUCCH resource set). Furthermore, for example, if information on the PUCCH resources of the RedCap terminal (e.g., t1, f1, and fl1) is configured in advance in terminal 200, it is not necessary to add a signal for notifying the PUCCH resources. Furthermore, for example, the information on the PUCCH resources of the RedCap terminal is information f1 on the difference and information fl1 on one end of the uplink BWP. Therefore, even when this information is notified from base station 100 to terminal 200, an increase in the amount of information to be notified can be suppressed compared to when all of the information on the PUCCH resources is notified.

[0085] Therefore, according to the operation example 1, it is possible to suppress an increase in signaling overhead for the RedCap terminal.

[0086] Furthermore, for example, according to the PUCCH resource configuration shown in Fig. 10, terminal 200 uses one PRB and does not need to perform frequency hopping, and therefore does not need to perform frequency switching (e.g., RF retuning or BWP switching) of terminal 200. This can simplify the processing of terminal 200.

[0087] Furthermore, for example, according to the PUCCH resource configuration shown in FIG. 10, the number of PRBs occupied by the PUCCH resource set configured in terminal 200 can be reduced compared to a non-RedCap terminal, thereby suppressing the occurrence of fragmentation of PUSCH resources allocated to non-RedCap terminals.

[0088] In addition, in operation example 1, at least one of t1 and f1 may be 0 (in other words, no difference). For example, when at least one of t1 and f1 is 0, PUCCH resource overhead can be reduced. Also, when at least one of t1 and f1 is not 0, collisions of PUCCH resources between non-RedCap terminals and RedCap terminals can be reduced.

[0089] For example, even when t1=0, if f1≠0, it is possible to set a PUCCH resource (for example, PRB) for a RedCap terminal in the same slot as a non-RedCap terminal. Also, for example, even when f1=0, if t1≠0, it is possible to set a PUCCH resource for a RedCap terminal in a different slot from a non-RedCap terminal and in the same PRB as a non-RedCap terminal. Also, for example, even when t1=0 and f1=0, it is possible to set a PUCCH resource for a RedCap terminal in the same slot and the same PRB as a non-RedCap terminal, for example, in a different slot. PUCCH Alternatively, the PUCCH resource of the RedCap terminal can be configured by different cyclic shifts.

[0090] Furthermore, in operation example 1, f1 is not limited to a positive value and may be a negative value. In other words, in an uplink BWP, the PRB set for a RedCap terminal is not limited to being set in an area inside the PRB set for a non-RedCap terminal as shown in Fig. 10, but may be set outside (toward the edge of the BWP).

[0091] Furthermore, in operation example 1, t1 is not limited to a positive value and may be a negative value. In other words, the time resource (e.g., slot) configured for terminal 200 may be configured to be a slot before or after the cell-specific PUCCH resource.

[0092] <Operation Example 2> In operation example 2, for example, with respect to a PUCCH time resource (e.g., represented as "T2") for a RedCap terminal, base station 100 and terminal 200 may set multiple slots based on information regarding the setting of PUCCH time resources for non-RedCap terminals.

[0093] Furthermore, for example, with respect to a PUCCH frequency resource (e.g., represented as "F2") for a RedCap terminal, base station 100 and terminal 200 may configure multiple PRBs based on information regarding the configuration of PUCCH resources for non-RedCap terminals. For example, the PUCCH resource for a RedCap terminal may be configured to a PRB corresponding to both a frequency near the lowest frequency and a frequency near the highest frequency in the BWP of the non-RedCap terminal.

[0094] In operation example 2, for example, among the processes shown in Figure 9, the process of S103 is different from operation example 1 (hereinafter referred to as "S103'"), but the other processes (for example, S101, S102 and S103) may be the same as operation example 1.

[0095] <S103′> Terminal 200 may, for example, determine a PUCCH resource set to be used by terminal 200. For example, terminal 200 may determine the PUCCH resource set based on the notified cell-specific PUCCH resource set and parameters related to the PUCCH resource set to be used by terminal 200.

[0096] For example, in terminal 200, with respect to the time resource (T2) of the PUCCH, parameters "t2" and "t3" (e.g., integer values) may be configured that relate to multiple relative positions (e.g., differences or offsets) between the time resource (e.g., slot) in the cell-specific PUCCH resource set and the time resource (e.g., slot) in the PUCCH resource set used by terminal 200.

[0097] For example, when a cell-specific PUCCH resource set is placed in slot n, terminal 200 may set slot n+t2 and slot n+t3 as PUCCH resources to be used by terminal 200 (e.g., RedCap terminal).

[0098] At least one of parameters t2 and t3 may be configured in advance in terminal 200, may be notified from base station 100 to terminal 200 using at least one of higher layer signaling and DCI, or may be defined in a standard. Also, one of t2 and t3 does not have to be configured in terminal 200. For example, when t2 is not configured, terminal 200 may configure, for example, slot n and slot n+t3, which are the same as the cell-specific PUCCH resource set, as the PUCCH resources used by terminal 200.

[0099] In this way, the PUCCH resources used by terminal 200 (e.g., a RedCap terminal) may include slots included in the PUCCH resources of the cell-specific PUCCH resource set and multiple slots that are set based on parameters t2 and t3 (e.g., information regarding the difference in time resources).

[0100] Furthermore, for example, the terminal 200 may be configured with a parameter "f2" (e.g., an integer value) relating to the relative position (e.g., difference or offset) between a frequency resource (e.g., PRB) in a cell-specific PUCCH resource set and a frequency resource (e.g., PRB) in a PUCCH resource set used by the terminal 200, with respect to the PUCCH frequency resource (F2).

[0101] For example, terminal 200 determines parameter f2 and offset RBs included in the cell-specific PUCCH resource set. BWP offset Based on this, the PRB to RB at both ends of the band included in the uplink BWP of the non-RedCap terminal BWP offsetTwo PRBs separated by +f2 may be set as PUCCH resources to be used by terminal 200 (for example, RedCap terminal).

[0102] Note that parameter f2 may be configured in advance in terminal 200, may be notified from base station 100 to terminal 200 using at least one of higher layer signaling and DCI, or may be defined in a standard. Furthermore, f2 does not have to be configured in terminal 200. In this case, terminal 200 may configure, for example, the same PRB as the cell-specific PUCCH resource set as the PUCCH resource used by terminal 200.

[0103] As an example, the terminal 200 may, for example, as shown in FIG. 11, transmit a PRB to an RB at both ends of a band included in the uplink BWP of a non-RedCap terminal. BWP offset Of the PRBs spaced +f2 apart, the PRB with the lower frequency may be set to slot n+t2, and the PRB with the higher frequency may be set to slot n+t3.

[0104] Alternatively, the terminal 200 may, for example, select PRBs to RBs at both ends of the band included in the uplink BWP of the non-RedCap terminal. BWP offset Of the PRBs spaced +f2 apart, the PRB with the higher frequency may be set to slot n+t2, and the PRB with the lower frequency may be set to slot n+t3 (not shown).

[0105] In this way, the PUCCH resources used by terminal 200 (e.g., a RedCap terminal) may include PRBs set at each end (e.g., the lower frequency and the higher frequency) of the UL BWP assigned to the non-RedCap terminal and multiple PRBs set based on the difference f2.

[0106] Furthermore, multiple PRBs included in the PUCCH resource used by terminal 200 (for example, RedCap terminal) may be set to different slots (for example, slot n+t2 and slot n+t3).

[0107] Thus, in operation example 2, similar to operation example 1, terminal 200 sets a PUCCH resource set to be used by terminal 200 (e.g., a RedCap terminal) based on information regarding the cell-specific PUCCH resource set and parameters set in terminal 200 (e.g., information regarding the difference between the cell-specific PUCCH resource and the PUCCH resource used by terminal 200).

[0108] Therefore, when determining the PUCCH resources to be used by the RedCap terminal, it is possible to use (in other words, reuse) the PUCCH resource configuration for non-RedCap terminals (e.g., information on a cell-specific PUCCH resource set). Also, for example, if information on the PUCCH resources of the RedCap terminal (e.g., t2, t3, and f2) is configured in advance in terminal 200, it is not necessary to add a signal for notifying the PUCCH resources. Also, for example, the information on the PUCCH resources of the RedCap terminal is information t2, t3, and f2 related to the differences. Therefore, even when this information is notified from base station 100 to terminal 200, an increase in the amount of information to be notified can be suppressed compared to when all of the information on the PUCCH resources is notified.

[0109] Therefore, according to the second operational example, it is possible to suppress an increase in signaling overhead for the RedCap terminal.

[0110] Furthermore, in operation example 2, the PUCCH resources used by terminal 200 include multiple slots, and therefore, for example, frequency switching (e.g., RF retuning or BWP switching) between the multiple slots is permitted for terminal 200. Thus, in operation example 2, for example, the PUCCH resources used by terminal 200 include multiple PRBs, and inter-slot frequency hopping is applied to the PUCCH resources, thereby enabling the frequency diversity effect to improve the reception accuracy of the PUCCH at base station 100.

[0111] In addition, in operation example 2, for example, the PUCCH resources used by terminal 200 are set to PRBs near both ends of the band included in the uplink BWP of the non-RedCap terminal (for example, PRBs within a threshold from the end), and allocation near the center of the band included in the uplink BWP can be suppressed, thereby suppressing the occurrence of fragmentation of PUSCH resources allocated to non-RedCap terminals.

[0112] In addition, in operation example 2, either one of t2 and t3 or f2 may be 0 (in other words, no difference). For example, when either one of t2 and t3 or f2 is 0, it is possible to reduce PUCCH resource overhead. Also, for example, when either one of t2 and t3 or f2 is not 0, it is possible to reduce collisions of PUCCH resources between non-RedCap terminals and RedCap terminals.

[0113] Furthermore, in the second operational example, the number of slots included in the PUCCH resource used by the RedCap terminal is not limited to two, and may be three or more.

[0114] In addition, in FIG. 11, as an example, the PRB to RB at each end (low frequency side and high frequency side) of the uplink BWP is BWP offset Although a case has been described in which PRBs spaced +f2 apart are set as PUCCH resources used by terminal 200, the present invention is not limited to this.

[0115] For example, the offset values ​​from the PRBs at each end (low frequency side and high frequency side) of the uplink BWP may be different. BWP offset +f2 PRBs away and the PRB to RB at the other end of the uplink BWP BWP offset +f3 (where f2≠f3) PRBs apart may be set as PUCCH resources used by terminal 200.

[0116] Or, from PRB to RB at one end (either the low frequency side or the high frequency side) of the uplink BWP BWP offsetPRBs spaced +f2 apart may be set across multiple slots (eg, slots n+t2 and n+t3).

[0117] Furthermore, in operation example 2, f2 is not limited to a positive value and may be a negative value. In other words, in an uplink BWP, the PRB set for a RedCap terminal is not limited to being set in an area inside the PRB set for a non-RedCap terminal as shown in Fig. 11, but may be set outside (toward the edge of the BWP).

[0118] Furthermore, in operation example 2, at least one of t2 and t3 is not limited to a positive value and may be a negative value. In other words, the time resource (e.g., slot) configured for terminal 200 may be configured to be a slot before or after the cell-specific PUCCH resource.

[0119] In addition, in operation example 2, in the PUCCH transmitted over multiple slots, terminal 200 may repeatedly transmit the same content. In other words, terminal 200 may perform repetition transmission in multiple slots. Repetition transmission enables more robust transmission and reception, and can improve the reception quality at base station 100.

[0120] An example of the operation of the base station 100 and the terminal 200 has been described above.

[0121] As described above, in this embodiment, base station 100 and terminal 200 configure PUCCH resources (resources different from the Cell-specific PUCCH resource set) for RedCap terminals, for example, based on information regarding the configuration of PUCCH resources for non-RedCap terminals (for example, the configuration of a Cell-specific PUCCH resource set).

[0122] This allows terminal 200 to configure a PUCCH resource set for RedCap separately from a PUCCH resource set for non-RedCap terminals, for example, based on the configuration of a Cell-specific PUCCH resource set, thereby suppressing an increase in the amount of signals (signaling overhead) required to configure a PUCCH resource set for RedCap for RedCap terminals.

[0123] Furthermore, for example, the PUCCH frequency resource for a RedCap terminal includes one PRB in Operation Example 1, and includes multiple PRBs near both ends of the UL BWP of a non-RedCap terminal in Operation Example 2. This makes it possible to prevent the PUCCH resource for a RedCap terminal from dividing the PUSCH resource for a non-RedCap terminal, thereby suppressing degradation of the peak data rate.

[0124] Therefore, according to this embodiment, it is possible to improve the efficiency of resource allocation to terminal 200.

[0125] The embodiments of the present disclosure have been described above.

[0126] Other Embodiments (Modification 1) In each of the operation examples of the embodiment of the present disclosure described above, at least one of f1 and f2 may be given by the following equation (1).

[0127] where N CS indicates the number of initial CS indexes included in the "set of initial CS indexes" in the configured cell-specific PUCCH resource.

[0128] For example, when the index of the cell-specific PUCCH resource set shown in FIG. 1 is set to 8, N CS =4. In this case, according to formula (1), the value of at least one of f1 and f2 may be set to 2.

[0129] This allows the cell-specific PUCCH resources of the non-RedCap terminal and the cell-specific PUCCH resources of the RedCap terminal to be transmitted in adjacent PRBs, thereby preventing the PUCCH resources of the RedCap terminal from being divided into PUSCH resources of the non-RedCap terminal.

[0130] The value "8" used in equation (1) is, for example, the frequency direction of the PRB allocated at one end of the band included in the uplink BWP in the Cell-specific PUCCH resource. PUCCH (e.g., eight values ​​from 0 to 7 or eight values ​​from 8 to 15 in FIGS. 10 and 11 ). In other words, the value “8” used in equation (1) may be based on a value used to determine the PRB index of the PUCCH resource (e.g., each hop, as described below).

[0131] Furthermore, at least one of f1 and f2 may be given by the following formula (2).

[0132] According to equation (2), the PUCCH resource used by the RedCap terminal is set to an adjacent PRB outside the Cell-specific PUCCH resource.

[0133] (Modification 2) In each of the operation examples of the embodiment of the present disclosure described above, the size of the time resource (length of the time resource) of the cell-specific PUCCH resource may differ between a non-RedCap terminal and a RedCap terminal.

[0134] Here, when a non-RedCap terminal transmits a cell-specific PUCCH by frequency hopping, the time resources before and after hopping may be called "hops" (for example, first hop and second hop), respectively.

[0135] In variant 2, for example, the size of at least one of the time domain and frequency domain per slot in the PUCCH resource used by a RedCap terminal may be different from the size of the hop within a slot in the PUCCH resource used by a non-RedCap terminal.

[0136] For example, the length of the time resource for each hop may be half the number of symbols given by the cell-specific PUCCH resource configuration (eg, Number of symbols).

[0137] In this case, for example, as shown in Fig. 12, the length d1 of the time resource per slot of the PUCCH for RedCap terminals may be longer than the hop length d for non-RedCap terminals. In the example shown in Fig. 12, d1 is set to twice d. This increases the PUCCH resources allocated to RedCap terminals, and the coding rate is reduced, thereby improving reception accuracy at base station 100.

[0138] Alternatively, for example, d1 may be set to be shorter than the hop length d in a non-RedCap terminal, thereby reducing resource overhead caused by PUCCH transmission in a RedCap terminal.

[0139] Note that d1 may be a value that is preset in terminal 200, or may be a value that is notified from base station 100 to terminal 200. Also, for example, multiple candidates for the value of d1 may be set, and multiple candidates may be switchable.

[0140] Similarly, the size of the frequency resource of the PUCCH used by a RedCap terminal may be different from the size of the frequency resource of each hop in the PUCCH used by a non-RedCap terminal. For example, the size of the frequency resource of the PUCCH of a RedCap terminal may be larger or smaller than the frequency resource size of a hop in the PUCCH of a non-RedCap terminal. This makes it possible, in the frequency domain as well as in the time domain, to improve reception accuracy at base station 100 by increasing the PUCCH resources allocated to RedCap terminals, or to reduce resource overhead due to PUCCH transmission from RedCap terminals by reducing the PUCCH resources allocated to RedCap terminals.

[0141] (Modification 3) In the embodiment of the present disclosure described above, different CSs may be applied between the cell-specific PUCCH of a non-RedCap terminal and the cell-specific PUCCH of a RedCap terminal.

[0142] For example, a RedCap terminal may transmit a cell-specific PUCCH using an initial CS index obtained by shifting the value of the initial CS index used by a non-RedCap terminal by c1. c1 may be, for example, 1 or a value different from 1. In other words, the CS value corresponding to the PUCCH resource used by a RedCap terminal may be a value obtained by adding an offset (c1) to the CS value corresponding to the PUCCH resource used by a non-RedCap terminal.

[0143] This ensures the orthogonality of the PUCCHs even when a RedCap terminal and a non-RedCap terminal transmit PUCCHs using the same time resources and frequency resources. Note that c1 may be a value that is preset in the terminal 20, a value that is notified from the base station 100 to the terminal 200, or a value that is specified in a standard.

[0144] (Variant 4) In one embodiment of the present disclosure, parameters (e.g., at least one of t1, t2, t3, f1, f2, d1, c1, and fl1) set in a RedCap terminal may be given fixed values, or the values ​​may be explicitly or implicitly notified by a control signal, or may be notified in combination with other parameters of the cell-specific PUCCH resource set.

[0145] For example, a column corresponding to at least one of t1, t2, t3, f1, f2, d1, c1, and fl1 may be added to a table used to determine a cell-specific PUCCH resource set (for example, the table shown in Figure 1), and may be notified in combination with parameters such as the PUCCH format, symbol, or PRB.

[0146] As an example, Figure 13 shows an example in which a value of "fl1" (e.g., lower or higher) is added in the association (e.g., information in a table format) between parameters (combinations of parameters) and indices (information identifying combinations of parameters) related to the resource set of the cell-specific PUCCH shown in Figure 1. That is, as shown in Figure 13, parameter combination candidates including both information related to the configuration of PUCCH resources for non-RedCap terminals and information related to PUCCH resources for RedCap terminals may be associated with indices that identify the candidates.

[0147] Note that FIG. 13 is an example, and is not limited to fl1, and other parameters may be added to the table shown in FIG.

[0148] For example, terminal 200 may determine a parameter (e.g., fl) to be set in the RedCap terminal based on an index of a parameter related to a cell-specific PUCCH resource set with reference to Fig. 13. Therefore, in the fourth modification, since it is possible to notify the parameter to be set in the RedCap terminal by using an existing index, it is possible to suppress an increase in signaling overhead.

[0149] For a cell-specific PUCCH resource set, the values ​​of t1, t2, t3, f1, f2, d1, c1, or fl1 may be set to be multiple selectable for a combination of parameters in which at least one of the PUCCH format, number of symbols, PRB offset, and set of initial CS index is the same. As an example, Index=1 and 2 shown in FIG. 13 have the same combination of PUCCH format, number of symbols, and set of initial CS index, but different values ​​of fl1. This increases the number of PUCCH resource patterns that can be configured for the same PUCCH format, number of symbols, or set of initial CS index, thereby improving the flexibility of PUCCH resource configuration.

[0150] Furthermore, for a cell-specific PUCCH resource set, the values ​​of t1, t2, t3, f1, f2, d1, c1, or fl1 may be the same for parameter combinations where at least one setting value of the PUCCH format, number of symbols, PRB offset, and set of initial CS index is the same. This reduces the number of PUCCH resource patterns that can be set for the same PUCCH format, number of symbols, PRB offset, or set of initial CS index, and can reduce the amount of processing (e.g., the amount of calculation) in terminal 200.

[0151] Furthermore, in a combination of parameters related to a cell-specific PUCCH resource set (for example, the table shown in FIG. 13 ), the number of indexes associated with a combination (for example, a row in the table) in which fl is either lower or higher may be greater than the number of indexes associated with a combination (for example, a row in the table) in which fl is the other of lower and higher. This increases the likelihood that the PUCCH of a RedCap terminal will be allocated to a frequency resource at either end in an uplink BWP, for example, and enables a reduction in the amount of processing (for example, the amount of calculation) in terminal 20.

[0152] In addition, in the fourth modification, information (for example, a column) regarding the configuration of PUCCH resources for RedCap terminals in the table regarding cell-specific PUCCH resources may be added to a table used by both RedCap terminals and non-RedCap terminals. Alternatively, a table (for example, a dedicated table) for RedCap terminals may be provided separately from the table for non-RedCap terminals, and columns corresponding to information regarding the configuration of PUCCH resources for RedCap terminals may be set (for example, added) to this table.

[0153] Figure 14 shows an example of a table dedicated to RedCap terminals. The cell-specific PUCCH resources provided by the table dedicated to RedCap terminals shown in Figure 14 may be different from the cell-specific PUCCH resources provided by a table for non-RedCap mobile stations (e.g., Figure 1). For example, the table shown in Figure 14 may allow more parameters with a larger number of symbols (or PUCCH format 1) to be set compared to the table shown in Figure 1.

[0154] For example, in the table shown in Fig. 14, the number of indexes giving the number of symbols = 14 or 10 may be set to be larger than in the table shown in Fig. 1. This increases the likelihood that a PUCCH with a longer number of symbols will be set for a RedCap terminal, whose performance is limited compared to non-RedCap terminals, and can improve the reception performance of signals transmitted from RedCap terminals.

[0155] Alternatively, parameters with fewer symbols (or PUCCH format 0) may be configured more frequently in cell-specific PUCCH resources provided by a table for RedCap terminals compared to cell-specific PUCCH resources provided by a table for non-RedCap terminals, thereby reducing the overhead of resources used by RedCap terminals.

[0156] The association between the combinations of parameters related to cell-specific PUCCH resources and the indexes that identify each combination is not limited to the table format information shown in Figures 13 and 14, and may be information in other formats.

[0157] (Variation 5) In one embodiment of the present disclosure, as an example, a case has been described in which the frequency resource of the cell-specific PUCCH for a RedCap terminal is determined based on the frequency location of the BWP for a non-RedCap terminal, but this is not limiting. For example, the frequency resource of the cell-specific PUCCH for a RedCap terminal may be determined based on the frequency location of the BWP for the RedCap terminal.

[0158] For example, even when the frequency resource of the cell-specific PUCCH for a RedCap terminal is determined based on the frequency position of the BWP for the RedCap terminal, one PRB may be set in a certain slot, as in Figure 10, or multiple PRBs may be set in different slots, as in Figure 11.

[0159] In this case, the terminal 200 may also receive, for example, information on the frequency location of the BWP for the RedCap terminal from the base station 100.

[0160] (Variation 6) In Operation Example 1, the combination of T1+F1 is described, and in Operation Example 2, the combination of T2+F2 is described, but this is not limited to this, and any one of T1, T2, F1, and F2 may be applied, or other combinations may be applied.

[0161] For example, by combining T1 and F2, multiple PRBs in one slot may be configured in the PUCCH resource used by terminal 200. For example, in slot n+t1, base station 100 and terminal 200 may configure RBs from PRBs at both ends of the band included in the uplink BWP of the non-RedCap terminal. BWP offset Two PRBs separated by +f2 PRBs may be set as PUCCH resources used by terminal 200.

[0162] Furthermore, for example, by the combination of T2+F1, one PRB in each of a plurality of slots may be configured in the PUCCH resource used by terminal 200. For example, base station 100 and terminal 200 may configure one PRB from one of the bands included in the uplink BWP of the non-RedCap terminal in each of a plurality of slots (for example, slot n+t2 and slot n+t3). BWP offset One PRB separated by +f2 PRBs may be set as the PUCCH resource used by terminal 200.

[0163] Alternatively, for example, a combination of T2+F1+F2 may be used. For example, in some of the slots used by the terminal 200, the PRBs and RBs at both ends of the band included in the uplink BWP of the non-RedCap terminal may be used. BWP offset +f2 apart, and in the remaining slots of the multiple slots used by the terminal 200, the PRBs at both ends of the band included in the uplink BWP of the non-RedCap terminal are used. BWP offset Either one of two PRBs separated by +f2 positions may be used.

[0164] Alternatively, any one of T1, T2, F1, and F2 may be applied. For example, when T1 or T2 is applied, the frequency resources (e.g., PRBs) of the PUCCH may be the same as the resources in the cell-specific PUCCH resource set. Similarly, for example, when F1 or F2 is applied, the time resources (e.g., slots) of the PUCCH may be the same as the resources in the cell-specific PUCCH resource set.

[0165] By setting the PUCCH resources used by terminal 200 in this manner, it is possible to improve the flexibility of allocation of PUCCH resources.

[0166] In addition, the PUCCH resource settings for the RedCap terminal (for example, the above-mentioned T1, T2, F1 and F2) may be switchable.

[0167] The above describes the modified examples.

[0168] (Type and Identification of Terminal) The above embodiment may be applied to, for example, a "RedCap terminal" or a non-RedCap terminal.

[0169] Note that a RedCap terminal may be a terminal that has at least one of the following characteristics (in other words, properties, attributes, or capabilities): (1) A terminal that notifies (e.g., reports) the base station 100 that it is a "terminal that is a target of coverage extension," a "terminal that receives repeatedly transmitted signals," or a "RedCap terminal." Note that, for example, uplink channels such as PRACH and PUSCH, or uplink signals such as Sounding Reference Signal (SRS) may be used for the above notification (report). (2) A terminal that corresponds to at least one of the following capabilities, or a terminal that reports at least one of the following capabilities to the base station 100. Note that, for example, uplink channels such as PRACH and PUSCH, or uplink signals such as UCI or SRS may be used for the above report. - A terminal that can support a frequency bandwidth that is equal to or less than a threshold (e.g., 20 MHz, 40 MHz, or 100 MHz). - A terminal that has the number of implemented receive antennas that is equal to or less than a threshold (e.g., threshold = 1). - A terminal whose number of supportable downlink ports (e.g., number of receive antenna ports) is equal to or less than a threshold (e.g., threshold = 2). - A terminal whose supportable number of transmission ranks (e.g., maximum number of Multiple-Input Multiple-Output (MIMO) layers (or number of ranks)) is equal to or less than a threshold (e.g., threshold = 2). - A terminal that can transmit and receive signals in a frequency band equal to or greater than a threshold (e.g., Frequency Range 2 (FR2) or a band equal to or greater than 52 GHz). - A terminal whose processing time is equal to or greater than a threshold. - A terminal whose usable transport block size (TBS) is equal to or less than a threshold. - A terminal whose usable number of transmission ranks (e.g., number of MIMO transmission layers) is equal to or less than a threshold. - A terminal whose usable modulation order is equal to or less than a threshold. - A terminal whose usable number of Hybrid Automatic Repeat request (HARQ) processes is equal to or less than a threshold. - A terminal that supports Rel-17 or later. (3) A terminal to which parameters corresponding to RedCap terminals are notified from base station 100.In addition, the parameters corresponding to the RedCap mobile station may include, for example, a parameter such as a Subscriber Profile ID for RAT / Frequency Priority (SPID).

[0170] In addition, "non-RedCap terminal" or "non-RedCap terminal" may mean, for example, a terminal that supports Rel-15 / 16 (e.g., a terminal that does not support Rel-17), or a terminal that supports Rel-17 but does not have the above characteristics.

[0171] (Type of Signal / Channel) Note that, in the above embodiment, resource allocation for uplink channels and signals (e.g., PUCCH) has been described, but the above embodiment may also be applied to downlink channels and signals (e.g., any of PUCCH, PUSCH, and PRACH) or other uplink channels and signals (e.g., any of PUSCH and PRACH).

[0172] Furthermore, in the above embodiment, a case has been described in which resources for a data signal (e.g., a PDSCH or a PUSCH) are assigned to terminal 200 by a PDCCH (e.g., downlink control information), but this is not limited to this, and resources may be set by, for example, a higher layer signal.

[0173] Furthermore, the PDCCH may be transmitted, for example, in either a Common Search Space (CSS) or a UE Specific Search Space (USS).

[0174] Furthermore, in one embodiment of the present disclosure, a method for configuring PUCCH resources for a RedCap terminal based on configuration of a cell-specific PUCCH resource set has been described as an example, but in one embodiment of the present disclosure, the PUCCH resources for a RedCap terminal are not limited to the cell-specific PUCCH resource set and may be determined based on other resource configurations. Also, in one embodiment of the present disclosure, a method for configuring PUCCH resources has been described as an example, but the target of resource configuration is not limited to PUCCH and may be other channels or signals.

[0175] In addition, the number of slots, the number of PRBs, the PRB offset, the number of symbols, the PUCCH format, the CS value, and r PUCCH The parameter values ​​such as the values ​​are merely examples, and other values ​​may be used.

[0176] Furthermore, the notation "... section" in each of the above-described embodiments may be replaced with other notations such as "... circuitry," "... device," "... unit," or "... module."

[0177] (Supplementary Note) Information indicating whether the terminal 200 supports the functions, operations, or processes described in the above-described embodiments may be transmitted (or notified) from the terminal 200 to the base station 100, for example, as capability information or capability parameters of the terminal 200.

[0178] The capability information may include an information element (IE) that individually indicates whether or not the terminal 200 supports at least one of the functions, operations, or processes described in the above-described embodiments. Alternatively, the capability information may include an information element that indicates whether or not the terminal 200 supports a combination of any two or more of the functions, operations, or processes described in the above-described embodiments, modifications, and supplements.

[0179] For example, the base station 100 may determine (or decide or assume) functions, operations, or processes that the terminal 200 that transmitted the capability information supports (or does not support) based on the capability information received from the terminal 200. The base station 100 may perform operations, processes, or control according to the determination result based on the capability information. For example, the base station 100 may control allocation (in other words, scheduling) of at least one uplink resource such as a PUCCH based on the capability information received from the terminal 200.

[0180] Note that the fact that terminal 200 does not support some of the functions, operations, or processes described in the above-described embodiments may be interpreted as meaning that such some of the functions, operations, or processes are restricted in terminal 200. For example, information or a request regarding such restrictions may be notified to base station 100.

[0181] Information regarding the capabilities or limitations of terminal 200 may, for example, be defined in a standard, or may be implicitly notified to base station 100 in association with information known at base station 100 or information transmitted to base station 100.

[0182] (Control Signal) In the present disclosure, a downlink control signal (or downlink control information) related to an embodiment of the present disclosure may be, for example, a signal (or information) transmitted in a Physical Downlink Control Channel (PDCCH) of a physical layer, or a signal (or information) transmitted in a Medium Access Control Control Element (MAC CE) or Radio Resource Control (RRC) of a higher layer. Furthermore, the signal (or information) is not limited to being notified by a downlink control signal, but may be predefined in a specification (or standard) or preconfigured in a base station and a terminal.

[0183] In the present disclosure, an uplink control signal (or uplink control information) related to an embodiment of the present disclosure may be, for example, a signal (or information) transmitted in a PUCCH of a physical layer, or a signal (or information) transmitted in a MAC CE or RRC of a higher layer. Furthermore, the signal (or information) is not limited to being notified by an uplink control signal, but may be predefined in a specification (or standard) or preconfigured in a base station and a terminal. Furthermore, the uplink control signal may be replaced with, for example, uplink control information (UCI), 1st stage sidelink control information (SCI), or 2nd stage SCI.

[0184] (Base Station) In an embodiment of the present disclosure, the base station may be a Transmission Reception Point (TRP), a cluster head, an access point, a Remote Radio Head (RRH), an eNodeB (eNB), a gNodeB (gNB), a Base Station (BS), a Base Transceiver Station (BTS), a parent device, a gateway, or the like. In sidelink communication, a terminal may play the role of a base station. Instead of a base station, a relay device that relays communication between an upper node and a terminal may be used. Alternatively, a roadside unit may be used.

[0185] (Uplink / Downlink / Sidelink) An embodiment of the present disclosure may be applied to, for example, any of the uplink, downlink, and sidelink. For example, an embodiment of the present disclosure may be applied to a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), or a Physical Random Access Channel (PRACH) in the uplink, a Physical Downlink Shared Channel (PDSCH), a PDCCH, or a Physical Broadcast Channel (PBCH) in the downlink, or a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Control Channel (PSCCH), or a Physical Sidelink Broadcast Channel (PSBCH) in the sidelink.

[0186] The PDCCH, PDSCH, PUSCH, and PUCCH are examples of a downlink control channel, a downlink data channel, an uplink data channel, and an uplink control channel, respectively. The PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel. The PBCH and PSBCH are examples of a broadcast channel, and the PRACH is an example of a random access channel.

[0187] (Data Channel / Control Channel) An embodiment of the present disclosure may be applied to, for example, either a data channel or a control channel. For example, the channel in an embodiment of the present disclosure may be replaced with any of the data channels PDSCH, PUSCH, and PSSCH, or the control channels PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.

[0188] (Reference Signal) In one embodiment of the present disclosure, a reference signal is, for example, a signal known by both a base station and a mobile station, and may also be called a Reference Signal (RS) or a pilot signal. The reference signal may be any of a Demodulation Reference Signal (DMRS), a Channel State Information - Reference Signal (CSI-RS), a Tracking Reference Signal (TRS), a Phase Tracking Reference Signal (PTRS), a Cell-specific Reference Signal (CRS), or a Sounding Reference Signal (SRS).

[0189] (Time Interval) In one embodiment of the present disclosure, the unit of time resource is not limited to one or a combination of slots and symbols, but may be, for example, a time resource unit such as a frame, a superframe, a subframe, a slot, a time slot subslot, a minislot, or a symbol, an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier-Frequency Division Multiplexing (SC-FDMA) symbol, or another time resource unit. Furthermore, the number of symbols included in one slot is not limited to the number of symbols exemplified in the above-mentioned embodiment, and may be another number of symbols.

[0190] (Frequency Band) An embodiment of the present disclosure may be applied to either a licensed band or an unlicensed band (unlicensed spectrum, shared spectrum). A channel access procedure (Listen Before Talk (LBT), carrier sense, Channel Clear Assessment (CCA)) may be performed before each signal transmission.

[0191] (Communication) An embodiment of the present disclosure may be applied to communication between a base station and a terminal (Uu link communication), communication between terminals (Sidelink communication), or Vehicle to Everything (V2X) communication. For example, the channel in an embodiment of the present disclosure may be replaced with any of PSCCH, PSSCH, Physical Sidelink Feedback Channel (PSFCH), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, or PBCH.

[0192] An embodiment of the present disclosure may be applied to a terrestrial network, a non-terrestrial network (NTN) using a satellite or a high altitude pseudo satellite (HAPS), or a terrestrial network in which transmission delay is large compared to the symbol length or slot length, such as a network with a large cell size or an ultra-wideband transmission network.

[0193] (Antenna Port) In one embodiment of the present disclosure, an antenna port refers to a logical antenna (antenna group) consisting of one or more physical antennas. For example, an antenna port does not necessarily refer to a single physical antenna, but may refer to an array antenna consisting of multiple antennas. For example, the number of physical antennas that an antenna port is composed of is not specified, and the antenna port may be specified as the smallest unit by which a terminal station can transmit a reference signal. Furthermore, an antenna port may also be specified as the smallest unit by which a weighting of a precoding vector is multiplied.

[0194] 5G NR System Architecture and Protocol Stack 3GPP continues work on the next release of fifth-generation cellular technology (also referred to simply as "5G"), which includes the development of new radio access technology (NR) operating in the frequency range up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, allowing for the prototyping and commercial deployment of 5G NR-compliant devices (e.g., smartphones).

[0195] For example, the system architecture generally assumes a Next Generation - Radio Access Network (NG-RAN) comprising gNBs. The gNBs provide UE-side termination of NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols. The gNBs are connected to each other via an Xn interface. The gNBs are also connected to a Next Generation Core (NGC) via a Next Generation (NG) interface, more specifically to an Access and Mobility Management Function (AMF) (e.g., a specific core entity performing AMF) via an NG-C interface, and to a User Plane Function (UPF) (e.g., a specific core entity performing UPF) via an NG-U interface. The NG-RAN architecture is shown in Figure 15 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0196] The NR user plane protocol stack (see, for example, 3GPP TS 38.300, section 4.4.1) includes a PDCP (Packet Data Convergence Protocol (see, for example, TS 38.300, section 6.4)) sublayer, a RLC (Radio Link Control (see, for example, TS 38.300, section 6.3)) sublayer, and a MAC (Medium Access Control (see, for example, TS 38.300, section 6.2)) sublayer, which are terminated on the network side in the gNB. A new access stratum (AS) sublayer (SDAP: Service Data Adaptation Protocol) has also been introduced above PDCP (see, for example, 3GPP TS 38.300, section 6.5). A control plane protocol stack has also been defined for the NR (see, for example, TS 38.300, section 4.4.2). An overview of Layer 2 functions is described in Section 6 of TS 38.300. The functions of the PDCP sublayer, RLC sublayer, and MAC sublayer are listed in clauses 6.4, 6.3, and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in clause 7 of TS 38.300.

[0197] For example, the Medium-Access-Control layer handles logical channel multiplexing and scheduling and scheduling-related functions, including handling various numerologies.

[0198] For example, the physical layer (PHY) is responsible for coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping of signals to appropriate physical time-frequency resources. The physical layer also handles mapping of transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used for transmitting a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, physical channels include the Physical Random Access Channel (PRACH), the Physical Uplink Shared Channel (PUSCH), and the Physical Uplink Control Channel (PUCCH) as uplink physical channels, and the Physical Downlink Shared Channel (PDSCH), the Physical Downlink Control Channel (PDCCH), and the Physical Broadcast Channel (PBCH) as downlink physical channels.

[0199] NR use cases / deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communication (mMTC), which have diverse requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps in the downlink and 10 Gbps in the uplink) and effective (user-experienced) data rates approximately three times higher than those offered by IMT-Advanced. On the other hand, URLLC imposes stricter requirements on ultra-low latency (0.5 ms for user plane latency in both UL and DL) and high reliability (1-10-5 within 1 ms). Finally, mMTC preferably requires high connection density (1,000,000 devices / km in urban environments).２ ), wide coverage in adverse environments, and extremely long battery life (15 years) for a low-cost device may be desired.

[0200] Therefore, OFDM numerology (e.g., subcarrier spacing, OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) suitable for one use case may not be valid for another use case. For example, low-latency services may preferably require a shorter symbol length (and therefore a larger subcarrier spacing) and / or fewer symbols per scheduling interval (also referred to as TTI) than mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require a longer CP length than scenarios with short delay spreads. The subcarrier spacing may be optimized accordingly to maintain similar CP overhead. NR may support one or more subcarrier spacing values. Correspondingly, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, etc. are currently considered. The symbol length Tu and subcarrier spacing Δf are directly related by the formula Δf = 1 / Tu. Similar to LTE systems, the term "resource element" can be used to mean the smallest resource unit consisting of one subcarrier for the length of one OFDM / SC-FDMA symbol.

[0201] In the new radio system 5G-NR, for each numerology and each carrier, a resource grid of subcarriers and OFDM symbols is defined for each uplink and downlink. Each element of the resource grid is called a resource element and is specified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211 v15.6.0).

[0202] <Functional Separation Between NG-RAN and 5GC in 5G NR> Figure 16 shows the functional separation between NG-RAN and 5GC. The logical node of NG-RAN is gNB or ng-eNB. 5GC has logical nodes AMF, UPF, and SMF.

[0203] For example, gNB and ng-eNB host the following main functions: - Radio Resource Management functions such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, dynamic allocation (scheduling) of resources to UEs in both uplink and downlink; - IP header compression, ciphering and integrity protection of data; - AMF selection at UE attach time if routing to the AMF cannot be determined from the information provided by the UE; - Routing of user plane data towards the UPF; - Routing of control plane information towards the AMF; - Connection setup and release; - Scheduling and transmission of paging messages; - Scheduling and transmission of system broadcast information (sourced from the AMF or Operation, Admission, Maintenance (OAM)); - Configuration of measurements and measurement reports for mobility and scheduling; - Transport level packet marking in the uplink; - Session management; Support for network slicing; - QoS flow management and mapping to data radio bearers; - Support for UEs in RRC_INACTIVE state; - NAS message delivery function; - Radio access network sharing; - Dual connectivity; - Close coordination between NR and E-UTRA.

[0204] The Access and Mobility Management Function (AMF) hosts the following main functions: - Termination of Non-Access Stratum (NAS) signaling; - Security of NAS signaling; - Security control of Access Stratum (AS); - Signaling between Core Network (CN) nodes for mobility between 3GPP access networks; - Reachability to idle mode UEs (including control and execution of paging retransmissions); - Registration area management; - Support for intra-system and inter-system mobility; - Access authentication; - Access authorization including checking of roaming rights; - Mobility management control (subscription and policy); - Support for network slicing; - Selection of Session Management Function (SMF).

[0205] Furthermore, the User Plane Function (UPF) hosts the following main functions: - anchor point for intra-RAT / inter-RAT mobility (if applicable); - external PDU (Protocol Data Unit) session point for interconnection with data networks; - packet routing and forwarding; - packet inspection and policy rule enforcement for the user plane part; - traffic usage reporting; - uplink classifier to support routing of traffic flows to the data network; - branching point to support multi-homed PDU sessions; - QoS processing for the user plane (e.g. packet filtering, gating, UL / DL rate enforcement); - uplink traffic validation (mapping of SDF to QoS flows); - downlink packet buffering and triggering of downlink data notifications.

[0206] Finally, the Session Management Function (SMF) hosts the following main functions: session management; allocation and management of IP addresses for UEs; selection and control of UPF; configuration of traffic steering in the User Plane Function (UPF) to route traffic to the appropriate destination; policy enforcement and QoS of the control part; downlink data notification.

[0207] <RRC connection setup and reconfiguration procedure> Figure 17 shows some of the interactions between the UE, gNB, and AMF (5GC entities) when the UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS part (see TS 38.300 v15.6.0).

[0208] RRC is a higher layer signaling (protocol) used to configure the UE and gNB. With this transition, the AMF prepares UE context data (including, for example, PDU session context, security keys, UE radio capabilities, UE security capabilities, etc.) and sends it to the gNB along with an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE, and the UE responding with a SecurityModeComplete message to the gNB. The gNB then sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB performs reconfiguration to set up Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, the steps related to RRCReconfiguration are omitted because SRB2 and DRB are not set up. Finally, the gNB notifies the AMF that the setup procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.

[0209] Accordingly, the present disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) that includes: a control circuit that, upon operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmitter that, upon operation, transmits an initial context setup message to the gNodeB via the NG connection so that a signaling radio bearer between the gNodeB and a user equipment (UE) is set up. Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling, including a resource allocation configuration information element (IE), to the UE via the signaling radio bearer. The UE then transmits in uplink or receives in downlink based on the resource allocation configuration.

[0210] <IMT Usage Scenarios Beyond 2020> Figure 18 shows some use cases for 5G NR. The 3rd Generation Partnership Project New Radio (3GPP NR) is considering three use cases envisioned by IMT-2020 to support a wide variety of services and applications. The first phase of specifications for enhanced mobile broadband (eMBB) has been completed. Current and future work includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC), in addition to expanding support for eMBB. Figure 18 shows some examples of envisioned usage scenarios for IMT beyond 2020 (see, for example, ITU-R M.2083 Figure 2).

[0211] The URLLC use case has stringent performance requirements for throughput, latency, and availability. It is envisioned as one of the enabling technologies for future applications such as wireless control of industrial production or manufacturing processes, remote medical surgery, automated power transmission and distribution in smart grids, and road safety. URLLC's ultra-high reliability is supported by identifying technologies that meet the requirements set by TR 38.913. Key requirements for NR URLLC in Release 15 include a target user plane latency of 0.5 ms on the uplink (UL) and 0.5 ms on the downlink (DL). The overall URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E-5 for a 32-byte packet size with a user plane latency of 1 ms.

[0212] From a physical layer perspective, reliability can be improved in many possible ways. Current room for reliability improvement includes defining a separate CQI table for URLLC, more compact DCI formats, PDCCH repetition, etc. However, this room can be expanded to achieve ultra-high reliability as NR (with respect to the key requirements of NR URLLC) becomes more stable and developed. Specific use cases for NR URLLC in Release 15 include Augmented Reality / Virtual Reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0213] Additionally, the technology enhancements targeted by NR URLLC aim to improve latency and reliability. Technology enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition in the data channel, and preemption in the downlink. Preemption means that a transmission with already allocated resources is stopped and the already allocated resources are used for another transmission with a later requested lower latency / higher priority. Therefore, a previously allowed transmission is preempted by a later transmission. Preemption is applicable regardless of the specific service type. For example, a transmission of service type A (URLLC) may be preempted by a transmission of service type B (eMBB, etc.). Technology enhancements for reliability improvement include a dedicated CQI / MCS table for a target BLER of 1E-5.

[0214] The use case of mMTC (massive machine type communication) is characterized by a very large number of connected devices that typically transmit relatively small amounts of data that are not sensitive to delays. These devices are required to be low-cost and have very long battery life. From the NR perspective, utilizing very narrow bandwidth portions is one solution that saves power and extends battery life from the UE's perspective.

[0215] As mentioned above, the scope of reliability improvement in NR is expected to be broader. One of the key requirements for all cases, for example, URLLC and mMTC, is high or ultra-high reliability. Several mechanisms can improve reliability from a radio perspective and a network perspective. Generally, there are two to three key areas that can help improve reliability. These areas include compact control channel information, repetition of data channels / control channels, and diversity in the frequency, time, and / or spatial domains. These areas are generally applicable to reliability improvement regardless of the specific communication scenario.

[0216] For NR URLLC, further use cases with more stringent requirements are envisaged, such as factory automation, transportation, and power distribution, with high reliability (up to 10-6 level reliability), high availability, packet size up to 256 bytes, time synchronization down to a few μs (depending on the use case, the value can be 1 μs or a few μs depending on the frequency range and low latency in the order of 0.5 ms to 1 ms (e.g., 0.5 ms latency on the targeted user plane)).

[0217] Furthermore, for NR URLLC, there may be several technical enhancements from the physical layer perspective. These technical enhancements include PDCCH (Physical Downlink Control Channel) enhancements for compact DCI, PDCCH repetition, and increased PDCCH monitoring. Also, UCI (Uplink Control Information) enhancements relate to enhanced Hybrid Automatic Repeat Request (HARQ) and CSI feedback enhancements. There may also be PUSCH enhancements related to minislot-level hopping and retransmission / repetition enhancements. The term "minislot" refers to a Transmission Time Interval (TTI) that contains fewer symbols than a slot (a slot comprises 14 symbols).

[0218] <QoS Control> The 5G Quality of Service (QoS) model is based on QoS flows and supports both QoS flows that require a guaranteed flow bit rate (Guaranteed Bit Rate QoS flows (GBR)) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Thus, at the NAS level, a QoS flow is the finest granularity of QoS classification in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI) carried in an encapsulation header over the NG-U interface.

[0219] For each UE, 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) for each PDU session, e.g., as shown above with reference to Figure 17. Additional DRBs for the QoS flows of that PDU session can be configured later (when this is up to the NG-RAN). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0220] Figure 19 shows the non-roaming reference architecture for 5G NR (see TS 23.501 v16.1.0, section 4.23). An Application Function (AF) (e.g., an external application server hosting 5G services, as illustrated in Figure 18) interacts with the 3GPP core network to provide services. For example, it may access a Network Exposure Function (NEF) to support applications that affect traffic routing, or interact with a policy framework for policy control (e.g., QoS control) (see Policy Control Function (PCF)). Based on operator deployment, Application Functions considered trusted by the operator can interact directly with associated Network Functions. Application Functions not permitted by the operator to directly access Network Functions interact with associated Network Functions using an external exposure framework via the NEF.

[0221] Figure 19 further illustrates further functional units of the 5G architecture, namely, Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and Data Network (DN, e.g., operator-provided services, Internet access, or third-party services). All or part of the core network functions and application services may be deployed and run in a cloud computing environment.

[0222] Therefore, the present disclosure provides an application server (e.g., an AF in a 5G architecture) comprising: a transmitter that, in operation, sends a request including QoS requirements for at least one of a URLLC service, an eMMB service, and an mMTC service to at least one of 5GC functions (e.g., an NEF, an AMF, an SMF, a PCF, an UPF, etc.) to establish a PDU session including a radio bearer between a gNodeB and a UE according to the QoS requirements; and a control circuit that, in operation, performs a service using the established PDU session.

[0223] The present disclosure can be realized by software, hardware, or software integrated with hardware. Each functional block described in the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit. Each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of a single chip that includes some or all of the functional blocks. The LSI may have data inputs and outputs. Depending on the level of integration, an LSI may be referred to as an IC, system LSI, super LSI, or ultra LSI. The integrated circuit implementation is not limited to LSIs, and may be realized using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, a field programmable gate array (FPGA), which can be programmed after LSI fabrication, or a reconfigurable processor, which allows the connections and settings of circuit cells within an LSI to be reconfigured, may also be used. The present disclosure may be realized as digital or analog processing. Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology may be used to integrate functional blocks. The application of biotechnology, etc. is also a possibility.

[0224] The present disclosure may be implemented in any type of apparatus, device, or system (collectively referred to as a communications apparatus) that has a communications function. The communications apparatus may include a radio transceiver and processing / control circuitry. The radio transceiver may include a receiver and a transmitter, or both functions. The radio transceiver (transmitter and receiver) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like. Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above devices.

[0225] The communication devices are not limited to portable or mobile devices, but also include any kind of non-portable or fixed equipment, devices, and systems, such as smart home devices (such as home appliances, lighting equipment, smart meters or measuring devices, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0226] Communications include data communications via cellular systems, wireless LAN systems, communication satellite systems, and the like, as well as data communications via combinations of these.

[0227] A communications apparatus also includes devices such as controllers and sensors connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.

[0228] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.

[0229] A terminal according to one embodiment of the present disclosure includes a control circuit that sets a second resource, which is different from the first resource, for a second type of terminal based on information regarding the setting of a first resource for a first type of terminal, and a transmission circuit that transmits a signal using the second resource.

[0230] In one embodiment of the present disclosure, the control circuit configures the second resource based on information about the configuration and information about a difference between the first resource and the second resource.

[0231] In one embodiment of the present disclosure, the second resource includes one resource block set based on the difference between a resource block set at either end of the bandwidth portion allocated to the first type of terminal.

[0232] In one embodiment of the present disclosure, the second resource includes a plurality of second resource blocks that are set based on the difference between each of a plurality of first resource blocks included in the first resource.

[0233] In one embodiment of the present disclosure, the plurality of second resource blocks are set to different slots.

[0234] In one embodiment of the present disclosure, the second resource includes one or more second slots that are set based on the difference between the first slot included in the first resource and the first slot.

[0235] In one embodiment of the present disclosure, the transmission circuit repeatedly transmits the signal using the second slots.

[0236] In one embodiment of the present disclosure, a size of at least one of a time domain and a frequency domain per slot in the second resource is different from a size of a hop within a slot in the first resource.

[0237] In one embodiment of the present disclosure, the cyclic shift value corresponding to the second resource is a value obtained by adding an offset to the cyclic shift value set for the first resource.

[0238] In one embodiment of the present disclosure, parameter combination candidates including both information about the setting and information about the second resource are associated with information identifying the candidates.

[0239] A base station according to one embodiment of the present disclosure includes a control circuit that sets a second resource, which is different from the first resource, for a second type of terminal based on information regarding the setting of a first resource for the first type of terminal, and a receiving circuit that receives a signal in the second resource.

[0240] In a communication method according to one embodiment of the present disclosure, a terminal configures a second resource, which is different from the first resource, for a second type of terminal based on information regarding the configuration of a first resource for a first type of terminal, and transmits a signal using the second resource.

[0241] In a communication method according to one embodiment of the present disclosure, a base station configures a second resource, which is different from the first resource, for a second type of terminal based on information regarding the configuration of a first resource for a first type of terminal, and receives a signal on the second resource.

[0242] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2021-129188, filed on August 5, 2021, are incorporated herein by reference in their entirety.

[0243] One embodiment of the present disclosure is useful in wireless communication systems.

[0244] REFERENCE SIGNS LIST 100 Base station 101, 206 Control unit 102 DCI generation unit 103 Upper layer signal generation unit 104, 208 Coding and modulation unit 105, 209 Signal mapping unit 106, 210 Transmission unit 107, 201 Antenna 108, 202 Reception unit 109 Signal separation unit 110, 205 Demodulation and decoding unit 200 Terminal 203 Signal separation unit 204 DCI detection unit 207 PUCCH sequence generation unit

Claims

DEPCT671. A terminal comprising a control circuit which, when operated, creates a second resource configuration different from the first resource for a Type 2 terminal based on information about the first resource configuration for a Type 1 terminal, and a transmission circuit which, when operated, transmits signals in the second resource.

2. A terminal under claim 1, where the control circuit creates the second resource configuration based on information about the configuration and information about the difference between the first and second resources.

3. A terminal under claim 2, where the second resource includes one resource block configured differently and a resource block configured first within the bandwidth allocated for a Type 1 terminal.

4. A terminal under claim 2, where the second resource includes a number of resource blocks configured differently and a number of resource blocks of the first resource, each block contained within the first resource, a number of resource blocks called a number of second resource blocks. 5.

6. A terminal under claim 4, where a number of secondary resource blocks are configured in different slots.

7. A terminal under claim 2, where the secondary resource includes a number of slots configured differently and the first slot in the first resource, a number of slots referred to as a number of secondary slots.

8. A terminal under claim 1, where the magnitude of at least one in the time domain and / or frequency domain for each slot in the secondary resource differs from the magnitude of the slot jump in the first resource.

9. A terminal under claim 1, where the value of the cycle shift corresponding to the secondary resource is obtained by adding an offset to the value of the cycle shift configured in the first resource.

10. A terminal under claim 1, where the option for the combination of parameters and specified data is linked, parameters that include both configuration information and information about the secondary resource. 11.A base station comprising a control circuit which, when operating, creates a second resource configuration different from the first resource for the second type of terminal based on information about the first resource configuration for the first type of terminal, and a receiving circuit which, when operating, receives the signal in the second resource.

12. A communication method comprising the creation of a second resource configuration different from the first resource for the second type of terminal with the terminal based on information about the first resource configuration for the first type of terminal and the transmission of signals in the second resource with the terminal.

13. A communication method comprising the creation of a second resource configuration different from the first resource for the second type of terminal with the base station based on information about the first resource configuration for the first type of terminal and the reception of signals in the second resource with the base station.

Images