Time-domain resource allocation for Transport Multi-Slot Block (TBOMS) transmission

Abstract

Various embodiments relate to time-domain resource allocation for Multi-Time-Slot Transport Block (TBoMS) transmission. An apparatus may include: a memory for storing configuration information including a list of shared time-domain resource allocations (TDRAs) associated with Multi-Time-Slot Transport Block (TBoMS) processing; and processing circuitry coupled to the memory to: retrieve the configuration information from the memory, wherein the TDRA list includes entries having indications of scheduling delay (k2) and number of time slots (N) for TBoMS transmission; and encode a message for transmission to a User Equipment (UE) including the configuration information. Other embodiments may be disclosed or claimed.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to the following: U.S. Provisional Patent Application No. 63 / 164,841, filed March 23, 2021; U.S. Provisional Patent Application No. 63 / 174,951, filed April 14, 2021; and U.S. Provisional Patent Application No. 63 / 243,871, filed September 14, 2021. Technical Field

[0003] In summary, the various embodiments may relate to the field of wireless communication. For example, some embodiments may relate to time-domain resource allocation for multi-slot transport block (TBoMS) transmission. Background Technology

[0004] Mobile communications have evolved from early voice systems to today's highly complex integrated communication platforms. The next generation of wireless communication systems, 5G or New Radio (NR), will enable users and applications to access information and share data anytime, anywhere. NR promises to be a unified network / system designed to meet diverse and sometimes conflicting performance dimensions and services. This diverse, multidimensional demand is driven by different services and applications. In general, NR will be developed based on 3GPP LTE-Advanced and other potential New Radio Access Technologies (RATs) to enrich people's lives with better, simpler, and seamless wireless connectivity solutions. NR will make everything wirelessly connected, providing fast, rich content and services. Attached Figure Description

[0005] The embodiments will be readily understood from the following detailed description taken in conjunction with the accompanying drawings. For ease of description, the same reference numerals denote the same structural elements. Embodiments are shown in the drawings by way of example rather than limitation.

[0006] Figure 1 Examples of a type A-based mechanism for TDRA for TBoMS according to various embodiments are shown.

[0007] Figure 2 Examples of a type B-based mechanism for TDRA for TBoMS according to various embodiments are shown.

[0008] Figure 3 A first example of a type B-based TDRA DMRS mode for TBoMS is shown according to various embodiments.

[0009] Figure 4 A second example of a type B-based TDRA DMRS mode for TBoMS according to various embodiments is shown.

[0010] Figure 5 A first example of processing the overlap between TBoMS and other physical channels / signals is shown according to various embodiments.

[0011] Figure 6 A second example of processing the overlap between TBoMS and other physical channels / signals according to various embodiments is shown.

[0012] Figure 7 Examples of single transmission timings of TBoMS when the gap is less than a threshold are shown according to various embodiments.

[0013] Figure 8 Examples of multiple transmission opportunities for TBoMS when the gap is greater than a threshold are shown according to various embodiments.

[0014] Figure 9 Wireless networks according to various embodiments are illustrated schematically.

[0015] Figure 10 The components of a wireless network according to various embodiments are illustrated schematically.

[0016] Figure 11 A block diagram is shown of components, according to some example embodiments, capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transient machine-readable storage medium) and performing any one or more methods discussed herein.

[0017] Figure 12 , 13 14 and 15 depict examples of processes for implementing the various embodiments discussed in this disclosure. Detailed Implementation

[0018] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details such as particular structures, architectures, interfaces, technologies, etc., are described for purposes of explanation and not limitation in order to provide a thorough understanding of various aspects of the various embodiments. However, those skilled in the art who benefit from this disclosure will appreciate that various aspects of the various embodiments may be implemented in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrases "A or B" and "A / B" refer to (A), (B), or (A and B).

[0019] For cellular systems, coverage is a critical factor for successful operation. Compared to Long Term Evolution (LTE) systems, New Radio (NR) systems can be deployed on relatively higher carrier frequencies within Frequency Range 1 (FR1, e.g., 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 transmission power at the User Equipment (UE) side.

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

[0021] In NR Rel-15, the number of repetitions for PUSCH transmissions can be configured to help improve coverage performance. When repetitions are used for both PUCCH and PUSCH transmissions, the same Time Domain Resource Allocation (TDRA) is used in each time slot. Furthermore, performance can be improved by utilizing frequency diversity to configure inter-slot frequency hopping. In Rel-16, the number of PUSCH repetitions can be dynamically indicated in the DCI.

[0022] Furthermore, in NR, transport blocks (TBs) carried by PUSCH are scheduled within a time slot, or the resource allocation for a single data transmission is limited to 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. To maintain a low code rate, transport blocks 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 PUSCH transmission. To support transmissions handling multi-slot TBs (TBoMS), certain design enhancements may need to be considered.

[0023] The embodiments of this disclosure relate to enhancements to transport block processing over multiple time slots of the Physical Uplink Shared Channel (PUSCH). More specifically, some embodiments disclosed herein target:

[0024] • TBoMS time-domain resource allocation instructions

[0025] DMRS mode for TBoMS transmission

[0026] • Mechanisms for handling overlap between TBoMS and other physical signals / channels.

[0027] • Overhead configuration determined by TBS for TBoMS

[0028] TBoMS Time Domain Resource Allocation Instructions

[0029] As described above, transport blocks (TBs) carried by PUSCH are scheduled within a time slot, or the resource allocation for a single data transmission is limited to 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. To maintain a low code rate, transport blocks can span more than one time slot, where a smaller number of physical resource blocks (PRBs) can be allocated across frequencies to improve the link budget for PUSCH transmission. To support transmissions handling multi-slot TBs (TBoMS), certain design enhancements may need to be considered.

[0030] It should be noted that for the Type A mechanism of TDRA used for TBoMS, the same time-domain resource allocation is assigned to TBoMS in each time slot. For the Type B mechanism of TDRA used for TBoMS, consecutive symbols are allocated to TBoMS. Figure 1 and Figure 2 Examples of type A and type B-based mechanisms for TDRA used in TBoMS are shown respectively.

[0031] The following is an example of a TBoMS time-domain resource allocation indicator:

[0032] In one embodiment, for Time Domain Resource Allocation (TDRA) of TBoMS, both Type A and Type B mechanisms can be supported. The Type A or Type B mechanism for TBoMS can be configured by higher layers via Minimum System Information (MSI), Residual Minimum System Information (RMSI), Other System Information (OSI), or Dedicated Radio Resource Control (RRC) signaling, or dynamically indicated in Downlink Control Information (DCI), or a combination thereof.

[0033] It should be noted that for Type A TDRA used for TBoMS, the start and length of each slot in the Start and Length Indicator Value (SLIV) and the number of slots used for TBoMS can be configured as part of the TDRA parameters. For Type B TDRA used for TBoMS, long SLIVs that may span multiple slots can be configured as part of the TBoMS TDRA. In this case, the length of TBoMS can be greater than 14 symbols for Normal CP (NCP) or greater than 12 symbols for Extended CP (ECP).

[0034] Additionally, the maximum number of time slots K for TBoMS transmission can be configured, and this can also be used to determine the number of bits for SLIV indication. More specifically, the length of TBoMS transmission can be less than the number of symbols in the maximum number of time slots. The start symbol S of TBoMS is defined relative to the start symbol of the time slot, and N for NCP can be defined in the first time slot where TBoMS is mapped. symb slot = 14 symbols (plus N for ECP) symb slot =12 symbols)

[0035] Next, consider the allocated TBoMS duration L, where L min ≤L≤K*N symb slot L min It is the minimum number of symbols that can be allocated in a TBoMS. In the example, L min =N symb slot In another example, at least for the type A-based mechanism L of TDRA used for TBoMS. min =N symb slot For the type B mechanism of TDRA used in TBoMS, L min It can be less than N symb slot .

[0036] For such an allocation, in an embodiment, the TDRA used for TBoMS can be indicated according to the SLIV mechanism of the currently specified TDRA. That is, the start symbol S relative to the start of the time slot, and the number L of consecutive symbols L calculated from the symbol S allocated to PUSCH, are determined by the start and length indicator SLIV of the index row:

[0037] if (L-1)≤ floor(K*N) symb slot / 2)then

[0038] SLIV = K * Nsymb slot *(L-1)+S

[0039] else

[0040] SLIV = K * N symb slot *(K*N symb slot –L+1)+(K*N symb slot –1–S),

[0041] where 0 <L min ≤L≤(K*N symb slot –S).

[0042] In the example of the embodiment, the above-described SLIV mechanism applies only to the Type B-based TDRA mechanism for TBoMS. For the Type A-based TDRA mechanism for TBoMS, the single-slot SLIV determination is reused to indicate the allocation in each slot, and the number of slots to which TBoMS is mapped is also provided to the UE.

[0043] In one example, such as Figure 2 As shown, the starting symbol is symbol #2 in the first time slot, and the allocated TBoMS transmission length is 45.

[0044] The aforementioned TDRA determination mechanism leads to significant signaling overhead as K increases. Therefore, in a variant of this embodiment, a minimum of 'n' consecutive symbols can be used to define the SLIV to compress the necessary signaling overhead at the granularity of TDRA, at the cost of reduced flexibility.

[0045] In another embodiment, if the UE is configured to support both type A and type B mechanisms for TDRAs used in TBoMS, a subset of the TDRA list can be configured for either type A or type B TDRAs for TBoMS. When scheduling the UE using entries from the configured subset of TDRAs, the UE can implicitly infer whether to use a type A or type B mechanism.

[0046] Table 1 illustrates an example of TDRA list partitioning indicating a mechanism based on type A or type B. In this example, entries from 0 to N0-1 in the TDRA list are for TBoMS with a mechanism based on type A, while entries from N0 to N1-1 are for TBoMS with a mechanism based on type B. Note that N0 and N1 can be configured by higher layers via MSI, RMSI (SIB1), OSI, or RRC signaling.

[0047] Based on this TDRA list partitioning, when scheduling a UE using TDRA entries from 0 to N0-1, the UE can determine that a type A mechanism is used for TBoMS TDRA. Similarly, when scheduling a UE using TDRA entries from N0 to N1-1, the UE can determine that a type B mechanism is used for TBoMS TDRA.

[0048] Table 1. TDRA list partitions indicating mechanisms based on type A or type B

[0049]

[0050] In another embodiment, a one-bit indicator may be included in the DCI to indicate whether a type A or type B mechanism of the TDRA for TBoMS is applied. It should be noted that this one-bit indicator can be used as part of the TDRA for resource allocation. Alternatively, existing fields in the DCI can be reused to indicate whether a type A or type B mechanism of the TDRA for TBoMS is applied.

[0051] Table 2 shows an example of an indication of a type A or type B mechanism for the TDRA used in TBoMS.

[0052] Table 2. Indicators based on type A or type B mechanisms

[0053]

[0054] In another option, the type A or type B mechanism indicating whether to apply TDRA for TBoMS can be configured by a higher layer via MSI, RMSI (SIB1), OSI, or RRC signaling according to the DCI format. In one example, when the type A mechanism is configured by a higher layer via RRC signaling for DCI format 0_1, only the type A mechanism is used for TDRA of TBoMS when DCI format 0_1 ​​is used to schedule TBoMS for PUSCH transport. In another example, when the type B mechanism is configured by a higher layer via RRC signaling for DCI format 0_2, only the type B mechanism is used for TDRA of TBoMS when DCI format 0_2 is used to schedule TBoMS for PUSCH transport.

[0055] In another embodiment, the TDRA mapping type for TBoMS is implicitly determined by the UE based on the indicated TDRA—if the combination of the indicated start symbol and duration indicates an allocation included within a time slot, the TDRA for TBoMS is identified as following TDRA mapping type A; however, if the combination of the indicated start symbol and duration (indicated via SLIV) indicates an allocation across a time slot boundary, or if the indicated duration is longer than 14 symbols (12 symbols for ECP), the TDRA for TBoMS is identified as following TDRA mapping type B.

[0056] In one embodiment, a shared TDRA table can be configured for both TBoMS and single-slot PUSCH transmissions with or without repetition. Note that for a subset of the TDRA list used for TBoMS, each row of the TDRA table used for TBoMS configures the number of slots (N), repetition count (M), scheduling delay (k2), start and length indicator values ​​(SLIV), and mapping type for a single TBoMS transmission. If M is absent or not configured, repetition is not configured for rows in the TDRA table used for TBoMS transmissions.

[0057] For a subset of the TDRA list for single-slot PUSCH, the PUSCH repetition count, K2, SLIV, and mapping type can be configured in each row of the TDRA table for single-slot PUSCH transmission. Similarly, if the PUSCH repetition count is absent or not configured, repetition is not configured for the rows of the TDRA table used for single-slot PUSCH transmission. Furthermore, multiple slots for a single TBoMS transmission or N=1 can be configured in one or more rows of the TDRA table to indicate single-slot PUSCH transmissions with or without repetition.

