Apparatus for use in a user equipment

Abstract

The present application relates to an apparatus for use in a user equipment (UE), the apparatus comprising logic and circuitry configured to cause the UE to: receive downlink control information (DCI) configured for scheduling a physical uplink shared channel (PUSCH) transmission carrying a transport block (TB) spanning more than one slot; and transmit the PUSCH transmission carrying the TB spanning more than one slot in accordance with the DCI.

Description

[0001] Priority requirements

[0002] This application is based on and claims priority to U.S. Patent Application No. 63 / 080,406, filed September 18, 2020; U.S. Patent Application No. 63 / 123,995, filed December 10, 2020; and U.S. Patent Application No. 63 / 168,816, filed March 31, 2021, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] Embodiments of this disclosure generally relate to the field of wireless communication, and more particularly to apparatus used in user equipment (UE). Background Technology

[0004] Mobile communication has evolved from early voice systems to today's highly complex integrated communication platforms. 5G, or new radio (NR) wireless communication systems, will provide various users and applications with access to information and data sharing anytime, anywhere. Attached Figure Description

[0005] Embodiments of this disclosure will be illustrated in the accompanying drawings by way of example rather than limitation, wherein similar reference numerals refer to similar elements.

[0006] Figure 1 A flowchart of a method used in a UE according to an embodiment of this disclosure is shown.

[0007] Figure 2 An example of time-domain resource allocation for carrying PUSCH transmissions spanning more than one time slot is shown according to an embodiment of this disclosure.

[0008] Figure 3 Another example of time-domain resource allocation for carrying PUSCH transmissions spanning more than one time slot, according to embodiments of this disclosure, is shown.

[0009] Figure 4 This illustrates yet another example of time-domain resource allocation for carrying PUSCH transmissions spanning more than one timeslot, according to embodiments of the present disclosure.

[0010] Figure 5 An example of inter-slot frequency hopping for carrying PUSCH transmissions spanning more than one time slot is shown according to an embodiment of the present disclosure.

[0011] Figure 6 An example of the cancellation of a PUSCH transmission carrying more than one time slot TB, according to an embodiment of this disclosure, is shown.

[0012] Figure 7 A schematic diagram of a network according to various embodiments of the present disclosure is shown.

[0013] Figure 8 A schematic diagram of a wireless network according to various embodiments of the present disclosure is shown.

[0014] Figure 9 A block diagram is shown of components according to some example embodiments of the present disclosure that are capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more methods discussed herein. Detailed Implementation

[0015] Various aspects of the illustrative embodiments will be described using terminology commonly used by those skilled in the art to convey the essence of this disclosure to them. However, it will be apparent to those skilled in the art that many alternative embodiments can be implemented using portions of the described aspects. Specific figures, materials, and configurations are given for illustrative purposes to provide a thorough understanding of the illustrative embodiments. However, it will be apparent to those skilled in the art that alternative embodiments can be implemented without these specific details. In other instances, well-known features may be omitted or simplified to avoid obscuring the illustrative embodiments.

[0016] Furthermore, the various operations are described sequentially as a plurality of discrete operations in a manner most conducive to understanding the illustrative embodiments; however, the order of description should not be construed as implying that these operations are necessarily sequentially related. In particular, these operations do not need to be performed in the order presented.

[0017] The phrases “in an embodiment,” “in one embodiment,” and “in some embodiments” are used repeatedly throughout this document. These phrases do not typically refer to the same embodiment; however, they may refer to the same embodiment. Unless the context otherwise requires, the terms “comprising,” “having,” and “including” are synonyms. The phrases “A or B” and “A / B” mean “(A), (B), or (A and B).”

[0018] The expectation is that NR wireless communication systems will be a unified network / system designed to meet diverse and sometimes conflicting performance dimensions and services. These varied, multidimensional needs are driven by different services and applications. Generally, NR wireless communication systems will build upon 3GPP Long Term Evolution (LTE)-Advanced (LTE-A) technologies to enrich people's lives with better, simpler, and seamless wireless connectivity solutions. NR wireless communication systems will enable wireless connectivity for all things and deliver fast, rich content and services.

[0019] For cellular systems, coverage is a critical factor for successful operation. Compared to LTE wireless communication systems, NR wireless communication systems can be deployed at relatively higher carrier frequencies in Frequency Range 1 (FR1), such as 3.5 GHz. In this case, coverage loss is expected due to greater path loss, making it more challenging to maintain adequate quality of service. Typically, uplink coverage is a bottleneck for system operation, given the low transmit power at the user equipment (UE) side.

[0020] For NR wireless communication systems, Physical Uplink Shared Channel (PUSCH) transmission based on dynamic granting and configuration granting is supported. Dynamically granted PUSCH transmission is scheduled by Downlink Control Information (DCI) formats 0_0, 0_1, or 0_2. Furthermore, two types of configuration-granted PUSCH transmission are specified. Specifically, Type 1 configuration-granted PUSCH transmission is based solely on Radio Resource Control (RRC) configuration (or reconfiguration) and is independent of any Layer 1 (L1) signaling. Specifically, semi-static resources, including time and frequency resources, modulation and coding schemes, reference signals, etc., can be configured for a UE. Type 2 configuration-granted PUSCH transmission activates / deactivates UL data transmission based on both RRC configuration and L1 signaling, similar to the semi-persistent (SPS) uplink transmission defined in LTE wireless communication systems.

[0021] In NR wireless communication systems, multiple repetitions can be configured for PUSCH transmissions to help improve their coverage performance. When repetition is used for PUSCH transmissions or Physical Uplink Control Channel (PUCCH) transmissions, the same Time Domain Resource Allocation (TDRA) is used in each time slot. Furthermore, inter-slot frequency hopping can be configured to utilize frequency diversity to improve the transmission performance of PUSCH or PUCCH transmissions. In NR wireless communication systems, the number of repetitions for PUSCH transmissions can be dynamically indicated in the DCI.

[0022] Furthermore, in NR wireless communication systems, transport blocks (TBs) carried by PUSCH transmissions are scheduled within time slots, or the resource allocation for a single data transmission is limited to within a time slot. In this case, the transport block size (TBS) is determined based on the number of resource elements (REs) in the time slot.

[0023] To maintain a low code rate, a TB can span more than one time slot, where a smaller number of Physical Resource Blocks (PRBs) can be allocated on the frequency to improve the link budget for carrying PUSCH transmissions that span more than one time slot. Supporting PUSCH transmissions that carry TBs spanning more than one time slot may require consideration of certain design aspects, including signaling details and TBS determination.

[0024] Figure 1 A flowchart illustrating a method used in a UE according to an embodiment of this disclosure is shown. Figure 1 As shown, method 100 includes: S102, receiving downlink control information (DCI), wherein the DCI is configured to schedule physical uplink shared channel (PUSCH) transmission carrying transport blocks (TBs) spanning more than one time slot; and S104, according to the DCI, transmitting PUSCH transmission carrying TBs spanning more than one time slot.

[0025] In some embodiments, the DCI is a non-fallback DCI, or the DCI is DCI format 1_1 or DCI format 1_2.

[0026] In some embodiments, method 100 further includes determining, based on at least one of Radio Resource Control (RRC) signaling and DCI, the number of time slots, transmission timings, or symbols for carrying PUSCH transmissions spanning more than one time slot.

[0027] In some embodiments, fields in the DCI are used to indicate whether a PUSCH transport scheduled by the DCI is used to carry a TB spanning more than one time slot.

[0028] In some embodiments, one or more existing fields in the DCI are repurposed or a known state of an existing field in the DCI is used to indicate that a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot.

[0029] In some embodiments, method 100 further includes determining, based on Radio Resource Control (RRC) signaling associated with the DCI, whether a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot. For example, a portion or a separate PUSCH-TimeDomainResourceAllocation parameter carried in the RRC signaling is configured to indicate whether a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot.

[0030] In some embodiments, transmitting a PUSCH transmission carrying a TB spanning more than one time slot includes: using the same time domain resource allocation in each time slot to transmit the PUSCH transmission carrying a TB spanning more than one time slot.

[0031] In some embodiments, transmitting a PUSCH transmission carrying a TB spanning more than one time slot includes: using consecutive time-domain resource allocation in more than one time slot to transmit the PUSCH transmission carrying a TB spanning more than one time slot.

[0032] In some embodiments, one or more of the following—the number of time slots, the start symbol in the time slot, and the number of symbols in the time slot—for carrying PUSCH transmissions spanning more than one time slot are configured separately as part of the PUSCH-time domain resource allocation parameters carried in RRC signaling or as separate PUSCH-time domain resource allocation parameters.

[0033] In some embodiments, the start symbol, end symbol, and number of time slots used to carry PUSCH transmissions spanning more than one time slot are configured separately as part of the PUSCH-time domain resource allocation parameters carried in the RRC signaling.

[0034] In some embodiments, time-domain resource allocation in different time slots is configured as part of the PUSCH-time-domain resource allocation parameters carried in RRC signaling.

