Terminal , base station and communication method

Abstract

The communication device comprises: a control circuit that determines the reading position of the encoded data of the aforementioned signal in a first interval of a plurality of intervals within a time zone resource to be allocated for signal transmission, wherein the determination of the reading position is based on the amount of resources not limited by the reading result of the encoded data in a second interval preceding the first interval; and a transmission circuit that transmits the signal according to the reading position.

Description

Technical Field

[0001] This disclosure relates to a communication device and a communication method. Prior Technology

[0002] In recent years, against the backdrop of the expansion and diversification of wireless services, the leapfrog development of the Internet of Things (IoT) is anticipated. The application of mobile communication has expanded beyond information terminals such as smartphones to all areas, including automobiles, homes, home appliances, and industrial machinery. To support this service diversification, in addition to increased system capacity, there is a demand for significant improvements in the performance and functionality of mobile communication systems, addressing various requirements such as the increase in the number of connected devices and low latency. Fifth-generation mobile communication systems (5G) feature high capacity and ultra-high speed (eMBB), massive machine-type communication (mMTC), and ultra-high reliability and low latency (URLLC), and can flexibly provide wireless communication according to various needs using these characteristics.

[0003] In the 3rd Generation Partnership Project (3GPP), an international standards organization, New Radio (NR) has been standardized as a type of 5G wireless interface. [Previous Technical Documents] [Non-patent literature]

[0004] Non-patent literature 1: 3GPP TS38.104 V15.14.0, “NR Base Station (BS) radio transmission and reception (Release 15),” June 2021. Non-patent literature 2: 3GPP TSG RAN Meeting #90e, RP-202928, “New WID on NR coverage enhancements,” China Telecom, December 2020. Non-patent literature 3: 3GPP TS38.211 V16.6.0, “NR Physical channels and modulation (Release 16),” June 2021. Non-patent literature 4: 3GPP TS38.212 V16.6.0, “NR Multiptexing and channel coding (Release 16),” June 2021. Non-patent literature 5: 3GPP TS38.213 V16.0.0, “NR Physical Layer procedures for control (Release 16),” June 2021. Non-patent literature 6: 3GPP TS38.214 V16.6.0, “NR Physical Layer procedures for data (Release 16),” June 2021. Non-patent document 7: 3GPP TS38.331 V16.5.0, “NR Radio Resource Control (RRC) protocol specification (Release 16)”, June 2021. Non-patent literature 8:3GPP TSG RAN WG1 #105-e, R1-2106251, “Final FL summary of TB processing over multi-slot PUSCH (AT 8.8.1.2),” Moderator (Nokia, Nokia Shanghai Bell), MAY 2021. Non-patent literature 9:3GPP TSG RAN WG1 #104-bis-e, R1-2104686, “TB processing over mluti-slot PUSCH,” Qualcomm Incorporated, May 2021. Non-Patent Document 10: 3GPP TSG RAN WG1 #105-e, R1-2104242, “Discussion on TB processing over multi-slot PUSCH, Huawei, HiSilicon, May 2021. Summary of the Invention Problems to be Solved by the Invention

[0005] However, there is still room for discussion on methods for improving communication efficiency in the uplink.

[0006] Non-limiting embodiments of the present disclosure contribute to providing a communication device and a communication method that can improve communication efficiency in the uplink. Means for Solving the Problems

[0007] A communication device according to an embodiment of the present disclosure includes: a control circuit that determines a reading position of encoded data of the signal in a first interval among a plurality of intervals in a time-domain resource to be allocated for transmitting the signal, wherein the determination of the reading position is based on a resource amount that is not limited by a reading result of the encoded data in a second interval earlier than the first interval; and a transmission circuit that transmits the signal according to the reading position.

[0008] In addition, these general or specific aspects can be implemented by a system, a device, a method, an integrated circuit, a computer program, or a recording medium, or can also be implemented by any combination of a system, a device, a method, an integrated circuit, a computer program, and a recording medium. Advantages of the Invention

[0009] According to an embodiment of the present disclosure, communication efficiency in the uplink can be improved.

[0010] Further advantages and effects of an embodiment of the present disclosure will become clearer based on the description and the drawings. These advantages and / or effects are provided separately by several implementation forms and the features described in the description and the drawings, but it is not necessary to provide all of them to obtain one or more of the same features. Brief Description of the Drawings

[0011] Figure 1 shows an example of the time zone resources that constitute a Transport Block processing over a Multi-Slot Physical Uplink Shared Channel (TBoMS). Figure 2 shows an example of using TBoMS derived from Option 1's Rate matching. Figure 3 shows an example of using TBoMS derived from Rate matching of Option 2. Figure 4 shows an example of using TBoMS derived from Rate matching in Option 3. Figure 5 shows an example of TBoMS derived from Rate matching of Option 2 with a variable Redundancy Version (RV) position. Figure 6 is a block diagram showing an example of the composition of a part of the base station. Figure 7 is a block diagram showing an example of the configuration of one part of a terminal. Figure 8 is a block diagram showing an example of the structure of a base station. Figure 9 is a block diagram showing an example of the configuration of a terminal. Figure 10 is a flowchart showing an example of the transmission operation of a terminal. Figure 11 shows an example of TBoMS using rate matching in implementation type 1. Figure 12 shows an example of TBoMS using Rate matching in Implementation Type 1. Figure 13 shows an example of TBoMS using rate matching in implementation type 2. Figure 14 shows an example of a Special slot. Figure 15 shows an example of the time zone resources that constitute TBoMS. Figure 16 is a diagram showing an example of the relationship between the value of the RV field and the RV position. Figure 17 is an example of the architecture of a 3GPP NR system. Figure 18 shows a schematic diagram of the functional separation between NG-RAN and 5GC. Figure 19 is a sequence diagram of the setup / reconfiguration procedure for Radio Resource Control (RRC) connection. Figure 20 shows a schematic diagram of the application scenarios for enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC). Figure 21 is a block diagram illustrating an example 5G system architecture for use in a non-roaming scenario. Implementation

[0012] The embodiments disclosed herein are described in detail below with reference to the diagrams.

[0013] In NR, in addition to the sub-6GHz bands, primarily the 700MHz to 3.5GHz bands used for cellular communication (e.g., also known as Frequency Range 1 (FR1)), millimeter waves in the 28GHz or 39GHz bands (e.g., also known as FR2) can be used to ensure a wide bandwidth (see, for example, Non-Patent Document 1). Furthermore, for example, in FR1, it is possible to use a higher frequency band than that used in Long Term Evolution (LET) or 3G (3rd Generation mobile communication systems) in the 3.5GHz band. The higher the frequency band, the greater the potential for radio wave transmission loss and the more likely the radio wave reception quality will deteriorate. Therefore, in NR, for example, when using a higher frequency band than LTE or 3G, it is necessary to ensure a communication range (or coverage) comparable to that of LTE or 3G Radio Access Technology (RAT). In other words, it is desirable to ensure adequate communication quality. For example, in Release 17 (referred to as "Rel.17"), methods for improving coverage in NR have been reviewed (see, for example, non-patent literature 2).

[0014] In NR, for example, a terminal (also known as User Equipment (UE)) transmits and receives data according to the resource allocation indicated by at least one of the downlink control signals (e.g., DCI: Downlink Control Information) of the physical layer (layer 1) transmitted in the downlink control channel (e.g., also known as PDCCH: Physical Downlink Control Channel) from the base station (e.g., also known as gNB) and the corresponding layer 3 Radio Resource Control (RRC) (e.g., see Non-Patent Documents 3 to 7).

[0015] In the uplink, for example, the terminal transmits uplink data channels (e.g., PUSCH: Physical Uplink Shared Channel) according to resource allocations (e.g., grants or UL grants) from the base station. The resource allocation information contained in at least one of the DCI and RRC may also include, for example, information about the time zone resources for transmitting the PUSCH. For example, the information about the time zone resources may include information about the time point from when the terminal receives the PDCCH to when the PUSCH is transmitted (e.g., slot offset) (e.g., K2), the position of the leading symbol of the PUSCH within the time slot, or the number of symbols for the transmitted PUSCH.

[0016] In NR uplink transmission, a method of transmitting the same information multiple times (also known as repetition) is supported. For example, Release 15 (e.g., "Rel.15") specifies a repetition in time slot units called "PUSCH repetition Type A", while Release 16 (e.g., "Rel.16") specifies a repetition called "PUSCH repetition Type B", which can transmit multiple PUSCHs within one time slot. For example, PUSCH repetition Type B can achieve lower latency than PUSCH repetition Type A.

[0017] In PUSCH repetition Type A, the same time resource allocation is applied across a plurality of consecutive time slots. In PUSCH repetition Type A, the base station notifies the terminal of the time resource allocation within the time slot and the number of repetitive time slots. Here, the number of repetitive time slots can be, for example, a value counted based on consecutive time slots.

[0018] In PUSCH repetition Type B, the base station system may, for example, notify the terminal of the time zone resources and repetition number relative to the first (initial) PUSCH transmission. In the allocation of time zone resources for subsequent PUSCH transmissions, the system may, for example, allocate symbols consecutive to the previous PUSCH transmission and with the same number of symbols.

[0019] In PUSCH repetition Type A, the number of repetition slots notified is a value counted based on consecutive slots. Therefore, the actual number of slots transmitted for PUSCH may sometimes be less than the number of repetition slots notified.

[0020] Therefore, in Rel.17, a method has been reviewed, for example, to set the number of repetition slots to a value that is counted based on the uplink slots available for use on PUSCH transmission, as a functional extension of PUSCH repetition Type A.

[0021] Furthermore, in Re.15 and Rel.16 (e.g., also referred to as "Rel.15 / 16"), the data size or transport block size (TBS) is not limited by the presence or absence of a repetition, but is determined by the amount of resources per time slot unit, or the amount of resources allocated to the initial PUSCH transmission in a repetition (e.g., the amount of resources allocated to the PUSCH transmission of the preceding time slot in a repetition) (see, for example, Non-Patent Document 6). Additionally, the amount of resources can be represented, for example, by the number of symbols or resource elements (RE). Furthermore, TBS is sometimes described as TB size.

[0022] On the other hand, in Rel. 17, a method was reviewed in which, when using multiple time slots to transmit PUSCH, the TBS calculated from the amount of resources to be allocated to the initial PUSCH transmission from the time slot unit or repetition is multiplied by a scaling factor greater than 1 to determine the TBS. PUSCH transmission in multiple time slots with a TBS determined by this method is also called "TB processing over multi-slot PUSCH (TBoMS)" or "TBoMS transmission".

[0023] In TBoMS, the allocation of the same time resources across multiple time slots was reviewed, for example, in the same manner as PUSCH repetition Type A. Furthermore, the parameters used to determine the number of time slots used in TBoMS were reviewed, for example, to be included in the RRC information element (IE:Information Element) that sets information about the time zone resources for transmitting PUSCH.

[0024] For example, the information element of the RRC regarding the time zone resource information for transmitting PUSCH can be a "PUSCH-TimeDomainResourceAllocation IE" (see Non-Patent Document 8). The PUSCH-TimeDomainResourceAllocation can include, for example, information about the time point from receiving the PUSCH time slot to transmitting the PUSCH (e.g., time slot offset), the position of the PUSCH leading symbol within the time slot, the number of symbols for transmitting the PUSCH, or parameters regarding the number of TBoMS time slots. For example, a candidate combination of such parameters can be set (e.g., called a "TDRA List" or "TDRA table"). The terminal can, for example, use the digital data of the DCI or RRC of the corresponding PUSCH to be allocated, and select a combination of parameters from the candidate combinations of parameters that is suitable for the PUSCH transmission actually used by the terminal.

[0025] Furthermore, in TBoMS, the use of non-contiguous time slots for TBoMS transmission, at least in Time Division Duplex (TDD), has been examined. Additionally, the intervals (groups) formed by one or a plurality of consecutive time slots within the time zone resources (e.g., time slots) allocated to TBoMS are sometimes referred to as "TOT: Transmission Occasion for TBoMS" (see, for example, Non-Patent Document 8). The time zone resources to be allocated to TBoMS can be formed by one or a plurality of TOTs.

[0026] Figure 1 shows an example of time zone resources for a TBoMS when four time slots are to be allocated to the TBoMS and two consecutive time slots constituting a TOT are to be allocated to the TBoMS. In Figure 1, the time zone resources to be allocated to the TBoMS consist of two TOTs (a total of four time slots).

[0027] Regarding rate matching using a Circular Buffer In NR, a Circular Buffer is used, for example, in retransmission control. The Circular Buffer is memory that stores encoder output (e.g., encoded data or encoded bits containing systematic bits and parity bits), and reads the encoder output from the Circular Buffer at a specified read start position (RV: Redundancy Version) that matches the allocated resource amount. The action of reading encoded bits from the Circular Buffer at the specified RV according to the allocated resource amount is also called "Rate matching".

[0028] In Rel. 15 / 16, for example, four RV positions are specified within the Circular Buffer. In Rel. 15 / 16, the RV positions specified in the Circular Buffer are fixed positions, not limited by the allocation amount. For example, in TBoMS, as a method for mapping the encoded bits of the TB generated by the above method onto multiple time slots, the following three methods (Option 1, Option 2, and Option 3) can be listed.

