Time domain resource allocation for multi-slot transport block (TBOMS) transmission

Abstract

Various embodiments are directed to time domain resource allocation for transport block over multiple slots (TBoMS) transmission. An apparatus includes a memory storing configuration information including a shared time domain resource allocation (TDRA) list associated with transport block over multiple slots (TBoMS) processing; and a processing circuit coupled to the memory, the processing circuit performing the steps of: retrieving the configuration information from the memory, the TDRA list including an entry having an indication of a scheduling delay (k2) and a number of slots (N) for TBoMS transmission; and encoding a message for transmission to a user equipment (UE) including the configuration information. Other embodiments may be disclosed or claimed.

Description

[Technical Field]

[0001] Cross-references to related applications This application claims priority to: 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).

[0002] field Various embodiments may generally relate to the field of wireless communications. For example, some embodiments may relate to time-domain resource allocation for transport block (TBoMS) transmission on multiple slots. [Background technology]

[0003] Mobile communications have evolved remarkably from early voice systems to today's highly sophisticated integrated communication platforms. Next-generation wireless communication systems, 5G, or New Radio (NR), will provide diverse users and applications with access to information and data sharing anywhere, anytime. NR is expected to be a unified network / system aiming to meet vastly different and sometimes competing performance dimensions and services. Such diverse and multidimensional requirements are driven by various services and applications. Generally, NR will evolve based on 3GPP® LTE-Advanced, along with further potential new Radio Access Technology (RAT), to enrich people's lives with better, simpler, and more seamless wireless connectivity solutions. NR will enable everything wirelessly connected, delivering high-speed, rich content and services. [Brief explanation of the drawing]

[0004] Embodiments will be readily understood by the following detailed description in relation to the accompanying drawings. For the sake of this description, similar reference numerals indicate similar structural elements. Embodiments are shown in the figures of the accompanying drawings as examples, not as limitations. [Figure 1] Examples of Type A-based mechanisms for TDRA of TBoMS by various embodiments are shown. [Figure 2] Examples of Type B-based mechanisms for TDRA of TBoMS are shown in various embodiments. [Figure 3] The first example of a DMRS pattern for a Type B-based TDRA for TBoMS is shown, according to various embodiments. [Figure 4] A second example of a DMRS pattern for a Type B-based TDRA for TBoMS is presented, according to various embodiments. [Figure 5] A first example of handling overlap between TBoMS and other physical channels / signals using various embodiments is shown. [Figure 6] A second example of handling overlap between TBoMS and other physical channels / signals using various embodiments is shown. [Figure 7] Examples of single TBoMS transmission opportunities when the gap is below a threshold, according to various embodiments, are shown. [Figure 8] Examples of multiple TBoMS transmission opportunities when the gap is greater than the threshold, according to various embodiments, are shown. [Figure 9] A schematic diagram of wireless networks in various embodiments is provided. [Figure 10] The components of a wireless network in various embodiments are schematically shown. [Figure 11] This block diagram shows components according to several exemplary embodiments that can read instructions from a machine-readable medium or computer-readable medium (e.g., a non-temporary machine-readable storage medium) and perform any one or more of the methods described herein. [Figure 12]This figure illustrates an example of the procedure for carrying out the various embodiments discussed herein. [Figure 13] This figure illustrates an example of the procedure for carrying out the various embodiments discussed herein. [Figure 14] This figure illustrates an example of the procedure for carrying out the various embodiments discussed herein. [Modes for carrying out the invention]

[0005] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, certain details such as specific structures, architectures, interfaces, and techniques are described for illustrative purposes, not limitation, to provide a full understanding of the various aspects of the various embodiments. However, it will be apparent to those skilled in the art who benefit from this disclosure that various aspects of the various embodiments may be carried out in other examples that deviate from these specific details. In some examples, descriptions of well-known devices, circuits, and methods are omitted so as not to overshadow the description of the various embodiments with unnecessary details. For the purposes of this paper, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).

[0006] 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 at relatively high carrier frequencies within Frequency Range 1 (FR1), for example, 3.5 GHz. In this case, coverage loss is expected due to greater path loss, which makes it more difficult to maintain adequate quality of service. Typically, uplink coverage is a bottleneck for system operation, given the low transmit power on the user equipment (UE) side.

[0007] For NR, dynamic grant and configured grant-based Physical Uplink Shared Channel (PUSCH) transmissions are supported. For dynamic grant PUSCH transmission, the PUSCH is scheduled by DCI format 0_0, 0_1, or 0_2. Further, two types of configured grant PUSCH transmissions are specified. Specifically, for type 1 configured grant PUSCH transmission, the uplink (UL) data transmission is based only on Radio Resource Control (RRC) (re)configuration without layer 1 (L1) signaling. Specifically, for one UE, semi-static resources including time and frequency resources, modulation and coding schemes, reference signals, etc. can be configured. For type 2 configured grant PUSCH transmission, the UL data transmission is based on both RRC configuration and L1 signaling to activate / deactivate the UL data transmission, which is similar to semi-persistent (SPS) uplink transmission as defined in LTE.

[0008] In NR Rel-15, several repetitions can be configured for PUSCH transmission to help improve the coverage performance. When repetitions are employed for PUCCH and PUSCH transmissions, the same time domain resource allocation (TDRA) is used in each slot. Further, inter-slot frequency hopping can be configured to improve the performance by leveraging frequency diversity. In Rel-16, the number of repetitions for PUSCH can be dynamically indicated in DCI.

[0009] Furthermore, in NR, the transport block (TB) carried by PUSCH is scheduled within a slot, or the resource allocation for one data transmission is confined within a slot. In this case, the transport block size (TBS) is determined based on the number of resource elements (REs) within the slot. To maintain a low coding rate, the transport block may span across two or more slots, where fewer physical resource blocks (PRBs) may be allocated in frequency to improve the link budget for PUSCH transmission. To support the transmission of transport block processing over multiple slots (TBoMS), certain design improvements may need to be considered.

[0010] In particular, embodiments of the present disclosure are directed towards improvements for transport block processing over multiple slots for the physical uplink shared channel (PUSCH). More specifically, some embodiments disclosed herein are directed towards the following: · Indication of time-domain resource allocation for TBoMS · DMRS pattern for TBoMS transmission · Mechanism for handling overlap between TBoMS and other physical signals / channels · Overhead configuration for TBS determination for TBoMS

[0011] Instructions for time-domain resource allocation for TBoMS As described above, the transport block (TB) carried by PUSCH is scheduled within a slot, or the resource allocation for one data transmission is restricted within a slot. In this case, the transport block size (TBS) is determined based on the number of resource elements (REs) within the slot. To maintain a low coding rate, the transport block may span across two or more slots, where fewer physical resource blocks (PRBs) may be allocated in frequency to improve the link budget for PUSCH transmission. To support the transmission of transport block processing over multiple slots (TBoMS), certain design improvements may need to be considered.

[0012] Note that for the Type A-based mechanism for TBoMS's TDRA, the same time-domain resource allocation is allocated for TBoMS in each slot. For the Type B-based mechanism for TBoMS's TDRA, consecutive symbols are allocated for TBoMS. Figures 1 and 2 show examples of Type A and Type B-based mechanisms for TBoMS's TDRA, respectively.

[0013] An embodiment of instructions for time-domain resource allocation for TBoMS is provided as follows:

[0014] In some embodiments, both Type A and Type B based mechanisms may be supported for the Time-Domain Resource Allocation (TDRA) of the TBoMS. Whether a Type A or Type B based mechanism is used for the TBoMS may be dynamically indicated in the lower layer via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI), or dedicated radio resource control (RRC) signaling, or in the downlink control information (DCI), or a combination thereof.

[0015] For a type A - based TDRA for TBoMS, the start and length in the start and length indicator value (SLIV) for each slot, as well as the number of slots for TBoMS, can be configured as part of the TDRA parameters. On the other hand, for a type B - based TDRA for TBoMS, note that a long SLIV that may span two or more slots can be configured as part of the TDRA for TBoMS. In this case, the length of TBoMS can be greater than 14 symbols for normal CP (NCP) and greater than 12 symbols for extended CP (ECP).

[0016] In addition, the maximum number of slots K can be configured for TBoMS transmission, and K 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 for the maximum number of slots. The start symbol S of TBoMS is defined with respect to the start symbol of the slot and for the NCP of the first slot to which TBoMS is mapped, N symb slot = 14 symbols (for ECP, N symb slot = 12 symbols) can be within it.

[0017] Next, consider the allocated TBoMS duration L. Here, L min ≦L≦K*N symb slot and L min is the minimum number of symbols for an allocatable TBoMS. In one example, L min =N symb slot In another example, at least for a type A - based mechanism for the TDRA of TBoMS, L min =N symb slot while for a type B mechanism for the TDRA of TBoMS, L min is N symbslot It can be less than.

[0018] For such an assignment, in one embodiment, the TDRA for the TBoMS may be shown according to the currently designated SLIV mechanism for the TDRA. That is, the starting symbol S for the start of a slot, and the number L of consecutive symbols counted from the symbol S allocated for the PUSCH, are determined from the indexed row start and length indicator SLIV.

number

[0019] In one example of this embodiment, the above SLIV mechanism applies only to a type B-based mechanism for TDRA for TBoMS. For a type A-based mechanism for TDRA for TBoMS, a single-slot SLIV determination is reused to indicate the allocation within each slot, and the number of slots to which TBoMS is mapped is also provided to the UE.

[0020] In one example, as shown in Figure 2, the starting symbol is symbol #2 in the first slot, and the length of the assigned TBoMS transmission is 45.

[0021] The above TDRA determination mechanism results in significant signal transmission overhead as K increases. Therefore, in one variation of this embodiment, SLIV can be defined using a minimum of n consecutive symbols in order to compress the necessary signal transmission overhead at the expense of reduced flexibility in the granularity of TDRA.

[0022] In another embodiment, if the UE is configured to support both type A-based and type B-based mechanisms for the TBoMS's TDRA, a subset of the TDRA list may be configured for either type A-based or type B-based TDRA for the TBoMS. When the UE is scheduled using entries from the configured TDRA subset, the UE can implicitly derive whether type A or type B-based mechanism will be used.

[0023] Table 1 shows an example of TDRA list divisions for indicating Type A or Type B based mechanisms. In this example, entries 0 through N0-1 in the TDRA list are for TDRA lists for TBoMS using Type A based mechanisms, and entries N0 through N1-1 are for TDRA lists for TBoMS using Type B based mechanisms. Note that N0 and N1 may be composed of higher layers via MSI, RMSI (SIB1), OSI, or RRC signaling.

[0024] Based on this TDRA list classification, when a UE is scheduled with a TDRA entry in entry 0 to N0-1, the UE can determine that a type A-based mechanism will be used for the TBoMS's TDRA. Similarly, when a UE is scheduled with a TDRA entry in entry N0 to N1-1, the UE can determine that a type B-based mechanism will be used for the TBoMS's TDRA. [Table 1]

[0025] In another embodiment, a one-bit indication may be included in the DCI to indicate whether a type A or type B-based mechanism should be applied for the TBoMS's TDRA. Note that this one-bit indication may be included as part of the TDRA for resource allocation. Alternatively, an existing field in the DCI may be repurposed to indicate whether a type A-based mechanism or a type B-based mechanism should be applied for the TBoMS's TDRA.

[0026] Table 2 shows an example of a Type A or Type B based mechanism specification for the TDRA of TBoMS. [Table 2]

[0027] Alternatively, the instruction to apply either a Type A or Type B-based mechanism for TBoMS TDRA can be configured by the upper layer via MSI, RMSI (SIB1), OSI, or RRC signaling for each DCI format. For example, if a Type A-based mechanism is configured by the upper layer via RRC signaling for DCI format 0_1, then when DCI format 0_1 ​​is used to schedule TBoMS for push transmission, only the Type A-based mechanism will be used for TBoMS TDRA. In another example, if a Type B-based mechanism is configured by the upper layer via RRC signaling for DCI format 0_2, then when DCI format 0_2 is used to schedule TBoMS for push transmission, only the Type B-based mechanism will be used for TBoMS TDRA.

