Terminal, base station, and communication method

Abstract

This terminal is provided with: a reception circuit that receives downlink control information including information scrambled by a terminal-specific identifier and serving to schedule an uplink signal regardless of terminal-specific configurations; and a transmission circuit that repeatedly transmits an uplink signal on the basis of information regarding repeated transmission of an uplink signal, the information being identified on the basis of the downlink control information.

Description

Terminal, base station and communication method

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

[0002] In recent years, the expansion and diversification of wireless services has led to the expectation of rapid development of the Internet of Things (IoT). Mobile communications are now being used in a wide range of applications, from smartphones and other information terminals to automobiles, homes, home appliances, and industrial equipment. To support this diversification, significant improvements in the performance and functionality of mobile communication systems are required, addressing various requirements, such as increased system capacity, an increased number of connected devices, and low latency. Fifth-generation mobile communication systems (5G) boast high-capacity and ultra-high-speed data transfer (eMBB: enhanced Mobile Broadband), massive machine-type communication (mMTC: massive Machine-Type Communication), and ultra-reliable and low-latency communication (URLLC), providing flexible wireless communications to meet diverse needs.

[0003] The 3rd Generation Partnership Project (3GPP), an international standardization organization, is working on the specification of New Radio (NR) as one of the 5G wireless interfaces.

[0004] 3GPP TS38.104 V15.19.0, “NR Base Station (BS) radio transmission and reception (Release 15),” June 2023.RP-202928, “New WID on NR coverage enhancements,” China Telecom, December 2020.RP-220937, “Revised WID on Further NR coverage enhancements,” China Telecom, March 2022.3GPP TS38.211 V17.6.0, “NR Physical channels and modulation (Release 17),” September 2023.3GPP TS38.212 V17.6.0, “NR Multiplexing and channel coding (Release 17),” September 2023.3GPP TS38.213 V17.6.0, “NR Physical layer procedures for control (Release 17),” September 2023.3GPP TS38.214 V17.6.0, “NR Physical layer procedures for data (Release 17),” September 2023.RP-232626, “Moderator's summary for REL-19 RAN1 additional topics,” RAN1 Chair, (Samsung), September 2023.3GPP TS38.331 V17.6.0, “NR Radio Resource Control (RRC) protocol specification Release 17), September 2023.

[0005] However, there is room for further consideration regarding the method of transmitting signals in the uplink.

[0006] Non-limiting examples of the present disclosure contribute to providing a terminal, a base station, and a communication method that can appropriately transmit signals in the uplink.

[0007] A terminal according to one embodiment of the present disclosure includes a receiving circuit that receives downlink control information including information scrambled by a terminal-specific identifier and that schedules an uplink signal regardless of terminal-specific settings, and a transmitting circuit that performs repeated transmission of the uplink signal based on information regarding repeated transmission of the uplink signal that is identified based on the downlink control information.

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

[0009] According to one embodiment of the present disclosure, signals can be transmitted appropriately in the uplink.

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

[0011] 3. Block diagram showing an example configuration of a part of a base station; 4. Block diagram showing an example configuration of a part of a terminal; 5. Flowchart showing an example operation of a terminal; 6. Diagram showing an example of Downlink Control Information (DCI) blindly decoded by a terminal; 7. Flowchart showing an example operation of a terminal; 8. Diagram showing an example of DCI blindly decoded by a terminal; 9. Block diagram showing an example configuration of a base station; 10. Block diagram showing an example configuration of a terminal; 11. Diagram of an example architecture of a 3GPP NR system; 12. Schematic diagram showing functional separation between NG-RAN and 5GC; 13. Sequence diagram of RRC (Radio Resource Control) connection setup / reconfiguration procedures; 14. Schematic diagram showing usage scenarios for enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC); 15. Block diagram showing an example 5G system architecture for a non-roaming scenario;

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

[0013] In NR, for example, in addition to frequency bands below 6 GHz, such as the 700 MHz to 3.5 GHz band (also referred to as Frequency Range 1 (FR1)), which have been used for cellular communications, millimeter wave bands such as the 28 GHz or 39 GHz band (also referred to as Frequency Range 2 (FR2)), which can ensure wide bandwidth, can be utilized (see, for example, Non-Patent Document 1). Furthermore, for example, in FR1, there is a possibility that a frequency band such as the 3.5 GHz band, which is higher than the frequency bands used in Long Term Evolution (LTE) or 3G (3rd Generation mobile communication systems), will be used.

[0014] The higher the frequency band, the greater the radio wave propagation loss and the more likely it is that radio wave reception quality will deteriorate. Therefore, when NR uses a frequency band higher than that of LTE or 3G, it is expected to ensure a communication area (or coverage) equivalent to that of radio access technologies (RATs) such as LTE or 3G, in other words, to ensure appropriate communication quality. For example, 3GPP Release 17 (e.g., referred to as "Rel. 17") and Release 18 (e.g., referred to as "Rel. 18") have considered methods for improving coverage in NR (see, for example, Non-Patent Document 2 and Non-Patent Document 3).

[0015] In NR, a terminal (e.g., also referred to as user equipment (UE)) transmits and receives data in accordance with, for example, a layer 1 control signal (e.g., DCI: Downlink Control Information) on a downlink control channel (e.g., PDCCH: Physical Downlink Control Channel) from a base station (e.g., also referred to as gNB) or a resource allocation indicated by layer 3 Radio Resource Control (RRC) (see, for example, Non-Patent Documents 4 to 7).

[0016] In NR, repetition transmission (repetition) can be applied as one of the uplink (UL) coverage extension techniques (see, for example, Non-Patent Documents 6 or 7). In NR up to Release 18, channels to which repetition can be applied are uplink data channels (e.g., PUSCH: Physical Uplink Shared Channel) scheduled by DCI format 0-1 or DCI format 0-2 (e.g., PUSCH scheduled after parameters are configured by a pusch-Config information element (IE), which is a terminal-specific RRC), Msg. 3 PUSCH (e.g., PUSCH scheduled by a Random Access Response (RAR)), uplink control channels (e.g., PUCCH: Physical Uplink Control Channel), and random access channels (e.g., PRACH: Physical Random Access Channel).

[0017] In NR, repetition is not supported for PUSCH scheduled by DCI format 0-0, which is one of the DCI formats to which a Cyclic Redundancy Check (CRC) parity bit scrambled by a Cell-Radio Network Temporary Identifier (C-RNTI) (e.g., an example of an identifier unique to a UE) is added.

[0018] For example, the terminal transmits Msg. 3 PUSCH, and until the terminal-specific PUSCH configuration (e.g., Dedicated PUSCH configuration) is completed, the PUSCH can be scheduled using DCI format 0-0 to which a CRC scrambled by the C-RNTI is added.

[0019] Here, the PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is added until the terminal transmits Msg.3 PUSCH and terminal-specific PUSCH configuration is completed is sometimes called "Msg.5 PUSCH."

[0020] For example, Msg.5 PUSCH may be a PUSCH including a message (e.g., RRCSetupComplete) that a terminal that has received a message (e.g., RRC Setup) including settings for the terminal notifies the base station that application of the settings included in the RRC Setup has been completed.

[0021] For example, the payload size of a PUSCH including RRCSetupComplete may be larger than the payload size of a PUSCH Msg. 3. In this case, a PUSCH to which no repetition is applied, such as a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added, may become a coverage bottleneck during initial access.

[0022] Therefore, application of repetition to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached has been studied (see, for example, Non-Patent Document 8). However, there is room for further study on a control method for a terminal to transmit a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached (for example, repetition transmission).

[0023] For example, as described above, a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached can be used to transmit an Msg.5 PUSCH (e.g., a PUSCH including RRCSetupComplete). Therefore, control taking into consideration the transmission of an Msg.5 PUSCH (e.g., a PUSCH including RRCSetupComplete) is expected. For example, when transmitting an Mg.5 PUSCH, there are cases where a terminal-specific RRC configuration (e.g., a Dedicated RRC configuration) is available and cases where a terminal-specific RRC configuration is not available. Therefore, even when a terminal-specific RRC configuration is not available, it is expected that the terminal will receive DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached and be able to transmit a PUSCH.

[0024] In NR, when a Type3-PDCCH Common Search Space (CSS) Set (e.g., SearchSpaceType = common in a terminal-specific PDCCH-Config) and a UE-specific Search Space (USS) Set are not provided to a terminal, that is, when a terminal-specific PDCCH reception configuration is not available in the terminal, the terminal monitors (or blindly decodes) PDCCH candidates for DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached within the Type1-PDCCH CSS Set. Therefore, it is expected that the terminal monitors PDCCH candidates within the Type1-PDCCH CSS Set and applies repetition to PUSCHs scheduled by decoded DCI (e.g., DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached).

[0025] Furthermore, DCI format 0-0 to which a CRC scrambled by a C-RNTI is attached does not have a function for reporting information related to PUSCH repetition (for example, the number of repetitions, etc.). Therefore, there is room for consideration regarding a method for reporting information related to repetition for a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by a C-RNTI is attached.

[0026] In one non-limiting embodiment of the present disclosure, a method is described in which the repetition function is efficiently applied to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by a C-RNTI is added, taking into consideration the transmission of a Msg.5 PUSCH (e.g., a PUSCH including RRCSetupComplete).

[0027] Non-limiting embodiments of the present disclosure will be described below.

[0028] [Overview of Communication System] A communication system according to each embodiment of the present disclosure includes, for example, at least one base station and at least one terminal.

[0029] FIG. 1 is a block diagram showing a partial configuration example of a base station 100 according to an embodiment of the present disclosure, and FIG. 2 is a block diagram showing a partial configuration example of a terminal 200 according to an embodiment of the present disclosure.