[0029] <option 1> Option 1 is a method for setting the time zone resources (also known as "TBoMS resources") to be allocated to TBoMS as the unit of rate matching.

[0030] For example, Option 1 reads encoded bits from a specified RV location that correspond to the number of time slots (e.g., multiple time slots, or one or multiple TOTs) of resources used for transmission in TBoMS, and maps the read encoded bits to TBoMS resources covering multiple time slots. In Option 1, for example, the RV location used for reading encoded bits is a single location.

[0031] Figure 2 illustrates an example of TBoMS using Option 1 Rate matching. In Figure 2, as an example, the TBoMS resources contain two TOTs consisting of two time slots each (e.g., a total of four time slots). In the example shown in Figure 2, the terminal can read the number of bits corresponding to the amount of resources to be allocated to the four time slots of the TBoMS from the specified RV position of the Circular Buffer (also represented as RV=0 or RV0), and map the read encoded bits to the TBoMS resources covering the four time slots.

[0032] In Option 1, for example, the encoded bits that correspond to the number of bits of the TBoMS resource are read sequentially from a single RV position. Therefore, it is highly likely that all encoded bits stored in the Circular Buffer in the TBoMS resource will be transmitted. Thus, it has the advantage of obtaining sufficient encoding gain and excellent decoding performance.

[0033] On the other hand, in Option 1, for example, when the unit of rate matching is the time resources to be allocated to TBoMS, the multiple time slots to be allocated to TBoMS are considered in the calculation of the number of bits that meet the allocation resource amount and the bit interleave processing. Thus, since rate matching processing can begin based on the resource amount of multiple time slots in Option 1, the processing latency in the terminal is prone to increase. For example, when TBoMS is transmitted using non-contiguous time slots as shown in Figure 2, the impact of processing latency in the terminal may become more significant.

[0034] Furthermore, for example, when the time zone resources transmitted by TBoMS conflict with the transmission resources of the uplink control channel (e.g., PUSCH: Physical Uplink Control Channel) for transmitting uplink control information (e.g., UCI: Uplink control Channel), the terminal can multiplex the UCI to TBoMS. In this case, in Option 1, since the terminal starts rate matching processing, for example, considering the UCI multiplexed at the end of the time slot allocated to TBoMS, the processing latency is likely to increase.

[0035] Furthermore, for example, when the time zone resources transmitted by TBoMS conflict with the resources indicated by the uplink cancellation notification (e.g., UL CI: Uplink Link Cancellation Indication), or when the time zone resources transmitted by TBoMS conflict with the allocation of high-priority uplink transmissions, the processing latency in the terminal is also likely to increase.

[0036] Alternatively, for example, the conflict-handling unit can be replaced from a time slot with a time zone resource to be allocated to TBoMS. In this case, for example, the time slot that can handle conflicts (e.g., referred to as the base time slot) is set to be allocated to the time slot preceding TBoMS, which may create a limitation on the terminal's processing timeline.

[0037] < / option> <option 2> Option 2 is a method for setting the time slot to the unit of rate matching.

[0038] For example, Option 2 reads the number of encoded bits from the specified RV position that matches the amount of resources to be allocated to the PUSCH transmission in each time slot used for TBoMS transmission, and maps the read encoded bits individually to the resources within the time slot. In Option 2, for example, the RV position used for reading the encoded bits can be different. In other words, in Option 2, the RV position can be set (e.g., changed) individually within the time slot.

[0039] Figure 3 illustrates an example of TBoMS using Option 2 rate matching. In Figure 3, as an example, the TBoMS resources contain two TOTs consisting of two time slots each (e.g., a total of four time slots). In the example shown in Figure 3, the terminal can read the number of bits corresponding to the resource amount of each of the four time slots to be allocated to the TBoMS from the specified RV position (e.g., any one of RV=0 (RV0), RV=2 (RV2), RV=3 (RV3), and RV=1 (RV1)) set in the Circular Buffer of that time slot, and map the read encoded bits to the resources within the time slot.

[0040] In Option 2, for example, the terminal can also begin rate matching processing without considering the resource availability of multiple time slots, and can process time slot units. Therefore, Option 2 is effective, for example, in facilitating support for non-contiguous time slots or in handling conflict, and can suppress the increase in processing latency in the terminal. Furthermore, in Option 2, for example, time slot units can be processed in conflict handling, and the time slots that can be conflicted (e.g., the base time slot) can be set to time slots that may conflict, so there is no limitation on the terminal's processing timeline.

[0041] On the other hand, in Option 2, as shown in Figure 3, when reading encoded bits from the existing four RV positions such as Rel. 15 / 16, it is not easy to transmit all encoded bits during TBoMS transmission. For example, the higher the coding rate, the fewer encoded bits are read, and it is highly likely that not all encoded bits can be transmitted in TBoMS. Therefore, in Option 2, it is not easy to obtain coding gain, and decoding performance is prone to degrade.

[0042] < / option><option 3> Option 3 sets TOT as the unit for rate matching.

[0043] For example, Option 3 reads the encoded bits corresponding to the number of resources in the TOT of the TBoMS from the specified RV position, and maps the read encoded bits individually to the resources within the TOT. In Option 3, for example, the RV position used for reading the encoded bits can be different. In other words, in Option 3, the RV position can be set (e.g., changed) individually within the TOT.

[0044] Figure 4 illustrates an example of TBoMS using Option 3 rate matching. In Figure 4, as an example, the TBoMS resources contain two TOTs (e.g., a total of four time slots) each consisting of two time slots. In the example shown in Figure 4, the terminal can read the number of bits corresponding to the resource amount of the TOT (e.g., two time slots) from the specified RV position (e.g., either RV=0 (RV0) or RV=2 (RV2)) set in the Circular Buffer of each of the two TOTs to be allocated to the TBoMS, and map the read encoded bits to the resources within the TOT.

[0045] In Option 3, for example, the impact of processing latency in the terminal can be mitigated because the rate matching unit is shorter than that in Option 1. Furthermore, Option 3, for example, can suppress the degradation in decoding performance caused by more (e.g., all) coded bits not being transmitted more effectively than Option 2.

[0046] On the other hand, in Option 3, as shown in Figure 4, when the TOT is constructed by multiple time slots, similarly to Option 3, since multiple time slots are considered in the handling of conflict resolution, the processing delay is more likely to increase compared to Option 2. In addition, it may impose limitations on the terminal processing timeline.

[0047] The above explains Option 1, Option 2, and Option 3.

[0048] In Rel.15 / 16, for example, four RV positions (e.g., RV0, RV1, RV2, and RV3) are specified within the Circular Buffer, and the RV positions in the Circular Buffer are fixed positions regardless of the amount of allocated resources. When using the existing RV positions specified in Rel.15 / 16 and applying Option 1, Option 2, and Option 3, as mentioned above, there is a trade-off between decoding performance, processing latency, or the complexity of collision handling.

[0049] For example, as a method to maintain the time slot unit in Option 2 and suppress the degradation of decoding performance, one method to make the RV position variable can be listed (see, for example, Non-Patent Document 9 and Non-Patent Document 10).

[0050] Figure 5 illustrates an example of a rate matching method for Option 2 that applies a variable RV position (also known as "continuous RV" or "floating RV"). As shown in Figure 5, in Option 2 with a variable RV position, the terminal system can, for example, read the number of encoded bits that match the amount of resources to be allocated to each time slot via PUSCH from the variable RV position, and map the read encoded bits individually to the resources within the time slot.

[0051] Here, the terminal system can retain the number of encoded bits read in each time slot, and determine the RV position when to read encoded bits in the next time slot based on the number of encoded bits to be retained. For example, the RV position (e.g., the read start bit position on the Circular Buffer) sn in the nth time slot constituting the TOT is given by the following formula (1). sn = l n-1+1 (1)

[0052] Here, Ln-1 represents the last bit position on the Circular Buffer of the encoded bits read in the (n-1)th time slot. That is, the RV position sn of the nth time slot can be set to the next bit position after the last bit position on the nCircular Buffer of the encoded bits read in the (n-1)th time slot.

[0053] In Option 2, which employs a variable RV position, for example, even when performing rate matching at the slot level, the terminal can easily transmit consecutive bit columns on the Circular Buffer, suppressing the performance degradation described in Option 2. Furthermore, in Option 2, since the unit of rate matching can be a slot, it maintains slot-level processing similar to Option 2, and compared to Option 1 or Option 3, it offers advantages such as reduced processing latency and simplified conflict handling.

[0054] Here, for example, in Option 2 with a fixed RV position, since the RV position is fixed, if the terminal obtains information about the amount of PUSCH transmission resources to be allocated to the time slot for rate matching, it can start rate matching processing without being limited by the number of encoded bits read in the time slot preceding that time slot. In other words, in Option 2 with a fixed RV position, rate matching processing can begin in each of the plurality of time slots to be allocated to TBoMS without waiting for the rate matching processing of the previous time slot.

[0055] On the other hand, in Option 2 with a variable RV position, the RV position (the start bit position on the Circular Buffer) when reading encoded bits from the multiple time slots to be allocated to TBoMS depends on the rate matching result of the previous time slot (e.g., the number of encoded bits read or the last bit position). Therefore, in Option 2 with a variable RV position, the terminal starts the rate matching process for a time slot after specifically specifying the number of encoded bits read in a time slot preceding the time slot where rate matching is applied. In other words, the rate matching process for a time slot will not start until the number of encoded bits read in a time slot preceding the time slot where rate matching is applied is specifically specified.

[0056] Thus, in Option 2 with a variable RV position, the processing latency in the terminal is more likely to increase compared to Option 2 with a fixed RV position.

[0057] Furthermore, for example, in time slots preceding the time slots where rate matching is applied, the following situations may occur: TBoMS time zone resources conflict with the transmission resources of the PUSCH relative to the transmission UCI, causing the UCI to be multiplexed in the PUSCH resources; TBoMS time zone resources conflict with the resources indicated by the UL CI, causing the PUSCH to be dropped; or TBoMS time zone resources conflict with the allocation of high-priority uplink transmissions, causing the PUSCH to be dropped.

[0058] In such cases, when using Option 2 with a variable RV position, the RV position at the time of reading encoded bits in a time slot (e.g., the start position of the read on the Circular Buffer) may be affected by the multiplexing result of the UCI in a time slot earlier than that time slot, the abandonment of the PUSCH transmission due to the UL CI, or the abandonment of the PUSCH transmission due to the allocation of a high-priority uplink transmission. This is, for example, indicating that the RV position at the time of reading encoded bits from the Circular Buffer depends not only on the DCI to be allocated for the corresponding TBoMS, but also on the DCI to be allocated for the downlink data channel (e.g., PDSCH: Physical Downlink Shared Channel) corresponding to the multiplexed UCI, the DCI for transmitting the UL CI, or the DCI to be allocated for the high-priority uplink.

[0059] For example, when such DCI false detections occur at the terminal, inconsistencies may arise between the base station and the terminal regarding the RV position when reading encoded bits from the Circular Buffer. Therefore, decoding performance may be significantly degraded when such DCI false detections occur at the terminal. Alternatively, while blind decryption may be performed at the base station to account for DCI false detections at the terminal, this could complicate the base station's decoding process.

[0060] In a non-limiting embodiment disclosed herein, a method for transmitting uplink signals that suppresses the increase in processing latency in TBoMS and is robust to false detections of DCI is described.

[0061] For example, in one non-limiting embodiment of this disclosure, the degradation of decoding performance can be suppressed by applying the variable RV position to the rate matching process of the time slot unit in TBoMS. Furthermore, in another non-limiting embodiment of this disclosure, the variable RV position (the read start bit position on the Circular Buffer) in each time slot of TBoMS can be determined based on the number of encoded bits calculated from resources (e.g., referred to as "reference resource usage") that are not limited to the rate matching results of the time slots preceding that time slot. This suppresses the increase in processing latency in the terminal, and even when false detections occur in the terminal's DCI, it suppresses the degradation of decoding performance and avoids complicating the decoding process at the base station.

[0062] (Implementation Type 1) [Overview of Communication Systems] The communication systems of each embodiment disclosed herein are equipped with a base station 100 and a terminal 200.

[0063] Figure 6 is a block diagram showing a configuration example of a portion of a base station 100 (e.g., corresponding to a communication device) according to one embodiment of this disclosure. In the base station 100 shown in Figure 6, the control unit 101 (e.g., corresponding to a control circuit) determines the read position (e.g., RV position) of the encoded data of the signal in the first interval within a plurality of intervals (e.g., time slots) of the time area resources (e.g., TBoMS resources or resources within TOT) to be allocated for the transmission of a signal (e.g., PUSCH). The determination of the read position is based on the amount of resources (e.g., reference resources) that are not limited by the read results (e.g., rate matching results) of the encoded data in the second interval preceding the first interval. The receiving unit 108 (e.g., corresponding to a receiving circuit) receives the signal according to the read position.

