Rate matching for processing transport blocks across multiple slots in a physical uplink shared channel.

Abstract

Various embodiments herein provide techniques for uplink transport block transmission across multiple slots, e.g., using bit interleaving and / or rate matching. Other embodiments may be described and claimed.

Description

[Technical Field]

[0001] Cross-reference of related applications This application claims priority to U.S. Provisional Patent Application No. 63 / 250,950, filed on 30 September 2021; U.S. Provisional Patent Application No. 63 / 256,910, filed on 18 October 2021; and U.S. Provisional Patent Application No. 63 / 301,853, filed on 21 January 2022. [Background technology]

[0002] Various embodiments may generally relate to the field of wireless communication. For example, some embodiments may relate to techniques for processing transport blocks across multiple slots.

[0003] Mobile communications have evolved remarkably from early voice systems to today's highly sophisticated integrated communication platforms. The next-generation wireless communication system, 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 conflicting, performance dimensions and services. Such diverse, multi-dimensional requirements will be driven by different services and applications. Generally, NR will evolve based on 3GPP® LTE-Advanced with additional potential new radio access technologies (RATs), enriching people's lives with better, simpler, and more seamless wireless connectivity solutions. NR will enable everything to be connected wirelessly, delivering rich content and services at high speed.

[0004] In cellular systems, coverage is a critical factor for successful operation. Compared to LTE, NR can be deployed at relatively higher carrier frequencies in frequency range 1 (FR1), for example, at 3.5 GHz. In this case, coverage loss due to greater path loss is expected, making 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 UE side. [Brief explanation of the drawing]

[0005] The embodiments will be readily apparent from the following detailed description in conjunction with the accompanying drawings. For the sake of this description, similar components are given the same reference numerals. The embodiments are shown in the figures of the accompanying drawings as examples, not limitations.

[0006] [Figure 1] This document presents examples of Physical Uplink Shared Channels (PUSCH) through Transport Block over Multiple Slot (TBoMS) processing, using various embodiments.

[0007] [Figure 2] Examples of TB processing across multiple slots using slot-by-slot bit interleaving are shown according to various embodiments.

[0008] [Figure 3] Examples of distributions of starting positions using fixed offsets for bit selection, according to various embodiments, are shown.

[0009] [Figure 4] Examples of bit selection start position distributions with fixed offsets in the case of cancellation, according to various embodiments, are shown.

[0010] [Figure 5] Examples of consecutive bit selection for the start position distribution in the case of cancellation are shown using various embodiments.

[0011] [Figure 6] Examples of TB processing across multiple slots with bit interleaving for each entire TBoMS are shown according to various embodiments.

[0012] [Figure 7] Examples of TB processing across multiple slots with bit interleaving for each entire TBoMS are shown according to various embodiments.

[0013] [Figure 8] A schematic representation of wireless networks in various embodiments is provided.

[0014] [Figure 9] The components of a wireless network in various embodiments are schematically shown.

[0015] [Figure 10] This block diagram shows a component capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-temporary machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to several exemplary embodiments.

[0016] [Figure 11] This specification provides exemplary procedures for carrying out the various embodiments discussed herein.

[0017] [Figure 12] Another exemplary procedure for carrying out the various embodiments discussed herein is provided. [Modes for carrying out the invention]

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

[0019] Various embodiments of this specification provide mechanisms for TB processing across multiple slots, including rate matching and / or bit interleaving. For example, embodiments may include: • A rate matching mechanism for TB processing across multiple slots, using a fixed bit selection start position for each slot and continuous bit selection across slots. • Rate matching mechanism for TB processing across multiple slots using bit interleaving, both for each slot assigned to TBoMS transmission and for all slots combined.

[0020] In NR, transport blocks (TBs) carried by PUSCH are scheduled within slots, or the resource allocation for a single data transmission is limited to within slots. 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 code rate, transport blocks may span multiple slots, and fewer Physical Resource Blocks (PRBs) may be allocated to the frequency to improve the link budget for PUSCH transmissions. In this case, the Transport Block Size (TBS) is determined based on the number of slots allocated to TB processing (TBoMS) spanning multiple slots. Following the same design principles as single-slot PUSCH repeating type A, the same time-domain resource allocation is allocated to each slot for TBoMS transmissions.

[0021] Figure 1 shows an example of a push operation using TB processing across multiple slots. In this example, four slots are allocated to TBoMS transmissions, and the same time-domain resource allocation is allocated to each TBoMS transmission slot.

[0022] In NR Rel-15, rate matching is performed for each slot in two steps: bit selection and interleaving. Furthermore, to support the transmission of TB processing across multiple slots (TBoMS), a specific rate matching mechanism may need to be considered.

[0023] For example, embodiments of TB processing across multiple slots, including rate matching and / or bit interleaving, are described further below.

[0024] Rate matching mechanism for TB processing across multiple slots using slot-by-slot bit interleaving. In one embodiment, bit interleaving is performed per slot. Specifically, the encoded bits for each code block are first divided into multiple segments based on the number of slots allocated to the TBoMS transmission. Interleaving is then applied to each code block segment. If more than one code block is carried by the TBoMS transmission, code block segments from different code blocks are concatenated and mapped to each slot allocated to the TBoMS transmission.

[0025] Figure 2 shows an example of TB processing across multiple slots with slot-by-slot bit interleaving. In this example, four slots are assigned to the TBoMS transmission. Furthermore, the bit sequence of each code block selected for the entire TBoMS transmission is divided into four parts corresponding to the four slots of the TBoMS transmission. Each bit sequence part is interleaved independently. Then, after concatenating the corresponding parts of all code blocks, the resulting sequence is mapped to the corresponding slots.

[0026] In one embodiment, the starting position of the encoded bits for slot-by-slot bit selection is predetermined within the circular buffer of each code block. Specifically, the starting position is determined according to the number of slots allocated to the TBoMS transmission and the size of the rate matching output. In this case, the starting position of the encoded bits for each slot is i·E r / N TBoMS slots It can be given by, where i is the slot index available for TBoMS, E r The rate matching size of code block r is N. TBoMS slots This is the number of slots allocated for TBoMS transmission.

[0027] Figure 3 shows an example of a starting position distribution with a fixed offset for bit selection. In this example, four slots are assigned to TBoMS transmissions. In this case, the distance between the starting positions of the code block segments for each slot of the TBoMS transmission is fixed.

[0028] Note that the above optional selection applies when a TBoMS transmission overlaps with a Physical Uplink Control Channel (PUCCH) carrying Uplink Control Information (UCI), when the UCI is multiplexed on the TBoMS within the overlapping slot, and when some of the encoded bits in the code block are dropped. In other words, the starting position does not depend on whether some or all of the encoded bits in the slot are dropped.

[0029] Figure 4 shows an example of a fixed-offset start position distribution for bit selection when some encoded bits in a slot are canceled. In this example, the start position is determined regardless of the cancellation of some encoding bits in the second slot allocated for TBoMS transmission.

[0030] The following is an example of the updated 3GPP® Technical Standard (TS) 38.212, V16.6.0 ("NR: Multiplexing and Channel Coding") [1] for rate matching and code block concatenation of TBoMS with bit interleaving per slot and bit selection start position distribution by fixed offset. 6.2.5 Rate Matching

number

[0031] After bit selection, the bits are

Number

[0032] The number of slots allocated for TBoMS transmission is N TBoMS slots is indicated. The bit sequence selected for slot s (s = 0, 1,..., N TBoMS slots - 1) is

Number

number

number

number

[0033] Code block concatenation is performed according to Section 5.5.

[0034] The bits after concatenating code blocks are:

number

[0035] Note that in the above example of the TS38.212 update, bit selection of the entire TBoMS is performed code block by code block according to section 5.4.2.1. Therefore, the above text provides an example of a per-slot procedure that is added to the conventional bit selection procedure in order to make the entire procedure work for both single-slot PUSCH transmissions and TBoMS.

[0036] In another example of this embodiment, slot-by-slot bit selection is performed immediately in section 5.4.2.1. Thus, if TBoMS is enabled, G is initialized with the total number of encoded bits to be transmitted within the TBoMS slots.

[0037] The following is an example of updating Section 5.4.2.1 of TS38.212[1] for TBoMS bit selection. Note that this example can be used to determine any bit interleaving options and start bit positions as shown herein. 5.4.2.1 Bit selection ------------------------Text omitted------------ rv id This transmits a redundant version number (rv id =0, 1, 2, or 3) is shown, and the rate-matched output bit sequence e k k=0,1,2,…,E-1 are generated as follows, where if TBoMS is not enabled, or if TBoMS is enabled, k0 is rv id The values ​​are given by Table 5.4.2.1-2 according to the LDPC base graph, otherwise k0 is consecutive from the last bit selected in the slot prior to the TBoMS transmission so that filler bits are not considered in the calculation of k0. k=0; j=0; while k <E if

number

number

[0038] Note that this may apply if a TBoMS transmission overlaps with a PUCCH carrying a UCI, and the UCI is multiplexed over the TBoMS in the overlapping slot, resulting in some of the encoded bits in the code block being dropped.

[0039] Furthermore, this may also apply when a TBoMS transmission in a slot is dropped due to a collision with a configured UL / DL indicated by a Dynamic Slot Format Indication (SFI), Uplink Cancellation Indication (CI), or a higher-priority uplink transmission.

[0040] In another optional case, if a TBoMS transmission within a slot is dropped due to a collision with a configured UL / DL indicated by a Dynamic Slot Formatting Instruction (SFI), Uplink Cancellation Instruction (CI), or a higher-priority uplink transmission, the starting position of the encoded bits for each slot for the TBoMS transmission is predetermined based on the number of allocated slots and the rate matching size of the TBoMS transmission, as described above. In other words, this is independent of whether the TBoMS is dropped due to a collision with a configured UL / DL indicated by a Dynamic SFI, Uplink CI, or a higher-priority uplink transmission.

[0041] Figure 5 shows an example of consecutive bit selection for the start position distribution in the case of cancellation. In this example, some of the encoded bits are dropped due to UCI multiplexing in TBoMS for the second slot. Furthermore, the start position of the third slot is determined based on the start position of the second slot and the number of rate-matching bits in the second slot. In this case, the encoded bits are selected consecutively for TBoMS transmission.