[0035] In some embodiments, transmitting a PUSCH transmission carrying a TB spanning more than one time slot includes: using frequency hopping in different time slots to transmit the PUSCH transmission carrying a TB spanning more than one time slot.

[0036] In some embodiments, transmitting a PUSCH transmission carrying a TB spanning more than one time slot includes: employing intra-time slot and inter-time slot frequency hopping to transmit the PUSCH transmission carrying a TB spanning more than one time slot.

[0037] In some embodiments, transmitting a PUSCH transmission carrying a TB spanning more than one time slot includes: employing inter-time slot and inter-transmission frequency hopping to transmit the PUSCH transmission carrying a TB spanning more than one time slot.

[0038] In some embodiments, method 100 further includes determining the transport block size (TBS) based on the number of time slots, the number of transmission opportunities, or the number of symbols used to carry PUSCH transmissions spanning more than one time slot.

[0039] In some embodiments, the DCI includes a TB scaling field that indicates a TB scaling factor for determining the TBS.

[0040] In some embodiments, method 100 further includes: determining a limit on the total number of resource elements (REs) allocated for carrying PUSCH transmissions spanning more than one time slot, based on the number of symbols and the number of time slots used to carry PUSCH transmissions spanning more than one time slot.

[0041] In some embodiments, method 100 further includes: when a PUSCH transmission carrying a TB spanning more than one time slot conflicts with a Physical Uplink Control Channel (PUCCH) transmission, a high-priority uplink transmission, or a downlink transmission, discarding or canceling all, part, or any time slots of the PUSCH transmission carrying a TB spanning more than one time slot.

[0042] Below, details relating to various aspects of method 100 are provided.

[0043] Signaling details for carrying PUSCH transmissions spanning more than one time slot (TB).

[0044] The following embodiment provides signaling details for carrying PUSCH transmissions spanning more than one time slot (TB):

[0045] In one embodiment of this disclosure, non-backoff DCI or DCI format 1_1 and / or DCI format 1_2 can be used to schedule PUSCH transmissions carrying TBs spanning more than one time slot. Furthermore, the number of time slots, transmission timings, or symbols used to carry PUSCH transmissions carrying TBs spanning more than one time slot can be configured by a higher layer via RRC signaling, dynamically indicated in the DCI, or determined by a combination of both.

[0046] In one option, a set of values ​​can be configured by a higher layer for the number of time slots, transmission timings, or symbols used to carry PUSCH transmissions spanning more than one time slot, and a field in the DCI can be used to indicate which value in the set is used as the number of time slots, transmission timings, or symbols used to carry PUSCH transmissions spanning more than one time slot.

[0047] In another option, the number of time slots, transmission timings, or symbols used to carry PUSCH transmissions spanning more than one time slot can be included in the DCI as part of the TDRA field, which can be combined with the scheduling offset (K2 for PUSCH scheduling), mapping type A or B, and start length indication value (SLIV) in the PUSCH-time domain resource allocation parameters.

[0048] Please note that for PUSCH transmissions scheduled by fallback DCI or DCI format 0_0 and scheduled by random access response (RAR) uplink grant or fallback RAR uplink grant, the PUSCH transmission is sent within the time slot. In other words, PUSCH transmissions carrying more than one time slot (TB) are not applicable to contention-based random access message 3 (Msg3) and cannot be scheduled by DCI format 0_0.

[0049] In another embodiment of this disclosure, an indication of a PUSCH transmission carrying a TB spanning more than one time slot can be explicitly included in the DCI used for uplink authorization. For example, a field from DCI format 0_1 ​​or 0_2 can be used to indicate whether a PUSCH transmission is used to carry a TB spanning more than one time slot. For instance, a bit "1" can be used to indicate that a PUSCH transmission is used to carry a TB spanning more than one time slot, and a bit "0" can be used to indicate that a PUSCH transmission is used to carry a TB spanning one time slot.

[0050] In another option, whether a PUSCH transport is used to carry a TB spanning more than one time slot can be configured by the RRC signaling for each DCI format. For example, when a DCI format (e.g., DCI format 0_1) is configured to schedule PUSCH transports carrying TBs spanning more than one time slot, a single TB spanning more than one time slot is carried by a PUSCH transport scheduled by that DCI format 0_1.

[0051] In another option, some existing fields in the DCI can be repurposed, or the known state of existing fields in the DCI can be used to indicate PUSCH transmissions spanning more than one time slot (TB).

[0052] In another option, the indication for carrying PUSCH transmissions spanning more than one time slot (TB) can be configured as part of the PUSCH-time domain resource allocation parameter or as a separate PUSCH-time domain resource allocation parameter. When the PUSCH-time domain resource allocation list includes different time domain resource allocations, the gNB can dynamically switch from single-time slot-based transmissions to multi-time slot-based transmissions for carrying PUSCH transmissions spanning more than one time slot.

[0053] In another option, when a PUSCH transmission is scheduled by DCI format 0_0, the PUSCH transmission is sent only within the time slot. In other words, a PUSCH transmission carrying a TB spanning more than one time slot cannot be scheduled by DCI format 0_0.

[0054] In another embodiment of this disclosure, for PUSCH transmissions carrying a TB spanning more than one time slot, the same time-domain resource allocation is used for PUSCH transmissions in each time slot. Note that the number of time slots used to carry PUSCH transmissions spanning more than one time slot can be configured as part of the PUSCH-time-domain resource allocation parameter, along with the scheduling offset K2, mapping type, and start symbol and length. In this case, start symbol and length indicate the start symbol and the number of symbols (i.e., the length) of the PUSCH transmission in each time slot.

[0055] Figure 2 An example of time-domain resource allocation for carrying PUSCH transmissions spanning more than one timeslot, according to an embodiment of this disclosure, is shown. Figure 2 In this process, four time slots are used to carry a single TB of PUSCH transmission, and the same time domain resource allocation is used for the PUSCH transmission in each time slot.

[0056] In another embodiment of this disclosure, for a PUSCH transmission carrying a TB spanning more than one time slot, a set of DCIs (e.g., DCI format 0_1 ​​or 0_2) indicates different time-domain and frequency-domain resource allocations. Each DCI is configured as a single-time-slot PUSCH transmission as part of a PUSCH transmission carrying a TB spanning more than one time slot.

[0057] For example, the first DCI in a group initiates a PUSCH transmission carrying a TB spanning more than one time slot and is configured as a first time slot PUSCH transmission as a first part of the PUSCH transmission carrying a TB spanning more than one time slot, and the other DCIs in the group are configured as the remaining PUSCH transmissions carrying the remaining parts of the PUSCH transmission carrying a TB spanning more than one time slot.

[0058] In another embodiment of this disclosure, for PUSCH transmissions carrying TBs spanning more than one time slot, a continuous allocation of time resources within the time slots can be employed.

[0059] In one option, the number of symbols used to carry a PUSCH transmission spanning more than one time slot and the starting symbol can be configured separately as part of the PUSCH-time domain resource allocation parameters. In this case, the number of symbols used for the PUSCH transmission can be greater than 14 symbols. To save signaling overhead, a subset of this number of symbols can be configured, for example, an integer (4) symbols.

[0060] In another option, the number of symbols and the start symbol used to carry PUSCH transmissions spanning more than one time slot (TB) can be configured separately as part of the PUSCH-time domain resource allocation parameters (i.e., start symbol and length). Furthermore, to save signaling overhead, symbol groups can be configured where the number of start symbols and / or symbols used for PUSCH transmissions is defined as a function of that symbol group. For example, the number of symbols in a symbol group can be expressed as... Furthermore, as shown by the start and length indication values ​​(SLIV) in the PUSCH-time domain resource allocation parameters, S group and L groupThese are represented as the start symbol group and the symbol length group, respectively. In this case, the start symbol and symbol length of the PUSCH transmission can be derived as follows: and

[0061] In another option, the start symbol, the number of symbols, and the number of time slots used to carry PUSCH transmissions spanning more than one time slot can be configured separately as part of the PUSCH-time domain resource allocation parameters. In this case, the start symbol can indicate the start symbol in the first time slot, and the end symbol in the last time slot can be determined accordingly based on the start symbol and the number of symbols. All 14 symbols in the time slot between the first and last time slots are allocated for PUSCH transmissions.

[0062] Figure 3 Another example of time-domain resource allocation for carrying PUSCH transmissions spanning more than one timeslot, according to embodiments of this disclosure, is shown. Figure 3 In this context, consecutive time resource allocation within a time slot is used to carry PUSCH transmissions spanning more than one time slot (TB). Specifically, the starting symbol and the number of symbols used to carry PUSCH transmissions spanning more than one time slot can be indicated as the third symbol and 45 symbols in the first time slot, respectively.

[0063] In another embodiment of this disclosure, consecutive time resource allocation within a time slot can be used to carry PUSCH transmissions spanning more than one time slot (TB). This is similar to PUSCH repetition type B using back-to-back transmission. In this case, the starting symbol, the number of symbols, and the number of transmission opportunities for the PUSCH transmission can be configured as part of the PUSCH-time domain resource allocation parameters. Note that the length of the PUSCH transmission in each transmission opportunity is less than or equal to 14 symbols.