[0030] In the base station 100 shown in Fig. 1, a transmitter (e.g., corresponding to a transmitter circuit) transmits downlink control information (e.g., DCI format 0-0) that includes information (e.g., CRC) scrambled by a terminal-specific identifier (e.g., C-RNTI) and schedules an uplink signal regardless of a terminal-specific setting (e.g., Dedicated RRC configuration). A receiver (e.g., corresponding to a receiver circuit) receives repeated transmission of the uplink signal based on information related to repeated transmission of the uplink signal (e.g., information related to Repetition) that is specified based on the downlink control information.

[0031] In the terminal 200 shown in Fig. 2, a receiving unit (e.g., corresponding to a receiving circuit) receives downlink control information (e.g., DCI format 0-0) that includes information (e.g., CRC) scrambled by a terminal-specific identifier (e.g., C-RNTI) and schedules an uplink signal regardless of a terminal-specific setting (e.g., Dedicated RRC configuration). A transmitting unit (e.g., corresponding to a transmitting circuit) repeatedly transmits the uplink signal based on information related to repeated transmission of the uplink signal (e.g., information related to Repetition) that is specified based on the downlink control information.

[0032] (Embodiment 1) In the present embodiment, it is assumed that Repetition is applied to transmission of a PUSCH such as a PUSCH including Msg.5 PUSCH and RRCSetupComplete, or a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added when terminal 200 transmits Msg.3 PUSCH and until terminal-specific PUSCH configuration (for example, Dedicated PUSCH configuration) is completed.

[0033] In this embodiment, the above PUSCHs are collectively referred to as "Msg.5 PUSCH."

[0034] For example, terminal 200 that has requested Msg.5 PUSCH repetition, terminal 200 that has notified the base station that it has the capability of Msg.5 PUSCH repetition, or terminal 200 that has the capability of Msg5 PUSCH repetition is notified of information related to PUSCH repetition (e.g., the number of repetitions) by some information fields of DCI format 0-0 to which a CRC scrambled by C-RNTI is added (e.g., by reusing some information fields).

[0035] For example, the following information fields of DCI format 0-0 to which a CRC scrambled by the C-RNTI is added may be reused to report information related to PUSCH repetition.

[0036] [Option 1: Modulation and Coding Scheme (MCS) field] For example, information on PUSCH repetition may be signaled using X most significant bits (MSBs) of the 5 bits of the MCS field. Also, an MCS index may be signaled using 5-X least significant bits (LSBs) of the 5 bits of the MCS field.

[0037] In this case, the information about PUSCH repetition that can be notified by the MCS field and the candidate values ​​of the MCS index are 2 X pcs and 2 5-X These values ​​may be predefined in the standard, or may be set in terminal 200 by a system information block (SIB) or RRC.

[0038] Also, for example, up to two columns containing information on the MCS index and PUSCH repetition are used. 5 A table of rows may be defined or configured by the SIB or RRC. For example, information about the MCS index and the PUSCH repetition may be signaled by signaling an identifier (e.g., an index) corresponding to each row of the table.

[0039] [Option 2: Time Domain Resource Allocation (TDRA) field] For example, information about PUSCH repetition (e.g., the number of repetitions) may be signaled using X most significant bits of the 4 bits of the TDRA field. Also, a TDRA index may be signaled using 4-X least significant bits of the 4 bits of the TDRA field.

[0040] At this time, there are two candidates for the information about PUSCH repetition that can be notified by the TDRA field and the value of the TDRA index. X pcs and 2 4-X These values ​​may be predefined in the standard, or may be configured in terminal 200 by SIB or RRC.

[0041] Also, for example, a maximum of two columns containing parameters related to TDRA (for example, slot index, number of symbols, etc.) and information related to PUSCH repetition in each column can be used. 4 A table of rows may be defined or configured by the SIB or RRC. For example, parameters related to TDRA and information related to PUSCH repetition may be notified by notifying an index corresponding to each row of the table.

[0042] [Option 3: Transmit Power Control (TPC) field] Of the two bits of the TPC field (also referred to as, for example, the TPC command for scheduled PUSCH field), information on PUSCH repetition (for example, the number of repetitions) may be reported using X most significant bits. Also, of the two bits of the TPC field, the TPC command may be reported using 2-X least significant bits.

[0043] At this time, the information about PUSCH repetition that can be notified by the TPC field and the candidate values ​​of the TPC command are each 2 X Pieces and 2 2-X These values ​​may be predefined in the standard, or may be configured in terminal 200 by SIB or RRC.

[0044] Also, for example, up to two columns containing information on TPC commands and PUSCH repetitions can be used. 2A table of rows may be defined or configured by the SIB or RRC. For example, information on the TPC command and the PUSCH repetition may be notified by notifying an index corresponding to each row of the table.

[0045] [Option 4: Frequency Domain Resource Allocation (FDRA) field] Information about PUSCH repetition (for example, the number of repetitions) may be signaled using X most significant bits of the Y bits of the FDRA field. Furthermore, frequency domain resources may be signaled using YX least significant bits of the Y bits of the FDRA field.

[0046] In this case, there are two candidates for information about PUSCH repetition that can be notified by the FDRA field. X These may be predefined in the standard or may be configured in terminal 200 by SIB or RRC.

[0047] The number of bits Y in the FDRA field is, for example, Here, may be the number of resource blocks (RB) of the initial BandWidth Part (BWP) (initial UL BWP) or the number of resource blocks of the Active BWP.

[0048] [Option 5: Redundancy Version (RV) field] Of the two bits in the RV field, information about PUSCH repetition (for example, the number of repetitions) may be reported using X most significant bits. Also, of the two bits in the RV field, 2-X least significant bits may be used to report an RV index.

[0049] At this time, the information about PUSCH repetition that can be notified by the RV field and the candidate values ​​of the RV index are respectively 2 X pcs and 2 2-XThese values ​​may be predefined in the standard, or may be configured in terminal 200 by SIB or RRC.

[0050] Also, for example, up to two columns containing information on the RV index and PUSCH repetition 2 A table of rows may be defined or configured by the SIB or RRC. For example, information on the RV index and PUSCH repetition may be notified by notifying an index corresponding to each row of the table.

[0051] [Option 6: Hybrid Automatic Repeat Request (HARQ) Process Number Field] Of the four bits in the HARQ process number field, information about PUSCH repetition (for example, the number of repetitions) may be reported using X most significant bits. Also, of the four bits in the HARQ process number field, 4-X least significant bits may be used to report the HARQ process number.

[0052] In this case, the information about PUSCH repetition that can be notified by the HARQ process number field and the candidate values ​​of the HARQ process number are respectively 2 X pcs and 2 4-X These values ​​may be predefined in the standard, or may be configured in terminal 200 by SIB or RRC.

[0053] Also, for example, up to two columns containing information on the HARQ process number and PUSCH repetition are used. 4 A table of rows may be defined or configured by the SIB or RRC. For example, information on the HARQ process number and PUSCH repetition may be signaled by signaling an index corresponding to each row of the table.

[0054] An example has been described above in which information related to PUSCH repetition is notified by reusing some information fields of DCI format 0-0 to which CRC scrambled by C-RNTI is added.

[0055] According to the present embodiment, when terminal 200 that has requested Mg.5 PUSCH repetition, terminal 200 that has notified base station 100 that it has Mg.5 PUSCH repetition capability, or terminal 200 that has Mg5 PUSCH repetition capability receives DCI format 0-0 to which a CRC scrambled by C-RNTI is attached, terminal 200 can obtain information related to PUSCH repetition by reinterpreting a specific information field as notification of information related to PUSCH repetition. Thus, according to the present embodiment, terminal 200 can perform repetition transmission of a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached.

[0056] Note that the PUSCH to which this embodiment can be applied is not limited to the above-described PUSCH including Mg.5 PUSCH and RRCSetupComplete, or a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached when terminal 200 transmits Mg.3 PUSCH and before terminal-specific PUSCH configuration is completed. For example, this embodiment can also be applied to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached after terminal-specific PUSCH configuration is completed.

[0057] Furthermore, in the above-described Options 1 to 6, information related to PUSCH repetition is not limited to being allocated to the MSB or LSB of a specific field, but may be allocated to another area of ​​X bits. Furthermore, X bits may be any number of bits from 1 bit to all bits in the information field to which information related to PUSCH repetition is allocated.

[0058] Furthermore, information related to PUSCH repetition may be allocated across multiple information fields. For example, information related to PUSCH repetition may be allocated to some or all of each of multiple information fields.

[0059] [Example of Operation of Terminal 200] FIG. 3 is a flowchart showing an example of operation of terminal 200.

[0060] 3, terminal 200 acquires information related to the repetition of a PUSCH (e.g., Msg. 5 PUSCH) scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is added (S101). The information related to PUSCH repetition acquired by terminal 200 in S101 may include, for example, multiple candidates for information related to repetition (e.g., the number of repetitions) notified by DCI format 0-0, information related to an information field reused for information related to repetition in DCI format 0-0, or information such as the number of bits X allocated to information related to repetition in that information field. Note that (some or all of) the above information may be determined in advance by a standard.

[0061] The terminal 200 receives DCI format 0-0 (S102).

[0062] Terminal 200 determines whether or not repetition of PUSCH scheduled by DCI format 0-0 is requested (S103).

[0063] If PUSCH repetition is requested (S103: Yes), terminal 200 reads some information fields (e.g., some bits) of the received DCI format 0-0 and acquires information related to PUSCH repetition (e.g., the number of repetitions) (S104). Then, terminal 200 transmits PUSCH repetition (e.g., the PUSCH to be repeated) (S105).

[0064] On the other hand, if PUSCH repetition is not requested (S103: No), terminal 200 reads the information field of the received DCI format 0-0 as it is and acquires information related to PUSCH transmission (S106). Then, terminal 200 transmits PUSCH (S107).

[0065] As described above, in the present embodiment, terminal 200 receives DCI format 0-0 that includes a CRC scrambled by the C-RNTI and schedules a PUSCH without relying on a terminal-specific RRC configuration (for example, a dedicated RRC configuration), and performs PUSCH repetition based on information on PUSCH repetition identified based on the received DCI format 0-0. Furthermore, base station 100 transmits DCI format 0-0 that includes a CRC scrambled by the C-RNTI and schedules a PUSCH without relying on a terminal-specific RRC configuration, and receives PUSCH repetition based on information on PUSCH repetition identified based on the transmitted DCI format 0-0.