[0028] In yet another embodiment, the TDRA mapping type for TBoMS is implicitly determined by the UE based on the indicated TDRA—if the indicated start symbol and duration combination indicates an allocation contained within a slot, the TDRA for TBoMS is identified as following TDRA mapping type A; on the other hand, if the indicated start symbol and duration combination (via SLIV indication) indicates an allocation that crosses a 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.

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

[0030] For a subset of the TDRA list for single-slot PUSCH, the number of repetitions, K2, SLIV, and mapping type for PUSCH repetitions may be configured in each row of the TDRA table for single-slot PUSCH transmissions. Similarly, if the number of repetitions for a PUSCH is not present or configured, the repetitions are not configured for that row of the TDRA table for single-slot PUSCH transmissions. Furthermore, the number of slots or N=1 for a single TBoMS transmission may be configured in one or more rows of the TDRA table to indicate a single-slot PUSCH transmission with or without repetitions.

[0031] To distinguish between TBoMS and single-slot PUSCH transmissions, one option is to include a 1-bit indication as part of the TDRA information in each row. For example, bit "1" may be used to indicate that a single-slot PUSCH transmission is scheduled, and bit "0" may be used to indicate that a TBoMS transmission is scheduled.

[0032] Alternatively, based on TDRA list partitioning, for example, when a UE is configured or scheduled using an entry in a configured TDRA subset, the UE can implicitly derive whether TBoMS or a single-slot PUSCH transmission will be used.

[0033] Table 3 shows an example of TDRA list divisions to indicate that TBoMS or single-slot PUSCH transmissions are scheduled. In this example, entries 0 through P0-1 in the TDRA list are for TDRA lists for single-slot PUSCH transmissions, and entries P0 through P1-1 are for TDRA lists for TBoMS transmissions. Note that P0 and P1 may be configured by higher layers via MSI, RMSI (SIB1), OSI, or RRC signaling.

[0034] Based on this TDRA list classification, when a UE is scheduled with a TDRA entry in entry 0 to P0-1, the UE can determine that a single-slot PUSCH transmission is scheduled. Similarly, when a UE is scheduled with a TDRA entry in entry P1 to P1-1, the UE can determine that a TBoMS transmission is scheduled. [Table 3]

[0035] In another embodiment, separate TDRA tables may be configured for TBoMS with or without repetition and single-slot PUSCH transmissions, respectively. For the TDRA table configured for TBoMS, the number of slots (N), the number of repetitions (M), k2, SLIV, and mapping type for single TBoMS transmissions may be configured in each row of the TDRA table for TBoMS.

[0036] Furthermore, to allow dynamic switching between TBoMS transmissions with or without repetition and single-slot PUSCH transmissions, the number of slots for a single TBoMS transmission, or N=1, may be configured in one or more rows of the TDRA table to indicate a single-slot PUSCH transmission with or without repetition. Alternatively, the number of slots for a single TBoMS transmission may not need to be configured in one or more rows of the TDRA to indicate a single-slot PUSCH transmission with or without repetition. Note that in the case of N=1, or when this parameter is not configured, the number of repetitions (M) may be reinterpreted and applied to a single-slot PUSCH transmission with repetition.

[0037] In one option, a single bit in the DCI can be used to indicate whether TBoMS or single-slot push transmission is scheduled. Specifically, bit "1" may be used to indicate that a single-slot push transmission is scheduled, and bit "0" may be used to indicate that a TBoMS transmission is scheduled. Furthermore, if this field is not configured in the DCI, single-slot push transmission is scheduled as the default configuration. Note that in the case of TBoMS retransmission, the gNB can switch from TBoMS transmission with or without repetition, depending on the selected row in the TDRA table.

[0038] Another option is to use one or more of several reserved states within existing fields in the DCI to indicate whether a TBoMS or single-slot PUSCH transmission is scheduled.

[0039] Alternatively, a separate RNTI can be used to schedule TBoMS transmissions. In particular, this RNTI can be configured or directed to a UE that is configured for a TBoMS transmission. When a UE receives a PDCCH with a CRC scrambled by the RNTI, this indicates that a TBoMS transmission is scheduled. Furthermore, for TBoMS transmissions, the initialization seed for scrambling sequence generation is defined as a function of the configured / directed RNTI for the TBoMS transmission.

[0040] DMRS pattern for TBoMS transmission Embodiments of demodulation reference signal (DMRS) patterns for TBoMS transmission are provided as follows:

[0041] For Type A-based TDRAs for TBoMS, the DMRS location in each slot is determined according to the DMRS location in the first slot, which is indicated in the scheduling DCI format or configured via a higher layer for a configured grant pusher (Configured Grant Pusher, CG Pusher) according to an existing specification.

[0042] In one embodiment, uniformly distributed DMRS symbols may be employed for TBoMS transmission using a Type B-based TDRA. In particular, the distance between the first symbol of a front-loaded DMRS symbol(s) and the first symbol of an additional symbol(s), and the distance between the additional symbols(s) may be configured by the upper layer via MSI, RMSI (SIB1), OSI, or RRC signaling, or dynamically indicated in DCI, or a combination thereof. Based on the distance between DMRS symbols and the length of the TBoMS transmission, the UE can derive the positions of the additional DMRS symbols.

[0043] Figure 3 shows an example of a DMRS pattern for a Type B-based TDRA for TBoMS. In this example, TBoMS is assigned 45 symbols. The distance between DMRS symbols is 14 symbols. In this case, the DMRS is transmitted with the first symbol of TBoMS and every 14 symbols in the TBoMS transmission.

[0044] In another variation of the above embodiment, the UE may be provided with several DMRS symbols evenly distributed in time over the TBoMS duration, such that the first DMRS position is within the first symbol of the TBoMS. In one example, the TBoMS duration excludes any invalid symbols(s) that the UE may not transmit within the TBoMS transmission duration. In another example, the TBoMS duration includes all valid and invalid symbols within the TBoMS transmission duration.

[0045] In another embodiment, when a type B-based TDRA mechanism is used for TBoMS, a pre-DMRS or a DMRS in the first symbol of the TBoMS transmission is used for the TBoMS transmission in the first slot. For subsequent slots for TBoMS transmissions, the DMRS is placed in the first symbol of that slot.

[0046] Furthermore, for TBoMS transmissions in the first and last slots, the position of additional DMRS symbols is determined based on the dmrs-AdditionalPosition and the number of symbols for the first and last slots for TBoMS transmissions, respectively. For TBoMS transmissions in slots other than the first and last slots, the position of additional DMRS symbols is determined based on the dmrs-AdditionalPosition, assuming a full-slot transmission in that slot.

[0047] Figure 4 shows an example of a DMRS pattern for a Type B-based TDRA for TBoMS. In this example, TBoMS is assigned 45 symbols. In addition, a pre-DMRS is assigned for TBoMS transmissions in each slot. The dmrs-AdditionalPosition is configured with "pos1", which indicates that in the first slot, symbol #11 is assigned for the DMRS symbol, in the second and third slots, symbol #9 is assigned for the DMRS, and in the last slot, symbol #4 is assigned for the DMRS.

[0048] In one embodiment, the presence of an additional DMRS symbol(s) within the slot duration for a TBoMS transmission follows the existing (according to the 3GPP Release 15 / Release 16 specification) higher-layer configuration of the presence of an additional DMRS symbol as part of the DMRS-UplinkConfig. In another embodiment, the presence of an additional DMRS may be configured separately for TBoMS and other PUSCH transmissions. In yet another embodiment, for TBoMS transmissions, an additional DMRS symbol(s) is always present within the slot duration.

[0049] In one embodiment, the maximum length of the "front-loaded" DMRS symbols (the first set of DMRS symbols in each slot of a TBoMS transmission) follows the value of the upper-layer parameter maxLength, as provided in DMRS-UplinkConfig. Alternatively, the maximum length of the "front-loaded" DMRS symbols (the first set of DMRS symbols in each slot of a TBoMS transmission) may be configured separately from the maximum length for other PUSCH transmissions.

[0050] In one embodiment, for a TBoMS transmission, the location of the additional DMRS symbol(s) follows the location for other PUSCH transmissions (for example, as indicated by dmrs-AdditionalPosition in DMRS-UplinkConfig). Alternatively, the location of the additional DMRS symbol(s) for a TBoMS transmission may be configured separately from that for other PUSCH transmissions.

[0051] Handling overlaps between TBoMS and other physical signals / channels Embodiments for handling overlaps between TBoMS and other physical signals / channels are provided as follows:

[0052] In one embodiment, when a Type B-based mechanism for TDRA is configured or directed for a TBoMS transmission, if the allocated temporal resources for the TBoMS conflict with invalid symbols for a PUSCH transmission, the TBoMS is segmented into two or more actual transmissions, each actual transmission containing a contiguous set of all potentially valid symbols for the TBoMS transmission. Note that each TBoMS transmission may span a slot boundary or span two or more slots. The initially indicated or configured length of a TBoMS transmission, expressed in terms of symbol count, is called the nominal duration of the TBoMS. The TB size is determined using at least the directed or configured MCS, frequency domain resource allocation (FDRA), and the nominal duration of the TBoMS. Furthermore, for the Type B-based mechanism for TDRA of TBoMS, the rules for determining which symbols (singular or plural) may be unavailable (invalid) for TBoMS transmission may be determined according to the same rules provided in TS38.214, subsection 6.1.2.1 for determining invalid symbols for PUSCH repeat Type B.

[0053] Furthermore, if the number of valid symbols for an actual TBoMS transmission is one symbol, the UE omits the actual TBoMS transmission. In another embodiment, if the number of valid symbols for an 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 actual TBoMS transmission in terms of the number of symbols. As another example of this embodiment, the value of N is the number of symbols such that, for a given FDRA and TB size, the effective channel coding rate when transmitting over N symbols is not greater than the configured or specified threshold coding rate (by a higher layer). In one example, the configured or specified coding rate threshold is less than 0.95. Furthermore, actual transmissions for TBoMS are omitted according to the conditions set out in section 11.1 of TS38.213[1]. In this case, the UE determines the transport block size (TBS) according to the allocated temporal resources, and it should be noted that the same TBS applies to the actual TBoMS transmission(s).

[0054] It should be noted that the determination of invalid symbols for TBoMS may follow the rules for PUSCH type B transmissions as defined in section 6.1.2.1 of TS38.214[2].

[0055] Figure 5 shows an example of how to handle overlaps between TBoMS and other physical channels / signals in the case of a type B-based mechanism for TDRA of TBoMS. In this example, 48 symbols are allocated to TBoMS. When the allocated TBoMS resources in time collide with semi-static DL symbols and invalid symbols, TBoMS is segmented into two actual transmissions, where each actual transmission may span slot boundaries, as with TBoMS. In this example, the first actual TBoMS transmission spans 14 symbols, while the second actual TBoMS transmission spans 29 symbols.

[0056] In another embodiment, when a Type B-based mechanism for TDRA is configured or directed for TBoMS transmission, if the allocated resources for TBoMS in time conflict with invalid symbols for PUSCH transmission, and the number of consecutive invalid symbols is less than or equal to M symbols, the UE shall continue to transmit the TBoMS without segmentation. More specifically, M can be configured by a higher layer via MSI, RMSI (SIB1), OSI, or RRC signaling, or can be predefined in the standard, or depends on the UE's capability for transmitting the TBoMS. In another example, the value of M may be reported by the UE as part of a UE capability report. Furthermore, if the number of consecutive invalid symbols is greater than M symbols, the TBoMS is segmented into two or more actual transmissions, each actual transmission containing a contiguous set of all potentially valid symbols for the TBoMS transmission.

[0057] Furthermore, the TB size is determined using, at a minimum, the indicated or configured MCS, frequency domain resource allocation (FDRA), and the nominal duration of the TBoMS. Additionally, rate matching or puncturing is performed for TBoMS transmissions when some symbols are not used for TBoMS transmissions, as described above. As an alternative to rate matching or puncturing-based processing of invalid symbols for TBoMS transmissions, TB size determination and mapping of PUSCH symbols to time-frequency resources are performed by excluding invalid symbols for TBoMS transmissions when the gap is no longer than M symbols. In other words, the nominal duration of the TBoMS is determined by excluding gaps caused by invalid symbols within the TBoMS, as long as the gap is no more than M symbols long.

