Communication device and communication method

Abstract

A communication device includes: control circuitry that decides, based on an amount of resources that does not depend on a reading result of coded data in a second interval that is earlier than a first interval among a plurality of intervals within a time-domain resource allocated to a signal transmission, a reading position of the coded data of the signal in the first interval; and transmission circuitry that transmits the signal based on the reading position.

Description

[0001] This application is a divisional application of Chinese invention patent application filed on May 6, 2022, with application number 202280050022.1, entitled "Communication Device and Communication Method", and filed by Panasonic Corporation (USA). Technical Field

[0002] This disclosure relates to communication devices and communication methods. Background Technology

[0003] In recent years, against the backdrop of the expansion and diversification of wireless services, the rapid development of the Internet of Things (IoT) is anticipated. The application of mobile communication is expanding beyond information terminals such as smartphones to all areas, including vehicles, homes, home appliances, and industrial equipment. To support this service diversification, in addition to increasing system capacity, significant improvements in the performance and functionality of mobile communication systems are required to meet various necessary conditions 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-reliable and low-latency communication (URLLC), and can flexibly provide wireless communication according to a variety of needs.

[0004] The 3rd Generation Partnership Project (3GPP), an international standards organization, is developing specifications for New Radio (NR), one of the wireless interfaces for 5G.

[0005] Existing technical documents

[0006] Non-patent literature

[0007] Non-patent document 1: 3GPP TS38.104 V15.14.0, “NR Base Station (BS) radiotransmission and reception (Release 15)”, June 2021.

[0008] Non-patent literature 2: 3GPP TSG RAN Meeting #90e, RP-202928, “New WID on NRcoverage enhancements,” China Telecom, December 2020.

[0009] Non-patent document 3: 3GPP TS38.211 V16.6.0, “NR Physical channels and modulation (Release 16)”, June 2021.

[0010] Non-patent document 4: 3GPP TS38.212 V16.6.0, “NR Multiplexing and channel coding (Release 16)”, June 2021.

[0011] Non-patent literature 5: 3GPP TS38.213 V16.6.0, “NR Physical layer procedures for control (Release 16)”, June 2021.

[0012] Non-patent document 6: 3GPP TS38.214 V16.6.0, “NR Physical layer procedures for data (Release 16)”, June 2021.

[0013] Non-patent document 7: 3GPP TS38.331 V16.5.0, “NR Radio Resource Control (RRC) protocol specification (Release 16)”, June 2021.

[0014] Non-patent literature 8: 3GPP TSG RAN WG1 #105-e, R1-2106251, “Final FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2),” Moderator (Nokia, Nokia Shanghai Bell), May 2021.

[0015] Non-patent document 9: 3GPP TSG RAN WG1 #104-bis-e, R1-2104686, “TB processing over multi-slot PUSCH,” Qualcomm Incorporated, May 2021.

[0016] Non-patent literature 10: 3GPP TSG RAN WG1 #105-e, R1-2104242, “Discussion on TBprocessing over multi-slot PUSCH,” Huawei, HiSilicon, May 2021. Summary of the Invention

[0017] However, there is still room for research into methods to improve communication efficiency in the uplink.

[0018] The non-limiting embodiments disclosed herein help to provide communication devices and methods that can improve communication efficiency in the uplink.

[0019] A communication apparatus according to an embodiment of this disclosure includes: a control circuit that determines the read position of the encoded data of the signal based on the amount of resources of a second interval preceding a first interval in a plurality of intervals allocated for signal transmission in the time domain, independent of the read result of encoded data in the second interval; and a transmission circuit that transmits the signal based on the read position.

[0020] It should be noted that these general or specific methods can be implemented by systems, devices, methods, integrated circuits, computer programs, or recording media, or by any combination of systems, devices, methods, integrated circuits, computer programs, and recording media.

[0021] According to one embodiment of this disclosure, communication efficiency in the uplink can be improved.

[0022] Further advantages and effects of one embodiment of this disclosure will be illustrated by the specification and drawings. These advantages and / or effects are provided by the various embodiments and the features described in the specification and drawings, but not necessarily all of them need to be provided in order to obtain one or more of the same features. Attached Figure Description

[0023] Figure 1This is a diagram illustrating an example of the time-domain resources that constitute the Transport Block processing over Multi-Slot Physical Uplink Shared Channel (TBoMS).

[0024] Figure 2 This is a diagram illustrating an example of TBoMS using rate matching based on Option 1.

[0025] Figure 3 This is a diagram illustrating an example of using TBoMS with rate matching based on option 2.

[0026] Figure 4 This is a diagram illustrating an example of using TBoMS with rate matching based on option 3.

[0027] Figure 5 This is a diagram illustrating an example of TBoMS using rate matching based on option 2 with the applied Variable Redundancy Version (RV) location.

[0028] Figure 6 This is a block diagram representing a structural example of a part of a base station.

[0029] Figure 7 This is a block diagram representing a structural example of a part of a terminal.

[0030] Figure 8 This is a block diagram representing a structural example of a base station.

[0031] Figure 9 This is a block diagram representing a structural example of a terminal.

[0032] Figure 10 This is a flowchart illustrating an example of a sending action in a terminal.

[0033] Figure 11 This is a diagram illustrating an example of TBoMS using rate matching in Implementation 1.

[0034] Figure 12 This is a diagram illustrating an example of TBoMS using rate matching in Implementation 1.

[0035] Figure 13 This is a diagram illustrating an example of TBoMS using rate matching in Implementation Method 2.

[0036] Figure 14 This is a diagram illustrating an example of a special slot.

[0037] Figure 15 This is a diagram representing an example of the time-domain resources that constitute TBoMS.

[0038] Figure 16 This is a diagram illustrating an example of the relationship between the value of the RV field and the RV position.

[0039] Figure 17 This is a diagram illustrating the exemplary architecture of a 3GPP NR system.

[0040] Figure 18 This is a schematic diagram illustrating the functional separation between NG-RAN (Next Generation-Radio Access Network) and 5GC (5th Generation Core).

[0041] Figure 19 This is a sequence diagram of the setup / resetting process for Radio Resource Control (RRC) connections.

[0042] Figure 20 This is a schematic diagram illustrating the application scenarios of enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and ultra-reliable and low-latency communications (URLLC).

[0043] Figure 21 This is a block diagram representing an exemplary 5G system architecture for non-roaming scenarios.

[0044] Explanation of reference numerals in the attached figures

[0045] 100 base stations

[0046] 101, 205 Control Department

[0047] 102 High-rise control signal generation unit

[0048] 103 Downlink Control Information Generation Unit

[0049] Coding sections 104 and 206

[0050] Modulation sections 105 and 207

[0051] Signal Distribution Sections 106 and 208

[0052] 107, 209 Sending Department

[0053] Receiving Departments 108 and 201

[0054] Extraction sections 109 and 202

[0055] 110, 203 De-escalation Department

[0056] Decoding sections 111 and 204

[0057] 200 terminals. Detailed Implementation

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

[0059] In NR, for example, in addition to frequency bands below 6 GHz, such as the 700 MHz to 3.5 GHz bands primarily used for cellular communication (e.g., also referred to as "Frequency Range 1" (FR1)), millimeter-wave bands such as the 28 GHz or 39 GHz bands that ensure wide bandwidth can also be used (e.g., also referred to as "FR2") (see, for example, Non-Patent Document 1). Furthermore, for example, it is possible to use frequency bands in FR1 that are higher than those used for Long Term Evolution (LTE) or 3G (3rd Generation mobile communication systems), such as the 3.5 GHz 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, it is expected that, even when using frequency bands higher than LTE or 3G, the same level of communication area (or coverage) as Radio Access Technology (RAT) such as LTE or 3G can be ensured; in other words, appropriate communication quality can be ensured. For example, in Release 17 (e.g., denoted as "Rel.17"), methods for improving coverage in NR were investigated (e.g., see Non-Patent Literature 2).

[0060] In NR, for example, a terminal (e.g., also referred to as "User Equipment") transmits and receives data according to resource allocation indicated by at least one of the physical layer (layer 1) downlink control signals (e.g., DCI: Downlink Control Information) transmitted in the downlink control channel (e.g., PDCCH: Physical Downlink Control Channel) and the radio resource control (RRC) corresponding to layer 3, which is sent from a base station (e.g., also referred to as "gNB") in the downlink control channel (e.g., PDCCH: Physical Downlink Control Channel).

[0061] In the uplink, for example, the terminal transmits uplink data channels (e.g., PUSCH: Physical Uplink Shared Channel, Physical Downlink Shared Channel) based on resource allocation (e.g., grant or UL grant) from the base station. The resource allocation information contained in at least one of the DCI and RRC may include, for example, information related to the time-domain resources for transmitting the PUSCH. For instance, the time-domain resource-related information may include information related to the timing (e.g., time slot offset) from the time slot from when the terminal receives the PDCCH until the PUSCH is transmitted (e.g., K2), and information related to the front-end symbol position of the PUSCH within the time slot or the number of symbols for the transmitted PUSCH.

[0062] In NR uplink transmissions, a method of sending the same information multiple times (also known as "repetition") is supported. For example, in version 15 (e.g., denoted as "Rel.15"), repetition of time slot units is specified as "PUSCH Repetition Type A," and in version 16 (e.g., denoted as "Rel.16"), repetition of multiple PUSCHs within one time slot is specified as "PUSCH Repetition Type B." For example, lower latency can be achieved compared to PUSCH Repetition Type A under PUSCH Repetition Type B.

[0063] In PUSCH repetition type A, the same time resource allocation is applied, for example, across multiple consecutive time slots. In PUSCH repetition type A, the base station, for example, informs the terminal of the time resource allocation within the time slot and the number of repeated time slots. Here, the number of repeated time slots can be, for example, a value counted based on consecutive time slots.

[0064] In PUSCH repetition type B, the base station can, for example, notify the terminal of the time-domain resources and repetition count for the first (initial) PUSCH transmission. In the allocation of time-domain resources for subsequent PUSCH transmissions, for example, symbols with the same number of symbols connected to the previous PUSCH transmission can be allocated.

[0065] 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 sent for PUSCH is sometimes less than the number of repetition slots notified.

[0066] Therefore, in Rel.17, as a functional extension of PUSCH repetition type A, it was studied, for example, to set the number of repetition slots to a value based on the uplink slots available for PUSCH transmission.

[0067] 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 determined based on the amount of resources per 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 slot in a repetition), regardless of whether there is a repetition (see, for example, Non-Patent Document 6). It should be noted that the amount of resources can be represented, for example, by the number of symbols or the number of resource elements (RE). Additionally, TBS is sometimes referred to as "TB size".

[0068] On the other hand, Rel. 17 investigated a method where, when sending PUSCH using multiple time slots, the TBS (Transmission Best Slot) is determined by multiplying the TBS calculated based on the resource amount per time slot unit or the resource amount allocated to the initial PUSCH transmission in a repetition by a scaling factor greater than 1. Sending PUSCH with a TBS determined by this method across multiple time slots is also known as "TB processing over multi-slot PUSCH (TBoMS)" or "TBoMS transmission".

[0069] In TBoMS, for example, the allocation of the same time resources across multiple time slots, similar to PUSCH repetition type A, was studied. Additionally, the parameters used to determine the number of time slots used by TBoMS were studied, for example, included in the RRC's information element (IE) which sets information related to the time domain resources for sending PUSCH.

[0070] For example, the information element of the RRC that sets information related to the time domain resources for transmitting PUSCH can be a "PUSCH-TimeDomainResourceAllocation IE" (see Non-Patent Document 8). The PUSCH time domain resource allocation may include, for example, information related to the timing (e.g., time slot offset) from the time slot of receiving the PDCCH to the time slot of transmitting the PUSCH, the PUSCH front-end symbol position within the time slot, the number of symbols for transmitting the PUSCH, or parameters related to the number of time slots in the TBoMS. For example, candidate combinations of the above parameters can be set (e.g., called a "TDRA (Time DomainResource Allocation) list" or "TDRA table"). The terminal can, for example, use the bits of the DCI or RRC that allocates the corresponding PUSCH to select a combination of parameters from the candidate combinations of parameters that the terminal actually uses for transmitting the PUSCH.

[0071] Furthermore, in TBoMS, the use of discontinuous time slots for TBoMS transmission has been studied, at least in Time Division Duplex (TDD). Additionally, an interval (group) consisting of one or more consecutive time slots from the time-domain resources (e.g., time slots) allocated to TBoMS is sometimes referred to as "TOT: Transmission Occasion for TBoMS" (e.g., see Non-Patent Document 8). The time-domain resources allocated to TBoMS may consist of one or more TOTs.