[0066] In this embodiment, information about repetition is allocated to at least a part of the information field included in DCI format 0-0 that notifies information different from information about repetition.

[0067] This enables terminal 200 to control repetition transmission for a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached. Also, for a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached, it becomes possible to notify terminal 200 of information related to repetition by this DCI format 0-0.

[0068] Therefore, according to the mobile station of this embodiment, it is possible to efficiently apply the repetition function to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added, taking into consideration the transmission of a Msg.5 PUSCH (for example, a PUSCH including RRCSetupComplete). As a result, terminal 200 can appropriately transmit signals in the uplink.

[0069] (Embodiment 2) In the present embodiment, it is assumed that Repetition is applied to transmission of a PUSCH such as a PUSCH including Msg.5 PUSCH and RRCSetupComplete, or a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added when terminal 200 transmits Msg.3 PUSCH and until terminal-specific PUSCH configuration (for example, Dedicated PUSCH configuration) is completed.

[0070] In this embodiment, the above PUSCHs are collectively referred to as "Msg.5 PUSCH."

[0071] In the first embodiment, some of the existing information fields of DCI format 0-0 are used (reused) for reporting information related to PUSCH repetition. This may reduce the flexibility of scheduling for existing parameters reported by information fields used for reporting information related to PUSCH repetition.

[0072] Here, it is assumed that the function (extended function) of applying Repetition to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added is applied to a PUSCH including Msg.5 PUSCH, RRCSetupComplete, or a PUSCH scheduled after terminal 200 transmits Msg.3 PUSCH and before terminal-specific PUSCH configuration is completed.

[0073] In this case, terminal 200 monitors PDCCH candidates for DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached within the Type1-PDCCH CSS Set, and applies Repetition to the PUSCH scheduled by the decoded DCI (for example, DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached). At this time, it is assumed that terminal 200 cannot use a terminal-specific PDCCH reception configuration. Therefore, for example, it is assumed that terminal 200 does not monitor in a terminal-specific USS, and therefore the number of blind decoding attempts by terminal 200 has some leeway.

[0074] Therefore, in the present embodiment, terminal 200 monitors PDCCH candidates for a DCI format specific to PUSCH repetition scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added.

[0075] For example, terminal 200 monitors PDCCH candidates for DCI format 0-0 with a payload size different from the payload size of existing DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached. Also, for example, base station 100 generates DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached, including information related to Msg.5 PUSCH repetition, using a payload size different from the payload size of existing DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached, and transmits the DCI format 0-0 to terminal 200.

[0076] Terminal 200 monitors, for example, PDCCH candidates for DCI format 0-0 to which a CRC scrambled by C-RNTI is added within the Type1-PDCCH CSS Set. At this time, terminal 200 blindly decodes DCI format 0-0 having a payload size different from that of existing DCI format 0-0 (and DCI format 1-0), in addition to existing DCI format 0-0 (e.g., DCI that does not include a repetition-related information field) and DCI format 1-0. That is, terminal 200 performs blind decoding of DCI format 0-0 for multiple payload sizes. Note that terminal 200 that performs blind decoding of DCI format 0-0 for multiple payload sizes may be, for example, terminal 200 that has requested Msg.5 PUSCH repetition, terminal 200 that has notified base station 100 that it has Msg.5 PUSCH repetition capability, or terminal 200 that has Msg5 PUSCH repetition capability.

[0077] Here, DCI format 0-0 having a payload size different from that of existing DCI format 0-0 to which a CRC scrambled by the C-RNTI is added may be, for example, a DCI format in which an information field for reporting information related to PUSCH repetition is added to existing DCI format 0-0. The information field for reporting information related to PUSCH repetition may be, for example, an information field for reporting the number of repetitions and at least one other information field (for example, a notification related to a frequency hopping method or a notification related to whether flexible symbols are used). Furthermore, the information field added to existing DCI format 0-0 is not limited to an information field for reporting information related to PUSCH repetition, and may be an information field used for purposes other than PUSCH repetition. Furthermore, in addition to the added information field, reserved bits may be added to existing DCI format 0-0 in consideration of future extensions to standards.

[0078] If the payload size of the successfully decoded DCI (for example, DCI format 0-0 to which a CRC scrambled by the C-RNTI is added) is the payload size of the existing DCI format 0-0 (and DCI format 1-0), terminal 200 determines that repetition is not applied to the scheduled PUSCH and transmits the PUSCH.

[0079] On the other hand, if the payload size of successfully decoded DCI (for example, DCI format 0-0 to which a CRC scrambled by the C-RNTI is added) differs from the payload size of the existing DCI format 0-0 (and DCI format 1-0), terminal 200 determines that repetition is applied to the scheduled PUSCH and transmits the PUSCH with repetition.

[0080] Furthermore, in the present embodiment, for example, as shown in FIG. 4 , the timing (or period) for performing blind decoding of multiple payload sizes (e.g., existing DCI and new DCI) for PDCCH candidates for DCI format 0-0 to which a CRC scrambled by C-RNTI is added within the Type1-PDCCH CSS Set may be the timing (or period) until a Type3-PDCCH CSS Set (e.g., SearchSpaceType = common in a terminal-specific PDCCH-Config) or a USS Set is provided to terminal 200. As shown in FIG. 4 , after a Type3-PDCCH CSS Set or a USS Set is provided to terminal 200, blind decoding of multiple payload sizes within the Type1-PDCCH CSS Set does not need to be performed. For example, as shown in FIG. 4 , after a Type3-PDCCH CSS Set or a USS Set is provided to terminal 200, blind decoding of existing DCI may be performed within the Type1-PDCCH CSS Set. This prevents an increase in the number of times (for example, up to four times) that different DCI payload sizes are blindly decoded, thereby reducing the impact on DCI decoding after USS acquisition.

[0081] Note that the blind decoding operation in terminal 200 is not limited to the example shown in FIG. 4 . For example, after a Type 3-PDCCH CSS Set or a USS Set is provided to terminal 200, terminal 200 may perform blind decoding of multiple payload sizes (e.g., existing DCI and new DCI).

[0082] [Example of Operation of Terminal 200] FIG. 5 is a flowchart showing an example of operation of terminal 200.

[0083] 5 , terminal 200 acquires information on the repetition of a PUSCH (for example, Msg. 5 PUSCH) scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is added (S201). The information on PUSCH repetition acquired by terminal 200 in S201 may include, for example, information on the payload size of DCI format 0-0 (or the size of the information field for PUSCH repetition in DCI format 0-0).

[0084] Terminal 200 determines whether or not repetition of PUSCH scheduled by DCI format 0-0 is requested (S202).

[0085] If PUSCH repetition is requested (S202: Yes), terminal 200 blindly decodes (monitors) DCI format 0-0 for multiple DCI payload sizes (e.g., existing DCI size and DCI size different from the existing DCI size) for PDCCH candidates for DCI format 0-0 to which a CRC scrambled by a C-RNTI is added, for example, in a Type-1 PDCCH CSS Set (S203). Then, for example, if blind decoding of DCI format 0-0 with a DCI size different from the existing DCI size is successful, terminal 200 acquires information on PUSCH repetition (e.g., the number of repetitions) from DCI format 0-0 (S204). Then, terminal 200 transmits PUSCH repetitions (e.g., the PUSCH to be repeated) (S205).

[0086] On the other hand, if PUSCH repetition is not requested (S202: No), terminal 200 blindly decodes (monitors) DCI format 0-0 of an existing DCI size for PDCCH candidates for DCI format 0-0 to which a CRC scrambled by C-RNTI is added, for example, in the Type-1 PDCCH CSS Set (S206). Then, for example, if blind decoding of DCI format 0-0 of the existing DCI size is successful, terminal 200 acquires information related to PUSCH transmission from DCI format 0-0 (S207). Then, terminal 200 transmits a PUSCH (S208).

[0087] As described above, in the present embodiment, terminal 200 receives DCI format 0-0 that includes a CRC scrambled by the C-RNTI and schedules a PUSCH without relying on a terminal-specific RRC configuration (for example, a Dedicated RRC configuration), and performs PUSCH repetition based on information related to PUSCH repetition identified based on the received DCI format 0-0.

[0088] In this embodiment, DCI format 0-0 with a payload size different from that of existing DCI format 0-0, i.e., DCI format 0-0 with multiple payloads, is used. For example, DCI format 0-0 with a payload size different from that of existing DCI format 0-0 includes an information field that reports information about PUSCH repetition. As a result, according to this embodiment, it is possible to report information about PUSCH repetition (for example, the number of repetitions) without changing the existing information field. Therefore, it is possible to schedule PUSCH repetition without degrading the flexibility of scheduling for parameters different from PUSCH repetition.

[0089] Furthermore, when terminal 200 does not have a terminal-specific PDCCH reception configuration available, which allows a relatively large number of blind decoding attempts, terminal 200 performs blind decoding of multiple payload sizes for PDCCH candidates for DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached. For example, terminal 200 performs blind decoding of DCI format 0-0 for multiple payload sizes until a terminal-specific search space (e.g., Type 3-PDCCH CSS Set or USS Set) is assigned. On the other hand, when terminal-specific PDCCH reception configuration is available, terminal 200 performs blind decoding of an existing DCI size for PDCCH candidates for DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached, and does not perform blind decoding of DCI format 0-0 of a size different from the existing DCI size. This can reduce the impact on the blind decoding capability of terminal 200.

[0090] (Embodiment 3) This embodiment assumes the application of Repetition to PUSCHs such as a PUSCH including Msg.5 PUSCH and RRCSetupComplete, or a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added when terminal 200 transmits Msg.3 PUSCH and until terminal-specific PUSCH configuration (for example, Dedicated PUSCH configuration) is completed.