[0058] It should be noted that the rules for determining which symbols (single or multiple) may be unavailable (invalid) for TBoMS transmission may be determined according to the same rules set out in TS38.214, subsection 6.1.2.1 for determining invalid symbols for PUSCH repeat type B.

[0059] Figure 5 shows an example of how to handle overlap between TBoMS and other physical channels / signals in the case of a type B-based mechanism for TDRA of TBoMS. In this example, 48 symbols are assigned to TBoMS. Furthermore, the number of invalid symbols is 3, which is below a predefined threshold, and the UE continues to transmit TBoMS. In addition, the total number of symbols assigned for this TBoMS transmission is 45.

[0060] In another embodiment, a single TBoMS transmission opportunity may span non-contiguous slots or symbols. The number of gaps or consecutive invalid symbols may be determined according to the quasi-static TDD UL / DL configuration, SSB symbols, or the rules for determining which symbols(s) may be unavailable (invalid) for TBoMS transmission may be determined according to the same rules provided in TS38.214, subsection 6.1.2.1 for determining invalid symbols for PUSCH repeat type B.

[0061] Furthermore, if the gap is below a threshold, the UE may assume a single transmission opportunity for the TBoMS, where a single redundant version (RV) is applied for the TBoMS transmission. Furthermore, if the gap is greater than a threshold, the UE may segment the TBoMS transmission into multiple transmission opportunities or iterations, where the same or different RVs may be applied to each TBoMS transmission opportunity.

[0062] The threshold may be configured by the upper layer via Minimum System Information (MSI), Remaining Minimum System Information (RMSI), Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling. This may also depend on UE capability on gaps within TBoMS transmission or TBoMS transmission opportunities.

[0063] Furthermore, if multiple TBoMSs or multiple consecutive invalid symbols are determined, the maximum gap or the maximum number of consecutive invalid symbols can be used to determine the transmission opportunity for a TBoMS.

[0064] Figure 7 shows an example of a single TBoMS transmission opportunity when the gap is below a threshold. In this example, the threshold is assumed to be configured as 2 slots. Based on TDRA and semi-static TDD UL / DL configurations, the gap in the TBoMS is 1 slot. In this case, a single TBoMS transmission opportunity is used, and a single redundant version (RV) is applied for TBoMS transmissions in slots #0 and #2, for example.

[0065] Figure 8 shows an example of multiple transmit opportunities in TBoMS when the gap is greater than the threshold. In this example, it is assumed that the threshold is configured as one slot. Based on TDRA and semi-static TDD UL / DL configurations, there are two slots in the gap within TBoMS. In this case, two transmit opportunities in TBoMS are used; for example, the first transmit opportunity is in slot #1 and the second transmit opportunity is in slot #4.

[0066] Configuration of overhead for TBS determination for TBoMS In NR Rel-15, the number of REs in the PRB for PUSCH transmission is determined as in section 6.1.4.2 of TS38.214[2]. More specifically,

number

[0067] An embodiment of the configuration of overhead for TBS determination for TBoMS is provided as follows:

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

[0069] Table 4 shows an example of the overhead configuration for TBoMS. In this example, N symb,i (i=0,1,2,3) are thresholds for the number of symbols, which may be configured by higher layers via MSI, RMSI (SIB1), OSI, or RRC signaling, or may be predefined in the specification. oh,i PRB (i=0,1,2) is the configured overhead for TBS decision-making regarding TBoMS. symb This is the number of symbols based on TDRA allocated for TBoMS.

[0070] In Table 4, the number of symbols is used to determine the overhead, but it should be noted that the same design principle can be easily extended when the number of slots is used to determine the overhead. [Table 4]

[0071] System and Implementation Figures 9 and 10 show various systems, devices, and components that can implement aspects of the disclosed embodiments.

[0072] Figure 9 shows network 900 according to various embodiments of this disclosure. Network 900 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, exemplary embodiments are not limited in this respect, and the embodiments described may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems.

[0073] Network 900 may include UE 902, which may include any mobile or non-mobile computing device designed to communicate with RAN 904 via an over-the-air connection. UE 902 may be communicatively coupled with RAN 904 by a Uu interface. UE 902 may include, but is not limited to, smartphones, tablet computers, wearable computing devices, desktop computers, laptop computers, automotive infotainment, automotive entertainment devices, instrument clusters, head-up display devices, onboard diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, network appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0074] In some embodiments, the network 900 may include multiple UEs directly coupled to one another via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as PSBCH, PSDCH, PSSCH, PSCCH, and PSFCH.

[0075] In some embodiments, the UE 902 may further communicate with the AP 906 via an over-the-air connection. The AP 906 may manage the WLAN connection, which may offload some / all network traffic from the RAN 904. The connection between the UE 902 and the AP 906 may be compatible with any IEEE 802.11 protocol, and the AP 906 may be a Wireless Fidelity (Wi-Fi®) router. In some embodiments, the UE 902, RAN 904, and AP 906 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve the UE 902 being configured by the RAN 904 to utilize both cellular radio resources and WLAN resources.

[0076] RAN 904 may include one or more access nodes, such as AN 908. AN 908 may terminate the air interface protocol for UE 902 by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 908 can enable data / voice connectivity between CN 920 and UE 902. In some embodiments, AN 908 may be implemented as one or more software entities operating on a discrete device or on a server computer as part of a virtual network which may be called CRAN or virtual baseband unit pool. AN 908 may be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 908 may be a macrocell base station, or a low-power base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0077] In embodiments where RAN 904 includes multiple ANs, they may be coupled to each other via an X2 interface (if RAN 904 is an LTE RAN) or an Xn interface (if RAN 904 is a 5G RAN). In some embodiments, the X2 / Xn interface may be separated into a control / user plane interface, allowing ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0078] Each AN of RAN 904 can manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE 902. UE 902 may be simultaneously connected to multiple cells provided by the same or different ANs of RAN 904. For example, UE 902 and RAN 904 may use carrier aggregation that allows UE 902 to connect to multiple component carriers corresponding to Pcells or Scells, respectively. In a dual-connection scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second ANs can be any combination of eNBs, gNBs, ng-eNBs, etc.

[0079] The RAN 904 can provide an air interface through licensed or unlicensed spectra. To operate in unlicensed spectra, nodes may use LAA, eLAA, and / or feLAA mechanisms based on CA technology using PCell / SCell. Prior to accessing unlicensed spectra, nodes may perform medium / carrier sensing operations based, for example, on a listen-before-talk (LBT) protocol.

[0080] In a V2X scenario, UE 902 or AN 908 can be or can function as an RSU, referring to any transport infrastructure entity used for V2X communication. An RSU may be implemented in or by a suitable AN or stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be called a “UE-type RSU,” an “eNB-type RSU” in the case of an eNB, a “gNB-type RSU” in the case of a gNB, and so on. In one example, an RSU is a computing device coupled to a radio frequency circuit located on the roadside, providing connectivity support to a passing vehicle UE. An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling oncoming vehicle and pedestrian traffic. An RSU can provide very low-latency communication required for high-speed events such as collision avoidance and traffic warnings. Additionally or alternatively, an RSU may provide other cellular / WLAN communication services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing wired connectivity (e.g., Ethernet®) to a traffic signal controller or backhaul network.

[0081] In some embodiments, RAN 904 may be an LTE RAN 910 having an eNB, for example, eNB 912. LTE RAN 940 can provide an LTE air interface having the following characteristics: 15kHz SCS; CP-OFDM waveforms for DL ​​and SC-FDMA waveforms for UL; turbo coding 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; CRS for cell discovery and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection at UE. The LTE air interface may operate in the sub-6GHz band.

[0082] In some embodiments, the RAN 904 may be an NG-RAN 914 having a gNB, for example, a gNB 916, or an ng-eNB, for example, an ng-eNB 918. The gNB 916 can connect to a 5G-enabled UE using a 5G NR interface. The gNB 916 can connect to the 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 918 can also connect to the 5G core through an NG interface, but can also connect to the UE via an LTE air interface. The gNB 916 and ng-eNB 918 can connect to each other through an Xn interface.

[0083] In some embodiments, the NG interface may be divided into two parts: an NG user plane (NG-U) interface (e.g., N3 interface) that carries traffic data between the nodes of the NG-RAN 914 and the UPF 948, and an NG control plane (NG-C) interface (e.g., N2 interface) that is a signaling interface between the nodes of the NG-RAN 914 and the AMF 944.

[0084] NG-RAN 914 can provide a 5G-NR air interface having the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetitive, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to an LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and a tracking reference signal for time tracking. The 5G-NR air interface may operate on the FR1 band, including the sub-6 GHz band, or the FR2 band, including the 24.25 GHz to 52.6 GHz band. The 5G-NR air interface may include SSB, which is the area of ​​the downlink resource grid including PSS / SSS / PBCH.

[0085] In some embodiments, a 5G-NR air interface can utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCSs. For instance, UE 902 may consist of multiple BWPs, each with a different SCS. When a BWP change is indicated to UE 902, the SCS of the transmission is also changed. Another example of a use case for BWPs relates to power saving. In particular, multiple BWPs may be configured for UE 902 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. BWPs with fewer PRBs may be used for data transmission with low traffic loads, allowing power saving in UE 902 and possibly in gNB 916. BWPs with more PRBs may be used for scenarios with higher traffic loads.

[0086] RAN 904 is telecommunicatively coupled to CN 920, which includes network elements for providing various functions to customers / subscribers (e.g., users of UE 902) to support data and telecommunications services. The components of CN 920 may be implemented on one physical node or on separate physical nodes. In some embodiments, NFV may be used to virtualize some or all of the functions provided by the network elements of CN 920 on physical computing / storage resources such as servers and switches. Logical instantiations of CN 920 may be referred to as network slices, and some logical instantiations of CN 920 may be referred to as network subslices.

[0087] In some embodiments, CN 920 may be LTE CN 922, sometimes referred to as EPC. LTE CN 922 may include MME 924, SGW 926, SGSN 928, HSS 930, PGW 932, and PCRF 934 coupled to one another through an interface (or “reference point”) as shown. The functions of the elements of LTE CN 922 can be briefly described below.

[0088] The MME 924 can implement mobility management capabilities to track the current location of the UE 902, facilitating paging, bearer activation / deactivation, handover, gateway selection, authentication, and more.

[0089] The SGW 926 terminates the S1 interface toward the RAN and can route data packets between the RAN and the LTE CN 922. The SGW 926 may also be a local mobility anchor point for inter-RAN node handover and may provide an anchor for 3GPP inter-mobility. Other roles may include lawful interception, billing, and some policy enforcement.

[0090] The SGSN 928 can track the location of the UE 902 and perform security functions and access control. Furthermore, the SGSN 928 can perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection specified by the MME 924; MME selection for handover, etc. An S3 reference point between the MME 924 and the SGSN 928 can enable the exchange of user and bearer information for inter-3GPP access network mobility in idle / active states.

[0091] The HSS 930 may include a database of network users, including subscription-related information to support the handling of communication sessions by network entities. The HSS 930 can provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS 930 and the MME 924 may enable the transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN 920.

[0092] PGW 932 may terminate an SGi interface toward a data network (DN) 936, which may include an application / content server 938. PGW 932 may route data packets between the LTE CN 922 and the data network 936. PGW 932 may be coupled with SGW 926 by an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 932 may further include nodes (e.g., PCEF) for policy enforcement and billing data collection. In addition, the SGi reference point between PGW 932 and the data network 936 may be an external public, private PDN, or intra-operator packet data network, for example, for providing IMS services. PGW 932 may be coupled with PCRF 934 via a Gx reference point.

[0093] PCRF 934 is the policy and billing control element of LTE CN 922. PCRF 934 may be telecommunically coupled to the app / content server 938 to determine appropriate QoS and billing parameters for the service flow. PCRF 932 may provision associated rules with appropriate TFT and QCI to the PCEF (via the Gx reference point).