[0072] Figure 1 This diagram illustrates an example of time-domain resources allocated to TBoMS when 4 time slots are allocated and 2 consecutive time slots constitute the TOT. Figure 1 In this context, the time-domain resources allocated to TBoMS consist of two TOTs (a total of 4 time slots).

[0073] [Regarding rate matching using a circular buffer]

[0074] In NR (Rapid Retransmission), a cyclic buffer is used, for example, in retransmission control. A cyclic buffer is a memory that stores encoder output (e.g., encoded data or encoded bits containing system bits and parity bits). From a specified start position (RV: Redundant Version) in the cyclic buffer, the number of bits read corresponds to the allocated resource amount of the encoder output. The action of reading encoded bits from the cyclic buffer according to the specified RV based on the allocated resource amount is also called "rate matching".

[0075] 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 independent of the amount of allocated resources. For example, in TBoMS, the following three methods (Options 1, 2, and 3) can be used to map the encoded bits of a TB generated by the above method to multiple time slots.

[0076] <Option 1>

[0077] Option 1 is a method of setting the time-domain resources allocated to TBoMS (e.g., also referred to as "TBoMS resources") to rate-matched units.

[0078] For example, Option 1 is a method that reads a number of encoded bits from a specified RV position, corresponding to the amount of resources in the time slots (e.g., multiple time slots, or one or more TOTs) used for TBoMS transmission, and maps the read encoded bits to TBoMS resources spanning multiple time slots. In Option 1, for example, the RV position used to read the encoded bits is single.

[0079] Figure 2 This is a diagram illustrating an example of TBoMS using rate matching with option 1. Figure 2 In this example, the TBoMS resource contains two (e.g., a total of 4 time slots) TOTs consisting of two time slots each. Figure 2 In the example shown, the terminal can read the number of bits corresponding to the amount of resources allocated to the 4 slots of TBoMS from the specified RV position of the circular buffer (sometimes also represented as "RV=0" or "RV0"), and map the read number of encoded bits to the TBoMS resources spanning the 4 slots.

[0080] In Option 1, for example, because the number of bits read sequentially from a single RV position corresponds to the amount of encoded bits in the TBoMS resource, there is a high probability that all the encoded bits stored in the circular buffer in the TBoMS resource will be sent. Therefore, it has the advantage of being able to obtain sufficient encoding gain and achieve excellent decoding performance.

[0081] On the other hand, in Option 1, for example, when the unit of rate matching is the time resources allocated to TBoMS, multiple time slots allocated to TBoMS are considered in the calculation of the number of bits corresponding to the allocated resource amount and in the bit interleaving processing. Thus, in Option 1, rate matching processing can begin based on the resource amount of multiple time slots, therefore, the processing latency in the terminal is likely to increase. For example, when using... Figure 2 When TBoMS is transmitted in discontinuous time slots as shown, the impact of processing latency in the terminal will be more pronounced.

[0082] Furthermore, for example, if the time-domain resources transmitted by TBoMS conflict with the transmission resources of uplink control channels (e.g., PUCCH: Physical Uplink Control Channel) for transmitting uplink control information (e.g., UCI: Uplink Control Channel), the terminal will transmit UCI multiplexed within TBoMS. In this case, in Option 1, the terminal, for example, considers the UCI multiplexed in the time slots allocated to the tail of TBoMS when initiating rate matching processing, thus potentially increasing processing latency.

[0083] In addition, processing latency in the terminal can also easily increase, for example, when the time domain resources sent by TBoMS conflict with the resources indicated by the cancellation notification sent by the uplink (e.g., UL CI: Uplink Link Cancellation Indication), or when the time domain resources sent by TBoMS conflict with the allocation of the uplink sent with higher priority.

[0084] Alternatively, the unit for conflict handling can be replaced from a time slot to a time-domain resource allocated to TBoMS. In this case, for example, the time slot for conflict handling (e.g., referred to as the "base time slot") is set to the time slot allocated to the front end of TBoMS, thus imposing a limitation on the terminal processing timeline.

[0085] <Option 2>

[0086] Option 2 is a method to set the time slot to a rate-matched unit.

[0087] For example, Option 2 is a method in which the number of encoded bits corresponding to the amount of PUSCH transmission resources allocated to each time slot used for transmission in TBoMS is read from a specified RV position, and the read encoded bits are individually mapped to resources within the time slot. In Option 2, for example, the RV position used to read the encoded bits can be different. In other words, in Option 2, the RV position can also be set (e.g., changed) individually for each time slot.

[0088] Figure 3 This is a diagram illustrating an example of TBoMS using rate matching with option 2. Figure 3 In this example, the TBoMS resource contains two (e.g., a total of 4 time slots) TOTs consisting of two time slots each. Figure 3In the example shown, the terminal can read the number of bits corresponding to the resource amount of the time slot from the specified RV position (e.g., RV=0 (RV0), RV=2 (RV2), RV=3 (RV3), and RV=1 (RV1)) of the circular buffer set for the time slot in the four time slots allocated to TBoMS, and map the read number of encoded bits to the resources in the time slot.

[0089] In Option 2, for example, the terminal does not need to start rate matching processing based on the amount of resources in multiple time slots, and can perform processing on a time slot unit basis. Therefore, from the viewpoint of easily supporting discontinuous time slots or easily handling conflict processing, Option 2 is effective and can suppress the increase in processing latency in the terminal. In addition, in Option 2, for example, time slot unit processing can be performed during conflict processing, and the time slot for conflict processing (e.g., the reference time slot) can be set to the time slot where conflict will occur, so there is no limitation on the terminal processing timeline.

[0090] On the other hand, in option 2, for example, in such Figure 3 When reading coded bits from existing four RV positions as shown in Rel.15 / 16, it is difficult to transmit all coded bits in TBoMS transmission. For example, the higher the coding rate, the fewer coded bits are read, and the higher the probability that not all coded bits can be transmitted in TBoMS. Therefore, in Option 2, it is difficult to obtain coding gain, and decoding performance is prone to degradation.

[0091] <Option 3>

[0092] Option 3 is the method to set TOT as the unit of rate matching.

[0093] For example, Option 3 is a method that reads the number of encoded bits corresponding to the resource amount of the TOT in TBoMS from a 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 to read the encoded bits can be different. In other words, in Option 3, the RV position can also be set (e.g., changed) individually for each TOT.

[0094] Figure 4 This is a diagram illustrating an example of TBoMS using rate matching with option 3. Figure 4 In this example, the TBoMS resource contains two (e.g., a total of 4 time slots) TOTs consisting of two time slots each. Figure 4In the example shown, the terminal can read the number of bits corresponding to the resource amount of the TOT (e.g., 2 slots) from the specified RV position (e.g., RV=0 (RV0) and RV=2 (RV2)) of the circular buffer set for the TOT in the two TOTs allocated to TBoMS, and map the read number of encoded bits to the resources within the TOT.

[0095] Option 3, for example, has a shorter rate-matching unit compared to Option 1, thus mitigating the impact of processing latency in the terminal. Furthermore, compared to Option 2, Option 3 can suppress the degradation in decoding performance caused by the inability to send more (e.g., all) of the encoded bits.

[0096] On the other hand, in option 3, for example, in such Figure 4 When the TOT is composed of multiple time slots, similar to option 3, multiple time slots are considered in the handling of conflicts. Therefore, compared with option 2, the processing latency is likely to increase, and it will also limit the terminal processing timeline.

[0097] The above explains options 1, 2, and 3.

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

[0099] For example, as a method to suppress the degradation of decoding performance and maintain the time slot unit in option 2, methods for variably setting the RV position can be listed (for example, see Non-Patent Document 9 and Non-Patent Document 10).

[0100] Figure 5 This is a diagram illustrating an example of a rate-matching method that applies a variable RV position (e.g., also known as "continuous RV" or "floating RV") to option 2. Figure 5 As shown, in option 2 with the application of a variable RV position, the terminal can, for example, read the number of bits corresponding to the amount of resources allocated to each time slot for PUSCH transmission from the variable RV position, and map the read coded bits individually to the resources within the time slot.

[0101] Here, the terminal can retain the number of encoded bits read in each time slot and, based on the retained number of encoded bits, determine the RV position when reading encoded bits in the next time slot. For example, the RV position in the nth time slot constituting the TOT (e.g., the read start bit position on the circular buffer) s n It can be provided by the following formula (1).

[0102] [Mathematical Expression 1]

[0103]

[0104] Here, l n－1 This represents the position of the last bit in the circular buffer of the encoded bits read in the (n-1)th time slot. That is, the RV position s of the nth time slot. n It can be set to the next bit position on the n-cycle buffer of the encoded bits read in the (n-1)th time slot, after the last bit position.

[0105] In Option 2, which employs a variable RV position, even when rate matching is performed at the time slot unit level, the terminal can easily transmit consecutive bit strings on the circular buffer, suppressing the degradation in decoding performance described in Option 2. Furthermore, in Option 2, since the rate matching unit can be a time slot, it offers the advantages of maintaining time slot unit processing as in Option 2, and achieving reduced processing latency and simplified collision handling compared to Options 1 or 3.

[0106] Here, for example, in Option 2 with a fixed RV position, because the RV position is fixed, the terminal can begin rate matching processing regardless of the number of encoded bits read in a time slot preceding that time slot, as long as it obtains information related to the amount of resources transmitted by the PUSCH in the time slot allocated for rate matching. In other words, in Option 2 with a fixed RV position, rate matching processing can begin in each of the multiple time slots allocated to TBoMS without waiting for rate matching processing in previous time slots.

[0107] On the other hand, in Option 2, which applies a variable RV position, the RV position (the start bit position on the circular buffer) when reading encoded bits in multiple time slots allocated to TBoMS depends on the rate matching results of previous time slots (e.g., the number of encoded bits read or the last bit position). Therefore, in Option 2, which applies a variable RV position, the terminal begins rate matching processing for a time slot after determining the number of encoded bits read in a time slot preceding the one for which rate matching is applied. In other words, rate matching processing for a time slot will not begin until the number of encoded bits read in a time slot preceding the one for which rate matching is applied is determined.

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

[0109] Additionally, for example, in time slots that are earlier than the application rate matching time slots, the following situations may occur: TBoMS time domain resources conflict with PUCCH transmission resources for transmitting UCI, resulting in the reuse of UCI in PUSCH resources; TBoMS time domain resources conflict with resources indicated by UL CI, resulting in the discarding of PUSCH; or TBoMS time domain resources conflict with the allocation of high-priority uplink transmissions, resulting in the discarding of PUSCH.

[0110] In these cases, in Option 2 with the application of variable RV positions, the RV position when reading coded bits in a time slot (e.g., the read start bit position on the circular buffer) is affected by the multiplexing result of UCI in time slots earlier than that time slot, the drop of PUSCH transmission due to UL CI, or the drop of PUSCH transmission due to the allocation of high-priority uplink transmissions. This indicates that, for example, the RV position when reading coded bits from the circular buffer depends not only on the DCI allocated to the corresponding TBoMS, but also on the DCI allocated to the downlink data channel (e.g., PDSCH: Physical Downlink Shared Channel) corresponding to the multiplexed UCI, the DCI for transmitting UL CI, or the DCI for allocating high-priority uplink transmissions.

[0111] For example, if these DCI false detections occur in the terminal, the RV position when reading the encoded bits from the circular buffer will be inconsistent between the base station and the terminal. Therefore, if these DCI false detections occur in the terminal, the decoding performance will be significantly reduced. Alternatively, although the base station can perform blind decoding that takes into account the DCI false detections in the terminal, the base station's decoding process will become more complicated in this case.

[0112] In one non-limiting embodiment of this disclosure, a method for transmitting uplink signals that suppresses the increase in processing latency in TBoMS and is robust against false detections of DCI is described.

[0113] For example, in one non-limiting embodiment of this disclosure, the degradation of decoding performance can be suppressed by applying a variable RV position to the rate matching processing of time slot units in TBoMS. Additionally, in another non-limiting embodiment of this disclosure, the variable RV position (read start bit position on the circular buffer) in each time slot of TBoMS can be determined based on the number of coded bits calculated according to resources (e.g., referred to as "reference resource usage") that are independent of the rate matching processing results in previous time slots. This suppresses the increase in processing latency in the terminal, and even in the event of false detection of DCI in the terminal, it suppresses the degradation of decoding performance and avoids complicating the decoding processing of the base station.

[0114] (Implementation Method 1)

[0115] [Overview of Communication Systems]

[0116] The communication system of the various embodiments of this disclosure includes a base station 100 and a terminal 200.