[0042] The following is an example of updating TS38.212 in sections 6.2.5 and 6.2.6[1] for rate matching and code block concatenation of TBoMS with per-slot bit interleaving and distribution of consecutive bit selection start positions. 6.2.5 Rate Matching

number

[0043] After bit selection, the bits are

number

[0044] The number of slots allocated for TBoMS transmission is N. TBoMS slotsThis is shown by the slot s(s=0, 1, ..., N). TBoMS slots The bit sequence selected for -1)

number

number

number

number

[0045] Code block concatenation is performed according to Section 5.5.

[0046] The bits after concatenating code blocks are:

number

[0047] In another embodiment, whether the starting position of the encoded bits within each slot is determined based on a predetermined starting position or on the actual number of bits transmitted in the previous slot may depend on whether semi-static or dynamic UCIs are multiplexed over a TBoMS transmission, with or without associated DCIs.

[0048] In the above optional selections, it should be noted that a semi-static UCI may include semi-persistent HARQ-ACK feedback in response to an SPS PDSCH without associated DCI, Scheduling Request (SR), Periodic Channel State Information (P-CSI), and / or semi-persistent CSI (SP-CSI). Furthermore, a dynamic UCI may include dynamic HARQ-ACK feedback in response to a PDSCH with associated DCI, HARQ-ACK feedback for a first SPS PDSCH associated with an activation DCI, and / or HARQ-ACK corresponding to an SPS release DCI.

[0049] Furthermore, TBoMS transmissions with associated DCIs may include Dynamic Grant TBoMS (DG-TBoMS) and / or Type 1 Configured Grant TBoMS (CG-TBoMS) associated with an Activation DCI. Additionally, TBoMS transmissions without associated DCIs may include Type 1 CG-TBoMS other than the first transmission, and Type 2 CG-TBoMS. In one optional case, when a semi-static UCI is multiplexed over a TBoMS transmission without associated DCI, the encoded bits are sequentially mapped to the resources allocated for the TBoMS transmission. In other words, the starting position of the encoded bits in each slot is determined based on the actual number of bits transmitted in the previous slot. Note that in this optional case, no timeline requirements for UCI multiplexing are necessary.

[0050] In another optional case, if a semi-static UCI is multiplexed over a TBoMS transmission without an associated DCI, and / or if a UCI is multiplexed over a TBoMS transmission within the slot that was first allocated, the encoded bits are sequentially mapped to the resources allocated for the TBoMS transmission. In other words, the starting position of the encoded bits in each slot is determined based on the actual number of bits transmitted in the previous slot.

[0051] In another optional case, when a semi-static UCI is multiplexed over a TBoMS transmission with an associated DCI, or when a dynamic UCI is multiplexed over a TBoMS transmission with or without an associated DCI, the starting position of the encoded bits in each slot is determined based on a predetermined starting position, as described above. In other words, the encoded bits are not sequentially mapped to the resources allocated for the TBoMS transmission, and the starting position is predetermined regardless of the number of bits actually transmitted in each slot.

[0052] In another optional case, when a semi-static UCI is multiplexed over a TBoMS transmission with an associated DCI, or when a dynamic UCI is multiplexed over a TBoMS transmission with or without an associated DCI, and when a UCI is multiplexed over a TBoMS transmission within the first allocated slot, the encoded bits are sequentially mapped to the resources allocated for the TBoMS transmission. In other words, the starting position of the encoded bits in each slot is determined based on the actual number of bits transmitted in the previous slot.

[0053] TBoMS rate matching mechanism with bit interleaving for every slot allocated for TBoMS transmission An embodiment of the rate matching mechanism for TBoMS with bit interleaving for each slot assigned to TBoMS transmission will be described further below.

[0054] In one embodiment, bit interleaving is performed for every slot assigned to the TBoMS by the code blocks mapped to each slot. Specifically, the encoding bits for each code block are interleaved first. Furthermore, the rate matching sequence for each code block is divided into multiple segments within each slot. Then, after concatenating the corresponding parts of all code blocks, the resulting sequence is mapped to the corresponding slot.

[0055] Figure 6 shows an example of multi-slot rate matching processing with bit interleaving for each entire TBoMS, where a code block is mapped to each slot. In this example, four slots are allocated to the TBoMS transmission. Furthermore, the bit sequences of each code block selected for the entire TBoMS transmission are interleaved. The rate matching sequence of each code block is divided into four parts corresponding to the four slots of the TBoMS transmission. Then, the corresponding parts of all code blocks are concatenated, and the resulting sequence is mapped to the corresponding slots.

[0056] Note that the same arbitrary selection as the bit selection start position distribution described above can be used for bit interleaving of the entire TBoMS by code blocks that map to each slot.

[0057] One example is shown below, which updates sections 6.2.5 and 6.2.6[1] to TS38.212 for rate matching and concatenation of TBoMS with bit interleaving for each slot assigned to TBoMS transmission, code blocks mapped to each slot, and bit selection start position distribution with fixed offsets. 6.2.5 Rate Matching

number

[0058] The bit after rate matching is

number

[0059] The number of slots allocated for TBoMS transmission is N. TBoMS slots This is shown by the slot s(s=0, 1, ..., N). TBoMS slots(-1) Selected bit sequence

number

number

[0060] Code block concatenation is performed according to Section 5.5.

[0061] The bits after concatenating code blocks are:

number

[0062] Another update example to TS38.212 in Sections 6.2.5 and 6.2.6[1] for rate matching and concatenation of TBoMS by bit interleaving for all slots allocated to TBoMS transmission, code blocks mapped to each slot, and the distribution of the starting positions of consecutive bit selections is shown below. 6.2.5 Rate Matching

Number

[0063] The bits after rate matching are

Number

[0064] The number of slots allocated to TBoMS transmission is indicated by N TBoMS slots . For each slot s (s = 0, 1,..., N TBoMS slots - 1), the selected bit sequence

Number

[0065] Code block concatenation is performed according to Section 5.5.

[0066] The bits after code block concatenation are [Number] indicated by where G s is the total number of coded bits to be transmitted within slot s.

[0067] In another embodiment, bit interleaving is performed for every slot assigned to the TBoMS by a series of code blocks mapped to the entire TBoMS transmission. Specifically, the encoding bits for each code block are first interleaved. Furthermore, the rate matching sequences of all code blocks are sequentially concatenated. The concatenated bits are then divided into multiple segments within each slot, and the resulting sequence is mapped to the corresponding slot.

[0068] Figure 7 shows an example of TB processing across multiple slots with bit interleaving for each TBoMS by sequential code block mapping to the entire TBoMS transmission. In this example, four slots are assigned to the TBoMS transmission. Furthermore, the bit sequences of each code block selected for the entire TBoMS transmission are interleaved. The rate matching sequences of all code blocks are concatenated sequentially. The concatenated bits are then divided into four parts corresponding to the four slots of the TBoMS transmission, and the resulting sequences are mapped to the corresponding slots.

[0069] Note that the same arbitrary selection as described above for the bit selection start position distribution can be used for bit interleaving per TBoMS with consecutive code blocks mapped to the entire TBoMS transmission, except that the splitting occurs after the code block concatenation. Therefore, in the case of a bit selection start position distribution with a fixed offset, the start position of the encoded bits per slot is i.e. r / N TBoMS slots It can be given by, where i is the slot index available for TBoMS, G is the total number of encoded bits for TBoMS transmission, and N TBoMS slots This is the number of slots allocated for TBoMS transmission.

[0070] For example, the following are updates to 3GPP TS38.212 for TBoMS rate matching and concatenation with bit interleaving for every slot assigned to a TBoMS transmission, a continuous code block mapped to the entire TBoMS transmission, and a bit selection start position distribution with a fixed offset in sections 6.2.5 and 6.2.6[1]. 6.2.5 Rate Matching

number

[0071] The bit after rate matching is

number

number

[0072] Code block concatenation is performed according to Section 5.5.

[0073] The bits after concatenating code blocks are:

number