[0094] In some embodiments, CN 920 may be 5GC 940. 5GC 940 may include AUSF 942, AMF 944, SMF 946, UPF 948, NSSF 950, NEF 952, NRF 954, PCF 956, UDM 958, AF 960, and LMF 962 coupled to one another through interfaces (or “reference points”) as shown. The functions of the elements of 5GC 940 can be briefly described below.

[0095] The AUSF 942 may store data for authentication of the UE 902 and handle authentication-related functions. The AUSF 942 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 940 through reference points as illustrated, the AUSF 942 may present a Nausf service-based interface.

[0096] The AMF 944 may allow other functions of the 5GC 940 to communicate with the UE 902 and RAN 904 and subscribe to notifications about mobility events concerning the UE 902. The AMF 944 may be responsible for registration management (e.g., for registering the UE 902), connectivity management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 944 may provide transport for SM messages between the UE 902 and the SMF 946 and act as a transparent proxy for routing SM messages. The AMF 944 may also provide transport for SMS messages between the UE 902 and the SMSF. The AMF 944 can interact with the AUSF 942 and UE 902 to perform various security anchor and context management functions. Furthermore, the AMF 944 may include, or be the N2 reference point between the RAN 904 and the AMF 944, and may also be the termination point of the RAN CP interface, and may also be the termination point of NAS(N1) signaling, enabling NAS encryption and integrity protection. The AMF 944 may also support NAS signaling with the UE 902 via the N3 IWF interface.

[0097] The SMF 946 may be responsible for SM (e.g., session establishment, tunnel management between UPF 948 and AN 908); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of traffic steering in UPF 948 for routing traffic to appropriate destinations; termination of interfaces to policy control functions; control of policy enforcement, billing, and some QoS; lawful interception (of SM events and interfaces to L1 systems); termination of SM portions of NAS messages; downlink data notification; initiation of AN-specific SM information sent to AN 908 on N2 via AMF 944; and determination of the session's SSC mode. SM may refer to the management of PDU sessions, and PDU sessions or “session” may refer to PDU connectivity services that provide or enable the exchange of PDUs between UE 902 and data network 936.

[0098] The UPF 948 can act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 936, and a branch point to support multi-homed PDU sessions. The UPF 948 can also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), perform transport-level packet marking on uplink and downlink, and perform downlink packet buffering and downlink data notification triggers. The UPF 948 may include an uplink classifier to support routing of traffic flows to the data network.

[0099] The NSSF 950 may select a set of network slice instances to serve the UE 902. The NSSF 950 may also determine, if necessary, the acceptable NSSAIs and their mappings to subscribed S-NSSAIs. The NSSF 950 may also determine a set of AMFs, or a list of candidate AMFs, to be used to serve the UE 902, based on a preferred configuration and possibly by querying the NRF 954. The selection of a set of network slice instances for the UE 902 may also be triggered by the AMF 944 to which the UE 902 registers, by interacting with the NSSF 950, which may result in a change of AMF. The NSSF 950 may interact with the AMF 944 via the N22 reference point, or communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, the NSSF 950 may provide an Nnssf service-based interface.

[0100] The NEF 952 can securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g., AF 960), edge computing, or fog computing systems. In such embodiments, the NEF 952 can authenticate, authorize, or throttle AFs. The NEF 952 can also translate information exchanged with AF 960 and information exchanged with internal network functions. For example, the NEF 952 can translate between AF service identifiers and internal 5 GC information. The NEF 952 can also receive information from other NFs based on the exposed capabilities of those NFs. This information may be stored in the NEF 952 as structured data or in a data storage NF using a standardized interface. The stored information can then be re-exposed by the NEF 952 to other NFs and AFs, or used for other purposes such as analysis. Furthermore, the NEF 952 can represent Nnef service-based interfaces.

[0101] The NRF 954 supports service discovery functionality, receiving NF discovery requests from NF instances and providing NF instances with information about discovered NF instances. The NRF 954 also maintains information about available NF instances and their supported services. As used herein, terms such as “instantiate” and “instantiation” may refer to the creation of an instance, while “instance” may refer to the specific occurrence of an object, for example, during the execution of program code. Furthermore, the NRF 954 can represent Nnrf service-based interfaces.

[0102] PCF 956 may provide policy rules to control plane functions that enforce them, and may also support a unified policy framework to govern network behavior. PCF 956 may also implement a front-end for accessing subscription information related to policy decisions within the UDR of UDM 958. In addition to communicating with functions through reference points as illustrated, PCF 956 exhibits an Npcf service-based interface.

[0103] The UDM 958 can process subscription-related information to support the processing of network entities in a communication session and can store subscription data for the UE 902. For example, subscription data may be communicated via an N8 reference point between the UDM 958 and the AMF 944. The UDM 958 can include two parts: an application frontend and a UDR. The UDR can store subscription and policy data for the UDM 958 and PCF 956, and / or structured data for publication and application data for the NEF 952 (including PFD for application discovery and application request information for multiple UE 902s). The Nudr service-based interface is indicated by the UDR 921 to allow the UDM 958, PCF 956, and NEF 952 to access specific sets of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes within the UDR. The UDM may include a UDM-FE responsible for credential processing, location management, subscription management, etc. Several different frontends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through a reference point as shown in the diagram, the UDM 958 may represent a Nudm service-based interface.

[0104] The AF 960 provides application influence on traffic routing, offers access to the NEF, and can interact with the policy framework for policy control.

[0105] In some embodiments, the 5GC 940 may enable edge computing by selecting operator / third-party services to be geographically closer to the point where the UE 902 is attached to the network. This can reduce latency and load on the network. To provide an edge computing implementation, the 5GC 940 may select a UPF 948 close to the UE 902 and perform traffic steering from the UPF 948 to the data network 936 via the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 960. In this way, the AF 960 may influence UPF (re)selection and traffic routing. When the AF 960 is considered a trusted entity based on the operator deployment, the network operator may allow the AF 960 to interact directly with the relevant NF. In addition, the AF 960 may represent a NAF service-based interface.

[0106] The data network 936 may represent various network operator services, internet access, or third-party services that may be provided by one or more servers, including, for example, an application / content server 938.

[0107] Figure 10 schematically illustrates wireless network 1000 in various embodiments. Wireless network 1000 may include UE 1002 wirelessly communicating with AN 1004. UE 1002 and AN 1004 are similar to and substantially interchangeable components of similar names described elsewhere in this specification.

[0108] UE 1002 can be communicatively coupled with AN 1004 via connection 1006. Connection 1006 is shown as an air interface to enable communicative coupling and can be compatible with cellular communication protocols such as LTE or 5G NR protocols operating on mm wave or sub-6GHz frequencies.

[0109] UE 1002 may include a host platform 1008 coupled to a modem platform 1010. The host platform 1008 may include an application processing circuit 1012 that can be coupled to the protocol processing circuit 1014 of the modem platform 1010. The application processing circuit 1012 can run various applications for UE 1002 to source / sink application data. The application processing circuit 1012 may further implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

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

[0111] The modem platform 1010 may further include a digital baseband circuit 1016 that can implement one or more layer operations, which are “lower” layer operations performed by the protocol processing circuit 1014 in the network protocol stack. These operations may include PHY operations, for example, one or more of the following: HARQ-ACK functionality, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port pre-coding / decoding which may include one or more of spatial time, spatial frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronous sequence generation / detection, control channel signal blind decoding, and other related functions.

[0112] The modem platform 1010 may further include a transmitting circuit 1018, a receiving circuit 1020, an RF circuit 1022, and an RF front end (RFFE) 1024, the RFFE of which may include or be connected to one or more antenna panels 1026. Briefly, the transmitting circuit 1018 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receiving circuit 1020 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 1022 may include a low-noise amplifier, a power amplifier, a power tracking component, etc.; the RFFE 1024 may include filters (e.g., surface / volume acoustic wave filters), switches, an antenna tuner, a beamforming component (e.g., a phase array antenna component), etc. The selection and arrangement of the components of the transmitting circuit 1018, receiving circuit 1020, RF circuit 1022, RFFE 1024, and antenna panel 1026 (collectively referred to as “transmitting and receiving components”) may be specific to particular implementation details, such as whether the communication is TDM or FDM at millimeter-wave or sub-6 GHz frequencies. In some embodiments, the transmitting and receiving components may be arranged in multiple parallel transmit and receive chains, or they may be located on the same or different chips / modules, and so on.

[0113] In some embodiments, the protocol processing circuit 1014 may include one or more instances of a control circuit (not shown) that provides control functions for the transmit / receive components.

[0114] UE reception may be established by and through the antenna panel 1026, RFFE 1024, RF circuit 1022, receiving circuit 1020, digital baseband circuit 1016, and protocol processing circuit 1014. In some embodiments, the antenna panel 1026 can receive transmissions from AN 1004 by receiving beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 1026.

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

[0116] Similar to UE 1002, AN 1004 may include a host platform 1028 coupled to a modem platform 1030. The host platform 1028 may include an application processing circuit 1032 coupled to the protocol processing circuit 1034 of the modem platform 1030. The modem platform may further include a digital baseband circuit 1036, a transmit circuit 1038, a receive circuit 1040, an RF circuit 1042, an RFFE circuit 1044, and an antenna panel 1046. The components of AN 1004 are similar to the components of UE 1002 with similar names and may be substantially interchangeable. In addition to performing data transmission / reception as described above, the components of AN 1008 can perform a variety of logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0117] Figure 11 is a block diagram showing components of several exemplary embodiments capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-temporary machine-readable storage medium) and executing any one or more of the methods described herein. Specifically, Figure 11 shows a schematic diagram of hardware resources including one or more processors (or processor cores) 1110, one or more memory / storage devices 1120, and one or more communication resources 1130, each of which may be communicatively coupled via a bus 1140 or other interface circuitry. In embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1102 may be executed to provide an execution environment in which one or more network slices / subslice utilize the hardware resources 1100.

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

[0119] The memory / storage device 1120 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1120 may also 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, or solid-state storage.