[0091] In this embodiment, the above PUSCHs are collectively referred to as "Msg.5 PUSCH."

[0092] In the present embodiment, terminal 200 monitors PDCCH candidates for multiple DCI formats 0-0 to which CRCs each scrambled by different C-RNTIs are attached. For example, terminal 200 monitors PDCCH candidates corresponding to multiple RNTIs, such as C-RNTIs for PUSCH scheduling that does not employ PUSCH repetition and C-RNTIs for PUSCH scheduling that employs PUSCH repetition, for DCI format 0-0 to which CRCs scrambled by C-RNTIs are attached.

[0093] For example, terminal 200 monitors PDCCH candidates for DCI format 0-0 to which a CRC scrambled by a C-RNTI is attached within a Type1-PDCCH CSS Set. At this time, terminal 200 blindly decodes multiple DCI formats 0-0 to which CRCs scrambled by different C-RNTIs are attached. That is, terminal 200 blindly decodes DCI format 0-0 for multiple C-RNTIs. Note that terminal 200 that blindly decodes DCI format 0-0 for multiple C-RNTIs may be, for example, terminal 200 that has requested Msg.5 PUSCH repetition, terminal 200 that has notified base station 100 that it has Msg.5 PUSCH repetition capability, or terminal 200 that has Msg.5 PUSCH repetition capability.

[0094] Here, the multiple different C-RNTIs may be C-RNTIs given as "n" and "n+1" when the C-RNTI set in terminal 200 is "n", or C-RNTI n may be a C-RNTI for PUSCH scheduling that does not apply PUSCH repetition, and C-RNTI n+1 may be a C-RNTI for PUSCH scheduling that applies PUSCH repetition.

[0095] Furthermore, the C-RNTI for PUSCH scheduling to which PUSCH repetition is applied is not limited to n+1, and may be a value calculated from C-RNTI n by other methods. Furthermore, the C-RNTI for PUSCH scheduling to which PUSCH repetition is applied may be predefined in the standard, or may be a value calculated from parameters set in terminal 200 by SIB or RRC.

[0096] If the successfully decoded DCI (e.g., DCI format 0-0 to which a CRC scrambled by a C-RNTI is added) is scrambled by a C-RNTI for PUSCH scheduling that does not apply PUSCH repetition (e.g., in the case of DCI format 0-0 that does not notify information related to PUSCH repetition), terminal 200 determines that repetition is not applied to the scheduled PUSCH and transmits the PUSCH.

[0097] On the other hand, if successfully decoded DCI (e.g., DCI format 0-0 to which a CRC scrambled by the C-RNTI is added) is scrambled by the C-RNTI for PUSCH scheduling that applies PUSCH repetition (e.g., in the case of DCI format 0-0 that reports information related to PUSCH repetition), terminal 200 determines that repetition is applied to the scheduled PUSCH and applies repetition to the PUSCH before transmitting. At this time, information related to PUSCH repetition (e.g., the number of repetitions) may be reported to terminal 200 by reusing some information fields of DCI format 0-0 based on, for example, any of Options 1 to 6 described in embodiment 1.

[0098] Furthermore, in the present embodiment, for example, as shown in Fig. 6 , the timing (or period) for performing blind decoding of multiple C-RNTIs for PDCCH candidates for DCI format 0-0 to which a CRC scrambled by the C-RNTI is added within a Type1-PDCCH CSS Set may be the timing (or period) when a Type3-PDCCH CSS Set (for example, SearchSpaceType = common in a terminal-specific PDCCH-Config) or a USS Set is provided to terminal 200. As shown in Fig. 6 , after a Type3-PDCCH CSS Set or a USS Set is provided to terminal 200, blind decoding of multiple C-RNTIs within the Type1-PDCCH CSS Set does not need to be performed. For example, as shown in Fig. 6 , after a Type3-PDCCH CSS Set or a USS Set is provided to terminal 200, blind decoding of existing C-RNTIs may be performed within the Type1-PDCCH CSS Set. This makes it possible to suppress an increase in the number of times (for example, up to four times) that blind decoding is performed for different C-RNTIs, and to suppress the impact on DCI decoding after USS acquisition.

[0099] Note that the blind decoding operation in terminal 200 is not limited to the example shown in FIG. 6 . For example, after a Type 3-PDCCH CSS Set or a USS Set is provided to terminal 200, terminal 200 may perform blind decoding of multiple C-RNTIs (e.g., existing DCI and new DCI).

[0100] As described above, in the present embodiment, terminal 200 receives DCI format 0-0 that includes a CRC scrambled by the C-RNTI and schedules a PUSCH without relying on a terminal-specific RRC configuration (for example, a Dedicated RRC configuration), and performs PUSCH repetition based on information related to PUSCH repetition identified based on the received DCI format 0-0.

[0101] In this embodiment, DCI format 0-0 of a plurality of payloads is used as the C-RNTI used for scrambling the CRC included in DCI format 0-0. For example, in DCI format 0-0 using a C-RNTI different from the C-RNTI of existing DCI format 0-0, information on PUSCH repetition is indicated in a part of the information field for indicating other parameters, as in embodiment 1. As a result, according to this embodiment, whether or not a part of the information field of the DCI format is reused for information on PUSCH repetition (for example, the number of repetitions) can be varied depending on whether or not PUSCH repetition is applied. For example, when PUSCH repetition is not applied, there is no need to change the existing information field, and therefore it is possible to maintain flexibility in scheduling when PUSCH repetition is not applied.

[0102] Furthermore, when a terminal-specific PDCCH reception configuration that allows a relatively large number of blind decoding attempts is not available in terminal 200, terminal 200 performs blind decoding of multiple C-RNTIs for PDCCH candidates for DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached. For example, terminal 200 performs blind decoding of DCI format 0-0 for multiple C-RNTIs until a terminal-specific search space (e.g., Type 3-PDCCH CSS Set or USS Set) is assigned. On the other hand, when a terminal-specific PDCCH reception configuration is available, terminal 200 performs blind decoding of existing C-RNTIs for PDCCH candidates for DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached, and does not perform blind decoding of C-RNTIs different from the existing C-RNTI. This can reduce the impact on the blind decoding capability of terminal 200.

[0103] Note that the PUSCH to which this embodiment can be applied is not limited to the above-described PUSCH including Mg.5 PUSCH and RRCSetupComplete, or a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached when terminal 200 transmits Mg.3 PUSCH and before terminal-specific PUSCH configuration is completed. For example, this embodiment can also be applied to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached after terminal-specific PUSCH configuration is completed.

[0104] Furthermore, in the present embodiment, when PUSCH repetition is applied, a case has been described in which part of the information field of existing DCI format 0-0 is replaced with (reused as) information related to PUSCH repetition, as in embodiment 1. However, the method of reporting information related to PUSCH repetition is not limited to this. For example, when successfully decoded DCI format 0-0 is scrambled by C-RNTI for PUSCH scheduling that applies PUSCH repetition, terminal 200 may determine that PUSCH repetition is applied and perform PUSCH repetition. That is, whether or not PUSCH repetition is applied may be implicitly reported to terminal 200. In this case, information related to PUSCH repetition (for example, the number of repetitions) may be specified in advance in a standard, or may be configured in terminal 200 by SIB or RRC.

[0105] Furthermore, in this embodiment, the number of C-RNTIs (C-RNTIs different from existing C-RNTIs) used when PUSCH repetition is applied is not limited to one, and multiple C-RNTIs may be set. For example, the operation of PUSCH repetition (for example, the number of repetitions) may differ depending on each of the multiple C-RNTIs.

[0106] (Variation of Embodiment 3) In Embodiment 3, a method has been described in which the C-RNTI for PUSCH scheduling that does not apply PUSCH repetition is made different from the C-RNTI for PUSCH scheduling that applies PUSCH repetition, thereby distinguishing whether or not information related to PUSCH repetition is included in DCI format 0-0 to which a CRC scrambled by C-RNTI is added, but the present invention is not limited to this.

[0107] For example, by using a different CRC mask instead of the C-RNTI, it is possible to apply a method of distinguishing whether or not information related to PUSCH repetition is included in DCI format 0-0 to which a CRC scrambled by the C-RNTI is added, thereby achieving the same effect as in embodiment 3.

[0108] For example, a CRC mask may not be applied to DCI format 0-0 for PUSCH scheduling that does not apply PUSCH repetition (or a CRC mask [0, 0, 0, 0, ..., 0] may be applied), and a CRC mask may be applied to DCI format 0-0 for PUSCH scheduling that applies PUSCH repetition. As an example, applying a CRC mask [0, 0, 0, 0, ..., 1] to DCI format 0-0 for PUSCH scheduling that applies PUSCH repetition has the same effect as using C-RNTIs n and n+1.

[0109] (Embodiment 4) In the present embodiment, it is assumed that Repetition is applied to PUSCHs such as a PUSCH including Msg.5 PUSCH and RRCSetupComplete, or a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added after terminal 200 transmits Msg.3 PUSCH and before terminal-specific PUSCH configuration (for example, Dedicated PUSCH configuration) is completed.

[0110] In this embodiment, the above PUSCHs are collectively referred to as "Msg.5 PUSCH."

[0111] Furthermore, the PUSCH to which the present embodiment can be applied is not limited to the above-described PUSCH including Mg.5 PUSCH and RRCSetupComplete, or a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached when terminal 200 transmits Mg.3 PUSCH and before terminal-specific PUSCH configuration is completed. For example, it is assumed that the present embodiment is also applied to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached after terminal-specific PUSCH configuration is completed.

[0112] In this embodiment, the function (or mechanism) for PUSCH repetition is set (or maintained) to be the same for the repetition of Msg.5 PUSCH (for example, a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached before the terminal-specific PUSCH configuration is completed) and a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached after the terminal-specific PUSCH configuration is completed.