[0058] To distinguish between TBoMS and single-slot PUSCH transmissions, in one option, a one-bit indication can be included in each line as part of the TDRA information. In one example, bit "1" can be used to indicate that a single-slot PUSCH transmission is scheduled and bit "0" can be used to indicate that a TBoMS transmission is scheduled.

[0059] In another option, based on TDRA list partitioning, for example, when the UE is configured or scheduled with entries of a configured subset of TDRA, the UE can implicitly infer whether to use TBoMS or single-slot PUSCH transmission.

[0060] Table 3 shows an example of a TDRA list partition indicating that a TBoMS or single-slot PUSCH transmission has been scheduled. In this example, entries from 0 to P0-1 in the TDRA list are TDRA lists for single-slot PUSCH transmissions, while entries from P0 to P1-1 are TDRA lists for TBoMS transmissions. Note that P0 and P1 can be configured via higher layers through MSI, RMSI (SIB1), OSI, or RRC signaling.

[0061] Based on this TDRA list partition, when a UE is scheduled using a TDRA entry in entries 0 to P0-1, the UE can determine that a single-slot PUSCH transmission is scheduled. Similarly, when a UE is scheduled using a TDRA entry in entries P1 to P1-1, the UE can determine that a TBoMS transmission is scheduled.

[0062] Table 3. TDRA List Partitions Indicating TBoMS and Single-Slot PUSCH Transmission

[0063]

[0064] In another embodiment, separate TDRA lists can be configured for TBoMS and single-slot PUSCH transmissions with or without repetition. For the TDRA list configured for TBoMS, the number of slots (N), repetition count (M), k2, SLIV, and mapping type for a single TBoMS transmission can be configured in each row of the TDRA list used for TBoMS.

[0065] Furthermore, to allow dynamic switching between TBoMS and single-slot PUSCH transmissions with or without repetition, the number of slots for a single TBoMS transmission or N=1 can be configured in one or more lines of the TDRA list to indicate whether a single-slot PUSCH transmission has repetitions or not. Alternatively, the number of slots for a single TBoMS transmission can be left unconfigured in one or more lines of the TDRA to indicate whether a single-slot PUSCH transmission has repetitions or not. Note that when N=1 or this parameter is not configured, the number of repetitions (M) can be reinterpreted and applied to single-slot PUSCH transmissions with repetitions.

[0066] In one selection, a single bit in the DCI can be used to indicate whether a TBoMS or single-slot PUSCH transmission is scheduled. Specifically, a bit "1" indicates that a single-slot PUSCH transmission is scheduled, while a bit "0" indicates that a TBoMS transmission is scheduled. Furthermore, if this field is not configured in the DCI, single-slot PUSCH transmissions will be scheduled according to the default configuration. Note that in the case of TBoMS retransmissions, the gNB may switch from TBoMS transmissions to single-slot PUSCH transmissions with or without repetitions, depending on the row selected in the TDRA list.

[0067] Alternatively, one or more of the reserved states in the existing fields of the DCI can be used to indicate whether a TBoMS or single-slot PUSCH transmission has been scheduled.

[0068] In another option, a separate RNTI can be used to schedule TBoMS transmissions. Specifically, this RNTI can be configured or indicated to a UE configured for TBoMS transmissions. When the UE receives a PDCCH with a CRC scrambled using the RNTI, this indicates that TBoMS has been scheduled. Furthermore, for TBoMS transmissions, the initialization seed for scrambling sequence generation is defined based on the RNTI configured / indicated for TBoMS transmissions.

[0069] DMRS mode for TBoMS transmission

[0070] The following provides an example of a demodulation reference signal (DMRS) mode for TBoMS transmission:

[0071] For Type A based on TDRA for TBoMS, the DMRS position in each slot follows the position in the first slot, which is indicated either in the scheduling DCI format or via a higher layer for configuration authorization PUSCH (CG PUSCH) to comply with existing specifications.

[0072] In one embodiment, uniformly distributed DMRS symbols can be used for TBoMS transmission with Type B-based TDRA. Specifically, the distance between the first symbol and the additional symbols in a previously loaded DMRS symbol sequence, as well as the distance between the additional symbols, can be configured by a higher layer via MSI, RMSI (SIB1), OSI, or RRC signaling, or dynamically indicated in the DCI, or a combination thereof. Based on the distance between DMRS symbols and the length of the TBoMS transmission, the UE can deduce the locations of the additional DMRS symbols.

[0073] Figure 3An example of a DMRS mode for TBoMS based on type B TDRA is shown. In this example, 45 symbols are allocated for TBoMS. Furthermore, the distance between DMRS symbols is 14 symbols. In this case, DMRS is transmitted in the first symbol of TBoMS and is transmitted once every 14 symbols in the TBoMS transmission.

[0074] In another variation of the above embodiments, multiple DMRS symbols may be provided to the UE, and these DMRS symbols may be evenly distributed temporally within the TBoMS duration, such that the first DMRS position is in the first symbol of the TBoMS. In this example, the TBoMS duration excludes any invalid symbols that the UE cannot transmit during the TBoMS transmission duration. In another example, the TBoMS duration includes all valid and invalid symbols within the TBoMS transmission duration.

[0075] In another embodiment, when the type B-based TDRA mechanism is used for TBoMS, for TBoMS transmission in the first time slot, the previously loaded DMRS or the DMRS in the first symbol of the TBoMS transmission is used. For subsequent TBoMS transmission time slots, the DMRS is located in the first symbol of that time slot.

[0076] Furthermore, for TBoMS transmissions in the first and last time slots, the positions of the additional DMRS symbols are determined based on the dmrs-AdditionalPosition and the number of symbols in the first and last time slots used for TBoMS transmissions, respectively. For TBoMS transmissions in time slots other than the first and last time slots, the positions of the additional DMRS symbols are determined based on the dmrs-AdditionalPosition and the assumption of full-time-slot transmission within the time slot.

[0077] Figure 4 An example of a DMRS mode for TBoMS based on type B TDRA is shown. In this example, 45 symbols are allocated for TBoMS. Furthermore, previously loaded DMRS are allocated for each TBoMS transmission in each time slot. Additionally, dmrs-AdditionalPosition is configured as "pos1", which indicates that symbol #11 is allocated to the DMRS symbol in the first time slot, symbol #9 is allocated to the DMRS in the second and third time slots, and symbol #4 is allocated to the DMRS in the last symbol.

[0078] In one embodiment, the presence of additional DMRS symbols during the slot duration for TBoMS transmissions follows the existing higher-level configuration (according to 3GPP Release 15 / 16 specifications) for the presence of additional DMRS symbols as part of the DMRS-UplinkConfig. In another embodiment, the presence of additional DMRS can be configured separately for TBoMS and other PUSCH transmissions. In yet another embodiment, for TBoMS transmissions, additional DMRS symbols are always present during the slot duration.

[0079] In this embodiment, the maximum length of the "previously loaded" DMRS symbols (the first set of DMRS symbols in each time slot of the TBoMS transmission) follows the value of the higher-level parameter maxLength provided in DMRS-UplinkConfig. Alternatively, the maximum length of the "previously loaded" DMRS symbols (the first set of DMRS symbols in each time slot of the TBoMS transmission) can be configured separately from the maximum length of other PUSCH transmissions.

[0080] In this embodiment, for TBoMS transmissions, the position of the additional DMRS symbol follows the position of other PUSCH transmissions (e.g., indicated by dmrs-AdditionalPosition in DMRS-UplinkConfig). Alternatively, the position of the additional DMRS symbol for TBoMS transmissions can be configured separately from the position for other PUSCH transmissions.

[0081] Handling overlap between TBoMS and other physical signals / channels

[0082] The following provides an example for handling overlap between TBoMS and other physical signals / channels:

[0083] In one embodiment, when configuring or indicating a Type B-based mechanism for TBoMS transmissions for TDRA, if the resources allocated for TBoMS conflict temporally with invalid symbols for PUSCH transmissions, the TBoMS is fragmented into more than one actual transmission, where each actual transmission comprises a contiguous set of all potentially valid symbols for the TBoMS transmission. Note that each TBoMS transmission may span time slot boundaries or multiple time slots. The length of the initially indicated or configured TBoMS transmission, expressed in symbol count, is called the nominal duration of the TBoMS. The TB size is determined using at least the indicated or configured MCS, Frequency Domain Resource Allocation (FDRA), and the nominal duration of the TBoMS. Furthermore, for a Type B-based mechanism for TDRAs for TBoMS, the rules for determining symbols that may be unavailable (invalid) for TBoMS transmissions can be determined using the same rules specified in Subclause 6.1.2.1 of TS 38.214 for determining invalid symbols for PUSCH repetition Type B.

[0084] Furthermore, if the number of valid symbols for the actual transmission of TBoMS is 1 symbol, the UE omits the actual TBoMS transmission. In another embodiment, if the number of valid symbols for the actual transmission of TBoMS is less than N symbols (where the value of N is specified (e.g., one of 2, 3, or 4) or configured via a higher layer), the UE omits the number of symbols in the actual TBoMS transmission. As another example of this embodiment, the value of N is: the number of symbols for which the effective channel code rate when transmitting on N symbols is not greater than the configured (by a higher layer) or specified threshold code rate for a given FDRA and TB size. In the example, the configured or specified code rate threshold is less than 0.95. Additionally, the actual transmission of TBoMS is omitted according to the conditions defined in Section 11.1 of TS 38.213[1]. It should be noted that in this case, the UE determines the Transport Block Size (TBS) based on the resources allocated in time, and the same TBS is applied to the actual transmission of TBoMS.

[0085] It should be noted that the determination of invalid symbols in TBoMS can follow the rules for PUSCH type B transmission as defined in section 6.1.2.1 of TS 38.214[2].

[0086] Figure 5An example is shown of handling overlap between TBoMS and other physical channels / signals when using a Type B-based mechanism for TDRA used for TBoMS. In the example, 48 symbols are allocated to TBoMS. When the allocated TBoMS resources conflict temporally with semi-static DL symbols and invalid symbols, TBoMS is split into two actual transmissions, each of which may span time slot boundaries, just like TBoMS. In this example, the first actual TBoMS transmission spans 14 symbols, while the second actual TBoMS transmission spans 29 symbols.

[0087] In another embodiment, when configuring or indicating a Type B-based TDRA mechanism for TBoMS transmission, if the resources allocated for TBoMS conflict in time with invalid symbols used for PUSCH transmission, and if the number of consecutive invalid symbols is less than or equal to M symbols, the UE should continue transmitting TBoMS without segmentation. More specifically, M can be configured by a higher layer via MSI, RMSI (SIB1), OSI, or RRC signaling, or predefined in the specification, or depend on the UE's capabilities for TBoMS transmission. In another example, the value of M can be reported by the UE as part of its capability report. Furthermore, if the number of consecutive invalid symbols is greater than M symbols, TBoMS is segmented into more than one actual transmission, where each actual transmission comprises a consecutive set of all potentially valid symbols used for TBoMS transmission.

[0088] Furthermore, the TB size is determined using at least the indicated or configured MCS, Frequency Domain Resource Allocation (FDRA), and the nominal duration of TBoMS. Additionally, as mentioned above, when multiple symbols are not used for TBoMS transmissions within them, rate matching or puncturing is performed on the transmissions used for TBoMS. As an alternative to rate matching or puncturing-based processing of invalid symbols used for TBoMS transmissions, when the gap is less than M symbols long, TB size determination and PUSCH symbol-to-time-frequency resource mapping are performed by excluding symbols invalid for TBoMS transmissions. In other words, the nominal duration of TBoMS is determined by excluding gaps caused by invalid symbols within TBoMS, provided the gap length is M symbols or less.

[0089] It should be noted that the rules used to determine symbols that may be unavailable (invalid) for TBoMS transmission can be determined in accordance with the same rules specified in Subclause 6.1.2.1 of TS38.214 for determining invalid symbols for PUSCH repeat type B.

[0090] Figure 5An example is shown of handling overlap between TBoMS and other physical channels / signals when using a Type B-based mechanism for TDRA used for TBoMS. In the example, 48 symbols are allocated for TBoMS. Furthermore, the number of invalid symbols is 3, less than a predetermined threshold, and the UE continues to transmit TBoMS. Additionally, the total number of symbols allocated for this TBoMS transmission is 45.