[0064] Figure 4 Another example of time-domain resource allocation for carrying PUSCH transmissions spanning more than one timeslot, according to embodiments of this disclosure, is shown. Figure 4 In this configuration, consecutive time resource allocation is used to carry PUSCH transmissions spanning more than one time slot (TB). In this case, the starting symbol is the third symbol, the length of the PUSCH transmission within a transmission slot is 10, and the number of transmission slots is 4. With this option, the total number of symbols allocated to PUSCH transmissions is 40.

[0065] In another embodiment of this disclosure, different time-domain resource allocations or SLIVs in different time slots can be configured as part of the PUSCH-time-domain resource allocation parameters to carry PUSCH transmissions spanning more than one time slot (TB). In this case, different start symbols and lengths of PUSCH transmissions in different time slots can be configured.

[0066] In another embodiment of this disclosure, an indication of a configuration-granted PUSCH transmission carrying a TB spanning more than one time slot can be configured as part of a ConfigurationGrantConfig parameter carried in RRC signaling. Furthermore, the aforementioned time-domain resource allocation mechanism can be applied to this configuration-granted PUSCH transmission. Note that the time-domain resource allocation configuration can be part of a PUSCH-time-domain resource allocation parameter or a separate PUSCH-time-domain resource allocation parameter.

[0067] In another embodiment of this disclosure, frequency hopping can be applied to PUSCH transmissions spanning more than one time slot (TB). Different frequency hopping mechanisms can be defined based on specific time-domain resource allocations.

[0068] In one option, similar to PUSCH repetition type A, intra-slot and inter-slot frequency hopping can be used to carry PUSCH transmissions spanning more than one time slot (TB).

[0069] In another option, similar to PUSCH repetition type B, inter-slot and inter-transmission frequency hopping can be used to carry PUSCH transmissions spanning more than one time slot (TB). For inter-transmission frequency hopping, different frequency resources are used for PUSCH transmissions in adjacent transmission times.

[0070] Please note that the frequency hopping distance between two hops can be configured by a higher layer via RRC signaling, dynamically indicated in the DCI, or determined by a combination of both. Alternatively, it can be determined based on the bandwidth of the uplink bandwidth portion (BWP).

[0071] Figure 5 An example of inter-slot frequency hopping for carrying PUSCH transmissions spanning more than one time slot, according to an embodiment of this disclosure, is shown. Figure 5 In this context, different frequency resources are used for PUSCH transmission in adjacent UL time slots.

[0072] TBS determination for carrying PUSCH transmissions spanning more than one time slot (TB).

[0073] The following is an example of TBS determination for carrying PUSCH transmissions spanning more than one time slot:

[0074] In one embodiment of this disclosure, for a PUSCH transmission carrying a TB spanning more than one timeslot, the TBS is calculated based on the number of timeslots used for the PUSCH transmission. This can be used when the same time-domain resource allocation in each timeslot is used to carry a PUSCH transmission spanning more than one timeslot.

[0075] The TBS calculation for a PUSCH transmission carrying a TB spanning more than one timeslot involves the following. Below, ePUSCH represents a PUSCH transmission carrying a TB spanning more than one timeslot.

[0076]

[0077]

[0078] In another option, the TBS calculation for carrying PUSCH transmissions spanning more than one time slot involves the following.

[0079]

[0080] In another option, the TBS calculation for carrying PUSCH transmissions spanning multiple time slots involves the following.

[0081]

[0082] In another option, the TBS calculation for carrying PUSCH transmissions spanning more than one time slot involves the following.

[0083]

[0084]

[0085] In another option, the TBS calculation for carrying PUSCH transmissions spanning more than one time slot involves the following.

[0086]

[0087] In another embodiment of this disclosure, for a PUSCH transmission carrying a TB spanning more than one time slot, the TBS is calculated based on the number of transmission opportunities used for that PUSCH transmission. This can be used when back-to-back transmission is applied to a PUSCH transmission carrying a TB spanning more than one time slot (similar to PUSCH repetition type B).

[0088] TBS calculations for carrying PUSCH transmissions spanning more than one time slot (TB) involve the following.

[0089]

[0090]

[0091] In another embodiment of this disclosure, for a PUSCH transmission carrying a TB spanning more than one time slot, the TB is calculated based on the number of symbols within the PUSCH transmission. In this case, It can be determined as the number of REs used for DM-RS in each PRB during the duration allocated for PUSCH transmission (which may span more than one time slot).

[0092] TBS calculations for carrying PUSCH transmissions spanning more than one time slot (TB) involve the following.

[0093]

[0094] In another option, the TBS calculation for carrying PUSCH transmissions spanning more than one time slot involves the following.

[0095]

[0096]

[0097] In another embodiment of this disclosure, the TBS calculation for carrying PUSCH transmissions spanning more than one time slot involves the following.

[0098]

[0099] In the above embodiments, N slot This can be defined as the number of time slots allocated to carry PUSCH transmissions spanning more than one time slot (TB). It can be configured by higher layers via Minimum System Information (MSI), Residual Minimum System Information RMSI (SIB1), Other System Information (OSI), or RRC signaling, or dynamically indicated in the DCI, or determined using a combination of both. Alternatively, N can be predefined. slot This indicates the maximum allowed number of time slots for carrying PUSCH transmissions spanning more than one time slot.

[0100] As another option, for TB processing on multi-slot PUSCH transmissions, the limitation on the total number of REs allocated for such multi-slot PUSCH transmissions can be calculated as follows:

[0101] N RE =min(12*(14*N) slot -1), N′ RE )·n PRB

[0102] Please note that the above options can be applied to TDRA based on repetition type A for TB processing on multi-slot PUSCH transport.

[0103] In another embodiment of this disclosure, for TB processing on multi-slot PUSCH transmission, the limitation on the total number of REs allocated for the multi-slot PUSCH transmission can be calculated as follows:

[0104]

[0105] in, N is the number of symbols allocated to carry PUSCH transmissions spanning more than one time slot (TB). slot This is the number of time slots used to carry PUSCH transmissions spanning more than one time slot (TB). In one option, N slot This can be indicated as part of the TDRA parameters for carrying PUSCH transmissions spanning more than one time slot (TB). Alternatively, the UE can determine the number of time slots N accordingly based on the start and length indication values ​​(SLIV). slot .

[0106] In another option, for TB processing on multi-slot PUSCH transmissions, the limitation on the total number of REs allocated for that multi-slot PUSCH transmission can be calculated as follows:

[0107]

[0108] As a further extension, for TB processing on multi-slot PUSCH transmissions, the limitation on the total number of REs allocated for such multi-slot PUSCH transmissions can be calculated as follows:

[0109] or

[0110]

[0111] Please note that the above options can be applied to TDRA based on repetition type B for TB processing on multi-slot PUSCH transport.

[0112] Collision handling when PUSCH transmissions spanning more than one time slot (TB) overlap with other uplink transmissions.

[0113] In NR wireless communication systems, if a set of symbols has been allocated for a semi-static PUSCH transmission, the UE should cancel the semi-static PUSCH transmission based on one or more of the following rules:

[0114] • When at least one symbol in the group is scheduled for DL ​​transmission by the DCI scheduling of DL transmission;

[0115] • When at least one symbol in this group is used as a DL symbol in the RRC signaling indication of the time slot format configuration;

[0116] • When at least one symbol in this group is configured by RRC signaling for single-sideband (SSB) transmission;

[0117] • When at least one symbol in the group is indicated as a DL or flexible symbol by a slot format indicator (SFI) (e.g., DCI format 2_0);

[0118] • When the UE does not receive an SFI and at least one of the symbols in the group is considered a flexible symbol (configured by RRC signaling or when no RRC configuration is available), after time T2 after the last symbol of the control resource set (CORESET) used for Slot Format Indication (SFI) transmission;

[0119] • For Configuration Grant (CG) PUSCH that overlaps with Dynamic Grant (DG) PUSCH (there is at least N2 time intervals between the scheduling DCIs of DG PUSCH and CG PUSCH);

[0120] • For CG PUSCH with the same Hybrid Automatic Repeat Request (HARQ) process number as DG PUSCH (there must be at least N2 time intervals between the scheduling DCIs of DGPUSCH and CG PUSCH).

[0121] The following embodiment provides conflict handling when a PUSCH transmission carrying more than one time slot (TB) overlaps with other uplink and / or downlink transmissions:

[0122] In one embodiment of this disclosure, when at least one symbol used to carry a PUSCH transmission spanning more than one time slot satisfies any of the above rules or conflicts with a high-priority uplink transmission or PUCCH transmission, the entire PUSCH transmission carrying the TB spanning more than one time slot is canceled or discarded.

[0123] Figure 6 An example of the cancellation of a PUSCH transmission spanning more than one time slot (TB) according to an embodiment of this disclosure is shown. Figure 6 In this example, four symbols are configured as DL symbols. Due to a conflict between time-domain resource allocation and DL symbols, the entire PUSCH transmission is cancelled. It should be understood that although the entire PUSCH transmission is cancelled in this example, in some embodiments, only a portion or one or more time slots of the PUSCH may be cancelled.