[0113] For example, when a method according to embodiment 1 (e.g., any of the methods of Option 1 to 6) or a method according to embodiment 3 is applied to a repetition of Msg.5 PUSCH (e.g., a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached before terminal-specific PUSCH configuration is completed), a method similar to the method applied to the repetition of Msg.5 PUSCH is also applied to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached after terminal-specific PUSCH configuration is completed.

[0114] According to the present embodiment, base station 100 can apply Repetition to and schedule a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by a C-RNTI is attached, without identifying an RRC processing delay (for example, RRC decoding time) of terminal 200, and without distinguishing between a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by a C-RNTI is attached before terminal-specific PUSCH configuration is complete and a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by a C-RNTI is attached after terminal-specific PUSCH configuration is complete.

[0115] (Embodiment 5) In the present embodiment, it is assumed that Repetition is applied to PUSCHs such as Msg.5 PUSCH, PUSCH including RRCSetupComplete, or PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added when terminal 200 transmits Msg.3 PUSCH and until terminal-specific PUSCH configuration (for example, Dedicated PUSCH configuration) is completed.

[0116] In this embodiment, the above PUSCHs are collectively referred to as "Msg.5 PUSCH."

[0117] Furthermore, the PUSCH to which the present embodiment can be applied is not limited to the above-described PUSCH including Mg.5 PUSCH and RRCSetupComplete, or a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached when terminal 200 transmits Mg.3 PUSCH and before terminal-specific PUSCH configuration is completed. For example, it is assumed that the present embodiment is also applied to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached after terminal-specific PUSCH configuration is completed.

[0118] In this embodiment, the function (or mechanism) for PUSCH repetition in Msg. 5 is differentiated between a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is added before terminal-specific PUSCH configuration is completed, and a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is added after terminal-specific PUSCH configuration is completed.

[0119] For example, any of the combinations (Options A to H) shown in FIG. 7 may be selected for the function applied to the repetition of Msg. 5 PUSCH (e.g., a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached before the terminal-specific PUSCH configuration is completed) and the function applied to the PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached after the terminal-specific PUSCH configuration is completed.

[0120] <Option A> In Option A, for example, the method of embodiment 1 (for example, any of the methods of Option 1 to Option 6) or the method of embodiment 3 is applied to Msg.5 PUSCH Repetition (for example, a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added until terminal-specific PUSCH configuration is completed).

[0121] Furthermore, a method similar to that applied to the repetition of Mg.5 PUSCH is applied to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached after terminal-specific PUSCH configuration is completed. However, in this case, an RRC configuration different from the RRC configuration for Mg.5 PUSCH may be followed. For example, when the method of embodiment 1 is applied, different candidates for information related to PUSCH repetition that can be notified (e.g., the number of repetitions) and other parameters may be configured by RRC for Mg.5 PUSCH repetition and for PUSCH repetition scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is attached after terminal-specific PUSCH configuration is completed.

[0122] <Option B> In Option B, for example, the method of embodiment 1 (for example, any of the methods of Option 1 to Option 6) is applied to Msg.5 PUSCH Repetition (for example, a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added until terminal-specific PUSCH configuration is completed).

[0123] Furthermore, the method of Embodiment 1 (for example, any of the methods of Option 1 to Option 6) is applied to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added after terminal-specific PUSCH configuration is completed. However, an Option different from the Option applied during Msg.5 PUSCH repetition is applied to this PUSCH.

[0124] <Option C> In Option C, the method of embodiment 1 (e.g., any of the methods of Option 1 to 6) or the method of embodiment 2 is applied to the repetition of Msg.5 PUSCH (e.g., PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added until the terminal-specific PUSCH configuration is completed).

[0125] Furthermore, the method of embodiment 3 is applied to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is added after terminal-specific PUSCH configuration is completed.

[0126] <Option D> In Option D, the method of embodiment 2 or 3 is applied to the repetition of Msg.5 PUSCH (for example, a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added until terminal-specific PUSCH configuration is completed).

[0127] Furthermore, the method of embodiment 1 (for example, any of the methods of Options 1 to 6) is applied to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added after the terminal-specific PUSCH configuration is completed.

[0128] <Option E> In Option E, the method of embodiment 1 (for example, any of the methods of Option 1 to Option 6), the method of embodiment 2, or the method of embodiment 3 is applied to the repetition of Msg.5 PUSCH (for example, a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added until the terminal-specific PUSCH configuration is completed).

[0129] Furthermore, after the terminal-specific PUSCH configuration is completed, the number of repetitions is configured by the terminal-specific RRC for the PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached, and terminal 200 applies repetition to the PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached, based on the quasi-static number of repetitions configured by the RRC.

[0130] <Option F> In Option F, the method of embodiment 1 (for example, any of the methods of Option 1 to Option 6), the method of embodiment 2, or the method of embodiment 3 is applied to the repetition of Msg.5 PUSCH (for example, a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added before the terminal-specific PUSCH configuration is completed).

[0131] Furthermore, after the terminal-specific PUSCH configuration is completed, repetition based on the repetition count of the Mg.5 PUSCH assigned immediately before is applied to the PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is added.

[0132] <Option G> In Option G, the method of embodiment 1 (for example, any of the methods of Option 1 to Option 6), the method of embodiment 2, or the method of embodiment 3 is applied to the repetition of Msg.5 PUSCH (for example, a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added until the terminal-specific PUSCH configuration is completed).

[0133] Furthermore, for PUSCHs scheduled by DCI format 0-0 with CRC scrambled by C-RNTI added after the terminal-specific PUSCH configuration is complete, the repetition count is set in the same way as for PUSCHs scheduled by DCI format 0-1 / 0-2 up to Release 18. For example, a maximum of 2 columns containing TDRA-related parameters (e.g., slot index, number of symbols, etc.) and the repetition count are used. 5 A table of rows may be set by RRC, and any of the indices corresponding to each row of the table may be notified to terminal 200, thereby notifying the TDRA parameters and the number of repetitions.

[0134] <Option H> In Option H, the method of embodiment 1 (for example, any of the methods of Option 1 to Option 6), the method of embodiment 2, or the method of embodiment 3 is applied to the repetition of Msg.5 PUSCH (for example, a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added until the terminal-specific PUSCH configuration is completed).

[0135] Furthermore, PUSCH repetition is not supported for PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added after terminal-specific PUSCH configuration is completed.

[0136] Examples of combinations of functions applied to each PUSCH have been described above. Note that the functions applied to each PUSCH and the combinations of functions are not limited to the examples shown in FIG.

[0137] According to the present embodiment, it is possible to have the flexibility to apply different design guidelines to a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached before terminal-specific PUSCH configuration is completed, and a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached after terminal-specific PUSCH configuration is completed.

[0138] (Variations of Embodiments 4 and 5) In the above-described Embodiments 4 and 5, a change in transmission timing may occur between the repetition of Msg. 5 PUSCH (for example, the transmission of a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached before a terminal-specific PUSCH configuration (Dedicated PUSCH configuration) is completed, and the transmission of a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached after a terminal-specific PUSCH configuration (Dedicated PUSCH configuration) is completed).

[0139] In this case, the timing of the switching (e.g., the timing at which the terminal-specific PUSCH configuration is completed) may be, for example, the timing after the terminal 200 has successfully received an RRC message (e.g., RRCSetup) and the corresponding RRC decoding time specified in Non-Patent Document 9 has elapsed.

[0140] For example, the timing of switching may be set to "a certain time (e.g., 10 ms) after receiving an RRC message (e.g., RRCSetup)" which is set as the required time for RRC processing from RRCSetup to transmitting RRCSetupComplete.

[0141] Furthermore, the timing of the switch (e.g., the timing at which terminal-specific PUSCH configuration is completed) may be specified in advance in a standard, or may be set in terminal 200 by SIB or RRC. For example, a certain time (e.g., 10 ms) after reception of an RRC message (e.g., RRC Setup) may be set.

[0142] The period after receiving an RRC message (for example, RRC Setup), which is set as the timing of switching, is not limited to 10 ms, and may be another value.

[0143] [Configuration of Base Station] Fig. 8 is a block diagram showing an example configuration of base station 100. In Fig. 8, base station 100 has a control unit 101, a higher-level control signal generation unit 102, a downlink control information generation unit 103, an encoding unit 104, a modulation unit 105, a signal allocation unit 106, a transmission unit 107, a reception unit 108, an extraction unit 109, a demodulation unit 110, and a decoding unit 111.

[0144] The transmitting unit 107 shown in Fig. 8 may be included in the transmitting unit shown in Fig. 1. Furthermore, at least one of the control unit 101, higher-level control signal generating unit 102, downlink control information generating unit 103, encoding unit 104, modulation unit 105, signal allocation unit 106, receiving unit 108, extraction unit 109, demodulation unit 110, and decoding unit 111 shown in Fig. 8 may be included in the receiving unit shown in Fig. 1.

[0145] The control unit 101 determines information related to uplink transmission (e.g., PUSCH transmission) for terminal 200, for example, and outputs the determined information to at least one of the higher control signal generation unit 102 and the downlink control information generation unit 103. The information related to PUSCH transmission may include, for example, information related to PUSCH repetition (e.g., the number of repetitions), time domain resource allocation information (e.g., TDRA), and frequency domain resource allocation information (e.g., FDRA). Furthermore, the control unit 101 outputs the determined information to the extraction unit 109, the demodulation unit 110, and the decoding unit 111.

[0146] Furthermore, the control unit 101 determines, for example, information related to a downlink signal for transmitting a higher control signal or downlink control information (for example, a modulation and coding scheme (MCS) and radio resource allocation), and outputs the determined information to the coding unit 104, the modulation unit 105, and the signal allocation unit 106. Furthermore, the control unit 101 outputs, for example, information related to the downlink signal (for example, a data signal or a higher control signal) to the downlink control information generation unit 103.

[0147] The higher-level control signal generating section 102 generates a higher-level layer control signal bit string based on information input from the control section 101 , for example, and outputs the higher-level layer control signal bit string to the encoding section 104 .