[0064] Figure 7 is a block diagram showing an example of the configuration of a portion of a terminal 200 (e.g., a communication device) according to one embodiment of this disclosure. In the terminal 200 shown in Figure 7, the control unit 205 (e.g., a control circuit) determines the reading position of the encoded data of a signal in a first interval among a plurality of intervals within a time zone resource to be allocated for signal transmission. The determination of the reading position is based on the amount of resources available, not limited by the reading results of encoded data in a second interval preceding the first interval. The transmission unit 209 (e.g., a transmission circuit) transmits the signal according to the reading position.

[0065] [The Structure of the Base Bureau] Figure 8 is a block diagram showing an example of the configuration of the base station 100 in Embodiment 1. In Figure 8, the base station 100 includes a control unit 101, a host control signal generation unit 102, a downlink control information generation unit 103, an encoding unit 104, a modulation unit 105, a signal distribution unit 106, a transmission unit 107, a receiving unit 108, an extraction unit 109, a demodulation unit 110, and a decoding unit 111.

[0066] The control unit 101 determines, for example, information regarding the reception of downlink data signals (e.g., PUSCH) from the terminal 200 and information regarding the transmission of uplink data signals (e.g., PUSCH), and outputs the determined information to the upper-level control signal generation unit 102. The information regarding the reception of downlink data signals and the information regarding the transmission of uplink data signals may, for example, include information regarding time zone resource allocation (e.g., information regarding the TDRA form) or information regarding TBoMS (e.g., information regarding the number of transmission slots).

[0067] Furthermore, the control unit 101 determines, for example, information about downlink data signals, upper-level control signals, or downlink signals used to transmit downlink control information (e.g., encoding, modulation and coding scheme (MCS), and radio resource allocation), and outputs the determined information to the encoding unit 104, the modulation unit 105, and the signal allocation unit 106. Additionally, the control unit 101 outputs, for example, information about downlink signals (e.g., data signals or upper-level control signals) to the downlink control information generation unit 103.

[0068] Furthermore, the control unit 101 may, for example, determine information regarding the transmission of uplink data signals (e.g., PUSCH) in the terminal 200 (e.g., MCS and radio resource allocation). The control unit 101 may, for example, output the determined uplink data signal information to the downlink control information generation unit 103, extraction unit 109, demodulation unit 110, and decoding unit 111. Furthermore, the control unit 101 may, for example, determine at least one of the TBS in the TBoMS and the RV position of the plurality of time slots contained in the TBoMS according to the method described later, and output the determined information to the decoding unit 111.

[0069] The upper-level control signal generation unit 102 generates an upper-level control signal bit array based on information input from the control unit 101, and outputs the upper-level control signal bit array to the encoding unit 104.

[0070] The downlink control information generation unit 103 generates downlink control information (e.g., DCI) bit columns based on information input from the control unit 101, and outputs the generated DCI bit columns to the encoding unit 104. Additionally, control information may be transmitted to multiple terminals.

[0071] The encoding unit 104 encodes, for example, downlink data (e.g., DL data signal), a bit column input from the upper-level control signal generation unit 102, or a DCI bit column input from the downlink control information generation unit 103, based on information input from the control unit 101. The encoding unit 104 outputs the encoded bit column to the modulation unit 105.

[0072] The modulation unit 105 modulates the encoded bit column input from the encoding unit 104 based on the information input from the control unit 101, and outputs the modulated signal (e.g., the symbol column) to the signal distribution unit 106.

[0073] The signal distribution unit 106 maps the symbol array (e.g., containing downlink data signals or control signals) input from the modulation unit 105 to the radio resources, for example, based on the information on the displayed radio resources input from the control unit 101. The signal distribution unit 106 then outputs the downlink signal that has been mapped to the transmission unit 107.

[0074] The transmission unit 107 performs transmission waveform generation processing, such as orthogonal frequency division multiplexing (OFDM), on the signal input from the signal distribution unit 106. Furthermore, when performing OFDM transmission with an added cyclic prefix (CP), the transmission unit 107 performs inverse fast fourier transform (IFFT) processing on the signal and adds CP to the IFFT-generated signal. Additionally, the transmission unit 107 performs RF processing, such as D / A conversion or upconversion, on the signal and transmits the wireless signal to the terminal 200 via the antenna.

[0075] The receiving unit 108 performs RF processing such as downconverting or A / D conversion on the uplink signal received from the terminal 200 via the antenna. Furthermore, in the case of OFDM transmission, the receiving unit 108 performs Fast Fourier Transform (FFT) processing on the received signal and outputs the obtained frequency range signal to the extraction unit 109.

[0076] Extraction unit 109 extracts the radio resource portion that transmits uplink data signals (e.g., PUSCH) from the received signal input from receiving unit 108 based on information input from control unit 101, and outputs the extracted radio resource portion to demodulation unit 110.

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

[0078] The decoding unit 111 performs error correction decoding of the uplink data signal (e.g., PUSCH) based on information input from the control unit 101 and demodulation results input from the demodulation unit 110, to obtain the decoded received bit series (e.g., UL data signal).

[0079] [Terminal Components] Figure 9 is a block diagram showing a configuration example of a terminal 200 according to one embodiment of the present disclosure. For example, in Figure 9, the terminal 200 includes a receiving unit 201, an extraction unit 202, a demodulation unit 203, a decoding unit 204, a control unit 205, an encoding unit 206, a modulation unit 207, a signal distribution unit 208, and a transmission unit 209.

[0080] The receiving unit 201 receives downlink signals (e.g., downlink data signals or downlink control information) from the base station 100 via an antenna, and performs RF processing such as down-conversion or A / D conversion on the received wireless signal to obtain the received signal (baseband signal). Furthermore, when receiving an OFDM signal, the receiving unit 201 performs FFT processing on the received signal to convert it to a frequency range. The receiving unit 201 outputs the received signal to the extraction unit 202.

[0081] Extraction unit 202 extracts radio resource portions that may contain downlink control information from the received signal input from receiving unit 201, for example, based on radio resource information regarding downlink control information input from control unit 205, and outputs it to demodulation unit 203. Furthermore, extraction unit 202 extracts radio resource portions containing downlink data based on radio resource information regarding data signals input from control unit 205, and outputs it to demodulation unit 203.

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

[0083] The decoding unit 204 performs error correction decoding of the PDCCH or PDSCH based on information input from the control unit 205 and demodulation results input from the demodulation unit 203, to obtain, for example, downlink received signals, upper-layer control signals, or downlink control information. The decoding unit 204 outputs the upper-layer control signals and downlink control information to the control unit 205, and also outputs the downlink received signal. Furthermore, the decoding unit 204 can also generate a response signal (e.g., ACK / NACK) based on the decoding result of the downlink received data.

[0084] The control unit 205 determines, for example, the radio resources for at least one of PDSCH reception and PUSCH transmission based on signals input from the decoding unit 204 (e.g., upper-layer control signals or downlink control signals). The control unit 205 outputs the determined information to, for example, the extraction unit 202, the demodulation unit 203, the encoding unit 206, the modulation unit 207, and the signal distribution unit 208.

[0085] Furthermore, the control unit 205 determines, for example, the position of the TBS in the TBoMS and the RV position of the plurality of time slots contained in the TBoMS according to the method described later, and outputs the determined information to the encoding unit 206, the modulation unit 207 and the signal distribution unit 208.

[0086] The encoding unit 206 performs error correction decoding on the uplink data signal based on information input from the control unit 205, for example. The encoding unit 206 outputs the encoded bit sequence to the modulation unit 207.

[0087] The modulation unit 207 modulates the encoded bit column input from the encoding unit 206 based on the information input from the control unit 205, and outputs the modulated signal (symbol column) to the signal distribution unit 208.

[0088] The signal distribution unit 208 maps the signal input from the modulation unit 207 to radio resources, for example, based on information input from the control unit 205. The signal distribution unit 208 then outputs the mapped uplink signal to the transmission unit 209, for example.

[0089] The transmission unit 209 generates a transmission signal waveform, such as OFDM, for the signal input from the signal distribution unit 208. Furthermore, when using OFDM transmission with CP, the transmission unit 209 performs IFFT processing on the signal and appends CP to the IFFT-generated signal. Alternatively, when generating a single-carrier waveform, the transmission unit 209 may add a Discrete Fourier Transform (DFT) section (not shown) after the modulation unit 207 or before the signal distribution unit 208. Additionally, the transmission unit 209 performs RF processing such as D / A conversion and upconversion on the transmitted signal and transmits the wireless signal to the base station 100 via an antenna.

[0090] [Examples of operations by Base Station 100 and Terminal 200] Hereinafter, we will explain the operation of the base station 100 and terminal 200, which have the above configuration.

[0091] Figure 10 is a flowchart illustrating an example of the TBoMS transmission operation in the terminal 200.

[0092] <s101> In Figure 10, terminal 200 receives instructions from base station 100 regarding the PUSCH transmission performed by TBoMS (e.g., resource allocation information regarding TBoMS transmission).

[0093] <s102> Terminal 200, for example, determines a resource or resource quantity (hereinafter also referred to as "reference resource"), which is used to determine the RV position (read start bit position in the Circular Buffer) of each of the plurality of time slots contained in TBoMS.

[0094] The reference resource system can be, for example, the amount of resources that are not limited by the rate matching result (read result) of the encoded data in a time slot earlier than the time slot for rate matching. In other words, the reference resource system can be resources determined without considering the factors that may change between time slots. As an example, the reference resource system can be the amount of resources that are not limited by the presence or absence of UCI multiplexing. Alternatively, the reference resource system can be, for example, the amount of resources that are not limited by dynamic SFI notification, UL CI, or whether the PUSCH transmission was abandoned due to the allocation of high-priority uplink transmissions.

[0095] For example, the reference resource can also be the amount of resources (e.g., the number of REs) to be allocated to PUSCH transmission in the preceding time slot within the TOT. As an example, the amount of the reference resource (e.g., referred to as the "reference resource amount") NRE can be calculated according to the following formula (2) or formula (3).

[0096] In equation (2), the upper limit of the number of REs in the time slot is set to, for example, 156. Alternatively, the upper limit of the number of REs in the time slot may not be limited to 156 and may be other values.

[0097] In equations (2) and (3), nPRB refers to the number of resource blocks (e.g., PRB: Physical Resource Block) to be allocated to TBoMS transmission. Furthermore, in equations (2) and (3), N'RE can be calculated, for example, by the following equation (4). Here, Number of subcarriers per resource block (e.g., 12). : The number of OFDM symbols to be allocated to the PUSCH transmission of the preceding slot within the TOT. : The number of REs to be allocated to the PUSCH transmission of the DMRS in the preceding slot within the TOT. The RRC notifies the terminal 200 of the overhead factor.

[0098] For example, the number of OFDM symbols to be allocated to the PUSCH transmission of the preceding time slot within the TOT can be notified to the terminal 200 using information about the symbol length of the Time Zone Resource Allocation (TDRA).

[0099] <s103> Terminal 200 series, for example, determines (e.g. calculates) the number of coded bits corresponding to the reference resource (hereinafter also referred to as "reference coded bits").

[0100] The reference code bit number Nref corresponding to the reference resource can also be calculated, for example, using the reference resource amount NRE calculated via equation (2) or equation (3), according to the following equation (5). N ref = N RE .Q m .υ (5) Here, Qm: Modulation multivalues. υ: Number of MIMO layers.

[0101] <s104> Terminal 200 series, for example, determines the RV position (e.g., variable RV position) in each time slot based on the reference code bit number and the time slot index (e.g., "n") of each time slot contained in TBoMS (or TOT).

[0102] For example, the RV position (read start bit position on the Circular Buffer) in the front time slot of the terminal 200 series can be set to an existing RV position (such as any one of RV0, RV1, RV2, RV3) as specified in Rel.15 / 16.

[0103] Furthermore, the terminal 200 system can, for example, determine the RV position in a time slot that is later than the preceding one in the TOT based on the reference code bit number Nref and the time slot index n of that time slot in the TOT. For example, the RV position Sn in the nth time slot (e.g., time slot index n) constituting the TOT can be given by the following equation (6).

[0104] Here, NRVx refers to the RV position used in the leading slot within the TOT (e.g., the bit position specified by RV0, RV1, RV2, or RV3).

[0105] Thus, the terminal 200 system determines the RV position of each time slot based on the reference code bit number Nref corresponding to the reference resource and the index of the time slot. In other words, the terminal 200 system does not determine the RV position of each time slot based on the rate matching result in the time slot preceding the current time slot.

[0106] <s105> Terminal 200 can also perform rate matching in each time slot based on the determined RV position. For example, terminal 200 reads the reference code bits corresponding to the reference resource (e.g., the number of bits corresponding to the amount of resource to be allocated to the PUSCH transmission of the preceding time slot in the TOT) from the RV position (variable RV position) determined for each time slot, and maps the read code bits to the PUSCH resource of each time slot.

[0107] <s106> Terminal 200 series, for example, transmits PUSCH via TBoMS.

[0108] The above provides an example of the TBoMS transmission operation in terminal 200.

[0109] Thus, in this embodiment, the terminal 200 series, for example, is not limited by the rate matching result of the time slots preceding the current time slot, but uniquely determines the RV position of each time slot within the TOT (e.g., the read start bit position on the Circular Buffer).

[0110] Figure 11 is a diagram showing an example of a TBoMS using rate matching in this embodiment. In Figure 11, as an example, the TBoMS contains four time slots and one TOT (e.g., four time slots).