[0124] Please note that the above cancellation for PUSCH transmissions spanning more than one time slot (TB) can also be applied to the other time-domain resource allocation mechanisms mentioned above.

[0125] In another embodiment of this disclosure, TB scaling can be applied to PUSCH transmissions with a single timeslot or to PUSCH transmissions carrying TBs spanning more than one timeslot.

[0126] Specifically, for non-backoff DCI (including DCI formats 0_1 or 0_2), a field in the DCI can be used to indicate the TB scaling factor used for TBS determination. Alternatively, some known states in the DCI can be adapted for use as an indicator of the TB scaling factor used for TBS determination.

[0127] The TBS calculation for carrying PUSCH transmissions spanning more than one time slot is as follows.

[0128]

[0129]

[0130] System and Implementation

[0131] Figure 7-8 Various systems, devices, and components are shown that can implement multiple aspects of the disclosed embodiments.

[0132] Figure 7 A schematic diagram of a network 700 according to various embodiments of the present disclosure is shown. Network 700 can operate according to the 3GPP technical specifications of Long Term Evolution (LTE) or 5G / NR systems. However, exemplary embodiments are not limited in this respect, and the described embodiments can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, etc.

[0133] Network 700 may include UE 702, which may include any mobile or non-mobile computing device designed to communicate with Radio Access Network (RAN) 704 via an over-the-air connection. UE 702 may be, but is not limited to, smartphones, tablets, wearable computing devices, desktop computers, laptops, in-vehicle infotainment devices, in-vehicle entertainment devices, dashboards, head-up displays, in-vehicle diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, network devices, machine-to-machine (M2M) or device-to-device (D2D) devices, Internet of Things (IoT) devices, etc.

[0134] In some embodiments, network 700 may include multiple UEs that are directly coupled to each other via a secondary link interface. The UE may be an M2M / D2D device that communicates using physical secondary link channels (e.g., but not limited to physical secondary link broadcast channel (PSBCH), physical secondary link discovery channel (PSDCH), physical secondary link shared channel (PSSCH), physical secondary link control channel (PSCCH), physical secondary link basic channel (PSFCH), etc.).

[0135] In some embodiments, UE 702 can also communicate with access point (AP) 706 via an over-the-air connection. AP 706 can manage wireless local area network (WLAN) connections and can be used to offload some / all network traffic from RAN 704. The connection between UE 702 and AP 706 can be consistent with any IEEE 802.11 protocol, wherein AP 706 can be Wireless Fibre Channel. Router. In some embodiments, UE 702, RAN 704, and AP 706 may utilize cellular WLAN aggregation (e.g., LTE-WLAN aggregation (LWA) / Lightweight IP (LWIP)). Cellular WLAN aggregation may involve RAN 704 configuring UE 702 to utilize both cellular radio resources and WLAN resources.

[0136] RAN 704 may include one or more access nodes, such as Access Node (AN) 708. AN 708 can terminate the air interface protocol of UE 702 by providing access layer protocols including Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Media Access Control (MAC), and L1 protocol. In this way, AN 708 enables data / voice connectivity between the core network (CN) 720 and UE 702. In some embodiments, AN 708 may be implemented in discrete devices or as one or more software entities running on a server computer (as part of, for example, a virtual network, which may be referred to as a distributed RAN (CRAN) or a virtual baseband unit pool). AN 708 may be referred to as a base station (BS), next-generation base station (gNB), RAN node, evolved Node B (eNB), next-generation eNB (ng eNB), Node B (NodeB), roadside unit (RSU), TRxP, Transmit / Receive Point (TRP), etc. AN 708 can be a macro cell base station or a low-power base station, used to provide microcells, picocells, or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0137] In embodiments where RAN 704 includes multiple ANs, they can be coupled to each other via an X2 interface (if RAN 704 is an LTE RAN) or an Xn interface (if RAN 704 is a 5G RAN). In some embodiments, the X2 / Xn interfaces, which can be separated into control / user plane interfaces, can allow ANs to transmit and handover, data / context transfer, mobility, load management, interference coordination, and other related information.

[0138] The AN of RAN 704 can manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE 702. UE 702 can simultaneously connect to multiple cells provided by the same or different ANs of RAN 704. For example, UE 702 and RAN 704 can use carrier aggregation to allow UE 702 to connect to multiple component carriers, each component carrier corresponding to a primary cell (Pcell) or a secondary cell (Scell). In a dual-connectivity scenario, the first AN can be the primary network node providing the primary cell group (MCG), and the second AN can be the secondary network node providing the secondary cell group (SCG). The first / second AN can be any combination of eNB, gNB, ng eNB, etc.

[0139] RAN 704 can provide an air interface on both licensed and unlicensed spectrum. To operate in unlicensed spectrum, nodes can use Licensed Assisted Access (LAA), Enhanced LAA (eLAA), and / or further enhanced LAA (feLAA) mechanisms based on PCell / Scell ​​carrier aggregation (CA) technology. Before accessing unlicensed spectrum, nodes can perform medium / carrier sensing operations based on, for example, a Listen-After-Speak (LBT) protocol.

[0140] In a vehicle-to-everything (V2X) scenario, UE 702 or AN 708 can be or act as a roadside unit (RSU), which can refer to any transportation infrastructure entity used for V2X communication. The RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE can be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU"; an RSU implemented in or by a next-generation NodeB (gNB) can be referred to as a "gNB-type RSU," and so on. In one example, the RSU is a computing device coupled to radio frequency circuitry located on the roadside, providing connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU can provide very low-latency communication required for high-speed events such as collision avoidance, traffic warnings, etc. Alternatively or additionally, the RSU can provide other cellular / WLAN communication services. RSU components can be enclosed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers or backhaul networks.

[0141] In some embodiments, RAN 704 may be LTE RAN 710, which includes an evolved Node B (eNB), such as eNB 712. LTE RAN 710 can provide an LTE air interface with the following characteristics: a 15 kHz subcarrier spacing (SCS); a single-carrier frequency division multiple access (SC-FDMA) waveform for uplink (UL) and a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform for downlink (DL); turbo codes for data and TBCC for control, etc. The LTE air interface may rely on Channel State Information Reference Signal (CSI-RS) for CSI acquisition and beam management; rely on Physical Downlink Shared Channel (PDSCH) / Physical Downlink Control Channel (PDCCH) Demodulation Reference Signal (DMRS) for PDSCH / PDCCH demodulation; and rely on Cell Reference Signal (CRS) for cell search and initial acquisition, channel quality measurement, and channel estimation, and rely on channel estimation for coherent demodulation / detection at the UE. The LTE air interface can operate on a sub-6 GHz band.

[0142] In some embodiments, RAN 704 may be a next-generation (NG) RAN 714 with a gNB (e.g., gNB 716) or a gn-eNB (e.g., ng-eNB 718). gNB 716 can connect to a 5G-enabled UE using a 5G NR interface. gNB 716 can connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. ng-eNB 718 can also connect to the 5G core via an NG interface, but can connect to the UE via an LTE air interface. gNB 716 and ng-eNB 718 can connect to each other via an Xn interface.

[0143] In some embodiments, the NG interface can be divided into two parts: the NG user plane (NG-U) interface and the NG control plane (NG-C) interface. The former carries traffic data between the nodes of UPF 748 and NG-RAN 714 (e.g., the N3 interface), while the latter is the signaling interface between the nodes of Access and Mobility Management Function (AMF) 744 and NG-RAN 714 (e.g., the N2 interface).

[0144] NG-RAN 714 can provide a 5G-NR air interface with the following features: Variable Subcarrier Spacing (SCS); Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) for downlink (DL), CP-OFDM and DFT-s-OFDM for UL; Polarity, Repetition, Simplex, and Reed-Muller codes for control, and Low-Density Parity-Check (LDPC) codes for data. The 5G-NR air interface can rely on Channel State Reference Signals (CSI-RS) and PDSCH / PDCCH Demodulation Reference Signals (DMRS) similar to those used in the LTE air interface. The 5G-NR air interface may not use Cell Reference Signals (CRS), but can use Physical Broadcast Channel (PBCH) Demodulation Reference Signals (DMRS) for PBCH demodulation; Phase Tracking Reference Signals (PTRS) for PDSCH phase tracking; and Tracking Reference Signals for time tracking. The 5G-NR air interface can operate on the FR1 band, which includes the sub-6GHz band, or the FR2 band, which includes the 24.25GHz to 52.6GHz band. The 5G-NR air interface can include synchronization signals and PBCH blocks (SSBs), where an SSB is an area of ​​the downlink resource grid that includes the primary synchronization signal (PSS), secondary synchronization signal (SSS), and PBCH.