[0117] Figure 6 This is a block diagram illustrating a structural example of a base station 100 (e.g., corresponding to a communication device) according to an embodiment of the present disclosure. Figure 6 In the base station 100 shown, 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 based on the amount of resources (e.g., reference resources) of the second interval, which is earlier than the first interval, in multiple intervals (e.g., time slots) of the time-domain resources (e.g., TBoMS resources or resources within TOT) allocated for signal (e.g., PUSCH) transmission, independent of the read result (e.g., rate matching result) of the encoded data in the second interval. The receiving unit 108 (e.g., corresponding to a receiving circuit) receives the signal based on the read position.

[0118] Figure 7 This is a block diagram illustrating a structural example of a portion of a terminal 200 (e.g., corresponding to a communication device) according to an embodiment of this disclosure. Figure 7 In the terminal 200 shown, the control unit 205 (e.g., corresponding to a control circuit) determines the read position of the encoded data of the signal in the first interval based on the amount of resources in a second interval that precedes the first interval among multiple intervals allocated to the time-domain resources for signal transmission, independent of the read result of the encoded data in the second interval. The transmission unit 209 (e.g., corresponding to a transmission circuit) transmits the signal based on the read position.

[0119] [Base station structure]

[0120] Figure 8 This is a block diagram illustrating a structural example of the base station 100 according to Embodiment 1. Figure 8 In this base station 100, there are a control unit 101, a higher layer 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.

[0121] Control unit 101 determines, for example, information related to the reception of downlink data signals (e.g., PDSCH) and the transmission of uplink data signals (e.g., PUSCH) for terminal 200, and outputs the determined information to higher-layer control signal generation unit 102. The information related to the reception of downlink data signals and the information related to the transmission of uplink data signals may include, for example, information related to time domain resource allocation (e.g., information related to the TDRA table) or information related to TBoMS (e.g., information related to the number of transmission time slots).

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

[0123] Additionally, the control unit 101 may, for example, determine information related to 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 information related to the uplink data signals 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 multiple time slots contained in the TBoMS based on the method described later, and output the determined information to the decoding unit 111.

[0124] The higher-level control signal generation unit 102 generates a higher-level control signal bit string based on information input from the control unit 101, and outputs the higher-level control signal bit string to the encoding unit 104.

[0125] The downlink control information generation unit 103 generates a downlink control information (e.g., DCI) bit string based on information input from the control unit 101, and outputs the generated DCI bit string to the encoding unit 104. Furthermore, the control information is sometimes sent to multiple terminals.

[0126] The encoding unit 104 encodes, for example, downlink data (e.g., DL data signal), a bit string input from the higher-layer control signal generation unit 102, or a DCI bit string 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 string to the modulation unit 105.

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

[0128] The signal allocation unit 106 maps the symbol string (e.g., containing downlink data signals or control signals) input from the modulation unit 105 to the radio resources, for example, based on information representing radio resources input from the control unit 101. The signal allocation unit 106 then outputs the mapped downlink signal to the transmission unit 107.

[0129] The transmitting unit 107 performs transmission waveform generation processing on the signal input from the signal distribution unit 106, for example, using orthogonal frequency division multiplexing (OFDM). Additionally, in the case of OFDM transmission with an added cyclic prefix (CP), the transmitting unit 107 performs inverse fast fourier transform (IFFT) processing on the signal and adds CP to the IFFT-derived signal. Furthermore, the transmitting unit 107 performs RF (radio frequency) processing on the signal, such as D / A (digital / analog) conversion or up-conversion, and transmits the wireless signal to the terminal 200 via an antenna.

[0130] The receiving unit 108 performs RF processing, such as down-conversion or A / D (Analog / Digital) conversion, on the uplink signal received from the terminal 200 via the antenna. Alternatively, 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 domain signal to the extraction unit 109.

[0131] The extraction unit 109 extracts, for example, the radio resource portion that has transmitted uplink data signals (e.g., PUSCH) based on the information input from the control unit 101 and the received signal input from the receiving unit 108, and outputs the extracted radio resource portion to the demodulation unit 110.

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

[0133] The decoding unit 111 performs error correction decoding on 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, thereby obtaining the decoded received bit sequence (e.g., UL data signal).

[0134] [Terminal Structure]

[0135] Figure 9 This is a block diagram illustrating a structural example of a terminal 200 according to an embodiment of the present disclosure. For example, in Figure 9 In the terminal 200, there are receiving units 201, extraction units 202, demodulation units 203, decoding units 204, control units 205, encoding units 206, modulation units 207, signal distribution units 208, and transmitting units 209.

[0136] 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 a received signal (baseband signal). Additionally, when receiving OFDM signals, the receiving unit 201 performs FFT processing on the received signal to convert it to the frequency domain. The receiving unit 201 then outputs the received signal to the extraction unit 202.

[0137] For example, based on radio resource-related information concerning downlink control information input from the control unit 205, the extraction unit 202 extracts a portion of radio resources that may contain downlink control information from the received signal input from the receiving unit 201, and outputs it to the demodulation unit 203. Additionally, based on radio resource-related information concerning data signals input from the control unit 205, the extraction unit 202 extracts a portion of radio resources containing downlink data, and outputs it to the demodulation unit 203.

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

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

[0140] 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., higher-layer control signals or downlink control information). The control unit 205 outputs the determined information to the extraction unit 202, demodulation unit 203, encoding unit 206, modulation unit 207, and signal allocation unit 208.

[0141] In addition, the control unit 205 may, for example, determine at least one of the TBS in the TBoMS and the RV position of the multiple time slots contained in the TBoMS according to the method described later, and output the determined information to the encoding unit 206, the modulation unit 207 and the signal distribution unit 208.

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

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

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

[0145] The transmitting unit 209 generates a transmit signal waveform, such as OFDM, from the signal input from the signal distribution unit 208. Alternatively, in the case of OFDM transmission using CP, the transmitting unit 209 performs IFFT processing on the signal and appends CP to the IFFT-derived signal. Or, if the transmitting unit 209 generates a single-carrier waveform, a Discrete Fourier Transform (DFT) section (not shown) may be added, for example, after the modulation unit 207 or before the signal distribution unit 208. Furthermore, the transmitting unit 209 performs RF processing on the transmit signal, such as D / A conversion and up-conversion, and transmits the wireless signal to the base station 100 via an antenna.

[0146] [Example of operation of base station 100 and terminal 200]

[0147] This section describes an example of the operation of a base station 100 and a terminal 200 with the above structure.

[0148] Figure 10 This is a flowchart illustrating an example of an action related to TBoMS transmission in terminal 200.

[0149] <S101>

[0150] exist Figure 10 In this process, terminal 200 receives from base station 100 an indication related to PUSCH transmission using TBoMS (e.g., resource allocation information related to TBoMS transmission).

[0151] <S102>

[0152] Terminal 200, for example, determines the resources or amount of resources (hereinafter also referred to as "reference resources") used to determine the RV position (read start bit position in the circular buffer) of each of the multiple time slots contained in TBoMS.

[0153] Reference resources can be, for example, the amount of resources in the slot preceding the rate-matched slot, independent of the rate-matching result (readout result) of the encoded data. In other words, reference resources can be resources determined regardless of the reasons for fluctuations between slots. As an example, reference resources can be the amount of resources independent of the presence or absence of UCI multiplexing. Alternatively, reference resources can be, for example, the amount of resources independent of whether PUSCH transmissions were discarded due to dynamic SFI (Slot Format Indicator) notification, UL CI, or allocation of high-priority uplink transmissions.

[0154] For example, the reference resource can also be the amount of resources (e.g., the number of REs) allocated to PUSCH transmissions in the front-end slots within the TOT. As an example, the amount of the reference resource (e.g., referred to as the "reference resource amount") N can be calculated based on the following equation (2) or equation (3). RE .

[0155] [Mathematical Expression 2]

[0156]

[0157] [Mathematical Expression 3]

[0158]

[0159] In equation (2), the upper limit of the number of REs within a time slot is set to, for example, 156. However, the upper limit of the number of REs within a time slot is not limited to 156 and can be other values.

[0160] In equations (2) and (3), n PRB This is the number of resource blocks (e.g., PRB: Physical Resource Block) allocated to TBoMS for transmission. Additionally, N' in equations (2) and (3) can be calculated, for example, based on the following equation (4). RE .

[0161] [Mathematical Expression 4]

[0162]

[0163] in,

[0164] The average number of subcarriers per resource block (e.g., 12).

[0165] The number of OFDM symbols transmitted by the PUSCH in the front-end slots allocated within the TOT.

[0166] The number of REs (References) for DMRS (Demodulation Reference Signal) transmitted by the PUSCH in the front-end time slots allocated within the TOT.

[0167] : Use RRC to notify terminal 200 of the overhead coefficient.

[0168] For example, the number of OFDM symbols transmitted by the PUSCH in the front-end slot allocated within the TOT can be notified to the terminal 200 using information related to the symbol length of the Time Domain Resource Allocation (TDRA).

[0169] <S103>

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

[0171] For example, the reference resource quantity N calculated according to equation (2) or equation (3) can be used. RE Based on the following equation (5), the number of reference coding bits N corresponding to the reference resource is calculated. ref .

[0172] [Mathematical Expression 5]

[0173]

[0174] in,

[0175] Modulation order

[0176] : Number of MIMO (Multiple Input Multiple Output) layers.

[0177] <S104>

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

[0179] Terminal 200 may, for example, set the RV position (the read start bit position on the circular buffer) in the front-end time slot within the TOT to an existing RV position (e.g., one of RV0, RV1, RV2, RV3) as specified in Rel.15 / 16.

[0180] Additionally, terminal 200 can, for example, be based on the reference coding bit number N. refThe time slot index n within the TOT determines the RV position in the time slot following the front end within the TOT. For example, the RV position s in the nth time slot (e.g., time slot index n) constituting the TOT. n It can be given by the following equation (6).

[0181] [Mathematical Expression 6]

[0182]

[0183] Here, N RVx It is the RV position used by the front-end time slot within the TOT (e.g., the bit position specified by RV0, RV1, RV2, or RV3).

[0184] Thus, terminal 200 is based on the number of reference coded bits N corresponding to the reference resource. ref The index of the time slot determines the RV position of each time slot. In other words, the terminal 200 determines the RV position of each time slot independently of the rate matching results in the time slots preceding it.

[0185] <S105>

[0186] Terminal 200 performs rate matching in each time slot based on the determined RV position. For example, terminal 200 can read the number of reference coded bits corresponding to the reference resources (e.g., the number of bits corresponding to the amount of PUSCH transmission allocated to the front-end time slot within the TOT) from the determined RV position (variable RV position) for each time slot, and map the read coded bits to the PUSCH resources of each time slot.

[0187] <S106>

[0188] Terminal 200, for example, uses TBoMS to send PUSCH.

[0189] The above describes an example of an action related to TBoMS transmission in terminal 200.

[0190] Thus, in this embodiment, the terminal 200 uniquely determines the RV position (e.g., the read start bit position on the circular buffer) of each time slot within the TOT without relying on the rate matching result of the time slot preceding the time slot.

[0191] Figure 11 This diagram illustrates an example of using rate-matched TBoMS in this embodiment. Figure 11 For example, TBoMS contains 4 time slots and one TOT (e.g., 4 time slots).