[0074] The number of slots allocated for TBoMS transmission is N. TBoMS slots This is shown by the slot s(s=0,1,…,N TBoMS slots (-1) Selected bit sequence

number

number

[0075] The bit after rate matching is

number

number

[0076] Code block concatenation is performed according to Section 5.5.

[0077] The bits after concatenating code blocks are:

number

[0078] The number of slots allocated for TBoMS transmission is N. TBoMS slotsThis is shown by the slot s(s=0, 1, ..., N). TBoMS slots (-1) Selected bit sequence

number

[0079] Figure 8 shows Network 800 in various embodiments. Network 800 may operate in a manner consistent with the 3GPP Technical Specifications for LTE or 5G / NR systems. However, the exemplary embodiments are not limited in this respect, and the embodiments described may be applied to future 3GPP systems or other networks that benefit from the principles described herein, such as similar systems.

[0080] Network 800 may include UE802, which may include any mobile or non-mobile computing device designed to communicate with RAN804 via a wireless communication connection. UE802 may be coupled to RAN804 in a communicative manner via a Uu interface. UE802 may include, but is not limited to, smartphones, tablet computers, wearable computing devices, desktop computers, laptop computers, automotive infotainment, in-car entertainment devices, instrument clusters, head-up display devices, automotive 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.

[0081] In some embodiments, the network 800 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, PSFCH, etc.

[0082] In some embodiments, the UE802 may additionally communicate with the AP806 via a wireless communication connection. The AP806 may manage a WLAN connection that can help offload some / all network traffic from the RAN804. The connection between the UE802 and the AP806 may conform to any IEEE 802.11 protocol, where the AP806 may be a Wireless Fidelity (Wi-Fi®) router. In some embodiments, the UE802, RAN804, and AP806 may utilize cellular WLAN aggregation (e.g., LWA / LWIP). Cellular WLAN aggregation may include the UE802 configured by the RAN804 to utilize both cellular radio resources and WLAN resources.

[0083] RAN804 may include one or more access nodes, e.g., AN808. AN808 may terminate the radio interface protocol of UE802 by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN808 may enable data / voice connectivity between CN820 and UE802. In some embodiments, AN808 may be implemented in a discrete device or as one or more software entities running on a server computer as part of a virtual network, which may be called CRAN or virtual baseband unit pool, for example. AN808 is referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN808 may be a macrocell base station or low-power base station for providing femtocells, picocells, or other similar cells having a smaller coverage area, smaller user capacity, or higher bandwidth compared to macrocells.

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

[0085] Each AN of RAN804 can manage one or more cells, cell groups, component carriers, etc., and provide a wireless interface for network access to UE802. UE802 can simultaneously connect to multiple cells provided by the same or different ANs of RAN804. For example, UE802 and RAN804 can use carrier aggregation to enable UE802 to connect to multiple component carriers, each corresponding to a Pcell or Scell. In a dual connectivity 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.

[0086] The RAN804 may provide a radio interface via the licensed or unlicensed spectrum. To operate in the unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA technology by PCell / Scell. Before accessing the unlicensed spectrum, a node may perform medium / carrier sense operations, for example, based on the Listen Before Talk (LBT) protocol.

[0087] In a V2X scenario, UE802 or AN808 may be, or function as, an RSU, which may refer to any traffic infrastructure entity used for V2X communication. An RSU may be implemented in, or by, a suitable AN or static (or relatively static) UE. An RSU implemented in, or by, a UE may be called a “UE-type RSU,” an eNB may be called an “eNB-type RSU,” a gNB may be called a “gNB-type RSU,” and so on. In one example, an RSU is a computing device coupled to a roadside radio frequency circuit that provides connectivity support to a passing vehicle UE. An RSU may also include internal data storage circuitry that stores intersection map geometry, traffic statistics, medium, and applications / software that sense and control ongoing vehicle and pedestrian traffic. An RSU may provide very low-latency communication required for high-speed events such as collision avoidance, traffic warnings, and similar. Additionally or alternatively, an RSU may provide other cellular / WLAN communication services. The components of the RSU may be packaged in a weather-resistant enclosure suitable for outdoor installation and may include a network interface controller for providing wired connectivity (e.g., Ethernet®) to a traffic signaling controller or backhaul network.

[0088] In some embodiments, RAN804 may be an LTE RAN810 having an eNB, eNB812, for example. The LTE RAN810 may provide an LTE radio interface with features such as a 15kHz SCS; CP-OFDM waveforms for DL ​​and SC-FDMA waveforms for UL; turbo code for data and TBCC for control. The LTE radio interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and CRS for channel estimation for cell search and initial acquisition, channel quality measurement, and coherent demodulation / detection at UE. The LTE radio interface may operate in the sub-6GHz band.

[0089] In some embodiments, the RAN804 may be an NG-RAN814 having a gNB, e.g., gNB816, or an ng-eNB, e.g., ng-eNB818. The gNB816 may connect to a 5G-enabled UE using a 5G NR interface. The gNB816 may connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB818 may also connect to the 5G core via an NG interface, but may connect to the UE via an LTE radio interface. The gNB816 and ng-eNB818 may connect to each other via an Xn interface.

[0090] 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 NG-RAN814 nodes and the UPF848, and an NG control plane (NG-C) interface (e.g., N2 interface) that is a signaling interface between the NG-RAN814 nodes and the AMF844.

[0091] NG-RAN814 may provide a 5G NR radio interface featuring variable SCS; CP-OFDM for DL; CP-OFDM and DFT-s-OFDM for UL; polar codes, repeating codes, simplex codes, and ReedMuller codes for data control and LDPC. The 5G NR radio interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to LTE radio interfaces. The 5G NR radio interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for PDSCH phase tracking; and a tracking reference signal for time tracking. The 5G NR radio interface may operate in the FR1 band, including the sub-6GHz band, or in the FR2 band, including the 24.25GHz to 52.6GHz band. The 5G NR radio interface may include SSB, which is an area of ​​the downlink resource grid including PSS / SSS / PBCH.

[0092] In some embodiments, a 5G NR radio interface can utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCSs. For instance, UE802 may consist of multiple BWPs, each BWP configuration having a different SCS. When a BWP change is indicated to UE802, the SCS of transmission is also changed. Another example of a use case for BWPs relates to power saving. Specifically, multiple BWPs can be configured for UE802 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. BWPs with fewer PRBs can be used for low-traffic-load data transmissions while enabling power saving in UE802 and, potentially, in gNB816. BWPs with more PRBs can be used for scenarios with higher traffic loads. RAN804 is communicably coupled to CN820, which contains network elements that provide various functions to support data and telecommunications services to customers / subscribers (e.g., users of UE802). The components of CN820 may be implemented on one physical node or separate physical nodes. In some embodiments, NFV may be used to virtualize some or all of the functions provided by the network elements of CN820 onto physical computing / storage resources such as servers and switches. Logical instantiations of CN820 may be called network slices, and some logical instantiations of CN820 may be called network subslices.

[0093] In some embodiments, CN820 may be LTE CN822, also known as EPC. LTE CN822 may include MME824, SGW826, SGSN828, HSS830, PGW832, and PCRF834 coupled to one another via an interface (or “reference point”), as shown. The functions of the elements of LTE CN822 can be briefly described below.

[0094] The MME824 can track the current location of the UE802 and implement mobility management functions such as paging, bearer activation / deactivation, handover, gateway selection, and authentication.

[0095] The SGW826 can terminate the S1 interface toward the RAN and route data packets between the RAN and the LTE CN822. The SGW826 can be a local mobility anchor point for handover between RAN nodes and can also provide an anchor for 3GPP mobility. Other roles may include lawful interception, billing, and any policy enforcement.

[0096] The SGSN828 can track the location of the UE802 and perform security functions and access control. Furthermore, the SGSN828 can perform EPC node-to-node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by the MME824; MME selection for handover; and so on. An S3 reference point between the MME824 and the SGSN828 can enable the exchange of user and bearer information for mobility between 3GPP access networks in idle / active states.

[0097] The HSS830 may include a database for network users, containing subscription-related information to support the processing of communication sessions for network entities. The HSS830 may provide support for routing / roaming, authentication, authorization, name / address resolution, location dependency, etc. An S6a reference point between the HSS830 and MME824 may enable the transfer of subscription and authentication data to authenticate / authorize user access to the LTE CN820.

[0098] PGW832 may terminate its SGi interface toward a data network (DN) 836, which may include an application / content server 838. PGW832 may route data packets between the LTE CN822 and the data network 836. PGW832 may be coupled to SGW826 by an S5 reference point to facilitate user plane tunneling and tunnel management. PGW832 may further include nodes for policy enforcement and billing data collection (e.g., PCEF). Furthermore, the SGi reference point between PGW832 and the data network 836 may be an external public, private PDN, or intra-operator packet data network, for example, for provisioning IMS services. PGW832 may be coupled to PCRF834 via a Gx reference point. PCRF834 is the policy and billing control element of the LTE CN822. PCRF834 may be communicably coupled to the application / content server 838 to determine appropriate QoS and billing parameters for service flows. PCRF832 can provision relevant rules to PCEF (via Gx reference points) using appropriate TFT and QCI.

[0099] In some embodiments, CN820 may be 5GC840. 5GC840 may include AUSF842, AMF844, SMF846, UPF848, NSSF850, NEF852, NRF854, PCF856, UDM858, and AF860 coupled to one another via interfaces (or “reference points”), as shown. The functions of the elements of 5GC840 can be briefly described below. AUSF842 may store data for authentication of UE802 and handle authentication-related functions. AUSF842 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC840 via reference points as shown, AUSF842 may represent a Nausf service-based interface.

[0100] The AMF844 may enable other functions of the 5GC 840 to communicate with the UE802 and RAN804, and to subscribe to notifications about mobility events related to the UE802. The AMF844 may be responsible for registration management (e.g., registration of the UE802), connectivity management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF844 may provide transport for SM messages between the UE802 and SMF846 and may act as a transparent proxy for routing SM messages. The AMF844 may also provide transport for SMS messages between the UE802 and SMSF. The AMF844 may interact with the AUSF842 and UE802 to perform various security anchor and context management functions. Furthermore, the AMF844 may be the endpoint of the RAN CP interface, including or potentially containing an N2 reference point between the RAN804 and the AMF844; the AMF844 is the endpoint of NAS(N1) signaling and can perform NAS encryption and integrity protection. The AMF844 may also support NAS signaling with the UE802 via the N3 IWF interface.

[0101] SMF846 may be responsible for SM (e.g., session establishment and tunnel management between UPF848 and AN808); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of traffic steering in UPF848 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 LI systems); termination of the SM portion of NAS messages; downlink data notification; initiation of AN-specific SM information transmitted to AN808 via N2 through AMF844; and determination of the session's SSC mode. SM may refer to the management of PDU sessions, and PDU sessions or "sessions" may refer to PDU connectivity services that provide or enable the exchange of PDUs between UE802 and data network 836.

[0102] The UPF848 can function as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 836, and a branch point supporting multi-homed PDU sessions. The UPF848 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 utilization reporting, perform user plane QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., flow mapping from SDF to QoS), forward level packet marking on uplinks and downlinks, and perform downlink packet buffering and downlink data notification triggers. The UPF848 may include an uplink classifier to support routing traffic flows to the data network.

[0103] The NSSF850 can select a set of network slice instances to serve the UE802. The NSSF850 can also determine, if necessary, the mapping to authorized NSSAIs and subscribed S-NSSAIs. The NSSF850 can also determine, based on appropriate configuration and possibly by querying the NRF854, a set of AMFs, or a list of candidate AMFs, to be used to serve the UE802. The selection of a set of network slice instances for the UE802 may be triggered by the AMF844 to which the UE802 is registered by interacting with the NSSF850, which may result in a change of AMF. The NSSF850 can interact with the AMF844 via the N22 reference point; and can communicate with another NSSF in the visited network via the N31 reference point (not shown). Furthermore, the NSSF850 may represent an Nnssf service-based interface.