[0120] The communication resource 1130 may include interconnects or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 1104 or one or more databases 1106 or other network elements via the network 1108. For example, the communication resource 1130 may include wired communication components (for coupling via USB, Ethernet®, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

[0121] Instruction 1150 may include other executable code causing at least one of the following to perform one or more of the methods described herein: software, programs, applications, applets, apps, or processor 1110. Instruction 1150 may reside entirely or partially in at least one of the following: processor 1110 (e.g., in the processor's cache memory), memory / storage device 1120, or any preferred combination thereof. Furthermore, any portion of instruction 1150 may be transferred to hardware resources from any combination of peripheral device 1104 or database 1106. Thus, the memory of processor 1110, memory / storage device 1120, peripheral device 1104, and database 1106 are examples of computer-readable and machine-readable media.

[0122] In one or more embodiments, at least one of the components shown in one or more of the aforementioned figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the following exemplary section. For example, the baseband circuit described above in relation to one or more of the aforementioned figures may be configured to operate according to one or more of the examples described below. In another example, the circuit related to the UE, base station, network element, etc., described above in relation to one or more of the aforementioned figures may be configured to operate according to one or more of the examples described in the following exemplary section.

[0123] Exemplary procedure In some embodiments, electronic devices(s), networks(s), systems(s), chips(s) or components(s), or parts or implementations thereof, shown in Figures 9-11 or some other figures herein may be configured to perform one or more processes, techniques, or methods, or parts thereof, as described herein. One such process is shown in Figure 12. For example, process 1200 may include, in 1205, retrieving configuration information from memory, including a shared time-domain resource allocation (TDRA) list related to transport block (TBoMS) processing on multiple slots, wherein the TDRA list includes entries having indications of a scheduling delay (k2) and the number of slots (N) for TBoMS transmission. The process further includes, in 1210, encoding a message for transmission to a user device (UE) containing the configuration information.

[0124] Another such process is shown in Figure 13. In this example, process 1300 includes determining configuration information in 1305, which includes a shared time-domain resource allocation (TDRA) list related to transport block (TBoMS) processing on multiple slots, where the TDRA list includes entries having indications of a scheduling delay (k2) and the number of slots (N) for TBoMS transmission. The process further includes encoding a message containing the configuration information for transmission to a user equipment (UE) in 1310.

[0125] Another such process is shown in Figure 14. In this example, process 1400 includes receiving a message from a next-generation NodeB (gNB) in 1405 that includes configuration information, which includes a shared time-domain resource allocation (TDRA) list related to transport block (TBoMS) processing on multiple slots, the TDRA list including entries that have indications of a scheduling delay (k2) and the number of slots (N) for TBoMS transmission. The process further includes encoding a TBoMS message for transmission based on the configuration information in 1410.

[0126] In one or more embodiments, at least one of the components shown in one or more of the aforementioned figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the following Examples section. For example, the baseband circuit described above in relation to one or more of the aforementioned figures may be configured to operate according to one or more of the examples described below. In another example, a circuit related to the UE, base station, network element, etc., described above in relation to one or more of the aforementioned figures may be configured to operate according to one or more of the examples described in the following Examples section.

[0127] Examples Example 1 may include a method for wireless communication for a fifth-generation (5G) or nu-radio (NR) system, the method being: To indicate whether the next-generation node B (gNB) uses a repeating type A-based mechanism or a repeating type B-based mechanism for transport blocks (TBs) (TBoMS) on multiple slots on a physical uplink shared channel (PUSCH); This includes the user equipment (UE) transmitting the TBoMS on the PUSCH in accordance with the instructions. Example 2 may include the methods of Example 1 or some other examples herein, and the indication for whether a repeating type A-based mechanism or a repeating type B-based mechanism is used for the TBoMS may be provided by the upper layer via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI), or dedicated radio resource control (RRC) signaling, or may be dynamically indicated in downlink control information (DCI), or a combination thereof. Example 3 may include the method of Example 1 or some other example herein, where the TDRA for TBoMS can be shown according to the currently specified SLIV mechanism for TDRA, where the starting symbol S for the start of a slot and the number L of consecutive symbols counted from the symbol S allocated for PUSCH are determined from the indexed row start and length indicator SLIV. Example 4 may include the methods of Example 1 or some other examples herein, and if the UE is configured to support both type A and type B based mechanisms for TDRAs of the TBoMS, a subset of the TDRA list may be configured for either type A or type B based TDRAs for the TBoMS. Example 5 may include the methods of Example 1 or some other examples herein, and when the UE is scheduled using entries in a configured TDRA subset, the UE can implicitly derive whether a Type A or Type B based mechanism is used. Example 6 may include the method of Example 1 or some other example herein, and a 1-bit indication may be included in the DCI to indicate whether a type A or type B based mechanism should be applied for the TDRA of the TBoMS. Example 7 may include the methods of Example 1 or some other examples herein, and may be adapted to show whether an existing field in DCI should be applied to a repeating type A or repeating type B based mechanism for the TDRA of TBoMS. Example 8 may include the methods of Example 1 or some other examples herein, and instructions on whether to apply a Type A or Type B based mechanism for the TDRA of the TBoMS may be made by the upper layer via MSI, RMSI (SIB1), OSI, or RRC signaling, depending on the DCI format. Example 9 may include the method of Example 1 or some other example herein, where the TDRA mapping type for TBoMS is implicitly determined by the UE based on the indicated TDRA. Example 10 may include the methods of Example 1 or some other examples herein, in which uniformly distributed DMRS symbols can be employed for TBoMS transmission using a Type B-based TDRA, and the distance between the first symbol of the pre-DMRS symbol(s) and the additional symbols(s), as well as the distance between the additional symbols(s), can be configured by the upper layer via MSI, RMSI (SIB1), OSI, or RRC signaling, or dynamically indicated in DCI, or a combination thereof. Example 11 may include the methods of Example 1 or some other examples herein, and the UE may provide several DMRS symbols that are evenly distributed in time over the duration of the TBoMS, such that the first DMRS position is within the first symbol of the TBoMS. Example 12 may include the methods of Example 1 or some other examples herein, where a Type B-based TDRA mechanism is used for TBoMS, with a pre-determined DMRS or a DMRS in the first symbol of the TBoMS transmission being used for the first slot, and with a subsequent slot for TBoMS transmission, the DMRS is located in the first symbol of the slot. Example 13 may include the methods of Example 1 or some other examples herein, where, when a type B-based mechanism for TDRA is configured or directed for a TBoMS transmission, if the allocated resources for the TBoMS in time conflict with invalid symbols for a PUSCH transmission, the TBoMS is segmented into two or more actual transmissions, each actual transmission containing a contiguous set of all potentially valid symbols for the TBoMS transmission. Example 14 may include the methods of Example 1 or some other examples herein, wherein the TB size is determined using at least the indicated or configured MCS, frequency domain resource allocation (FDRA), and nominal duration of the TBoMS. Example 15 may include the method of Example 1 or some other example herein, where the number of valid symbols for the actual transmission for TBoMS is less than N symbols, and the value of N is specified (e.g., one of 2, 3, or 4) or configured via a higher layer, the UE omits the actual TBoMS transmission for that number of symbols. Example 16 may include the methods of Example 1 or some other examples herein, where, when a Type B-based mechanism for TDRA is configured or directed for TBoMS transmission, if the allocated resources for TBoMS in time collide with invalid symbols for PUSCH transmission, and the number of consecutive invalid symbols is less than or equal to M symbols, the UE shall continue to transmit TBoMS without segmentation. Example 17 may include the methods of Example 1 or some other examples herein, where M may be configured by a higher layer via MSI, RMSI (SIB1), OSI, or RRC signaling, or may be predefined in the specification, or depend on the UE's capabilities in TBoMS transmission. Example 18 may include the method of Example 1 or some other example herein, where if the number of consecutive invalid symbols is greater than M symbols, the TBoMS is segmented into multiple actual transmissions, each actual transmission containing a consecutive set of all potentially valid symbols for the TBoMS transmission. Example 19 may include the methods of Example 1 or some other examples herein, in which rate matching or puncturing is performed for TBoMS transmission when some symbols are not used for TBoMS transmission in the intermediate stage, as described above. Example 20 may include the method of Example 1 or some other example herein, wherein the nominal duration of the TBoMS is determined by excluding gaps caused by invalid symbols in the TBoMS, as long as the gap is less than or equal to M symbols in length. Example 21 may include the methods of Example 1 or some other examples herein, in which multiple overhead values ​​may be configured by the upper layer via MSI, RMSI (SIB1), OSI, or RRC signaling, each overhead value being associated with a range of symbols or slots. Example 22 includes the method of Example 1 or some other example herein, wherein the UE first determines the number of symbols or slots based on the allocated resources in time, and then determines the overhead for TBS determination accordingly. Example 23 may include the methods of Example 1 or some other examples herein, where if the gap is less than or equal to a threshold, the UE may assume a single transmission opportunity for the TBoMS, and a single redundant version (RV) is applied for the TBoMS transmission; where the gap is greater than a threshold, the UE may segment the TBoMS transmission into multiple transmission opportunities or iterations, and the same or different RVs may be applied for each transmission opportunity of the TBoMS. Example 24 may include the method of Example 1 or some other example herein, wherein the threshold may be configured by a higher layer via Minimum System Information (MSI), Remaining Minimum System Information (RMS SI), Other System Information (OSI), or Dedicated Radio Resource Control (RRC) signaling. Example 25 may include the methods of Example 1 or some other examples, wherein the shared TDRA table can be configured for both TBoMS and single-slot PUSCH transmissions, with or without repetitions, and for a subset of the TDRA list for TBoMS, the number of slots (N), number of repetitions (M), k2, SLIV, and mapping type for single TBoMS transmissions are configured in each row of the TDRA table for TBoMS. Example 26 may include methods from Example 1 or some other examples herein, and based on TDRA list partitioning, for example, when a UE is configured or scheduled using entries in a configured TDRA subset, the UE can implicitly derive whether TBoMS or single-slot PUSCH transmission is used. Example 27 may include the method of Example 1 or some other example herein, and the 1-bit instruction may be included as part of the TDRA information in each line. Example 28 may include the methods of Example 1 or some other examples herein, in which separate TDRA tables may be configured for TBoMS and single-slot PUSCH transmissions, with or without repetition, respectively. Example 29 may include the methods of Example 1 or some other examples herein, where the number of slots or N=1 for a single TBoMS transmission may be configured in one or more rows of the TDRA table to represent a single-slot PUSCH transmission with or without repetition. Example 30 is: The next-generation NodeB (gNB) includes a step in determining configuration information, including instructions on whether the user equipment (UE) will use an iterative type A or iterative type B-based mechanism for transport blocks (TBoMS) on multiple slots on a physical uplink shared channel (PUSCH); The step includes encoding a message for transmission to the UE, which includes the aforementioned configuration information. Includes methods. Example 31 comprises the method of Example 30 or some other example herein, wherein the message is a minimum system information (MSI) message, a remaining minimum system information (RMSI) message, an other system information (OSI) message, a radio resource control (RRC) message, or a downlink control information (DCI) message. Example 32 comprises a method of Example 30 or several other examples herein, wherein the configuration information further includes instructions for Time Domain Resource Allocation (TDRA) for TBoMS. Example 33 comprises the method of Example 30 or some other example herein, wherein the TBoMS spans non-continuous slots or symbols. Example 34 includes the method of Example 33 or several other examples herein, wherein the number of gaps or consecutive invalid symbols is determined based on a quasi-static time-division duplex (TDD) uplink (UL) or downlink (DL) configuration. Example 35 comprises the method of Example 34 or some other example herein, wherein the gap is below a threshold associated with a single transmission opportunity for TBoMS. Example 36 comprises the method of Example 35 or some other example herein, wherein the threshold is two slots. Example 37 includes a method of Example 30 or some other example herein, wherein determining the configuration information includes determining a time-domain resource allocation (TDRA) table configured for TBoMS or single-slot PUSCH transmissions with or without repetition. Example 38 includes a method of Example 37 or some other example herein, wherein the TDRA table includes, for a subset of the TDRA list for TBoMS, an indication of the number of slots (N), the number of iterations (M), k2, SLIV, and mapping type for a single TBoMS transmission. Example 39 includes a method from Example 38 or several other examples herein, wherein the TDRA table shows when the UE is configured or scheduled using entries in the configured TDRA subset and indicates to the UE whether TBoMS or single-slot PUSCH transmission is used. Example 40 may include the method of Example 38 or some other example herein, wherein the 1-bit instruction is included as part of the TDRA information in the TDRA table. Example 41 may include the methods of Example 30 or some other examples herein, wherein determining the configuration information includes determining separate TDRA tables configured for TBoMS with or without repetition and single-slot PUSCH transmissions, respectively. Example 42 may include the method of Example 30 or some other example herein, where the number of slots or N=1 for a single TBoMS transmission is shown in the TDRA table to indicate a single-slot PUSCH transmission with or without repetition.

[0128] Example X1 is: Memory that stores configuration information including a shared time-domain resource allocation (TDRA) list related to transport block (TBoMS) processing on multiple slots; A device having a processing circuit coupled to the memory, wherein the processing circuit is: A step of retrieving the configuration information from the memory, wherein the TDRA list includes an entry having an indication of the scheduling delay (k2) and the number of slots (N) for TBoMS transmission; This involves the step of encoding a message for transmission to the user equipment (UE), including the aforementioned configuration information. Device. Example X2 comprises the apparatus of Example X1 or some other example herein, wherein the entry further includes an instruction for the number (M) of repetitions for the TBoMS transmission. Example X3 comprises the apparatus of Example X2 or some other example herein, wherein N=1 in the entry indicating M is reinterpreted and applied by the UE for single-slot physical uplink shared channel (PUSCH) transmission. Example X4 includes the apparatus of Example X3 or some other example herein, and the entry further includes instructions that M is reinterpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission with repetition. Example X5 includes the apparatus of any of Examples X1 to X4, wherein the entry in the TDRA list includes an instruction for the start and length indicator value (SLIV) for the TBoMS transmission, or an instruction for the mapping type for the TBoMS transmission. Example X6 includes one or more computer-readable media storing instructions, which, when executed by one or more processors, are sent to a next-generation NodeB (gNB): A step of determining configuration information including a shared time-domain resource allocation (TDRA) list related to transport block (TBoMS) processing on multiple slots, wherein the TDRA list includes entries having indications of a scheduling delay (k2) and the number of slots (N) for TBoMS transmission; This involves the process of encoding a message, including the aforementioned configuration information, for transmission to the user equipment (UE). Example X7 comprises one or more computer-readable media of Example X6 or some other examples herein, wherein the entry further comprises an instruction for the number of repetitions (M) for the TBoMS transmission. Example X8 includes one or more computer-readable media of Example X7 or some other examples herein, wherein N=1 in the entry indicating M is reinterpreted and applied by the UE for single-slot physical uplink shared channel (PUSCH) transmission. Example X9 includes one or more computer-readable media of Example X8 or some other examples herein, the entry further includes instructions that M is reinterpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission with repetition. Example X10 comprises one or more computer-readable media from Examples X6-X9 or some other examples herein, wherein the entry in the TDRA list comprises an instruction for a start and length indicator value (SLIV) for the TBoMS transmission, or an instruction for a mapping type for the TBoMS transmission. Embodiment X11 includes one or more computer-readable media for storing instructions, and when the instructions are executed by one or more processors, they are sent to the user equipment (UE): A step of receiving a message from a next-generation node B (gNB) containing configuration information including a shared time-domain resource allocation (TDRA) list related to transport block (TBoMS) processing on multiple slots, wherein the TDRA list includes entries having indications of a scheduling delay (k2) and the number of slots (N) for TBoMS transmission; This involves executing the step of encoding a TBoMS message for transmission based on the aforementioned configuration information. Example X12 comprises one or more computer-readable media of Example X11 or some other examples herein, wherein the entry further comprises an instruction for the number of iterations (M) for the TBoMS transmission. Example X13 includes one or more computer-readable media of Example X12 or some other examples herein, wherein N=1 in the entry indicating M is reinterpreted and applied by the UE for single-slot physical uplink shared channel (PUSCH) transmission. Example X14 includes one or more computer-readable media of Example X13 or some other examples herein, the entry further includes instructions that M is reinterpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission with repetition. Example X15 comprises one or more computer-readable media from Examples X11-X14 or some other examples herein, wherein the entries in the TDRA list include instructions for start and length indicator values ​​(SLIV) for the TBoMS transmission, or instructions for the mapping type for the TBoMS transmission.

[0129] Example Z01 may include an apparatus equipped with means for performing one or more elements of any method or process described in or related to any of Examples 1 to X15, or any other method or process described herein. Example Z02 may include one or more non-temporary computer-readable media containing instructions, which, when executed by one or more processors of the electronic device, cause the electronic device to perform one or more elements of the methods described in or related to any of Examples 1 to X15, or any other methods or processes described herein. Example Z03 may include an apparatus comprising logic, modules, or circuits for performing one or more elements of any method described in or related to any of Examples 1 to X15, or any other method or process described herein. Example Z04 may include methods, techniques, or processes described or related to Examples 1 to X15, or any part or portion thereof. Example Z05 may include a device having one or more processors and one or more computer-readable media containing instructions. When executed by the one or more processors, the instructions cause the one or more processors to perform a method, technique, or process described in or related to any of Examples 1 to X15, or any part thereof. Example Z06 may include signals described or related to Examples 1 to X15 or any part or portion thereof. Example Z07 may include datagrams, packets, frames, segments, protocol data units (PDUs), or messages as described in or related to Examples 1 to X15 or any part or portion thereof, or as otherwise described in this disclosure. Example Z08 may include data-encoded signals as described in or related to Examples 1 to X15 or any part or portion thereof, or as otherwise described in this disclosure. Example Z09 may include a signal that encodes a datagram, packet, frame, segment, protocol data unit (PDU), or message, as described in or related to Examples 1 to X15 or any part or portion thereof, or otherwise described in this disclosure. Example Z10 may include an electromagnetic signal that carries a computer-readable instruction, and the execution of the computer-readable instruction by one or more processors causes the one or more processors to perform a method, technique, or process described in or related to any of Examples 1 to X15 or any part thereof. Example Z11 may include a computer program containing instructions, and the execution of the program by the processing element causes the processing element to perform a method, technique, or process described in or related to any of Examples 1 to X15 or any part thereof. Example Z12 may include signals in a wireless network as shown and described herein. Example Z13 may include a method of communication in a wireless network as shown and described herein. Example Z14 may include a system for providing wireless communication as shown and described herein. Example Z15 may include a device for providing wireless communication as shown and described herein.

[0130] Any of the above examples can be combined with any other example (or combination of examples) unless expressly otherwise specified. The above descriptions of one or more implementations are illustrative and explanatory, but are not intended to be exhaustive or to limit the scope of embodiments to the exact form disclosed. Modifications and variations are possible in light of the above teachings, or modifications and variations may be obtained from the practice of various embodiments.

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

[0132] 3GPP Third Generation Partnership Project 4G Fourth Generation 5G Fifth Generation 5GC 5G Core network AC Application Client ACK (Acknowledgement) ACID Application Client Identification AF Application Function AM Acknowledged Mode AMBR Aggregate Maximum Bit Rate AMF Access and Mobility Management Function AN Access Network ANR Automatic Neighbor Relation AP (Application Protocol), Antenna Port, Access Point API Application Programming Interface APN (Access Point Name) ARP Allocation and Retention Priority ARQ Automatic Repeat Request Automatic repeat request AS Access Stratum Access Layer ASP Application Service Provider ASN.1 Abstract Syntax Notation One AUSF Authentication Server Function AWGN Additive White Gaussian Noise BAP (Backhaul Adaptation Protocol) BCH Broadcast Channel BER (Bit Error Ratio) BFD Beam Failure Detection BLER Block Error Rate BPSK (Binary Phase Shift Keying) - 2-state phase shift keying BRAS Broadband Remote Access Server BSS Business Support System BS Base Station BSR Buffer Status Report BW Bandwidth BWP Bandwidth Part C-RNTI Cell Radio Network Temporary Identity CA (Carrier Aggregation), Certification Authority CAPEX CAPital EXpenditure Capital Expenditure CBRA Contention-Based Random Access CC Component Carrier, Country Code, Cryptographic Checksum CCA Clear Channel Assessment (Available Channel Assessment) CCE Control Channel Element CCCH Common Control Channel CE Coverage Enhancement CDM (Content Delivery Network) CDMA Code-Division Multiple Access CFRA Contention Free Random Access CG Cell Group CGF Charging Gateway Function CHF Charging Function CI cell characteristics [identification information] CID Cell-ID Cell ID (e.g., positioning method) CIM Common Information Model CIR Carrier-to-Interference Ratio CK Cipher Key CM Connection Management, Conditional Mandatory CMAS Commercial Mobile Alert Service CMD Command CMS Cloud Management System CO Conditional Optional CoMP Coordinated Multi-Point CORESET Control Resource Set Control resource set COTS Commercial Off-The-Shelf CP Control Plane, Cyclic Prefix, Connection Point CPD Connection Point Descriptor CPE Customer Premise Equipment CPICH Common Pilot Channel CQI Channel Quality Indicator CPU (CSI processing unit), Central Processing Unit (CSI processing unit) C / R Command / Response field bit CRAN (Cloud Radio Access Network) CRB Common Resource Block CRC Cyclic Redundancy Check Cyclic Redundancy Check CRI Channel-State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI Cell RNTI CS Circuit Switched CSCF call session control function CSAR Cloud Service Archive CSI Channel-State Information CSI-IM CSI Interference Measurement CSI Interference Measurement CSI-RS CSI Reference Signal CSI reference signal CSI-RSRP CSI reference signal received power CSI reference signal received power CSI-RSRQ CSI reference signal received quality CSI reference signal received quality CSI-SINR CSI signal-to-noise and interference ratio CSMA Carrier Sense Multiple Access CSMA / CA CSMA with collision avoidance CSS Common Search Space, Cell-specific Search Space CTF Charging Trigger Function CTS Clear-to-Send transmission enabled. CWCodeword Codeword CWS Contention Window Size D2D Device-to-Device DC Dual Connectivity, Direct Current DCI Downlink Control Information DF Deployment Flavor DL Downlink DMTF Distributed Management Task Force DPDK Data Plane Development Kit DM-RS, DMRS Demodulation Reference Signal DN Data Network DNN Data Network Name DNAI (Data Network Access Identifier) DRB Data Radio Bearer DRS Discovery Reference Signal DRX Discontinuous Reception DSL (Domain Specific Language), Digital Subscriber Line DSLAM DSL Access Multiplexer DwPTS Downlink Pilot Time Slot E-LAN ​​Ethernet Local Area Network E2E End-to-End ECCA extended clear channel assessment, extended CCA ECCE Enhanced Control Channel Element ED Energy Detection EDGE Enhanced Datarates for GSM Evolution EAS Edge Application Server EASID (Edge Application Server Identification) ECS Edge Configuration Server ECSP (Edge Computing Service Provider) EDN (Edge Data Network) EEC Edge Enabler Client EECID Edge Enabler Client Identification EES Edge Enabler Server EESID: Edge Enabler Server Identification EHE Edge Hosting Environment EGMF Exposure Governance Management Function: Public Governance Table Management Function EGPRS Enhanced GPRS Enhanced GPRS EIR Equipment Identity Register eLAA (enhanced Licensed Assisted Access) EM, Element Manager eMBB Enhanced Mobile Broadband EMS Element Management System eNB evolved NodeB, E-UTRAN NodeB EN-DC E-UTRA-NR Dual Connectivity EPC Evolved Packet Core EPDCCH enhanced PDCCH, enhanced Physical Downlink Control Channel EPRE: Energy per resource element EPS Evolved Packet System EREG (enhanced REG), enhanced resource element groups ETSI (European Telecommunications Standards Institute) ETWS Earthquake and Tsunami Warning System eUICC embedded UICC, embedded Universal Integrated Circuit Card E-UTRA Evolved UTRA Evolved UTRA E-UTRAN Evolved UTRAN EV2X Improved V2X F1AP F1 Application Protocol F1-C F1 Control Plane Interface F1-U F1 User Plane Interface FACCH Fast Associated Control Channel FACCH / F Fast Associated Control Channel / Full rate FACCH / H Fast Associated Control Channel / Half rate FACH (Forward Access Channel) FAUSCH Fast Uplink Signalling Channel FB Functional Block FBI Feedback Information FCC (Federal Communications Commission) FCCH Frequency Correction Channel FDD (Frequency Division Duplex) FDM Frequency Division Multiplexing FDMA Frequency Division Multiple Access FE Front End FEC Forward Error Correction FFS For Further Study FFT Fast Fourier Transformation feLAA (Further Enhanced Licensed Assisted Access) FN Frame Number FPGA Field-Programmable Gate Array FR Frequency Range FQDN: Fully Qualified Domain Name G-RNTI GERAN Radio Network Temporary Identity GERAN (GSM EDGE RAN), GSM EDGE Radio Access Network GGSN Gateway GPRS Support Node GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System) gNB Next Generation NodeB gNB-CU (gNB-centralized unit), Next Generation NodeB Centralized unit gNB-DU (gNB-distributed unit), Next Generation NodeB distributed unit GNSS Global Navigation Satellite System GPRS General Packet Radio Service GPSI Generic Public Subscription Identifer General Public Subscription Identifier GSM Global System for Mobile Communications, Groupe Spécial Mobile GSM Alliance GTP GPRS Tunneling Protocol GTP-U GPRS Tunneling Protocol for User Plane GTS Go To Sleep Signal (Sleep Transition Signal related to WUS) GUMMEI: Globally Unique MME Identifier GUTI: Globally Unique Temporary UE Identity HARQ Hybrid ARQ, Hybrid Automatic Repeat Request HANDO handover HFN HyperFrame Number HHO Hard Handover HLR Home Location Register HN Home Network Home Network HO Handover HPLMN Home Public Land Mobile Network HSDPA (High Speed ​​Downlink Packet Access) HSN Hopping Sequence Number HSPA High Speed ​​Packet Access HSS Home Subscriber Server HSUPA High Speed ​​Uplink Packet Access HTTP (Hypertext Transfer Protocol) HTTPS (Hypertext Transfer Protocol Secure) is a secure hypertext transfer protocol (HTTPS stands for http / 1.1 over SSL, i.e., port 443). I-Block Information Block ICCID (Integrated Circuit Card Identification) IAB Integrated Access and Backhaul ICIC Inter-Cell Interference Coordination ID Identity, Identifier Identification information, Identifier IDFT Inverse Discrete Fourier Transform IE Information Element IBE In-Band Emission IEEE Institute of Electrical and Electronics Engineers IEI Information Element Identifier IEIDL Information Element Identifier Data Length IETF Internet Engineering Task Force IF Infrastructure IM Interference Measurement, Intermodulation, IP Multimedia IMC IMS Credentials IMS Credentials IMEI (International Mobile Equipment Identity) IMGI International mobile group identity IMPI IP Multimedia Private Identity IMPU IP Multimedia Public Identity IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IoT (Internet of Things) IP Internet Protocol IPsec IP Security, Internet Protocol Security IP-CAN IP-Connectivity Access Network IP-M IP Multicast IP Multicast IPv4 Internet Protocol Version 4 IPv6 Internet Protocol Version 6 IR Infrared IS In Sync Syncing IRP Integration Reference Point ISDN Integrated Services Digital Network ISIM IM Services Identity Module ISO International Organization for Standardization ISP (Internet Service Provider) IWF Interworking Function I-WLAN Interworking WLAN Constraint length of the convolutional code, USIM individual key kB Kilobyte (1000 bytes) kbps kilobits per second Kc Ciphering key Encryption key Individual subscriber authentication key KPI Key Performance Indicator KQI Key Quality Indicator KSI Key Set Identifier ksps kilo-symbols per second KVM (Kernel Virtual Machine) L1 Layer 1 (physical layer) L1-RSRP Layer 1 reference signal received power L2 Layer 2 (data link layer) L3 Layer 3 (Network Layer) LAA Licensed Assisted Access LAN (Local Area Network) LADN (Local Area Data Network) LBT Listen Before Talk LCM (Life Cycle Management) LCR Low Chip Rate LCS Location Services LCID: Logical Channel ID LI Layer Indicator LLC Logical Link Control, Low Layer Compatibility LPLMN Local PLMN Local PLMN LPP LTE Positioning Protocol LSB (Least Significant Bit) LTE Long Term Evolution LWA LTE-WLAN aggregation LWIP LTE / WLAN Radio Level Integration with IPsec Tunnel: LTE / WLAN radio level integration via IPsec tunnel. LTE Long Term Evolution M2M Machine-to-Machine MAC Medium Access Control (in the context of protocol layering) MAC Message authentication code (in the context of security / encryption) MAC-A MAC used for authentication and key agreement (in the context of TSG T WG3) MAC-I MAC used for data integrity: MAC used for data integrity in signaling messages (in the context of TSG T WG3) MANO Management and Orchestration MBMS (Multimedia Broadcast and Multicast Service) MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MCC Mobile Country Code MCG Master Cell Group MCOT Maximum Channel Occupancy Time MCS Modulation and coding scheme MDAF Management Data Analytics Function MDAS Management Data Analytics Service Minimization of Drive Tests (MDT) ME Mobile Equipment Mobile Devices MeNB master eNB Master eNB MER Message Error Ratio MGL Measurement Gap Length MGRP Measurement Gap Repetition Period MIB Master Information Block, Management Information Base MIMO Multiple Input Multiple Output MLC Mobile Location Centre MM Mobility Management Mobility Management MME Mobility Management Entity MN Master Node MNO Mobile Network Operator MO: Measurement Object, Mobile Originated. MPBCH MTC Physical Broadcast Channel MPDCCH MTC Physical Downlink Control Channel MPDSCH MTC Physical Downlink Shared Channel MPRACH MTC Physical Random Access Channel MPUSCH MTC Physical Uplink Shared Channel MPLS (MultiProtocol Label Switching) MS Mobile Station Mobile Station MSB Most Significant Bit Most Significant Bit MSC Mobile Switching Centre Mobile Switching Centre MSI Minimum System Information, MCH Scheduling Information Minimum System Information, MCH Scheduling Information MSID Mobile Station Identifier Mobile Station Identifier MSIN Mobile Station Identification Number Mobile Station Identification Number MSISDN Mobile Subscriber ISDN Number Mobile Subscriber ISDN Number MT Mobile Terminated Mobile Terminated, Mobile Termination Mobile Termination MTC Machine-Type Communications Machine-Type Communications mMTC massive MTC, massive Machine-Type Communications massive MTC, massive Machine-Type Communications MU-MIMO Multi User MIMO Multi User MIMO MWUS MTC wake-up signal MTC wake-up signal, MTC WUS MTC WUS NACK Negative Acknowledgement Negative Acknowledgement NAI Network Access Identifier Network Access Identifier[[ID=]} NAS Non-Access Stratum Non-Access Stratum, Non-Access Stratum layer Non-Access Stratum layer NCT Network Connectivity Topology Network Connectivity Topology NC-JT Non-Coherent Joint Transmission NEC Network Capability Exposure: Network Function Disclosure NE-DC NR-E-UTRA Dual Connectivity NEF Network Exposure Function (Network Exposure Function) NF Network Function NFP Network Forwarding Path NFPD Network Forwarding Path Descriptor NFV (Network Functions Virtualization) NFVI NFV Infrastructure NFV Infrastructure NFVO NFV orchestrator NFV orchestrator NG Next Generation Next Generation, Next Gen NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity NM Network Manager NMS Network Management System N-PoP Network Point of Presence NMIB, N-MIB, Narrowband MIB NPBCH (Narrowband Physical Broadcast Channel) NPDCCH Narrowband Physical Downlink Control Channel NPDSCH Narrowband Physical Downlink Shared Channel NPRACH Narrowband Physical Random Access Channel NPUSCH Narrowband Physical Uplink Shared Channel NPSS Narrowband Primary Synchronization Signal NSSS Narrowband Secondary Synchronization Signal NR (New Radio), Neighbor Relation NRF NF Repository Function NRS Narrowband Reference Signal NS Network Service NSA Non-Standalone operation mode NSD (Network Service Descriptor) NSR Network Service Record NSSAI Network Slice Selection Assistance Information S-NNSAI Single-NSSAI Single NSSAI NSSF Network Slice Selection Function NW Network NWUS (Narrowband WUS) NZP Non-Zero Power O&M Operation and Maintenance ODU2 Optical Channel Data Unit - Type 2 OFDM (Orthogonal Frequency Division Multiplexing) OFDMA (Orthogonal Frequency Division Multiple Access) OOB (Out-of-band) OOS (Out of Sync) OPEX: Operating Expenses OSI Other System Information OSS Operations Support System OTA over-the-air PAPR (Peak-to-Average Power Ratio) PAR (Peak to Average Ratio) PBCH (Physical Broadcast Channel) PC Power Control, Personal Computer PCC Primary Component Carrier, Primary CC P-CSCF Proxy CSCF PCell Primary Cell PCI Physical Cell ID, Physical Cell Identity PCEF Policy and Charging Enforcement Function PCF Policy Control Function PCRF Policy Control and Charging Rules Function PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol layer PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDN Packet Data Network, Public Data Network PDSCH Physical Downlink Shared Channel PDU Protocol Data Unit PEI Permanent Equipment Identifiers PFD Packet Flow Description P-GW PDN Gateway PHICH Physical hybrid-ARQ indicator channel PHY Physical layer PLMN Public Land Mobile Network PIN (Personal Identification Number) PM Performance Measurement Performance measurement PMI Precoding Matrix Indicator PNF (Physical Network Function) PNFD (Physical Network Function Descriptor) PNFR (Physical Network Function Record) POC PTT over Cellular PP, PTP: Point-to-Point PPP (Point-to-Point Protocol) PRACH Physical RACH Physical RACH PRB Physical resource block PRG Physical resource block group ProSe (Proximity Services), Proximity-Based Service PRS Positioning Reference Signal PRR Packet Reception Radio PS Packet Services PSBCH Physical Sidelink Broadcast Channel PSDCH Physical Sidelink Downlink Channel PSCCH Physical Sidelink Control Channel PSSCH Physical Sidelink Shared Channel PSCell Primary SCell Primary SCell PSS Primary Synchronization Signal Primary synchronization signal PSTN Public Switched Telephone Network PT-RS Phase-tracking reference signal Phase-tracking reference signal PTT Push-to-Talk PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel QAM (Quadrature Amplitude Modulation) QCI QoS class of identifier QCL Quasi co-location (quasi-co-location) QFI QoS Flow ID, QoS Flow Identifier QoS (Quality of Service) QPSK Quadrature (Quaternary) Phase Shift Keying QZSS Quasi-Zenith Satellite System RA-RNTI (Random Access RNTI) RAB Radio Access Bearer, Random Access Burst RACH Random Access Channel RADIUS Remote Authentication Dial In User Service RAN Radio Access Network RAND: Random number (used for authentication) RAR (Random Access Response) RAT Radio Access Technology RAU Routing Area Update RB Resource block, Radio Bearer RBG Resource block group REG Resource Element Group Rel Release REQ REQuest request RF Radio Frequency RI Rank Indicator RIV Resource indicator value RL Radio Link RLC Radio Link Control, Radio Link Control layer RLC AM RLC Acknowledged Mode RLC UM RLC Unacknowledged Mode RLF Radio Link Failure RLM Radio Link Monitoring RLM-RS Reference Signal for RLM RM Registration Management RMC Reference Measurement Channel RMSI (Remaining MSI), Remaining Minimum System Information RN Relay Node RNC Radio Network Controller RNL (Radio Network Layer) RNTI (Radio Network Temporary Identifier) ROHC Robust Header Compression RRC Radio Resource Control Radio resource control, Radio Resource Control layer Wireless resource control layer RRM Radio Resource Management Radio resource management RS Reference Signal Reference signal RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality RSSI Received Signal Strength Indicator RSU Road Side Unit RSTD Reference Signal Time Difference RTP (Real Time Protocol) RTS Ready-To-Send Ready to send RTT (Round Trip Time) Rx Reception, Receiving Receiver S1AP S1 Application Protocol S1-MME S1 for the control plane S1-U S1 for the user plane S-CSCF serving CSCF serviceCSCF S-GW Serving Gateway S-RNTI SRNC Radio Network Temporary Identity S-TMSI SAE Temporary Mobile Station Identifier SAE Temporary Mobile Station Identifier SA Standalone operation mode SAE System Architecture Evolution SAP Service Access Point SAPD Service Access Point Descriptor SAPI Service Access Point Identifier SCC Secondary Component Carrier, Secondary CC SCell Secondary Cell SCEF Service Capability Exposure Function SC-FDMA (Single Carrier Frequency Division Multiple Access) SCG Secondary Cell Group SCM Security Context Management SCS Subcarrier Spacing SCTP Stream Control Transmission Protocol SDAP (Service Data Adaptation Protocol) - Service Data Adaptation Protocol Layer SDL Supplementary Downlink SDNF (Structured Data Storage Network Function) SDP Session Description Protocol SDSF (Structured Data Storage Function) SDU Service Data Unit SEAF Security Anchor Function SeNB secondary eNB SEPP Security Edge Protection Proxy SFI Slot Format Indication SFTD (Space-Frequency Time Diversity), SFN (Space-Frequency Network) and frame timing difference SFN System Frame Number SgNB Secondary gNB Secondary gNB SGSN Serving GPRS Support Node S-GW Serving Gateway SI System Information SI-RNTI System Table RNTI System Information RNTI SIB System Information Block SIM Subscriber Identity Module SIP Session Initiation Protocol SiP System in Package SL Sidelink SLA (Service Level Agreement) SM Session Management SMF Session Management Function SMS Short Message Service SMSF SMS Function SMTC SSB-based Measurement Timing Configuration SN Secondary Node, Sequence Number SoC (System on Chip) SON Self-Organizing Network SpCell Special Cell SP-CSI-RNTI Semi-Persistent CSI RNTI SPS Semi-Persistent Scheduling SQN Sequence number SR Scheduling Request SRB Signaling Radio Bearer SRS Sounding Reference Signal Detection reference signal SS Synchronization Signal Synchronization signal SSB Synchronization Signal Block SSID (Service Set Identifier) SS / PBCH Block SS / PBCH Block SSBRI SS / PBCH Block Resource Indicator, Syncheronization Signal Block Resource Indicator SSC Session and Service Continuity SS-RSRP Synchronization Signal based Reference Signal Received Power SS-RSRQ Synchronization Signal based Reference Signal Received Quality SS-SINR Synchronization Signal-based Signal-to-Noise and Interference Ratio SSS Secondary Synchronization Signal SSSG Search Space Set Group SSSIF Search Space Set Indicator SST Slice / Service Types SU-MIMO (Single User MIMO) SUL Supplementary Uplink TA Timing Advance, Tracking Area TAC Tracking Area Code TAG Timing Advance Group TAI Tracking Area Identity TAU Tracking Area Update TB Transport Block TBS Transport Block Size TBD To Be Defined TCI Transmission Configuration Indicator TCP Transmission Communication Protocol TDD (Time Division Duplex) TDM Time Division Multiplexing TDMA (Time Division Multiple Access) TE Terminal Equipment TEID: Tunnel End Point Identifier TFT Traffic Flow Template TMSI (Temporary Mobile Subscriber Identity) TNL (Transport Network Layer) TPC Transmit Power Control TPMI Transmitted Precoding Matrix Indicator TR Technical Report Technical Report TRP, TRxP Transmission Reception Point TRS Tracking Reference Signal TRx Transceiver TS Technical Specifications, Technical Standards TTI Transmission Time Interval Tx Transmission, Transmitting, Transmission, Transmitter U-RNTI UTRAN Radio Network Temporary Identity UART Universal Asynchronous Receiver and Transmitter UCI Uplink Control Information UE User Equipment UDM Unified Data Management: Centralized Data Management UDP User Datagram Protocol UDSF (Unstructured Data Storage Network Function) UICC Universal Integrated Circuit Card UL Uplink UM Unacknowledged Mode (No Acknowledgment Response Mode) UML (Unified Modeling Language) UMTS Universal Mobile Telecommunications System UP User Plane UPF User Plane Function URI Uniform Resource Identifier URL Uniform Resource Locator URLLC Ultra-Reliable and Low Latency USB Universal Serial Bus USIM Universal Subscriber Identity Module USS UE-specific search space UTRA UMTS Terrestrial Radio Access UTRAN (Universal Terrestrial Radio Access Network) UwPTS Uplink Pilot Time Slot V2I Vehicle-to-Infrastructure V2P Vehicle-to-Pedestrian V2V Vehicle-to-Vehicle V2X Vehicle-to-everything VIM Virtualized Infrastructure Manager VL Virtual Link, VLAN (Virtual LAN), Virtual Local Area Network VM (Virtual Machine) VNF (Virtualized Network Function) VNF Forwarding Graph VNFFGD VNF Forwarding Graph Descriptor VNFM VNF Manager VNF Manager VoIP (Voice-over-IP, Voice-over-Internet Protocol) VPLMN Visited Public Land Mobile Network VPN (Virtual Private Network) VRB (Virtual Resource Block) WiMAX Worldwide Interoperability for Microwave Access WLAN (Wireless Local Area Network) WMAN Wireless Metropolitan Area Network WPAN Wireless Personal Area Network X2-C X2-Control plane X2-U X2-User plane XML eXtensible Markup Language XRES Expected User Response XOR eXclusive OR exclusive OR ZC Zadoff-Chu ZP Zero Power