[0192] like Figure 11As shown, terminal 200 can, for example, set the RV position (read start bit position on the circular buffer) s0 in the front-end time slot within the TOT to the existing RV position specified in Rel. 15 / 16 (in Figure 11 (RV0 in the middle).

[0193] In addition, Figure 11 In this context, terminal 200 can, for example, set the resources allocated to PUSCH in the front-end time slot within the TOT as reference resources. As mentioned above, the reference resources can be, for example, a resource quantity independent of the presence or absence of UCI multiplexing. Moreover, terminal 200 can, for example, determine the reference resources (e.g., the number of reference code bits N) based on equation (6). ref The time slot index n within the TOT (e.g., n = 1, 2, or 3) determines the RV positions s1, s2, and s3 in the nth time slot.

[0194] Here, for example, such as Figure 11 (a) The last bit position on the circular buffer for reading encoded bits in the front-end time slot in the case of no UCI multiplexing in the front-end time slot, and as in Figure 11 In the case of UCI multiplexing in the front-end time slot, as in (b), the position of the last bit on the circular buffer for reading the encoded bits in the front-end time slot will be different.

[0195] In contrast, as mentioned above, in Figure 11 In this process, terminal 200 determines the RV position of a time slot that is later than the front-end time slot, based on a reference resource that is independent of UCI multiplexing and serves as the allocation resource for the PUSCH in the front-end time slot within the TOT. Therefore, even in situations like... Figure 11 (a) and Figure 11 In cases where the last bit position on the circular buffer of the read encoded bit in the front-end time slot (in other words, the rate matching result) is different, the terminal 200 will also uniquely determine the RV positions s1, s2 and s3 in the time slot that is later than the front-end time slot, regardless of the presence or absence of UCI multiplexing.

[0196] Therefore, terminal 200 can, for example, start rate matching processing for each time slot without waiting for the rate matching processing result of the previous time slot, thus suppressing the increase in processing latency in terminal 200.

[0197] Additionally, for example, in the RV position determination method based on equation (1), the last bit position l on the circular buffer of the read encoded bits in the previous time slot. n－1The location will vary depending on whether UCI multiplexing is present within the PUSCH resource. In contrast, in the RV location determination method based on equation (6), the RV location of each time slot is determined based on reference resources that do not depend on UCI multiplexing, and is unaffected by the presence or absence of UCI multiplexing. Therefore, in this embodiment, for example, the RV location of each time slot does not depend on the DCI of the PDSCH allocated to the multiplexed UCI. Thus, the terminal 200 can perform PUSCH transmission with robust false detection against the DCI.

[0198] Furthermore, in this embodiment, the terminal 200 may, for example, decide whether to actually send the PUSCH for each time slot in the uplink time slot available for TBoMS, according to the PUSCH discarding specification.

[0199] Terminal 200 may, for example, also count the time slots that are determined not to actually send PUSCH (discard PUSCH transmission) as time slots constituting TOT. In other words, the time slot index n within TOT can be appended to each time slot constituting TOT regardless of whether PUSCH transmission is discarded.

[0200] For example, in the PUSCH discarding specification, if the time resource allocation within a PUSCH transmission slot conflicts with downlink symbols set by dynamic SFI notification, if the time resource allocation within a PUSCH transmission slot conflicts with resources indicated by UL CI, or if the time resource allocation within a PUSCH transmission slot conflicts with the allocation of higher-priority uplink transmissions, the terminal 200 may decide not to transmit PUSCH in the conflicting slot (e.g., discard PUSCH transmission). In this embodiment, for example, the terminal 200 may count the slots in which PUSCH is not transmitted (slots in which PUSCH transmission is discarded) as slots constituting the TOT.

[0201] Figure 12 This diagram illustrates an example of using rate-matched TBoMS in this embodiment. Figure 12 In this example, TBoMS contains 4 time slots and one TOT (e.g., 4 time slots). Figure 12 As shown, for example, when it is decided to discard PUSCH transmission in the third time slot within the TOT, terminal 200 can set a time slot index of n = 0 to 3 for the four time slots within the TOT that include the third time slot. In other words, terminal 200 also counts the third time slot where PUSCH transmission is discarded as a time slot constituting the TOT.

[0202] Terminal 200 determines the RV position (read start bit position on the circular buffer) in the front-end time slot within the TOT and the nth time slot constituting the TOT (e.g., n is an integer greater than 1) according to the above method.

[0203] Furthermore, terminal 200 can, for example, discard PUSCH transmissions by simply setting the encoded transmission to RF off. For example, in Figure 12 In the example, terminal 200 can perform RF shutdown in a time slot of n=2.

[0204] In addition, the base station 100 may, for example, determine the RV position of each time slot in the TBoMS of the terminal 200 based on reference resources (e.g., the allocation resources of the front-end time slots within the TOT), and perform reception processing of signals transmitted from the TBoMS of the terminal 200 based on the determined RV positions.

[0205] The above describes the operation examples of base station 100 and terminal 200.

[0206] According to this embodiment, the base station 100 and the terminal 200 determine the RV position in a certain time slot within the time domain resources allocated to TBoMS, for example, based on reference resources that do not depend on the rate matching results in time slots earlier than the time slot.

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

[0208] 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 independent of the DCI corresponding to the allocation of dynamic SFI notification, UL CI, or high-priority uplink transmission. Thus, the RV position determination method of this embodiment is robust against false detection of DCI.

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

[0210] As described above, this embodiment can improve communication efficiency in the uplink.

[0211] (Implementation Method 2)

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

[0213] In this embodiment, terminal 200 may, for example, in the uplink time slots available for TBoMS, similar to embodiment 1, decide whether to actually send the PUSCH for each time slot according to the PUSCH discarding specification.

[0214] Furthermore, in this embodiment, for example, terminal 200 may not count the time slots determined not to send PUSCH (discard PUSCH transmission) as time slots constituting TOT. In other words, time slots that are different from the time slots that discard PUSCH transmission, such as time slots that perform PUSCH transmission, can be appended with a time slot index n within TOT.

[0215] Figure 13 This diagram illustrates an example of using rate-matched TBoMS in this embodiment. Figure 13 In this example, TBoMS contains 4 time slots and one TOT (e.g., 4 time slots). Figure 13 As shown, for example, when it is decided to discard PUSCH transmission in the third time slot within the TOT, terminal 200 can 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, terminal 200 does not count the third time slot where PUSCH transmission is discarded as a time slot constituting the TOT.

[0216] Terminal 200 can, for example, be based on the number of reference coded bits N corresponding to the reference resource. ref The relevant time slot index n within the TOT determines the variable RV position (the read start bit position on the circular buffer) in each time slot of TBoMS. Furthermore, as mentioned above, the time slot index n is the index of the time slot within the TOT that actually transmits PUSCH, excluding the time slots where PUSCH transmission is discarded.

[0217] Additionally, similar to Implementation 1, the reference resource can be a resource amount from a time slot preceding the time slot where rate matching is performed, independent of the rate matching result (read result) of the encoded data in that time slot. For example, the reference resource can be a resource amount independent of the presence or absence of UCI multiplexing. Alternatively, the reference resource can be, for example, a resource amount independent of whether PUSCH transmissions were discarded due to allocation of dynamic SFI notification, UL CI, or high-priority uplink transmissions.

[0218] For example, the reference resource can also be the amount of resources (REs) allocated to PUSCH transmission in the front-end slots within the TOT. For example, the number of reference coded bits N calculated based on the reference resource can be determined according to equation (5). ref .

[0219] Terminal 200, for example, from the reference encoded bit number N ref and the RV position s given by the time slot index n within TOT n The number of read bits corresponds to the amount of coded bits allocated to the PUSCH transmission in the nth time slot within the TOT, and the read coded bits are mapped to the PUSCH resources in the nth time slot. For example, the RV position s in the nth PUSCH transmission within the TOT (e.g., time slot index n). n It can be given by the following equation (7).

[0220] [Mathematical Expression 7]

[0221]

[0222] Here, N RVx It is the RV position used by the front-end PUSCH transmission within the TOT (e.g., the bit position specified by RV0, RV1, RV2, or RV3).

[0223] For example, in Figure 13 In the example shown, terminal 200 can, for example, set the RV position (read start bit position on the circular buffer) s0 in the PUSCH transmission of the front end within the TOT (e.g., the slot where n=0) to the existing RV position specified in Rel. 15 / 16 (in Figure 13 (RV0 in the middle).

[0224] In addition, Figure 13 In this embodiment, terminal 200 can, for example, set the resources allocated to the PUSCH in the PUSCH transmission of the front-end within the TOT as reference resources. Similar to embodiment 1, the reference resources can, for example, be a resource amount independent of UCI multiplexing. Furthermore, terminal 200 can, for example, determine the reference resources (e.g., the number of reference code bits N) based on equation (7).ref The time slot index n within the TOT (e.g., n = 1 or 2) determines the RV positions s1 and s2 in the nth time slot.

[0225] According to this embodiment, similar to Embodiment 1, in TBoMS, a variable RV position can be applied to the rate matching processing of time slot units. Therefore, similar to Option 2 above, decoding performance can be improved, and the increase in processing latency in 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 notification, UL CI, or high-priority uplink transmission allocation, and is independent of the corresponding DCI. Therefore, similar to Embodiment 1, the method for determining the RV position is robust against DCI false detection. Moreover, 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 are less likely to occur between base station 100 and terminal 200. Additionally, base station 100 can avoid performing decoding processing that considers DCI false detection in terminal 200, thus suppressing the complexity of decoding processing in base station 100.

[0226] Furthermore, in this embodiment, the terminal 200 determines the RV position based on the reference number of coded bits corresponding to the reference resource quantity and the slot index of the slot that is different from the slot where PUSCH transmission is discarded among multiple slots within the TOT (or TBoMS). Therefore, even if PUSCH is not transmitted in at least one slot within the TOT (discarded PUSCH transmission), the coded bits stored in the circular buffer can still be continuously read in multiple slots within the TOT where PUSCH is transmitted, thus preventing degradation of decoding performance.

[0227] For example, Figure 12 This diagram illustrates an example of discarding the PUSCH transmission in the third time slot in Implementation 1. Figure 13 This diagram illustrates an example of discarding the PUSCH transmission in the third time slot in Implementation 2. For example, in... Figure 12 In this case, the PUSCH transmission in the third time slot is discarded; therefore, terminal 200 does not transmit the encoded bits read from RV position s2. In contrast, for example in... Figure 13 Even if the PUSCH transmission in the third time slot is discarded, 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, all the encoded bits stored in the circular buffer are transmitted via TBoMS transmission, thereby preventing degradation of decoding performance.

[0228] (Implementation Method 3)

[0229] The structure 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.

[0230] In TBoMS, in order to make efficient use of uplink resources, a transmission method was studied that enables PUSCH to be transmitted in a time slot even if at least one symbol in the PUSCH resources (e.g., symbols) within the allocated time slot is a symbol that cannot be used for PUSCH transmission, if it contains a certain number of symbols that can be used for PUSCH transmission.

[0231] Here, at least one symbol in the PUSCH resources within the allocated time slot is a symbol that cannot be used for PUSCH transmission. In addition, a time slot containing a certain number of symbols that can be used for PUSCH transmission is called a "special time slot".

[0232] Figure 14 This diagram illustrates an example where the PUSCH front-end symbol position S=0 within a time slot, the number of PUSCH symbols transmitted L=14, the TBoMS time slot number is set to 4, and a special time slot (e.g., time slot #1) is included within a portion of consecutive time slots (e.g., time slots #0, #1, #2, and #3). Figure 14 In the diagram, the portion indicated by "U" represents the PUSCH resource (symbol) that is actually used to send the PUSCH. Additionally, in... Figure 14 In the diagram, the part indicated by "D" represents the resources for transmitting downlink signals, and the part indicated by "F" represents the resources that can transmit both downlink and uplink signals (e.g., flexible symbols).

[0233] Additionally, for convenience, time slots that are not special time slots will be referred to as "normal time slots" below. For example... Figure 14 As shown in slots #0, #2 and #3, a typical slot can also be a slot in which the symbols within the slot constitute symbols that can be used for PUSCH transmission.

[0234] For example, terminal 200 uses uplink symbols contained in a special time slot to send PUSCH, thereby improving the utilization efficiency of uplink resources and expecting to improve the coverage performance of PUSCH.

[0235] In this embodiment, for example, the following situation will be described: the method for determining the reference resource (e.g., the calculation method) is different depending on whether the front-end time slot within the TOT is a special time slot.

[0236] The following describes three methods related to the calculation of reference resources.

[0237] <Method 1>

[0238] In Method 1, the reference resource can be, for example, the amount of resources (e.g., number of REs) allocated to the front-end slots within the TOT for PUSCH transmission multiplied by a scaling factor greater than 1 (e.g., denoted as "K"). Furthermore, the resources allocated to the front-end slots within the TOT for PUSCH transmission used to calculate the reference resource can be resources without considering UCI multiplexing.

[0239] Here, the scaling factor K can vary depending on whether the front-end timeslot within the TOT is a special timeslot. For example, if the front-end timeslot within the TOT is not a special timeslot (in the case of a normal timeslot), K can be set to 1. On the other hand, if the front-end timeslot within the TOT is a special timeslot, K can be set to > 1.

[0240] For example, the reference resource quantity N can also be calculated according to the method shown in equation (8) below. RE .

[0241] [Mathematical Expression 8]

[0242]

[0243] Here, N RE,0 This represents the amount of resources (e.g., number of REs) allocated to the front-end slots within the TOT, as given by equation (2) or equation (3).

[0244] According to Method 1, even if the front-end time slot within the TOT is a special time slot, the resource amount of the same level as that of a normal time slot can be set as the reference resource amount.

[0245] In addition, the scaling factor K can also be multiplied by the number of coded bits (reference coded bits) N calculated based on the reference resource. ref Instead of multiplying by the reference resource quantity N RE,0 .

[0246] <Method 2>

[0247] In Method 1, for example, the time slot used as the basis for calculating the reference resource quantity is the front-end time slot within the TOT, regardless of whether the front-end time slot of the TOT is a special time slot. In Method 2, for example, the time slot used as the basis for calculating the reference resource quantity can be the initial normal time slot within the TOT.

[0248] For example, if the front-end timeslot within a TOT is a normal timeslot, the timeslot used as the basis for calculating the reference resource quantity can be the front-end timeslot. On the other hand, if the front-end timeslot within a TOT is a special timeslot, the timeslot used as the basis for calculating the reference resource quantity can be a normal timeslot within the TOT that is different from the front-end timeslot (e.g., the initial normal timeslot).

[0249] According to method 2, terminal 200 can calculate the reference resource quantity using a normal time slot as a reference, regardless of the setting of special time slots within the TOT. Therefore, according to method 2, for example, it is not necessary to adjust the scaling factor based on whether the front-end time slot within the TOT is a special time slot, as in method 1, thus simplifying the processing of terminal 200.

[0250] <Method 3>

[0251] For example, in TBoMS, as one of the methods for notifying information related to time-domain resource allocation, there is a method that notifies the terminal 200 of multiple information related to the front-end symbol position of the PUSCH in the time slot and the number of symbols of the PUSCH sent (e.g., SLIV: Start symbol and allocation Length IndicatorValue).

[0252] Methods for notifying multiple SLIVs include, for example, notifying each SLIV in a time slot separately within TBoMS, or notifying different SLIVs based on whether it is a normal time slot or a special time slot.

[0253] In method 3, when multiple SLIVs are notified using information related to the time-domain resource allocation for terminal 200 (e.g., also referred to as "TDMA entry") as described above, the time slot that serves as the basis for calculating the reference resource amount can be set to the time slot that notifies the value of the maximum symbol length (L) among the multiple SLIVs.

[0254] For example, in method 3, when different SLIVs are notified based on whether it is a normal time slot or a special time slot, terminal 200 may also set the resource of the time slot that notifies the SLIV corresponding to the normal time slot as a reference resource.

[0255] The above explains three methods related to the calculation of reference resources.

[0256] Furthermore, in this embodiment, the terminal 200 can determine the RV position (read start bit position on the circular buffer) of the nth time slot within the TOT based on equation (6) in the same manner as in embodiment 1, and can also determine the RV position (read start bit position on the circular buffer) of the nth time slot within the TOT based on equation (7) in the same manner as in embodiment 2.

[0257] According to this embodiment, even when there are both normal time slots and special time slots mixed within the TOT, the parameters used to determine the RV position of each time slot are still the two parameters corresponding to the reference coding bits and the time slot index. Therefore, it has the advantage of simplifying the processing of the terminal 200.

[0258] Furthermore, 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.

[0259] (Implementation Method 4)

[0260] The structure 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.

[0261] For example, in TBoMS, to improve the efficiency of uplink resource utilization, sometimes the following are allowed: Figure 15 The PUSCH resources allocated to TBoMS within a time slot are different in each time slot within TOT.

[0262] In this embodiment, the terminal 200 may, for example, be based on the number of PUSCH symbols as a reference (e.g., denoted as "L"). ref The reference resource is calculated based on the number of PUSCH symbols (the baseline value for the number of symbols) L. ref For example, it could be the number of symbols constituting a time slot (L) ref =14), or other values.

[0263] Additionally, terminal 200 can, for example, be based on the number of reference coding bits N corresponding to the reference resource. ref The slot index n within TOT, and the ratio of the actual number of symbols used for PUSCH transmission in each slot to the number of PUSCH symbols used as a reference (e.g., denoted as "γ"), determine the variable RV position (read start bit position on the circular buffer) in each slot of TBoMS.

[0264] Furthermore, 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.

[0265] Additionally, the reference resource can be the amount of resources in a time slot preceding the time slot used for rate matching, independent of the rate matching result (read result) of the coded data in that time slot. For example, the reference resource can be the amount of resources independent of the presence or absence of UCI multiplexing. Alternatively, the reference resource can be, for example, the amount of resources independent of whether PUSCH transmissions were discarded due to dynamic SFI notification, UL CI, or allocation of high-priority uplink transmissions.

[0266] For example, the reference resource could also be the number of PUSCH symbols allocated as a reference (e.g., L). ref =14) is the amount of resources sent by PUSCH (e.g., number of REs). As an example, the reference resource amount N can be calculated based on the following equation (9) or equation (10). RE .

[0267] [Mathematical Expression 9]

[0268]

[0269] [Mathematical Expression 10]

[0270]

[0271] In equation (9), the upper limit of the number of REs within a time slot is set to, for example, 156. It should be noted that the upper limit of the number of REs within a time slot is not limited to 156 and can be other values.

[0272] In equations (9) and (10), n PRB This is the number of resource blocks (e.g., PRBs) allocated to TBoMS for transmission. Alternatively, N' in equations (9) and (10) can be calculated, for example, based on the following equation (11). RE .

[0273] [Mathematical Expression 11]

[0274]

[0275] in,

[0276] The average number of subcarriers per resource block (e.g., 12).

[0277] The number of PUSCH symbols used as a reference (e.g., 14).

[0278] : Number of REs for DMRS transmitted by PUSCH in the front-end slots allocated within the TOT

[0279] : Use RRC to notify terminal 200 of the overhead coefficient.

[0280] Alternatively, the reference resource quantity N calculated according to equation (9) or equation (10) can be used, for example. RE The number of reference coding bits N corresponding to the reference resource is calculated using the following equation (12). ref .

[0281] [Mathematical Expression 12]

[0282]

[0283] in,

[0284] Modulation order

[0285] Number of MIMO layers.

[0286] Furthermore, the ratio γ of the actual number of symbols used in each time slot's PUSCH transmission to the baseline number of PUSCH symbols can be derived from the actual number of PUSCH symbols L in the nth time slot. n With the number of PUSCH symbols L as the benchmark REF The ratio L n / L ref Provided. For example, in Figure 15 In the example shown, it could be that in L REF When γ = 14, set it as γ0 = L0 / L ref =14 / 14=1, set as γ1=L1 / L ref =4 / 14 = 2 / 7, and set as γ2 = L2 / L ref =12 / 14=6 / 7.

[0287] Terminal 200, for example, obtains the reference coding bits N according to the reference resource. ref The RV position s is given by the time slot index n and ratio γ within the TOT. n Read the encoded bits corresponding to the amount of PUSCH resources allocated to that time slot in the nth time slot within the TOT, and map the read encoded bits to the PUSCH resources in the nth time slot.

[0288] For example, the RV position s in the nth time slot of TOT n It can be provided by the following equation (13).

[0289] [Mathematical Expression 13]

[0290]

[0291] Here, N RVx It is the RV position used by the front-end time slot within the TOT (e.g., the bit position specified by RV0, RV1, RV2, or RV3).

[0292] According to this embodiment, the terminal 200 determines the RV position of each of the multiple time slots within the TOT based on the ratio γ of the number of symbols used for PUSCH transmission in each time slot to the reference number of PUSCH symbols. By using the ratio γ, the number of reference coded bits N corresponding to the reference resources can be adjusted according to the amount of PUSCH transmission resources allocated to each time slot (in other words, the ratio of the reference number of PUSCH symbols to the number of PUSCH symbols in each time slot). ref Therefore, it can improve the accuracy of rate matching in each time slot and improve decoding performance.

[0293] (Implementation Method 5)

[0294] The structure 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.

[0295] In this embodiment, the same situation as in embodiment 4 will be described, which refers to the situation where it is permissible to have the following conditions: Figure 15 The PUSCH resources allocated to TBoMS within a time slot are different in each time slot within TOT.

[0296] For example, in Embodiments 1 to 4, a method was described that sets reference resources for multiple time slots within a TOT and determines the RV position of each of the multiple time slots within a TOT based on the reference resources.

[0297] In this embodiment, for example, a method is described in which reference resources are set separately for each of the multiple time slots within the TOT, and the RV position of each time slot is determined based on the reference resources of each of the multiple time slots within the TOT.

[0298] For example, terminal 200 can calculate the number of reference coded bits (e.g., denoted as "N") based on the reference resources of that time slot. RE,n The slot index n in TOT determines the variable RV position (read start bit position on the circular buffer) in the nth slot of TBoMS.

[0299] Furthermore, 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.

[0300] For example, the reference resource in the nth time slot within the TOT can also be the amount of resources allocated to the PUSCH transmission in the nth time slot without considering UCI multiplexing (e.g., the number of REs). As an example, the amount of reference resource N in the nth time slot within the TOT can be calculated based on the following equation (14) or equation (15). RE,n .

[0301] [Mathematical Expression 14]

[0302]

[0303] [Mathematical Expression 15]

[0304]

[0305] In equation (14), the upper limit of the number of REs within a time slot is set to, for example, 156. However, the upper limit of the number of REs within a time slot is not limited to 156 and can be other values.

[0306] In equations (14) and (15), n PRB This is the number of resource blocks (e.g., PRBs) allocated to TBoMS for transmission. Alternatively, N' in equations (14) and (15) can be calculated, for example, based on the following equation (16). RE .

[0307] [Mathematical Expression 16]

[0308]

[0309] in,

[0310] The average number of subcarriers per resource block (e.g., 12).

[0311] The number of OFDM symbols transmitted by the PUSCH in the nth time slot allocated within the TOT.

[0312] : The number of REs for DMRS transmitted by the PUSCH in the nth time slot within the TOT

[0313] : Use RRC to notify terminal 200 of the overhead coefficient.

[0314] Alternatively, the reference resource quantity N calculated according to equation (14) or equation (15) can be used, for example. RE,n Based on the following equation (17), calculate the number of reference coding bits N corresponding to the reference resource in the nth time slot within the TOT. ref (n).

[0315] [Mathematical Expression 17]

[0316]

[0317] in,

[0318] Modulation order

[0319] Number of MIMO layers.

[0320] Terminal 200, for example, obtains the reference coding bits N according to the reference resource corresponding to the nth time slot. ref (n) and the RV location s provided by the time slot index n within TOT. n Read the encoded bits corresponding to the amount of PUSCH resources allocated to that time slot in the nth time slot within the TOT, and map the read encoded bits to the PUSCH resources in the nth time slot.

[0321] For example, the RV position s in the nth time slot of TOT n It can be provided by the following equation (18).

[0322] [Mathematical Expression 18]

[0323]

[0324] Here, N RVx It is the RV position used by the front-end time slot within the TOT (e.g., the bit position specified by RV0, RV1, RV2, or RV3).

[0325] According to this embodiment, the terminal 200 sets reference resources separately for each of the multiple time slots within the TOT. By setting reference resources separately, the terminal 200 can, for example, map the encoded bits to the resources within the time slot according to the amount of resources allocated to each time slot for PUSCH transmission (in other words, the amount of resources allocated to each time slot for PUSCH transmission). Therefore, the accuracy of rate matching in each time slot can be improved, and the decoding performance can be improved.

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

[0327] Furthermore, according to this embodiment, for example, the parameters used to determine the RV position of each time slot are the number of reference coding bits and the time slot index, which correspond to the reference resources of each time slot that are not dependent on UCI multiplexing. Therefore, it has the advantage of simplifying the processing of the terminal 200.

[0328] (Implementation Method 6)

[0329] The structure 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.

[0330] As described above, the time-domain resources allocated to TBoMS can consist of multiple TOTs. In this embodiment, when the time-domain resources allocated to TBoMS consist of multiple TOTs, the RV position (read start bit position on the circular buffer) of the front-end time slot of each TOT can be determined according to one of the following methods.

[0331] <Method 1>

[0332] In Method 1, the RV position (read start bit position on the circular buffer) in the front-end time slot within the 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).