[0145] In some embodiments, the 5G-NR air interface can use the bandwidth portion (BWP) for various purposes. For example, the BWP can be used for dynamic adaptation of the SCS. For instance, UE 702 can be configured with multiple BWPs, each configured with a different SCS. When a BWP is indicated to UE 702 for a change, the transmitted SCS also changes. Another use case for BWPs relates to power saving. Specifically, multiple BWPs with different numbers of frequency resources (e.g., PRBs) can be configured for UE 702 to support data transmission under different traffic load scenarios. A BWP containing fewer PRBs can be used for data transmission with lower traffic loads, while allowing power saving at UE 702 and, in some cases, at gNB 716. A BWP containing more PRBs can be used for scenarios with higher traffic loads.

[0146] RAN 704 is communicatively coupled to CN 720, which includes network elements, to provide various functions supporting data and telecommunications services to customers / subscribers (e.g., users of UE 702). Components of CN 720 can be implemented in a single physical node or in different physical nodes. In some embodiments, Network Function Virtualization (NFV) can be used to virtualize any or all of the functions provided by the network elements of CN 720 onto physical compute / storage resources such as servers, switches, etc. A logical instance of CN 720 can be referred to as a network slice, and a logical instance of a portion of CN 720 can be referred to as a network subslice.

[0147] In some embodiments, CN 720 may be LTE CN 722, or may also be referred to as EPC. LTE CN 722 may include a Mobility Management Entity (MME) 724, a Serving Gateway (SGW) 726, a Serving General Packet Radio Service (GPRS) Support Node (SGSN) 728, a Home Subscriber Server (HSS) 730, a Proxy Gateway (PGW) 732, and a Policy Control and Charging Rules Function (PCRF) 734, as shown in the figure. These components are coupled to each other through interfaces (or "reference points"). The functions of the elements of LTE CN 722 can be briefly described below.

[0148] The MME 724 enables mobility management functions to track the current location of the UE 702, thereby facilitating paging, bearer activation / deactivation, handover, gateway selection, authentication, and other functions.

[0149] The SGW 726 can terminate the S1 interface toward the RAN and route data packets between the RAN and the LTE CN 722. The SGW 726 can serve as a local mobility anchor for handover between RAN nodes and can also provide anchoring for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0150] The SGSN 728 can track the location of UE 702 and perform security functions and access control. Additionally, the SGSN 728 can perform EPC inter-node signaling for mobility between different RAT networks; PDN and S-GW selection specified by the MME 724; MME selection for handover, etc. The S3 reference point between the MME 724 and SGSN 728 enables the exchange of user and bearer information for 3GPP indirect network access mobility in idle / active states.

[0151] The HSS 730 may include a database for network users, containing subscription-related information that supports network entities in handling communication sessions. The HSS 730 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 730 and the MME 724 enables the transmission of subscription and authentication data for authenticating / authorizing user access to the LTE CN 720.

[0152] The PGW 732 can terminate the SGi interface toward a data network (DN) 736, which may include an application / content server 738. The PGW 732 can route data packets between the LTE CN 722 and the data network 736. The PGW 732 can be coupled to the SGW 726 via an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 732 may also include nodes for policy enforcement and charging data collection (e.g., PCEF). Additionally, the SGi reference point between the PGW 732 and the data network 736 can be, for example, an external public or private PDN or an internal packet data network for providing IP Multimedia Subsystem (IMS) services. The PGW 732 can be coupled to the PCRF 734 via a Gx reference point.

[0153] PCRF 734 is the policy and charging control element of LTE CN 722. PCRF 734 can be communicatively coupled to application / content server 738 to determine appropriate Quality of Service (QoS) and charging parameters for service flows. PCRF 732 can provide relevant rules to PCEF (via Gx reference point) with appropriate Service Flow Template (TFT) and QoS Class Identifier (QCI).

[0154] In some embodiments, CN 720 may be a 5G core network (5GC) 740. 5GC 740 may include Authentication Server Function (AUSF) 742, Access and Mobility Management Function (AMF) 744, Session Management Function (SMF) 746, User Plane Function (UPF) 748, Network Slice Selection Function (NSSF) 750, Network Open Function (NEF) 752, NF Storage Function (NRF) 754, Policy Control Function (PCF) 756, Unified Data Management (UDM) 758, and Application Function (AF) 760, as shown in the figure. These functions are coupled to each other through interfaces (or "reference points"). The functions of the components of 5GC 740 can be briefly described below.

[0155] The AUSF 742 can store data for UE 702 authentication and handle authentication-related functions. The AUSF 742 facilitates a common authentication framework for various access types. In addition to communicating with other components of the 5GC 740 via a reference point, as shown in the figure, the AUSF 742 can also demonstrate an interface based on Nausf services.

[0156] The AMF 744 allows the 5GC 740 to communicate with UE 702 and RAN 704, and subscribe to notifications regarding mobility events for UE 702. The AMF 744 can handle registration management (e.g., registering UE 702), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 744 can provide the transmission of Session Management (SM) messages between UE 702 and SMF 746, and acts as a transparent broker for routing SM messages. The AMF 744 can also provide the transmission of SMS messages between UE 702 and the SMSF. The AMF 744 can interact with the AMFF 742 and UE 702 to perform various security anchoring and context management functions. Furthermore, the AMF 744 can be the termination point of the RAN CP interface, which may include or be the N2 reference point between RAN 704 and AMF 744; the AMF 744 can serve as the termination point for NAS (N1) signaling and perform NAS encryption and integrity protection. The AMF 744 can also support NAS signaling with the UE 702 via the N3 IWF interface.

[0157] SMF 746 can be responsible for SM (e.g., tunnel management and session establishment between UPF 748 and AN 708); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring flow control at UPF 748 to route traffic to appropriate destinations; termination of interfaces to policy control functions; control of policy enforcement, charging, and QoS as a part; lawful interception (for SM events and interfaces to the LI system); termination of the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information (sent to AN 708 on N2 via AMF 744); and determining the SSC mode of the session. SM can refer to the management of PDU sessions, and a PDU session or "session" can refer to the PDU connectivity service that provides or enables PDU exchange between UE 702 and data network 736.

[0158] The UPF 748 can be used as an anchor point for mobility within and between RATs, an external PDU session point interconnecting with the data network 736, and a branch point supporting multi-homed PDU sessions. The UPF 748 can also perform packet routing and forwarding, packet inspection, user plane portion of policy rules, lawful packet interception (IP collection), traffic usage reporting, QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic authentication (e.g., SDF-to-QoS flow mapping), transport-level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF 748 may include an uplink classifier to support traffic flow routing to the data network.

[0159] The NSSF 750 can select a set of network slice instances to serve UE 702. If needed, the NSSF 750 can also determine the allowed network slice selection assistance information (NSSAI) and the mapping to the subscribed individual NSSAI (S-NSSAI). The NSSF 750 can also determine the set of AMFs to be used to serve UE 702 based on appropriate configuration and possibly by querying the NRF 754, or determine a list of candidate AMFs. The selection of a set of network slice instances for UE 702 can be triggered by the AMF 744 (to which UE 702 registers by interacting with the NSSF 750), resulting in a change of AMF. The NSSF 750 can interact with the AMF 744 via the N22 reference point; and can communicate with another NSSF in the access network via the N31 reference point (not shown). Furthermore, the NSSF 750 can expose an interface based on NNSSF services.

[0160] The NEF 752 can securely expose services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, AFs (e.g., AF 760), edge computing, or fog computing systems. In these embodiments, the NEF 752 can authenticate, authorize, or restrict AFs. The NEF 752 can also translate information exchanged with the AF 760 and information exchanged with internal network functions. For example, the NEF 752 can translate between AF service identifiers and internal 5GC information. The NEF 752 can also receive information from other NFs based on their exposed capabilities. This information can be stored as structured data at the NEF 752 or stored at a data storage NF using a standardized interface. The NEF 752 can then re-expose the stored information to other NFs and AFs, or use it for other purposes such as analytics. Additionally, the NEF 752 can expose interfaces based on Nnef services.

[0161] NRF 754 supports service discovery, receiving NF discovery requests from NF instances and providing information about discovered NF instances to those instances. NRF 754 also maintains information about available NF instances and the services they support. As used herein, the terms "instantiation," "instance," etc., can refer to the creation of an instance, and an "instance" can refer to the concrete occurrence of an object, such as during program code execution. Furthermore, NRF 754 can demonstrate interfaces based on NRF services.

[0162] The PCF 756 can provide policy rules to control plane functions to execute them, and can also support a unified policy framework to manage network behavior. The PCF 756 can also implement a front-end to access subscription information related to policy decisions in the UDR of the UDM 758. In addition to communicating with functions via reference points as shown in the figure, the PCF 756 also demonstrates an interface based on Npcf services.

[0163] UDM 758 can process subscription-related information to support network entities in handling communication sessions and can store subscription data for UE 702. For example, subscription data can be transmitted via the N8 reference point between UDM 758 and AMF 744. UDM 758 can include two parts: an application front-end and a User Data Record (UDR). The UDR can store policy data and subscription data for UDM 758 and PCF 756, and / or structured data and application data for exposure (including PFDs for application detection and application request information for multiple UEs 702) for NEF 752. UDR 221 can expose a Nudr service-based interface to allow UDM 758, PCF 756, and NEF 752 to access specific sets of stored data, as well as to read, update (e.g., add, modify), delete, and receive notifications of relevant data changes in the subscription UDR. UDM may include UDM-FE (UDM front-end), which is responsible for handling credentials, location management, subscription management, etc. Several different front-ends can provide services to the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown in the figure, the UDM 758 can also demonstrate interfaces based on Nudm services.