[0148] The downlink control information generation unit 103 generates a downlink control information (e.g., DCI) bit sequence based on, for example, information input from the control unit 101, and outputs the generated DCI bit sequence to the encoding unit 104. Note that control information may be transmitted to multiple terminals. For example, the downlink control information generation unit 103 may generate a DCI bit sequence (also referred to as a DCI sequence) including information related to PUSCH repetition according to any of the above-described embodiments. Furthermore, the downlink control information generation unit 103 may add a CRC sequence scrambled by an RNTI (e.g., C-RNTI) to the DCI sequence according to any of the above-described embodiments.

[0149] For example, based on information input from the control unit 101, the coding unit 104 codes the bit sequence input from the higher control signal generation unit 102 or the DCI bit sequence input from the downlink control information generation unit 103. The coding unit 104 outputs the coded bit sequence to the modulation unit 105.

[0150] The modulation unit 105 modulates the coded bit sequence input from the coding unit 104, for example, based on information input from the control unit 101, and outputs the modulated signal (for example, a symbol sequence) to the signal allocation unit 106.

[0151] The signal allocation unit 106 maps the symbol sequence (including, for example, a downlink data signal or a control signal) input from the modulation unit 105 to the radio resource, for example, based on information indicating the radio resource input from the control unit 101. The signal allocation unit 106 outputs the downlink signal onto which the signal has been mapped to the transmission unit 107.

[0152] The transmitting unit 107 performs, for example, orthogonal frequency division multiplexing (OFDM) transmission waveform generation processing on the signal input from the signal allocating unit 106. Furthermore, in the case of OFDM transmission that adds a cyclic prefix (CP), the transmitting unit 107 performs inverse fast Fourier transform (IFFT) processing on the signal and adds the CP to the signal after the IFFT. Furthermore, the transmitting unit 107 performs RF processing, such as D / A conversion or up-conversion, on the signal and transmits the radio signal to the terminal 200 via an antenna.

[0153] The receiving unit 108 performs RF processing such as downconvert or A / D conversion on an uplink signal received from the terminal 200 via an antenna. In addition, in the case of OFDM transmission, the receiving unit 108 performs Fast Fourier Transform (FFT) processing on the received signal, for example, and outputs the resulting frequency domain signal to the extracting unit 109.

[0154] The extraction unit 109 extracts, for example, based on information input from the control unit 101, a radio resource portion from which an uplink signal (e.g., PUSCH) is transmitted, from the received signal input from the receiving unit 108, and outputs the extracted radio resource portion to the demodulation unit 110.

[0155] The demodulation unit 110 demodulates the uplink signal (e.g., PUSCH) input from the extraction unit 109, based on, for example, information input from the control unit 101. The demodulation unit 110 outputs the demodulation result to, for example, the decoding unit 111.

[0156] The decoding unit 111 performs error correction decoding of the uplink signal (e.g., PUSCH) based on, for example, information input from the control unit 101 and the demodulation result input from the demodulation unit 110, and obtains a decoded received bit sequence.

[0157] [Terminal Configuration] Fig. 9 is a block diagram showing an exemplary configuration of a terminal 200 according to an embodiment of the present disclosure. For example, in Fig. 9, the terminal 200 includes a receiving unit 201, an extracting unit 202, a demodulating unit 203, a decoding unit 204, a control unit 205, an encoding unit 206, a modulating unit 207, a signal allocating unit 208, and a transmitting unit 209.

[0158] Note that receiving unit 201 shown in Fig. 9 may be included in the receiving unit shown in Fig. 2. Also, at least one of extracting unit 202, demodulating unit 203, decoding unit 204, control unit 205, encoding unit 206, modulating unit 207, signal allocating unit 208, and transmitting unit 209 shown in Fig. 9 may be included in the transmitting unit shown in Fig. 2.

[0159] The receiving unit 201 receives, for example, a downlink signal (e.g., a downlink data signal or downlink control information) from the base station 100 via an antenna, and performs RF processing such as downconverting or A / D conversion on the radio received signal to obtain a received signal (baseband signal). Furthermore, when receiving an OFDM signal, the receiving unit 201 performs FFT processing on the received signal to convert it into the frequency domain. The receiving unit 201 outputs the received signal to the extracting unit 202.

[0160] For example, based on information relating to the radio resource of the downlink control information input from the control unit 205, the extraction unit 202 extracts a radio resource portion that may include the downlink control information from the received signal input from the receiving unit 201, and outputs the extracted radio resource portion to the demodulation unit 203. Furthermore, based on information relating to the radio resource of the data signal input from the control unit 205, the extraction unit 202 extracts a radio resource portion that includes the downlink data signal, and outputs the extracted radio resource portion to the demodulation unit 203.

[0161] The demodulation unit 203 demodulates the signal (for example, PDCCH or PDSCH) input from the extraction unit 202 based on information input from the control unit 205 , for example, and outputs the demodulation result to the decoding unit 204 .

[0162] The decoding unit 204 performs error correction decoding of the PDCCH or PDSCH using, for example, the demodulation result input from the demodulation unit 203, and obtains, for example, an upper layer control signal or downlink control information. The decoding unit 204 outputs the upper layer control signal and the downlink control information to the control unit 205. Furthermore, the decoding unit 204 may generate a response signal (for example, ACK / NACK) based on the decoding result of the PDSCH.

[0163] The control unit 205 performs uplink transmission control (including, for example, specifying information about PUSCH repetition, such as whether or not repetition is performed for PUSCH transmission and the number of repetitions) according to the above-described method, based on, for example, information about PUSCH transmission obtained from a signal (for example, a higher layer control signal or downlink control information) input from the decoding unit 204. The control unit 205 outputs the determined information to, for example, the encoding unit 206 and the signal allocation unit 208.

[0164] The encoding unit 206 encodes an uplink data signal (UL data signal) or an uplink control signal, for example, based on information input from the control unit 205. The encoding unit 206 outputs the encoded bit string to the modulation unit 207.

[0165] The modulation unit 207 modulates, for example, the coded bit sequence input from the coding unit 206 and outputs the modulated signal (symbol sequence) to the signal allocation unit 208 .

[0166] The signal allocation unit 208 maps the signal (e.g., a sequence) input from the modulation unit 207 to a radio resource, for example, based on information input from the control unit 205. The signal allocation unit 208 outputs the uplink signal onto which the signal is mapped to the transmission unit 209, for example.

[0167] The transmitter 209 generates a transmission signal waveform, such as OFDM, for the signal input from the signal allocation unit 208. Furthermore, in the case of OFDM transmission using a CP, for example, the transmitter 209 performs IFFT processing on the signal and adds a CP to the signal after the IFFT. Alternatively, when the transmitter 209 generates a single-carrier waveform, a DFT unit (not shown) may be added after the modulator 207 or before the signal allocation unit 208. Furthermore, the transmitter 209 performs RF processing, such as D / A conversion and up-conversion, on the transmission signal, and transmits the radio signal to the base station 100 via an antenna.

[0168] (Other Embodiments) (1) In the above-described embodiments, base station 100 may notify terminal 200 in an SIB that it supports Msg.5 PUSCH repetition or the repetition function for a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by C-RNTI is added until a terminal-specific PUSCH configuration (e.g., a Dedicated PUSCH configuration) is completed.

[0169] (2) In the above-described embodiment, terminal 200 may request Msg.5 PUSCH repetition from base station 100, or may notify base station 100 that it has Msg.5 PUSCH repetition capability.

[0170] Terminal 200 does not need to notify base station 100 that it has Msg.5 PUSCH repetition capability. In the above-described second or third embodiment, base station 100 may transmit DCI format 0-0 with a different DCI payload size or DCI format 0-0 scrambled by a different C-RNTI to terminal 200, regardless of the capability of terminal 200, and terminal 200 may transmit a PUSCH or PUSCH repetition corresponding to DCI format 0-0 that has been successfully decoded.

[0171] (3) In the above-described embodiment, whether flexible symbols can be used for a PUSCH scheduled using DCI format 0-0 to which a CRC scrambled by the C-RNTI is added may be determined by the following method: For example, terminal 200 may be configured by the following explicit notification whether slots including flexible symbols or flexible symbols themselves, which are configured via higher layer parameters (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), are available for PUSCH repetition.

[0172] [Option 1: Notification by Bitmap via SIB / Msg.4 PDSCH / DCI] Base station 100 includes a bitmap indicating whether slots including Flexible symbols are available in an SIB, Msg.4 PDSCH, or DCI, and notifies terminal 200. Each bit in the bitmap corresponds to one slot or multiple slots configured by Flexible symbols, and indicates whether the associated slot is available.

[0173] [Option 2: Notification by 1-bit flag in SIB / Msg.4 PDSCH / DCI] Base station 100 includes a 1-bit flag indicating whether a slot including a Flexible symbol is available in an SIB, Msg.4 PDSCH, or DCI, and notifies terminal 200. For example, if the 1-bit flag is triggered, it indicates that the Flexible symbol is available for PUSCH repetition, and if the 1-bit flag is not triggered, it indicates that the Flexible symbol is not available for PUSCH repetition.

[0174] [Option 3: Notification by invalidSymbolPattern in SIB / Msg.4 PDSCH / DCI] Base station 100 includes information (e.g., existing invalidSymbolPattern) indicating symbols that are invalid for PUSCH repetition (e.g., invalid symbol patterns) in an SIB, Msg.4 PDSCH, or DCI, and notifies terminal 200. The invalidSymbolPattern indicates, for example, whether flexible symbols are available.

[0175] The above describes an example of a method for notifying whether a slot containing a Flexible symbol is available.

[0176] Furthermore, when notification regarding whether flexible symbols can be used is transmitted by DCI, in the above-described second embodiment, a field for reporting information regarding whether flexible symbols can be used may be added to DCI format 0-0 as an information field for reporting information regarding PUSCH repetition.