[0333] For example, terminal 200 can determine the RV position for PUSCH transmitted in the front-end slots of each TBoMS based on, for example, the RV field contained in the DCI. For instance, in the case of scheduling TBoMS transmissions according to a DCI format containing a 2-bit RV field, such as... Figure 16 As shown, the RV applied to the front-end slot of the m-th TOT can also be set.

[0334] For example, in Figure 16 In the case where the 2-bit RV field represents "2", terminal 200 can sequentially set the RV position in the front-end time slot to RV2, RV3, RV1, and RV0, starting from the TOT of the front-end within TBoMS. For Figure 16 Other values ​​for the RV field shown can also be set in the same way. Furthermore, the RV position applied to the respective front-end slots of multiple TOTs is not limited to... Figure 16 The example shown.

[0335] According to method 1, the RV position of the front-end time slot in each of the multiple TOTs within TBoMS is set to a predetermined RV position, thus simplifying the processing of terminal 200. Additionally, for example, as... Figure 16 As shown, the RV position of the front-end time slot in each of the multiple TOTs is set to the specified RV position in the circular buffer, which makes it easy to send all the encoded bits stored in the circular buffer and improves decoding performance.

[0336] <Method 2>

[0337] In method 2, the RV position (read start bit position on the circular buffer) in the front-end slot within the TOT can be variably set. For example, the RV position of the front-end slot within the TOT can be determined based on reference resources (e.g., reference coding bit count).