[0091] In another embodiment, a TBoMS transmission timing may span non-contiguous time slots or symbols. The number of gaps or consecutive invalid symbols can be determined based on a semi-static TDD UL / DL configuration, SSB symbols, or rules for determining symbols that may be unavailable (invalid) for TBoMS transmission, which can be determined according to the same rules specified in subclause 6.1.2.1 of TS 38.214 for determining invalid symbols for PUSCH repeat type B.

[0092] Furthermore, if the gap is less than or equal to the threshold, the UE can assume a single transmission opportunity for TBoMS, where a single redundant version (RV) is applied to the TBoMS transmission. Alternatively, if the gap is greater than the threshold, the UE can divide the TBoMS transmission into multiple transmission opportunities or repeat them, where the same or different RVs can be applied to each transmission opportunity of the TBoMS.

[0093] The threshold can be configured by higher layers via Minimum System Information (MSI), Residual Minimum System Information (RMSI), Other System Information (OSI), or Dedicated Radio Resource Control (RRC) signaling. This may also depend on the UE's ability to manage gaps within TBoMS transmissions or the timing of TBoMS transmissions.

[0094] It should be noted that when multiple gaps or multiple consecutive invalid symbols are identified, the maximum gap or the maximum number of consecutive invalid symbols can be used to determine the transmission timing for TBoMS transmission.

[0095] Figure 7 An example of a single transmission timing for TBoMS when the gap is less than a threshold is shown. In the example, it is assumed that the threshold is configured for 2 time slots. Based on TDRA and semi-static TDD UL / DL configuration, the gap within TBoMS is 1 time slot. In this case, a single transmission timing using TBoMS, for example, a single redundant version (RV), is applied to the transmission of TBoMS in time slots #0 and #2.

[0096] Figure 8An example of multiple transmission opportunities for TBoMS when the gap is greater than a threshold is shown. In the example, it is assumed that the threshold is configured to be 1 time slot. Based on TDRA and semi-static TDD UL / DL configuration, the gap within TBoMS is 2 time slots. Then, in this case, two transmission opportunities of TBoMS are used, for example, the first transmission opportunity is in time slot #1 and the second transmission opportunity is in time slot #4.

[0097] Overhead configuration determined by TBS for TBoMS

[0098] In NR Rel-15, the number of REs in the PRB used for PUSCH transmission is determined in Section 6.1.4.2 of TS38.214[2]. More specifically,

[0099]

[0100] in This refers to the overhead configured by the higher-level parameter xOverhead in PUSCH-ServingCellConfig. If not configured... (A value from 6, 12, or 18), then assume It is 0.

[0101] The following provides an example of the overhead configuration for TBoMS determination:

[0102] In one embodiment, multiple overhead values ​​can be configured by a higher layer via MSI, RMSI (SIB1), OSI, or RRC signaling, where each overhead value is associated with a range of the number of symbols or time slots. In this case, the UE first determines the number of symbols or time slots based on the resources allocated in time, and then determines the overhead for TBS determination accordingly.

[0103] Table 4 shows an example configuration of the overhead for TBoMS. In the example, N symb,i , (i = 0, 1, 2, 3) is the threshold for the number of symbols, which can be configured by higher layers through MSI, RMSI (SIB1), OSI or RRC signaling or predefined in the specification. This is the overhead of TBS determination configuration for TBoMS. symb It is based on the number of symbols in the TDRA assigned to TBoMS.

[0104] It should be noted that although the number of symbols is used to determine the overhead in Table 4, the same design principle can be directly extended to the case where the number of time slots is used to determine the overhead.

[0105] Table 4. Overhead Configuration for TBoMS

[0106]

[0107] System and Implementation

[0108] Figure 9-10 Various systems, devices, and components that can implement aspects of the disclosed embodiments are shown.

[0109] Figure 9 A network 900 according to various embodiments is illustrated. Network 900 can operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the 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.

[0110] Network 900 may include UE902, which may include any mobile or non-mobile computing device designed to communicate with RAN904 via an over-the-air connection. UE902 may be communicatively coupled to RAN904 via a Uu interface. UE902 may be, but is not limited to, smartphones, tablets, wearable computing devices, desktop computers, laptops, in-vehicle infotainment systems, in-vehicle entertainment systems, instrument clusters, head-up displays, in-vehicle diagnostic equipment, 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, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0111] In some embodiments, network 900 may include multiple UEs that are directly coupled to each other via sidelink interfaces. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, and PSFCH.

[0112] In some embodiments, UE902 can also communicate with AP906 via an over-the-air connection. AP906 can manage WLAN connections, which can be used to offload some / all network services from RAN904. The connection between UE902 and AP906 can conform to any IEEE 802.11 protocol, where AP906 can be Wireless Fibre. Router. In some embodiments, UE902, RAN904, and AP906 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve UE902 configured by RAN904 to utilize both cellular radio resources and WLAN resources.

[0113] RAN904 may include one or more access nodes, such as AN908. AN908 can terminate the air interface protocol of UE902 by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN908 can establish a data / voice connection between CN920 and UE902. In some embodiments, AN908 may be implemented in a discrete device 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 CRAN or a virtual baseband unit pool. AN908 is referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN908 may be a macrocell base station or a low-power base station used to provide femtocells, picocells, or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

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

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

[0116] RAN904 can provide an air interface on both licensed and unlicensed spectrum. For operation in unlicensed spectrum, nodes can use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCell / Scell. Before accessing unlicensed spectrum, nodes can perform medium / carrier sensing operations based on, for example, a Listen-After-Speak (LBT) protocol.

[0117] In V2X scenarios, UE902 or AN908 can be or act as an RSU, which can refer to any transport infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable AN or a fixed (or relatively fixed) UE. An RSU implemented in or by a UE can be called a "UE-type RSU"; an RSU implemented in or by an eNB can be called an "eNB-type RSU"; an RSU implemented in or by a gNB can be called a "gNB-type RSU"; and so on. In one example, an RSU is a computing device coupled to a roadside radio frequency circuitry system that provides connectivity support to passing vehicle UEs. An RSU may also include an internal data storage circuitry system for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. An RSU can provide very low latency communication required for high-speed events such as collision avoidance, traffic warnings, etc. Additionally or alternatively, an 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.

[0118] In some embodiments, RAN904 may be an LTE RAN910 with an eNB (e.g., eNB912). The LTE RAN910 may provide an LTE air interface with the following characteristics: a 15 kHz SCS; CP-OFDM waveforms for DL ​​and SC-FDMA waveforms for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on a sub-6 GHz band.

[0119] In some embodiments, RAN904 may be an NG-RAN914 with a gNB (e.g., gNB916) or an ng-eNB (e.g., ng-eNB918). gNB916 can connect to a 5G-enabled UE using a 5G NR interface. gNB916 can connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. ng-eNB918 can also connect to the 5G core via an NG interface, but can connect to the UE via an LTE air interface. gNB916 and ng-eNB918 can connect to each other via an Xn interface.

[0120] 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 NG user plane (NG-U) interface carries service data between the nodes of NG-RAN914 and UPF948 (e.g., the N3 interface), and the NG control plane (NG-C) interface is the signaling interface between the nodes of NG-RAN914 and AMF944 (e.g., the N2 interface).

[0121] The NG-RAN914 can provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polarity code, repetition code, simplex code and Reed-Muller code for control, and LDPC for data. Similar to the LTE air interface, the 5G-NR air interface can rely on CSI-RS, PDSCH / PDCCHDMRS. The 5G-NR air interface cannot use CRS, but can use PBCH DMRS for PBCH demodulation; PTRS for phase tracking of PDSCH; and a tracking reference signal for time tracking. The 5G-NR air interface can operate on the FR1 band including the sub-6GHz band or the FR2 band including the band from 24.25GHz to 52.6GHz. The 5G-NR air interface can include SSB, which is an area of ​​the downlink resource grid including PSS / SSS / PBCH.

[0122] In some embodiments, the 5G-NR air interface can utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For instance, UE902 can be configured with multiple BWPs, each configured with a different SCS. When a BWP change is indicated to UE902, the transmitted SCS is also changed. Another example of a use case for BWPs involves power saving. In particular, multiple BWPs can be configured for UE902 with different numbers of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with low traffic loads, while allowing power savings at UE902 and, in some cases, at gNB916. A BWP containing a larger number of PRBs can be used for scenarios with high traffic loads.

[0123] RAN904 communications are coupled to CN920, which includes network elements that provide data and telecommunications services to customers / subscribers (e.g., users of UE902). Components of CN920 can be implemented in a single physical node or in separate physical nodes. In some embodiments, NFV can be used to virtualize any or all of the functionality provided by the network elements of CN920 onto physical computing / storage resources such as servers, switches, etc. A logical instantiation of CN920 may be referred to as a network slice, and a logical instantiation of a portion of CN920 may be referred to as a network subslice.

[0124] In some embodiments, CN920 may be an LTE CN922, which may also be referred to as an EPC. The LTE CN922 may include MME924, SGW926, SGSN928, HSS930, PGW932, and PCRF934 coupled to each other via the interface (or "reference point") shown. The functions of the components of the LTE CN922 can be briefly described below.

[0125] The MME924 can implement mobility management functions to track the current location of the UE902 for paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0126] The SGW926 can terminate the S1 interface toward the RAN and route data packets between the RAN and the LTE CN922. The SGW926 can serve as a local mobility anchor for inter-RAN node handover and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and certain policy enforcement.

[0127] The SGSN928 can track the location of UE902 and perform security functions and access control. Furthermore, the SGSN928 can perform inter-EPC node signaling for mobility between different RAT networks; such as PDN and S-GW selection specified by the MME924; and MME selection for handover. The S3 reference point between the MME924 and SGSN928 can facilitate the exchange of user and bearer information for 3GPP indirect access network mobility in idle / active states.

[0128] The HSS930 may include a database for network users, including subscription-related information for network entity processing to support communication sessions. The HSS930 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. The S6a reference point between the HSS930 and MME924 enables the transmission of subscription and authentication data for authenticating / authorizing user access to the LTECN920.

[0129] The PGW932 can terminate its SGi interface toward a data network (DN) 936, which may include an application / content server 938. The PGW932 can route data packets between the LTE CN922 and the data network 936. The PGW932 can be coupled to the SGW926 via an S5 reference point for user plane tunneling and tunnel management. The PGW932 may also include nodes for policy enforcement and charging data collection (e.g., PCEF). Additionally, the SGi reference point between the PGW932 and the data network 936 can be an external public or private PDN or an intra-carrier packet data network, for example, for providing IMS services. The PGW932 can be coupled to the PCRF934 via a Gx reference point.

[0130] PCRF934 is the policy and charging control unit of LTE CN922. PCRF934 is communicatively coupled to app / content server 938 to determine appropriate QoS and charging parameters for service flows. PCRF932 can provide associated rules to PCEF (via Gx reference point) with appropriate TFT and QCI.

[0131] In some embodiments, CN920 may be 5GC940. As shown, 5GC940 may include AUSF942, AMF944, SMF946, UPF948, NSSF950, NEF952, NRF954, PCF956, UDM958, and AF960, which are coupled to each other via interfaces (or "reference points"). The functionality of the components of 5GC940 can be briefly described below.

[0132] The AUSF942 can store data for UE902 authentication and handle authentication-related functions. The AUSF942 facilitates a common authentication framework for various access types. In addition to communicating with other components of the 5GC940 at the indicated reference point, the AUSF942 can also present an interface based on Nausf services.

[0133] The AMF944 allows other functions of the 5GC940 to communicate with UE902 and RAN904 and subscribe to notifications regarding mobility events for UE902. The AMF944 can handle registration management (e.g., for UE902 registration), connection management, reachability management, mobility management, lawful listening to AMF-related events, and access authentication and authorization. The AMF944 can provide SM message transmission between UE902 and SMF946 and act as a transparent broker for routing SM messages. The AMF944 can also provide SMS message transmission between UE902 and the SMSF. The AMF944 can interact with AUSF942 and UE902 to perform various security anchor and context management functions. Furthermore, the AMF944 can be the termination point of the RAN CP interface, which may include or be the N2 reference point between RAN904 and AMF944; the AMF944 can be the termination point of NAS (N1) signaling and perform NAS encryption and integrity protection. The AMF944 can also support NAS signaling with the UE902 via the N3 IWF interface.

[0134] The SMF946 can be responsible for SM (e.g., session establishment, tunnel management between UPF948 and AN908); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring service redirection on UPF948 to route services to appropriate destinations; terminating the interface to policy control functions; control of policy enforcement, charging, and QoS; lawful interception (for SM events and LI system interfaces); termination of the SM portion of NAS messages; downlink data notification; initiating AN-specific SM messages, which are sent to AN908 on N2 via AMF944; 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 UE902 and data network 936.