[0111] As shown in Figure 11, the terminal 200 series, for example, can set the RV position (read start bit position on the Circular Buffer) s0 in the preceding time slot in the TOT to the existing RV position specified in Rel.15 / 16 (RV0 in Figure 11).

[0112] Furthermore, in Figure 11, the terminal 200 system can, for example, set the resources to be allocated to PUSCH in the preceding time slots within the TOT as reference resources. As mentioned above, the reference resources can, for example, be a resource quantity not limited by the presence or absence of UCI multiplexing. Moreover, the terminal 200 system can, for example, determine the RV positions s1, s2, and s3 in the nth time slot according to Equation (6), based on the reference resources (e.g., the number of reference code bits Nref) and the time slot index n within the TOT (e.g., n = any one of 1, 2, or 3).

[0113] Here, for example, as shown in Figure 11(a), the last bit position on the Circular Buffer of the read code bit in the preceding time slot without UCI multitasking, as shown in Figure 11(b), can be different from the last bit position on the Circular Buffer of the read code bit in the preceding time slot with UCI multitasking.

[0114] In contrast, as mentioned above, in Figure 11, the allocation of PUSCH resources in the preceding time slot within the TOT by the terminal 200 determines the RV position of the time slot following the preceding time slot based on reference resources not limited by UCI multiplexing. Therefore, as shown in Figures 11(a) and 11(b), even if the last bit position on the Circular Buffer of the read encoded bits in the preceding time slot (in other words, the Rate matching result) is different, the terminal 200 uniquely determines the RV positions s1, s2, and s3 in the time slot following the preceding time slot, regardless of the presence or absence of UCI multiplexing.

[0115] Therefore, the terminal 200 system can start the rate matching process for each time slot without waiting for the rate matching result of the previous time slot, thus suppressing the increase of processing delay in the terminal 200.

[0116] Furthermore, for example, in the method for determining the RV position according to Equation (1), the last bit position Ln-1 on the Circular Buffer of the read encoded bits in the previous time slot can vary depending on the presence or absence of UCI multiplexing within the PUSCH resource. In contrast, in the method for determining the RV position according to Equation (6), the RV position of each time slot is determined based on a reference resource that is not limited by UCI multiplexing and is not affected by the presence or absence of UCI multiplexing. Therefore, in this embodiment, for example, the RV position of each time slot is not limited by the DCI of the PDSCH corresponding to the multi-site transmission of UCI. Therefore, the terminal 200 can perform PUSCH transmission with robustness against false detection of the DCI.

[0117] In addition, in this embodiment, the terminal 200 series, for example, can decide whether to actually transmit the PUSCH of each time slot in the uplink time slot that can be used in TBoMS, according to the PUSCH dropping specification.

[0118] The terminal 200 series can, for example, count time slots that are determined not to actually transmit PUSCH (discarded PUSCH transmission) as time slots constituting the TOT. In other words, the time slot index n within the TOT can be attached to each of the time slots constituting the TOT regardless of whether PUSCH transmission is discarded.

[0119] For example, in the PUSCH obsolescence specification, when the time resource allocation within the PUSCH transmission time slot conflicts with the downlink symbol set by dynamic SFI notification, when the time resource allocation within the PUSCH transmission time slot conflicts with the resources indicated by UL CI, or when the time resource allocation within the PUSCH transmission time slot conflicts with the allocation of a high-priority uplink transmission, the terminal 200 can decide not to transmit the PUSCH (e.g., obsolescence of the PUSCH transmission) in the time slot where the conflict occurs. In this embodiment, for example, the terminal 200 can also count time slots that do not transmit PUSCH (time slots where PUSCH transmission is obsolescence) as time slots constituting the TOT.

[0120] Figure 12 illustrates an example of a TBoMS using rate matching in this embodiment. In Figure 12, as an example, the TBoMS contains four time slots, and the number of TOTs is one (e.g., four time slots). As shown in Figure 12, the terminal 200 can, for example, when deciding to discard a PUSCH transmission in the third time slot within a TOT, set a time slot index of n=0 to 3 for the four time slots within the TOT containing the third time slot. In other words, the terminal 200 also counts the third time slot where the PUSCH transmission is discarded as a time slot constituting the TOT.

[0121] Terminal 200 uses the above method to determine the RV position (read start bit position on the Circular Buffer) in each of the first time slot in the TOT and the nth time slot (e.g., n is an integer greater than 1) that constitutes the TOT.

[0122] Alternatively, the terminal 200 system can, for example, implement a process to discard the PUSCH transmission by simply setting the encoded transmission to RF off. For example, in the example of Figure 12, the terminal 200 can also perform RF off in a time slot of n=2.

[0123] In addition, the base station 100 system can, for example, determine the RV position of each time slot in the TBoMS of the terminal 200 based on reference resources (such as the allocation resources of the front time slots in the TOT) in the same way as the terminal 200, and perform the reception processing of the signal transmitted from the terminal 200 to the TBoMS based on the determined RV position.

[0124] The above provides an example of the actions of base station 100 and terminal 200.

[0125] According to this embodiment, the base station 100 and the terminal 200, for example, determine the RV position in a certain time slot within the time zone resources to be allocated to TBoMS based on a reference resource that is not limited by the rate matching results in time slots earlier than that time slot.

[0126] Therefore, according to this embodiment, in TBoMS, the variable RV position can be applied to the rate matching processing of the time slot unit, thus improving decoding performance in the same way as Option 2 mentioned above. Furthermore, according to this embodiment, in TBoMS, by using the rate matching processing of the time slot unit, the increase in processing latency in the terminal 200 can be suppressed.

[0127] Furthermore, in this embodiment, the RV position (read start bit position on the Circular Buffer) of each time slot is not affected by the presence or absence of dynamic SFI notification, UL CI, or high-priority uplink transmission allocation. Therefore, in this embodiment, the RV position of each time slot is not limited by dynamic SFI notification, UL CI, or DCI corresponding to the allocation of high-priority uplink transmission. Therefore, the method for determining the RV position in this embodiment is robust against false detections of DCI.

[0128] Furthermore, for example, since the RV position is set regardless of the presence or absence of DCI false detection, inconsistencies in the RV position when reading encoded bits from the Circular Buffer between the base station 100 and the terminal 200 are less likely to occur. Therefore, for example, in the base station 100, decoding processing that takes into account DCI false detection in the terminal 200 can be omitted. Thus, according to this embodiment, the complexity of decoding processing in the base station 100 can be suppressed.

[0129] In summary, this implementation can improve communication efficiency in the uplink.

[0130] (Implementation Type 2) The configuration of the base station and terminal in this embodiment can be the same as that of the base station 100 and terminal 200 in embodiment 1.

[0131] In this embodiment, the terminal 200 series can, for example, in the uplink time slots that can be used in TBoMS, decide whether to actually transmit the PUSCH of each time slot according to the PUSCH obsolescence specification, just like in embodiment 1.

[0132] Furthermore, in this embodiment, for example, the terminal 200 does not count the time slots determined not to transmit PUSCH (abandoned PUSCH transmission) as time slots constituting the TOT. In other words, the time slot index n within the TOT can be attached to a time slot that is different from the time slot where PUSCH transmission is abandoned, for example, to each of the time slots where PUSCH transmission is performed.

[0133] Figure 13 illustrates an example of a TBoMS using rate matching in this embodiment. In Figure 13, as an example, the TBoMS contains 4 time slots and 1 TOT (e.g., 4 time slots). As shown in Figure 13, the terminal 200 can, for example, when deciding to discard a PUSCH transmission in the third time slot within a TOT, set a time slot index of n=0 to 2 for the other three time slots within the TOT that are different from the third time slot. In other words, the terminal 200 does not count the third time slot, where the PUSCH transmission was discarded, as a time slot constituting the TOT.

[0134] The terminal 200 series can, for example, determine the variable RV position (read start bit position on the Circular Buffer) in each time slot of TBoMS based on the reference code bit number Nref corresponding to the reference resource and the time slot index n within the TOT. Furthermore, as mentioned above, the time slot index n is the index of the actual PUSCH transmission time slot within the TOT, excluding time slots where PUSCH transmission is abandoned.

[0135] Furthermore, the reference resource system can be, for example, the same as in Implementation 1, a resource amount not limited to the rate matching result (read result) of encoded data in a time slot preceding the rate matching time slot. For example, the reference resource system can be a resource amount not limited to the presence or absence of UCI multiplexing. Alternatively, the reference resource system can be, for example, a resource amount not limited to dynamic SFI notification, UL CI, or whether PUSCH transmission was abandoned due to the allocation of high-priority uplink transmissions.

[0136] For example, the reference resource can also be the amount of resources (REs) to be allocated to PUSCH transmission in the first time slot of the TOT. For example, the reference code bit number Nref calculated based on the reference resource can be determined according to equation (5).

[0137] Terminal 200, for example, in the nth time slot within the TOT, reads a number of encoded bits that correspond to the amount of resources to be allocated to the PUSCH transmission in that time slot from the RV position Sn given according to the reference encoded bit number Nref and the time slot index n within the TOT, and maps the read encoded bits to the PUSCH resources in the nth time slot. For example, the RV position Sn in the nth PUSCH transmission within the TOT (e.g., time slot index n) can be given by the following equation (7).

[0138] Here, NRVx refers to the RV position (e.g., the bit position specified by RV0, RV1, RV2 or RV3) used in the preceding PUSCH transmission within TOT.

[0139] For example, in the example shown in Figure 13, the terminal 200 system can, for example, set the RV position (read start bit position on the Circular Buffer) s0 in the previous PUSCH transmission (e.g., the time slot n=0) in the TOT to the existing RV position (RV0 in Figure 13) specified in Rel. 15 / 16.

[0140] Furthermore, in Figure 13, the terminal 200 system can, for example, set the resources to be allocated to the PUSCH in the preceding PUSCH transmission within the TOT as reference resources. The reference resources can be, similar to Embodiment 1, for example, a resource quantity not limited by UCI multiplexing. Moreover, the terminal 200 system can, for example, determine the RV positions s1 and s2 in the nth time slot according to Equation (7), based on the reference resources (e.g., the number of reference code bits Nref) and the time slot index n within the TOT (e.g., either n=1 or 2).

[0141] According to this embodiment, similar to Embodiment 1, since the variable RV position can be applied to the rate matching processing of time slot units in TBoMS, decoding performance can be improved in the same way as Option 2 described above, and the increase in processing latency in the terminal 200 can be suppressed. Furthermore, in this embodiment, the RV position of each time slot is not affected by the presence or absence of dynamic SFI notifications, ULCI, or high-priority uplink transmission allocations, and is not limited by the corresponding DCI. Therefore, similar to Embodiment 1, the method for determining the RV position is robust against DCI false detection. Moreover, for example, since the RV position is set regardless of the presence or absence of DCI false detection, inconsistencies in the RV position when reading encoded bits from the Circular Buffer between the base station 100 and the terminal 200 are less likely to occur. Furthermore, in the base station 100, decoding processing considering DCI false detection in the terminal 200 can be omitted. Therefore, the complexity of decoding processing in the base station 100 can be suppressed.

[0142] Furthermore, in this embodiment, the terminal 200 determines the RV position based on the number of reference encoded bits corresponding to the reference resource quantity and the slot index of the slot that is different from the slot where PUSCH transmission was abandoned in the plurality of slots within the TOT (or TBoMS). Therefore, even when PUSCH is not transmitted in at least one slot within the TOT (PUSCH transmission is abandoned), encoded bits stored in the Circular Buffer can be continuously read in the plurality of slots within the TOT where PUSCH is to be transmitted, thus preventing degradation of decoding performance.

[0143] For example, Figure 12 shows an example where the PUSCH transmission in the third time slot is abandoned in Embodiment 1, and Figure 13 shows an example where the PUSCH transmission in the third time slot is abandoned in Embodiment 2. For example, in Figure 12, because the PUSCH transmission in the third time slot is abandoned, the terminal 200 will not transmit the encoded bits read from RV position s2. In contrast, for example, in Figure 13, even when the PUSCH transmission in the third time slot is abandoned, the terminal 200 will still transmit the encoded bits read from RV position s2 in the PUSCH transmission of the fourth time slot. Thus, according to this embodiment, the encoded bits stored in the Circular Buffer are transmitted without omission via TBoMS transmission, thereby preventing degradation of decoding performance.

[0144] (Implementation Type 3) The configuration of the base station and terminal in this embodiment can be the same as that of the base station 100 and terminal 200 in embodiment 1.

[0145] In TBoMS, in order to efficiently utilize uplink resources, a transmission method was reviewed that allows PUSCH transmission in the slot to proceed even if at least one symbol in the PUSCH resources (e.g., symbols) in the slot is unusable for PUSCH transmission, provided that a certain number of symbols are available for PUSCH transmission.

[0146] Here, at least one symbol in the PUSCH resources to be allocated is a symbol that cannot be used for PUSCH transmission, and a number of time slots containing symbols that can be used for PUSCH transmission are called "Special slots".