[0338] For example, the RV position s in the front-end slot of the m-th TOT (e.g., n=0). m,0 It can be provided by the following equation (19).

[0339] [Mathematical Expression 19]

[0340]

[0341] in,

[0342] The RV position used by the front-end time slot within the front-end TOT (e.g., the bit position specified by RV0, RV1, RV2, or RV3).

[0343] The number of time slots contained in TOT

[0344] Reference encoding bit count.

[0345] Furthermore, Equation (19) is an example of the case where each TOT contains the same number of time slots.

[0346] When the number of time slots contained in each TOT is set individually (for example, the number of time slots contained in each TOT may be different), the RV position s in the front-end time slot of the m-th TOT is... m,0 It can also be given by the following equation (20).

[0347] [Mathematical Expression 20]

[0348]

[0349] in, It is the number of time slots contained in the m-th TOT.

[0350] According to method 2, since the RV position in the front-end slot of each of the multiple TOTs in TBoMS can be variably set 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.

[0351] The above describes various implementation methods of one embodiment of this disclosure.

[0352] (Variation Example 1)

[0353] In TBoMS, TBS can also be calculated using, for example, the following method.

[0354] The TBS can be determined by multiplying the TBS calculated based on the amount of resources (e.g., number of symbols or number of REs) allocated to the front-end slots within the TOT by a scaling factor greater than 1. For example, the amount of resources (number of REs) N allocated to the front-end slots for PUSCH transmission can be calculated based on the following equation (21). RE .

[0355] [Mathematical Expression 21]

[0356]

[0357] In equation (21), the upper limit of the number of REs within a time slot is set to, for example, 156. It should be noted that the upper limit of the number of REs within a time slot is not limited to 156 and can be other values.

[0358] In equation (21), n PRB This is the number of resource blocks (e.g., PRBs) allocated to PUSCH for transmission. Alternatively, N' in equation (21) can be calculated, for example, based on the following equation (22). RE .

[0359] [Mathematical Expression 22]

[0360]

[0361] in,

[0362] The average number of subcarriers per resource block (e.g., 12).

[0363] The number of OFDM symbols transmitted by the PUSCH allocated to the front-end time slot.

[0364] : Number of REs for DMRS transmitted by PUSCH allocated to the front-end time slot

[0365] : Use RRC to notify terminal 200 of the overhead coefficient.

[0366] For example, the number of OFDM symbols transmitted by the PUSCH allocated to the front-end time slot can be notified to the terminal 200 using information related to the symbol length of the Time Domain Resource Allocation (TDRA).

[0367] Alternatively, the resource amount N allocated to the front-end time slot for PUSCH transmission, calculated according to equation (21), can be used. RE For example, the TB size N is calculated based on the following equation (23). info .

[0368] [Mathematical Expression 23]

[0369]

[0370] in,

[0371] Coding rate

[0372] Modulation order

[0373] MIMO layer number

[0374] : Scaling factor greater than 1.

[0375] Terminal 200 can, for example, use the value of TBS used to calculate PUSCH transmission to calculate the number of reference coded bits (N) corresponding to the reference resource amount used to determine the RV position of each slot within the TOT. ref For example, N in equation (21) during the TBS calculation process can also be appropriated. RE N' of equation (22) RE At least one of the above embodiments is used to calculate the amount of reference resources (e.g., the number of reference coding bits).

[0376] By redirecting the value used to calculate TBS to the calculation reference resources, the amount of processing or memory used in terminal 200 can be reduced.

[0377] The above explains the variations.

[0378] Furthermore, in a non-limiting embodiment of this disclosure, the reference resource is not limited to being set based on resources in the front-end timeslot or the initial normal timeslot within the TOT; it may also be set based on resources in a specific timeslot within the TOT.

[0379] Furthermore, in a non-limiting embodiment of this disclosure, although the processing of option 2 (rate matching of time slot units) with variable RV position has been described, it is not limited thereto. For example, the processing of option 3 (rate matching of TOT units) with variable RV position can also be performed. In this case, for example, the processing of time slot units and the time slot-specific or general parameters in the above embodiments can be replaced with the processing of TOT units and the TOT-specific or general parameters.

[0380] Additionally, in a non-limiting embodiment of this disclosure, TOT can also be a single TBoMS transmission unit. Furthermore, repeated transmissions (repetitions) of multiple TBoMS transmission units can also be applied. In this case, for example, TOT in the above embodiment can be replaced with a single TBoMS transmission unit.

[0381] Additionally, in a non-limiting embodiment of this disclosure, the number of reference coded bits may also be the number of bits in an LDPC (Lowdensity Parity Check) code excluding filler bits. For example, in the case where the i-th time slot constituting the TOT in equation (18) above contains filler bits, the RV position s in the n-th time slot constituting the TOT... n It can be provided by the following formula (24).

[0382] [Mathematical Expression 24]

[0383]

[0384] Here, It is the number of fill bits in the i-th time slot.

[0385] Additionally, in a non-limiting embodiment of this disclosure, the size of the recirculating buffer or the length of the recirculating buffer N can also be used. cb The RV position is calculated using a modulo operation. For example, in equation (18) above, the RV position s in the nth time slot of the TOT is... n It can be given by the following equation (25).

[0386] [Mathematical Expression 25]

[0387]

[0388] Additionally, in one non-limiting embodiment of this disclosure, the PUSCH resources available for PUSCH transmission are not limited to containing uplink symbols (U), but may also include flexible symbols (F).

[0389] Furthermore, in one non-limiting embodiment of this disclosure, although TBoMS transmission is 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. Additionally, transmission using multiple time slots is not limited to PUSCH transmission and may also be the transmission of other channels or signals.

[0390] In one non-limiting embodiment of this disclosure, 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, the various embodiments or variations are not limited to uplink transmission, but may also be applied to either downlink transmission or sidelink transmission.

[0391] The implementation methods, variations, and methods in this non-limiting embodiment may be interchanged or differ according to the communication method (type) or channel / signal category.

[0392] Furthermore, the name of the information element or the name of the parameter set for the information element used in one non-limiting embodiment of this disclosure is an example, and other names may also be used. Additionally, the values ​​of parameters exemplified in various embodiments or variations, 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 within a time slot, the setting of the time slot category (e.g., "D", "U", or "F") within a TOT, and the specified number of RV positions, are examples, and other values ​​may also be used.

[0393] In addition, the term "...part" in the above embodiments can also be replaced with other terms such as "...circuitry", "...device", "...unit" or "...module".

[0394] (Replenish)

[0395] Information indicating whether terminal 200 supports the functions, actions, or processes shown in the above embodiments and variations can also be sent (or notified) by terminal 200 to base station 100 as capability information or capability parameters of terminal 200.

[0396] The capability information may also include the following information elements (IE): each of which individually indicates whether the terminal 200 supports at least one of the functions, actions, and processes shown in the above embodiments and variations. Alternatively, the capability information may also include the following information elements: each of which indicates whether the terminal 200 supports a combination of two or more of the functions, actions, and processes shown in the above embodiments and variations.

[0397] 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 the capability information received from terminal 200. Base station 100 can implement actions, processes, or controls corresponding to 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.

[0398] Furthermore, if terminal 200 does not support some of the functions, actions, or processes shown in the above embodiments and variations, this can be replaced by a limitation on such a portion of the functions, actions, or processes in terminal 200. For example, information or requests related to such limitations can also be notified to base station 100.

[0399] Information related to the capabilities or limitations of terminal 200 may be defined in a standard, or may be implicitly communicated to base station 100 in association with information known to base station 100 or information sent to base station 100.

[0400] (Control signal)

[0401] In this disclosure, the downlink control signal (information) associated with this disclosure can be a signal (information) transmitted in the physical layer PDCCH, or a signal (information) transmitted in the higher layer MAC (Medium Access Control) CE (Control Element) or RRC. Alternatively, a predefined signal (information) can also be used as the downlink control signal.

[0402] The uplink control signals (information) associated with this disclosure can be signals (information) transmitted in the physical layer PUCCH, or signals (information) transmitted in the higher layer MAC CE or RRC. Alternatively, the uplink control signals can be predefined signals (information). Furthermore, the uplink control signals can be replaced with UCI (Uplink Control Information), first-stage SCI (Sidelink Control Information), or second-stage SCI.

[0403] (Base station)

[0404] 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 (BaseStation), BTS (Base Transceiver Station), host, gateway, etc. Additionally, in sidelink communication, the terminal can also act as the base station. A base station can also be a relay device for communication between a high-level relay node and the terminal. Furthermore, a base station can also be a roadside device.

[0405] (Uplink / Downlink / Sidelink)

[0406] This disclosure can be applied to any link in the uplink, downlink, and sidelink. For example, this disclosure can be applied to the uplink PUSCH, PUCCH, PRACH (Physical Random Access Channel), downlink PDSCH, PDCCH, PBCH (Physical Broadcast Channel), and sidelink PSSCH (Physical Sidelink Shared Channel), PSCCH (Physical Sidelink Control Channel), and PSBCH (Physical Sidelink Broadcast Channel).

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

[0408] (Data Channel / Control Channel)

[0409] This disclosure can be applied to any channel in the data channel and the control channel. For example, the channels of this disclosure can also be replaced with PDSCH, PUSCH, PSSCH of the data channel and PDCCH, PUCCH, PBCH, PSCCH, PSBCH of the control channel.

[0410] (Reference signal)

[0411] In this disclosure, the reference signal is a signal known to both the base station and the terminal, and is sometimes referred to as "RS (Reference Signal)" or "pilot signal". The reference signal can also be one of the following: DMRS (Demodulation Reference Signal), 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).

[0412] (Time interval)

[0413] In this disclosure, the unit of time resource is not limited to one or a combination of time slots and symbols. For example, it can be a frame, superframe, subframe, time slot, sub-time slot, micro-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 one time slot is not limited to the number of symbols exemplified in the above embodiments, and can also be other numbers of symbols.

[0414] (frequency band)

[0415] This disclosure can be applied to any band domain, whether it is an authorized band domain or an unauthorized band domain.

[0416] (communication)

[0417] This disclosure can be applied to any communication in base station-terminal communication (Uu link communication), terminal-to-terminal communication (sidelink communication), and V2X (Vehicle to Everything) communication. For example, the channels in this disclosure can be replaced with PSCCH, PSSCH, PSFCH (Physical Sidelink Feedback Channel), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.

[0418] Furthermore, this disclosure can be applied to any network, including terrestrial networks and non-terrestrial networks (NTNs) that use satellites or High Altitude Pseudo Satellites (HAPS). Additionally, this disclosure can also be applied to terrestrial networks with transmission delays greater than the symbol length or time slot length, such as networks with large cell sizes and ultra-wideband transmission networks.

[0419] (Antenna Port)

[0420] An antenna port refers to a logical antenna (antenna array) consisting of one or more physical antennas. That is, an antenna port does not necessarily refer to a single physical antenna; sometimes it refers to an array antenna composed of multiple antennas. For example, instead of specifying the number of physical antennas constituting an antenna port, it is defined as the smallest unit that the terminal can transmit a reference signal. Additionally, an antenna port is sometimes defined as the smallest unit multiplied by a precoding vector.

[0421] <5G NR System Architecture and Protocol Stack>

[0422] To realize the next version of fifth-generation mobile phone technology (also known simply as "5G"), which includes the development of a new radio access technology (NR) operating in the frequency range up to 100 GHz, 3GPP is continuing its work. The first version of the 5G standard was completed at the end of 2017, thus enabling the transition to the trial production of terminals (e.g., smartphones) according to the 5G NR standard and commercial deployment.

[0423] For example, the overall system architecture envisions a gNB-RAN (Next Generation Radio Access Network). The gNB provides UE-side termination for the NG radio access user plane (SDAP (Service Data Adaptation Protocol) / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY (Physical Layer)) and control plane (RRC) protocols. gNBs are interconnected via the Xn interface. Additionally, 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., a specific core entity implementing the AMF) via the NG-C interface, and to the UPF (User Plane Function) (e.g., a specific core entity implementing the UPF) via the NG-U interface. Figure 17 This refers to the NG-RAN architecture (e.g., refer to 3GPP TS 38.300 v15.6.0, section 4).

[0424] 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 (refer to section 6.4 of TS 38.300)) sublayer, the RLC (Radio Link Control (refer to section 6.3 of TS 38.300)) sublayer, and the MAC (Media Access Control (refer to section 6.2 of TS 38.300)) sublayer, which terminates on the network side in the gNB. Additionally, a new Access Stratum (AS) sublayer (SDAP: Service Data Adaptation Protocol) has been incorporated into PDCP (e.g., refer to section 6.5 of 3GPP TS 38.300). Furthermore, a control plane protocol stack is defined for NR (e.g., refer to TS 38.300, section 4.4.2). A summary of Layer 2 functionality is described 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.