[0135] The UPF948 can be used as an anchor point for mobility within and between RATs, an external PDU session point interconnecting to the data network 936, and a branch point supporting multihomed PDU sessions. The UPF948 can also perform packet routing and forwarding, packet inspection, user plane portion enforcement of policy rules, lawful packet capture (UP collection), traffic usage reporting, user plane QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic verification (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 UPF948 may include an uplink classifier to support traffic routing to the data network.

[0136] The NSSF950 can select a set of network slice instances to serve UE902. If needed, the NSSF950 can also determine the allowed NSSAIs and the mapping to subscribed S-NSSAIs. The NSSF950 can also determine the set of AMFs or a list of candidate AMFs to use for serving UE902 based on appropriate configuration and possibly by querying the NRF954. The selection of a set of network slice instances for UE902 can be triggered by the AMF944, which UE902 registers with by interacting with the NSSF950, potentially leading to changes in the AMFs. The NSSF950 can interact with the AMF944 via reference point N22; and can communicate with another NSSF in the visited network via reference point N31 (not shown). Additionally, the NSSF950 can expose an interface based on NNSSF services.

[0137] The NEF952 can securely expose services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, AFs (e.g., AF960), edge computing, or fog computing systems. In such embodiments, the NEF952 can authenticate, authorize, or suppress AFs. The NEF952 can also translate information exchanged with the AF960 and information exchanged with internal network functions. For example, the NEF952 can translate between AF-Service-Identifier and internal 5GC information. The NEF952 can also receive information from other NFs based on their exposure capabilities. This information can be stored as structured data in the NEF952 or stored in a data storage NF using a standardized interface. The stored information can then be re-exposed by the NEF952 to other NFs and AFs, or used for other purposes such as analysis. Additionally, the NEF952 can expose interfaces based on Nnef services.

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

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

[0140] UDM958 can process subscription-related information to support network entities in handling communication sessions and can store UE902 subscription data. For example, subscription data can be transmitted via the N8 reference point between UDM958 and AMF944. UDM958 can include two parts: an application front-end and a UDR. The UDR can store subscription and policy data for UDM958 and PCF956, and / or exposed structured data and application data for NEF952 (including PFD for application detection and application request information for multiple UE902). UDR221 can expose an interface based on Nudr services to allow UDM958, PCF956, and NEF952 to access specific groups of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of data changes in the UDR. UDM can include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front-ends can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via the reference point shown in the figure, the UDM958 can also present an interface based on Nudm services.

[0141] The AF960 can provide application impact on service routing, access to NEF, and interaction with policy control frameworks.

[0142] In some embodiments, the 5GC940 can enable edge computing by selecting the operator / third-party service as the point geographically close to where the UE902 is attached to the network. This can reduce latency and load on the network. To provide edge computing implementation, the 5GC940 can select a UPF948 close to the UE902 and perform service redirection from the UPF948 to the data network 936 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by the AF960. In this way, the AF960 can influence UPF(re)selection and service routing. Based on operator deployment, when the AF960 is considered a trusted entity, the network operator can allow the AF960 to interact directly with the relevant NF. Additionally, the AF960 can expose an interface based on Naf services.

[0143] Data network 936 can refer to 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 938.

[0144] Figure 10A wireless network 1000 according to various embodiments is schematically illustrated. The wireless network 1000 may include a UE 1002 that wirelessly communicates with an AN 1004. The UE 1002 and the AN 1004 may be similarly named components described elsewhere herein and may be substantially interchangeable with similarly named components described elsewhere herein.

[0145] UE1002 can be communicatively coupled to AN1004 via connection 1006. Connection 1006 is shown as an air interface that enables communication coupling and can be consistent with cellular communication protocols such as LTE or 5G NR protocols operating at millimeter wave or sub-6 GHz frequencies.

[0146] UE1002 may include a host platform 1008 coupled to a modem platform 1010. Host platform 1008 may include an application processing circuitry system 1012, which may be coupled to a protocol processing circuitry system 1014 of the modem platform 1010. Application processing circuitry system 1012 may run various applications for UE1002, providing source / destination application data. Application processing circuitry system 1012 may also implement one or more layer operations for sending / receiving application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

[0147] The protocol processing circuitry system 1014 can implement one or more layer operations to facilitate the transmission or reception of data via the connection 1006. The layer operations implemented by the protocol processing circuitry system 1014 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0148] The modem platform 1010 may also include a digital baseband circuitry system 1016 that implements one or more layer operations "below" the layer operations performed by the protocol processing circuitry system 1014 in the network protocol stack. These operations may include, for example, PHY operations, including one or more of HARQ-ACK functionality, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, and multi-antenna port precoding / decoding. Multi-antenna port precoding / decoding may include one or more of 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.

[0149] The modem platform 1010 may also include a transmitting circuit system 1018, a receiving circuit system 1020, an RF circuit system 1022, and an RF front-end (RFFE) 1024, which may include or be connected to one or more antenna panels 1026. In short, the transmitting circuit system 1018 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receiving circuit system 1020 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit system 1022 may include a low-noise amplifier, a power amplifier, a power tracking component, etc.; and the RFFE 1024 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 components of the transmitting circuit system 1018, receiving circuit system 1020, RF circuit system 1022, RFFE 1024, and antenna panel 1026 (generally referred to as the "transmit / receive assembly") may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, at millimeter wave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive assembly may be arranged in multiple parallel transmit / receive chains, may be arranged in the same or different chips / modules, etc.

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

[0151] UE reception can be established via and through antenna panel 1026, RFFE 1024, RF circuitry 1022, receiver circuitry 1020, digital baseband circuitry 1016, and protocol processing circuitry 1014. In some embodiments, antenna panel 1026 can receive transmissions from AN1004 via receive beamforming signals received by a plurality of antennas / antenna elements of one or more antenna panels 1026.

[0152] UE transmission can be established via or through protocol processing circuitry 1014, digital baseband circuitry 1016, transmit circuitry 1018, RF circuitry 1022, RFFE 1024, and antenna panel 1026. In some embodiments, the transmit component of UE 1004 may apply a spatial filter to the data to be transmitted to form a transmit beam transmitted by the antenna elements of antenna panel 1026.

[0153] Similar to UE1002, AN1004 may include a host platform 1028 coupled to a modem platform 1030. Host platform 1028 may include an application processing circuitry 1032 coupled to a protocol processing circuitry 1034 of modem platform 1030. The modem platform may also include a digital baseband circuitry 1036, a transmit circuitry 1038, a receive circuitry 1040, an RF circuitry 1042, an RFFE circuitry 1044, and an antenna panel 1046. Components of AN1004 may be similar to components of the same name in UE1002 and are substantially interchangeable with components of the same name in UE1002. In addition to performing data transmission / reception as described above, components of AN1008 may perform various logical functions, including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and packet scheduling.

[0154] Figure 11 This is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transient machine-readable storage medium) and performing any one or more methods discussed herein, according to some example embodiments. Specifically, Figure 11 A graphical representation of hardware resources 1100 is shown, including one or more processors (or processor cores) 1110, one or more memory / storage devices 1120, and one or more communication resources 1130, wherein each communication resource may be communicatively coupled via a bus 1140 or other interface circuitry. In embodiments utilizing node virtualization (e.g., NFV), a hypervisor 1102 may be executed to provide an execution environment for one or more network slices / subslices to utilize hardware resources 1100.

[0155] Processor 1110 may include, for example, processor 1112 and processor 1114. Processor 1110 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 DSP, ASIC, FPGA, radio frequency integrated circuit (RFIC) such as a baseband processor, another processor (including the processors discussed herein), or any suitable combination thereof.

[0156] The memory / storage device 1120 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1120 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 storage devices, etc.

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