[0164] The AF 760 can provide application impact on service routing, provide access to NEF, and interact with the policy framework for policy control.

[0165] In some embodiments, 5GC 740 can enable edge computing by selecting an operator / third-party service that is geographically close to the point where UE 702 connects to the network. This can reduce latency and load on the network. To provide edge computing implementation, 5GC 740 can select a UPF 748 close to UE 702 and perform traffic routing from UPF 748 to data network 736 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 760. In this way, AF 760 can influence UPF (re)selection and service routing. Based on operator deployment, when AF 760 is considered a trusted entity, the network operator can allow AF 760 to interact directly with the relevant NF. Additionally, AF 760 can expose interfaces based on Naf services.

[0166] Data network 736 can represent various network operator services, Internet access, or third-party services that can be provided by one or more servers (including, for example, application / content server 738).

[0167] Figure 8A wireless network 800 according to various embodiments is illustrated schematically. The wireless network 800 may include a UE 802 that communicates wirelessly with an AN 804. The UE 802 and the AN 804 may be similar to and substantially interchangeable with components of the same name described elsewhere herein.

[0168] UE 802 can be communicatively coupled to AN 804 via connection 806. Connection 806 is shown as an air interface to enable communication coupling and can operate at millimeter wave or sub-6 GHz frequencies according to cellular communication protocols such as LTE or 5G NR.

[0169] UE 802 may include a host platform 808 coupled to a modem platform 810. Host platform 808 may include application processing circuitry 812, which may be coupled to protocol processing circuitry 814 of the modem platform 810. Application processing circuitry 812 may run various applications for UE 802 to process source / receive application data. Application processing circuitry 812 may also implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0170] Protocol processing circuitry 814 can implement one or more layer operations to facilitate the transmission or reception of data via connection 806. Layer operations implemented by protocol processing circuitry 814 may include, for example, Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), RRC, and Non-Access Stratum (NAS) operations.

[0171] The modem platform 810 may further include digital baseband circuitry 816, which can implement one or more layer operations "below" the layer operations performed by protocol processing circuitry 814 in the network protocol stack. These operations may include, for example, one or more of the following PHY operations: HARQ-ACK function, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding. These functions may include one or more of the following: space-time, space-frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals, and other related functions.

[0172] The modem platform 810 may further include transmitting circuitry 818, receiving circuitry 820, RF circuitry 822, and RF front-end (RFFE) circuitry 824, which may include or be connected to one or more antenna panels 826. In short, transmitting circuitry 818 may include a digital-to-analog converter, mixer, intermediate frequency (IF) component, etc.; receiving circuitry 820 may include an analog-to-digital converter, mixer, IF component, etc.; RF circuitry 822 may include a low-noise amplifier, power amplifier, power point tracking component, etc.; RFFE circuitry 824 may include filters (e.g., surface acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the components of transmitting circuitry 818, receiving circuitry 820, RF circuitry 822, RFFE circuitry 824, and antenna panels 826 (collectively, the "transmit / receive assembly") may be specific to implementation details, such as whether the communication is time-division multiplexing (TDM) or frequency-division multiplexing (FDM), at mmWave or below 6 GHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains and may be arranged in the same or different chips / modules, etc.

[0173] In some embodiments, the protocol processing circuit 814 may include one or more instances of control circuitry (not shown) to provide control functions for the transmitting / receiving components.

[0174] UE reception can be established via and through antenna panel 826, RFFE circuit 824, RF circuit 822, receiving circuit 820, digital baseband circuit 816, and protocol processing circuit 814. In some embodiments, antenna panel 826 can receive transmissions from AN 804 by receiving beamforming signals received by a plurality of antennas / antenna elements of one or more antenna panels 826.

[0175] UE transmission can be established via and through protocol processing circuitry 814, digital baseband circuitry 816, transmission circuitry 818, RF circuitry 822, RFFE circuitry 824, and antenna panel 826. In some embodiments, the transmission component of UE 802 can apply spatial filtering to the data to be transmitted to form a transmission beam emitted by the antenna elements of antenna panel 826.

[0176] Similar to UE 802, AN 804 may include a host platform 828 coupled to a modem platform 830. Host platform 828 may include application processing circuitry 832 coupled to protocol processing circuitry 834 of modem platform 830. The modem platform may also include digital baseband circuitry 836, transmit circuitry 838, receive circuitry 840, RF circuitry 842, RFFE circuitry 844, and antenna panel 846. Components of AN 804 may be similar to their namesake components in UE 802 and are substantially interchangeable with their namesake components in UE 802. In addition to performing data transmission / reception as described above, components of AN 804 may perform various logical functions, including, for example, Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management, and packet scheduling.

[0177] Figure 9 This is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any or more methods discussed herein, according to some example embodiments. Specifically, Figure 9 A schematic diagram of hardware resource 900 is shown, which includes one or more processors (or processor cores) 910, one or more memory / storage devices 920, and one or more communication resources 930, wherein each of these processors, memory / storage devices, and communication resources can be communicatively coupled via bus 940 or other interface circuitry. For embodiments utilizing node virtualization (e.g., Network Functions Virtualization (NFV)), a hypervisor 902 can be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resource 900.

[0178] Processor 910 may include, for example, processor 99 and processor 914. Processor 910 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0179] The memory / storage device 920 may include main memory, disk storage devices, or any suitable combination thereof. The memory / storage device 920 may include, but is not limited to, any type of volatile, non-volatile, or semi-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, etc.