[0133] Terminology For the purposes of this specification, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0134] As used herein, the term “circuit” refers to, is part of, or includes hardware components configured to provide the functions described, such as electronic circuits, logic circuits, processors (shared, dedicated, or group) and / or memory (shared, dedicated, or group), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), composite PLDs (CPLDs), high-performance PLDs (HCPLDs), constructed ASICs, or programmable SoCs), and digital signal processors (DSPs). In some embodiments, a circuit may run one or more software or firmware programs to provide at least some of the functionalities described. The term “circuit” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) having program code used to perform the functions of the program code. In these embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuit.

[0135] As used herein, the term “processor circuit” refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. A processing circuit may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term “processor circuit” may also refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single-core processors, dual-core processors, triple-core processors, quad-core processors, and / or any other devices that can execute or otherwise operate computer-executable instructions, such as program code, software modules, and / or functional processes. A processing circuit may include more hardware accelerators, such as microprocessors and programmable processing devices. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuit” and / or “baseband circuit” may be considered synonymous with “processor circuit” and may also be referred to as “processor circuit.”

[0136] As used herein, the term “interface circuit” refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term “interface circuit” may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and / or others.

[0137] As used herein, the terms “User Equipment” or “UE” refer to a device having wireless communication capabilities and may represent a remote user of network resources within a communication network. The terms “User Equipment” or “UE” may be considered synonymous with, and may be referred to as, a client, mobile, 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. Furthermore, the terms “User Equipment” or “UE” may include any computing device including any type of wireless / wired device or wireless communication interface.