[0158] Instructions 1150 may include software, programs, applications, applets, apps, or other executable code for causing at least any one of the processors 1110 to perform any one or more of the methods discussed herein. Instructions 1150 may reside wholly or partially within at least one of the processors 1110 (e.g., within the processor's cache), memory / storage device 1120, or any suitable combination thereof. Furthermore, any portion of instructions 1150 may be transferred from any combination of peripheral device 1104 or database 1106 to hardware resource 1100. Therefore, the memory of processor 1110, memory / storage device 1120, peripheral device 1104, and database 1106 are examples of computer-readable and machine-readable media.

[0159] Example Program

[0160] In some embodiments, Figure 9-11 Electronic devices, networks, systems, chips, or components, or portions thereof, or implementations thereof, may be configured to perform one or more processes, techniques, or methods, or portions thereof, as described herein. Figure 12 The document describes such a process. For example, process 1200 may include: at 1205, retrieving configuration information from memory, which includes a shared time-domain resource allocation (TDRA) list associated with Multi-Slot Transport Block (TBoMS) processing, wherein the TDRA list includes entries with indications of scheduling delay (k2) and number of time slots (N) for TBoMS transmission. The process also includes: at 1210, encoding a message transmitted to the User Equipment (UE), which includes the configuration information.

[0161] Figure 13Another such process is illustrated. In this example, process 1300 includes: at 1305, determining configuration information including a shared time-domain resource allocation (TDRA) list associated with Multi-Slot Transport Block (TBoMS) processing, wherein the TDRA list includes entries with indications of scheduling delay (k2) and number of time slots (N) for TBoMS transmission. The process also includes, at 1310, encoding a message transmitted to the User Equipment (UE) that includes the configuration information.

[0162] Figure 14 Another such process is illustrated. In this example, process 1400 includes: at 1405, receiving a message from the next-generation NodeB (gNB) including configuration information, which includes a shared time-domain resource allocation (TDRA) list associated with Multi-Slot Transport Block (TBoMS) processing, wherein the TDRA list includes entries with indications of scheduling delay (k2) and number of time slots (N) for TBoMS transmission. The process also includes, at 1410, encoding the TBoMS message for transmission based on the configuration information.

[0163] For one or more embodiments, at least one of the components described in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more examples described below. As another example, the circuitry system associated with a UE, base station, network element, etc., as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more examples described in the Examples section below.

[0164] Example

[0165] Example 1 may include a wireless communication method for fifth-generation (5G) or new radio (NR) systems, the method comprising:

[0166] Indication by the next-generation NodeB (gNB) on whether the mechanism based on repetition type A or repetition type B on the Physical Uplink Shared Channel (PUSCH) is used for Multi-Slot Transport Block (TB) (TBoMS); and

[0167] The User Equipment (UE) sends TBoMS on the PUSCH according to this instruction.

[0168] Example 2 may include the methods of Example 1 or some other examples herein, wherein the indication for whether a mechanism based on repetition type A or repetition type B is used for TBoMS may be configured by a higher layer via Minimum System Information (MSI), Residual Minimum System Information (RMSI), Other System Information (OSI), or Dedicated Radio Resource Control (RRC) signaling, or dynamically indicated in Downlink Control Information (DCI), or a combination thereof.

[0169] Example 3 may include the methods of Example 1 or some other examples in this document, wherein the TDRA for TBoMS may be indicated in accordance with the currently specified SLIV mechanism for TDRA, wherein the start symbol S relative to the start of the time slot, and the number L of consecutive symbols calculated from the symbol S assigned to PUSCH, are determined by the start and length indicators SLIV of the index row.

[0170] Example 4 may include the methods of Example 1 or some other examples in this document, wherein if the UE is configured to support type A and type B based mechanisms for TDRA for TBoMS, a subset of the TDRA list may be configured for type A or type B based TDRA for TBoMS.

[0171] Example 5 may include the approach of Example 1 or some other examples in this document, where the UE can implicitly infer whether to use a type A or type B mechanism when scheduling the UE with entries of a configured subset of TDRA.

[0172] Example 6 may include the approach of Example 1 or some other examples in this document, wherein a one-bit indication may be included in the DCI to indicate whether a type A or type B mechanism for TDRA for TBoMS is applied.

[0173] Example 7 may include methods from Example 1 or some other examples in this document, where existing fields in the DCI can be reused to indicate whether a type A or type B-based mechanism for TDRA for TBoMS is applied.

[0174] Example 8 may include the methods of Example 1 or some other examples in this document, wherein the mechanism indicating whether to apply TDRA for TBoMS based on type A or type B can be configured by a higher layer via MSI, RMSI (SIB1), OSI or RRC signaling in the DCI format.

[0175] Example 9 may include the methods of Example 1 or some other examples in this document, wherein the TDRA mapping type for TBoMS is implicitly determined by the UE based on the indicated TDRA.

[0176] Example 10 may include the method of Example 1 or some other examples herein, wherein uniformly distributed DMRS symbols may be used for TBoMS transmission with type B-based TDRA; wherein the distance between the first symbol and the additional symbols in the previously loaded DMRS symbols and the distance between the additional symbols may be configured by a higher layer via MSI, RMSI (SIB1), OSI or RRC signaling, or dynamically indicated in DCI, or a combination thereof.

[0177] Example 11 may include the method of Example 1 or some other examples herein, wherein multiple DMRS symbols may be provided to the UE and then these DMRS symbols are evenly distributed over time during the TBoMS duration, such that the first DMRS position is in the first symbol of the TBoMS.

[0178] Example 12 may include the method of Example 1 or some other examples in this document, wherein when the type B-based TDRA mechanism is used for TBoMS, for TBoMS transmission in the first time slot, the previously loaded DMRS or the DMRS in the first symbol of the TBoMS transmission is used, wherein for subsequent TBoMS transmission time slots, the DMRS is located in the first symbol of that time slot.

[0179] Example 13 may include the method of Example 1 or some other examples in this document, wherein when configuring or indicating a type B-based mechanism for TDRA for a TBoMS transport, if the resources allocated for TBoMS conflict in time with invalid symbols for a PUSCH transport, TBoMS is split into more than one actual transport, wherein each actual transport comprises a contiguous set of all potentially valid symbols for the TBoMS transport.

[0180] Example 14 may include the methods of Example 1 or some other examples in this document, wherein the TB size is determined using at least the indicated or configured MCS, Frequency Domain Resource Allocation (FDRA), and the nominal duration of TBoMS.

[0181] Example 15 may include the method of Example 1 or some other examples herein, wherein if the number of valid symbols used for the actual TBoMS transmission is less than N symbols, where the value of N is specified (e.g., one of 2, 3, or 4) or configured via a higher layer, the UE omits the number of symbols in the actual TBoMS transmission.

[0182] Example 16 may include the method of Example 1 or some other examples herein, wherein when a type B-based TDRA mechanism is configured or indicated for TBoMS transmission, if the resources allocated for TBoMS conflict in time with invalid symbols used for PUSCH transmission, and if the number of consecutive invalid symbols is less than or equal to M symbols, the UE should continue to transmit TBoMS without segmentation.

[0183] Example 17 may include the method of Example 1 or some other examples in this document. M may be configured by a higher layer via MSI, RMSI (SIB1), OSI or RRC signaling, or predefined in the specification, or depending on the UE’s ability to transmit on TBoMS.

[0184] Example 18 may include the method of Example 1 or some other examples in this document, wherein if the number of consecutive invalid symbols is greater than M symbols, TBoMS is divided into more than one actual transmission, wherein each actual transmission comprises a consecutive set of all potentially valid symbols for the transmission used in TBoMS.

[0185] Example 19 may include the method of Example 1 or some other examples in this document, wherein, as described above, rate matching or puncturing is performed on the transmissions used for TBoMS when multiple symbols are not used for TBoMS transmissions in between.

[0186] Example 20 may include the method of Example 1 or some other examples in this document, wherein the nominal duration of TBoMS is determined by excluding gaps caused by invalid symbols within TBoMS, provided that the length of the gap is M symbols or less.

[0187] Example 21 may include the approach of Example 1 or some other examples in this document, wherein multiple overhead values ​​may be configured by a higher layer via MSI, RMSI (SIB1), OSI or RRC signaling, wherein each overhead value is associated with a range of the number of symbols or time slots.

[0188] Example 22 includes the method of Example 1 or some other examples in this document, in which the UE first determines the number of symbols or time slots based on the resources allocated in time, and then determines the overhead for TBS determination accordingly.

[0189] Example 23 may include the method of Example 1 or some other examples herein, wherein if the gap is less than or equal to a threshold, the UE may assume a single transmission timing for TBoMS, wherein a single redundant version (RV) is applied to the transmission of TBoMS; wherein if the gap is greater than the threshold, the UE may divide the TBoMS transmission into multiple transmission timings or repetitions, wherein the same or different RVs may be applied to each transmission timing of TBoMS.

[0190] Example 24 may include the methods of Example 1 or some other examples herein, wherein the threshold may be configured by a higher layer via Minimum System Information (MSI), Residual Minimum System Information (RMSI), Other System Information (OSI), or Dedicated Radio Resource Control (RRC) signaling.

[0191] Example 25 may include the methods of Example 1 or some other examples in this document, wherein a shared TDRA table can be configured for TBoMS and single-slot PUSCH transmissions with or without repetition, wherein for a subset of the TDRA list for TBoMS, the number of slots (N), number of repetitions (M), k2, SLIV, and mapping type for a single TBoMS transmission are configured in each row of the TDRA table for TBoMS.

[0192] Example 26 may include the methods of Example 1 or some other examples in this document, where, based on TDRA list partitioning, for example, when the UE is configured or scheduled with entries of a configured subset of TDRA, the UE may implicitly infer whether to use TBoMS or single-slot PUSCH transmission.

[0193] Example 27 may include the approach of Example 1 or some other examples in this document, where a one-bit indication may be included in each line as part of the TDRA information.

[0194] Example 28 may include the methods of Example 1 or some other examples in this document, where separate lists of TDRAs can be configured for TBoMS and single-slot PUSCH transports with or without duplicates.

[0195] Example 29 may include the methods of Example 1 or some of the examples in this document, wherein the number of slots for a single TBoMS transmission or N=1 can be configured in one or more lines of the TDRA list to indicate whether there is a repeated single-slot PUSCH transmission.

[0196] Example 30 includes a method that includes:

[0197] The configuration information is determined by the next-generation NodeB (gNB), which includes an indication of whether the mechanism based on repetition type A or repetition type B on the Physical Uplink Shared Channel (PUSCH) is used by the User Equipment (UE) for Multi-Time Slot Transport Blocks (TBoMS); and

[0198] The message transmitted to the UE is encoded, and the message includes configuration information.

[0199] Example 31 includes the methods of Example 30 or some other examples in this document, wherein the message is a Minimal System Information (MSI) message, a Residual Minimal System Information (RMSI) message, an Other System Information (OSI) message, a Radio Resource Control (RRC) message, or a Downlink Control Information (DCI) message.

[0200] Example 32 includes the methods of Example 30 or some other examples in this document, where configuration information is also used for the indication of Time Domain Resource Allocation (TDRA) for TBoMS.

[0201] Example 33 includes methods from Example 30 or some other examples in this paper, where TBoMS spans non-contiguous time slots or symbols.

[0202] Example 34 includes methods from Example 33 or some other examples in this paper, where the number of gaps or consecutive invalid symbols is determined based on a semi-static time-division duplex (TDD) uplink (UL) or downlink (DL) configuration.

[0203] Example 35 includes methods from Example 34 or some other examples in this document, where the gap is less than or equal to a threshold associated with a single transmission timing for TBoMS.

[0204] Example 36 includes the methods of Example 35 or some other examples in this paper, where the threshold is two time slots.

[0205] Example 37 includes the method of Example 30 or some other examples in this document, wherein determining configuration information includes: determining a Time Domain Resource Allocation (TDRA) table for TBoMS or single-slot PUSCH transport configurations with or without repetition.

[0206] Example 38 includes the method of Example 37 or some other examples in this document, wherein, for a subset of the TDRA list used for TBoMS, the TDRA table includes the number of time slots (N), the number of repetitions (M), k2, SLIV, and an indication of the mapping type for a single TBoMS transmission.

[0207] Example 39 includes a method from Example 38 or some other examples herein, wherein a TDRA table is used to indicate when the UE is configured or scheduled to have entries for a configured subset of TDRA, and to indicate to the UE whether to use TBoMS or single-slot PUSCH transmission.

[0208] Example 40 may include the methods of Example 38 or some of the examples in this document, wherein a one-bit indication is included as part of the TDRA information in the TDRA table.

[0209] Example 41 may include the method of Example 30 or some of the examples herein, wherein determining the configuration information includes: determining separate TDRA tables, which are configured separately for TBoMS and single-slot PUSCH transports with or without duplication.

[0210] Example 42 may include the method of Example 30 or some other examples herein, wherein the number of time slots for a single TBoMS transmission or N=1 is indicated in the TDRA table to indicate whether there is a repeated single-time-slot PUSCH transmission.

[0211] Example X1 includes an apparatus comprising:

[0212] Memory for storing configuration information, including a list of shared time-domain resource allocations (TDRAs) associated with Multi-Slot Transport Block (TBoMS) processing; and

[0213] The processing circuitry, coupled to the memory, is used for:

[0214] Retrieve configuration information from memory, wherein the TDRA list includes entries with indications of the scheduling delay (k2) and number of time slots (N) for TBoMS transmission; and

[0215] The message transmitted to the user equipment (UE) is encoded, and the message includes configuration information.

[0216] Example X2 includes the apparatus of Example X1 or some other examples herein, wherein the entry also includes an indication of the number of repetitions (M) of the TBoMS transmission.

[0217] Example X3 includes the apparatus of Example X2 or some other examples herein, wherein N=1 in the entry indicates that M will be reinterpreted by the UE and applied to single-slot physical uplink shared channel (PUSCH) transmission.

[0218] Example X4 includes the apparatus of Example X3 or some other examples herein, wherein the entry also includes an indication that M will be reinterpreted by the UE and applied to transmissions with repeated single-slot physical uplink shared channel (PUSCH).

[0219] Example X5 includes the apparatus of any of Examples X1-X4, wherein the entries in the TDRA list include: an indication of a start and length indicator value (SLIV) for TBoMS transmission, or an indication of a mapping type for TBoMS transmission.

[0220] Example X6 includes one or more computer-readable media storing instructions that, when executed by one or more processors, enable the next-generation NodeB (gNB):

[0221] The configuration information is determined, including a list of shared time-domain resource allocations (TDRAs) associated with Multi-Slot Transport Block (TBoMS) processing, wherein the TDRA list includes entries indicating the scheduling delay (k2) and the number of time slots (N) for TBoMS transmission; and

[0222] The message to be transmitted to the user equipment (UE) is encoded, and the message includes configuration information.

[0223] Example X7 includes one or more computer-readable media of Example X6 or some other examples herein, wherein the entries also include an indication of the number of repetitions (M) for TBoMS transmission.

[0224] Example X8 includes one or more computer-readable media of Example X7 or some other examples herein, wherein N=1 in the entry indicates that M will be reinterpreted by the UE and applied to single-slot physical uplink shared channel (PUSCH) transmissions.

[0225] Example X9 includes one or more computer-readable media of Example X8 or some other examples herein, wherein the entry also includes an indication that M will be reinterpreted by the UE and applied to transmissions with repeated single-slot physical uplink shared channel (PUSCH).

[0226] Example X10 includes one or more computer-readable media of any of Examples X6-X9 or some other examples herein, wherein the entries in the TDRA list include: an indication of a start and length indicator value (SLIV) for TBoMS transmission, or an indication of a mapping type for TBoMS transmission.

[0227] Example X11 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to:

[0228] Receive a message from the next-generation NodeB (gNB) including configuration information, which includes a list of shared time-domain resource allocations (TDRAs) associated with Multi-Slot Transport Block (TBoMS) processing, wherein the TDRA list includes entries with indications of scheduling delay (k2) and number of slots (N) for TBoMS transmission; and

[0229] The TBoMS messages used for transmission are encoded based on the configuration information.

[0230] Example X12 includes one or more computer-readable media of Example X11 or some other examples herein, wherein the entries also include an indication of the number of repetitions (M) for TBoMS transmission.

[0231] Example X13 includes one or more computer-readable media of Example X12 or some other examples herein, wherein N=1 in the entry indicates that M will be reinterpreted by the UE and applied to single-slot physical uplink shared channel (PUSCH) transmissions.

[0232] Example X14 includes one or more computer-readable media of Example X13 or some other examples herein, wherein the entries also include an indication that M will be reinterpreted by the UE and applied to transmissions with repeated single-slot physical uplink shared channel (PUSCH).

[0233] Example X15 includes one or more computer-readable media of any of Examples X11-X14 or some other examples herein, wherein the entries in the TDRA list include: an indication of a start and length indicator value (SLIV) for TBoMS transmission, or an indication of a mapping type for TBoMS transmission.

[0234] Example Z01 may include an apparatus comprising various units for performing: one or more elements of a method described or associated with any of Examples 1-X15, or one or more elements of any other method or process described herein.

[0235] Example Z02 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform: one or more elements of a method described or associated with any of Examples 1-X15, or one or more elements of any other method or process described herein.

[0236] Example Z03 may include an apparatus comprising logic, modules, or circuitry for performing: one or more elements of a method described or associated with any of Examples 1-X15, or one or more elements of any other method or process described herein.

[0237] Example Z04 may include the methods, techniques or processes, or parts or components thereof, described or associated with any of Examples 1-X15.

[0238] Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform: a method, technique, or process, or a portion thereof, described or associated with any of Examples 1-X15.

[0239] Example Z06 may include a signal, or a portion thereof, as described or associated with any of Examples 1-X15.

[0240] Example Z07 may include datagrams, packets, frames, segments, protocol data units (PDUs) or messages, or portions or components thereof, as described or associated with any of Examples 1-X15, or others as described in this disclosure.

[0241] Example Z08 may include signals encoded with data, or portions thereof, as described or associated with any of Examples 1-X15, or others as described in this disclosure.

[0242] Example Z09 may include signals encoded, or portions thereof, of datagrams, packets, frames, segments, protocol data units (PDUs) or messages as described or associated with any of Examples 1-X15, or others as described in this disclosure.

[0243] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause one or more processors to perform: a method, technique or process, or a portion thereof, described or associated with any of Examples 1-X15.

[0244] Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform: a method, technique, or process, or a portion thereof, described or associated with any of Examples 1-X15.

[0245] Example Z12 may include signals in wireless networks as shown and described herein.

[0246] Example Z13 may include methods for communicating in a wireless network as shown and described herein.

[0247] Example Z14 may include systems for providing wireless communication as shown and described herein.

[0248] Example Z15 may include devices for providing wireless communication as shown and described herein.

[0249] Unless otherwise expressly stated, any of the above examples may be combined with any other example (or combination of examples). The above description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in accordance with the above teachings, or may be obtained from implementations of the various embodiments.

[0250] abbreviation

[0251] Unless used differently herein, the terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR 21.905v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may be applied to the examples and embodiments discussed herein.

[0252] 3GPP Third Generation Partnership Project

[0253] 4G fourth generation

[0254] 5G (Fifth Generation)

[0255] 5GC 5G Core Network

[0256] AC Application Client

[0257] ACK confirmation

[0258] ACID application client identifier

[0259] AF application functions

[0260] AM Confirmation Mode

[0261] AMBR Aggregated Maximum Bit Rate

[0262] AMF Access and Mobility Management Functions

[0263] AN access network

[0264] ANR Automatic Neighbor Relations

[0265] AP application protocol, antenna port, access point

[0266] API (Application Programming Interface)

[0267] APN (Access Point Name)

[0268] ARP allocation and retention priority

[0269] ARQ (Automatic Repeat Request)

[0270] AS Access Layer

[0271] ASP application service provider

[0272] ASN.1 Abstract Syntax Markup 1

[0273] AUSF Authentication Server Functionality

[0274] AWGN Additive White Gaussian Noise

[0275] BAP Return Route Adaptation Protocol

[0276] BCH Broadcast Channel

[0277] BER (Bit Error Rate)

[0278] BFD Beam Fault Detection

[0279] BLER block error rate

[0280] BPSK (Binary Phase Shift Keying)

[0281] BRAS Broadband Remote Access Server

[0282] BSS Business Support System

[0283] BS base station

[0284] BSR Buffer Status Report

[0285] BW bandwidth

[0286] BWP bandwidth portion

[0287] C-RNTI Cellular Radio Network Temporary Identity

[0288] CA carrier aggregation, certification authority

[0289] CAPEX (Capital Expenditure)

[0290] CBRA (Contest-Based Random Access)

[0291] CC component carrier, country code, cryptographic checksum

[0292] CCA Idle Channel Assessment

[0293] CCE Control Channel Element

[0294] CCCH Common Control Channel

[0295] CE coverage enhancement

[0296] CDM Content Delivery Network

[0297] CDMA Code Division Multiple Access

[0298] CFRA (Contest-Free Random Access)

[0299] CG Community Group

[0300] CGF Billing Gateway Function

[0301] CHF Billing Function

[0302] CI Community Identity

[0303] CID Cell-ID (e.g., location method)

[0304] CIM (Common Information Model)

[0305] CIR carrier interference ratio

[0306] CK key

[0307] CM connection management, conditional enforcement

[0308] CMAS Business Mobile Alarm Service

[0309] CMD command

[0310] CMS Cloud Management System

[0311] CO conditions are optional

[0312] CoMP Coordination Multipoint

[0313] CORESET Control Resource Set

[0314] COTS (Commercial Off-the-shelf Products)

[0315] CP control plane, cyclic prefix, connection point

[0316] CPD Connection Point Descriptor

[0317] CPE client device

[0318] CPICH Common Pilot Channel

[0319] CQI Channel Quality Indicator

[0320] CPU CSI processing unit, Central Processing Unit

[0321] C / R command / response field bits

[0322] CRAN (Cloud Radio Access Network)

[0323] CRB Public Resource Block

[0324] CRC Cyclic Redundancy Check

[0325] CRI (Channel Status Information Resource Indicator), CSI-RS Resource Indicator

[0326] C-RNTI Community RNTI

[0327] CS circuit switching

[0328] CSCF call session control function

[0329] CSAR Cloud Service Archive

[0330] CSI Channel State Information

[0331] CSI-IM CSI Interference Measurement

[0332] CSI-RS CSI Reference Signal

[0333] CSI-RSRP CSI Reference Signal Received Power

[0334] CSI-RSRQ CSI reference signal reception quality

[0335] CSI-SINR, CSI signal-to-noise ratio, and interference ratio

[0336] CSMA (Carrier Sense Multiple Access)

[0337] CSMA / CA with conflict-avoiding CSMA

[0338] CSS public search space, community-specific search space

[0339] CTF Billing Trigger Function

[0340] CTS Clear Send

[0341] CW coding

[0342] CWS Competition Window Size

[0343] D2D device to device

[0344] DC dual-connection, DC

[0345] DCI Downlink Control Information

[0346] DF Deployment Flavor

[0347] DL downlink

[0348] DMTF Distributed Management Task Group

[0349] DPDK Data Plane Development Kit

[0350] DM-RS, DMRS demodulation reference signal

[0351] DN Data Network

[0352] DNN Data Network Name

[0353] DNAI Data Network Access Identifier

[0354] DRB data radio bearer

[0355] DRS detects reference signal

[0356] DRX discontinuous reception

[0357] DSL Domain Specific Language. Digital Subscriber Line.

[0358] DSLAM (DSL Access Multiplexer)

[0359] DwPTS Downlink Pilot Time Slot

[0360] E-LAN ​​Ethernet LAN

[0361] E2E end-to-end

[0362] ECCA Extended Idle Channel Assessment, Extended CCA

[0363] ECCE Enhanced Control Channel Element, Enhanced CCE

[0364] ED energy detection

[0365] Enhanced data rates in the evolution of EDGE GSM (GSM evolution)

[0366] EAS Edge Application Server

[0367] EASID Edge Application Server Identifier

[0368] ECS Edge Configuration Server

[0369] ECSP Edge Computing Service Provider

[0370] EDN Edge Data Network

[0371] EEC Edge Enabler Client

[0372] EECID Edge Enabler Client Identifier

[0373] EES Edge Enabler Server

[0374] EESID Edge Enabler Server Identifier

[0375] EHE Edge Hosting Environment

[0376] EGMF Exposure Governance Management Function

[0377] EGPRS Enhanced GPRS

[0378] EIR Device Identity Register

[0379] eLAA Enhanced Licensed Access, Enhanced LAA

[0380] EM Unit Manager

[0381] eMBB Enhanced Mobile Broadband

[0382] EMS Component Management System

[0383] eNB evolved NodeB, E-UTRAN NodeB

[0384] EN-DC E-UTRA-NR Dual Connectivity

[0385] EPC Evolved Packet Core

[0386] EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel

[0387] EPRE (Energy Per Resource Element)

[0388] EPS Evolution Grouping System

[0389] EREG (Enhanced REG), Enhanced Resource Element Group

[0390] ETSI (European Telecommunications Standards Institute)

[0391] ETWS Earthquake and Tsunami Warning System

[0392] eUICC, Embedded UICC, Embedded Universal Integrated Circuit Card

[0393] E-UTRA Evolution UTRA

[0394] E-UTRAN Evolution UTRAN

[0395] EV2X Enhanced V2X

[0396] F1AP F1 Application Protocol

[0397] F1-C F1 Control Plane Interface

[0398] F1-U F1 User Plane Interface

[0399] FACCH (Fast Correlation Control Channel)

[0400] FACCH / F Fast Correlation Control Channel / Full Rate

[0401] FACCH / H Fast Correlation Control Channel / Half Rate

[0402] FACH Forward Access Channel

[0403] FAUSCH Fast Uplink Signaling Channel

[0404] FB Function Block

[0405] FBI feedback information

[0406] FCC (Federal Communications Commission)

[0407] FCCH Frequency Correction Channel

[0408] FDD (Frequency Division Duplex)

[0409] FDM (Frequency Division Multiplexing)

[0410] FDMA (Frequency Division Multiple Access)

[0411] FE front end

[0412] FEC Forward Error Correction

[0413] FFS is used for further research.

[0414] FFT (Fast Fourier Transform)

[0415] feLAA further enhanced licensed assisted access, further enhanced LAA

[0416] FN Frames

[0417] FPGA (Field Programmable Gate Array)

[0418] FR frequency range

[0419] FQDN (Fully Qualified Domain Name)

[0420] G-RNTI GERAN Radio Network Temporary Identity

[0421] GERAN (GSM EDGE RAN) is a type of radio access network for GSM and EDGE networks.

[0422] GGSN Gateway GPRS Support Nodes

[0423] GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System)