[0147] Figure 14 illustrates an example assuming the PUSCH leading symbol position S=0 within a time slot, the number of transmitted PUSCH symbols L=14, and the TBoMS time slot number is set, with a Special slot (e.g., time slot #1) included in a portion of consecutive time slots (e.g., time slots #0, #1, #2, and #3). In Figure 14, the portion indicated by "U" represents the PUSCH resources (symbols) actually transmitted. Furthermore, in Figure 14, the portion indicated by "D" represents the resources for downlink signal transmission, and the portion indicated by "F" represents resources that can be transmitted by both downlink and uplink signals (e.g., flexible symbols).

[0148] Furthermore, for ease of explanation, slots that are not Special slots will be referred to as "ordinary slots" below. Ordinary slots, such as slots #0, #2, and #3 as shown in Figure 14, are slots in which the symbols constituting the slots can be used for PUSCH transmission.

[0149] For example, by using the uplink symbols contained in the Special slot to transmit PUSCH through the terminal 200, it is expected to improve the utilization efficiency of uplink resources and improve the coverage performance of PUSCH.

[0150] In this embodiment, the method of determining the reference resource (e.g., the calculation method) differs depending on whether the leading time slot in the TOT is a Special slot.

[0151] The following describes three methods for calculating reference resources.

[0152] Method 1 In Method 1, the reference resource can be, for example, the amount of resources (e.g., the number of REs) to be allocated to the PUSCH transmission of the preceding time slot within the TOT, multiplied by a scaling factor (e.g., denoted as "K") larger than 1. Furthermore, the resources to be allocated to the preceding time slot within the TOT using the reference resource can be resources that do not consider UCI multiplexing.

[0153] Here, the scaling factor K can vary depending on whether the preceding time slot in the TOT is a special slot. For example, when the preceding time slot in the TOT is not a special slot (it is a normal time slot), K can be set to 1. On the other hand, for example, when the preceding time slot in the TOT is a special slot, K can be set to > 1.

[0154] For example, the reference resource quantity NRE system can be calculated using the method shown in equation (8). N RE =KN RE,0 (8)

[0155] Here, NRE,0 indicates the amount of resources (e.g., number of REs) to be allocated to the PUSCH transfer of the preceding time slot within the TOT given by equation (2) or (3).

[0156] According to Method 1, even when the preceding time slot in the TOT is a Special slot, the same amount of resources as a normal time slot can be set as the reference resource amount.

[0157] Alternatively, the scaling factor K may not be multiplied by the non-reference resource quantity NRE,0, but rather by the number of coded bits (reference coded bits) Nref calculated based on the reference resource.

[0158] Method 2 In Method 1, for example, the time slot that serves as the basis for calculating the reference resource quantity is not limited to whether the preceding time slot of the TOT is a Special slot, but is the preceding time slot within the TOT. In Method 2, for example, the time slot that serves as the basis for calculating the reference resource quantity can be the initial ordinary time slot within the TOT.

[0159] For example, when the preceding time slot in a TOT is a regular time slot, the time slot that serves as the basis for calculating the reference resource quantity can be the preceding time slot. On the other hand, when the preceding time slot in a TOT is a special slot, the time slot that serves as the basis for calculating the reference resource quantity can be a regular time slot that is different from the preceding time slot in the TOT (e.g., the initial regular time slot).

[0160] According to method 2, the terminal 200 can calculate the reference resource quantity based on the ordinary time slot without being limited by the setting of the special slot within the TOT. Therefore, according to method 2, for example, as shown in method 1, the scaling factor can be adjusted without depending on whether the preceding time slot within the TOT is a special slot, thus simplifying the processing of the terminal 200.

[0161] Method 3 For example, in TBoMS, as one of the methods for notifying information about time zone resource allocation, there is also a method that notifies multiple terminals 200 of information about the position of the leading symbol of the PUSCH in the time slot and the number of symbols of the transmitted PUSCH (e.g., SLIV: Start symbol and allocation Length Indicator Value).

[0162] Methods for notifying multiple SLIVs, such as listing individual SLIVs within each slot of TBoMS, or notifying different SLIVs between ordinary slots and special slots.

[0163] In method 3, when multiple SLIVs are notified in this manner by information related to the time zone resource allocation of the terminal 200 (e.g., also known as TDMA entry), the time slot that serves as the basis for calculating the reference resource quantity can be set to the time slot with the largest symbol length (L) among the multiple SLIVs that have been notified.

[0164] For example, in method 3, when different SLIVs are notified between a normal time slot and a special slot, the terminal 200 system can set the resource of the time slot that is notified to correspond to the SLIV of the normal time slot as the reference resource.

[0165] The above has explained three methods for calculating reference resources.

[0166] In addition, in this embodiment, the terminal 200 system can determine the RV position (read start bit position on the Circular Buffer) of the nth time slot in the TOT according to Equation (6) in the same way as in embodiment 1, and can also determine it according to Equation (7) in the same way as in embodiment 2.

[0167] According to this embodiment, even when ordinary time slots and special slots coexist in the TOT, the parameters used to determine the RV position of each time slot are two parameters corresponding to the reference code bit number of the reference resource and the time slot index, thus having the advantage of simplifying the processing of the terminal 200.

[0168] In addition, in this embodiment, the setting of the time slot index n can be the same as in embodiment 1 or the same as in embodiment 2.

[0169] (Implementation Type 4) The configuration of the base station and terminal in this embodiment can be the same as that of the base station 100 and terminal 200 in embodiment 1.

[0170] For example, in TBoMS, in order to improve the efficiency of uplink resource utilization, as shown in Figure 15, there may be a situation where the PUSCH resources to be allocated to TBoMS in different time slots within TOT are different.

[0171] In this embodiment, the terminal 200 series can calculate the reference resource based on the number of PUSCH symbols (e.g., denoted as "Lref"). The number of PUSCH symbols (the base value of the number of symbols) Lref can be, for example, the number of symbols constituting the time slot (Lref=14), or other values.

[0172] In addition, the terminal 200 can also determine the variable RV position (read start bit position on the Circular Buffer) in each time slot of TBoMS, for example, based on the reference code bit number Nref corresponding to the reference resource, the time slot index n in the TOT, and the ratio of the actual number of PUSCH symbols used for each time slot to the number of PUSCH symbols that serve as the reference (for example, denoted as "γ").

[0173] In addition, in this embodiment, the setting of the time slot index n can be the same as in embodiment 1 or the same as in embodiment 2.

[0174] Furthermore, the reference resource can be the amount of resource not limited to the rate matching result (read result) of the encoded data in a time slot preceding the time slot for rate matching. For example, the reference resource can be the amount of resource not limited to the presence or absence of UCI multiplexing. Alternatively, the reference resource can also be, for example, the amount of resource not limited to dynamic SFI notification, UL CI, or whether the PUSCH transmission was abandoned due to the allocation of high-priority uplink transmissions.

[0175] For example, the reference resource system can be the amount of resources (e.g., the number of REs) to be allocated to the PUSCH transmission of the reference PUSCH symbol number (e.g., Lref=14). As an example, the reference resource number NRE system can be calculated according to the following equation (9) or equation (10).

[0176] In equation (9), the upper limit of the number of REs in the time slot is set to, for example, 156. Alternatively, the upper limit of the number of REs in the time slot may not be limited to 156 and may be other values.

[0177] In equations (9) and (10), nPRB refers to the number of resource blocks (e.g., the number of PRBs) to be allocated to TBoMS transmission. Furthermore, in equations (9) and (10), N'RE can be calculated, for example, according to equation (11). Here, Number of subcarriers per resource block (e.g., 12). L ref : The number of PUSCH symbols used as the reference (e.g., 14). : The number of REs to be allocated to the PUSCH transmission of the DMRS in the preceding slot within the TOT. The execution time factor is communicated to terminal 200 via RRC.

[0178] Furthermore, the reference code bit number Nref corresponding to the reference resource can be calculated using the reference resource quantity NRE calculated by equation (9) or equation (10), according to the following equation (12). N ref =N RE .Q m .υ (12) Here, Qm: Modulation multivalues. υ: Number of MIMO layers.

[0179] Furthermore, the ratio γ of the actual number of PUSCH symbols used in each time slot to the reference number of PUSCH symbols is given by the ratio Ln / Lref of the actual number of PUSCH symbols in the nth time slot to the reference number of PUSCH symbols Lref. For example, in the example shown in Figure 15, when Lref=14, γ0 can be set as L0 / Lref=14 / 14=1, γ1=L1 / Lref=4 / 14=2 / 7, and γ2 can be set as L2 / Lref=12 / 14=6 / 7.

[0180] For example, in the nth time slot within the TOT, the terminal 200 reads the coded bits corresponding to the amount of PUSCH transmission to be allocated to that time slot from the RV position Sn given by the reference coded bit number Nref corresponding to the reference resource, the time slot index n within the TOT, and the ratio γ, and maps the read coded bits to the PUSCH resource in the nth time slot.

[0181] For example, the RV position Sn in the nth time slot of the TOT can be given by the following formula (13).

[0182] Here, NRVx refers to the RV position used in the leading slot within the TOT (e.g., the bit position specified by RV0, RV1, RV2, or RV3).

[0183] According to this embodiment, the terminal 200 determines the RV position in each of the plurality of time slots within the TOT based on the ratio γ of the number of symbols used for PUSCH transmission in each time slot to the number of PUSCH symbols used as a reference. By using the ratio γ, the number of reference coding bits Nref corresponding to the reference resource can be adjusted according to the amount of PUSCH transmission resources to be allocated to each time slot (i.e., the ratio of the number of PUSCH symbols used as a reference to the number of PUSCH symbols in each time slot), thereby improving the accuracy of rate matching in each time slot and improving decoding performance.

[0184] (Implementation Type 5) The configuration of the base station and terminal in this embodiment can be the same as that of the base station 100 and terminal 200 in embodiment 1.

[0185] In this embodiment, similar to embodiment 4, as shown in Figure 15, the description addresses the case where the PUSCH resources to be allocated to TBoMS in different time slots within TOT are not the same.

[0186] For example, in embodiments 1 to 4, a method is described for setting reference resources for a plurality of time slots within the TOT and determining the RV position of each of the plurality of time slots within the TOT based on the reference resources.

[0187] In this embodiment, for example, a method is described for individually setting reference resources in multiple time slots within a TOT, and determining the RV position of each time slot based on the reference resources of each of the multiple time slots within the TOT.

[0188] For example, the terminal 200 series can determine the variable RV position (read start bit position on the Circular Buffer) in the nth time slot of TBoMS based on the reference code bit number calculated based on the reference resource of the time slot (e.g., denoted as "NRE,n") and the time slot index n in the TOT.

[0189] In addition, in this embodiment, the setting of the time slot index n can be the same as in embodiment 1 or the same as in embodiment 2.

[0190] For example, the reference resource in the nth time slot within the TOT can be the amount of resources (e.g., the number of REs) to be allocated to the pUSCH transmission in the nth time slot without considering UCI multiplexing. As an example, the reference resource NRE,n in the nth time slot within the TOT can be calculated according to the following equation (14) or equation (15).

[0191] In equation (14), the upper limit of the number of REs in the time slot is set to, for example, 156. Alternatively, the upper limit of the number of REs in the time slot may not be limited to 156 and may be other values.

[0192] In equations (14) and (15), nPRB refers to the number of resource blocks (e.g., the number of PRBs) to be allocated to TBoMS transmission. Furthermore, in equations (14) and (15), N'RE can be calculated, for example, according to equation (16). Here, Number of subcarriers per resource block (e.g., 12). : The number of OFDM symbols to be allocated to the PUSCH transmission of the nth time slot within the TOT. : The number of REs for DMRS to be allocated to the PUSCH transmission of the nth time slot within the TOT. The RRC notifies the terminal 200 of its load factor.

[0193] Furthermore, in the nth time slot within the TOT, the reference code bit number Nref(n) corresponding to the reference resource can be calculated, for example, using the reference resource amount NRE,n calculated by equation (14) or equation (15), according to the following equation (17). N ref (n)=N RE、n .Q m .υ (17) Here, Q m: The number of modulated values. υ: Number of MIMO layers.

[0194] For example, in the nth time slot within the TOT, the terminal 200 reads the code bits that correspond to the amount of PUSCH transmission to be allocated to that time slot from the reference code bit number Nref(n) of the reference resource corresponding to the nth time slot and the RV position Sn given by the time slot index n within the TOT, and maps the read code bits to the PUSCH resource in the nth time slot.

[0195] For example, the RV position Sn in the nth time slot of the TOT can be given by the following formula (18).

[0196] Here, NRVx refers to the RV position used in the leading slot within the TOT (e.g., the bit position specified by RV0, RV1, RV2, or RV3).

[0197] According to this embodiment, the terminal 200 system individually sets the reference resources in multiple time slots within the TOT. By individually setting the reference resources, the terminal 200 system can, for example, map the encoded bits to the resources in the time slots according to the amount of resources to be allocated to each time slot for PUSCH transmission (i.e., the amount of resources to be allocated to each time slot for PUSCH transmission), thereby improving the accuracy of rate matching in each time slot and improving decoding performance.

[0198] In this embodiment, since the reference resources are individually set in each time slot, the reference resources (or the number of reference code bits) can be different between time slots, for example, depending on the different settings of DMRS between time slots. Therefore, compared with the method of embodiment 4 (using the ratio of the number of PUSCH symbols used as a reference to the actual number of PUSCH symbols in each time slot), the accuracy of rate matching can be further improved.

[0199] Furthermore, according to this embodiment, for example, the parameters used to determine the RV position of each time slot are two parameters corresponding to the reference code bit number of the reference resource of each time slot which is not limited by UCI multiplexing, and the time slot index, thus having the advantage of simplifying the processing of the terminal 200.

[0200] (Implementation Type 6) The configuration of the base station and terminal in this embodiment can be the same as that of the base station 100 and terminal 200 in embodiment 1.

[0201] In summary, the time region resources to be allocated to TBoMS can be constructed using a plurality of TOTs. In this embodiment, when the time region resources to be allocated to TBoMS are constructed using a plurality of TOTs, the RV position (read start bit position on the Circular Buffer) of the preceding time slot of each TOT can be determined by any of the following methods.

[0202] Method 1 In Method 1, the RV position (read start bit position on the Circular Buffer) in the preceding slot within TOT can be a specified RV position (e.g., the read start bit position on the Circular Buffer specified by RV0, RV1, RV2 or RV3).

[0203] For example, the terminal 200 series can determine the RV position of the PUSCH to be transmitted in the preceding time slot of each TOT in TBoMS based on the RV field contained in the DCI. For example, when scheduling the transmission of TBoMS using the DCI format containing a two-bit RV field, the RV to be applied to the preceding time slot of the m-th TOT can also be set as shown in Figure 16.

[0204] For example, in Figure 16, when the RV field of the two-bit terminal displays "2", the terminal 200 system can sequentially set the RV position in the preceding time slot of the preceding TOT in the TBoMS to RV2, RV3, RV1, and RV0. Other values ​​of the RV field shown in Figure 16 can also be set in the same way. Furthermore, the RV position applied to the preceding time slot of multiple TOTs is not limited to the example shown in Figure 16.

[0205] According to method 1, since the RV position of the leading time slot in each of the plurality of TOTs within TBoMS is set to a predetermined RV position, the processing of the terminal 200 can be simplified. Furthermore, for example, as shown in FIG16, the RV position of the leading time slot in each of the plurality of TOTs is set to all predetermined RV positions within the Circular Buffer, making it easier to transmit all encoded bits stored in the Circular Buffer and improving decoding performance.

[0206] Method 2 In Method 2, the RV position (read start bit position on the Circular Buffer) in the preceding time slot within the TOT can be set to variable. For example, the RV position of the preceding time slot within the TOT can be determined based on a reference resource (e.g., the number of reference encoded bits).

[0207] For example, the RV position Sm,0 in the slot before the m-th TOT (e.g., n=0) can be given by the following equation (19). Here, : The RV position used in the front timing slot within the front TOT (e.g., the bit position specified by RV0, RV1, RV2 or RV3). The number of time slots contained in TOT. N ref : Number of reference encoding bits.

[0208] In addition, Equation (19) is an example when the number of time slots contained in each TOT is the same.

[0209] When the number of time slots contained in each TOT is set individually (e.g., when they may be different), the RV position Sm,0 in the preceding time slot of the m-th TOT can be given by the following formula (20). Here, : The number of time slots contained in the m-th TOT.

[0210] According to method 2, since the RV position of the leading slot in each of the multiple TOTs in TBoMS can be set to be variable according to the amount of resources (e.g., reference resources) in each TOT, the encoded bits stored in the Circular Buffer can be read continuously, thus improving decoding performance.

[0211] The various embodiments of one of the present disclosures have been described above.

[0212] (Variation Example 1) In TBoMS, for example, TBS can be calculated using the following methods.

[0213] The TBS system can be determined by multiplying the TBS calculated from the amount of resources (e.g., number of symbols or number of REs) to be allocated to the PUSCH transmission of the preceding time slot within the TOT by a scaling factor greater than 1. For example, the amount of resources (number of REs) to be allocated to the PUSCH transmission of the preceding time slot NRE system can be calculated according to the following formula (21).

[0214] In equation (21), the upper limit of the number of REs in the time slot is set to, for example, 156. Alternatively, the upper limit of the number of REs in the time slot may not be limited to 156 and may be other values.

[0215] In equation (21), nPRB refers to the number of resource blocks (e.g., PRBs) to be allocated to the PUSCH transfer. Furthermore, in equation (21), N'RE can be calculated, for example, according to equation (22). Here, Number of subcarriers per resource block (e.g., 12). : The number of OFDM symbols to be allocated to the PUSCH transmission of the preceding time slot. : The number of REs to be allocated to the PUSCH transmission of the preceding time slot for DMRS. The RRC notifies the terminal 200 of its load factor.

[0216] For example, the OFDM symbol number to be allocated to the PUSCH transmission of the preceding time slot can be notified to the terminal 200 by information about the symbol length of the Time Zone Resource Allocation (TDRA).

[0217] The TB size Ninfo can be calculated using the reference resource amount NRE to be allocated to the PUSCH transmission of the preceding time slot calculated by equation (21), for example, according to the following equation (23). N info = N RE .RQ m .υ.K (23) Here, R: Coding rate. Qm: Modulation multivalues. υ: Number of MIMO layers. K: A scaling factor greater than 1.

[0218] Terminal 200, for example, can use the value calculated in TBS transmitted in PUSCH in the calculation of the reference code bits (Nref) corresponding to the RV position of each time slot within TOT when determining the reference resource quantity. For example, the calculation of the reference resource quantity (e.g., the reference code bits) in the above embodiments can use at least one of NRE in equation (21) and N'RE in equation (22) calculated in TBS.

[0219] By using the values ​​calculated for TBS for the calculation of reference resources, the processing power or memory usage in terminal 200 can be reduced.

[0220] In summary, the variations have been explained.

[0221] In addition, in a non-limiting embodiment disclosed herein, the reference resource is not limited to the resource set according to the preceding time slot or the initial ordinary time slot in the TOT, but can also be set according to the resource of any time slot in the TOT.

[0222] Furthermore, in a non-limiting embodiment disclosed herein, although the processing of Option 2 (rate matching for time slot units) with variable RV position has been described, it is not limited to this; for example, the processing of Option 3 (rate matching for TOT units) with variable RV position can also be performed. In this case, for example, the processing of time slot units and parameters that are independent of or common to time slots in the above embodiments can also be read as the processing of TOT units and parameters that are independent of or common to TOT.

[0223] Furthermore, in a non-limiting embodiment disclosed herein, TOT can also be defined as a unit of TBoMS transmission (Single TBoMS). Additionally, repetition of TBoMS transmissions of multiple TBoMS units can also be applied. In this case, for example, TOT in the above embodiment can also be read as a unit of TBoMS transmission (Single TBoMS).

[0224] Furthermore, in a non-limiting embodiment disclosed herein, the reference coding bit count may also be the bit count after deducting the filler bits of the LDPC symbol. For example, in equation (18) above, when the i-th time slot constituting the TOT contains filler bits, the RV position Sn of the n-th time slot constituting the TOT can be given by the following equation (24). Here, τ(i) represents the number of filler bits in the i-th time slot.

[0225] Furthermore, in a non-limiting embodiment disclosed herein, the RV position can be calculated using a Modulo calculus modulo the size or length of the Circular Buffer Ncb. For example, in equation (18) above, the RV position Sn in the nth time slot constituting the TOT can be given by equation (25).

[0226] Furthermore, in a non-limiting embodiment disclosed herein, the PUSCH resources available for PUSCH transmission are not limited to including uplink symbols (U), but may also include flexible symbols (F).

[0227] Furthermore, in a non-limiting embodiment disclosed herein, although TBoMS transmission has been described as an example of PUSCH transmission using multiple time slots, PUSCH transmission using multiple time slots is not limited to TBoMS transmission and may also be other transmission methods. Moreover, transmission using multiple time slots is not limited to PUSCH transmission and may also be the transmission of other channels or signals.

[0228] In one non-limiting embodiment disclosed herein, for example, the communication device for transmitting data is not limited to terminal 200, but may also be base station 100. Similarly, the communication device for receiving data is not limited to base station 100, but may also be terminal 200. In other words, each embodiment or variation is not limited to uplink transmission, but may also be applied to downlink transmission or sidelink transmission.

[0229] The embodiments, variations, and methods in each embodiment disclosed herein are not limited and can be switched, and the communication methods (types) or types of channels / signals can be individually different.

[0230] Furthermore, the name of the information element or the name of the parameter set in the information element used in the non-limiting embodiment disclosed herein is an example, and may be other names. In addition, the values ​​of parameters such as the number of time slots constituting the TBoMS, the number of time slots constituting the TOT, the number of TOTs contained in the TBoMS, the number of symbols in the time slots, the setting of the time slot category (e.g., "D", "U" or "F") in the TOT, and the specified number of RV positions, as illustrated in each embodiment or variation, are an example, and may be other values.

[0231] Furthermore, the designation "...part" in the above-mentioned implementations can also be replaced with other designations such as "...circuitry", "...device", "...unit", or "...module".

[0232] (Replenish) Information indicating whether the terminal 200 supports the functions, actions, or processing shown in the above-mentioned implementation types and variations can also be transmitted from the terminal 200 to (or notified to) the base station 100, for example, as capability information or capability parameters of the terminal 200.

[0233] The capability information may include information elements (IEs) indicating whether the individual display terminal 200 supports at least one of the functions, actions, or processes shown in the above-described embodiments and variations. Alternatively, the capability information may include information elements indicating whether the display terminal 200 supports any two or more combinations of the functions, actions, or processes shown in the above-described embodiments and variations.

[0234] Base station 100 can, for example, determine (or decide or envision) the functions, actions, or processes supported (or not supported) by the source terminal 200, based on capability information received from terminal 200. Base station 100 can then implement actions, processes, or controls consistent with the determination results based on the capability information. For example, base station 100 can control TBoMS transmission based on the capability information received from terminal 200.

[0235] Furthermore, the statement that terminal 200 does not support a portion of the functions, actions, or processes described in the aforementioned implementations and variations can also be interpreted as meaning that such a portion of the functions, actions, or processes in terminal 200 are restricted. For example, information or requests regarding such restrictions can also be notified to base station 100.

[0236] Information regarding the capabilities or limitations of terminal 200 may be defined in the specifications, or may be implicitly communicated to base station 100 by associating it with known information or information to be transmitted to base station 100.

[0237] (Control signal) In this disclosure, the downlink control signal (information) can be a signal (information) transmitted by the physical layer PDCCH, or a signal (information) transmitted by the upper layer MAC CE (Control Element) or RRC. Furthermore, the downlink control signal can be set to a predefined signal (information).

[0238] The uplink control signals (information) disclosed herein can be signals (information) transmitted by the physical PUCCH, or signals (information) transmitted by the upper-level MAC CE or RRC. Furthermore, the uplink control signals can be set to predefined signals (information). Additionally, the uplink control signals can also be replaced with UCI (Uplink Control Information), 1st stage SCI (Sidelink Control Information), and 2nd stage SCI.

[0239] (Base Bureau) In this disclosure, a base station can be a TRP (Transmission Reception Point), cluster head, access point, RRH (Remote Radio Head), eNodeB (eNB), gNodeB (gNB), BS (Base Station), BTS (Base Transceiver Station), host, gateway, etc. Furthermore, in sidelink communication, a terminal can act as a base station. A base station can also be a relay device for communication between a relay host node and a terminal. Additionally, a base station can also be a roadside unit.

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

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

[0242] (Data Channel / Control Channel) This disclosure can be applied to either the data channel or the control channel. For example, the channels disclosed herein can also be replaced with PDSCH, PUSCH, PSSCH of the data channel, and PDCCH, PUCCH, PBCH, PSCCH, PSBCH of the control channel.

[0243] (Reference signal) In this disclosure, the reference signal is a known signal on both the base station and the terminal, sometimes referred to as the RS (reference signal) or pilot signal. The reference signal can 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), or SRS (Sounding Reference Signal).