[0425] For example, the media access control layer handles the multiplexing of logical channels, scheduling of processing involving various parameter sets, and various functions associated with scheduling.

[0426] For example, the Physical Layer (PHY) is responsible for encoding, PHY HARQ (Physical Layer Hybrid Automatic Repeat Request) processing, modulation, multi-antenna processing, and mapping signals to appropriate physical time-frequency resources. Additionally, the Physical Layer handles the mapping of physical channels to transport channels. The Physical Layer provides services to the MAC Layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used to transmit a specific transport channel; each transport channel is mapped to a corresponding physical channel. For example, in physical channels, uplink physical channels include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel), while downlink physical channels include PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel).

[0427] In NR use cases / extended scenarios, enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC) may have multiple necessary conditions in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates approximately three times that of IMT-Advanced (20Gbps in downlink and 10Gbps in uplink) and effective (user-experienced) data rates. On the other hand, in the case of URLLC, more stringent necessary conditions are proposed for ultra-low latency (0.5ms latency in both UL and DL) and high reliability (within 1ms, 1-10-5). Finally, in mMTC, high connection density (1,000,000 devices / km in urban environments) is preferably required. 2 ), wide coverage in harsh environments and extremely long battery life (15 years) for inexpensive devices.

[0428] Therefore, a set of OFDM parameters suitable for one use case (e.g., subcarrier spacing (SCS), OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) may be ineffective for 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 (also known as "TTI"). Moreover, in extended scenarios with large channel delay spread, it is preferable to require a longer CP length than in scenarios with shorter delay spread. The subcarrier spacing can also be optimized depending on the situation to maintain the same CP overhead. NR supports more than one subcarrier spacing value. Correspondingly, subcarrier spacings of 15kHz, 30kHz, 60kHz, etc., are currently considered. The symbol length Tu and the subcarrier spacing Δf are directly related according to the formula Δf = 1 / Tu. Similar to LTE systems, the term "resource element" can be used to represent the smallest unit of resources consisting of a subcarrier of the length of one OFDM / SC-FDMA (Single-Carrier Frequency Division Multiple Access) symbol.

[0429] In the new 5G-NR wireless system, resource grids for subcarriers and OFDM symbols are defined in both the uplink and downlink for each parameter set and each carrier. Each element of the resource grid is called a "resource element," which is determined based on the frequency index in the frequency domain and the symbol position in the time domain (refer to 3GPP TS 38.211 v15.6.0).

[0430] <Functional Separation between NG-RAN and 5GC in 5G NR>

[0431] Figure 18 This indicates the functional separation between NG-RAN and 5GC. The logical node of NG-RAN is either gNB or ng-eNB. 5GC has logical nodes AMF, UPF, and SMF (Session Management Function).

[0432] For example, gNB and ng-eNB host the following main functions:

[0433] - Functions such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, and Radio Resource Management (RRM) that dynamically allocates (schedules) resources to the UE in both the uplink and downlink links;

[0434] - Data IP (Internet Protocol) header compression, encryption, and integrity protection;

[0435] - Selection of AMF when attaching a UE in situations where the route to the AMF cannot be determined based on the information provided by the UE;

[0436] - Routing to user plane data towards UPF;

[0437] - Routing of control plane information toward AMF;

[0438] - Setting and canceling connections;

[0439] - Scheduling and sending paging messages;

[0440] - The scheduling and transmission of system broadcast information (originating from AMF or Operation, Admission, and Maintenance functions (OAM));

[0441] - Setting up measurements and measurement reports for mobility and scheduling;

[0442] - Packet markings for transmission class in the uplink;

[0443] -Session management;

[0444] -Support for network slicing;

[0445] - QoS (Quality of Service) flow management and mapping to data radio bearers;

[0446] Support for UEs in RRC_INACTIVE (RRC inactive) state;

[0447] - NAS (Non-Access Stratum) message distribution function;

[0448] - Sharing of wireless access networks;

[0449] - Dual connectivity;

[0450] - Close collaboration between NR and E-UTRA (Evolved Universal Terrestrial Radio Access).

[0451] The Access and Mobility Management Function (AMF) administers the following main functions:

[0452] - Function to terminate Non-Access Stratum (NAS) signaling;

[0453] -Security of NAS signaling;

[0454] - Security controls at the access layer (AS);

[0455] - Core Network (CN) inter-node signaling for mobility between 3GPP access networks;

[0456] - The possibility of a UE reaching idle mode (including control and execution of paging retransmission);

[0457] -Management of the registered area;

[0458] - Support for intra-system mobility and inter-system mobility;

[0459] -Access authentication;

[0460] - Access licenses that include roaming permission checks;

[0461] - Mobility management controls (subscription and policies);

[0462] -Support for network slicing;

[0463] - Selection of Session Management Function (SMF).

[0464] In addition, the User Face Function (UPF) hosts the following main functions:

[0465] - Anchor points for intra-RAT (Radio Access Technology) mobility / inter-RAT (where applicable) mobility;

[0466] - External PDU (Protocol Data Unit) session points used for interconnection with data networks;

[0467] - Packet routing and forwarding;

[0468] - Enforcement of policy rules in group checks and user-facing aspects;

[0469] - Reports on business usage;

[0470] - Uplink classifier used to support routing of service flows toward the data network;

[0471] - Branching points used to support multi-homed PDU sessions;

[0472] - For user plane QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement);

[0473] - Uplink service verification (SDF (Service Data Flow) mapping to QoS flow);

[0474] - Downlink packet buffering and downlink data notification triggering functions.

[0475] Finally, the Session Management Function (SMF) administers the following main functions:

[0476] -Session management;

[0477] - The allocation and management of UE IP addresses;

[0478] -Selection and control of UPF;

[0479] - A function for setting traffic steering in the User Plane Function (UPF) to direct traffic to the appropriate destination;

[0480] - Enforcing policies and QoS in the control section;

[0481] - Notification of downlink data.

[0482] <The process of setting up and resetting RRC connection>

[0483] Figure 19 This refers to several interactions between the UE, gNB, and AMF (5GC entity) when the UE in the NAS part transitions from RRC_IDLE (RRC idle) to RRC_CONNECTED (RRC connected) (refer to TS 38.300 v15.6.0).

[0484] RRC is a higher-level signaling (protocol) used for UE and gNB configuration. Through this transition, the AMF prepares UE context data (which includes, for example, PDU session context, security keys, UE radio capabilities, and UE security capabilities) and sends it to the gNB along with an initial context setting request. Next, the gNB and UE activate AS security together. The gNB sends a SecurityModeCommand message to the UE, and the UE responds with a SecurityModeComplete message, thereby activating AS security. Then, the gNB sends an RRCReconfiguration message to the UE, and receives an RRCReconfigurationComplete message from the UE for this message, thus performing the reconfiguration of Signaling RadioBearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, since SRB2 and DRB are not configured, the steps related to RRC reconfiguration can be omitted. Finally, the gNB notifies the AMF that the configuration process is complete using the Initial Context Setup Reply.

[0485] Therefore, this disclosure provides an entity (e.g., AMF, SMF, etc.) for a fifth-generation core network (5GC), comprising: a control circuit that, upon operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmission unit that, upon operation, transmits an initial context setting message to the gNodeB via the NG connection to configure the signaling radio bearer between the gNodeB and the User Equipment (UE). Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling containing an Information Element (IE) to the UE via the signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation settings.

[0486] <Application Scenarios of IMT after 2020>

[0487] Figure 20This section outlines several use cases for 5G NR. Within the 3rd Generation Partnership Project New Radio (3GPP NR), three use cases supporting a wide variety of services and applications, conceived through IMT-2020, have been studied. Planning for the first phase of specifications for enhanced mobile broadband (eMBB) has been completed. Current and future work, in addition to gradually expanding eMBB support, includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC). Figure 20 Several examples illustrating conceptual application scenarios for IMT after 2020 (e.g., referring to ITU-R M.2083). Figure 2 ).

[0488] URLLC use cases have strict requirements related to performance aspects such as throughput, latency, and availability. URLLC is conceived as a key technology for enabling wireless control of future industrial production or manufacturing processes, remote medical surgery, automation of power transmission and distribution in smart grids, and traffic safety applications. Ultra-high reliability of URLLC is supported by defining technologies that meet the requirements set by TR38.913. In NR URLLC version 15, a crucial requirement is a target user plane latency of 0.5ms in the UL (uplink) and 0.5ms in the DL (downlink). For a single packet transmission, the overall requirement for URLLC is a block error rate (BLER) of 1E-5 for a 32-byte packet size with a user plane latency of 1ms.

[0489] Considering the physical layer, numerous methods are available to improve reliability. Current possibilities for reliability enhancement include defining additional CQI (Channel Quality Indicator) tables for URLLC, a more compact DCI format, and PDCCH iteration. However, as NR (a crucial prerequisite for NR URLLC) becomes more stable and is further developed, this scope can be expanded to achieve ultra-high reliability. Specific use cases for NR URLLC in version 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and other critical applications.

[0490] Furthermore, the technical enhancements for NR URLLC aim to improve latency and reliability. Latency enhancements include configurable parameter sets, non-slot-based scheduling utilizing flexible mapping, unlicensed (already licensed) uplinks, slot-level repetition in the data channel, and pre-emption in the downlink. Pre-emption means stopping transmissions with allocated resources and using those resources for later-requested transmissions that require lower latency / higher priority. Therefore, a permitted transmission is replaced by a subsequent transmission. Pre-emption can be applied regardless of the specific service type. For example, a transmission for service type A (URLLC) can be replaced by a transmission for service type B (eMBB, etc.). Reliability enhancements include a dedicated CQI / MCS table for a target BLER of 1E-5.

[0491] The use cases for mMTC (massive machine-type communications) are characterized by a large number of connected devices that transmit relatively small amounts of data that are not easily affected by latency. These devices require low cost and very long battery life. From NR's perspective, utilizing very narrow bandwidth segments is a solution to save UE power and extend its battery life.

[0492] As mentioned above, the potential for improved reliability in NR is further expanded. It is one of the essential conditions for all situations; for example, high or ultra-high reliability is a crucial requirement related to URLLC and mMTC. From both wireless and network perspectives, reliability can be improved through several mechanisms. Generally, there are two to three important areas that could potentially contribute to improved reliability. These areas include compact control channel information, data / control channel iteration, and diversity related to the frequency, time, and / or spatial domains. These areas can be used universally to improve reliability, independent of specific communication scenarios.

[0493] Regarding NR URLLC, further use cases with more stringent requirements are envisioned, such as factory automation, transportation, and power transmission. Stricter requirements refer to high reliability (reaching level 10⁻⁶), high availability, a packet size of 256 bytes, and time synchronization of approximately several microseconds (μs) (capable of corresponding to use cases, with values ​​set to 1 μs or several microseconds depending on the frequency range and short latency of approximately 0.5ms to 1ms (e.g., 0.5ms latency in the target user plane)).

[0494] Furthermore, from a physical layer perspective, there are several technical enhancements to NR URLLC. These enhancements include strengthening the PDCCH (Physical Downlink Control Channel) associated with compact DCI, PDCCH repetition, and increased PDCCH monitoring. Additionally, enhancements to UCI (Uplink Control Information) are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback. Furthermore, there may be enhancements to PUSCH and retransmission / repetition related to mini-slot-level frequency hopping. The term "mini-slot" refers to a transmission time interval (TTI) containing fewer symbols than a time slot (a time slot has 14 symbols).

[0495] <QoS Control>

[0496] 5G's QoS (Quality of Service) model is based on QoS flows, supporting both QoS flows that require guaranteed bit rate (GBR) and QoS flows that do not require guaranteed bit rate (non-GBR QoS flows). Therefore, at the NAS level, QoS flows represent the finest granular QoS classification within a PDU session. QoS flows are determined within a PDU session based on the QoS Flow ID (QFI) transmitted via the encapsulation header through the NG-U interface.

[0497] For each UE, 5GC establishes one or more PDU sessions. For each UE, in conjunction with the PDU session, NG-RAN, for example, refers to the previous text. Figure 19 As explained, at least one Data Radio Bearer (DRB) is established. Additionally, DRBs can be subsequently configured in QoS flows added to this PDU session (when to configure this depends on the NG-RAN). The NG-RAN maps packets belonging to various PDU sessions to various DRBs. NAS-level packet filters in the UE and 5GC are used to associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0498] Figure 21 This refers to the non-roaming reference architecture of 5G NR (refer to TS 23.501 v16.1.0, section 4.23). Application Function (AF) (e.g., hosting...) Figure 20The external application server for the illustrated 5G service interacts with the 3GPP core network to provide services. For example, it may access a Network Exposure Function (NEF) to support applications that impact service routing, or it may interact with a policy framework (see Policy Control Function (PCF)) for policy control (e.g., QoS control). Based on operator deployment, operators deem trusted application functions capable of directly interacting with associated network functions. Application functions not permitted by the operator to directly access network functions interact with associated network functions via the NEF, using an open framework accessible to the outside world.