[0424] gNB Next Generation NodeB

[0425] gNB-CU gNB-Centralized Cell, Next-Generation NodeB Centralized Cell

[0426] gNB-DU gNB-Distributed Unit, the next-generation NodeB distributed unit

[0427] GNSS Global Navigation Satellite System

[0428] GPRS General Packet Radio Service

[0429] GPSI General Public Subscription Identifier

[0430] GSM Global System for Mobile Communications, Groupe spécial Mobile

[0431] GTP GPRS Tunneling Protocol

[0432] GTP-UGPRS is a tunneling protocol for the user plane.

[0433] GTS transitions to sleep signals (related to WUS)

[0434] GUMMEI is a globally unique MME identifier.

[0435] GUTI Globally Unique Temporary UE Identifier

[0436] HARQ Hybrid ARQ, a hybrid automatic repeat request mechanism.

[0437] HANDO switch

[0438] HFN Superframe Number

[0439] HHO hard switch

[0440] HLR Home Location Register

[0441] HN Home Network

[0442] HO switch

[0443] HPLMN Home Public Land Mobile Network

[0444] HSDPA High-Speed ​​Downlink Packet Access

[0445] HSN Frequency Hopping Serial Number

[0446] HSPA High-Speed ​​Packet Access

[0447] HSS Home User Server

[0448] HSUPA High-Speed ​​Uplink Packet Access

[0449] HTTP (Hypertext Transfer Protocol)

[0450] HTTPS (Hypertext Transfer Protocol Security) is an HTTP / 1.1 protocol over SSL, operating on port 443.

[0451] I-Block Message Block

[0452] ICCID Integrated Circuit Card Identification

[0453] IAB Integration Access and Backhaul

[0454] ICIC Inter-cell Interference Coordination

[0455] ID (identity) or identifier

[0456] IDFT (Inverse Discrete Fourier Transform)

[0457] IE Information Elements

[0458] IBE In-band Launch

[0459] IEEE Institute of Electrical and Electronics Engineers

[0460] IEI Information Element Identifier

[0461] IEIDL Information Element Identifier Data Length

[0462] IETF Internet Engineering Task Force

[0463] IF Infrastructure

[0464] IM interference measurement, intermodulation, IP multimedia

[0465] IMC IMS Certificate

[0466] IMEI International Mobile Equipment Identity

[0467] IMGI International Mobility Group logo

[0468] IMPI IP Multimedia Private Identifier

[0469] IMPU IP Multimedia Public Signage

[0470] IMS IP Multimedia Subsystem

[0471] IMSI (International Mobile Subscriber Identity)

[0472] IoT (Internet of Things)

[0473] IP Internet Protocol

[0474] IPsec IP Security, Internet Protocol Security

[0475] IP-CAN IP-Connectivity Access Network

[0476] IP-M IP Multicast

[0477] IPv4 (Internet Protocol Version 4)

[0478] IPv6 (Internet Protocol Version 6)

[0479] IR infrared

[0480] IS is synchronizing

[0481] IRP Indicator Reference Points

[0482] ISDN (Integrated Services Digital Network)

[0483] ISIM IM Service Identity Module

[0484] ISO International Organization for Standardization

[0485] ISP (Internet Service Provider)

[0486] IWF Interoperability

[0487] I-WLAN Interconnection WLAN

[0488] Constraint length of convolutional code, USIM

[0489] single key

[0490] kB (kilobytes)

[0491] kbps (kilobits per second)

[0492] Kc encryption key

[0493] Ki Individual User Authentication Key

[0494] KPI Key Performance Indicator

[0495] KQI Key Quality Indicator