[0244] (Time interval) In this disclosure, the unit of time resource is not limited to one or a combination of time slots and symbols, but may also be a time resource unit such as a frame, super frame, subframe, time slot, mini time slot, or symbol, OFDM (Orthogonal Frequency Division Multiplexing) symbol, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbol, or other time resource units. Furthermore, the number of symbols contained in a time slot is not limited to the number of symbols exemplified in the above embodiments, but may also be other numbers of symbols.

[0245] (Frequency band domain) This disclosure may also be applied to either licensed bands or unlicensed bands.

[0246] (communication) This disclosure can also be applied to any of the following: communication between base station and terminal (Uu link communication), communication between terminals (Sidelink communication), and V2X (Vehicle to Everything) communication. For example, the channels disclosed herein can also be replaced with PSCCH, PSSCH, PSFCH (Physical Sidelink Feedback Channel), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.

[0247] Furthermore, this disclosure can also be applied to any of the following: terrestrial networks, satellite networks, or high-altitude pseudo-satellite (HAPS) networks (NTN: Non-Terrestrial Network). Additionally, this disclosure can also be applied to terrestrial networks with larger cell sizes, ultra-wideband transmission networks, etc., where the transmission delay is greater than the symbol length or time slot length.

[0248] (Antenna port) An antenna port refers to a logical antenna (antenna group) consisting of one or more physical antennas. That is, an antenna port does not necessarily refer to a single physical antenna; it can also refer to an array antenna composed of multiple antennas. For example, an antenna port is not specified as consisting of a certain number of physical antennas, but is defined as the smallest unit that a terminal can transmit a reference signal. Furthermore, an antenna port is sometimes also defined as the smallest unit for performing weighted multiplication operations on precoding vectors.