[0138] 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, networked computers, networking hardware, network equipment, network nodes, routers, switches, hubs, bridges, wireless network controllers, RAN devices, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, and / or others.

[0139] As used herein, the term “computer system” refers to any type of interconnected electronic devices, computer devices, or components thereof. Furthermore, the terms “computer system” and / or “system” may refer to various components of a computer that are interconnected by communication. Additionally, the terms “computer system” and / or “system” may refer to multiple computer devices and / or multiple computing systems that are interconnected by communication and configured to share computing and / or networking resources.

[0140] As used herein, terms such as “appliance” and “computer appliance” refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide a particular computing resource. A “virtual appliance” is a virtual machine image implemented by a hypervisor-based device that virtualizes or emulates a computer appliance, or is otherwise dedicated in a way to provide a particular computing resource.

[0141] As used herein, the term “resource” refers to physical or virtual devices, physical or virtual components, and / or physical or virtual components within a particular device in a computing environment, including computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operation, ports or network sockets, channel / link allocation, throughput, memory usage, storage, networks, databases and applications, and workload units. “Hardware resources” may refer to computing, storage, and / or network resources provided by a physical hardware element(s). “Virtualized resources” may refer to computing, storage, and / or network resources provided to applications, devices, systems, etc., by a virtualization infrastructure. The term “network resources” or “communication resources” may refer to resources accessible by computer devices / systems over a communication network. The term “system resources” may refer to any kind of shared entity providing services, and may include computing and / or network resources. System resources can be considered as a set of coherent functions, network data objects, or services that reside on a single host or multiple hosts and are accessible via a clearly identifiable server.