[0496] KSI Key Set Identifier

[0497] ksps kilobytes per second

[0498] KVM kernel virtual machine

[0499] L1 Layer 1 (Physical Layer)

[0500] L1-RSRP Layer 1 Reference Signal Received Power

[0501] Layer 2 (Data Link Layer)

[0502] Layer 3 (Network Layer)

[0503] LAA Licensed Assisted Access

[0504] LAN (Local Area Network)

[0505] LADN Local Area Data Network

[0506] LBT Listen before you speak

[0507] LCM Lifecycle Management

[0508] LCR Low Chip Rate

[0509] LCS Location Service

[0510] LCID Logical Channel ID

[0511] LI layer indicator

[0512] LLC logical link control, low-level compatibility

[0513] LPLMN Local PLMN

[0514] LPP LTE positioning protocol

[0515] LSB (Least Significant Bit)

[0516] LTE Long Term Evolution

[0517] LWA LTE-WLAN aggregation

[0518] LWIP with IPsec tunneling, LWIP LTE / WLAN radio-grade integrated LTE Long Term Evolution

[0519] M2M (Machine-to-Machine)

[0520] MAC Media Access Control (Protocol Layering Context)

[0521] MAC Message Authentication Code (Security / Encryption Context)

[0522] MAC-A is a MAC used for authentication and key negotiation (TSG T WG3 scenario).

[0523] MAC-I is a MAC used for data integrity of signaling messages (TSG T WG3 scenario).

[0524] MANO Management and Scheduling

[0525] MBMS Multimedia Broadcasting and Multicast Services

[0526] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0527] MCC Mobile Country Code

[0528] MCG Main Cell Group

[0529] MCOT maximum channel occupancy time

[0530] MCS modulation and coding scheme

[0531] MDAF Management Data Analysis Function

[0532] MDAS Management Data Analysis Service

[0533] Minimize MDT-driven testing

[0534] ME mobile devices

[0535] MeNB main eNB

[0536] MER message error rate

[0537] MGL Measurement Gap Length

[0538] MGRP measurement gap repetition cycle

[0539] MIB (Master Information Block), Management Information Base

[0540] MIMO (Multiple Input Multiple Output)

[0541] MLC Mobile Location Center

[0542] MM Mobility Management

[0543] MME (Mobility Management Entity)

[0544] MN master node

[0545] MNO mobile network operator

[0546] MO (Measurement Object), Movement Origin

[0547] MPBCH MTC Physical Broadcast Channel

[0548] MPDCCH MTC Physical Downlink Control Channel

[0549] MPDSCH MTC Physical Downlink Shared Channel

[0550] MPRACH MTC Physical Random Access Channel

[0551] MPUSCH MTC Physical Uplink Shared Channel

[0552] MPLS (Multiprotocol Label Switching)

[0553] MS mobile station

[0554] MSB Most significant bit

[0555] MSC Mobile Switching Center

[0556] MSI Minimum System Information

[0557] MCH scheduling information

[0558] MSID (Mobile Site Identifier)

[0559] MSIN (Mobile Station Identifier)

[0560] MSISDN Mobile Subscriber ISDN Number

[0561] MT mobile termination, mobile end connection

[0562] MTC machine-type communication

[0563] mMTC (Massively Machine-Type Communication)

[0564] MU-MIMO (Multi-User MIMO)

[0565] MWUS MTC wake-up signal, MTC WUS

[0566] NACK (Negative Response)

[0567] NAI Network Access Identifier

[0568] NAS (Non-Access Layer)

[0569] NCT Network Connection Topology

[0570] NC-JT Non-coherent Joint Transmission

[0571] NEC Network Capabilities Exposure

[0572] NE-DC NR-E-UTRA Dual Connectivity

[0573] NEF Network Exposure Function

[0574] NF Network Functions

[0575] NFP Network Forwarding Path

[0576] NFPD Network Forwarding Path Descriptor

[0577] NFV (Network Functions Virtualization)

[0578] NFVI NFV infrastructure

[0579] NFVO NFV orchestrator

[0580] NG Next Generation, Next Generation Intercontinent

[0581] NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity

[0582] NM Network Manager

[0583] NMS Network Management System

[0584] N-PoP network existence points

[0585] NMIB, N-MIB narrowband MIB

[0586] NPBCH Narrowband Physical Broadcast Channel

[0587] NPDCCH Narrowband Physical Downlink Control Channel

[0588] NPDSCH Narrowband Physical Downlink Shared Channel

[0589] NPRACH Narrowband Physical Random Access Channel

[0590] NPUSCH Narrowband Physical Uplink Shared Channel

[0591] NPSS Narrowband Master Synchronization Signal

[0592] Narrowband secondary synchronization signal (NSSS)

[0593] NR New Radio, Neighborhood Relations

[0594] NRF NF storage function

[0595] NRS Narrowband Reference Signal

[0596] NS Network Services

[0597] NSA Non-Standalone Operation Mode

[0598] NSD Network Service Descriptor

[0599] NSR Network Service Records

[0600] NSSAI Network Slice Selection Assistance Information

[0601] S-NNSAI Single NSSAI

[0602] NSSF Network Slice Selection Function

[0603] NW Network

[0604] NWUS narrowband wake-up signal, narrowband WUS

[0605] NZP non-zero power

[0606] O&M Operation and Maintenance

[0607] ODU2 Optical Channel Data Unit - Type 2

[0608] OFDM (Orthogonal Frequency Division Multiplexing)

[0609] OFDMA (Orthogonal Frequency Division Multiple Access)

[0610] Out-of-band (OOB)

[0611] OOS out of step

[0612] OPEX transaction fees

[0613] OSI Other System Information

[0614] OSS Operation Support System

[0615] OTA (Over-the-Air) Download

[0616] PAPR peak-to-average power ratio

[0617] PAR peak-to-average ratio

[0618] PBCH (Physical Broadcast Channel)

[0619] PC power control, personal computers

[0620] PCC main component carrier, main CC

[0621] P-CSCF proxy CSCF

[0622] PCell Main Cell

[0623] PCI Physical Cell ID, Physical Cell Identity

[0624] PCEF policy and billing enforcement functions

[0625] PCF policy control function

[0626] PCRF policy control and billing rules functions

[0627] PDCP (Packet Data Convergence Protocol) is a packet data convergence protocol layer.

[0628] PDCCH (Physical Downlink Control Channel)

[0629] PDCP (Packet Data Convergence Protocol)

[0630] PDN (Packet Data Network), Public Data Network

[0631] PDSCH (Physical Downlink Shared Channel)

[0632] PDU Protocol Data Unit

[0633] PEI Permanent Device Identifier

[0634] PFD Packet Flow Description

[0635] P-GW PDN Gateway

[0636] PHICH Physical Hybrid ARQ Indicator Channel

[0637] PHY physical layer

[0638] PLMN Public Land Mobile Network

[0639] PIN Personal Identifier

[0640] PM Performance Measurement

[0641] PMI Precoding Matrix Indicator

[0642] PNF (Physical Network Function)

[0643] PNFD Physical Network Function Descriptor

[0644] PNFR Physical Network Function Record

[0645] POC (PoC) based on cellular PTT

[0646] PP, PTP point-to-point

[0647] PPP (Point-to-Point Protocol)

[0648] PRACH Physical RACH

[0649] PRB (Physical Resource Block)

[0650] PRG Physical Resource Block Group

[0651] ProSe ProSe proximity service, a service based on proximity.

[0652] PRS Positioning Reference Signal

[0653] PRR Packet Receive Radio

[0654] PS Grouping Service

[0655] PSBCH Physical Side Link Broadcast Channel

[0656] PSDCH Physical Side Downlink Channel

[0657] PSCCH (Physical Side Link Control Channel)

[0658] PSSCH Physical Side Link Shared Channel

[0659] PSCell main SCell

[0660] PSS Master Synchronization Signal

[0661] PSTN (Public Switched Telephone Network)

[0662] PT-RS phase tracking reference signal

[0663] PTT One-Click

[0664] PUCCH (Physical Uplink Control Channel)

[0665] PUSCH Physical Uplink Shared Channel

[0666] QAM Quadrature Amplitude Modulation

[0667] QoS class of QCI identifier

[0668] QCL Quasi-co-located

[0669] QFI QoS Flow ID, QoS Flow Identifier

[0670] QoS (Quality of Service)

[0671] QPSK Quadrature Phase Shift Keying

[0672] QZSS Quasi-Zenith Satellite System

[0673] RA-RNTI Random Access RNTI

[0674] RAB (Radio Access Bearer) for Random Access Bursts

[0675] RACH Random Access Channel

[0676] RADIUS Remote Authentication Dial-in User Service

[0677] RAN (Radio Access Network)

[0678] RAND RANDom number (used for authentication)

[0679] RAR Random Access Response

[0680] RAT Radio Access Technology

[0681] RAU Routing Area Update

[0682] RB resource block, radio bearer

[0683] RBG resource block group

[0684] REG Resource Element Group

[0685] Rel version

[0686] REQ Request

[0687] RF (Radio Frequency)

[0688] RI rank indicator

[0689] RIV resource indicator value

[0690] RL radio link

[0691] RLC Radio Link Control, Radio Link Control Layer

[0692] RLC AM RLC Confirmation Mode

[0693] RLC UM RLC Unconfirmed Mode

[0694] RLF radio link failure

[0695] RLM Radio Link Monitoring

[0696] RLM-RS is a reference signal used for RLM.

[0697] RM Registration Management

[0698] RMC Reference Measurement Channel

[0699] RMSI (Remaining Minimum System Information)

[0700] RN relay node

[0701] RNC Radio Network Controller

[0702] RNL Radio Network Layer

[0703] RNTI (Radio Network Temporary Identifier)

[0704] ROHC Robust Header Compression

[0705] RRC Radio Resource Control, Radio Resource Control Layer

[0706] RRM Radio Resource Management

[0707] RS reference signal

[0708] RSRP reference signal received power

[0709] RSRQ reference signal reception quality

[0710] RSSI Received Signal Strength Indicator

[0711] RSU roadside unit

[0712] RSTD (Reference Signal Time Difference)

[0713] RTP Real-Time Protocol

[0714] RTS ready to send

[0715] RTT round trip time

[0716] Rx (receiver, receiver)

[0717] S1AP S1 Application Protocol

[0718] S1-MME is used for the S1 control plane.

[0719] S1-U is used for the user plane.

[0720] S-CSCF Service CSCF

[0721] S-GW Service Gateway

[0722] S-RNTI SRNC Radio Network Temporary Identity

[0723] S-TMSI SAE Temporary Mobile Station Identifier

[0724] SA Independent Operation Mode

[0725] SAE System Architecture Evolution

[0726] SAP Service Access Point

[0727] SAPD Service Access Point Descriptor

[0728] SAPI Service Access Point Identifier

[0729] SCC secondary component carrier, secondary CC

[0730] SCell Auxiliary Community

[0731] SCEF service capability exposure function

[0732] SC-FDMA Single-Carrier Frequency Division Multiple Access

[0733] SCG Auxiliary Community Group

[0734] SCM Security Context Management

[0735] SCS Subcarrier Spacing

[0736] SCTP Flow Control Protocol

[0737] SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer

[0738] SDL assisted downlink

[0739] SDNF (Structured Data Storage Network) Functionality

[0740] SDP Session Description Protocol

[0741] SDSF structured data storage function

[0742] SDU Service Data Unit

[0743] SEAF Safety Anchor Function

[0744] SeNB and eNB

[0745] SEPP Secure Edge Protection Agent

[0746] SFI Slot Format Indicator

[0747] SFTD (Spatial-Frequency Time Diversity), SFN (Spatial-Frequency Time Differential), and Frame Timing Difference

[0748] SFN system frame number

[0749] SgNB secondary gNB

[0750] SGSN service GPRS supported nodes

[0751] S-GW Service Gateway

[0752] SI System Information

[0753] SI-RNTI System Information RNTI

[0754] SIB System Information Block

[0755] SIM User Identity Module

[0756] SIP Session Initiation Protocol

[0757] System in SiP package

[0758] SL side link

[0759] SLA (Service Level Agreement)

[0760] SM Session Management

[0761] SMF Session Management Function

[0762] SMS (Short Message Service)

[0763] SMSF SMS Function

[0764] SMTC Measurement Timing Configuration Based on SSB

[0765] SN (Secondary Node), Serial Number

[0766] SoC (System-on-a-Chip)

[0767] SON Self-Organizing Network

[0768] SpCell Dedicated Cell

[0769] SP-CSI-RNTI Semi-Permanent CSI RNTI

[0770] SPS Semi-Permanent Scheduling

[0771] SQN serial number

[0772] SR scheduling request

[0773] SRB signaling radio bearer