[0249] <5G NR System Architecture and Protocol Stack> 3GPP continues to work toward the next release of fifth-generation mobile phone technology (5G), which includes new radio access technology operating in the frequency range up to 100 GHz. The initial version of the 5G specification was completed at the end of 2017, which has enabled the trial and commercial development of terminals (such as smartphones) that comply with the 5G NR specification.

[0250] For example, the overall system architecture assumes that the entire system has a gNB-RAN (Next Generation Radio Access Network). The gNB is a UE-side terminal that provides NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols. The gNBs are interconnected via the Xn interface. In addition, the gNBs are connected to the NGC (Next Generation Core) via the next-generation (NG) interface, and more specifically, to the AMF (Access and Mobility Management Function) (e.g., the core entity that performs the specific designation of the AMF) via the NG-C interface. Furthermore, they are connected to the UPF (User Plane Function) (e.g., the core entity that performs the specific designation of the UPF) via the NG-U interface. Figure 17 shows the NG-RAN architecture (e.g., refer to 3GPP TS 38.300 v15.6.0, section 4).

[0251] The user plane protocol stack for NR (e.g., refer to 3GPP TS 38.300, section 4.4.1) includes the PDCP (Packet Data Convergence Protocol) sublayer (refer to section 6.4 of TS 38.300), RLC (Radio Link Control) sublayer (refer to section 6.3 of TS 38.300), and MAC (Medium Access Control) sublayer (refer to section 6.2 of TS 38.300) sublayer, which form the terminal on the network side in the gNB. Furthermore, a new Access Stratum sublayer (SDAP: Service Data Adaptation Protocol) is introduced on top of PDCP (e.g., refer to section 6.5 of 3GPP TS 38.300). Additionally, the control plane protocol stack is defined for NR use (e.g., refer to TS 38.300, section 4.4.2). A summary of the functions of Layer 2 is described in the TS. In Section 6 of TS 38.300, the functions of the PDCP sublayer, RLC sublayer, and MAC sublayer are listed in Sections 6.4, 6.3, and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in Section 7 of TS 38.300.

[0252] For example, the Medium-Access-Control layer handles multiplexing of logical channels and scheduling and scheduling-related functions for various parameter sets (numerologies).

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

[0254] NR use cases / deployment scenarios, from the perspective of data rate, latency, and coverage, may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communication (mMTC) with various requirements. For example, eMBB is expected to support peak data rates (20Gbps in downlink and 10Gbps in uplink) and user-experienced data rates that are approximately three times higher than those provided by IMT-Advanced. On the other hand, in the case of URLLC, more stringent requirements are imposed on ultra-low latency (0.5ms for both UL and DL regarding the user plane) and high reliability (1-10-5 within 1ms). Finally, in mMTC, the preferred approach is to require high connection density (1,000,000 devices / km2 in urban environments), wide coverage in harsh environments, and extremely long-life batteries (15 years) for low-cost devices.

[0255] Therefore, a parameter set for OFDM suitable for one use case (e.g., subcarrier spacing, OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) may be invalid in other use cases. For example, in low latency services, it is preferable to require a shorter symbol length than in mMTC services (therefore, a larger subcarrier spacing) and / or fewer symbols per scheduling interval (TTI) than in mMTC services. Furthermore, in scenarios with larger channel delays, it is preferable to require a longer CP length than in scenarios with shorter delays. The subcarrier spacing can be optimized to maintain the same CP load. NR supports more than one subcarrier spacing value. Currently, subcarrier spacings of 15kHz, 30kHz, 60kHz, etc., have been considered for this purpose. The symbol length Tu and the subcarrier spacing Δf can be directly related using the formula Δf = 1 / Tu. Similar to the LTE system, the term "resource element" can be used to refer to the smallest resource unit consisting of a subcarrier, which is the length of one OFDM / SC-FDMA symbol.

[0256] In the new 5G-NR wireless system, the resource grid for each parameter set and each carrier, subcarrier, and OFDM symbol number is defined for both uplink and downlink. Each element of the resource grid is called a resource element, which is specifically specified according to the frequency index of the frequency region and the symbol position of the time region (refer to 3GPP TS 38.211 v15.6.0).

[0257] Functional Separation Between NG-RAN and 5GC in 5G NR Figure 18 shows the functional separation between NG-RAN and 5GC. NG-RAN's logical nodes are either gNB or ng-eNB. 5GC has logical nodes AMF, UPF, and SMF.

[0258] For example, gNB and ng-eNB systems integrate the following main functions: - Functions of radio resource management, including radio bearer control, radio admission control, connection mobility control, and dynamic allocation (scheduling) of resources for the UE in both uplink and downlink; - Data IP header compression, encryption, and security protection; - When the UE cannot determine the routing for the AMF based on the information provided by the UE, the selection of the AMF during UE attachment; - Routing of user plane data toward UPF; - Routing of control plane information toward AMF; - Setting up and disconnecting the connection; - Scheduling and delivery of paging messages; -Scheduling and transmission of system notification information (sourced from AMF or Operation Admission Maintenance (OAM) functions); -Settings for measurements and measurement reports used for mobility and scheduling; - Packet marking at the port level in the uplink; -Session management; - Support for network slicing; - Management of QoS traffic and matching of data wireless carriers; - Support for UEs in RRC_INACTIVE state; - NAS message sending function; - Sharing of wireless access networks; - Dual connectivity; -Close collaboration between NR and E-UTRA.

[0259] The Access and Mobility Management Function (AMF) is responsible for the following main functions. - Enables Non-Access Stratum (NAS) signaling to form a terminal; -Security of NAS signals; -Security controls for the Access Stratum (AS); - Core Network (CN) inter-node signaling for mobility between 3GPP access networks; - The possibility of a UE reaching idle mode (including control and execution of paging retransmission); -Management of the login area; -Support for intra-system and inter-system mobility; -Access authentication; - Access approval including checks on roaming permissions; - Mobility management controls (joining and policies); - Support for network slicing; -Selection of Session Management Function (SMF).

[0260] Furthermore, the User Plane Function (UPF) is responsible for the following main functions. - Anchor points for intra-RAT mobility / inter-RAT mobility (where applicable); - External PDU (Protocol Data Unit) dialogue points for interconnection with data networks; - Packet routing and forwarding; - Policy rule enforcement for packet inspection and user plane part; - Reporting of traffic usage; - Uplink classifier for supporting routing of traffic flows in the data network; - Branching Point for supporting multi-homed PDU sessions; - QoS handling for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement); - Verification of uplink traffic (mapping of SDFs to QoS flows); - Buffer for downlink packets and trigger function for downlink data notification.

[0261] Finally, the Session Management Function (SMF) is in charge of the following main functions. - Session management; - Allocation and management of IP addresses for the UE; - Selection and control of UPF; - Configuration function for traffic steering in the user plane function (UPF) for routing traffic to the appropriate destination; - Enforcement of control part policies and QoS; - Notification of downlink data.

[0262] <Procedures for setting up and reconfiguring RRC connections> Figure 19 shows several handovers between the UE, gNB, and AMF (5GC entities) when the UE in the NAS part transitions from RRC_IDLE to RRC_CONNECTED (refer to TS 38.300 v15.6.***).

[0263] RRC is a higher-level signaling (protocol) used for UE and gNB configuration. Through this transfer, the AMF prepares UE context data (which includes, for example, PDU dialogue context, security keys, UE radio capabilities, and UE security capabilities) and transmits it to the gNB along with the initial context setting request. Furthermore, the gNB, together with the UE, enables AS security. This is done by the gNB sending a SecurityModeCommand message to the UE, and the UE responding with a SecurityModeComplete message. Afterwards, the gNB sends an RRCReconfiguration message to the UE, and the gNB receives an RRCReconfigurationComplete from the UE, thereby reconfiguring the Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). Regarding connections with only signaling, the steps regarding RRCReconfiguration are omitted since SRB2 and DRB are not configured. Finally, the gNB system notifies the AMF that the setup procedure is complete by responding with an Initial Context Setup Request.

[0264] Therefore, this disclosure provides an entity of a 5th Generation Core (5GC) (e.g., AMF, SMF, etc.), which includes: a control circuit that establishes a Next Generation (NG) connection with the gNodeB during operation; and a transmission unit that, when operating in a manner that sets the signaling radio carrier between the gNodeB and the User Equipment (UE), transmits initial context setting information to the gNodeB via the NG connection. Specifically, the gNodeB transmits Radio Resource Control (RRC) signals containing resource allocation setting information elements (IEs) to the UE via the signaling radio carrier. Furthermore, the UE performs uplink transmission or downlink reception according to the resource allocation settings.

[0265] <Use Scenarios of IMT after 2020> Figure 20 shows several use cases for NR. The 3rd generation partnership project new radio (3GPP NR) reviews three use cases supporting various services and applications through the IMT-2020 vision. Planning for the first phase of specifications for enhanced mobile-broadband (eMBB) has been completed. Current and future work includes expanding eMBB support, as well as standardization for ultra-reliable low-latency communications (URLLC) and massive machine-type communications (mMTC). Figure 20 shows several examples of use cases for IMT after 2020 (see, for example, Figure 2 of ITU-R M.2083).

[0266] URLLC use cases have stringent performance requirements regarding throughput, latency, and availability. URLLC use cases are envisioned as a key technology for future applications such as wireless control of industrial production processes or manufacturing steps, remote medical surgery, automation of power transmission and distribution in smart grids, and traffic safety. URLLC's ultra-high reliability is supported by technologies specifically designed to meet the requirements set by TR 38.913. In the NR URLLC of release 15, a target user plane latency of 0.5ms for the uplink (UL) and 0.5ms for the downlink (DL) is included as an important requirement. For the overall URLLC requirements of a single packet transmission, when the user plane latency is 1ms, the block error rate (BLER) is 1E-5 relative to a 32-byte packet size.

[0267] From a physical layer perspective, reliability can be improved in many ways. Current potential for reliability improvement includes defining individual CQI tables for URLLCs, a more streamlined DCI format, and PDCCH redundancy. However, this potential will expand further as NR (a crucial component of NR URLLCs) becomes more stable and developed, in order to achieve ultra-high reliability. Specific use cases for NR URLLCs in release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0268] Furthermore, the technical enhancements targeted at NR URLLC focus on improving latency and reliability. Latency enhancements include configurable parameter sets, non-slot-based scheduling with flexible mapping, grant-free uplinks, time slot repetition in data channels, and preemption on the downlink. Preemption refers to stopping a transmission for which resources have been allocated, using those resources for other transmissions with lower latency / higher priority than subsequent requests. Thus, a granted transmission is replaced by a subsequent transmission. Preemption can be applied regardless of the specific service type. For example, a transmission in service type A (URLLC) can be replaced by a transmission in service type B (eMBB, etc.). Reliability enhancements include a dedicated CQI / MCS table for the target BLER of 1E-5.

[0269] The typical use case of mMTC (massive machine-type communication) involves a large number of connected devices transmitting relatively small amounts of data that are less susceptible to latency. These devices are required to be inexpensive and have extremely long battery life. From an NR (Radio Frequency Identification) perspective, utilizing a very narrow bandwidth is one solution that, from a UE (User Equipment) perspective, can save power and extend battery life.

[0270] In summary, the scope for improving reliability in NR is expected to become wider. One of the important requirements for all cases, such as those related to URLLC and mMTC, is high reliability or ultra-high reliability. Several mechanisms can improve reliability from both a wireless and a network perspective. Overall, there are two to three important areas that may contribute to improving reliability. In these areas, there is diversity regarding streamlined control channel information, repetition of data channels / control channels, and frequency, time, and / or space domains. These areas can be generally applied to improving reliability without being limited to specific communication scenarios.

[0271] Regarding NR URLLC, further use cases with more stringent requirements, such as those in factory automation, transportation, and power distribution, are envisioned. By "stringent requirements," we mean high reliability (reliability up to the 10-6 level), high availability, packet size up to 256 bits, and time synchronization up to about a few μs (depending on the use case, set to 1 μs or a few μs by setting the value to the frequency range and a short waiting time of about 0.5 ms to 1 ms, e.g., a waiting time of 0.5 ms for the target user plane).

[0272] Furthermore, regarding NR URLLC, from a physical layer perspective, there may be several technical enhancements. Among these technical enhancements, there are enhancements to the PDCCH (Physical Downlink Control Channel) regarding streamlined DCI, repetition of the PDCCH, and increased monitoring of the PDCCH. In addition, enhancements to the UCI (Uplink control Channel) are related to enhancements of enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback. In addition, there may be enhancements to the PUSCH related to hopping at the mini-slot level and enhancements to retransmission / repetition. The term "mini-slot" refers to a Transmission Time Interval (TTI) that contains fewer symbols than a slot (a slot has 14 symbols).