[0142] As used herein, the term “channel” refers to any tangible or intangible transmission medium used to communicate data or data streams. The term “channel” may be synonymous and / or equivalent to any other similar term indicating a path or medium through which data is communicated, such as “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. Furthermore, as used herein, the term “link” refers to a connection between two devices via a RAT for the purpose of transmitting and receiving information.

[0143] As used herein, terms such as "instantiate" and "instantiate" refer to the creation of an instance. An "instance" can also refer to the specific occurrence of an object, for example, during the execution of program code.

[0144] The terms “coupled” and “communicationally coupled” are used herein together with their derivatives. The term “coupled” may mean that two or more elements are in direct physical or electrical contact with each other, that two or more elements are indirectly in contact with each other but still cooperate or interact with each other, and / or that one or more other elements are coupled or connected between elements said to be coupled to each other. The term “directly coupled” may mean that two or more elements are in direct contact with each other. The term “communicationally coupled” may mean that two or more elements are in contact with each other by means of communication, such as through wires or other interconnections, through wireless communication channels or links.

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

[0146] The term "SMTC" refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration. The term "SSB" refers to the SS / PBCH block.

[0147] The term "Primary Cell" refers to the MCG cell operating on the primary frequency from which the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure. The term "primary SCG cell" refers to the SCG cell through which the UE performs random access when executing the Reconfiguration with Sync procedure for DC operation. The term "Secondary Cell" refers to a cell that provides additional radio resources on top of a special cell for a UE configured using CA. The term "sub-cell group" refers to a subset of serving cells that includes a PSCell and zero or more sub-cells for a UE composed of DCs. The term "Serving Cell" refers to the primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, and there is only one serving cell that constitutes a primary cell. The term "serving cell" or "multiple serving cells" refers to a set of cells that includes the special cell for the UE in RRC_CONNECTED configured with CA / , and all sub-cells. The term "special cell" refers to MCG's PCell or SCG's PSCell for DC operation; otherwise, the term "special cell" refers to Pcell.

Claims

1. Memory for storing configuration information including a shared time-domain resource allocation (TDRA) list related to transport block (TBoMS) processing on multiple slots; A device having a processing circuit coupled to the memory, wherein the processing circuit is: A step of retrieving the configuration information from the memory, wherein the TDRA list includes an entry having an indication of the scheduling delay (k2) and the number of slots (N) for TBoMS transmission; This process includes the step of encoding a message for transmission to the user equipment (UE), which includes the aforementioned configuration information. The entry in the TDRA list includes an instruction for a start and length indicator value (SLIV) for the TBoMS transmission, or an instruction for a mapping type for the TBoMS transmission.

2. The apparatus according to claim 1, wherein the entry further includes an instruction for the number (M) of repetitions for the TBoMS transmission.

3. The apparatus according to claim 2, wherein N=1 in the entry indicating M is reinterpreted and applied by the UE for single-slot physical uplink shared channel (PUSCH) transmission.

4. The apparatus according to claim 3, further comprising the instruction that the entry M is reinterpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission with repetition.

5. One or more computer-readable media storing instructions, wherein, when executed by one or more processors, the instructions are transmitted to a next-generation NodeB (gNB): A step of determining configuration information including a shared time-domain resource allocation (TDRA) list related to transport block (TBoMS) processing on multiple slots, wherein the TDRA list includes entries having indications of a scheduling delay (k2) and the number of slots (N) for TBoMS transmission; This involves the step of encoding a message for transmission to the user equipment (UE), including the aforementioned configuration information. The entry in the TDRA list includes an instruction for the start and length indicator values ​​(SLIV) for the TBoMS transmission, or an instruction for the mapping type for the TBoMS transmission. One or more computer-readable media.

6. The entry further includes an instruction for the number of repetitions (M) for the TBoMS transmission, one or more computer-readable media according to claim 5.

7. One or more computer-readable media according to claim 6, wherein N=1 in the entry indicating M is reinterpreted and applied by the UE for single-slot physical uplink shared channel (PUSCH) transmission.

8. The computer-readable medium according to claim 7, further comprising instructions that the entry M is reinterpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission with repetition.

9. The system includes one or more computer-readable media storing instructions, and when the instructions are executed by one or more processors, they are sent to the user equipment (UE): Steps include receiving a message from a next-generation node B (gNB) containing configuration information including a shared time-domain resource allocation (TDRA) list related to transport block (TBoMS) processing on multiple slots, wherein the TDRA list includes entries having indications of a scheduling delay (k2) and the number of slots (N) for TBoMS transmission; This involves executing the step of encoding a TBoMS message for transmission based on the aforementioned configuration information. The entry in the TDRA list is one or more computer-readable media containing an instruction for a start and length indicator value (SLIV) for the TBoMS transmission, or an instruction for a mapping type for the TBoMS transmission.

10. The entry further includes an instruction for the number of repetitions (M) for the TBoMS transmission, one or more computer-readable media according to claim 9.

11. One or more computer-readable media according to claim 10, wherein N=1 in the entry indicating M is reinterpreted and applied by the UE for single-slot physical uplink shared channel (PUSCH) transmission.

12. The computer-readable media according to claim 11, further comprising instructions that the entry M is reinterpreted and applied by the UE for a single-slot physical uplink shared channel (PUSCH) transmission with repetition.

Images