[0104] The NEF852 can securely expose services and functions provided by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g., AF860), edge computing systems, or fog computing systems. In such embodiments, the NEF852 can authenticate, authorize, or coordinate AFs. The NEF852 can also translate information exchanged with AF860 and information exchanged with internal network functions. For example, the NEF852 can translate between AF service identifiers and internal 5GC information. The NEF852 can also receive information from other NFs based on the exposed capabilities of those NFs. This information can be stored in the NEF852 as structured data or stored in a data storage NF using a standardized interface. The stored information can then be re-exposed by the NEF852 to other NFs and AFs, or used for other purposes such as analysis. Furthermore, the NEF852 can represent an Nnef service-based interface. NRF854 supports service discovery functionality, can receive NF discovery requests from NF instances, and can provide information about discovered NF instances to those instances. NRF854 also maintains information about available NF instances and their supported services. As used herein, “instantiate,” “instantiation,” and similar terms may refer to the creation of an instance, and “instance” may refer to the concrete creation of an object, for example, which may occur during the execution of program code. Furthermore, NRF854 may represent an Nnrf service-based interface. PCF856 can provide policy rules to control plane functions and enforce them, and may also support an integrated policy framework for managing network behavior. PCF856 may also implement a front-end to access subscription information related to policy decisions in the UDR of UDM858. In addition to communicating with functions via reference points as shown, PCF856 represents an Npcf service-based interface.The UDM858 may process subscription-related information to support the processing of communication sessions of network entities and may store subscription data for UE802. For example, subscription data may be communicated between the UDM858 and AMF844 via an N8 reference point. The UDM858 may include two parts: an application frontend and a UDR. The UDR may store subscription and policy data for the UDM858 and PCF856, and / or structured data for exposure and application data for the NEF852 (including a PFD for application discovery and application request information for multiple UE802s). A Nudr service-based interface may be indicated by the UDR221 to allow the UDM858, PCF856, and NEF852 to access specific sets of stored data and to subscribe to read, update (e.g., add, modify), delete, and receive notifications of changes to the relevant data within the UDR. The UDM may include a UDM-FE responsible for processing such as credentialing, location management, and subscription management. Multiple 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 via reference points as illustrated, the UDM858 may represent a Nudm service-based interface. The AF860 may influence application traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0105] In some embodiments, the 5GC 840 may enable edge computing by selecting an operator / third-party service geographically close to the point where the UE 802 is connected to the network. This can reduce latency and load on the network. To provide an edge computing implementation, the 5GC 840 may select a UPF 848 close to the UE 802 and perform traffic steering from the UPF 848 to the data network 836 via the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 860. In this way, the AF 860 may influence UPF (re)selection and traffic routing. When the AF 860 is considered a trusted entity based on the operator's deployment, the network operator may allow the AF 860 to interact directly with the relevant NF. Furthermore, the AF 860 may represent a NAF service-based interface. The data network 836 may represent various network operator services, internet access, or third-party services, which may be provided by one or more servers, including, for example, an application / content server 838.

[0106] Figure 9 schematically illustrates the wireless network 900 in various embodiments. The wireless network 900 may include a UE 902 that wirelessly communicates with AN 904. The UE 902 and AN 904 are similar to and substantially interchangeable components of similar names described elsewhere in this specification. The UE 902 may be communicatively coupled to AN 904 via a connection 906. The connection 906 is shown as a wireless interface to enable communicative coupling and may be compliant with a cellular communication protocol such as the LTE protocol or 5G NR protocol operating at millimeter wave or sub-6 GHz frequencies. The UE 902 may include a host platform 908 coupled to a modem platform 910. The host platform 908 may include an application processing circuit 912 that can be coupled to a protocol processing circuit 914 of the modem platform 910. The application processing circuit 912 may perform various applications for the UE 902 to source / sink application data. The application processing circuit 912 may further implement one or more layer operations for transmitting / receiving application data to and from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations. The protocol processing circuit 914 may implement one or more of these layer operations to facilitate the transmission or reception of data over connection 906. Layer operations implemented by the protocol processing circuit 914 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations. The modem platform 910 may further include a digital baseband circuit 916 that can implement one or more layer operations that are “lower” layer operations performed by the protocol processing circuit 914 in the network protocol stack.These operations may include PHY operations that include, for example, HARQ-ACK functionality, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bitmetric determination, multi-antenna port precoding / decoding which may include one or more of spatiotemporal, spatial frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronous sequence generation / detection, blind decoding of control channel signals, and one or more other related functions. The modem platform 910 may further include a transmit circuit 918, a receive circuit 920, an RF circuit 922, and one or more antenna panels 926, or an RF front end (RFFE) 924 which may be connected thereto. In short, the transmitting circuit 918 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receiving circuit 920 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 922 may include a low-noise amplifier, a power amplifier, a power tracking component, etc.; the RFFE 924 may include filters (e.g., surface / bulk acoustic wave filters), switches, an antenna tuner, beamforming components (e.g., phase array antenna components), etc. The selection and arrangement of the components of the transmitting circuit 918, the receiving circuit 920, the RF circuit 922, the RFFE 924, and the antenna panel 926 (collectively referred to as “transmitting / receiving components”) may be specific to particular implementation details such as whether the communication is TDM or FDM, millimeter wave frequency or sub-6 GHz frequency. In some embodiments, the transmitting / receiving components may be arranged in multiple parallel transmitting / receiving chains, on the same or different chips / modules, etc. In some embodiments, the protocol processing circuit 914 may include one or more instances of control circuits (not shown) for providing control functions to the transmit / receive components. UE reception may be established by and through the antenna panel 926, RFFE 924, RF circuit 922, receiving circuit 920, digital baseband circuit 916, and protocol processing circuit 914.In some embodiments, the antenna panel 926 may receive transmissions from AN904 by received beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 926.

[0107] UE transmission can be established by and through the protocol processing circuit 914, digital baseband circuit 916, transmitting circuit 918, RF circuit 922, RFFE 924, and antenna panel 926. In some embodiments, the transmitting components of UE 904 may apply spatial filtering to the transmitted data to form a transmit beam radiated by the antenna elements of antenna panel 926. Similar to UE 902, AN 904 may include a host platform 928 coupled to a modem platform 930. The host platform 928 may include an application processing circuit 932 coupled to the protocol processing circuit 934 of the modem platform 930. The modem platform may further include a digital baseband circuit 936, transmitting circuit 938, receiving circuit 940, RF circuit 942, RFFE circuit 944, and antenna panel 946. The components of AN 904 are similar to and substantially interchangeable with the similarly named components of UE 902. In addition to performing data transmission / reception as described above, the components of AN908 can perform various logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling. Figure 10 is a block diagram showing components that, in some exemplary embodiments, are capable of reading instructions from machine-readable or computer-readable media (e.g., non-temporary machine-readable storage media) and performing any one or more of the methodologies discussed herein. Specifically, Figure 10 shows a graphical representation of hardware resources 1000, including one or more processors (or processor cores) 1010, one or more memory / storage devices 1020, and one or more communication resources 1030, each of which can be communicably coupled via bus 1040 or other interface circuits. In embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1002 may be run to provide an execution environment for one or more network slices / subslice to utilize the hardware resources 1000.

[0108] Processor 1010 may include, for example, processors 1012 and 1014. Processor 1010 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a composite 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 discussed herein), or any suitable combination thereof.

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