[0774] SRS Detection Reference Signal

[0775] SS synchronization signal

[0776] SSB Synchronization Signal Block

[0777] SSID (Service Set Identifier)

[0778] SS / PBCH block

[0779] SSBRI SS / PBCH block resource indicator, synchronization signal block resource indicator

[0780] SSC Session and Service Continuity

[0781] SS-RSRP Reference Signal Received Power Based on Synchronization Signal

[0782] SS-RSRQ Reference Signal Reception Quality Based on Synchronization Signal

[0783] SS-SINR is based on the signal-to-noise ratio and interference ratio of the synchronization signal.

[0784] SSS auxiliary synchronization signal

[0785] SSSG Search Space Collection Group

[0786] SSSIF Search Space Set Indicator

[0787] SST Slicing / Service Type

[0788] SU-MIMO Single-User MIMO

[0789] SUL supplements uplink

[0790] TA will be scheduled in advance to track the area.

[0791] TAC Tracking Area Code

[0792] TAG Timed Advance Group

[0793] TAI tracks regional identity

[0794] TAU tracking area update

[0795] TB transfer block

[0796] TBS (Transfer Block Size)

[0797] TBD to be defined

[0798] TCI Transport Configuration Indicator

[0799] TCP Transmission Communication Protocol

[0800] TDD (Time Division Duplex)

[0801] TDM (Time Division Multiplexing)

[0802] TDMA (Time Division Multiple Access)

[0803] TE terminal equipment

[0804] TEID (Tunnel Endpoint Identifier)

[0805] TFT Business Flow Template

[0806] TMSI Temporary Mobile User Identity

[0807] TNL Transport Network Layer

[0808] TPC transmit power control

[0809] TPMI Transport Precoding Matrix Indicator

[0810] TR Technical Report

[0811] TRP, TRxP Transmitter / Receiver Point

[0812] TRS Tracking Reference Signal

[0813] TRx transceiver

[0814] TS Technical Specifications, Technical Standards

[0815] TTI Transmission Time Interval

[0816] Tx transmission, transmission, transmitter

[0817] U-RNTI UTRAN Radio Network Temporary Identity

[0818] UART Universal Asynchronous Receiver and Transmitter

[0819] UCI uplink control information

[0820] UE User Equipment

[0821] UDM Unified Data Management

[0822] UDP User Datagram Protocol

[0823] UDSF Unstructured Data Storage Network Function

[0824] UICC General Integrated Circuit Card

[0825] UL uplink

[0826] UM Unconfirmed Mode

[0827] UML (Unified Modeling Language)

[0828] UMTS Universal Mobile Telecommunication System

[0829] UP User Plane

[0830] UPF User Plane Functions

[0831] URI (Uniform Resource Identifier)

[0832] URL Uniform Resource Locator

[0833] URLLC: Ultra-reliable, low latency

[0834] USB Universal Serial Bus

[0835] USIM Universal Subscriber Identity Module

[0836] USS UE-specific search space

[0837] UTRA UMTS Terrestrial Wireless Access

[0838] UTRAN (Universal Terrestrial Radio Access Network)

[0839] UwPTS Uplink Pilot Time Slot

[0840] V2I (Vehicle-to-Infrastructure)

[0841] V2P (Vehicle-to-Pedestrian)

[0842] V2V (Vehicle-to-Vehicle)

[0843] V2X: From Vehicles to Everything

[0844] VIM Virtualization Infrastructure Manager

[0845] VL Virtual Link

[0846] VLAN (Virtual Local Area Network)

[0847] VM virtual machine

[0848] VNF Virtualization Network Function

[0849] VNFFG VNF forwarded image

[0850] VNFFGD VNF Forwarding Graph Descriptor

[0851] VNFM VNF Manager

[0852] VoIP (Voice over IP) is a type of communication technology that uses the Internet Protocol (IP) to communicate with other users.

[0853] VPLMN surveyed public terrestrial mobile networks

[0854] VPN (Virtual Private Network)

[0855] VRB (Virtual Resource Block)

[0856] WiMAX Global Microwave Access Interoperability

[0857] WLAN (Wireless Local Area Network)

[0858] WMAN Wireless Metropolitan Area Network

[0859] WPAN (Wireless Personal Area Network)

[0860] X2-C X2-Control Plane

[0861] X2-U X2-User Plane

[0862] XML (Extensible Markup Language)

[0863] XRES Expected User Response

[0864] XOR (Exclusive OR)

[0865] ZC Zadoff-Chu

[0866] ZP Zero Power

[0867] the term

[0868] For the purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein.

[0869] As used herein, the term "circuit system" refers to hardware components configured to provide the described functionality, such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) and / or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc., or is part of or includes said hardware components. In some embodiments, the circuit system may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit system" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and program code for performing the functionality of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit system.

[0870] As used herein, the term "processor circuit system" refers to, is part of, or includes, a circuit system capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transmitting digital data. A processing circuit system may include one or more processing cores that execute instructions and one or more memory structures that store program and data information. The term "processor circuit system" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (e.g., program code, software modules, and / or functional procedures). A processing circuit system may include further hardware accelerators, which may be microprocessors, programmable processing devices, etc. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuit system" and / or "baseband circuit system" may be considered synonymous with "processor circuit system" and may be referred to as such.

[0871] As used herein, the term "interface circuit system" refers to, is part of, or includes a circuit system capable of exchanging information between two or more components or devices. The term "interface circuit system" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, etc.

[0872] As used herein, the term "User Equipment" or "UE" refers to a device with radio communication capabilities and can describe a remote user of network resources in a communication network. The term "User Equipment" or "UE" may be considered synonymous with client, mobile device, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc., and may be referred to as such. Furthermore, the term "User Equipment" or "UE" can include any type of wireless / wired device or any computing device including a wireless communication interface.

[0873] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as the above, including networked computers, network hardware, network devices, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN devices, RAN nodes, gateways, servers, virtualized virtual networks (VNFs), and NFVIs.

[0874] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the terms "computer system" and / or "system" may refer to individual components of a computer that are communicatively coupled to each other. Furthermore, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or network resources.

[0875] As used herein, the terms “appliance,” “computer appliance,” etc., refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide particular computing resources. A “virtual appliance” is a virtual machine image implemented by a device equipped with a hypervisor, which virtualizes or emulates a computer appliance or is specifically designed to provide particular computing resources.

[0876] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, and / or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, electrical power, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage devices, networks, databases and applications, workload units, etc. "Hardware resources" can refer to computing, storage, and / or networking resources provided by physical hardware components. "Virtualization resources" can refer to computing, storage, and / or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resources" or "communication resources" can refer to resources accessible by computer equipment / systems via a communication network. The term "system resources" can refer to any type of shared entity providing services and can include computing and / or networking resources. System resources can be considered as a set of coherent functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0877] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to transmit data or data streams. The term "channel" may be synonymous and / or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar term denoteing a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices via a RAT for sending and receiving information.

[0878] As used in this article, the terms "instantiation" and "instantiation behavior" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which can occur, for example, during the execution of program code.

[0879] This document uses the terms "coupling," "communication coupling," and their derivatives. The term "coupling" can refer to two or more elements in direct physical or electrical contact with each other, or two or more elements in indirect contact but still cooperating or interacting with each other, and / or can refer to one or more other elements coupled or connected between elements referred to as coupled to each other. The term "direct coupling" can refer to two or more elements in direct contact with each other. The term "communication coupling" can refer to two or more elements being in contact with each other through communication means, including wired or other interconnected connections, wireless communication channels or links, etc.

[0880] The term "information element" refers to a structured element that contains one or more fields. The term "field" refers to the individual content of an information element, or a data element that contains content.

[0881] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0882] The term "SSB" refers to the SS / PBCH block.

[0883] The term "primary cell" refers to an MCG cell operating on the primary frequency, in which the UE performs the initial connection establishment procedure or initiates a connection reconstruction procedure.

[0884] The term "primary SCG cell" refers to the SCG cell in which the UE performs random access when performing a reconfiguration with a Sync procedure for DC operation.

[0885] The term "secondary cell" refers to a cell that provides additional radio resources on top of a dedicated cell for a UE configured with a CA.

[0886] The term "secondary cell group" refers to a subset of serving cells, including PSCell and zero or more secondary cells, for a UE configured with a DC.

[0887] The term "serving cell" refers to the primary cell of a UE in RRC_CONNECTED that is not configured with CA / DC, and there is only one serving cell that includes the primary cell.

[0888] The term "serving cell" or "multiple serving cells" refers to the set of cells, including dedicated cells and all secondary cells, for a UE configured with CA / in RRC_CONNECTED.

[0889] The term "dedicated cell" refers to the PCcell of the MCG or the PSCell of the SCG used for DC operation; otherwise, the term "dedicated cell" refers to the Pcell.

Claims

1. A communication device, comprising: The memory stores configuration information, including a list of shared time-domain resource allocations (TDRAs) associated with multi-slot transport block (TBoMS) processing. as well as The processing circuitry system is coupled to the memory to: Retrieve configuration information from the memory, wherein the TDRA list includes entries indicating a scheduling delay k2 and a slot number N for TBoMS transmission and single-slot Physical Uplink Shared Channel (PUSCH) transmission, wherein a slot number N greater than 1 indicates TBoMS transmission, and a slot number N of 1 indicates single-slot PUSCH transmission; and The message to be transmitted to the user equipment (UE) is encoded, the message including the configuration information.

2. The communication apparatus according to claim 1, wherein The entry also includes an indication of the number of repetitions M for TBoMS transmission.

3. The communication device according to claim 2, wherein, The N=1 in the entry indicates that M will be reinterpreted by the UE and applied to single-slot physical uplink shared channel (PUSCH) transmission.

4. The communication device according to claim 3, wherein, The entry also includes an indication that M will be reinterpreted by the UE and applied to transmissions with repeated single-slot physical uplink shared channel (PUSCH).

5. The communication device according to any one of claims 1-4, wherein, The entries in the TDRA list include: indications of start and length indicator values ​​(SLIVs) for TBoMS transmission, or indications of mapping types for TBoMS transmission.

6. One or more computer-readable media storing instructions that, when executed by one or more processors, enable a next-generation NodeB (gNB): The configuration information is determined, including a shared time-domain resource allocation (TDRA) list associated with Multi-Slot Transport Block (TBoMS) processing. The TDRA list includes entries indicating a scheduling delay k2 and a slot number N for both TBoMS transmission and Single-Slot Physical Uplink Shared Channel (PUSCH) transmission, wherein a slot number N greater than 1 indicates TBoMS transmission, and a slot number N of 1 indicates Single-Slot PUSCH transmission; and The message to be transmitted to the user equipment (UE) is encoded, the message including the configuration information.

7. The one or more computer-readable media according to claim 6, wherein, The entry also includes an indication of the number of repetitions M for TBoMS transmission.

8. The one or more computer-readable media according to claim 7, wherein, The N=1 in the entry indicates that M will be reinterpreted by the UE and applied to single-slot physical uplink shared channel (PUSCH) transmission.

9. The one or more computer-readable media according to claim 8, wherein, The entry also includes an indication that M will be reinterpreted by the UE and applied to transmissions with repeated single-slot physical uplink shared channel (PUSCH).

10. One or more computer-readable media according to any one of claims 6-9, wherein, The entries in the TDRA list include: indications of start and length indicator values ​​(SLIVs) for TBoMS transmission, or indications of mapping types for TBoMS transmission.

11. One or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: Receive a message from the next-generation NodeB (gNB) including configuration information, which includes a list of shared time-domain resource allocations (TDRAs) associated with Multi-Slot Transport Block (TBoMS) processing. The TDRA list includes entries indicating a scheduling delay k2 and a slot number N for both TBoMS transmission and Single-Slot Physical Uplink Shared Channel (PUSCH) transmission, wherein a slot number N greater than 1 indicates TBoMS transmission, and a slot number N of 1 indicates Single-Slot PUSCH transmission; and The TBoMS messages used for transmission are encoded based on the configuration information.

12. One or more computer-readable media according to claim 11, wherein, The entry also includes an indication of the number of repetitions M for TBoMS transmission.

13. One or more computer-readable media according to claim 12, wherein, The N=1 in the entry indicates that M will be reinterpreted by the UE and applied to single-slot physical uplink shared channel (PUSCH) transmission.

14. One or more computer-readable media according to claim 13, wherein, The entry also includes an indication that M will be reinterpreted by the UE and applied to transmissions with repeated single-slot physical uplink shared channel (PUSCH).

15. One or more computer-readable media according to any one of claims 11-14, wherein, The entries in the TDRA list include: indications of start and length indicator values ​​(SLIVs) for TBoMS transmission, or indications of mapping types for TBoMS transmission.

Images