[0180] Communication resource 930 may include an interconnect or network interface controller, component, or other suitable device for communicating with one or more peripheral devices 904 or one or more databases 906 or other network elements via network 908. For example, communication resource 930 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, near field communication (NFC) components, etc. (or Low-energy components Components and other communication components.

[0181] Instruction 950 may include software, a program, application program, applet, or other executable code for causing at least any one of the processors 910 to perform any one or more of the methods discussed herein. Instruction 950 may reside wholly or partially within processor 910 (e.g., in the processor's cache), memory / storage device 920, or any suitable combination thereof. Furthermore, any portion of instruction 950 may be transferred from any combination of peripheral device 904 or database 906 to hardware resource 900. Therefore, the memory of processor 910, memory / storage device 920, peripheral device 904, and database 906 are examples of computer-readable and machine-readable media.

[0182] The following paragraphs describe examples of various embodiments.

[0183] Example 1 includes an apparatus for use in a user equipment (UE), comprising logic and circuitry configured to cause the UE to perform the following processes: receiving downlink control information (DCI) configured to schedule physical uplink shared channel (PUSCH) transmissions carrying transport blocks (TBs) spanning more than one time slot; and, according to the DCI, transmitting the PUSCH transmissions carrying TBs spanning more than one time slot.

[0184] Example 2 includes the apparatus described in Example 1, wherein the DCI is a non-fallback DCI, or the DCI is DCI format 1_1 or DCI format 1_2.

[0185] Example 3 includes the apparatus described in Example 1, wherein the logic and circuitry further cause the UE to: determine, based on at least one of Radio Resource Control (RRC) signaling and the DCI, the number of time slots, transmission timings, or symbols for the PUSCH transmission carrying a TB spanning more than one time slot.

[0186] Example 4 includes the apparatus described in Example 1, wherein a field in the DCI is used to indicate whether a PUSCH transmission scheduled by the DCI is used to carry a TB spanning more than one time slot.

[0187] Example 5 includes the apparatus described in Example 1, wherein one or more existing fields in the DCI are repurposed or the known state of the existing fields in the DCI is used to indicate that PUSCH transmissions scheduled by the DCI are used to carry TBs spanning more than one time slot.

[0188] Example 6 includes the apparatus described in Example 1, wherein the logic and circuitry are further configured to cause the UE to: determine, based on Radio Resource Control (RRC) signaling associated with the DCI, whether a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot.

[0189] Example 7 includes the apparatus described in Example 6, wherein a portion or a single PUSCH-time domain resource allocation parameter carried in the RRC signaling is configured to indicate whether a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot.

[0190] Example 8 includes the apparatus described in Example 1, wherein the logic and circuitry are further configured to cause the UE to transmit the PUSCH transmission, which carries a TB spanning more than one time slot, using the same time-domain resource allocation in each time slot.

[0191] Example 9 includes the apparatus described in Example 1, wherein the logic and circuitry are further configured to cause the UE to: employ consecutive time-domain resource allocation in more than one time slot to transmit the PUSCH transmission carrying a TB spanning more than one time slot.

[0192] Example 10 includes the apparatus described in Example 8 or 9, wherein the number of time slots for carrying PUSCH transmissions spanning more than one time slot, the start symbol in the time slot, and the number of symbols in the time slot are configured separately as part of or as separate PUSCH-time domain resource allocation parameters carried in Radio Resource Control (RRC) signaling.

[0193] Example 11 includes the apparatus described in Example 8 or 9, wherein one or more of the number of time slots, start symbol, and end symbol for the PUSCH transmission spanning more than one time slot of the TB are configured separately as part of the PUSCH-time domain resource allocation parameters carried in the Radio Resource Control (RRC) signaling.

[0194] Example 12 includes the apparatus described in Example 8 or 9, wherein time-domain resource allocation in different time slots is configured as part of PUSCH-time-domain resource allocation parameters carried in Radio Resource Control (RRC) signaling.

[0195] Example 13 includes the apparatus described in Example 1, wherein the logic and circuitry are further configured to cause the UE to: employ frequency hopping in different time slots to transmit the PUSCH transmission carrying a TB spanning more than one time slot.

[0196] Example 14 includes the apparatus described in Example 1, wherein the logic and circuitry are further configured to cause the UE to: employ intra-slot and inter-slot frequency hopping to transmit the PUSCH transmission carrying a TB spanning more than one time slot.

[0197] Example 15 includes the apparatus described in Example 1, wherein the logic and circuitry are further configured to cause the UE to: employ inter-slot and inter-transmission frequency hopping to transmit the PUSCH transmission carrying a TB spanning more than one time slot.

[0198] Example 16 includes the apparatus described in Example 1, wherein the logic and circuitry are further configured to cause the UE to determine the Transport Block Size (TBS) based on the number of time slots, the number of transmission opportunities, or the number of symbols used for the transmission of PUSCH carrying a TB spanning more than one time slot.

[0199] Example 17 includes the apparatus described in Example 16, wherein the DCI includes a TB scaling field that indicates a TB scaling factor for determining the TBS.

[0200] Example 18 includes the apparatus described in Example 16, wherein the logic and circuitry are further configured to cause the UE to: determine a limit on the total number of resource elements (TBs) allocated for the PUSCH transmission carrying a TB spanning more than one time slot, based on the number of symbols and the number of time slots used for the PUSCH transmission carrying a TB spanning more than one time slot.

[0201] Example 19 includes the apparatus described in Example 1, wherein the logic and circuitry are further configured to cause the UE to: discard or cancel all, part, or a time slot of the PUSCH transmission carrying a TB spanning more than one time slot when the PUSCH transmission carrying a TB spanning more than one time slot conflicts with an uplink control channel (PUCCH) transmission, a high-priority uplink transmission, or a downlink transmission.

[0202] Example 20 includes a computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to: receive downlink control information (DCI) configured to schedule physical uplink shared channel (PUSCH) transmissions carrying transport blocks (TBs) spanning more than one time slot; and, according to the DCI, provide the PUSCH transmissions carrying the TBs spanning more than one time slot to a radio interface for transmission.

[0203] Example 21 includes the computer-readable storage medium of Example 20, wherein the DCI is a non-fallback DCI, or the DCI is DCI format 1_1 or DCI format 1_2.

[0204] Example 22 includes the computer-readable storage medium of Example 20, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to: determine, based on at least one of Radio Resource Control (RRC) signaling and the DCI, the number of time slots, transmission timings, or symbols for the PUSCH transmission carrying more than one time slot.

[0205] Example 23 includes the computer-readable storage medium of Example 20, wherein a field in the DCI is used to indicate whether a PUSCH scheduled by the DCI is used to carry a TB spanning more than one time slot.

[0206] Example 24 includes the computer-readable storage medium of Example 20, wherein one or more existing fields in the DCI are repurposed or a known state of the existing fields in the DCI is used to indicate that PUSCH transmissions scheduled by the DCI are intended to carry TBs spanning more than one time slot.

[0207] Example 25 includes the computer-readable storage medium of Example 20, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to: determine, based on Radio Resource Control (RRC) signaling associated with the DCI, whether a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot.

[0208] Example 26 includes the computer-readable storage medium of Example 25, wherein a portion or a single PUSCH-time domain resource allocation parameter carried in the RRC signaling is configured to indicate whether a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot.

[0209] Example 27 includes the computer-readable storage medium of Example 20, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to: provide the PUSCH transmission carrying more than one time slot (TB) to the radio interface for transmission using the same time-domain resource allocation in each time slot.

[0210] Example 28 includes the computer-readable storage medium of Example 20, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to: provide the PUSCH transmission carrying a TB spanning more than one time slot to the radio interface for transmission using consecutive time-domain resource allocation in more than one time slot.

[0211] Example 29 includes the computer-readable storage medium described in Example 27 or 28, wherein the number of time slots, the start symbol in the time slot, and the number of symbols in the time slot for carrying PUSCH transmissions spanning more than one time slot are configured separately as part of or as separate PUSCH-time domain resource allocation parameters carried in Radio Resource Control (RRC) signaling.

[0212] Example 30 includes the computer-readable storage medium described in Example 27 or 28, wherein the number of time slots, the start symbol, and the end symbol for the PUSCH transmission spanning more than one time slot TB are configured separately as part of the PUSCH-time domain resource allocation parameters carried in Radio Resource Control (RRC) signaling.

[0213] Example 31 includes the computer-readable storage medium described in Example 27 or 28, wherein time-domain resource allocation in different time slots is configured as part of PUSCH-time-domain resource allocation parameters carried in Radio Resource Control (RRC) signaling.

[0214] Example 32 includes the computer-readable storage medium of Example 20, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to: provide the PUSCH transmission carrying a TB spanning more than one time slot to the wireless interface for transmission using frequency hopping in different time slots.

[0215] Example 33 includes the computer-readable storage medium of Example 20, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to: provide the PUSCH transmission carrying a TB spanning more than one time slot to the wireless interface for transmission using intra-time slot and inter-time slot frequency hopping.

[0216] Example 34 includes the computer-readable storage medium of Example 20, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to: provide the PUSCH transmission carrying more than one time slot (TB) to the wireless interface for transmission using inter-time slot and inter-transmission frequency hopping.

[0217] Example 35 includes the computer-readable storage medium of Example 20, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to determine the transport block size (TBS) based on the number of time slots, the number of transmission opportunities, or the number of symbols for the PUSCH transmission carrying more than one time slot TB.

[0218] Example 36 includes the apparatus described in Example 35, wherein the DCI includes a TB scaling field that indicates a TB scaling factor for determining the TBS.

[0219] Example 37 includes the computer-readable storage medium of Example 35, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to: determine a limit on the total number of resource elements (TBs) allocated for the PUSCH transmission carrying a TB spanning more than one time slot, based on the number of symbols and the number of time slots used for the PUSCH transmission carrying a TB spanning more than one time slot.

[0220] Example 38 includes the computer-readable storage medium of Example 20, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to: discard or cancel a slot, part or all of the slot of the PUSCH transmission carrying more than one slot TB when the PUSCH transmission carrying more than one slot TB conflicts with an uplink control channel (PUCCH) transmission, a high-priority uplink transmission, or a downlink transmission.

[0221] Example 39 includes a method for use in a user equipment (UE), comprising: receiving downlink control information (DCI) configured to schedule physical uplink shared channel (PUSCH) transmissions carrying transport blocks (TBs) spanning more than one time slot; and, according to the DCI, transmitting the PUSCH transmissions carrying TBs spanning more than one time slot.

[0222] Example 40 includes the method described in Example 39, wherein the DCI is a non-fallback DCI, or the DCI is DCI format 1_1 or DCI format 1_2.

[0223] Example 41 includes the method of Example 39, further comprising: determining, based on at least one of Radio Resource Control (RRC) signaling and the DCI, the number of time slots, transmission timings, or symbols for the PUSCH transmission carrying a TB spanning more than one time slot.

[0224] Example 42 includes the method described in Example 39, wherein a field in the DCI is used to indicate whether a PUSCH transport scheduled by the DCI is intended to carry a TB spanning more than one time slot.

[0225] Example 43 includes the method of Example 39, wherein one or more existing fields in the DCI are repurposed or the known state of the existing fields in the DCI is used to indicate that PUSCH transmissions scheduled by the DCI are intended to carry TBs spanning more than one time slot.

[0226] Example 44 includes the method of Example 39, further comprising: determining, based on Radio Resource Control (RRC) signaling associated with the DCI, whether a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot.

[0227] Example 45 includes the method described in Example 44, wherein a portion or a single PUSCH-time domain resource allocation parameter carried in the RRC signaling is configured to indicate whether a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot.

[0228] Example 46 includes the method of Example 39, wherein sending the PUSCH transmission of the bearer spanning more than one time slot TB includes: using the same time domain resource allocation in each time slot to send the PUSCH transmission of the bearer spanning more than one time slot TB.

[0229] Example 47 includes the method of Example 39, wherein sending the PUSCH transmission of the bearer spanning more than one time slot includes: using consecutive time domain resource allocation in more than one time slot to send the PUSCH transmission of the bearer spanning more than one time slot.

[0230] Example 48 includes the method described in Example 46 or 47, wherein the number of time slots, the start symbol in the time slot, and the number of symbols in the time slot for the PUSCH transmission carrying more than one time slot are configured separately as part of or as separate PUSCH-time domain resource allocation parameters carried in Radio Resource Control (RRC) signaling.

[0231] Example 49 includes the method described in Example 46 or 47, wherein the number of time slots, the start symbol, and the end symbol for the PUSCH transmission spanning more than one time slot are configured separately as part of the PUSCH-time domain resource allocation parameters carried in the Radio Resource Control (RRC) signaling.

[0232] Example 50 includes the method described in Example 46 or 47, wherein time-domain resource allocation in different time slots is configured as part of PUSCH-time-domain resource allocation parameters carried in Radio Resource Control (RRC) signaling.

[0233] Example 51 includes the method described in Example 39, wherein sending the PUSCH transmission of the bearer spanning more than one time slot includes: using frequency hopping in different time slots to send the PUSCH transmission of the bearer spanning more than one time slot.

[0234] Example 52 includes the method described in Example 39, wherein transmitting the PUSCH transmission of the bearer spanning more than one time slot TB includes: employing intra-slot and inter-slot frequency hopping to transmit the PUSCH transmission of the bearer spanning more than one time slot TB.

[0235] Example 53 includes the method described in Example 39, wherein sending a PUSCH transmission with the bearer spanning more than one time slot (TB) includes: employing inter-slot and inter-transmission frequency hopping to send the PUSCH transmission with the bearer spanning more than one time slot (TB).

[0236] Example 54 includes the method of Example 39, further comprising: determining the transport block size (TBS) based on the number of time slots, the number of transmission opportunities, or the number of symbols used for the PUSCH transmission that carries a TB spanning more than one time slot.

[0237] Example 55 includes the method described in Example 54, wherein the DCI includes a TB scaling field that indicates a TB scaling factor for determining the TBS.

[0238] Example 56 includes the method of Example 54, further comprising: determining a limit on the total number of resource elements (TBs) allocated for the PUSCH transmission carrying a TB spanning more than one time slot, based on the number of symbols and the number of time slots used for the PUSCH transmission carrying a TB spanning more than one time slot.

[0239] Example 57 includes the method described in Example 39, further comprising: when the PUSCH transmission carrying a TB spanning more than one time slot conflicts with an uplink control channel (PUCCH) transmission, a high-priority uplink transmission, or a downlink transmission, discarding or canceling the time slot, part, or all of the PUSCH transmission carrying a TB spanning more than one time slot.

[0240] Example 58 includes a user equipment (UE) comprising: one or more processors; and a memory storing instructions, wherein, when executed by the one or more processors, the instructions cause the one or more processors to cause the UE to perform any one of Examples 39 to 57.

[0241] While certain embodiments have been illustrated and described herein for purposes of description, various alternative and / or equivalent embodiments or implementations that achieve the same purpose may be substituted for the illustrated and described embodiments without departing from the scope of the invention. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, the embodiments described herein are clearly limited only by the appended claims and their equivalents.

Claims

1. An apparatus for use in a user equipment (UE), comprising logic and circuitry configured to cause the UE to perform the following processes: Receive downlink control information (DCI) configured to schedule Physical Uplink Shared Channel (PUSCH) transmissions carrying transport blocks (TBs) spanning more than one time slot; and According to the DCI, the PUSCH transmission carrying more than one time slot (TB) is sent. in, The fields in the DCI are used to indicate whether the PUSCH transmissions scheduled by the DCI are intended to carry a TB spanning more than one time slot. The logic and circuitry are further configured to cause the UE to: determine, according to Radio Resource Control (RRC) signaling associated with the DCI, whether a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot, wherein a portion or a single PUSCH-time domain resource allocation parameter carried in the RRC signaling is configured to indicate whether a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot; The logic and circuitry are further configured to cause the UE to determine the Transport Block Size (TBS) based on the number of time slots, the number of transmission opportunities, or the number of symbols used for the PUSCH transmission of the TB that carries more than one time slot.

2. The apparatus according to claim 1, wherein, The DCI is a non-backoff DCI, or the DCI is DCI format 1_1 or DCI format 1_2.

3. The apparatus according to claim 1, wherein, The logic and circuitry further enable the UE: The number of time slots, transmission timings, or symbols for the PUSCH transmission carrying a TB spanning more than one time slot is determined based on at least one of the Radio Resource Control (RRC) signaling and the DCI.

4. The apparatus according to claim 1, wherein, One or more existing fields in the DCI are repurposed, or a known state of an existing field in the DCI is used, to indicate that PUSCH transmissions scheduled by the DCI are intended to carry TBs spanning more than one time slot.

5. The apparatus according to claim 1, wherein, The logic and circuitry are further configured to cause the UE to: The same time-domain resource allocation is used in each time slot to send PUSCH transmissions that span more than one time slot (TB).

6. The apparatus according to claim 1, wherein, The logic and circuitry are further configured to cause the UE to: The PUSCH transmission, which carries a TB spanning more than one time slot, is transmitted using continuous time-domain resource allocation in more than one time slot.

7. The apparatus according to claim 5 or 6, wherein, One or more of the number of time slots, the start symbol in the time slot, and the number of symbols in the time slot used for PUSCH transmissions that carry more than one time slot are configured separately as part of the PUSCH-time domain resource allocation parameters carried in the Radio Resource Control (RRC) signaling or as separate PUSCH-time domain resource allocation parameters.

8. The apparatus according to claim 5 or 6, wherein, The number of time slots, start symbol, and end symbol used for PUSCH transmissions that carry more than one time slot in a TB are configured separately as part of the PUSCH-time domain resource allocation parameters carried in the Radio Resource Control (RRC) signaling.

9. The apparatus according to claim 5 or 6, wherein, The allocation of time-domain resources in different time slots is configured as part of the PUSCH-time-domain resource allocation parameters carried in the Radio Resource Control (RRC) signaling.

10. The apparatus according to claim 1, wherein, The logic and circuitry are further configured to cause the UE to: Frequency hopping is used in different time slots to transmit PUSCH transmissions that carry more than one time slot across TB.

11. The apparatus according to claim 1, wherein, The logic and circuitry are further configured to cause the UE to: Frequency hopping within and between time slots is used to transmit PUSCH transmissions that carry more than one time slot (TB).

12. The apparatus according to claim 1, wherein, The logic and circuitry are further configured to cause the UE to: Frequency hopping between time slots and during transmission is used to transmit the PUSCH transmission that carries more than one time slot (TB).

13. The apparatus according to claim 1, wherein, The DCI includes a TB scaling field, which indicates the TB scaling factor used to determine the TBS.

14. The apparatus according to claim 1, wherein, The logic and circuitry are further configured to cause the UE to: Based on the number of symbols and the number of time slots used for PUSCH transmissions carrying TBs spanning more than one time slot, a limit is determined on the total number of resource elements (TBs) allocated for PUSCH transmissions carrying TBs spanning more than one time slot.

15. The apparatus according to claim 1, wherein, The logic and circuitry are further configured to cause the UE to: When a PUSCH transmission spanning more than one time slot (TB) conflicts with an uplink control channel (PUCCH) transmission, a high-priority uplink transmission, or a downlink transmission, the entirety, part, or any time slots of the PUSCH transmission spanning more than one time slot (TB) of the bearer are discarded or canceled.

16. A computer-readable storage medium storing instructions, said instructions, when executed by one or more processors, causing said one or more processors to: Receive downlink control information (DCI) configured to schedule Physical Uplink Shared Channel (PUSCH) transmissions carrying transport blocks (TBs) spanning more than one time slot; and According to the DCI, the PUSCH transmission carrying more than one time slot (TB) is provided to the wireless interface for transmission. in, The fields in the DCI are used to indicate whether the PUSCH transmissions scheduled by the DCI are intended to carry a TB spanning more than one time slot. When the instruction is executed by the one or more processors, it further causes the one or more processors to: determine, according to Radio Resource Control (RRC) signaling associated with the DCI, whether a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot, wherein a portion or a single PUSCH-time domain resource allocation parameter carried in the RRC signaling is configured to indicate whether a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot; When executed by the one or more processors, the instructions further cause the one or more processors to determine the Transport Block Size (TBS) based on the number of time slots, the number of transmission opportunities, or the number of symbols used for the PUSCH transmission that carries a TB spanning more than one time slot.

17. The computer-readable storage medium of claim 16, wherein, The DCI is a non-backoff DCI, or the DCI is DCI format 1_1 or DCI format 1_2.

18. The computer-readable storage medium according to claim 16, wherein, When the instruction is executed by the one or more processors, it further prompts the one or more processors to: The number of time slots, transmission timings, or symbols for the PUSCH transmission carrying a TB spanning more than one time slot is determined based on at least one of the Radio Resource Control (RRC) signaling and the DCI.

19. The computer-readable storage medium according to claim 16, wherein, One or more existing fields in the DCI are repurposed, or a known state of an existing field in the DCI is used, to indicate that a PUSCH transmission scheduled by the DCI is intended to carry a TB spanning more than one time slot.

Images