[0110] The communication resource 1030 may include interconnects or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 1004, or with one or more databases 1006 or other network elements via the network 1008. For example, the communication resource 1030 may include wired communication components (e.g., for coupling via USB, Ethernet®, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

[0111] Instruction 1050 may comprise software, programs, applications, applets, apps, or other executable code that causes at least one of the processors 1010 to execute any one or more of the methodologies discussed herein. Instruction 1050 may reside entirely or partially in at least one of the processors 1010 (e.g., in the processor's cache memory), the memory / storage device 1020, or any suitable combination thereof. Furthermore, any portion of instruction 1050 may be transferred to the hardware resource 1000 from any combination of the peripheral device 1004 or the database 1006. Thus, the memory of the processor 1010, the memory / storage device 1020, the peripheral device 1004, and the database 1006 are examples of computer-readable and machine-readable media.

[0112] Exemplary Procedures In some embodiments, electronic devices, networks, systems, chips, or components, or parts or implementations thereof, shown in Figures 8–10, 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 1100 is shown in Figure 11. Process 1100 may be performed by a UE or a part thereof. In 1102, process 1100 may include receiving a slot allocation for the transmission of a transport block across multiple slots, where the transport block corresponds to a physical uplink shared channel (PUSCH) transmission. In 1104, process 1100 may further include performing bit interleaving of the transport block within the individual slots of the allocated slots. For example, to perform bit interleaving, the UE may divide the encoded bits from the individual code blocks of the transport block into multiple segments based on the number of allocated slots and apply bit interleaving to each segment.

[0113] Figure 12 shows another process 1200 according to various embodiments. Process 1200 may be performed by a gNB or a part thereof. In 1202, process 1200 may include assigning slots to User Equipment (UE) for the transmission of transport blocks across multiple slots, where the transport blocks correspond to physical uplink shared channel (PUSCH) transmissions. In 1204, process 1200 may further include receiving the transport blocks within the assigned slots, where the encoded bits of the transport blocks are interleaved within the individual slots of the assigned slots.

[0114] In one or more embodiments, at least one of the components described in one or more of the drawings above may be configured to perform one or more operations, techniques, processes, and / or methods as described in the following exemplary sections. For example, a baseband circuit described above in relation to one or more of the drawings above may be configured to operate according to one or more of the examples described below. In another example, a circuit associated with a UE, base station, network element, etc., described above in relation to one or more of the drawings above may be configured to operate according to one or more of the examples described in the following exemplary sections. [example]

[0115] Example A1, when executed by one or more processors of a user device (UE), receives a slot allocation for transmitting transport blocks across multiple slots, where the transport blocks correspond to physical uplink shared channel (PUSCH) transmissions; and may include one or more computer-readable media (CRM) storing instructions that constitute the UE to perform bit interleaving of the transport blocks within the individual slots of the allocated slots.

[0116] Example A2 may include one or more CRMs of Example A1, where, in order to perform bit interleaving, the UE divides the encoded bits from individual code blocks of the transport block into multiple segments based on the number of allocated slots; and applies bit interleaving to each segment.

[0117] Example A3 may include one or more CRMs from Example A2, where the instruction, when executed, further configures the UE to concatenate segments of different code blocks and map the concatenated segments to each of the assigned slots.

[0118] Example A4 may include one or more CRMs from Example A1, where the starting position of the encoded bits for bit selection per slot is predetermined according to the number of assigned slots and the rate matching size of the PUSCH transmission.

[0119] Example A5 may include one or more CRMs from Example A4, where the PUSCH transmission is dropped in one or more of the assigned slots.

[0120] Example A6 may include one or more CRMs of Example A5, where a PUSCH transmission is dropped in one or more of the allocated slots based on a semi-static time-division duplexing (TDD) uplink (UL) / downlink (DL) configuration, a dynamic slot format indication (SFI), an uplink cancellation indication (CI), or a collision with a higher-priority uplink transmission.

[0121] Example A7 may include one or more CRMs from Example A1, where the instruction further configures the UE to perform rate matching for code blocks of transport blocks in the assigned slot when executed.

[0122] Example A8 may include one or more CRMs from Examples A1 to A7, where the instruction further constitutes a UE that, when executed, multiplexes semi-static uplink control information (UCI) with a transport block in an allocated slot.

[0123] Example A9 may include one or more CRMs of Example A8, where the encoded bits are sequentially mapped to resources in the allocated slots, or the starting position of the encoded bits in each slot is determined based on a predetermined starting position.

[0124] Example A10 may include one or more CRMs from Example A8, where the UCI is multiplexed in the slots that overlap with the physical uplink control channel (PUCCH) among the allocated slots.

[0125] Example A11, when executed by one or more processors of a Next Generation NodeB (gNB), may include one or more computer-readable media (CRMs) storing instructions that constitute the gNB, such that the gNB assigns slots to a user device (UE) for transmitting transport blocks across multiple slots, where the transport blocks correspond to physical uplink shared channel (PUSCH) transmissions; and receives the transport blocks in the assigned slots, where the encoded bits of the transport blocks are interleaved within the individual slots of the assigned slots.

[0126] Example A12 may include one or more CRMs of Example A11, where the encoded bits from individual code blocks of the transport block are divided into multiple segments based on the number of slots allocated, and the segments are interleaved within the individual slots.

[0127] Example A13 may include one or more CRMs from Example A11, where the starting position of the encoded bits for bit selection per slot is predetermined according to the number of slots allocated and the rate matching size of the PUSCH transmission.

[0128] Example A14 may include one or more CRMs from Example A13, where the PUSCH transmission is dropped in one or more of the assigned slots.

[0129] Example A15 may include one or more CRMs of Example A14, where a PUSCH transmission is dropped in one or more of the assigned slots based on a semi-static time-division duplexing (TDD) uplink (UL) / downlink (DL) configuration, a dynamic slot format indication (SFI), an uplink cancellation indication (CI), or a collision with a higher-priority uplink transmission.

[0130] Example A16 may include one or more CRMs from Example A11, where the code blocks of the transport block are rate-matched within their assigned slots.

[0131] Example A17 may include one or more CRMs from Examples A11 to A16, where the instruction further configures the gNB to determine uplink control information that, when executed, is multiplexed with the transport block in the assigned slot.

[0132] Example A18 may include one or more CRMs of Example A17, where the encoded bits are sequentially mapped to resources in the allocated slots, or the starting position of the encoded bits in each slot is determined based on a predetermined starting position.

[0133] Example A19 may include one or more CRMs from Example A17, where the UCI is multiplexed in the slots that overlap with the physical uplink control channel (PUCCH) among the allocated slots.

[0134] Example A20 may include a device implemented in a user device (UE), the device comprising an interface for receiving transport blocks for transmission across multiple slots; and a processor circuit coupled to the interface. The processor circuit divides the encoded bits from individual code blocks of a transport block into multiple segments based on the number of slots allocated for the transmission of the transport block; and encodes the transport block for transmission using segments from different code blocks interleaved into individual slots of the allocated slots.

[0135] Example A21 may include the apparatus of Example A20, where the transmission is dropped in one or more of the allocated slots, and the starting position of the encoded bits per slot is determined based on the number of allocated slots and the rate matching size of the PUSCH transmission.

[0136] Example A22 may include the apparatus of Example A21, where a transmission may be dropped in one or more of the allocated slots based on a semi-static time-division duplication (TDD) uplink (UL) / downlink (DL) configuration, a dynamic slot format instruction (SFI), an uplink cancellation instruction (CI), or a collision with a higher-priority uplink transmission.

[0137] Example A23 may include the apparatus of Example A20, where the processor circuit further multiplexes semi-static uplink control information (UCI) with the transport block in the assigned slot.

[0138] Example A24 may include any of the devices in Examples A20 to A23, where the transport block is a physical uplink shared channel (PUSCH) transport block.

[0139] Example B1 may include a method of wireless communication for a fifth generation (5G) or New Radio (NR) system, the method comprising performing interleaving and rate matching by a UE based on a slot or all slots assigned to TB processing over a plurality of slots (TBoMS) for physical uplink shared channel (PUSCH) transmission.

[0140] Example B2 may include the method of Example B1 or some other example herein, wherein the coded bits for each code block are first divided into a plurality of segments based on the number of slots assigned to TBoMS transmission; interleaving is applied for each code block segment.

[0141] Example B3 may include the method of Example B1 or some other example herein, wherein when a plurality of code blocks are carried by TBoMS transmission, the code block segments of different code blocks are concatenated and mapped to each slot assigned to TBoMS transmission.

[0142] Example B4 may include the method of Example B1 or some other example herein, wherein the start position of the coded bits for bit selection for each slot is predetermined within the cyclic buffer of each code block; the start position is determined according to the number of slots assigned to TBoMS transmission and the size of the rate matching output.

[0143] Example B5 may include the method of Example B1 or some other example herein, wherein the start position of the encoding bits for each slot for TBoMS transmission depends on the number of selected coded bits of the previous slot.

[0144] Example B6 may include the method of Example B1 or some other example herein, wherein when some or a part of the encoding bits are dropped within a slot, the start position for the next slot is determined based on the number of rate matching bits within the slot.

[0145] Example B7 may include the method of Example B1 or some other examples herein, where if the TBoMS transmission within a slot is dropped due to a collision with a configured UL / DL indicated by a dynamic slot format indication (SFI), an uplink cancellation indication (CI), or a higher-priority uplink transmission, the starting position of the encoded bits for each slot for the TBoMS transmission is predetermined based on the number of allocated slots and the rate matching size of the TBoMS transmission.

[0146] Example B8 may include the method of Example B1 or some other examples herein, where bit interleaving is performed for every slot allocated to TBoMS using code blocks mapped to each slot.

[0147] Example B9 may include the method of Example B1 or some other examples herein, where the encoding bits for each code block are first interleaved; the rate matching sequence for each code block is split into multiple segments within each slot; after concatenating the corresponding parts of all code blocks, the resulting sequence is mapped to the corresponding slot.

[0148] Example B10 may include the method of Example B1 or some other examples herein, where the encoding bits for each code block are first interleaved; the rate matching sequences of all code blocks are concatenated continuously; after splitting the concatenated bits into multiple segments within each slot, the resulting sequence is mapped to the corresponding slot.

[0149] Example B11 may include the method of Example B1 or some other examples herein, where if multiplexing is performed on a TBoMS transmission without associated DCI with a semi-static UCI, the encoded bits are continuously mapped to the resources allocated for the TBoMS transmission.

[0150] Example B12 may include the method of Example B1 or some other example herein, where the encoded bits are sequentially mapped to the resources allocated for the TBoMS transmission when a semi-static UCI is multiplexed on a TBoMS transmission without an associated DCI, and / or when the UCI is multiplexed on a TBoMS transmission within the slot that was initially allocated.

[0151] Example B13 may include the method of Example B1 or some other example herein, where a semi-static UCI is multiplexed on a TBoMS transmission having an associated DCI, or a dynamic UCI is multiplexed on a TBoMS transmission with or without an associated DCI, the starting position of the encoded bits in each slot is determined based on a predetermined starting position as described above.

[0152] Example B14 may include the methods of Example B1 or some other examples herein, where the encoded bits are sequentially mapped to the resources allocated for the TBoMS transmission when a semi-static UCI is multiplexed on a TBoMS transmission with an associated DCI, or when a dynamic UCI is multiplexed on a TBoMS transmission with or without an associated DCI, and when the UCI is multiplexed on a TBoMS transmission within the slot that was initially allocated. Example B15 may include a method of the UE, the method comprising the steps of receiving a slot allocation for processing transport blocks across multiple slots, where the transport blocks correspond to physical uplink shared channel (PUSCH) transmissions; and performing interleaving and rate matching for code blocks of transport blocks in the allocated slots.

[0153] Example B16 may include the method of Example B15 or some other example herein, further comprising the step of dividing the encoded bits within an individual code block into multiple segments based on the number of allocated slots, wherein interleaving is applied to each segment.

[0154] Example B17 may include the methods of Examples B15-B16 or some other examples herein, where code block segments of different code blocks are concatenated and mapped to each of the assigned slots.

[0155] Example B18 may include the methods of Examples B15 to B17 or some other examples herein, where the starting position of the encoded bits for slot-by-slot bit selection is predetermined within a circular buffer of each code block; the starting position is determined according to the number of allocated slots and the size of the rate-matching output.

[0156] Example B19 may include the methods of Examples B15 to B18 or some other examples herein, further including the step of multiplexing a semi-static UCI with a transport block, where the encoded bits are sequentially mapped to the resources of the allocated slots.

[0157] Example B20 may include the method of Example B19 or some other example herein, wherein the transmission of the transport block does not have an associated DCI.

[0158] Example B21 may include the methods of Examples B19 to B20 or some other examples herein, where the UCI is multiplexed within the earliest allocated slot among the allocated slots.

[0159] Example B22 may include the methods of Examples 15-18 or some other examples herein, further including the step of multiplexing the UCI with a transport block, wherein the start position of the encoded bits in each slot is determined based on a predetermined start position.

[0160] Example B23 may include the methods of Example B19, Example B21, Example B22, or some other example of the Spec., where UCI is a semi-static UCI and the transmission has an associated DCI.

[0161] Example B24 may include the method of Example B19, Example B21, Example B22, or some other example herein, where the UCI is a dynamic UCI.

[0162] Example Z01 may include an apparatus comprising means for performing one or more elements of a method described in or related to any of Examples A1 to A24, Examples B1 to B24, or any other method or process described herein.

[0163] Example Z02 may include one or more non - transient computer - readable media containing instructions for causing an electronic device to perform one or more elements of a method described in or related to any of Examples A1 to A24, Examples B1 to B24, or any other method or process described herein when the instructions are executed by one or more processors of the electronic device.

[0164] Example Z03 may include an apparatus comprising logic, a module, or a circuit for performing one or more elements of a method described in or related to any of Examples A1 to A24, Examples B1 to B24, or any other method or process described herein.

[0165] Example Z04 may include a method, technique, or process described in or related to any of Examples A1 to A24, Examples B1 to B24, or any part or portion thereof.

[0166] Example Z05 may include an apparatus having one or more processors and one or more computer - readable media containing instructions for causing the one or more processors to perform a method, technique, or process described in or related to any of Examples A1 to A24, Examples B1 to B24, or any part of them when the instructions are executed by the one or more processors.

[0167] Example Z06 may include a signal described in or related to any of Examples A1 to A24, Examples B1 to B24, or any part or portion thereof.

[0168] Example Z07 may include datagrams, packets, frames, segments, protocol data units (PDUs), or messages described in or related to, or otherwise described in, Examples A1 to A24, Examples B1 to B24, or any part or portion thereof.

[0169] Example Z08 may include signals encoded with data described in or relating to any of Examples A1 to A24, Examples B1 to B24, or any part or portion thereof, or otherwise described in this disclosure.

[0170] Example Z09 may include signals encoded in any of Examples A1 to A24, Examples B1 to B24, or any part or portion thereof, or in any other way described herein, such as datagrams, packets, frames, segments, protocol data units (PDUs), or messages.

[0171] Example Z10 may include an electromagnetic signal carrying a computer-readable instruction, where the execution of the computer-readable instruction by one or more processors is to cause one or more processors to perform a method, technique, or process described in or related to any of Examples A1 to A24, Examples B1 to B24, or any part thereof.

[0172] Example Z11 may include a computer program containing instructions, where the execution of the program by a processing element is to cause the processing element to perform any of the methods, techniques, or processes described in or related to Examples A1 to A24, Examples B1 to B24, or any part thereof.

[0173] Example Z12 may include signals in a wireless network as shown and described herein.

[0174] Example Z13 may include a method of communication over a wireless network as shown and described herein.

[0175] Example Z14 may include a system for providing wireless communication as shown and described herein.

[0176] Example Z15 may include a device for providing wireless communication as shown and described herein.

[0177] Any of the above examples may be combined with any other example (or combination of examples) unless otherwise expressly stated. The foregoing descriptions relating to one or more implementations are for illustrative and explanatory purposes only, and are not intended to be exhaustive or to limit the scope of embodiments to the exact forms disclosed. Modifications and variations are possible in light of the above teachings or can be obtained from the implementation of various embodiments.

[0178] abbreviation Unless otherwise used herein, terms, definitions, and abbreviations may correspond to those defined in 3GPP TR21.905 v16.0.0 (2019-06). For the purposes of this specification, the following abbreviations may apply to the examples and embodiments discussed herein. 3GPP: Third Generation Partnership Project 4G: 4th generation 5G: Fifth Generation 5GC: 5G Core Network AC: Application Client ACR: Application Context Relocation ACK: Affirmative response ACID: Application Client Identification AF: Application Function AM: Approval Mode AMBR: Aggregated Maximum Bitrate AMF: Access and Mobility Management Function AN: Access Network ANR: Automatic Neighborhood Relationship AOA: Angle of arrival AP: Application Protocol, Antenna Port, Access Point API: Application Programming Interface APN: Access Point Name ARP: Allocation and retention priority ARQ: Automatic resend request AS: Access Layer ASP: Application Service Provider ASN.1: Abstract Syntax Notation 1 AUSF: Authentication Server Function AWGN: Additional white Gaussian noise BAP: Backhaul Adaptive Protocol BCH: Broadcast Channel BER: Bit Error Ratio BFD: Beam Fault Detection BLER: Block Error Rate BPSK: Binary Phase Shift Keying BRAS: Broadband Remote Access Server BSS: Business Support System BS: Base station BSR: Buffer Status Report BW: Bandwidth BWP: Bandwidth portion C-RNTI: Cellular Radio Network Temporary Identity CA: Carrier Aggregation, Certification Authority CAPEX: Capital expenditure CBRA: Competition-based random access CC: Component carrier, country code, cryptographic checksum CCA: Clear Channel Assessment CCE: Control Channel Element CCCH: Common Control Channel CE: Enhanced Coverage CDM: Content Delivery Network CDMA: Code Division Multiple Access CDR: Billing Data Request CDR: Billing Data Response CFRA: Random Access Without Conflict CG: Cell Group CGF: Billing Gateway Function CHF: Billing function CI: Cell Identity CID: Cell ID (e.g., positioning method) CIM: Common Information Model CIR: Carrier Interference Ratio CK: Encryption key CM: Connection Management, Stated Obligations CMAS: Commercial Mobile Alarm Service CMD: Command CMS: Cloud Management System CO: Stated optional selection CoMP: Cooperative Multipoint CORESET: Control Resource Set COTS: Commercial Off-the-Shelf CP: Control Plane, Cyclic Prefix, Connection Point CPD: Connection Point Descriptor CPE: Customer Perimeter Equipment CPICH: Common Pilot Channel CQI: Channel Quality Indicator CPU: CSI Processing Unit, Central Processing Unit C / R: Command / Response Field Bits CRAN: Cloud Wireless Access Network, Cloud RAN CRB: Common Resource Block CRC: Cyclic Redundancy Check CRI: Channel Status Information Resource Indicator, CSI-RS Resource Indicator C-RNTI: Cell RNTI CS: Circuit switch CSCF: Call Session Control Function CSAR: Cloud Service Archive CSI: Channel Status Information CSI-IM:CSI interference measurement CSI-RS:CSI reference signal CSI-RSRP: CSI Reference Signal Received Power CSI-RSRQ: CSI Reference Signal Reception Quality CSI-SINR: CSI signal-to-noise and interference ratio CSMA: Carrier-Sensitive Multiple Access CSMA / CA: CSMA with collision avoidance CSS: common search space, cell-specific search space CTF: Billing trigger function CTS: Permit sending CW: Codeword CWS: Conflict window size D2D: Device-to-device DC: Dual connectivity, direct current DCI: Downlink Control Information DF: Distributing Flavor DL: Downlink DMTF: Distributed Management Task Force DPDK: Dataplane Development Kit DM-RS, DMRS: Demodulation Reference Signal DN: Data Network DNN: Data Network Name DNAI: Data Network Access Identifier DRB: Data Wireless Bearer DRS: Discovery Reference Signal DRX: Intermittent reception DSL: Domain-Specific Language Digital subscriber line DSLAM: DSL access multiplexer DwPTS: Downlink Pilot Time Slot E-LAN: Ethernet (registered trademark) Local Area Network E2E: End to End EAS: Edge Application Server ECCA: Extended Clear Channel Assessment, Extended CCA ECCE: Improved Control Channel Element, Improved CCE ED: Energy detection EDGE: Extended data rates for GSM Evolution (registered trademark) EAS: Edge Application Server EASID: Edge Application Server Identifier ECS: Edge Configuration Server ECSP: Edge Computing Service Provider EDN: Edge Data Network EEC: Edge Enabler Client EECID: Edge Enabler Client Identifier EES: Edge Enabler Server EESID: Edge Enabler Server Identifier EHE: Edge Host Environment EGMF: Critical Governance Management Function EGPRS: Enhanced GPRS EIR: Device Identity Register eLAA: Enhanced License Assisted Access, Enhanced LAA EM: Element Manager eMBB: Enhanced Mobile Broadband EMS: Element Management System eNB: Evolution NodeB, E-ULTRAN NodeB EN-DC:E-UTRA-NR Dual Connectivity EPC: Advanced Packet Core EPDCCH: Enhanced PDCCH, Enhanced Physical Downlink Control Channel EPRE: Energy per resource element EPS: Advanced Packet System EREG: Enhanced REG, Enhanced Resource Element Group ETSI: European Telecommunications Standards Institute ETWS: Earthquake and Tsunami Warning System eUICC: Embedded UICC, Embedded General Purpose Integrated Circuit Card E-UTRA: Development UTRA E-UTRAN: Advanced UTRAN EV2X: Enhanced V2X F1AP: F1 Application Protocol F1-C: F1 Control Plane Interface F1-U: F1 User Plane Interface FACCH: High-speed accompanying control channel FACCH / F: High-speed accompanying control channel / full rate FACCH: High-speed accompanying control channel / half-rate FACH: Forward Access Channel FAUSCH: High-speed uplink signaling 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: Frontend FEC: Forward Error Correction FFS: For further research FFT: Fast Fourier Transform feLAA: Enhanced License Assist Access, Enhanced LAA FN: Frame count FPGA: Field-Programmable Gate Array FR: Frequency range FQDN: Fully specified domain name G-RNTI: GERAN Wireless Network Temporary Identity GERAN: GSM® Edge RAN, GSM® Edge Wireless Access Network GGSN: Gateway GPRS Support Node GLONASS: GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Positioning 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 Positioning System GPRS (General Packet Radio Service) GPSI: Generic Public Subscriber Identifier GSM (Registered Trademark): Global System for Mobile Communications, Groupe Special Mobile GTP: GPRS Tunneling Protocol GTP-U: GPRS tunneling protocol for user planes GTS: Go To Sleep signal (related to WUS) GUMMEI: Globally unique MME identifier GUTI: Globally Unique Temporary UE Identity HARQ: Hybrid ARQ, Hybrid Automated Resend Request HANDO: Handover HFN: Hyperframe number HHO: Hard Handover HLR: Home Position Register HN: Home Network HO: Handover HPLMN: Home Public Terrestrial 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 (https is http / 1.1 over SSL, i.e., port 443) I-Block: Information Block ICCID: Integrated Circuit Card Authentication IAB: Integrated Access and Backhaul ICIC: Inter-cell interference adjustment ID: Identity, Identifier IDFT: Discrete Inverse Fourier Transform IE: Information element IBE: In-band radiation IEEE: Institute of Electrical and Electronics Engineers IEI: Information Element Identifier IEIDL: Information element identifier data length IETF: Internet Technology Standardization Committee IF: Infrastructure IIOT: Internet of Industrial Things IM: Interferometry, Intermodulation, IP Multimedia IMC: IMS Certificate IMEI: International Mobile Device Identification Number IMGI: International Mobile Group Identification Number IMPI: IP Multimedia Private Identity IMPU: IP Multimedia Public Identity IMS: IP Multimedia Subsystem IMSI: International Mobile Subscriber Identification Number IoT: Internet of Things IP: Internet Protocol IPsec: IP security, Internet Protocol security IP-CAN: IP Connectivity Access Network IP-M: IP multicast IPv4: Internet Protocol Version 4 IPv6: Internet Protocol Version 6 IR: Infrared IS: Synchronous IRP: Integrated Reference Point ISDN (registered trademark): Integrated Services Digital Network ISIM: IM Service Identification Module ISO: International Organization for Standardization ISP: Internet Service Provider IWF: Interworking Function I-WLAN: Interworking WLAN Constraints on the length of superimposed codes, USIM: individual keys kB: kilobyte (1000 bytes) kbps: kilobits per second Kc: Encryption key Ki: Individual subscriber authentication key KPI: Key Performance Indicators KQI: Key Quality Indicators KSI: Key Set Identifier ksps: kilosymbols 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: License Assistance Access LAN: Local Area Network LADN: Local Area Data Network LBT: Listen Before Talk LCM: Lifecycle Management LCR: Low Chip Rate LCS: Location Services LCID: Logical Channel ID LI: Layer Indicator LLC: Logical Link Control, Low-Level Compatibility LMF: Location Management Function LOS: Line of Sight LPLMN: Local PLMN LPP: LTE Positioning Protocol LSB: Least least significant bit LTE: Long-Term Evolution LWA: LTE-WLAN Aggregation LWIP: Integration of LTE / WLAN radio levels with IPsec tunnels LTE: Long-Term Evolution M2M: Machine to Machine MAC: Media Access Control (in the context of protocol layering) MAC: Message Authentication Code (in a security / encryption context) MAC-A: MAC used for authentication and key sharing (in the context of TSG T WG3) MAC-I: 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: Mastercell Group MCOT: Maximum Channel Occupancy Time MCS: Modulation and Coding Scheme MDAF: Management Data Analysis Function MDAS: Management Data Analysis Service MDT: Minimizing Drive Tests ME: Mobile devices MeNB: MastereNB 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 Center MM: Mobility Management MME: Mobility Management Entity MN: Master Node MNO: Mobile Network Operator MO: Measurement object, mobile transmission 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 MSB: Most significant bit MSC: Mobile Switching Center MSI: Minimum System Information, MCH Scheduling Information MSID: Mobile Station Identifier MSIN: Mobile Station Identification Number MSISDN: Mobile subscriber ISDN (registered trademark) number MT: Mobile Terminated, Mobile Termination MTC: Machine Type Communication mMTC: Mass MTC, Mass Machine Type Communication MU-MIMO: Multi-user MIMO MWUS: MTC Wake-up signal, MTC WUS NACK: Negative response NAI: Network Access Identifier NAS: Non-Access Stratum, Non-Access Stratum layer NCT: Network Connectivity Topology NC-JT: Non-coherent joint transmission NEC: Network Functions Revealed NE-DC:NR-E-UTRA Dual Connectivity NEF: Network publishing function NF: Network Function NFP: Network Transfer Path NFPD: Network Forwarding Path Descriptor NFV: Network Functions Virtualization NFVI: NFV infrastructure NFVO: NFV Orchestrator NG: 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 wireless, proximity relations NRF: NF Repository Function NRS: Narrowband Reference Signal NS: Network Services NSA: Non-standalone operating mode NSD: Network Service Descriptor NSR: Network Service Record NSSAI: Network Slice Selection Aid Information S-NNSAI Single NSSAI NSSF: Network Slice Selection Function NW: Network NWUS: Narrowband Wake-up Signal, 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 cost OSI: Other System Information OSS: Operational Support System OTA: Wireless Communication 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 billing enforcement function PCF: Policy Control Function PCRF: Policy control and billing rule 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 Identifier PFD: Packet Flow Description P-GW: PDN Gateway PHICH: Physical Hybrid ARQ Indicator Channel PHY: Physical layer PLMN: Public Terrestrial Mobile Network PIN: Personal Identification Number PM: Performance measurement PMI: Precoded Matrix Indicator PNF: Physical Network Function PNFD: Physical Network Function Descriptor PNFR: Physical Network Function Record POC: PTT via cellular network PP, PTP: Point-to-Point PPP: Point-to-Point Protocol PRACH:Physical RACH PRB: Physical Resource Block PRG: Physical Resource Block Group ProSe: Proximity services, proximity-based services PRS: Positioning Reference Signal PRR: Packet Receiving Radio PS: Packet service PSBCH: Physical Sidelink Broadcast Channel PSDCH: Physical Sidelink Downlink Channel PSCCH: Physical Sidelink Control Channel PSSCH: Physical Sidelink Shared Channel PSCell: Primary SCell PSS: Primary Sync Signal PSTN: Public Switched Telephone Network PT-RS: Phase-tracing reference signal PTT: Push-to-Talk PUCCH: Physical uplink control channel PUSCH: Physical uplink shared channel QAM: Quadrature Amplitude Modulation QCI: QoS class of identifiers QCL: Pseudo-collocation QFI: QoS Flow ID, QoS Flow Identifier QoS: Quality of Service QPSK: Quadrature (4-phase) Phase Shift Keying QZSS: Quasi-Zenith Satellite System RA-RNTI: Random Access RNTI RAB: Wireless Access Bearer, Random Access Burst RACH: Random Access Channel RADIUS: Remote Authentication Dial-in User Service RAN: Wireless Access Network RAND: Random number (used for authentication) RAR: Random Access Response RAT: Wireless Access Technology RAU: Routing Area Update RB: Resource Block, Wireless Bearer RBG: Resource Block Group REG: Resource Element Group Rel: Release REQ:Request RF: Radio frequency RI: Rank Indicator RIV: Resource Indicator Value RL: Wireless Link RLC: Wireless Link Control, Wireless Link Control Layer RLC AM: RLC Approval Mode RLC UM: RLC Unapproved Mode RLF: Wireless Link Failure RLM: Wireless Link Monitoring RLM-RS: Reference signal for RLM RM: Registration Management RMC: Reference Measurement Channel RMSI (Remaining MSI), Minimum Remaining System Information RN: Relay node RNC: Wireless Network Controller RNL: Wireless Network Layer RNTI: Temporary Wireless Network Identifier ROHC: Robust Header Compression RRC: Wireless Resource Control, Wireless Resource Control Layer RRM: Wireless Resource Management RS: Reference signal RSRP: Reference signal received power RSRQ: Reference Signal Received Quality RSSI: Received Signal Strength Indicator RSU: Roadside Unit RSTD: Reference signal time difference RTP: Real-time Protocol RTS: Request to send RTT: Round-trip time Rx: Reception, Receiving, Receiver S1AP: S1 Application Protocol S1-MME: S1 for control plane S1-U: S1 for user plane S-CSCF: Serving CSCF S-GW: Functional Gateway S-RNTI: SRNC Wireless Network Temporary Identity S-TMSI:SAE Temporary Mobile Station Identifier SA: Standalone operating 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 Function Exposure Function SC-FDMA: Single Carrier Frequency Division Multiple Access SCG: Secondary Cell Group SCM: Security Context Management SCS: Subcarrier Spacing SCTP: Stream Controlled Transmission Protocol SDAP: Service Data Adaptive Protocol, Service Data Adaptive Protocol Layer SDL: Auxiliary Downlink SDNF: Structured Data Storage Network Function SDP: Session Description Protocol SDSF: Structured Data Storage Function SDT: Small Data Transmission SDU: Service Data Unit SEAF: Security Anchor Function SeNB: SecondaryeNB SEPP: Security Edge Protection Proxy SFI: Slot Formatting Instructions SFTD: Spatial-Frequency-Time Diversity, SFN, and Frame Timing Difference SFN: System Frame Number SgNB: SecondarygNB SGSN: Functional GPRS-supported node S-GW: Functional Gateway SI: System Information SI-RNTI: System Information RNTI SIB: System Information Block SIM: Subscriber Identity Module SIP: Initiating Session 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, number of sequences SoC: System-on-a-chip SON: Self-organizing networks 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 SS: Synchronization signal SSB: Synchronized Signal Block SSID: Service Set Identifier SS / PBCH block SSBRI SS / PBCH Block Resource Indicator, Synchronization 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 reception quality SS-SINR: Synchronization signal-based signal-to-noise and interference ratio SSS: Secondary Sync Signal SSSG: Search Space Set Group SSSIF: Search Space Set Indicator SST: Slice / Service Type SU-MIMO: Single-User MIMO SUL: Auxiliary uplink TA: Timing advance, tracking area TAC: Tracking Area Code TAG: Timing Advance Group TAI: Tracking Area Identity TAU: Tracking area updated TB: Transport Block TBS: Transport Block Size TBD: undefined 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 endpoint identifier TFT: Traffic Flow Template TMSI: Temporary Mobile Subscriber Identity TNL: Transport Network Layer TPC: Transmission Power Control TPMI: Transmission Precode Matrix Indicator TR: Technical Report TRP, TRxP: Transmission receiving point TRS: Tracking Reference Signal TRx: Transmitter / Receiver TS: Technical specifications, technical standards TTI: Transmission Time Interval Tx: Transmission, Transmitting, Transmitter U-RNTI: UTRAN Wireless Network Temporary Identity UART: General-purpose asynchronous receiver and transmitter UCI: Uplink Control Information UE: User Equipment UDM: Integrated Data Management UDP: User Datagram Protocol UDSF: Unstructured Data Storage Network Function UICC: General-purpose integrated circuit card UL:Uplink UM: Unauthorized Mode UML: Integrated Modeling Language UMTS: General-purpose 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: General-purpose serial bus USIM: General-Purpose Subscriber Identity Module USS:UE specific search space UTRA: UMTS Ground Wireless Access UTRAN: General-purpose terrestrial wireless access network UwPTS: Uplink Pilot Time Slot V2I: Vehicle-to-Infrastructure V2P: Pedestrian-vehicle interaction V2V: Vehicle-to-vehicle distance V2X: Vehicle-to-vehicle / road-to-vehicle VIM: Virtualization Infrastructure Manager VL: Virtual Link VLAN: Virtual LAN, Virtual Local Area Network VM: Virtual Machine VNF: Virtualized Network Function VNFFG: VNF Transfer Graph VNFFGD: VNF transfer graph descriptor VNFM: VNF Manager VoIP: Voice over IP, Voice over Internet Protocol VPLMN: Visiting Public Land Mobile Network VPN: Virtual Private Network VRB: Virtual Resource Block WiMAX (registered trademark): 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-UserPlane XML: Extended Markup Language XRES: Expected User Response XOR: Exclusive OR ZC: Zadoff-Chu ZP: Zero Power [term] For the purposes of this specification, the following terms and definitions apply to the examples and embodiments discussed herein.

[0179] As used herein, the term “circuit” refers to, 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), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured 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 functions described. The term “circuit” may also refer to a combination of one or more hardware elements (or combinations of circuits used in an electrical or electronic system) and program code used to perform the functions of that program code. In these embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuit.

[0180] 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 process 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, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device that can cause computer executable instructions, such as program code, software modules, and / or function processes, to be executed or otherwise operated. A processing circuit may comprise more hardware accelerators, which may be microprocessors, programmable processing devices, or similar. One or more hardware accelerators may comprise, 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 be referred to as “processor circuit.” As used herein, the term “interface circuit” refers to, a 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 buses, I / O interfaces, peripheral component interfaces, and / or network interface cards, and / or similar.

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

[0182] As used herein, the term “Network Element” refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless network services. The term “Network Element” may be considered synonymous with and / or referred to as networked computers, networked hardware, network equipment, network nodes, routers, switches, hubs, bridges, wireless network controllers, RAN devices, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, and / or similar.

[0183] 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 in a communicative manner. Furthermore, the terms “computer system” and / or “system” may refer to multiple computer devices and / or multiple computing systems that are interconnected in a communicative manner and configured to share computing resources and / or networking resources.

[0184] As used herein, the terms “appliance,” “computer appliance,” or similar terms refer to a computer device or computer system that includes 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 device, or otherwise is dedicated to providing a particular computing resource.

[0185] As used herein, the term “resource” means physical or virtual devices, physical or virtual components within a computing environment, and / or physical or virtual components within a particular device, such as 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, workload units, and / or similar. “Hardware resources” may mean computing resources, storage resources, and / or network resources provided by physical hardware elements. “Virtualization resources” may mean computing resources, storage resources, and / or network resources provided to applications, devices, systems, etc., by a virtualization infrastructure. The term “network resources” or “communication resources” may mean resources accessible by computer devices / systems via a communication network. The term “system resources” may mean any kind of shared entity for providing services, and may include computing resources 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 through a clearly identifiable server.

[0186] 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 meaning “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 meaning the path or medium through which data is communicated. 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.

[0187] As used herein, “instantiation,” “instantiation,” and similar terms refer to the creation of an instance. “Instance” also refers to the specific occurrence of an object that may occur, for example, during the execution of program code.

[0188] The terms “coupled” and “communicatively 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 one another, that two or more elements are indirectly in contact with one another but still work together or interact with one another, and / or that one or more other elements are coupled or connected between elements said to be coupled to one another. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements are able to come into contact with one another by communication, including through wired or other interconnections, through wireless communication channels or links, and / or similar means.

[0189] 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 data element that contains content.

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

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

[0192] The term "primary cell" refers to the MCG cell operating at the primary frequency from which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

[0193] The term "primary SCG cell" refers to the SCG cell that the UE performs random access to when it executes a synchronous reconfiguration procedure for DC operation.

[0194] The term "secondary cell" refers to a cell that provides additional radio resources on top of a special cell for UEs configured in a CA (Carrier Aggregation).

[0195] The term "secondary cell group" refers to a subset of zero or more secondary cells for a serving cell with a PSCell, and for a UE composed of DCs.

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

[0197] The term "serving cell" or "serving cells" refers to a special cell and a set of cells that have all secondary cells for UE in RRC_CONNECTED, which is composed of CA / DC.

[0198] The term "special cell" refers to the PCell of the MCG or the PSCell of the SCG in the case of DC operation; otherwise, the term "special cell" refers to the Pcell.

Claims

1. When executed by one or more processors of a user device (UE), Receive slot allocation for transmission of transport blocks across multiple slots, where the transport blocks correspond to physical uplink shared channel (PUSCH) transmissions; and Perform bit interleaving of the transport block within each of the allocated slots. Thus, one or more computer-readable media (CRM) storing the instructions constituting the UE, In order to perform the aforementioned bit interleaving, the UE shall The encoded bits from each code block of the transport block are divided into multiple segments based on the number of allocated slots; and The bit interleaving described above is applied to each segment. One or more CRMs.

2. The CRM according to claim 1, wherein, when the instruction is executed, the UE is further configured to concatenate the plurality of segments of different code blocks and map the concatenated plurality of segments to each of the assigned slots.

3. The CRM according to claim 1, wherein the starting position of the encoded bits for bit selection for each slot is predetermined according to the number of assigned slots and the rate matching size of the PUSCH transmission.

4. The PUSCH transmission is dropped in one or more of the allocated slots, one or more CRMs according to claim 3.

5. The one or more CRMs according to claim 4, wherein the PUSCH transmission is dropped in one or more of the allocated slots based on a semi-static time-division duplication (TDD) uplink (UL) / downlink (DL) configuration, a dynamic slot format instruction (SFI), an uplink cancellation instruction (CI), or a collision with a higher-priority uplink transmission.

6. The CRM according to claim 1, wherein the instruction, when executed, further configures the UE to perform rate matching for the code blocks of the transport blocks in the assigned slot.

7. The CRM according to any one of claims 1 to 6, wherein the instruction, when executed, further configures the UE to multiplex semi-static uplink control information (UCI) with the transport block in the assigned slot.

8. The CRM according to claim 7, wherein the encoded bits are sequentially mapped to the resources of the allocated slots, or the starting position of the encoded bits in each slot is determined based on a predetermined starting position.

9. The one or more CRMs according to claim 7, wherein the UCI is multiplexed in the slots of the allocated slots that overlap with the physical uplink control channel (PUCCH).

10. When executed by one or more next-generation NodeB (gNB) processors, Assigning slots to user equipment (UE) for transmitting transport blocks across multiple slots, where the transport blocks correspond to physical uplink shared channel (PUSCH) transmissions; and The transport block in the allocated slot is received, where the encoded bits of the transport block are interleaved within the individual slots of the allocated slot. Thus, one or more computer-readable media (CRM) storing the instructions constituting the gNB, The encoded bits from each code block of the transport block are divided into multiple segments based on the number of allocated slots, and the multiple segments are interleaved within each slot. One or more CRMs.

11. The CRM according to claim 10, wherein the starting position of the encoded bits for bit selection per slot is predetermined according to the number of assigned slots and the rate matching size of the PUSCH transmission.

12. The PUSCH transmission is dropped in one or more of the allocated slots, one or more CRMs according to claim 11.

13. The one or more CRMs according to claim 12, wherein the PUSCH transmission is dropped in one or more of the allocated slots based on a semi-static time-division duplication (TDD) uplink (UL) / downlink (DL) configuration, a dynamic slot format instruction (SFI), an uplink cancellation instruction (CI), or a collision with a higher-priority uplink transmission.

14. The code block of the transport block is rate-matched within the assigned slot, one or more CRMs according to claim 10.

15. The CRM according to any one of claims 10 to 14, wherein the instruction further configures the gNB to determine uplink control information that, when executed, is multiplexed with the transport block in the assigned slot.

16. The CRM according to claim 15, wherein the encoded bits are sequentially mapped to the resources of the allocated slots, or the starting position of the encoded bits in each slot is determined based on a predetermined starting position.

17. The UCI is multiplexed in the slots of the allocated slots that overlap with the physical uplink control channel (PUCCH), one or more CRMs according to claim 15.

18. A device implemented in a user device (UE), wherein the device is An interface for receiving slot allocations for transmitting transport blocks across multiple slots, wherein the transport blocks correspond to physical uplink shared channel (PUSCH) transmissions; and Processor circuit coupled to the interface Equipped with, The aforementioned processor circuit is Based on the number of slots allocated for transmission of the transport block, the encoded bits from each code block of the transport block are divided into multiple segments; and The transport block for transmission is encoded using the multiple segments from different code blocks interleaved into each of the assigned slots. Device.

19. The apparatus according to claim 18, wherein the transmission is dropped in one or more of the allocated slots, and the starting position of the encoded bits for each slot is determined based on the number of allocated slots and the rate matching size of the PUSCH transmission.

20. The apparatus according to claim 19, wherein the transmission is dropped in one or more of the allocated slots based on a semi-static time-division duplication (TDD) uplink (UL) / downlink (DL) configuration, a dynamic slot format instruction (SFI), an uplink cancellation instruction (CI), or a collision with a higher-priority uplink transmission.

21. The apparatus according to claim 18, wherein the processor circuit further multiplexes semi-static uplink control information (UCI) with the transport block in the assigned slot.

22. The apparatus according to any one of claims 18 to 21, wherein the transport block is a physical uplink shared channel (PUSCH) transport block.

Images