[0177] Furthermore, the function regarding whether Flexible symbols can be used may be different between Mg.5 PUSCH Repetition (e.g., a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is added before a terminal-specific PUSCH configuration (e.g., a Dedicated PUSCH configuration) is completed) and a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is added after a terminal-specific PUSCH configuration (e.g., a Dedicated PUSCH configuration) is completed). For example, in Mg.5 PUSCH Repetition, whether Flexible symbols can be used may be determined based on a notification regarding whether Flexible symbols can be used. On the other hand, in a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is added after a terminal-specific PUSCH configuration is completed, whether Flexible symbols can be used may be predetermined in the standard (e.g., a setting that allows Flexible symbols to be used at all times may be used).

[0178] (4) In the above-described embodiment, for a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by a C-RNTI is added, whether or not frequency hopping is applied and the hopping method may be determined by the following method.

[0179] [Option a] Intra-slot frequency hopping is not applied to PUSCH repetitions scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is added. In this case, the information field related to the frequency hopping flag in DCI format 0-0 may be used, for example, to notify whether inter-slot frequency hopping is enabled or disabled.

[0180] [Option b] Both intra-slot frequency hopping and inter-slot frequency hopping are supported for PUSCH repetitions scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is added. The information field related to the frequency hopping flag in DCI format 0-0 may be used, for example, to notify whether inter-slot frequency hopping or intra-slot frequency hopping is enabled or disabled. Furthermore, for example, information regarding which hopping method, inter-slot frequency hopping or intra-slot frequency hopping, is to be applied may be included in an SIB, Msg.4 PDSCH, or DCI and notified to terminal 200.

[0181] Furthermore, when information on a frequency hopping method is indicated by DCI, in the above-described second embodiment, a field for indicating information on a frequency hopping method may be added to DCI format 0-0 as an information field for indicating information on PUSCH repetition.

[0182] Furthermore, the frequency hopping functionality may be differentiated between Msg.5 PUSCH Repetition (e.g., a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached before terminal-specific PUSCH configuration (e.g., Dedicated PUSCH configuration) is completed) and a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached after terminal-specific PUSCH configuration (e.g., Dedicated PUSCH configuration) is completed. For example, Msg.5 PUSCH Repetition may support inter-slot frequency hopping but not intra-slot frequency hopping. On the other hand, a PUSCH scheduled by DCI format 0-0 to which a CRC scrambled by the C-RNTI is attached after terminal-specific PUSCH configuration is completed may support both inter-slot frequency hopping and intra-slot frequency hopping.

[0183] (5) In the above-described embodiment, the RNTI used to scramble the CRC added to the DCI is not limited to the C-RNTI, and may be another type of RNTI. For example, the C-RNTI may be replaced with a Temporary C-RNTI (TC-RNTI).

[0184] (6) In the above-described embodiments, the DCI format is not limited to DCI format 0-0 and may be another format. DCI format 0-0 may also be called, for example, a fallback DCI format. Furthermore, in the above-described embodiments, the types of information fields included in the DCI, the number of information fields, and the size (number of bits) of the information fields are merely examples, and DCI formats including information fields of other types, other numbers, or other sizes may also be used.

[0185] Furthermore, in each of the above-described embodiments, the channel used for uplink transmission (or the channel to which Repetition is applied) is not limited to PUSCH, but may be another channel. Furthermore, the type of information to be transmitted is not limited to data, but may be another type of information (for example, an uplink control signal (PUCCH)). Furthermore, an embodiment of the present disclosure is not limited to uplink transmission, but may be applied to downlink transmission or sidelink transmission.

[0186] The present disclosure may be applied to communication between terminals, such as sidelink communication, for example.

[0187] Furthermore, in the present disclosure, the downlink control channel, downlink data channel, uplink control channel, and uplink data channel are not limited to PDCCH, PDSCH, PUCCH, and PUSCH, respectively, and may be control channels with other names.

[0188] Furthermore, in the present disclosure, RRC signaling is assumed as higher layer signaling, but it may be replaced with Medium Access Control (MAC) signaling and notification by DCI, which is physical layer signaling.

[0189] (Supplementary Note) Information indicating whether the terminal 200 supports the functions, operations, or processes described in each of the above-described embodiments and each supplementary note 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.

[0190] 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, modifications, and supplements. 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.

[0191] For example, the base station 100 may determine (or decide or assume) the 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 controls according to the determination result based on the capability information. For example, the base station 100 may control uplink-related processing based on the capability information received from the terminal 200.

[0192] Note that the fact that terminal 200 does not support some of the functions, operations, or processes described in the above-described embodiments, modifications, and supplementary notes 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.

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

[0194] The above has described the embodiments, modifications, and supplementary notes according to a non-limiting example of the present disclosure.

[0195] (Control Signal) In the present disclosure, a downlink control signal (information) related to the present disclosure may be a signal (information) transmitted by a PDCCH of a physical layer, or may be a signal (information) transmitted by a MAC CE (Control Element) or RRC of a higher layer. Also, the downlink control signal may be a signal (information) that is specified in advance.

[0196] The uplink control signal (information) related to the present disclosure may be a signal (information) transmitted on a PUCCH in the physical layer, or a signal (information) transmitted on a MAC CE or RRC in a higher layer. The uplink control signal may also be a predefined signal (information). The uplink control signal may also be replaced with uplink control information (UCI), 1st stage sidelink control information (SCI), or 2nd stage SCI.

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

[0198] (Uplink / Downlink / Sidelink) The present disclosure may be applied to any of the uplink, downlink, and sidelink. For example, the present disclosure may be applied to the uplink PUSCH, PUCCH, and PRACH, the downlink PDSCH, PDCCH, and PBCH, and the sidelink PSSCH (Physical Sidelink Shared Channel), PSCCH (Physical Sidelink Control Channel), and PSBCH (Physical Sidelink Broadcast Channel).

[0199] 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. The PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel. The PBCH and PSBCH are examples of broadcast channels, and the PRACH is an example of a random access channel.

[0200] (Data Channel / Control Channel) The present disclosure may be applied to either a data channel or a control channel. For example, the channels of the present disclosure may be replaced with data channels such as PDSCH, PUSCH, and PSSCH, and control channels such as PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.

[0201] (Reference Signal) In the present disclosure, a reference signal is a signal known by both a base station and a terminal, and may also be referred to as an RS (Reference Signal) or a pilot signal. The reference signal may be any of DMRS, CSI-RS (Channel State Information - Reference Signal), TRS (Tracking Reference Signal), PTRS (Phase Tracking Reference Signal), CRS (Cell-specific Reference Signal), and SRS (Sounding Reference Signal).

[0202] (Time Interval) In 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, a subslot, a minislot, a symbol, an OFDM (Orthogonal Frequency Division Multiplexing Access) symbol, or an SC-FDMA (Single Carrier-Frequency Division Multiple Access) 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.

[0203] (Frequency Band) The present disclosure may be applied to either a licensed band or an unlicensed band.

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

[0205] The present disclosure may be applied to a terrestrial network, a non-terrestrial network (NTN) using satellites or highly advanced pseudo satellites (HAPS), or a terrestrial network in which the 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.

[0206] (Full Duplex and SBFD) In ​​one embodiment of the present disclosure, operations on uplink, downlink, and sidelink symbols may be applied to symbols (e.g., SBFD symbols) on which SBFD (Subband Non-Overlapping Full Duplex) operations or control are performed. In SBFD symbols, a frequency domain (or frequency resource, frequency band) is divided into multiple frequency domains (e.g., subbands, RB sets, subbands, or sub-BWPs (Bandwidth Parts)). A terminal transmits and receives in different directions (e.g., downlink or uplink) in units of subbands, which are the divided domains. In SBFD symbols, a terminal may transmit and receive in one direction, either uplink or downlink, but not in the other direction. On the other hand, a base station may transmit and receive on the uplink and downlink simultaneously, or may be able to transmit and receive on both the uplink and downlink simultaneously. In SBFD symbols, the frequency domain available for the downlink may be smaller than in symbols that transmit and receive only downlink. Furthermore, in the SBFD symbol, the frequency region available for uplink transmission may be smaller than in the symbol for transmitting and receiving only uplink.

[0207] In addition, in the SBFD symbol, a terminal may transmit and receive uplink and downlink simultaneously. In this case, the frequency domain in which the terminal transmits and the frequency domain in which the terminal receives may not be adjacent, but may be separated by a frequency interval (also called a frequency gap).

[0208] Furthermore, different directions in subband units, which are divided areas, may include transmission and reception of sidelinks.

[0209] In one embodiment of the present disclosure, the operations for uplink, downlink, and sidelink symbols may be applied to symbols (e.g., full duplex symbols) for which full duplex operation or control is performed. In full duplex symbols, both the terminal and the base station can simultaneously transmit and receive on the uplink and downlink. In full duplex symbols, the terminal and the base station may simultaneously transmit and receive in an available frequency region (or frequency resource, frequency band), or may simultaneously transmit and receive in a partial frequency region (i.e., transmission or reception may be performed in a frequency region other than the partial frequency region). In this case, the frequency region in which the base station or terminal transmits and receives may not be adjacent, but may have a frequency interval (also called a frequency gap). Furthermore, for example, for the purpose of reducing interference, either the terminal or the base station may simultaneously transmit and receive (i.e., the other may transmit or receive).

[0210] In addition, full duplex operation may be applied to an operation in which a terminal can simultaneously transmit and receive sidelinks, or to an operation in which a terminal can simultaneously transmit and receive sidelinks and uplinks or downlinks.

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

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

[0213] For example, the system architecture generally assumes a Next Generation - Radio Access Network (NG-RAN) comprising gNBs. The gNBs provide UE-side termination of the 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 10 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0214] The NR user plane protocol stack (see, for example, 3GPP TS 38.300, section 4.4.1) includes a Packet Data Convergence Protocol (PDCP) sublayer (see Section 6.4 of TS 38.300), a Radio Link Control (RLC) sublayer (see Section 6.3 of TS 38.300), and a Medium Access Control (MAC) sublayer (see Section 6.2 of TS 38.300), which are terminated on the network side in the gNB. A new Access Stratum (AS) sublayer (Service Data Adaptation Protocol (SDAP)) has also been introduced above PDCP (see, for example, Section 6.5 of 3GPP TS 38.300). A control plane protocol stack has also been defined for the NR (see, for example, Section 4.4.2 of TS 38.300). An overview of Layer 2 functions is provided 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.

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

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

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

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

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