[0273] ​The 5G QoS (Quality of Service) model is based on QoS flows, supporting both QoS flows requiring a guaranteed flow bit rate (GBR) and QoS flows not requiring a guaranteed flow bit rate (non-GBR QoS flows). Therefore, in the NAS (Network Address Translation) level, QoS traffic represents the finest granularity of QoS distinction within a PDU (Programmable Utility) conversation. QoS flows are specifically specified within the PDU conversation via the NG-U interface using the QoS Flow ID (QFI) carried in the encapsulation header.

[0274] For each UE, the 5GC establishes one or more PDU conversations. For each UE, in conjunction with the PDU conversation, the NG-RAN establishes at least one Data Radio Bearer (DRB) as shown above, for example, with reference to Figure 19. Furthermore, additional DRBs for QoS traffic can be configured for this PDU conversation later (when to configure them depends on the NG-RAN). The NG-RAN maps packets belonging to various PDU conversations to various DRBs. The NAS-level packet filters in the UE and 5GC associate UL packets, DL packets, and QoS flows; correspondingly, the AS-level mapping rules in the UE and NG-RAN associate UL QoS flows, DL QoS flows, and DRBs.

[0275] Figure 21 illustrates the non-roaming reference architecture for 5G NR (refer to TS 23.501 v16.1.0, paragraph 4.23). Application Functions (AFs) (such as the external application servers responsible for 5G services illustrated in Figure 20) are authorized to the 3GPP core network to provide services. For example, access to the Network Exposure Function (NEF) is granted to support applications that impact traffic routing, or access to the policy framework (refer to the Policy Control Function (PCF)) is granted for policy control (e.g., QoS control). Depending on the operator's setup, Application Functions trusted by the operator can be directly authorized to the relevant Network Functions. Application Functions not authorized by the operator to directly access Network Functions exchange information with the relevant Network Functions via the NEF using an externally accessible architecture.

[0276] Figure 21 further illustrates the functional units of the 5G architecture, namely the 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, such as operator services, internet access, or third-party services). All or part of the core network functions and application services can also be deployed and operate in a cloud computing environment.

[0277] Therefore, this disclosure provides an application server (e.g., an AF in a 5G architecture) comprising: a transmission unit that, in order to establish a PDU dialogue between a gNodeB and a UE containing radio carriers conforming to QoS requirements, transmits, during operation, at least one of the functions of the 5GC (e.g., NEF, AMF, SMF, PCF, UPF, etc.) containing QoS requirements for at least one of URLLC service, eMMB service, and mMTC service; and a control circuit that, during operation, performs services using the established PDU dialogue.

[0278] This disclosure can be implemented using software, hardware, or software that works in conjunction with hardware. The functional blocks used in the above embodiments are implemented, partially or entirely, using an LSI (Liquid Crystal Sensor) belonging to integrated circuits. The processes described in the above embodiments can be controlled, partially or entirely, by a single LSI or a combination of LSIs. An LSI can be constructed from individual chips, or it can be a single chip containing part or all of the functional blocks. An LSI can have data input and output capabilities. Depending on its integration level, an LSI is also referred to as an IC, system LSI, super LSI, or ultra LSI (Very Large Scale Integrated Circuit).

[0279] The method of integrated circuitization is not limited to LSI; it can also be implemented using dedicated circuits, general-purpose processors, or special-purpose processors. Furthermore, after LSI fabrication, a programmable FPGA (Field Programmable Gate Array) or a reconfigurable processor that can reconfigure the connections or settings of the internal circuitry of the LSI can be used. This disclosure can be implemented in digital or analog processing form.

[0280] Furthermore, if advancements in semiconductor technology or other derived technologies lead to the development of integrated circuitry that replaces LSIs, this technology can certainly be used for the integration of functional blocks. It is also possible that this technology could be applied to biotechnology and other fields.

[0281] This disclosure can be implemented in all kinds of devices, apparatuses, and systems with communication capabilities (collectively referred to as communication devices). A communication device may include a wireless transceiver and processing / control circuitry. A wireless transceiver may include a receiving unit, a transmitting unit, or both functionally. The wireless transceiver (transmitting unit, receiving unit) may include an RF (Radio Frequency) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or similar devices. As non-limiting examples of communication devices, the following can be listed: telephones (mobile phones, smartphones, etc.), tablets, personal computers (PCs) (laptops, desktops, notebooks, etc.), cameras (digital still / video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, digital book readers, telehealth, telemedicines (remote health care, drug prescription) devices, vehicles or mobile transportation vehicles with communication functions (cars, airplanes, ships, etc.), and combinations of the above-mentioned devices.

[0282] Communication devices are not limited to those that can be moved or transported, but also include all kinds of devices, components, and systems that cannot be moved or fixed, such as smart home devices (home appliances, lighting machines, smart meters or measuring machines, control panels, etc.), vending machines, and all other "things" that may exist on the IoT (Internet of Things) network.

[0283] In addition to data communication conducted by cellular systems, wireless LAN systems, and communication satellite systems, communication also includes data communication composed of combinations of these.

[0284] Furthermore, the communication device also includes devices such as controllers or sensors that are connected or linked to the communication device performing the communication function as described in this disclosure. For example, a controller or sensor may generate control signals or data signals used by the communication device that performs the communication function of the communication device.

[0285] Furthermore, the communication device includes infrastructure equipment for communicating with or controlling the various non-limited devices mentioned above, such as base stations, access points, and other devices, components, and systems.

[0286] The communication device according to one embodiment of the present disclosure includes: a control circuit that determines the reading position of the encoded data of the aforementioned signal in a first interval of a plurality of intervals within a time region resource to be allocated for the transmission of the signal, wherein the determination of the reading position is based on the amount of resources not limited by the reading result of the encoded data in a second interval preceding the first interval; and a transmission circuit that transmits the aforementioned signal according to the reading position.

[0287] In one embodiment disclosed herein, the aforementioned resource quantity is a resource quantity that is not limited by the presence or absence of uplink control information multiplexing.

[0288] In one embodiment of this disclosure, the aforementioned resource quantity is a resource quantity that is not limited by whether the transmission of the aforementioned signal has been abandoned.

[0289] In one embodiment of this disclosure, the aforementioned control circuit determines the aforementioned read position based on the number of encoded bits corresponding to the aforementioned resource quantity and the index of the aforementioned first interval among the aforementioned plurality of intervals.

[0290] In one embodiment of this disclosure, the aforementioned control circuit determines the aforementioned read position based on the number of encoded bits corresponding to the aforementioned resource quantity and the index of the aforementioned first interval among the aforementioned plurality of intervals that are different from the interval where the transmission of the aforementioned signal was abandoned.

[0291] In one embodiment of this disclosure, the aforementioned control circuit determines the amount of resources differently depending on whether the interval preceding the aforementioned time region resource is a special time slot.

[0292] In one embodiment of this disclosure, the aforementioned control circuit determines the aforementioned read position in each of the aforementioned plurality of intervals based on the ratio of the number of symbols used in the transmission of the aforementioned signal in each of the aforementioned plurality of intervals to a reference value about the number of symbols.

[0293] In one embodiment of this disclosure, the aforementioned control circuit individually sets the aforementioned resource quantity within the aforementioned plurality of intervals.

[0294] In one embodiment of this disclosure, the aforementioned time zone resource includes at least a group consisting of one or a plurality of consecutive intervals, and the aforementioned reading position in the preceding interval within the aforementioned group is a defined position.

[0295] In one embodiment of this disclosure, the aforementioned time zone resource includes at least a group consisting of one or a plurality of consecutive intervals, and the aforementioned read position in the preceding interval within the aforementioned group is determined according to the aforementioned resource quantity.

[0296] In one embodiment of this disclosure, the aforementioned control circuit uses the value already calculated for the transmission block size of the aforementioned signal in the calculation of the aforementioned resource quantity.

[0297] The communication device according to one embodiment of the present disclosure includes: a control circuit that determines the reading position of the encoded data of the aforementioned signal in a first interval of a plurality of intervals within a time region resource to be allocated for the transmission of the signal, wherein the determination of the reading position is based on the amount of resources not limited by the reading result of the encoded data in a second interval preceding the first interval; and a transmission circuit that transmits the aforementioned signal according to the reading position.

[0298] In a communication method according to one embodiment of the present disclosure, the communication device determines the reading position of the encoded data of the aforementioned signal in the first interval of a plurality of intervals within the time zone resources to be allocated for signal transmission. The determination of the reading position is based on the amount of resources not limited by the reading result of the encoded data in the second interval preceding the first interval, and the communication device transmits the aforementioned signal according to the reading position.

[0299] In a communication method according to one embodiment of the present disclosure, a communication device determines the reading position of the encoded data of the aforementioned signal in a first interval among a plurality of intervals within a time region resource to be allocated for signal transmission. The determination of the reading position is based on the amount of resources not limited by the reading result of the encoded data in a second interval preceding the first interval, and the communication device receives the aforementioned signal according to the reading position.

[0300] The contents of the specification, drawings and abstract contained in Japanese Application No. 2021-126687, filed on August 2, 2021, are all incorporated herein by reference. [Industry availability]

[0301] One embodiment disclosed herein is extremely useful for wireless communication systems.

[0302] 100: Base Bureau 101,205: Control Department 102: Upper-level control signal generation unit 103: Downlink Control Information Generation Department 104,206: Coding Department 105,207: Modulation Unit 106, 208: Signal Distribution Section 107,209: Teleportation Department 108,201: Receiving Section 109,202: Extraction section 110,203: Demodulation Department 111,204: Decoding Department 200: Terminal < / option>

Claims

1. A terminal, comprising: The circuit, in operation, determines the start bit position of the read encoded data on the circular buffer in the first time slot based on the start bit position of the read encoded data on the circular buffer in the second time slot, which is a time slot preceding the first time slot, and the number of encoded bits in the second time slot available for transmitting the aforementioned encoded data. The first and second time slots are one of a plurality of time slots within the time region resources to be allocated for signal transmission. The transmitter, in operation, transmits the aforementioned signal based on the aforementioned start bit position of the read encoded data in the first time slot. The determination of the number of encoded bits in the second time slot available for transmitting the aforementioned encoded data is not limited by the presence or absence of uplink control information (UCI) multiplexing in the second time slot.

2. The terminal as described in claim 1, wherein, The aforementioned second time slot is the first position time slot among the aforementioned plurality of time slots, and the aforementioned second time slot contains the aforementioned encoded data at the position of the aforementioned read start bit, which is indicated by the redundant version 0, 1, 2 or 3.

3. The terminal as described in claim 1, wherein, The size of the aforementioned signal transmission block is calculated by multiplying the amount of resources to be allocated to the aforementioned data transmission slot by a scaling factor.

4. The terminal as described in claim 3, wherein, The aforementioned resource quantity for the aforementioned time slot is determined based on information related to the symbol length, and this information is indicated by the base station.

5. The terminal as described in claim 1, wherein, Information related to the aforementioned plurality of time slots is instructed from the base station.

6. The terminal as described in claim 1, wherein, The aforementioned signals are transmitted on the Physical Uplink Shared Channel (PUSCH).

7. A base station, comprising: The circuit, in operation, determines the start bit position of the read encoded data on the circular buffer in the first time slot based on the start bit position of the read encoded data on the circular buffer in the second time slot, which is a time slot preceding the first time slot, and the number of encoded bits in the second time slot available for transmitting the aforementioned encoded data. The first and second time slots are one of a plurality of time slots within the time region resources to be allocated for signal transmission. The receiver, in operation, receives the aforementioned signal based on the aforementioned start bit position of the read encoded data in the first time slot. The determination of the number of encoded bits in the second time slot available for transmitting the aforementioned encoded data is not limited by the presence or absence of uplink control information (UCI) multiplexing in the second time slot.

8. The base station as described in claim 7, wherein, The aforementioned second time slot is the first position time slot among the aforementioned plurality of time slots, and the aforementioned second time slot contains the aforementioned encoded data at the position of the aforementioned read start bit, which is indicated by the redundant version 0, 1, 2 or 3.

9. The base station as described in claim 7, wherein, The size of the aforementioned signal transmission block is calculated by multiplying the amount of resources to be allocated to the aforementioned data transmission slot by a scaling factor.

10. The base station as described in claim 9, wherein, The aforementioned resource quantity for the aforementioned time slot is determined based on information related to the symbol length, and this information is indicated by the base station.

11. The base station as described in claim 7, wherein, Information related to the aforementioned plurality of time slots is instructed from the base station.

12. The base station as described in claim 7, wherein, The aforementioned signals are transmitted on the Physical Uplink Shared Channel (PUSCH).

13. A communication method, comprising: The starting bit position for reading the encoded data on the circular buffer in the second time slot, which is an earlier time slot than the first time slot, is determined based on the starting bit position for reading the encoded data on the circular buffer in the first time slot and the number of encoded bits in the second time slot available for transmitting the encoded data. The first and second time slots are one of a plurality of time slots to be allocated within the time region resources for signal transmission. The signal is transmitted based on the starting bit position for reading the encoded data in the first time slot. The determination of the number of encoded bits in the second time slot available for transmitting the encoded data is not limited by the presence or absence of uplink control information (UCI) multiplexing in the second time slot.

Images