[0499] Figure 21 It also indicates further functional units of the 5G architecture, namely, the Network Slice Selection Function (NSSF), the Network Repository Function (NRF), Unified Data Management (UDM), the Authentication Server Function (AUSF), the Access and Mobility Management Function (AMF), the Session Management Function (SMF), and the Data Network (DN: Data Network, such as services provided by operators, internet access, or services provided by third parties). All or part of the core network's functions and application services can also be deployed and operate in a cloud computing environment.

[0500] Therefore, this disclosure provides an application server (e.g., an AF in a 5G architecture) comprising: a transmitting unit that, in order to establish a PDU session containing a radio bearer between a g node B and a UE corresponding to QoS requirements, sends, during operation, a request containing at least one of URLLC service, eMMB service, and mMTC service to at least one of the functions of 5GC (e.g., NEF, AMF, SMF, PCF, UPF, etc.); and a control circuit that, during operation, performs services using the established PDU session.

[0501] This disclosure can be implemented in software, hardware, or software in cooperation with hardware. The functional blocks used in the above embodiments are implemented partially or wholly as LSIs (Large Scale Integration), and the processes described in the above embodiments can also be controlled partially or wholly by a single LSI or a combination of LSIs. An LSI can be composed of individual chips, or it can be composed of a single chip containing some or all of the functional blocks. An LSI can also include data input and output. Depending on the degree of integration, an LSI can also be referred to as an "IC (Integrated Circuit)," "System LSI," "Super LSI," or "Ultra LSI."

[0502] The method of integrating the LSI is not limited to LSI; it can also be implemented using dedicated circuits, general-purpose processors, or special-purpose processors. Alternatively, it can utilize FPGAs (Field Programmable Gate Arrays) that can be programmed after LSI fabrication, or reconfigurable processors that can reconfigure the connections or settings of the circuit blocks within the LSI. This disclosure can also be implemented for digital or analog processing.

[0503] Furthermore, if advancements in semiconductor technology or the emergence of other derivative technologies lead to integrated circuit technologies that can replace LSIs, these technologies could also be used to integrate functional blocks. There are also possibilities for applications such as biotechnology.

[0504] 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 also include a wireless transceiver and processing / control circuitry. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these units. The wireless transceiver (transmitting unit, receiving unit) may also include an RF (Radio Frequency) module and one or more antennas. The RF module may also include an amplifier, an RF modulator / demodulator, or similar devices. Non-limiting examples of communication devices include: telephones (mobile phones, smartphones, etc.), tablet computers, personal computers (PCs) (laptops, desktops, laptops, etc.), cameras (digital cameras, digital camcorders, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, e-book readers, remote health / telemedicine (remote healthcare / medical prescription) devices, vehicles or transportation vehicles with communication capabilities (cars, airplanes, ships, etc.), and combinations of the various devices described above.

[0505] Communication devices are not limited to portable or movable devices, but also include all kinds of devices, equipment, and systems that cannot be carried or fixed. Examples include: smart home devices (home appliances, lighting equipment, smart meters or meters, control panels, etc.), vending machines, and all other "things" that can exist on the IoT (Internet of Things) network.

[0506] In addition to data communication via cellular systems, wireless LAN (Local Area Network) systems, and communication satellite systems, communication also includes data communication via a combination of these systems.

[0507] In addition, the communication device also includes devices such as controllers or sensors that are connected or linked to a communication device performing the communication functions described in this disclosure. For example, it includes a controller or sensor that generates control signals or data signals used by the communication device to perform the communication functions of the communication device.

[0508] In addition, the communication device includes infrastructure equipment that communicates with or controls the various devices described above (not limited to these), such as base stations, access points, and all other devices, equipment, and systems.

[0509] A communication apparatus according to an embodiment of this disclosure includes: a control circuit that determines the read position of the encoded data of the signal based on the amount of resources of a second interval preceding a first interval in a plurality of intervals allocated for signal transmission in the time domain, independent of the read result of encoded data in the second interval; and a transmission circuit that transmits the signal based on the read position.

[0510] In one embodiment of this disclosure, the resource quantity is a resource quantity that is independent of the presence or absence of uplink control information multiplexing.

[0511] In one embodiment of this disclosure, the amount of resources is independent of whether the transmission of the signal is discarded.

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

[0513] In one embodiment of this disclosure, the control circuit determines the read position based on the number of encoded bits corresponding to the resource quantity and the index of the first interval among the plurality of intervals that is different from the interval in which the transmission of the signal was discarded.

[0514] In one embodiment of this disclosure, the control circuit determines the amount of resources differently depending on whether the front end interval of the time-domain resource is a special time slot.

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

[0516] In one embodiment of this disclosure, the control circuit sets the resource amount individually for each of the plurality of intervals.

[0517] In one embodiment of this disclosure, the time-domain resource includes at least one group consisting of one or more consecutive intervals, wherein the read position in the front-end interval within the group is a predetermined position.

[0518] In one embodiment of this disclosure, the time-domain resource includes at least one group consisting of one or more consecutive intervals, and the communication device determines the read position in the front-end interval within the group based on the amount of the resource.

[0519] In one embodiment of this disclosure, the control circuit uses a value for calculating the transport block size of the signal to calculate the resource quantity.

[0520] A communication apparatus according to an embodiment of this disclosure includes: a control circuit that determines the read position of the encoded data of the signal based on the amount of resources of a second interval preceding a first interval in a plurality of intervals allocated for signal transmission in the time domain, independent of the read result of encoded data in the second interval; and a transmission circuit that receives the signal based on the read position.

[0521] In a communication method according to an embodiment of this disclosure, the communication device performs the following processing: determining the read position of the encoded data of the signal in the first interval based on the amount of resources of a second interval that is earlier than the first interval among a plurality of intervals allocated to signal transmission in the time domain, independent of the read result of the encoded data in the second interval; and transmitting the signal based on the read position.

[0522] In a communication method according to an embodiment of this disclosure, the communication device performs the following processing: determining the read position of the encoded data of the signal in the first interval based on the amount of resources of a second interval that is earlier than the first interval among a plurality of intervals allocated to signal transmission in the time domain, independent of the read result of the encoded data in the second interval; and receiving the signal based on the read position.

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

[0524] Industrial applicability

[0525] One embodiment of this disclosure is useful for wireless communication systems.

Claims

1. A communication device, characterized in that, include: The control circuit determines the read position of the encoded data of the signal in the first time slot from among the multiple time slots allocated for signal transmission, based on the read position of the encoded data in the second time slot which is earlier than the first time slot and the number of encoded bits that can be used for the transmission of encoded data in the second time slot. as well as The transmitting unit transmits the signal based on the read position in the first time slot. The number of encoded bits available for transmission of the encoded data in the second time slot does not depend on the presence or absence of uplink control information multiplexing.

2. The communication device as claimed in claim 1, wherein, The second time slot is the front-end time slot among the plurality of time slots, and the reading position of the encoded data in the second time slot is the position shown in redundancy version 0, 1, 2 or 3.

3. The communication device as claimed in claim 1, wherein, The transmission block size of the signal is calculated by multiplying the amount of resources allocated in a time slot for the transmission of the signal by a scaling factor.

4. The communication device as claimed in claim 3, wherein, The amount of resources allocated to the Physical Uplink Shared Channel (PUSCH) transmission in a time slot is determined based on information related to the symbol length indicated from the base station.

5. The communication device as claimed in claim 1, wherein, Information related to the multiple time slots is notified from the base station via resource allocation information.

6. The communication device as claimed in claim 1, wherein, The signal is transmitted via the Physical Uplink Shared Channel, or PUSCH.

7. A communication method, characterized in that, include: The reading position of the encoded data of the signal in the first time slot is determined based on the reading position of the encoded data in the second time slot, which is earlier than the first time slot, among multiple time slots allocated to the time domain resources for signal transmission, and the number of encoded bits that can be used for the transmission of encoded data in the second time slot. The signal is sent based on the read position in the first time slot. The number of encoded bits available for transmission of the encoded data in the second time slot does not depend on the presence or absence of uplink control information multiplexing.

8. The communication method as described in claim 7, wherein, The second time slot is the front-end time slot among the plurality of time slots, and the reading position of the encoded data in the second time slot is the position shown in redundancy version 0, 1, 2 or 3.

9. The communication method as described in claim 7, wherein, The transmission block size of the signal is calculated by multiplying the amount of resources allocated in a time slot for the transmission of the signal by a scaling factor.

10. The communication method as described in claim 9, wherein, The amount of resources allocated to the Physical Uplink Shared Channel (PUSCH) transmission in a time slot is determined based on information related to the symbol length indicated from the base station.

11. The communication method as described in claim 7, wherein, Information related to the multiple time slots is notified from the base station via resource allocation information.

12. The communication method as described in claim 7, wherein, The signal is transmitted via the Physical Uplink Shared Channel, or PUSCH.

13. An integrated circuit, characterized in that, control: The process of determining the read position of the encoded data of the signal in the first time slot among the multiple time slots allocated for the transmission of the signal is based on the read position of the encoded data in the second time slot that is earlier than the first time slot and the number of encoded bits that can be used for the transmission of encoded data in the second time slot. The processing of sending the signal based on the read position in the first time slot. The number of encoded bits available for transmission of the encoded data in the second time slot does not depend on the presence or absence of uplink control information multiplexing.

14. A communication device, characterized in that, include: The control circuit determines the read position of the encoded data of the signal in the first time slot from among the multiple time slots allocated for signal transmission, based on the read position of the encoded data in the second time slot which is earlier than the first time slot and the number of encoded bits that can be used for the transmission of encoded data in the second time slot. as well as The receiving circuit receives the signal based on the read position in the first time slot. The number of encoded bits available for transmission of the encoded data in the second time slot does not depend on the presence or absence of uplink control information multiplexing.

15. The communication device as claimed in claim 14, wherein, The second time slot is the front-end time slot among the plurality of time slots, and the reading position of the encoded data in the second time slot is the position shown in redundancy version 0, 1, 2 or 3.

16. The communication device as claimed in claim 14, wherein, The transmission block size of the signal is calculated by multiplying the amount of resources allocated in a time slot for the transmission of the signal by a scaling factor.

17. The communication device as claimed in claim 16, wherein, The amount of resources allocated to the Physical Uplink Shared Channel (PUSCH) transmission in a time slot is determined based on information related to the symbol length indicated from the base station.

18. The communication device as claimed in claim 14, wherein, Information related to the multiple time slots is notified from the base station via resource allocation information.

19. The communication device as claimed in claim 14, wherein, The signal is transmitted via the Physical Uplink Shared Channel, or PUSCH.

20. A communication method, characterized in that, include: The reading position of the encoded data of the signal in the first time slot is determined based on the reading position of the encoded data in the second time slot, which is earlier than the first time slot, among multiple time slots allocated to the time domain resources for signal transmission, and the number of encoded bits that can be used for the transmission of encoded data in the second time slot. The signal is received based on the read position in the first time slot. The number of encoded bits available for transmission of the encoded data in the second time slot does not depend on the presence or absence of uplink control information multiplexing.

21. The communication method as described in claim 20, wherein, The second time slot is the front-end time slot among the plurality of time slots, and the reading position of the encoded data in the second time slot is the position shown in redundancy version 0, 1, 2 or 3.

22. The communication method as described in claim 20, wherein, The transmission block size of the signal is calculated by multiplying the amount of resources allocated in a time slot for the transmission of the signal by a scaling factor.

23. The communication method as described in claim 22, wherein, The amount of resources allocated to the Physical Uplink Shared Channel (PUSCH) transmission in a time slot is determined based on information related to the symbol length indicated from the base station.

24. The communication method as described in claim 20, wherein, Information related to the multiple time slots is notified from the base station via resource allocation information.

25. The communication method as described in claim 20, wherein, The signal is transmitted via the Physical Uplink Shared Channel, or PUSCH.

26. An integrated circuit, characterized in that, control: The process of determining the read position of the encoded data of the signal in the first time slot among the multiple time slots allocated for the transmission of the signal is based on the read position of the encoded data in the second time slot that is earlier than the first time slot and the number of encoded bits that can be used for the transmission of encoded data in the second time slot. as well as Based on the read position in the first time slot, the signal is received and processed. The number of encoded bits available for transmission of the encoded data in the second time slot does not depend on the presence or absence of uplink control information multiplexing.

Images