[0220] <Functional Separation Between NG-RAN and 5GC in 5G NR> Figure 11 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.

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

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

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

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

[0225] <RRC connection setup and reconfiguration procedure> Figure 12 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).

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

[0227] Therefore, 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.

[0228] <IMT Usage Scenarios Beyond 2020> Figure 13 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 13 shows some examples of envisioned usage scenarios for IMT beyond 2020 (see, for example, ITU-R M.2083 Figure 2).

[0229] The URLLC use case has stringent performance requirements, such as 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.

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

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

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

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

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

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

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

[0237] 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 FIG. 12. 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.

[0238] Figure 14 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 13) 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 the associated Network Functions. Application Functions not permitted by the operator to directly access Network Functions interact with the associated Network Functions using an external exposure framework via the NEF.

[0239] Figure 14 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.

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

[0241] The term "portion" used in this disclosure may be interchangeably used with other terms such as "circuitry," "device," "unit," or "module."

[0242] The present disclosure can be realized by software, hardware, or software in conjunction with hardware. Each functional block used in the description of the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit, and 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 input and output. Depending on the degree of integration, the LSI may also be called an IC, system LSI, super LSI, or ultra LSI.

[0243] The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. Also, a field programmable gate array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells within the LSI, may be used. The present disclosure may be realized as digital processing or analog processing.

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

[0245] The present disclosure can be implemented in any type of apparatus, device, or system (collectively referred to as a communication apparatus) having a communication function. The communication apparatus may include a radio transceiver and processing / control circuitry. The radio transceiver may include a receiver and a transmitter, or both as 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.

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

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

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

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

[0250] A terminal according to one embodiment of the present disclosure includes a receiving circuit that receives downlink control information including information scrambled by a terminal-specific identifier and that schedules an uplink signal regardless of terminal-specific settings, and a transmitting circuit that performs repeated transmission of the uplink signal based on information regarding repeated transmission of the uplink signal that is identified based on the downlink control information.

[0251] In one embodiment of the present disclosure, the downlink control information includes a field for notifying information different from the information regarding the repeat transmission, and the information regarding the repeat transmission is allocated to at least a part of the field.

[0252] In one embodiment of the present disclosure, the downlink control information is a first DCI format 0-0 including a field indicating information related to the repeated transmission, and the payload size of the first DCI format 0-0 is different from the payload size of a second DCI format 0-0 that does not include a field indicating information related to the repeated transmission.

[0253] In one embodiment of the present disclosure, the receiving circuit performs blind decoding on a plurality of payload sizes corresponding to the first DCI format 0-0 and the second DCI format 0-0, respectively.

[0254] In one embodiment of the present disclosure, the terminal is a terminal that requests the repeated transmission of the uplink signal, a terminal that has notified the base station that it has the capability of the repeated transmission of the uplink signal, or a terminal that has the capability of the repeated transmission of the uplink signal.

[0255] In one embodiment of the present disclosure, the receiving circuit performs blind decoding for the plurality of payload sizes until a terminal-specific search space is given.

[0256] In one embodiment of the present disclosure, the identifier is a Radio Network Temporary Identifier (RNTI), the downlink control information is a first DCI format 0-0 that notifies information related to the repeated transmission, and the RNTI corresponding to the first DCI format 0-0 is different from the RNTI corresponding to a second DCI format 0-0 that does not notify information related to the repeated transmission.

[0257] In one embodiment of the present disclosure, the receiving circuit performs blind decoding on a plurality of RNTIs corresponding to the first DCI format 0-0 and the second DCI format 0-0, respectively.

[0258] In one embodiment of the present disclosure, the terminal is a terminal that requests the repeated transmission of the uplink signal, a terminal that has notified the base station that it has the capability of the repeated transmission of the uplink signal, or a terminal that has the capability of the repeated transmission of the uplink signal.

[0259] In one embodiment of the present disclosure, the receiving circuit performs blind decoding on the plurality of RNTIs until a terminal-specific search space is given.

[0260] In one embodiment of the present disclosure, the function for the repeated transmission is the same for the uplink signal scheduled by the downlink control information received by the terminal before the completion of the terminal-specific setting and the uplink signal scheduled by the downlink control information received by the terminal after the completion of the terminal-specific setting.

[0261] In one embodiment of the present disclosure, the function for the repeated transmission differs between the uplink signal scheduled by the downlink control information received by the terminal before the completion of the terminal-specific setting and the uplink signal scheduled by the downlink control information received by the terminal after the completion of the terminal-specific setting.

[0262] A base station according to one embodiment of the present disclosure includes a transmitting circuit that transmits downlink control information including information scrambled by a terminal-specific identifier and that schedules an uplink signal regardless of terminal-specific settings, and a receiving circuit that receives repeated transmissions of the uplink signal based on information regarding repeated transmissions of the uplink signal that is identified based on the downlink control information.

[0263] In a communication method according to one embodiment of the present disclosure, a terminal receives downlink control information that includes information scrambled by a terminal-specific identifier and schedules an uplink signal regardless of terminal-specific settings, and performs repeated transmission of the uplink signal based on information regarding repeated transmission of the uplink signal that is identified based on the downlink control information.

[0264] In a communication method according to one embodiment of the present disclosure, a base station transmits downlink control information including information scrambled by a terminal-specific identifier and scheduling an uplink signal regardless of terminal-specific settings, and receives repeated transmission of the uplink signal based on information regarding repeated transmission of the uplink signal that is identified based on the downlink control information.

[0265] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2023-201637, filed November 29, 2023, are incorporated herein by reference in their entirety.

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

[0267] 100 Base station 101, 205 Control unit 102 Upper control signal generation unit 103 Downlink control information generation unit 104, 206 Encoding unit 105, 207 Modulation unit 106, 208 Signal allocation unit 107, 209 Transmission unit 108, 201 Reception unit 109, 202 Extraction unit 110, 203 Demodulation unit 111, 204 Decoding unit 200 Terminal

Claims

1. A terminal comprising: a receiving circuit for receiving downlink control information including information scrambled by a terminal-specific identifier and for scheduling an uplink signal independent of terminal-specific settings; and a transmitting circuit for repeatedly transmitting the uplink signal based on information regarding the repeated transmission of the uplink signal, which is specified based on the downlink control information.

2. The terminal according to claim 1, wherein the downlink control information includes a field for notifying information different from the information relating to the repeat transmission, and the information relating to the repeat transmission is assigned to at least a portion of the field.

3. The terminal according to claim 1, wherein the downlink control information is a first DCI format 0-0 including a field indicating information related to the repeated transmission, and a payload size of the first DCI format 0-0 is different from a payload size of a second DCI format 0-0 that does not include a field indicating information related to the repeated transmission.

4. The terminal according to claim 3, wherein the receiving circuit performs blind decoding on a plurality of payload sizes corresponding to each of the first DCI format 0-0 and the second DCI format 0-0.

5. The terminal according to claim 4, wherein the terminal is a terminal that requests the repeated transmission of the uplink signal, a terminal that has notified a base station that it has the capability of the repeated transmission of the uplink signal, or a terminal that has the capability of the repeated transmission of the uplink signal.

6. The terminal according to claim 4, wherein the receiving circuit performs blind decoding for the plurality of payload sizes until a terminal-specific search space is given.

7. The terminal according to claim 1, wherein the identifier is a Radio Network Temporary Identifier (RNTI), the downlink control information is a first DCI format 0-0 that notifies information related to the repeat transmission, and the RNTI corresponding to the first DCI format 0-0 is different from the RNTI corresponding to a second DCI format 0-0 that does not notify information related to the repeat transmission.

8. The terminal according to claim 7, wherein the receiving circuit performs blind decoding on a plurality of RNTIs corresponding to the first DCI format 0-0 and the second DCI format 0-0, respectively.

9. The terminal according to claim 8, wherein the terminal is a terminal that requests the repeated transmission of the uplink signal, a terminal that has notified a base station that it has the capability of the repeated transmission of the uplink signal, or a terminal that has the capability of the repeated transmission of the uplink signal.

10. The terminal according to claim 8, wherein the receiving circuit performs blind decoding on the plurality of RNTIs until a terminal-specific search space is given.

11. The terminal according to claim 1, wherein the function for the repeated transmission is the same for the uplink signal scheduled by the downlink control information received by the terminal before the completion of the terminal-specific setting and the uplink signal scheduled by the downlink control information received by the terminal after the completion of the terminal-specific setting.

12. The terminal according to claim 1, wherein the function for the repeated transmission is different between the uplink signal scheduled by the downlink control information received by the terminal before the completion of the terminal-specific setting and the uplink signal scheduled by the downlink control information received by the terminal after the completion of the terminal-specific setting.

13. A base station comprising: a transmitting circuit that transmits downlink control information including information scrambled by a terminal-specific identifier and that schedules an uplink signal regardless of terminal-specific settings; and a receiving circuit that receives repeated transmissions of the uplink signal based on information regarding repeated transmissions of the uplink signal that is identified based on the downlink control information.

14. A communication method in which a terminal receives downlink control information including information scrambled by a terminal-specific identifier and scheduling an uplink signal regardless of terminal-specific settings, and performs repeated transmission of the uplink signal based on information regarding repeated transmission of the uplink signal identified based on the downlink control information.

15. A communication method in which a base station transmits downlink control information including information scrambled by a terminal-specific identifier and scheduling an uplink signal regardless of terminal-specific settings, and receives repeated transmission of the uplink signal based on information regarding repeated transmission of the uplink signal identified based on the downlink control information.