Small Data Transmission During Random Access Procedure for New Radio Systems

Abstract

Various embodiments may relate to small data transmission (SDT), also referred to herein as “early data transmission (SDT).” In particular, some embodiments disclosed herein include indicating a transport block size (TBS) and / or a modulation and coding scheme (MCS) for Msg3 and / or MsgA PUSCH transmissions, and / or indicating a fallback mechanism for SDT.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 058,106, filed July 29, 2020.

[0002] Field Various embodiments may generally relate to the field of wireless communications. For example, some embodiments may relate to small data transmission (SDT), also referred to herein as “early data transmission (EDT).” In particular, some embodiments disclosed herein include indicating a transport block size (TBS) and / or modulation and coding scheme (MCS) for Msg3 and / or MsgA PUSCH transmissions, and / or indicating a fallback mechanism for SDT. [Background technology]

[0003] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated, integrated communications platforms. The next-generation wireless communications system, 5G or New Radio (NR), provides access to information and data sharing by various users and applications anywhere, anytime. NR is expected to be a unified network / system that aims to meet very different, sometimes conflicting, performance dimensions and services. Such diverse multi-dimensional requirements are driven by different services and applications. In general, NR evolves based on 3GPP® LTE-Advanced and adds the potential of new radio access technologies (RATs) to enrich people's lives with better, simpler, and seamless wireless connectivity solutions. NR enables everything to be wirelessly connected, providing high-speed, rich content and services. [Brief explanation of the drawings]

[0004] [Figure 1] 1 illustrates an example of a four-step RACH procedure, according to various embodiments. [Figure 2] 1 illustrates an example of a two-step RACH procedure, according to various embodiments. [Figure 3] 3A and 3B illustrate examples of RAR UL grants indicating maximum resources for Msg3 PUSCH transmissions, according to various embodiments. [Figure 4] 10 illustrates an example of one-to-many mapping between preambles and PRUs for SDT with two-step RACH, according to various embodiments. [Figure 5] 10 illustrates an example of fallback to a 4-step RACH without SDT according to various embodiments. [Figure 6] 1 illustrates an example of fallback to a 4-step RACH with SDT, according to various embodiments. [Figure 7]10 illustrates an example of an R bit in fallbackRAR indicating a four-step fallback to RACH with and without SDT, according to various embodiments. [Figure 8-1] 1 illustrates an example of an E / T / R / R / BI MAC subheader, according to various embodiments. [Figure 8-2] 1 illustrates an example of an E / T / RAPID MAC subheader, according to various embodiments. [Figure 8-3] 1 illustrates an example of a MAC PDU including a MAC RAR, according to various embodiments. [Figure 8x-1] 10 illustrates an example of a BI MAC subheader, according to various embodiments. [Figure 8x-2] 10 illustrates an example of a FallbackRAR MAC subheader, according to various embodiments. [Figure 8x-3] 10 illustrates an example of a SuccessRAR MAC subheader, according to various embodiments. [Figure 8a-1] 10 illustrates an example of a BI MAC subheader, according to various embodiments. [Figure 8a-2] 10 illustrates an example of a FallbackRAR MAC subheader, according to various embodiments. [Figure 8a-3] 10 illustrates an example of a SuccessRAR MAC subheader, according to various embodiments. [Figure 8a-4] 1 illustrates an example of a MSGB MAC PDU with a MAC SDU, according to various embodiments. [Figure 8a-5] 1 illustrates an example of a MSGB MAC PDU that does not include a MAC SDU, according to various embodiments. [Figure 9] 1 illustrates a network in accordance with various embodiments. [Figure 10] 1 illustrates a wireless network in accordance with various embodiments. [Figure 11]FIG. 1 is a block diagram illustrating components that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methods discussed herein, according to some example embodiments. [Figure 12] 1 illustrates an exemplary procedure for carrying out various embodiments discussed herein. [Figure 13] 1 illustrates another exemplary procedure for carrying out various embodiments. [Figure 14] 1 illustrates another exemplary procedure for carrying out various embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0005] The following detailed description refers to the accompanying drawings, in which the same reference numbers may be used in different drawings to identify the same or similar elements.

[0006] In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to one of ordinary skill in the art having the benefit of this disclosure that various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In some instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this document, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).

[0007] I. Aspects of the Random Access Procedure Rel-15 NR defined a four-step procedure (also called the "random access procedure" or "RACH procedure") used for initial contention-based random access. As shown in Figure 1, in the first step of the four-step procedure, the UE transmits a physical random access channel (PRACH) in the uplink by selecting a preamble signature (e.g., Msg1: Random Access Preamble in Figure 1). This allows the gNB to estimate the delay between the gNB and the UE for subsequent UL timing adjustment. After the random access preamble is selected / determined, in the second step, the gNB feeds back a random access response (RAR), which carries timing advanced (TA) command information and an uplink grant for the uplink transmission. Then, in a third step, the UE transmits an L1 / L2 message (e.g., Msg3) over the physical uplink shared channel (PUSCH), which may carry the contention resolution ID and / or other information. Msg3 may be a message submitted from higher layers and transmitted on the UL-SCH containing a C-RNTI MAC CE or CCCH SDU associated with the UE Contention Resolution Identity as part of the random access procedure. In a fourth step, the gNB transmits a contention resolution message (e.g., Msg4) on the physical downlink shared channel (PDSCH).

[0008] In Rel-16 NR, a two-step RACH procedure was defined to allow for fast access and low-latency uplink transmission. In particular, the four-step RACH procedure is reduced to two steps, and the UE may combine Msg1 and Msg3 in the conventional RACH procedure for low-latency PRACH transmission. Furthermore, the two-step RACH can also be beneficial for supporting mMTC, where an MTC device can simply wake up, transmit uplink data, and go back to sleep using the two-step RACH procedure.

[0009] As shown in Figure 2, in the first step, the UE transmits a PRACH preamble and an associated MsgA PUSCH on the configured time and frequency resources, where the MsgA PUSCH may carry at least the equivalent content of Msg3 in a four-step RACH procedure. In the second step, after the gNB successfully detects the PRACH preamble and decodes the MsgA PUSCH, the gNB transmits MsgB, which may carry the equivalent content of Msg2 and Msg4 in a four-step RACH procedure.

[0010] To optimize support for infrequent small data transmissions, what is called early data transmission (EDT) or small data transmission (SDT), among other terms, may be used during the random access procedure, which helps reduce data transmission delay and save UE power consumption for UEs in RRC_INACTIVE mode. In particular, for a 4-step RACH, uplink (UL) and downlink (DL) data transmission may be enabled in Msg3 and Msg4, respectively. Furthermore, for UEs in RRC_INACTIVE mode, EDT can be completed without transitioning to RRC_CONNECTED mode, thereby saving state transition signaling overhead.

[0011] For SDT, depending on the data traffic, the UE may transmit data for Msg3 with potentially different payload sizes or transport block sizes (TBS). To enable the gNB to successfully decode Msg3 without substantially increasing receiver complexity, some mechanism may need to be defined for indication of the TBS or modulation and coding scheme (MCS) for Msg3 transmission.

[0012] The present disclosure provides embodiments related to SDT during a random access procedure in an NR system. In particular, embodiments herein include: Indication of the transport block size (TBS) and / or modulation and coding scheme (MCS) for Msg.3 and / or MsgA PUSCH transmissions; and · Fallback mechanism instructions for SDT.

[0013] II. TBS and / or MCS Indication for Msg3 and / or MsgA PUSCH Transmissions As mentioned above, for small data transmission (SDT), depending on the data traffic, the UE can transmit data for Msg3 using potentially different payload sizes or transport block sizes (TBS), or even taking into account other information that may be desirable to take into account various NR applications / scenarios, and may include, for example: (a) whether data segmentation is allowed (this can be understood in terms of whether the gNB allows 1 UL SDT (optionally followed by 1 DL SDT) or N UL SDTs (optionally followed by M DL SDTs) where N,M>1); (b) traffic delay tolerance, and / or (c) Traffic periodicity, etc.

[0014] Thus, this possible information can also be taken into consideration when creating different RACH configurations and associated ones, such as for Msg3 / MsgA. For brevity, the embodiments herein are discussed in terms of TBS / MCS, but any possible information is applicable for transmission according to the embodiments herein, even if such information is not explicitly mentioned in the following discussion.

[0015] To enable a gNB to successfully decode Msg3 without substantially increasing receiver complexity, some mechanism may need to be defined for indicating the TBS or modulation and coding scheme (MCS) for Msg3 transmission. Embodiments for indicating the TBS and / or MCS for Msg3 and / or MsgA PUSCH transmission are provided as follows:

[0016] In one embodiment, for EDT during the four-step and / or two-step RACH procedures, the UE can transmit the Msg.3 and / or MsgA PUSCH according to a TBS / MCS from a set of TBS / MCS values ​​configured by higher layers via NR remaining minimum system information (RMSI), NR other system information (OSI), or dedicated radio resource control (RRC) signaling. Note that a set of TBS / MCS values ​​may be configured for preamble groups A and B, respectively, and the UE selects a group whose set of TBS / MCS values ​​can handle the Msg3 / MsgA payload size.

[0017] Furthermore, for SDT during the 4-step RACH procedure, the RAR UL grant may indicate two or more Msg3 PUSCH frequency domain resource allocations (FDRA) and / or time domain resource allocations (TDRA). Based on the indicated MCS, the UE may first derive multiple TBSs according to the indicated FDRA and TDRA. If the Msg.3 payload size (for transmitting Msg3) is smaller than one of the derived TBSs for FDRA and TDRA, the UE performs zero padding to match the TBSs and selects the corresponding FDRA and TDRA for Msg3 PUSCH transmission.

[0018] In another embodiment, for SDT during a four-step RACH procedure, the RAR UL grant may indicate a single Msg3 PUSCH FDRA and TDRA. Additionally, the MCS field in the UL grant may be reserved, indicating that the UE ignores this field for Msg3 PUSCH transmission.

[0019] For this embodiment, the set of MCS values ​​for Msg3 transmission may be configured by higher layers via minimum system information (MSI), residual minimum system information (RMSI), other system information (OSI), and / or dedicated radio resource control (RRC) signaling. A set of MCS values ​​can be configured per preamble group A or preamble group B, or both preamble groups A and B.

[0020] Furthermore, based on the indicated FDRA and TDRA in the RAR UL authorization, the UE can derive a set of TBS according to the set of MCS values ​​configured by higher layers associated with the preamble group. If the payload size is smaller than one smallest TBS (denoted as TBS_A), the UE performs zero padding and selects an MCS from the set of MCS values ​​corresponding to TBS_A for the transmission of Msg3 PUSCH.

[0021] Table II-1 shows an example of the RAR UL acknowledgement field. In this example, the MCS field is reserved for SDT using a four-step RACH procedure. [Table 1]

[0022] As a further enhancement, the MCS in the RAR grant field for EDT in a 4-step RACH procedure may be used to indicate the maximum MCS index that the UE can use for Msg3 PUSCH transmission from the set of configured MCS values. In one example, assuming MCS#0 and MCS#3 are configured for SDT in a 4-step RACH, if the MCS field in the RAR UL grant indicates MCS#3, the UE can select either MCS#0 or MCS#3 for MSG3 transmission depending on the payload size of MSG3. In another example, if the MCS field in the RAR UL grant indicates MCS#0, the UE can use only MCS#0 for MSG3 transmission.

[0023] In another embodiment, for SDT during a 4-step RACH procedure, the RAR UL grant may be used to indicate a single Msg3 PUSCH FDRA and TDRA, which corresponds to the maximum resource allocation for Msg3 transmission. It also indicates the maximum TBS that can be carried by the Msg3 PUSCH, which can be derived according to the indicated FDRA and TDRA resources and MCS.

[0024] If the TBS set can be used for Msg3 transmission and the payload size is smaller than the one minimum TBS, the UE can use the indicated MCS and a subset of the allocated resources for Msg3 transmission.

[0025] In one example, a set of scaling factors can be configured to derive the subset of the allocated resources. When the scaling factor = 0.5, the UE may select half of the number of PRBs for Msg3 transmission. Note that the starting PRB for Msg3 PUSCH transmission can be derived based on the FDRA indicated in the RAR UL grant.

[0026] Figures 3a and 3b show an exemplary RAR UL grant indicating the maximum resources for Msg3 PUSCH transmission. Figures 3a and 3b show an example of using the RAR UL grant to indicate the maximum resources for Msg3 PUSCH transmission. In this example, TBS#0 and TBS#1 can be carried by Msg3 PUSCH, and TBS#1 is the maximum TBS (e.g., TBS#0 < TBS#1). In the RAR UL grant, the gNB can indicate the maximum resources, or N1 PRBs, which corresponds to TBS#1 as shown in Figure 3a. If the payload size is smaller than TBS#0, the UE can perform zero-padding and select a subset of the indicated maximum resources or N2 PRBs for Msg3 transmission as shown in Figure 3b. Note that Msg3 PUSCH transmission starts from the starting PRB indicated in the FDRA.

[0027] In another embodiment, for SDT with 2-step RACH procedure, if the gNB performs a fallback mechanism to SDT with 4-step RACH procedure, the gNB may use the fallback RAR UL grant to indicate the MCS and resources for Msg3 transmission. Furthermore, the above embodiments for the RAR UL grant are directly applicable for the fallback RAR UL grant for Msg3 transmission.

[0028] In another embodiment, the UE may be configured with two or more DMRS resources for transmission of Msg3 for the 4-step RACH and / or MsgA PUSCH for the 2-step RACH. The UE may transmit the DMRS on one of the DMRS resources according to the TBS / MCS for Msg3 for the 4-step RACH and / or MsgA PUSCH for the 2-step RACH.

[0029] In one example, if a UE is configured with two DMRS resources, when the UE transmits DMRS on the first DMRS resource, it can be used to indicate a first TBS / MCS for the transmission of Msg3 for the 4-step RACH and / or MsgA PUSCH for the 2-step RACH. When the UE transmits DMRS on the second DMRS resource, it can be used to indicate a second TBS / MCS for the transmission of Msg3 for the 4-step RACH and / or MsgA PUSCH for the 2-step RACH.

[0030] Note that the DMRS resource may include a DMRS sequence, a cyclic shift, a scrambling ID, and / or a DMRS antenna port. In one embodiment, for SDT using a 4-step RACH, multiple DMRS ports may be defined for Msg3 transmission. For example, two DMRS ports may be defined for Msg3 transmission. In this case, DMRS port 0 may be used to indicate the first TBS / MCS for Msg3 transmission, while DMRS port 1 or 2 may be used to indicate the second TBS / MCS for Msg3 transmission.

[0031] In another embodiment, for EDT using a 4-step RACH, when a CP-OFDM waveform is configured for transmission of Msg3, two or more scrambling IDs may be configured for Msg3 transmission by higher layers via RMSI (SIB1), OSI, or RRC signaling. If two scrambling IDs are configured, the first scrambling ID may be used to indicate a first TBS / MCS for transmission of Msg3, while the second scrambling ID may be used to indicate a second TBS / MCS for transmission of Msg3.

[0032] In another embodiment, for SDT using two-step RACH, a one-to-many mapping between MsgA PRACH preambles and PUSCH resource units (PRUs) may be defined. Note that a PRU is defined as an MsgA PUSCH opportunity associated with a DMRS resource. Here, an MsgA PUSCH opportunity is defined by the time and frequency resource for MsgA PUSCH transmission. When a one-to-two mapping is defined between an MsgA PRACH preamble and a PRU, one MsgA PRACH preamble is mapped to two PRUs. Furthermore, a first PRU may be used to indicate a first TBS / MCS for transmission of the MsgA PUSCH, while a second PRU may be used to indicate a second TBS / MCS for transmission of the MsgA PUSCH.

[0033] Figure 4 shows an example of one-to-many mapping between PRACH preambles and PRUs for SDT with two-step RACH. In this example, one-to-two mapping is assumed. Furthermore, for preamble #0, PRU #0 can be used to indicate the first TBS / MCS for MsgA PUSCH transmission, and PRU #1 can be used to indicate the second TBS / MCS for MsgA PUSCH transmission.

[0034] III. Specifying Fallback Mechanisms for SDT For SDT during RACH procedure, when the UE initiates an SDT request using a dedicated PRACH preamble reserved for SDT operation, the gNB will cause SDT over Msg3 to fall back to the legacy RACH procedure, or SDT over MsgA to fall back to the legacy RACH procedure (e.g., when the gNB cannot decode the MsgA PUSCH and the SDT Msg3 PUSCH resource is congested). In this case, some mechanism may need to be defined on how to indicate the fallback mechanism for SDT for both the two-step and four-step RACH procedures. An embodiment of the indication of the fallback mechanism for SDT during RACH procedure is provided as follows:

[0035] In an embodiment, a field in the Random Access Response (RAR) may be repurposed for SDT during the four-step RACH procedure, or some state in one or more existing fields in the RAR may be reserved and repurposed to indicate a fallback mechanism from SDT to the legacy four-step RACH procedure. Note that after the UE receives the RAR with the fallback indication, the UE follows the legacy RACH procedure and sends Msg3 without any SDT operation (e.g., resume or establish a connection that brings the UE to RRC_CONNECTED).

[0036] In one example, if the timing advance (TA) commands in the RAR are set to all '1', and / or the PUSCH frequency resource allocation in the RAR UL grant is set to all '1', and / or the MCS in the RAR UL grant is set to all '1', and / or the transmit power control (TPC) commands in the RAR UL grant are set to all '1', the UE may assume fallback to the legacy 4-step RACH without SDT operation.

[0037] In another example, if the channel state information (CSI) request in the RAR UL grant is set to '1', the UE may assume fallback to the legacy 4-step RACH without SDT operation.

[0038] In another embodiment, for SDT during the two-step RACH procedure, the UE may transmit the MsgA PUSCH according to a TBS / MCS from a set of TBS / MCS values ​​configured by higher layers via RMSI (SIB1), OSI, or RRC signaling. Note that the set of TBS / MCS values ​​can be configured for groups A and B, respectively.

[0039] After the UE transmits the MsgA PUSCH, the gNB may indicate that the UE should fall back to a four-step RACH with and without SDT. This may be the case if the gNB successfully detects the PRACH preamble but fails to decode the MsgA PUSCH. In particular, if the UE receives a fallback RAR, the UE may assume that the SDT with two-step RACH procedure falls back to a four-step RACH. Note that this fallback mechanism may assume a four-step RACH with or without SDT.

[0040] 5 illustrates an exemplary fallback mechanism to a four-step RACH without an SDT for a two-step RACH procedure, according to various embodiments. In the first step, the UE transmits both the MsgA PRACH and the PUSCH using the SDT. If the gNB successfully detects the PRACH preamble but fails to decode the MsgA PUSCH, the gNB may fall back to a four-step RACH without an SDT. In this case, the UE transmits Msg3 without an SDT.

[0041] 6 illustrates an example of an exemplary fallback mechanism to a four-step RACH with SDT for a two-step RACH procedure, according to various embodiments. In the first step, the UE transmits both the MsgA PRACH and PUSCH using the SDT. If the gNB successfully detects the PRACH preamble but fails to decode the MsgA PUSCH, the gNB may fall back to a four-step RACH with SDT. In this case, the UE transmits Msg3 using the SDT.

[0042] To inform the UE of the fallback decision, one or more fields in the fallback RAR may be repurposed, or some states in one or more fields in the fallback RAR may be reserved to indicate the fallback mechanism from SDT using 2-step RACH to a 4-step RACH procedure with and without SDT.

[0043] In one embodiment, the reserved field "R" in the fallback RAR can be set to '1' to indicate fallback to a 4-step RACH with SDT. In this case, the default state or '0' can be used to indicate fallback to a 4-step RACH without SDT. Alternatively, the reserved field "R" in the fallback RAR can be set to '1' to indicate fallback to a 4-step RACH without SDT. In this case, the default state or '0' can be used to indicate fallback to a 4-step RACH with SDT.

[0044] Figure 7 shows an example of using the R bit in the fallback RAR to indicate fallback to a 4-step RACH with and without SDT. Note that the fallback RAR is described in section 6.2.3a of 3GPP TS 36.310. In this example, bit '1' can be used to indicate fallback to a 4-step RACH with SDT, and bit '0' can be used to indicate fallback to a 4-step RACH without SDT. [Non-Patent Document 1] TS 38.321 v. 15.8.0, 202-01-07

[0045] In another embodiment, some states in one or more fields in the RAR may be reserved to indicate fallback to a 4-step RACH procedure with or without SDT. Note that the above embodiments can be used for indication. In one example, if the TA command in the fallbackRAR is set to all '1', and / or the PUSCH frequency resource allocation in the fallbackRAR UL grant is set to all '1', and / or the MCS in the fallbackRAR UL grant is set to all '1', and / or the TPC command in the fallbackRAR UL grant is set to all '1', the UE may assume fallback to the legacy 4-step RACH without SDT operation.

[0046] In another example, if the channel state information (CSI) request in the fallbackRAR UL grant is set to '1', the UE may assume fallback to the legacy 4-step RACH without SDT operation.

[0047] In another embodiment, different fallback RARs can be considered: one for non-SDT (e.g., using a legacy fallback RAR) and one for SDT (e.g., introducing a new SDT fallback RAR). This distinction can be indicated in the subheader for the RAR, as shown in the following figures:

[0048] A MAC PDU contains one or more MAC subPDUs, optionally including padding (see, for example, Figure 8-3). Each MAC subPDU contains one of the following: ·MAC subheader with only backoff indicator; ·MAC subheader with RAPID only (i.e., acknowledgment for SI request); · MAC subheader with RAPID and MAC RAR.

[0049] The MAC subheader with backoff indicator contains five header fields E / T / R / R / BI as shown in Figure 8-1. The MAC subheader with RAPID contains three header fields E / T / RAPID as shown in Figure 8-2.

[0050] A MAC subPDU with only a backoff indicator, if included, is placed at the beginning of the MAC PDU. A MAC subPDU with only RAPID and a MAC subPDU with RAPID and MAC RAR can be placed anywhere between the MAC subPDU with only a backoff indicator (if present) and the padding (if present). The padding is placed at the end of the MAC PDU, if present. The presence and length of the padding is implied based on the TB size, the size of the MAC subPDU.

[0051] For a 4-step RACH, the RAR PDU includes a subheader as shown by Figure 8-1 or Figure 8-2.

[0052] For a two-step RACH, the MsgB PDU includes a subheader as shown in Figure 8x-1, Figure 8x-2, and / or Figure 8x-3.

[0053] Field T indicates whether it is a backoff indication (T=00) or one of the fallback RARs (e.g., T=01 for non-SDT and T=10 for SDT fallback). In some embodiments, field T indicates whether it is a backoff indicator (or last MAC subPDU), a Fallback RAR (SDT or non-SDT), and / or a Success RAR.

[0054] If data / traffic segmentation is exchanged via SDT (or EDT), the mechanism described in this invention may also be used. Thus, the Msg.3 payload generated by the UE may be included in segmented data (where padding may be added if necessary) so that it fits within the allowed TBS for Msg.3 transmission. Furthermore, the network may control whether segmentation is allowed when using the SDT (or SDT) feature or a given RACH configuration.

[0055] The MAC PDU for MsgB contains one or more MAC subPDUs, optionally including padding. Each MAC subPDU consists of one of the following: ·MAC subheader with only backoff indicator; MAC subheader and fallback RAR; · MAC subheader and successRAR; ·MAC subheader and MAC SDU for CCCH or DCCH; MAC subheader and padding.

[0056] The MAC subheader with backoff indicators contains the five header fields E / T1 / T2 / R / BI as shown in Figure 8a-1. The MAC subPDU with only backoff indicators, if included, is placed at the beginning of the MAC PDU.

[0057] The MAC subheader for a fallbackRAR contains three header fields: E / T1 / RAPID, as shown in Figure 8a-2. The MAC subheader for a successRAR contains eight header fields: E / T1 / T2 / S / R / R / R / R, as shown in Figure 8a-3. The MAC subheader for a MAC SDU contains four header fields: R / F / LCID / L, as shown in Figure 6.1.2-1 and Figure 6.1.2-2 of TS38.321.

[0058] A MAC PDU contains at most one "MAC subPDU for successRAR" that indicates the presence of a "MAC subPDU for MAC SDU." The MAC subPDU for the MAC SDU is placed immediately after the "MAC subPDU for successRAR" that indicates the presence of a "MAC subPDU for MAC SDU."

[0059] If a MAC PDU contains MAC subPDUs for a MAC SDU, the last MAC subPDU for the MAC SDU is placed before the MAC subPDU with padding, as shown in Figure 8a-4. Otherwise, the last MAC subPDU in a MAC PDU is placed before the padding, as shown in Figure 8a-5. A MAC subPDU with padding includes the R / R / LCID MAC subheader and padding shown in Figure 6.1.2-3 of TS38.321. The size of the padding in a MAC subPDU with padding may be zero. The length of the padding is implicitly determined based on the TS size and the MAC subPDU size.

[0060] IV. Random Access Procedure Before the start of the physical random access (PRACH) procedure, Layer 1 (L1) receives a set of SS / PBCH block indices from higher layers and provides a corresponding set of RSRP measurements to higher layers. Before the start of the PRACH procedure, L1 may receive instructions from higher layers to perform a Type 1 random access procedure (e.g., a four-step PRACH procedure as shown in Figure 1 and / or as shown in clauses 8.1 to 8.4 of TS 38.213, v.16.1.0, 2020-04-03) or a Type 2 random access procedure (e.g., as shown in Figure 2 and / or as shown in clauses 8.1 to 8.2A of TS 38.213). Before starting the PRACH procedure, L1 receives the following information from higher layers: Configuration of Physical Random Access Channel (PRACH) transmission parameters (PRACH preamble format, time resources, and frequency resources for PRACH transmission). Parameters for determining the root sequence and its cyclic shift in the PRACH preamble sequence set (index to the logical root sequence table, cyclic shift (N CS ) and set type (unconstrained, constrained set A, or constrained set B).

[0061] From a physical layer (e.g., L1) perspective, the Type 1 L1 random access procedure includes the transmission of a random access preamble (Msg1) on the PRACH, a random access response (RAR) message (Msg2) with the PDCCH / PDSCH, and, if applicable, the transmission of a PUSCH scheduled by the RAR UL acknowledgement and a PDSCH for contention resolution.

[0062] From a physical layer (e.g., L1) perspective, the Type 2 L1 random access procedure includes the transmission of a random access preamble and PUSCH (MsgA) on the PRACH, the reception of a RAR message (MsgB) with the PDCCH / PDSCH, and, if applicable, the transmission of a scheduled PUSCH with a fallback RAR UL grant and a PDSCH for contention resolution.

[0063] If the random access procedure is initiated by a PDCCH command to the UE, the PRACH transmission has the same SCS as PRACH transmissions initiated by higher layers. If the UE is configured with two UL carriers for the serving cell and the UE detects a PDCCH command, the UE uses the UL / SUL indicator field value from the detected PDCCH command to determine the UL carrier for the corresponding PRACH transmission.

[0064] IV.1. Random Access Preamble The physical random access procedure is triggered upon a request for PRACH transmission by higher layers or by a PDCCH command. The configuration by higher layers for PRACH transmission includes: Configuration for PRACH transmission. Preamble index, preamble SCS, PPRACH, target, corresponding RA-RNTI, and PRACH resource.

[0065] The PRACH transmits with a transmit power P as described in section 7.4 on the indicated PRACH resources. PRRACH,b,f,c In (i), it is transmitted using the selected PRACH format.

[0066] For a Type 1 random access procedure, the UE is provided with N SS / PBCH block indices associated with one PRACH opportunity and R contention-based preambles per SS / PBCH block index per enabled PRACH opportunity with ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0067] For Type 1 random access procedure and Type 2 random access procedure with common PRACH opportunity configuration, the UE is provided with N SS / PBCH block indices associated with one PRACH opportunity via ssb-perRACH-OccasionAndCB-PreamblesPerSSB and Q contention-based preambles per SS / PBCH block index per enabled PRACH opportunity via msgA-CB-PreamblesPerSSB. PRACH transmissions may be performed on a subset of PRACH opportunities associated with the same SS / PBCH block index for UEs that have been provided with a PRACH mask index via msgA-ssb-sharedRO-MaskIndex according to TS 38.321.

[0068] For Type 1 random access procedure and Type 2 random access procedure with separate PRACH opportunity configuration, the UE is provided with N SS / PBCH block indices associated with one PRACH opportunity and R contention-based preambles per SS / PBCH block index per enabled PRACH opportunity according to ssb-perRACH-OccasionAndCB-PreamblesPerSSB-msgA if provided, or ssb-perRACH-OccasionAndCB-PreamblesPerSSB otherwise.

[0069] For a Type 1 random access procedure, or a Type 2 random access procedure with a separate PRACH opportunity configuration from the Type 1 random access procedure, if N<1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities, and R contention-based preambles with consecutive indices associated with the SS / PBCH block index for each valid PRACH opportunity are mapped, starting with preamble index 0. If N≥1, R contention-based preambles with consecutive indices associated with SS / PBCH block index n (0≤n≤N-1) for each valid PRACH opportunity are mapped, starting with preamble index n⋅N. total premable Starts with / N, where N total preamble is given by totalNumberOfRA-Preambles for Type 1 random access procedures or by msgA-totalNumberOfRA-Preambles for Type 2 random access procedures with separate PRACH opportunity configuration from Type 1 random access procedures and is an integer multiple of N.

[0070] For a Type 2 random access procedure with a common PRACH opportunity configuration with a Type 1 random access procedure, if N<1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities, and Q contention-based preambles with consecutive indices associated with the SS / PBCH block index for each valid PRACH opportunity are mapped starting from preamble index R. If N≥1, Q contention-based preambles with consecutive indices associated with SS / PBCH block index n (0≤n≤N-1) for each valid PRACH opportunity are mapped starting from preamble index n⋅N. total premable It starts with / N+R, where N total preamble is given by totalNumberOfRA-Preambles for Type 1 random access procedures.

[0071] For link recovery, the UE is provided with N SS / PBCH block indices associated with one PRACH opportunity by ssb-perRACH-Occasion in BeamFailureRecoveryConfig. For a dedicated RACH configuration provided by RACH-ConfigDedicated, if cfra is provided, the UE is provided with N SS / PBCH block indices associated with one PRACH opportunity by ssb-perRACH-Occasion in occasions. If N<1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities. If N≥1, all N consecutive SS / PBCH block indices are associated with one PRACH opportunity.

[0072] The SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon are mapped to valid PRACH opportunities in the following order: First, within a single PRACH opportunity, in ascending order of preamble index Second, for frequency multiplexed PRACH opportunities, in ascending order of frequency resource index Third, for time-multiplexed PRACH opportunities within a PRACH slot, in ascending order of time resource index Fourth, in ascending order of index for PRACH slots.

[0073] For mapping SS / PBCH block index to PRACH opportunities, the association period starting from frame 0 is the minimum value in the set determined by the PRACH configuration period according to Table IV.1-1, N Tx SSBN SS / PBCH block indices are mapped to PRACH opportunities at least once during the association period, and the UE shall determine N positions from the value of ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon. Tx SSB After an integer number of SS / PBCH block index to PRACH opportunity mapping cycles within the association period, N Tx SSB If there is a PRACH opportunity or a set of PRACH preambles that is not mapped to an SS / PBCH block index, no SS / PBCH block index is mapped to that PRACH opportunity or set of PRACH preambles. An association pattern period includes one or more association periods and is determined such that the pattern between PRACH opportunities and SS / PBCH block indices is repeated at most every 160 ms. After an integer number of association periods, PRACH opportunities that are not associated with an SS / PBCH block index, if any, are not used for PRACH transmission.

[0074] For a PRACH transmission triggered by a PDCCH command, if the value of the Random Access Preamble Index field is not zero, the PRACH Mask Index field indicates the PRACH opportunity for the PRACH transmission, and the PRACH opportunity is associated with the SS / PBCH block index indicated by the SS / PBCH Block Index field of the PDCCH command.

[0075] For PRACH transmissions triggered by higher layers, if ssb-ResourceList is provided, the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex, which indicates the PRACH opportunity for PRACH transmission, where the PRACH opportunity is associated with the selected SS / PBCH block index.

[0076] The PRACH opportunities are mapped consecutively for each corresponding SS / PBCH block index. The indexing of the PRACH opportunities indicated by the mask index value is reset for each mapping cycle of consecutive PRACH opportunities for each SS / PBCH block index. The UE selects the PRACH opportunity indicated by the PRACH mask index value for the indicated SS / PBCH block index in the first available mapping cycle for PRACH transmission.

[0077] For the indicated preamble index, the order of PRACH opportunities is as follows: First, for frequency multiplexed PRACH opportunities, in ascending order of frequency resource index Second, for time-multiplexed PRACH opportunities within a PRACH slot, in ascending order of time resource index Third, in ascending order of index for the PRACH slots.

[0078] For PRACH transmissions triggered upon request by higher layers, if csirs-ResourceList is provided, the value of ra-OccasionList indicates a list of PRACH opportunities for PRACH transmissions, where the PRACH opportunities are associated with the selected CSI-RS index indicated by csi-RS. The indexing of the PRACH opportunities indicated by ra-OccasionList is reset every association pattern period. [Table 2]

[0079] For paired spectrum, all PRACH opportunities are valid.

[0080] For unpaired spectra, If the UE is not provided with tdd-UL-DL-ConfigurationCommon, the PRACH opportunity in the PRACH slot is not before the SS / PBCH block in the PRACH slot and is at least N symbols after the last SS / PBCH block received. gap Start symbols (where N gap is given in Table IV.1-2), if ChannelAccessMode-r16=semistatic is given, it is valid if it does not overlap with the set of consecutive symbols before the start of the next channel occupation period during which the UE does not transmit. The candidate SS / PBCH block indices for the SS / PBCH blocks correspond to the SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon as described in clause 4.1 of TS38.213. If the UE is provided with tdd-UL-DL-ConfigurationCommon, a PRACH opportunity within a PRACH slot is valid if: Within the UL symbol, or At least N symbols after the last downlink symbol and not before the SS / PBCH block in the PRACH slot gap symbols and at least N after the last SS / PBCH block symbol gap Start symbols (where N gap is given in Table IV.1-2), and if ChannelAccessMode-r16=semistatic is given, there shall be no overlap with the set of consecutive symbols before the start of the next channel occupation period in which there is no transmission at all. The candidate SS / PBCH block indices for the SS / PBCH blocks correspond to the SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon as described in Section 4.1.

[0081] For preamble format B4, N gap =0 N gap =0. [Table 3]

[0082] If the random access procedure is initiated by a PDCCH command, the UE transmits the PRACH at the selected PRACH opportunity if requested by higher layers. In this case, the time between the last symbol of the PDCCH command reception and the first symbol of the PRACH transmission is N T,2 +Δ BWPSwitching +Δ Delay +T switch msec or more, where N T,2 is the duration of N symbols corresponding to the PUSCH preparation time for UE processing capability 1, and it is assumed that μ corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH command and the SCS configuration of the corresponding PRACH transmission. If the active UL BWP does not change, Δ BWPSwitching =0, otherwise Δ BWPSwitching is defined in any suitable way. Δ for FR1 Delay = 0.5 msec, and for FR2, Δ Delay =0.25msec. T switch is the switching gap duration.

[0083] For PRACH transmissions using an SCS of 1.25 kHz or 5 kHz, the UE determines N2 assuming an SCS configuration μ=0.

[0084] For single-cell operation or operation with carrier aggregation on the same frequency band, the UE shall not transmit PRACH and PUSCH / PUCCH / SRS in the same slot or if the gap between the first or last symbol of PRACH transmission in the first slot is less than N symbols away from the last or first symbol, respectively, of PUSCH / PUCCH / SRS transmission in the second slot, where N=2 for μ=0 or μ=1, and N=4 for μ=2 or μ=3, and μ is the SCS configuration for the active UL BWP. For PUSCH transmissions with repetition type B, this applies to each actual repetition of the PUSCH transmission.

[0085] IV.1A PUSCH for Type 2 Random Access Procedure For a Type 2 random access procedure, the UE transmits the PUSCH after transmitting the PRACH, if applicable. The UE encodes the transport block provided for PUSCH transmission using redundancy version number 0. The PUSCH transmission occurs at least N symbols after the PRACH transmission, where N=2 for μ=0 or μ=1, and N=4 for μ=2 or μ=3, and μ is the SCS configuration for the active UL BWP.

[0086] If the PUSCH opportunity associated with the DMRS resource is not mapped to the preamble of a valid PRACH opportunity, or if the associated PRACH preamble is not transmitted as described in Section 7.5 or Section 11.1, the UE does not transmit a PUSCH on the PUSCH opportunity. If the PRACH preamble is not mapped to a valid PUSCH opportunity, the UE may transmit a PRACH preamble on a valid PRACH opportunity.

[0087] The mapping between one or more PRACH preambles and the PUSCH opportunities associated with the DMRS resource is per PUSCH configuration.

[0088] The UE determines the time and frequency resources for PUSCH opportunities in the active UL BWP from the msgA-PUSCH-Config for the active UL BWP. If the active UL BWP is not the first UL BWP and the msgA-PUSCH-Config for the active UL BWP is not provided, the UE uses the msgA-PUSCH-Config provided for the first UL BWP.

[0089] The UE determines the first interlace or first RB for the first PUSCH opportunity in the active UL BWP from interlaceIndexFirstPO-MsgA-PUSCH or frequencyStartMsgA-PUSCH, respectively, which gives an offset in the number of RBs in the active UL BWP from the first RB in the active UL BWP. A PUSCH opportunity includes several interlaces or several RBs, as provided by nrofInterlacesPerMsgA-PO or nrofPRBs-perMsgA-PO, respectively. Consecutive PUSCH opportunities in the frequency domain of the UL BWP are separated by a number of RBs, as provided by guardBandMsgA-PUSCH. The number of PUSCH opportunities in the frequency domain of the UL BWP, N, is f is provided by nrMsgA-PO-FDM.

[0090] If the UE does not have a dedicated RRC configuration, or has an initial UL BWP as the active UL BWP, or startSymbolAndLengthMsgA-PO is not provided, msgA-PUSCH-timeDomainAllocation provides the SLIV and PUSCH mapping type for PUSCH transmission by indicating: If PUSCH-TimeDomainResourceAllocationList is provided in PUSCH-ConfigCommon, the first maxNrofUL-Allocations values ​​from PUSCH-TimeDomainResourceAllocationList If PUSCH-TimeDomainResourceAllocationList is not provided in PUSCH-ConfigCommon Otherwise, the SLIV is provided by startSymbolAndLengthMsgA-PO and the PUSCH mapping type is provided by mappingTypeMsgA-PUSCH for PUSCH transmission.

[0091] To map one or more preambles in a PRACH slot to a PUSCH opportunity associated with a DMRS resource, the UE determines the first slot for the first PUSCH opportunity in the active UL BWP from msgA-PUSCH-TimeDomainOffset, which provides an offset, in slot numbers, in the active UL BWP relative to the start of the PUSCH slot containing the start of each PRACH slot. The UE does not expect to have a PRACH preamble transmission and a PUSCH transmission with msgA in the PRACH slot or PUSCH slot, or to have overlapping msgA PUSCH opportunities for the MsgA PUSCH configuration. The UE expects the first PUSCH opportunity in each slot to have the same SLIV for the PUSCH transmission provided by startSymbolAndLengthMsgA-PO.

[0092] Consecutive PUSCH opportunities in each slot are separated by guardPeriodMsgA-PUSCH symbols and have the same duration. The number of time-domain PUSCH opportunities in each slot, N t is the number of consecutive slots containing PUSCH opportunities, N, given by nrofMsgA-PO-perSlot. sis provided by nrofSlotsMsgA-PUSCH.

[0093] The UE is provided with the DMRS configuration for PUSCH transmissions on PUSCH opportunities in the active UL BWP via msgA-DMRS-Configuration.

[0094] The UE is provided with the MCS for data information in the PUSCH transmission for the PUSCH opportunity according to msgA-MCS.

[0095] For PUSCH transmission with frequency hopping in a slot, as indicated by msgA-intraSlotFrequencyHopping for an active UL BWP, the frequency offset for the second hop is N UL,hop The PUSCH transmission is determined using msgA-HoppingBits instead of guardPeriodMsgA-PUSCH. If guardPeriodMsgA-PUSCH is provided, the first symbol of the second hop is separated by guardPeriodMsgA-PUSCH symbols from the end of the last symbol of the first hop; otherwise, there is no time separation of PUSCH transmissions before and after frequency hopping. If the UE is provided with useInterlacePUCCH-PUSCH in BWP-UplinkCommon, the UE shall transmit PUSCH without frequency hopping. PUSCH transmissions use the same spatial filter as the associated PRACH transmission.

[0096] The UE decides whether to apply transform pre-coding for the PUSCH transmission.

[0097] A PUSCH opportunity for a PUSCH transmission is defined by frequency and time resources and is associated with DMRS resources, which are provided by msgA-DMRS-Configuration.

[0098] N out of valid PRACH opportunities in a PRACH slot preambleEach successive number of preamble indices is First, in ascending order of preamble index within a single PRACH opportunity Second, for frequency multiplexed PRACH opportunities, in ascending order of frequency resource index Third, for time-multiplexed PRACH opportunities within a PRACH slot, in ascending order of time resource index The associated DMRS resources are mapped to available PUSCH opportunities. First, for frequency multiplexed PUSCH, the frequency resource index f id In ascending order of Second, within a PUSCH opportunity, in ascending order of DMRS resource index, where DMRS resource index DMRS id is determined first in ascending order of DMRS port index and second in ascending order of DMRS sequence index, Third, for time-multiplexed PUSCH opportunities within a PUSCH slot, the time resource index t id In ascending order of Fourth, in ascending order of index for PUSCH slots. where N preamble =ceil(T preamble / T PUSCH ) and T preamble is the total number of valid PRACH opportunities per association pattern period multiplied by the number of preambles per valid PRACH opportunity provided by the msgA-PUSCH-PreambleGroup, and T PUSCH is the total number of valid PUSCH opportunities per PUSCH configuration per association pattern period multiplied by the number of DMRS resource indices per valid PUSCH opportunity provided by msgA-DMRS-Configuration.

[0099] A PUSCH opportunity is valid if it does not overlap in time and frequency with any PRACH opportunity associated with either a Type 1 or Type 2 random access procedure. Furthermore, for unpaired spectrum and for SS / PBCH blocks with indices provided by ssb-PositionsInBurst in SIB1 or by ServingCellConfigCommon If the UE is not provided with tdd-UL-DL-ConfigurationCommon, the PUSCH opportunity -Does not precede the SS / PBCH block in the PUSCH slot, At least N symbols from the last SS / PBCH block symbol gap If you start after the symbol, PUSCH opportunities are available, where N gap is given in Table IV.1-2, If the UE is provided with tdd-UL-DL-Configuration Common, the PUSCH opportunity Within UL symbols, or does not precede an SS / PBCH block in a PUSCH slot, and At least N symbols after the last downlink symbol gap symbol after the last SS / PBCH block symbol and at least N gap Starts after the symbol (where N gap is given in Table IV.1-2), and if ChannelAccessMode-r16=semistatic is provided, the UE does not transmit if it does not overlap with the set of consecutive symbols before the start of the next channel occupation period. PUSCH opportunities are available.

[0100] IV.2 Random Access Response - Type 1 Random Access Procedure In response to a PRACH transmission, the UE attempts to detect DCI format 1_0 using a CRC scrambled by the corresponding RA-RNTI during a window controlled by higher layers. The window starts with the first symbol of the earliest CORESET for which the UE is configured to receive a PDCCH for the Type1-PDCCH CSS set, as defined in Section 10.1, i.e., at least one symbol after the last symbol of the PRACH opportunity corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for the Type1-PDCCH CSS set, as defined in Section 10.1. The length of the window in number of slots, based on the SCS for the Type1-PDCCH CSS set, is given by ra-ResponseWindow.

[0101] If the UE detects DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI, where the LSB of the SFN field in DCI format 1_0 is the same as the corresponding LSB of the SFN, as applicable, where the UE transmits a PRACH, and the UE receives a transport block on the corresponding PDSCH within that window, the UE passes the transport block to higher layers. The higher layers parse the transport block for the random access preamble identity (RAPID) associated with the PRACH transmission. If the higher layers identify RAPID in the RAR message(s) for the transport block, the higher layers indicate an uplink acknowledgment to the physical layer. This is called a random access response (RAR) UL acknowledgment at the physical layer.

[0102] If the UE does not detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within that window, or if the UE detects DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within that window and the LSB of the SFN field in DCI format 1_0 is not the same as the corresponding LSB of the SFN, as applicable, where the UE transmitted a PRACH, or if the UE does not correctly receive a transport block in the corresponding PDSCH within that window, or if the upper layer does not identify a RAPID associated with the PRACH transmission from the UE, the upper layer can instruct the physical layer to transmit a PRACH. If requested by the upper layer, the UE is expected to transmit a PRACH within msec of the last symbol of the window or the last symbol of the PDSCH reception. where is the duration of symbols corresponding to the PDSCH processing time for UE processing capability 1, and corresponds to the smallest SCS configuration for the PDCCH carrying DCI format 1_0, the corresponding PDSCH when an additional PDSCH DM-RS is configured, and the corresponding PRACH. For , the UE assumes . For PRACH transmissions using 1.25 kHz or 5 kHz SCS, the UE determines given the SCS configuration.

[0103] If the UE detects DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI, and the LSB of the SFN field in DCI format 1_0 is the same as the corresponding LSB of the SFN, as applicable, where the UE transmits a PRACH and the UE receives a transport block in the corresponding PDSCH, the UE may assume the same DM-RS antenna port quasi-co-location characteristics for the SS / PBCH blocks or CSI-RS resources that the UE used for the PRACH association, as described in Section IV.1, regardless of whether the UE is provided with a TCI-State for the CORESET for which the UE receives a PDCCH with DCI format 1_0.

[0104] If the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order triggering a contention-free random access procedure for an SpCell, the UE may assume that the PDCCH containing DCI format 1_0 and the PDCCH order have the same DM-RS antenna port quasi-co-location characteristic. If the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order triggering a contention-free random access procedure for a secondary cell, the UE may assume the DM-RS antenna port quasi-co-location characteristic of the CORESET associated with the Type1-PDCCH CSS configured to receive the PDCCH containing DCI format 1_0.

[0105] The RAR UL grant schedules the PUSCH transmission from the UE. The contents of the RAR UL grant, starting from the MSB and ending with the LSB, are given in Table IV.2-1.

[0106] If the value of the frequency hopping flag is 0, the UE transmits the PUSCH without frequency hopping; otherwise, the UE transmits the PUSCH with frequency hopping.

[0107] The UE determines the MCS for the PUSCH transmission from the first 16 indices of the applicable MCS index table for the PUSCH.

[0108] The TPC command value Ĥ is used to set the power of the PUSCH transmission as described in clause 7.1.1 of TS 38.213 and is interpreted according to Table IV.2-2 below and / or Table II-1 above.

[0109] The CSI request field is reserved.

[0110] The ChannelAccess-CPext field indicates the channel access type and CP extension for operation with shared spectrum channel access. [Table 4] [Table 5]

[0111] Unless the UE is configured with an SCS, the UE receives subsequent PDSCHs using the same SCS as the PDSCH reception that provided the RAR message.

[0112] If the UE does not detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the window, or if the UE detects DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the window and the LSB of the SFN field of DCI format 1_0 is not the same as the corresponding LSB of the SFN, if included and applicable, and if the UE transmits the PRACH or if the UE does not correctly receive the corresponding transport block within the window, the UE procedures shall be as described in TS 38.321.

[0113] IV.2A Random Access Response - Type 2 Random Access Procedure In response to a PRACH and PUSCH transmission, or a PRACH-only transmission if the PRACH preamble is mapped to a valid PUSCH opportunity, the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding MsgB-RNTI during a window controlled by higher layers. The window starts with the first symbol of the earliest CORESET for which the UE is configured to receive a PDCCH for the Type1-PDCCH CSS set, as defined in Section 10.1, i.e., at least one symbol after the last symbol of the PUSCH opportunity corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for the Type1-PDCCH CSS set. The length of the window in number of slots, based on the SCS for the Type1-PDCCH CSS set, is given by msgB-ResponseWindow.

[0114] In response to a PRACH transmission, if the PRACH preamble is not mapped to a valid PUSCH case, the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding MsgB-RNTI during a window controlled by higher layers. The window starts with the first symbol of the earliest CORESET for which the UE is configured to receive a PDCCH for the Type1-PDCCH CSS set, as defined in Section 10.1, i.e., at least one symbol after the last symbol of the PRACH opportunity corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for the Type1-PDCCH CSS set. The length of the window in number of slots, based on the SCS for the Type1-PDCCH CSS set, is given by msgB-ResponseWindow.

[0115] If the UE detects DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI, and if applicable, the LSB of the SFN field in DCI format 1_0 is the same as the corresponding LSB of the SFN at which the UE transmitted the PRACH, and if the UE receives a transport block in the corresponding PDSCH within the window, the UE shall pass that transport block to higher layers.

[0116] The upper layer indicates to the physical layer: uplink acknowledgement, if the RAR message is for fallbackRAR and the random access preamble identity (RAPID) associated with the PRACH transmission is identified and when the UE detects the RAR uplink acknowledgement, the UE procedures continue as described in clauses IV.2, IV.3 and IV.4, or If the RAR message is for successRAR, sending a PUCCH with HARQ-ACK information with an ACK value, where: The PUCCH resource for PUCCH transmission is indicated by the 4-bit PUCCH resource indicator field in successRAR from the PUCCH resource set provided by pucch-ResourceCommon. The slot for PUCCH transmission is indicated by the 3-bit PDSCH-to-HARQ_feedback timing indicator field in successRAR with value k from {1,2,3,4,5,6,7,8} and duration T slot With reference to the slot for PUCCH transmission with The UE determines whether the first symbol of the PUCCH transmission is N symbols later than the last symbol of the PDSCH reception. T,1 It is not expected to occur in less than +5 msec. T,1 is the PDSCH processing time for UE processing capability 1 For operation with shared spectrum channel access, the channel access type and CP extension for PUCCH transmission are indicated by the ChannelAccess-CPext field in the successRAR. The PUCCH transmission has the same spatial domain transmit filter and is within the same active UL BWP as the previous PUSCH transmission.

[0117] If the UE detects DCI format 1_0 within a window with a CRC scrambled by C-RNTI and a transport block in the corresponding PDSCH, the UE shall transmit a PUCCH with HARQ-ACK information with an ACK value if the UE correctly detects the transport block, or with a NACK value if the UE incorrectly detects the transport block and the time alignment timer is running.

[0118] If the UE detects DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI and receives a transport block within the window on the corresponding PDSCH, the UE may assume the same DM-RS antenna port quasi-co-location properties as for the SS / PBCH block that the UE used for PRACH association as described in Section IV.1, regardless of whether the UE is provided with a TCI-State for the CORESET in which the UE receives a PDCCH with DCI format 1_0.

[0119] The UE does not expect to be instructed to transmit the PUCCH with the HARQ-ACK information at a time prior to the time at which the UE applies the TA command provided by the transport block.

[0120] If the UE does not detect DCI format 1.0 with a CRC scrambled by the corresponding MsgB-RNTI within a window, or if the UE detects DCI format 1.0 with a CRC scrambled by the corresponding MsgB-RNTI within a window and the LSB of the SFN field in DCI format 1.0, if applicable, is not the same as the corresponding LSB of the SFN at which the UE transmitted the PRACH, or if the UE does not correctly receive a transport block in the corresponding PDSCH within a window, or if the upper layer does not identify a RAPID associated with the PRACH transmission from the UE, the upper layer can instruct the physical layer to transmit only the PRACH according to a Type 1 random access procedure, or to transmit both the PRACH and PUSCH according to a Type 2 random access procedure. If requested by the upper layer, the UE shall transmit the PRACH and PUSCH at the latest N symbols after the last symbol of the window or the last symbol of the PDSCH reception. T,1 + 0.75 msec, where N T,1 is the duration of N1 symbols, corresponding to the PDSCH processing time for UE processing capability 1 when an additional PDSCH DM-RS is configured. For μ=0, the UE 1,0Assume =14.

[0121] Unless the UE is configured with an SCS, the UE receives subsequent PDSCHs using the same SCS as for the PDSCH reception that provides the RAR message.

[0122] If the UE does not detect DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI within the window, or if it detects DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI within the window and, if applicable, the LSB of the SFN field in DCI format 1_0 is not the same as the corresponding LSB of the SFN with which the UE transmitted the PRACH, or if the UE does not correctly receive the corresponding transport block within the window, the UE procedures are as described in TS 38.321.

[0123] IV.3 RAR UL Approved Scheduled PUSCH The active UL BWP for PUSCH transmissions scheduled by the RAR UL grant is indicated by higher layers.

[0124] If useInterlace-PUCCH-PUSCH is not provided by BWP-UplinkCommon and BWP-UplinkDedicated, to determine the frequency domain resource allocation for PUSCH transmission within the active UL BWP: If the active UL BWP and the initial UL BWP have the same SCS and the same CP length, and the active UL BWP contains all the RBs of the initial UL BWP, or if the active UL BWP is the initial UL BWP, the initial UL BWP is used. Otherwise, the RB numbering starts from the first RB in the active UL BWP, and the maximum number of RBs for frequency domain resource allocation is equal to the number of RBs in the initial UL BWP.

[0125] Frequency domain resource allocation is according to uplink resource allocation type 1. The initial UL BWP size is N BWP size For the case where there are RBs, the UE processes the frequency domain resource allocation field as follows: N BWP size If ≦180, or N BWP size For operation with shared spectrum channel access if ≤ 90, Frequency domain resource allocation field

number

number

number

[0126] If useInterlace-PUCCH-PUSCH is provided by BWP-UplinkCommon or BWP-UplinkDedicated, the frequency domain resource allocation is according to uplink resource allocation type 2. The UE processes the frequency domain resource allocation field as follows: Truncate the frequency domain resource allocation field to X=6 LSBs if μ=0 or X=5 LSBs if μ=1 For interlace allocation of PUSCH transmission, the X MSBs of the truncated frequency domain resource allocation field for the active UL BWP are interpreted in the same way as for the X MSBs of the frequency domain resource allocation field in DCI format 0_0. For RB set allocation for PUSCH transmission, the RB set of the active UL BWP is the RB set of the PRACH transmission associated with the RAR UL grant.

[0127] The UE decides whether to apply transform pre-coding as described in

[0043] .

[0128] For PUSCH transmissions with frequency hopping scheduled by RAR UL grant, or for Msg3 PUSCH retransmissions, the frequency offset for the second hop is given in Table IV.3-1. [Table 6]

[0129] The SCS for PUSCH transmission is provided by the subcarrierSpacing in BWP-UplinkCommon. The UE transmits PRACH and PUSCH on the same uplink carrier of the same serving cell.

[0130] For PUSCHs scheduled by RAR UL grants, the UE shall transmit the transport blocks in the corresponding RAR messages using redundancy version number 0. If TC-RNTI is provided by higher layers, scrambling initialization for PUSCHs corresponding to RAR UL grants in subclause IV.2 shall be by TC-RNTI. Otherwise, scrambling initialization for PUSCHs corresponding to RAR UL grants in subclause IV.2 shall be by C-RNTI. Msg3 PUSCH retransmissions of transport blocks shall be scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI, if any, provided in the corresponding RAR message. The UE always transmits PUSCHs scheduled by RAR UL grants without repetition.

[0131] With reference to the slot for PUSCH transmission scheduled by the RAR UL grant, if the UE receives a PDSCH with an RAR message that ends in the slot for the corresponding PRACH transmission from the UE, the UE transmits the PUSCH within the slot.

[0132] The UE determines whether the minimum time between the last symbol of a PDSCH reception carrying a RAR message with a RAR UL grant and the first symbol of the corresponding PUSCH transmission scheduled by that RAR UL grant is N T,1 +N T,2 +0.5 msec, where N T,1 is the duration of N1 symbols, corresponding to the PDSCH processing time for UE processing capability 1 when an additional PDSCH DM-RS is configured, and N T,2 is the duration of N symbols corresponding to the PUSCH preparation time for UE processing capability 1, and to determine the minimum time, the UE considers N and N to correspond to the smaller of the SCS configurations for the PDSCH and PUSCH. For example, for μ=0, the UE considers N 1,0 =14.

[0133] IV.4 PDSCH with UE contention resolution identity When the UE is not provided with a C-RNTI in response to a PUSCH transmission scheduled by an RAR UL grant, the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding TC-RNTI scheduling that schedules a PDSCH including the UE contention resolution identity. In response to a PDSCH reception with the UE contention resolution identity, the UE transmits HARQ-ACK information on the PUCCH. The PUCCH transmission is within the same active UL BWP as the PUSCH transmission. The minimum time between the last symbol of the PDSCH reception and the first symbol of the corresponding PUCCH transmission with HARQ-ACK information is equal to msec. is the duration in symbols, which corresponds to the PDSCH processing time for UE processing capability 1 when an additional PDSCH DM-RS is configured. For , the UE assumes that

[0134] When detecting a DCI format in response to a PUSCH transmission scheduled by a RAR UL grant or a corresponding PUSCH retransmission scheduled with DCI format 0_0 with a CRC scrambled by the TC-RNTI provided in the corresponding RAR message, the UE may assume that the PDCCH carrying the DCI format has the same DM-RS antenna port quasi-co-location properties as for the SS / PBCH block used by the UE for PRACH association, as described in Section IV.1, regardless of whether the UE provides a TCI-State for the CORESET in which the UE receives a PDCCH with the DCI format.

[0135] V. System and Implementation 9-10 illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments.

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

[0137] The network 900 includes a UE 902, which is any mobile or non-mobile computing device designed to communicate with a RAN 904 over a wireless connection. The UE 902 is communicatively coupled to the RAN 904 by a Uu interface, which may be applicable to both LTE and NR systems. Examples of a UE 902 include, but are not limited to, a smartphone, a tablet computer, a wearable computer, a desktop computer, a laptop computer, an in-vehicle infotainment system, an in-vehicle entertainment system, an instrument cluster, a head-up display (HUD) device, an on-board diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine-type communication device, a machine-to-machine (M2M), a device-to-device (D2D), a machine-type communication (MTC) device, an Internet of Things (IoT) device, etc. The network 900 may include multiple UEs 902 directly coupled to each other via D2D, ProSe, PC5, and / or sidelink interfaces. These UEs 902 may be M2M / D2D / MTC / IoT devices and / or vehicular systems communicating using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, and PSFCH. The UEs 902 may be the same as or similar to the UEs previously described with respect to any of the figures previously described or described below.

[0138] In some embodiments, the UE 902 may additionally communicate with the AP 906 via an over-the-air (OTA) connection. The AP 906 manages a WLAN connection, which may serve to offload some or all network traffic from the RAN 904. The connection between the UE 902 and the AP 906 may be consistent with the IEEE 802.11 protocol. Additionally, the UE 902, the RAN 904, and the AP 906 may utilize cellular-WLAN aggregation / integration (e.g., LWA / LWIP). Cellular-WLAN integration may involve the UE 902 being configured by the RAN 904 to utilize both cellular radio resources and WLAN resources.

[0139] The RAN 904 includes one or more access network nodes (ANs) 908. The ANs 908 terminate the air interface for the UE 902 by providing access stratum protocols, including RRC, PDCP, RLC, MAC, and PHY / L1 protocols. In this manner, the ANs 908 enable data / voice connectivity between the CN 920 and the UE 902. The ANs 908 may be macrocell base stations or low-power base stations for providing femtocells, picocells, or other similar cells with smaller coverage areas, lower user capacities, or larger bandwidths compared to macrocells, or some combination thereof. In these implementations, the ANs 908 may be referred to as BSs, gNBs, RAN nodes, eNBs, ng-eNBs, NodeBs, RSUs, TRxPs, etc.

[0140] One example implementation is a "CU / DU split" architecture, in which the AN 908 is embodied as a gNB-Central Unit (CU) communicatively coupled to one or more gNB-Distributed Units (DUs), each of which may be communicatively coupled to one or more Radio Units (RUs) (also referred to as RRHs, RRUs, etc.) (see, for example, 3GPP TS38.401 v16.1.0(2020-03)). In some implementations, the one or more RUs may be individual RSUs. In some implementations, the CU / DU split may include a ng-eNB-CU and one or more ng-eNB-DUs instead of or in addition to a gNB-CU and gNB-DU, respectively. The AN 908 used as a CU 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 including, for example, a virtual baseband unit (BBU) or BBU pool, a cloud RAN (CRAN), a radio equipment controller (REC), a radio cloud center (RCC), a centralized RAN (C-RAN), a virtualized RAN (vRAN), and / or others (although these terms may refer to different implementation concepts). Any other type of architecture, arrangement, and / or configuration may be used.

[0141] Multiple ANs may be coupled to each other via an X2 interface (if the RAN 904 is an LTE RAN or an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 910) or an Xn interface (if the RAN 904 is an NG-RAN 914). The X2 / Xn interface may be separated into a control / user plane interface in some embodiments, but may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0142] The ANs of the RAN 904 may each manage one or more cells, cell groups, component carriers, etc. to provide an air interface for network access to the UE 902. The UE 902 may simultaneously connect to multiple cells provided by the same or different ANs 908 of the RAN 904. For example, the UE 902 and the RAN 904 may use carrier aggregation to enable the UE 902 to connect to multiple component carriers, each corresponding to a Pcell or Scell. In a dual connectivity scenario, the first AN 908 may be a master node providing an MCG, and the second AN 908 may be a secondary node providing an SCG. The first and second ANs 908 may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0143] The RAN 904 can provide the air interface through a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, a node can use LAA, eLAA, and / or feLAA mechanisms based on CA techniques with a PCell / Scell. Before accessing the unlicensed spectrum, the node may perform medium / carrier sensing operations, for example, based on a listen-before-talk (LBT) protocol.

[0144] In a V2X scenario, the UE 902 or AN 908 may be or function as a roadside unit (RSU). A roadside unit may refer to any transportation infrastructure entity used for V2X communications. The RSU may be implemented in an appropriate AN or a stationary (or relatively static) UE. An RSU implemented within or by a UE may be referred to as a "UE-type RSU," an "eNB-type RSU" for an eNB, a "gNB-type RSU" for a gNB, etc. In one example, an RSU is a computing device coupled with radio frequency circuits located at the roadside to provide connectivity support for passing vehicular UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicular and pedestrian traffic. The RSU can provide very low latency communications necessary for high-speed events such as collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing a wired connection (e.g., Ethernet) to a traffic signal controller or backhaul network.

[0145] In some embodiments, the RAN 904 may be an E-UTRAN 910 with one or more eNBs 912. The E-UTRAN 910 provides an LTE air interface (Uu) with the following characteristics: SCS 15 kHz; CP-OFDM waveform for DL ​​and SC-FDMA waveform for UL; turbo codes for data and TBCC for control. The LTE air interface may rely on CSI-RS for CSI collection and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and CRS for cell search and initial collection, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate in bands below 6 GHz.

[0146] In some embodiments, the RAN 904 may be a Next Generation (NG)-RAN 914 having one or more gNBs 916 and / or one or more ng-eNBs 918. The gNBs 916 connect to the 5G-capable UEs 902 using a 5G NR interface. The gNBs 916 connect to the 5G-enabled UEs 902 through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNBs 918 also connect to the 5GC 940 through an NG interface, but may connect to the UEs 902 through a Uu interface. The gNBs 916 and ng-eNBs 918 may connect to each other through an Xn interface.

[0147] In some embodiments, the NG interface may be divided into two parts: an NG User Plane (NG-U) interface (e.g., N3 interface), which carries traffic data between nodes in the NG-RAN 914 and the UPF 948, and an NG Control Plane (NG-C) interface (e.g., N2 interface), which is a signaling interface between nodes in the NG-RAN 914 and the AMF 944.

[0148] The NG-RAN 914 may provide a 5G-NR air interface (sometimes referred to as the Uu interface) with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface may rely on CSI-RS and PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for phase tracking for PDSCH, and tracking reference signals for time tracking. The 5G-NR air interface may operate on the FR1 band, which includes bands below 6 GHz, or the FR2 band, which includes bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB, which is a region of the downlink resource grid that includes the PSS / SSS / PBCH.

[0149] The 5G-NR air interface can utilize BWPs for various purposes. For example, BWPs can be used for dynamic SCS adaptation. For example, a UE 902 can be configured with multiple BWPs, each with a different SCS. When a BWP change is indicated to the UE 902, the SCS for transmission also changes. Another example use case for BWPs relates to power conservation. In particular, multiple BWPs can be configured for a UE 902 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP with a small number of PRBs can be used for data transmissions with a low traffic load, allowing power savings at the UE 902 and potentially at the gNB 916. A BWP with a larger number of PRBs can be used for scenarios with a higher traffic load.

[0150] The RAN 904 is communicatively coupled to a CN 920, which includes network elements and / or network functions (NFs), to provide various functions to support data and communication services to customers / subscribers (e.g., UEs 902). The components of the CN 920 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 920 onto physical compute / storage resources in servers, switches, etc. A logical instantiation of the CN 920 may be referred to as a network slice, and a logical instantiation of a portion of the CN 920 may be referred to as a network sub-slice.

[0151] The CN 920 may be an LTE CN 922 (also referred to as an Evolved Packet Core (EPC) 922). The EPC 922 may include an MME 924, an SGW 926, an SGSN 928, an HSS 930, a PGW 932, and a PCRF 934 coupled to each other through interfaces (or "reference points") as shown. The NFs in the EPC 922 are briefly introduced as follows.

[0152] The MME 924 implements mobility management functionality that tracks the current location of the UE 902 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0153] The SGW 926 terminates the S1 interface towards the RAN 910 and routes data packets between the RAN 910 and the EPC 922. The SGW 926 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0154] The SGSN 928 tracks the location of the UE 902 and performs security functions and access control. The SGSN 928 also performs signaling between EPC nodes for mobility between different RAT networks; PDN and S-GW selection designated by the MME 924; MME 924 selection for handover, etc. The S3 reference point between the MME 924 and the SGSN 928 allows the exchange of user and bearer information for inter-3GPP access network mobility in idle / active state.

[0155] The HSS 930 includes a database for network users, containing subscriber-related information to support network entities handling communication sessions. The HSS 930 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS 930 and the MME 924 may enable the transfer of subscription and authentication data to authenticate / authorize user access to the EPC 920.

[0156] The PGW 932 may terminate the SGi interface toward a data network (DN) 936, which may include an application (app) / content server 938. The PGW 932 routes data packets between the EPC 922 and the data network 936. The PGW 932 is communicatively coupled to the SGW 926 by an S5 reference point to facilitate user plane tunnels and tunnel management. The PGW 932 may further include nodes for policy enforcement and charging data collection (e.g., PCEF). Furthermore, the SGi reference point may communicatively couple the PGW 932 with the same or a different data network 936. The PGW 932 may be communicatively coupled to the PCRF 934 via a Gx reference point.

[0157] The PCRF 934 is the policy and charging control element of the EPC 922. The PCRF 934 is communicatively coupled to the app / content server 938 to determine the appropriate QoS and charging parameters for a service flow. The PCRF 932 also provisions the relevant rules in the PCEF (via the Gx reference point) with the appropriate TFT and QCI.

[0158] The CN 920 may be a 5GC 940 including an AUSF 942, an AMF 944, an SMF 946, a UPF 948, an NSSF 950, an NEF 952, an NRF 954, a PCF 956, a UDM 958, and an AF 960 coupled to each other through various interfaces as shown. The NFs in the 5GC 940 are briefly introduced as follows.

[0159] The AUSF 942 stores data and handles authentication-related functions for authentication of the UE 902. The AUSF 942 can facilitate a common authentication framework for various access types.

[0160] The AMF 944 allows other functions of the 5GC 940 to communicate with the UE 902 and the RAN 904 and subscribe to notifications regarding mobility events related to the UE 902. The AMF 944 is also responsible for registration management (e.g., for registering the UE 902), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 944 provides transport for SM messages between the UE 902 and the SMF 946 and acts as a transparent proxy for routing SM messages. The AMF 944 also provides transport for SMS messages between the UE 902 and the SMSF. The AMF 944 interacts with the AUSF 942 and the UE 902 to perform various security anchor and context management functions. Additionally, the AMF 944 is the termination point of the RAN-CP interface, which includes the N2 reference point between the RAN 904 and the AMF 944. The AMF 944 is also the termination point for NAS (N1) signaling and performs NAS encryption and integrity protection.

[0161] The AMF 944 also supports NAS signaling with the UE 902 through the N3IWF interface. The N3IWF provides access to untrusted entities. The N3IWF may be the termination point for the N2 interface between the (R)AN 904 and the AMF 944 for the control plane, and the termination point for the N3 reference point between the (R)AN 914 and the AMF 948 for the user plane. Thus, the AMF 944 handles N2 signaling from the SMF 946 and the AMF 944 for PDU sessions and QoS, encapsulates / decapsulates packets for IPSec and N3 tunnels, marks N3 user plane packets in the uplink, and enforces QoS corresponding to N3 packet markings, taking into account QoS requirements associated with such markings received through the N2. The N3IWF may also relay UL and DL control plane NAS signaling between the UE 902 and the AMF 944 and relay uplink and downlink user plane packets between the UE 902 and the UPF 948 via the N1 reference point between the UE 902 and the AMF 944. The N3IWF also provides a mechanism for IPsec tunnel establishment with the UE 902. The AMF 944 may represent a Namf service-based interface and may be the termination point of the N14 reference point between two AMFs 944 and the N17 reference point between the AMF 944 and the 5G-EIR (not shown in FIG. 9).

[0162] The SMF 946 is responsible for SM (e.g., session establishment, tunnel management between the UPF 948 and the AN 908); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of traffic steering in the UPF 948 to route traffic to the correct destination; termination of the interface to the policy control function; control of policy enforcement, charging, and parts of QoS; lawful interception (for SM events and the interface to the LI system); termination of the SM portion of NAS messages; downlink data notification; initiation of specific SM information sent through the N2 to the AN 908 via the AMF 944; and determination of the SSC mode for the session. SM refers to the management of PDU sessions, and PDU sessions or "sessions" refer to the PDU connectivity services that provide or enable the exchange of PDUs between the UE 902 and the DN 936.

[0163] The UPF 948 serves as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 936, and a branching point for supporting multi-homed PDU sessions. The UPF 948 also performs packet routing and forwarding, packet inspection, enforces the user plane portion of policy rules, lawfully intercepts packets (UP collection), performs traffic usage reporting, performs QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic validation (e.g., SDF-to-QoS flow mapping), performs transport-level packet marking in the uplink and downlink, downlink packet buffering, and downlink data notification triggering. The UPF 948 may also include an uplink classifier to support routing traffic flows to the data network.

[0164] The NSSF 950 selects a set of network slice instances to serve the UE 902. The NSSF 950 also determines the allowable NSSAIs and their mapping to the subscribed S-NSSAIs, if necessary. The NSSF 950 also determines the AMF set, or list of candidate AMFs 944, to be used to serve the UE 902 based on appropriate configuration and possibly by querying the NRF 954. The selection of a set of network slice instances for the UE 902 may be triggered by the AMF 944 to which the UE 902 is registered by interacting with the NSSF 950; this may lead to a change in the AMF 944. The NSSF 950 interacts with the AMF 944 via the N22 reference point; it can communicate with another NSSF in the visited network via the N31 reference point (not shown).

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

[0166] The NRF 954 supports a service discovery function, receiving NF discovery requests from NF instances and providing information about discovered NF instances to the requesting NF instance. The NRF 954 also maintains information about available NF instances and their supported services. The NRF 954 also supports a service discovery function, in which the NRF 954 receives NF discovery requests from NF instances or SCPs (not shown) and provides information about discovered NF instances to the NF instances or SCPs.

[0167] The PCF 956 provides policy rules to control plane functions to enforce the control plane functions and may also support a unified policy framework that governs network behavior. The PCF 956 may also implement a front end to access subscription information related to policy decisions within the UDRs of the UDM 958. In addition to communicating with functions through reference points as shown, the PCF 956 also exhibits an NPCF service-based interface.

[0168] The UDM 958 handles subscription-related information to support network entities in handling communication sessions and stores subscription data for the UE 902. For example, the subscription data may be communicated via the N8 reference point between the UDM 958 and the AMF 944. The UDM 958 may include two parts: an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 958 and the PCF 956, and / or structured data and application data for publication to the NEF 952 (including PFDs for application discovery and application request information for multiple UEs 902). The Nudr service-based interface, represented by the UDR 221, allows the UDM 958, the PCF 956, and the NEF 952 to access specific sets of stored data as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of associated data changes in the UDR. The UDM may contain a UDM-FE responsible for credential processing, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, the UDM 958 may expose a Nudm service-based interface.

[0169] The AF 960 provides application influence over traffic routing, provides access to the NEF 952, and interacts with the policy framework for policy control. The AF 960 may influence UPF 948 (re)selection and traffic routing. Based on operator deployment, if the AF 960 is considered a trusted entity, the network operator may allow the AF 960 to interact directly with associated NFs. Additionally, the AF 960 may be used for edge computing implementations.

[0170] The 5GC 940 may enable edge computing by selecting an operator / third-party service that is geographically close to the point where the UE 902 is attached to the network. This may reduce latency and load on the network. In an edge computing implementation, the 5GC 940 may select a UPF 948 that is close to the UE 902 and perform traffic steering from the UPF 948 to the DN 936 over the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 960, which allows the AF 960 to influence UPF (re)selection and traffic routing.

[0171] The data network 936 may represent various network operator services, Internet access, or third-party services that may be provided by one or more servers, including, for example, an application (app) / content server 938. The DN 936 may be, for example, a public or private PDN external to the operator, or a packet data network within the operator for the provision of IMS services. In this embodiment, the server 938 may be coupled to the IMS via an S-CSCF or an I-CSCF. In some implementations, the DN 936 may represent one or more local area DNs (LADNs), which are DNs 936 (or DN names (DNNs)) accessible by the UE 902 within one or more specific areas. Outside of these specific areas, the UE 902 cannot access the LADN / DN 936.

[0172] Additionally or alternatively, DN 936 may be an edge DN 936, which is a (local) data network that supports an architecture for enabling edge applications. In these embodiments, app server 938 may represent a physical hardware system / device that provides app server functionality and / or application software residing in the cloud or on an edge compute node that performs server functionality. In some embodiments, app / content server 938 provides an edge hosting environment that provides the support needed for the execution of edge application servers.

[0173] In some embodiments, the 5GS may use one or more edge computing nodes to provide interfacing and offload processing of wireless communication traffic. In these embodiments, the edge computing node may be included in one or more RANs 910, 914 or may be co-located with one or more RANs 910, 914. For example, the edge computing node may provide connectivity between the RAN 914 and the UPF 948 in the 5GC 940. The edge computing node may use one or more NFV instances instantiated on a virtualization infrastructure within the edge computing node to handle the wireless connection between the RAN 914 and the UPF 948.

[0174] The 5GC 940 interfaces include reference points and service-based interfaces. The reference points are N1 (between UE 902 and AMF 944), N2 (between RAN 914 and AMF 944), N3 (between RAN 914 and UPF 948), N4 (between SMF 946 and UPF 948), N5 (between PCF 956 and AF 960), N6 (between UPF 948 and DN 936), N7 (between SMF 946 and PCF 956), N8 (between UDM 958 and AMF 944), N9 (between two UPF 948s), N10 (between UDM 958 and SMF 946), N11 (between AMF 944 and SMF 946), N12 (between AUSF 942 and AMF 944), N13 (between AUSF 942 and UDM 958), N14 (between two AMFs 944; not shown), N15 (between a PCF 956 and an AMF 944 in a non-roaming scenario, or between a PCF 956 and an AMF 944 in a visited network in a roaming scenario), N16 (between two SMFs 946; not shown), and N22 (between an AMF 944 and an NSSF 950). Other reference point representations not shown in Figure 9 can also be used. The service-based representation in Figure 9 represents an NF in the control plane that allows other authorized NFs to access a service. The service-based interfaces (SBIs) include Namf (SBI indicated by AMF 944), Nsmf (SBI indicated by SMF 946), Nnef (SBI indicated by NEF 952), Npcf (SBI indicated by PCF 956), Nudm (SBI indicated by UDM 958), Naf (SBI indicated by AF 960), Nnrf (SBI indicated by NRF 954), Nnssf (SBI indicated by NSSF 950), and Nausf (SBI indicated by AUSF 942). Other service-based interfaces (e.g., Nudr, N5g-eir, Nudsf) not shown in FIG. 9 may also be used. In some embodiments, the NEF 952 may provide an interface to an edge compute node 936x that may be used to handle wireless connectivity with the RAN 914.

[0175] As previously mentioned, the system 900 may include an SMSF responsible for SMS subscription checking and verification, and relaying SM messages to / from other entities such as an SMS-GMSC / IWMSC / SMS router to / from the UE 902. The SMS may also interact with the AMF 942 and the UDM 958 for notification procedures that the UE 902 is available for SMS forwarding (e.g., setting a UE unreachable flag, notifying the UDM 958 when the UE 902 is available for SMS).

[0176] 5GS may also include SCPs (or separate instances of such SCPs) supporting indirect communication (see, for example, 3GPP TS 23.501 Section 7.1.1); delegated discovery (see, for example, 3GPP TS 23.501 Section 7.1.1); message forwarding and routing to destination NFs / NF services; communication security (e.g., authorization of NF service consumers to access NF service producer APIs) (see, for example, 3GPP TS 33.501); load balancing, monitoring, overload control, etc.; and discovery and selection functions for UDMs, AUSFs, UDRs, and PCFs (see, for example, 3GPP TS 23.501 Section 6.3) with access to subscription data stored in the UDR based on the UE's SUPI, SUCI, or GPSI. The load balancing, monitoring, and overload control functions provided by the SCPs may be implementation-specific. SCPs may be deployed in a distributed manner. Multiple SCPs can exist in the communication paths between various NF services. SCPs are also not NF instances, but can be deployed in a distributed, redundant, and scalable manner.

[0177] 10 schematically illustrates a wireless network 1000 according to various embodiments. The wireless network 1000 includes a UE 1002 in wireless communication with an AN 1004. Like-named components described may be the same, similar, and / or substantially interchangeable.

[0178] The UE 1002 may be communicatively coupled to the AN 1004 via a connection 1006. The connection 1006 is shown as an air interface for enabling the communicative coupling and may be consistent with a cellular communication protocol such as an LTE protocol or a 5G NR protocol operating at frequencies below 6 GHz, such as mmWave or mmWave.

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

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

[0181] The modem platform 1010 may further include digital baseband circuitry 1016 that can perform one or more layer operations within a network protocol stack that are "below" the layer operations performed by the protocol processing circuitry 1014. These operations may include PHY operations including, for example, one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / descaling, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding, which may include one or more of space-time, space-frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0182] The modem platform 1010 may further include transmit circuitry 1018, receive circuitry 1020, RF circuitry 1022, and an RF front end (RFFE) 1024, which may include or connect to one or more antenna panels 1026. Briefly, the transmit circuitry 1018 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc.; the receive circuitry 1020 may include analog-to-digital converters, mixers, IF components, etc.; the RF circuitry 1022 may include low-noise amplifiers, power amplifiers, power tracking components, etc.; and the RFFE 1024 may include filters (e.g., surface / volume acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the transmit circuitry 1018, receive circuitry 1020, RF circuitry 1022, RFFE 1024, and antenna panel 1026 components (commonly referred to as "transmit / receive components") may be specific to the details of a particular implementation, such as, for example, whether communications are TDM or FDM, mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be located on the same or different chips / modules, etc.

[0183] In some embodiments, the protocol processing circuit 1014 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.

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

[0185] UE transmissions may be established by and through protocol processing circuitry 1014, digital baseband circuitry 1016, transmit circuitry 1018, RF circuitry 1022, RFFE 1024, and antenna panel 1026. In some embodiments, the transmit components of UE 1004 may apply spatial filters to data to be transmitted to form transmit beams that are radiated by antenna elements of antenna panel 1026.

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

[0187] FIG. 11 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some example embodiments. Specifically, FIG. 11 shows a diagrammatic representation of hardware resources 1100, including one or more processors (or processor cores) 1110, one or more memory / storage devices 1120, and one or more communication resources 1130, each of which may be communicatively coupled via a bus 1140 or other interface circuitry. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1102 may run to provide an execution environment for one or more network slices / sub-slices for utilizing the hardware resources 1100.

[0188] Processor 1110 includes, for example, processor 1112 and processor 1114. Processor 1110 includes one or more processor cores and circuitry such as, but not limited to, one or more of: a cache memory, a low dropout voltage regulator (LDO), an interrupt controller, a serial interface, such as SPI, I2C, or general-purpose programmable serial interface circuitry, a real-time clock (RTC), timer counters including interval and watchdog timers, general-purpose I / O, a memory card controller, such as a Secure Digital / Multimedia Card (SD / MMC) or the like, an interface, a Mobile Industrial Processor Interface (MIPI) interface, and a Joint Test Access Group (JTAG) test access port.

[0189] The processor 1110 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, an Acorn RISC machine (ARM) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), one or more digital signal processors (DSPs), such as baseband processors, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a radio frequency integrated circuit (RFIC), one or more microprocessors or controllers, another processor (including those discussed herein), or any suitable combination thereof. In some implementations, the processor circuitry 1110 may include one or more hardware accelerators, which may be a microprocessor, a programmable processing device (e.g., an FPGA, a complex programmable logic device (CPLD), etc.), etc.

[0190] The memory / storage 1120 may include main memory, disk storage, or any suitable combination thereof. The memory / storage 1120 may include any type of volatile, non-volatile, or semi-volatile memory, such as random access memory (RAM), dynamic RAM (DRAM), static RAM (SRAM), synchronous DRAM (SDRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, phase-change RAM (PRAM), resistive memory, such as magnetoresistive random access memory (MRAM), and may incorporate three-dimensional (3D) cross-point (XPOINT) memory from Intel® and Micron®. The memory / storage 1120 may also include persistent storage, which may be any type of temporary and / or persistent memory, including, but not limited to, non-volatile memory, optical, magnetic, and / or solid-state mass storage, etc.

[0191] Communications resources 1130 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 1104 or one or more databases 1106 or other network elements over network 1108. For example, communications resources 1130 may include wired communications components (e.g., for coupling via USB, Ethernet, etc.), cellular communications components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communications components.

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

[0193] VI. Exemplary Procedures In some embodiments, the electronic devices, networks, systems, chips, or components of Figures 9-11 or other figures herein, or portions or implementations thereof, may be configured to perform one or more processes, techniques, or methods, or portions thereof, described herein. One such process is depicted in Figure 12.

[0194] For example, process 1200 may include retrieving transport block size (TBS) and modulation and coding scheme (MCS) information associated with a small data transmission (SDT) for a user equipment (UE) from a memory at 1205. The process may further include encoding a message for transmission to the UE that includes the TBS and MCS information, at 1210. For example, in some embodiments, the UE selects a PRACH preamble from group A or group B to indicate a TBS and / or MCS value for a Msg3 PUSCH or MsgA PUSCH transmission.

[0195] 13 illustrates another process according to various embodiments. In this example, process 1300 includes, at 1305, determining transport block size (TBS) and modulation and coding scheme (MCS) information associated with a small data transmission (SDT) from a user equipment (UE), where the SDT transmission is associated with a four-step random access (RACH) procedure or a two-step RACH procedure. The process further includes, at 1310, encoding a message for transmission to the UE, including the TBS and MCS information. The process further includes, at 1315, encoding an Msg2 random access response (RAR) for transmission to the UE, including an RAR uplink (UL) grant field.

[0196] 14 illustrates another process according to various embodiments. In this example, process 1400 includes, at 1405, receiving a configuration message from a next generation NodeB (gNB) including transport block size (TBS) and modulation and coding scheme (MCS) information associated with a small data transmission (SDT) from the UE, where the SDT transmission is associated with a four-step random access (RACH) procedure or a two-step RACH procedure. The process further includes, at 1410, encoding a message for transmission to the gNB based on the configuration message.

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

[0198] VII. Working Examples Further examples of the embodiments described herein include the following non-limiting implementations: Each of the following non-limiting examples may stand on its own or may be combined in any permutation or combination with one or more of the other examples provided below or throughout this disclosure.

[0199] Example A01 includes a method of wireless communication for a fifth generation (5G) or new radio (NR) system, the method including: configuring, by a gNodeB (gNB), a small data transmission (SDT) in a Message 3 (Msg3) PUSCH using a four-step random access (RACH) procedure and / or a Message A (MsgA) PUSCH using a two-step RACH procedure; and transmitting, by a UE, the Msg3 in the four-step RACH and / or the MsgA PUSCH in the two-step RACH according to the SDT.

[0200] Example A02 includes the method of example A01 and / or some other examples herein, where, for SDT during a four-step and / or two-step RACH procedure, the UE can transmit Msg.3 and / or MsgA PUSCH according to a transport block size (TBS) / modulation and coding scheme (MCS) from a set of TBS / MCS values ​​configured by higher layers via NR remaining minimum system information (RMSI), NR other system information (OSI), or dedicated radio resource control (RRC) signaling. Example A03 includes the method of example A01 and / or any other example herein, wherein the sets of TBS / MCS values ​​may be configured for preamble groups A and B, respectively, and the UE selects a group whose sets of TBS / MCS values ​​can handle Msg3 / MsgA payload sizes.

[0201] Example A04 includes the method of example A03 and / or some other examples herein, wherein for SDT during a 4-step RACH procedure, the RAR UL grant can indicate two or more Msg3 PUSCH frequency domain resource allocations (FDRA) and / or time domain resource allocations (TDRA).

[0202] Example A05 includes the method of example A01 and / or any other example herein, wherein for SDT during a 4-step RACH procedure, the RAR UL grant can indicate a single Msg3 PUSCH FDRA and / or TDRA; the MCS field in the UL grant can be reserved.

[0203] Example A06 includes the method of example A05 and / or some other examples, where the set of MCS values ​​for Msg3 transmission may be configured by higher layers via minimum system information (MSI), residual minimum system information (RMSI), other system information (OSI), and / or dedicated radio resource control (RRC) signaling.

[0204] Example A07 includes the method of example A05 and / or any other example herein, wherein based on the indicated FDRA and TDRA in the RAR UL authorization, the UE can derive a set of TBSs according to a set of MCS values ​​configured by a higher layer associated with the preamble group, and wherein if the payload size is smaller than one smallest TBS (denoted as TBS_A), the UE performs zero padding and selects an MCS from the set of MCS values ​​corresponding to TBS_A for transmission of the Msg3 PUSCH.

[0205] Example A08 includes the method of example A05 and / or some other examples herein, wherein the MCS in the RAR acknowledgement field for SDT in a 4-step RACH procedure may be used to indicate the maximum MCS index, from a set of configured MCS values, that the UE may use for Msg3 PUSCH transmission.

[0206] Example A09 includes the method of example A01 and / or some other examples herein, wherein, for an SDT during a 4-step RACH procedure, the RAR UL acknowledgement may be used to indicate a single Msg3 PUSCH FDRA and TDRA, which corresponds to the maximum resource allocation for Msg3 transmission; if a set of TBSs is available for Msg3 transmission and the payload size is smaller than the single minimum TBS, the UE may use the indicated MCS and a subset of the allocated resources for Msg3 transmission.

[0207] Example A10 includes the methods of Example A01 and / or some other examples herein, where the above embodiments for RAR UL authorization are directly applicable for fallback RAR UL authorization for Msg3 transmission.

[0208] Example A11 includes the method of example A01 and / or some other examples herein, wherein the UE may be configured with two or more DMRS resources for transmission of Msg3 for a 4-step RACH and / or MsgA PUSCH for a 2-step RACH, and wherein the UE may transmit the DMRS in one of the DMRS resources according to the TBS / MCS for Msg3 for the 4-step RACH and / or MsgA PUSCH for the 2-step RACH.

[0209] Example A12 includes the method of example A01 and / or some other examples herein, wherein when the UE transmits DMRS in a first DMRS resource, it can be used to indicate a first TBS / MCS for transmission of Msg3 for a 4-step RACH and / or MsgA PUSCH for a 2-step RACH; and when the UE transmits DMRS in a second DMRS resource, it can be used to indicate a second TBS / MCS for transmission of Msg3 for a 4-step RACH and / or MsgA PUSCH for a 2-step RACH.

[0210] Example A13 includes the method of example A01 and / or some other examples herein, wherein for an SDT during a four-step RACH procedure, a field in a random access response (RAR) may be diverted, or some state in one or more existing fields in the RAR may be reserved and diverted, to indicate a fallback mechanism from the SDT to a legacy four-step RACH procedure.

[0211] Example A14 includes the method of example A01 and / or some other examples herein, wherein after the UE transmits the MsgA PUSCH, the gNB may instruct the UE to fall back to a 4-step RACH with and without SDT.

[0212] Example A15 includes the method of example A14 and / or some other examples herein, wherein one or more fields in the fallback RAR may be repurposed or some state in one or more fields in the fallback RAR may be reserved to indicate a fallback mechanism from SDT using a two-step RACH to a four-step RACH procedure with and without SDT.

[0213] Example A16 includes the method of example A14 and / or some other examples herein, wherein a reserved field "R" in the fallback RAR can be set to "1" to indicate a fallback to a 4-step RACH with SDT.

[0214] Example A17 includes the method of example A14 and / or some other examples herein, wherein some states in one or more fields in the RAR may be reserved to indicate fallback to a four-step RACH procedure with or without SDT.

[0215] Example A18 includes the method of example A01 and / or some other examples herein, where different fallback RARs can be considered, one for non-SDT (e.g., using a legacy fallback RAR) and another for SDT (e.g., introducing a new SDT fallback RAR), and this distinction can be indicated in the subheader for the RAR.

[0216] Example B01 includes a method including a step of performing a Type 1 or Type 2 random access procedure, wherein a message communicated during the Type 1 or Type 2 random access procedure includes a small data transmission (SDT).

[0217] Example B02 includes the method of example B01 and / or any other example herein, where SDT indicates a transport block size (TBS) or a modulation and coding scheme (MCS).

[0218] Example B03 includes the method of Examples B01-B02 and / or any other example herein, further including: transmitting Msg.3 and / or MsgA PUSCH according to a TBS / MCS from a set of TBS / MCS values ​​configured by a higher layer via NR remaining minimum system information (RMSI), NR other system information (OSI), or radio resource control (RRC) signaling.

[0219] Example B03 includes the method of Examples B01-B02 and / or any other examples herein, where the random access response (RAR) uplink (UL) grant indicates two or more Msg3 PUSCH frequency domain resource allocations (FDRAs) and / or time domain resource allocations (TDRAs), and the method further includes: deriving one or more TBSs according to the indicated FDRAs and TDRAs based on the indicated MCS in the RAR UL.

[0220] Example B04 includes the method of example B03 and / or any other example of this specification, further comprising: if the Msg.3 payload size is smaller than one of the derived TBSs for the FDRA and TDRA, performing zero padding to match the derived TBS and selecting the corresponding FDRA and TDRA for Msg3 PUSCH transmission.

[0221] Example B05 includes the method of Examples B01-B02 and / or any other example herein, wherein the RAR UL grant indicates a single Msg3 PUSCH FDRA and TDRA, and the MCS field in the RAR UL grant is reserved, indicating that this field is to be ignored for Msg3 PUSCH transmission.

[0222] Example B06 includes the method of example B05 and / or some other examples herein, wherein the set of MCS values ​​for MSG3 transmission is configured by higher layers via MSI, RMSI, OSI, and / or RRC signaling.

[0223] Example B07 includes the method of example B06 and / or any other example herein, wherein a set of MCS values ​​is configured per preamble group A, per preamble group B, or for both preamble groups A and B.

[0224] Example B08 includes the method of example B07 and / or any other example herein, and further includes: deriving a set of TBSs according to a set of MCS values ​​configured by a higher layer associated with the preamble group based on the indicated FDRA and TDRA in the RAR UL authorization.

[0225] Example B09 includes the method of example B08 and / or any other example herein, further including: if the payload size is less than the smallest TBS (TBS_A), performing zero padding and selecting an MCS from the set of MCS values ​​corresponding to TBS_A for transmission of the Msg3 PUSCH.

[0226] Example B10 includes the method of Examples B01-B09 and / or some other examples herein, wherein the MCS in the RAR grant field for SDT using Type 1 random access procedure indicates the maximum MCS index that can be used for Msg3 PUSCH transmission from a configured set of MCS values.

[0227] Example B11 includes the method of Examples B01 to B10 and / or some other examples herein, wherein for an SDT during a Type 1 random access procedure, the RAR UL grant indicates a single Msg3 PUSCH FDRA and TDRA corresponding to a maximum resource allocation for Msg3 transmission, and the RAR UL grant further indicates a maximum TBS that can be carried by the Msg3 PUSCH, which can be derived according to the indicated FDRA and TDRA resources and MCS.

[0228] Example B12 includes the method of Examples B01-B11 and / or any other example herein, and further includes: if a set of TBSs is available for Msg3 transmission and if the payload size is less than the one smallest TBS, using the indicated MCS and a subset of the allocated resources for Msg3 transmission.

[0229] Example B13 includes the method of example B12 and / or any other example herein, further including: deriving the subset of allocated resources using a set of scaling factors.

[0230] Example B14 includes the method of Examples B01 to B11 and / or any other example herein, and further includes: for an SDT using a Type 2 random access procedure, performing a fallback mechanism to an SDT using a Type 1 random access procedure.

[0231] Example B15 includes the method of example B14 and / or any other example herein, and further includes: using a fallback RAR UL acknowledgement to indicate the MCS and resources to be used for the MSG3 transmission.

[0232] Example B16 includes the method of Example B14 and / or any other example herein, further including: transmitting one or more demodulation reference signals (DMRS) over one or more configured DMRS resources for transmission of Msg3 for a Type 1 random access procedure and / or MsgA PUSCH for a Type 2 random access procedure, the transmission based on the TBS / MCS for Msg3 for a Type 1 random access procedure and / or MsgA PUSCH for a Type 2 random access procedure.

[0233] Example B17 includes the method of Example B14 and / or any other example herein, and further includes: transmitting a first DMRS in a first DMRS resource to indicate a first TBS / MCS for transmitting Msg3 for a Type 1 random access procedure and / or MsgA PUSCH for a Type 2 random access procedure; and transmitting a second DMRS in a second DMRS resource to indicate a second TBS / MCS for transmitting Msg3 for a Type 1 random access procedure and / or MsgA PUSCH for a Type 2 random access procedure.

[0234] Example B17 includes the method of example B16 and / or any other example herein, wherein for SDT using a Type 1 random access procedure, when a CP-OFDM waveform is configured for transmission of Msg3, two or more scrambling IDs are configured for Msg3 transmission by higher layers via RMSI(SIB1), OSI, or RRC signaling.

[0235] Example B18 includes the method of Examples B16-B17 and / or some other examples herein, wherein for an SDT using a Type 2 random access procedure, a one-to-many mapping between MsgA PRACH preambles and PUSCH resource units (PRUs) may be defined.

[0236] Example B18A includes the method of examples B15-B17 and / or any other example herein, where one or more fields in the fallback RAR are repurposed to indicate the fallback mechanism.

[0237] Example B19 includes the method of Examples B15-B18 and / or any other example herein, wherein one or more states (or values) in one or more fields in the fallback RAR are used to indicate a fallback mechanism from SDT using Type 2 random access procedure to Type 1 random access procedure with and without SDT.

[0238] Example B20 includes the method of Examples B15-B18 and / or any other example herein, wherein the reserved field "R" in the fallback RAR is set to "1" to indicate a fallback to a Type 1 random access procedure with an SDT, and the default state or a "0" value indicates a fallback to a Type 1 random access procedure without an SDT.

[0239] Example B21 includes the method of Examples B19-B20 and / or any other example herein, wherein the reserved field "R" in the fallback RAR is set to "1" to indicate fallback to a Type 1 random access procedure without EDT, and the default state or a "0" value indicates fallback to a Type 1 random access procedure with EDT.

[0240] Example B22 includes the method of Examples B01 to B21 and / or some other examples herein, where the method is performed by a user equipment (UE) or a next generation node B (gNB).

[0241] Example X1 is: a memory for storing transport block size (TBS) and modulation and coding scheme (MCS) information related to small data transmission (SDT) from a user equipment (UE); a processing circuit coupled to the memory, the processing circuit comprising: retrieving the TBS and MCS information from the memory; configured to encode a message for transmission to a UE that includes the TBS and MCS information. and a processing circuit. Includes the device.

[0242] Example X2 includes the apparatus of example X1 or any other example herein, wherein the SDT transmission is associated with a four-step random access (RACH) procedure or a two-step RACH procedure.

[0243] Example X3 includes the apparatus of example X2 or any other example herein, wherein the processing circuitry is further configured to encode an Msg2 random access response (RAR) for transmission to the UE that includes an RAR uplink (UL) grant field.

[0244] Example X3 includes the apparatus of example X3 or any other example herein, wherein the RAR UL grant field indicates multiple Msg3 PUSCH frequency domain resource allocations (FDRA) or multiple time domain resource allocations (TDRA).

[0245] Example X5 includes the apparatus of example X3 or any other example herein, wherein the RAR UL acknowledgement field indicates a single Msg3 PUSCH FDRA and a single Msg3 PUSCH TDRA.

[0246] Example X6 includes the apparatus of example X3 or any other example herein, wherein the RAR UL grant field includes a reserved MCS field to indicate that the UE ignores the MCS field for Msg3 PUSCH transmissions.

[0247] Example X7 includes the apparatus of example X3 or any other example herein, wherein the RAR UL grant field includes an MCS field to indicate a maximum MCS index that the UE can use for MSG3 PUSCH transmission from a set of MCS values ​​in the TBS and MCS information.

[0248] Example X8 includes the apparatus of examples X1-X7 or any other example herein, wherein the processing circuitry further selects a PRACH preamble from group A or group B to indicate a TBS or MCS value for transmission of the Msg3 PUSCH or MsgA PUSCH.

[0249] Example X9 includes the apparatus of any of Examples X1 to X8 or any other example herein, where the SDT transmission from the UE is associated with an Msg3 transmission or an MsgA Physical Uplink Shared Channel (PUSCH) transmission.

[0250] Example X10 includes the apparatus of Examples X1 to X9 or any other example herein, wherein the message is encoded for transmission to the UE via New Radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or dedicated radio resource control (RRC) signaling.

[0251] Example X11 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a next generation Node B (gNB) to: determining transport block size (TBS) and modulation and coding scheme (MCS) information associated with a small data transmission (SDT) from a user equipment (UE), the SDT transmission associated with a four-step random access channel (RACH) procedure or a two-step RACH procedure; encoding a message for transmission to a UE including the TBS and MCS information; encoding a Msg2 Random Access Response (RAR) for transmission to the UE, the RAR including an RAR Uplink (UL) grant field;

[0252] Example X12 includes one or more computer-readable media of example X11 or any other example herein, wherein the RAR UL acknowledgement field indicates multiple Msg3 PUSCH frequency domain resource allocations (FDRAs) or multiple time domain resource allocations (TDRAs).

[0253] Example X13 includes one or more computer-readable media of example X11 or any other example herein, wherein the RAR UL acknowledgement field indicates a single Msg3 PUSCH FDRA and a single Msg3 PUSCH TDRA.

[0254] Example X14 includes one or more computer-readable media of example X11 or any other example herein, wherein the RAR UL acknowledgement field includes a reserved MCS field to indicate that the UE should ignore the MCS field for Msg3 PUSCH transmission.

[0255] Example X15 includes one or more computer-readable media of example X11 or any other example herein, wherein the RAR UL grant field includes an MCS field indicating the maximum MCS index that the UE can use for MSG3 PUSCH transmission from the set of MCS values ​​in the TBS and MCS information.

[0256] Example X16 includes one or more computer-readable media of example X11 or any other example herein, wherein the TBS and MCS information includes values ​​configured for preamble group A or preamble group B.

[0257] Example X17 includes one or more computer-readable media of example X11 or any other example of this specification, wherein the message is encoded for transmission to the UE via New Radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or dedicated radio resource control (RRC) signaling.

[0258] Example embodiment X18 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: receiving, from a next generation Node B (gNB), a configuration message including transport block size (TBS) and modulation and coding scheme (MCS) information associated with a small data transmission (SDT) from the UE, the SDT transmission associated with a four-step random access channel (RACH) procedure or a two-step RACH procedure; Encoding a message for transmission to the gNB based on the configuration message.

[0259] Example X19 includes one or more computer-readable media of example X18 or any other example herein, wherein the message is an Msg3 message or an MsgA PUSCH message.

[0260] Example X20 includes one or more computer-readable media of example X18 or any other example herein, wherein the RAR UL authorization field: Multiple Msg3 PUSCH Frequency Domain Resource Allocation (FDRA); or Multiple Time Domain Resource Allocation (TDRA); or A single Msg3 PUSCH FDRA and a single Msg3 PUSCH TDRA are shown.

[0261] Example X21 includes one or more computer-readable media of Example X20 or any other example of this specification, wherein the medium further stores instructions for causing the UE to derive one or more TBSs based on the configuration message and the FDRA or TDRA indicated in the RAR UL authorization field.

[0262] Example X22 includes one or more computer-readable media of example X18 or any other example herein, wherein: The RAR UL acknowledgement field includes a reserved MCS field indicating that the UE should ignore the MCS field for Msg3 PUSCH transmission; or The RAR UL grant field includes an MCS field that indicates the maximum MCS index that the UE can use for MSG3 PUSCH transmission from the set of MCS values ​​in the TBS and MCS information.

[0263] Example X23 includes one or more computer-readable media of Examples X18 to X22 or any other example herein, where the medium further stores instructions for causing the UE to select a PRACH preamble from Group A or Group B to indicate a TBS or MCS value for transmission of an Msg3 PUSCH or an MsgA PUSCH.

[0264] Example Z01 includes an apparatus having means for performing one or more elements of a method described in or related to any of Examples A01-A18, B01-B22, X1-X23, or any other method or process described herein.

[0265] Example Z02 includes one or more non-transitory computer-readable media containing instructions that, when executed by one or more processors of an electronic device, cause one or more elements of a method described in or related to any of Examples A01-A18, B01-B22, X1-X23, or any other method or process described herein.

[0266] Example Z03 includes an apparatus having logic, modules, or circuitry for performing one or more elements of a method described or related to any of examples A01-A18, B01-B22, X1-X23, or any other method or process described herein.

[0267] Example Z04 includes any method, technique, or process, or portion thereof, described in or related to any of Examples A01-A18, B01-B22, and X1-X23.

[0268] Example Z05 includes an apparatus having one or more processors and one or more computer-readable media having instructions that, when executed by the one or more processors, cause the one or more processors to perform a method or portion thereof described in or related to any of Examples A01-A18, B01-B22, X1-X23.

[0269] Example Z06 includes a signal described in any one or a part of Examples A01 to A18, B01 to B22, and X1 to X23.

[0270] Example Z07 includes a datagram, packet, frame, segment, protocol data unit (PDU), or message described in, related to, or otherwise described in any or any portion of Examples A01-A18, B01-B22, X1-X23, or any portion thereof, in this disclosure.

[0271] Example Z08 includes a signal encoded with data described in, related to, or otherwise described in any or any portion of Examples A01-A18, B01-B22, X1-X23, or any portion thereof.

[0272] Example Z09 includes a signal that encodes a datagram, packet, frame, segment, protocol data unit (PDU), or message described in, related to, or otherwise described in any or any portion of examples A01-A18, B01-B22, X1-X23, or any portion thereof, in this disclosure.

[0273] Example Z10 includes an electromagnetic signal carrying computer-readable instructions, the execution of which by one or more processors causes the one or more processors to perform a method, technique, or process described in or related to any one or portions of Examples A01-A18, B01-B22, X1-X23.

[0274] Example Z11 includes a computer program including instructions, the execution of which by a processing element causes the processing element to perform a method, technique, or process described in or related to any one or portions of Examples A01-A18, B01-B22, X1-X23.

[0275] Example Z12 includes signals within a wireless network as shown and described herein.

[0276] Example Z13 includes a method of communicating within a wireless network as shown and described herein.

[0277] Example Z14 includes a system for providing wireless communication as shown and described herein.

[0278] Example Z15 includes an apparatus for providing wireless communication as shown and described herein.

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

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

[0281] The terms "coupled," "communicatively coupled," and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by communication means, including through a wired or other interconnection, through a wireless communication channel or link, etc.

[0282] As used herein, the term "circuitry" refers to, is a part of, or includes hardware components, such as electronic circuits, logic circuits, processors (shared, dedicated, or group) and / or memories (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), digital signal processors (DSPs), etc., configured to provide a described functionality. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least a portion of the described functionality. The term "circuitry" may also refer to a combination of program code with one or more hardware elements (or a combination of circuitry used in an electrical or electronic system) used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

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

[0284] As used herein, the terms "memory" and / or "memory circuitry" refer to one or more hardware devices for storing data, including RAM, MRAM, PRAM, DRAM, and / or SDRAM, core memory, ROM, magnetic disk storage media, optical storage media, flash memory devices, or other machine-readable media for storing data. The term "computer-readable medium" may include, but is not limited to, memory, portable or permanent storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instructions or data.

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

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

[0287] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or may be referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN equipment, RAN node, gateway, server, virtualized VNF, NFVI, and / or others.

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

[0289] As used herein, the terms "appliance," "computer appliance," and the like refer to a computing device or system having program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image implemented by a hypervisor-equipped device dedicated to virtualizing or emulating a computing appliance or otherwise providing specific computing resources. The term "element" refers to a unit that is indivisible at a given level of abstraction and has clearly defined boundaries. An element can be any type of entity, including, for example, one or more devices, systems, controllers, network elements, modules, etc., or combinations thereof. The term "device" refers to a physical entity embedded within or connected to another physical entity in its vicinity, and has the ability to communicate digital information to or from that physical entity. The term "entity" refers to a separate component of an architecture or device, or information transferred as a payload. The term "controller" refers to an element or entity that has the ability to affect a physical entity, such as by changing its state or moving the physical entity.

[0290] The term "cloud computing" or "cloud" refers to a paradigm that enables network access to a scalable, elastic pool of shareable computing resources through on-demand self-service provisioning and management without active user management. Cloud computing provides cloud computing services (or cloud services), which are one or more functions provided through cloud computing and invoked using a defined interface (e.g., API). The term "computing resource" or simply "resource" refers to any physical or virtual component with limited availability within a computer system or network, or the use of such a component. Examples of computing resources include the use / access over a period of time to a server, processor, storage device, memory device, memory space, network, power, input / output (peripheral) devices, mechanical devices, network connections (e.g., channels / links, ports, network sockets, etc.), operating system, virtual machine (VM), software / applications, computer files, etc. "Hardware resources" may refer to computation, storage, and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to computational, storage, and / or network resources provided by a virtualization infrastructure to an application, device, system, etc. The term "network resources" or "communications resources" may refer to resources accessible by a computer device / system over a communications network. The term "system resources" may refer to any type of shared entity for providing services and may include computational and / or network resources. System resources may be thought of as a coherent collection of functions, network data objects, or services accessible through a server, and such system resources may reside on a single host or multiple hosts and be clearly identifiable.As used herein, the term "cloud service provider" (or CSP) refers to an organization that operates typically large-scale "cloud" resources consisting of centralized, regional, and edge data centers (e.g., used in the context of public clouds). In other instances, a CSP may also be referred to as a cloud service operator (CSO). References to "cloud computing" generally refer to computing resources and services provided by a CSP or CSO in remote locations that have at least some increased latency, distance, or constraints compared to edge computing.

[0291] As used herein, the term "data center" refers to a purposefully designed structure intended to house multiple high-performance computing and data storage nodes, such that a large amount of computing, data storage, and network resources reside in a single location. This often requires specialized rack and enclosure systems, appropriate heating, cooling, ventilation, security, fire suppression, and power supply systems. The term may also refer to the computing and data storage nodes in some contexts. Data centers can vary in size between centralized or cloud data centers (e.g., the largest), regional data centers, and edge data centers (e.g., the smallest).

[0292] As used herein, the term "edge computing" refers to the implementation, coordination, and use of computing resources near the "edge" or collection of "edges" of a network. Deploying computing resources at the edge of a network can shorten application and network latency, reduce network backhaul traffic and associated energy consumption, improve service capacity, improve compliance with security or data privacy requirements (especially compared to traditional cloud computing), and improve overall cost of ownership. As used herein, the term "edge compute node" refers to a real-world, logical, or virtualized implementation of a computing element in the form of a device, gateway, bridge, system or subsystem, or component, whether operating in server, client, endpoint, or peer mode, and whether located at the "edge" of the network or at a more distant, connected location within the network. As used herein, references to a "node" are generally interchangeable with "device," "component," and "subsystem," while references to an "edge computing system" or "edge computing network" generally refer to a collection, organization, or distributed architecture of multiple nodes and devices configured to achieve or provide some aspect of a service or resource in an edge computing scenario.

[0293] The term "Internet of Things" or "IoT" refers to a system of interconnected computing devices, mechanical and digital machines capable of transferring data with little or no human interaction and may include technologies such as real-time analytics, machine learning and / or AI, embedded systems, wireless sensor networks, control systems, automation, etc. (e.g., smart home, smart building, and / or smart city technologies). IoT devices are typically low-power devices without heavy computing or storage capabilities. An "edge IoT device" may be any type of IoT device that is deployed at the edge of a network.

[0294] As used herein, the term "cluster" refers to a collection or group of entities as part of an edge computing system(s), in the form of physical entities (e.g., different computing systems, networks, or network groups), logical entities (e.g., applications, functions, security structures, containers), etc. In some locations, a "cluster" is also referred to as a "group" or "domain." Cluster membership may be modified or influenced based on conditions or functions, including from dynamic or property-based membership, from network or system management scenarios, or from various exemplary techniques described below that may add, modify, or remove entities within a cluster. A cluster may also include or be associated with multiple layers, levels, or properties (including variations in security functions and results based on such layers, levels, or properties).

[0295] As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. An "instance" also refers to a concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0296] 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 the data element that contains the contents.

[0297] 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 with and / or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier wave," "radio frequency carrier wave," and / or other similar terms indicating a path or medium over which data is communicated. Furthermore, as used herein, the term "link" refers to a connection between two devices through a RAT for the transmission and reception of information.

[0298] As used herein, the term "wireless technology" refers to technology for wireless transmission and / or reception of electromagnetic radiation for information transfer. The term "radio access technology" or "RAT" refers to technology used for the underlying physical connection to a radio-based communication network. As used herein, the term "communications protocol" (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communication device and / or system to communicate with other devices and / or systems, including instructions for packetizing / depacketizing data, modulating / demodulating signals, implementing a protocol stack, and / or otherwise.

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

[0300] The term "SSB" refers to an SS / PBCH block.

[0301] The term "primary cell" refers to an MCG cell operating on a primary frequency in which a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

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

[0303] The term "secondary cell" refers to a cell that provides additional radio resources above a special cell for a UE configured with CA.

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

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

[0306] The term "serving cell(s)" refers to the set of cells including the serving cell(s) and all secondary cells for a UE that is in RRC_CONNECTED and configured with CA / .

[0307] The term "special cell" refers to a PCell of an MCG or a PSCell of an SCG for DC operation; otherwise, the term "special cell" refers to a Pcell.

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

Claims

1. a memory for storing transport block size (TBS) and modulation and coding scheme (MCS) information related to small data transmission (SDT) from a user equipment (UE); a processing circuit coupled to the memory, the processing circuit comprising: Retrieving the TBS and MCS information from the memory; configured to encode a message for transmission to the UE, the message including the TBS and MCS information. and processing circuitry, the TBS and MCS information includes a first combination of TBS and MCS and a second combination of TBS and MCS, and the apparatus is configured to indicate which combination of TBS and MCS is applied based on at least one of a physical uplink shared channel (PUSCH) resource unit (PRU), a demodulation reference signal (DMRS) resource, or a scrambling indicator. Device.

2. The apparatus of claim 1 , wherein the transmission of the SDT is associated with a four-step random access control (RACH) procedure or a two-step RACH procedure.

3. 3. The apparatus of claim 2, wherein the processing circuitry further encodes a Msg2 Random Access Response (RAR) for transmission to the UE, the Msg2 Random Access Response (RAR) including an RAR Uplink (UL) grant field.

4. The apparatus of claim 3 , wherein the RAR UL grant field indicates multiple Msg3 PUSCH frequency domain resource allocations (FDRA) or multiple time domain resource allocations (TDRA).

5. The apparatus of claim 3 , wherein the RAR UL grant field indicates a single Msg3 PUSCH FDRA and a single Msg3 PUSCH TDRA.

6. 4. The apparatus of claim 3, wherein the RAR UL grant field includes a reserved MCS field, indicating that the UE ignores the MCS field for Msg3 PUSCH transmissions.

7. 4. The apparatus of claim 3, wherein the RAR UL grant field includes an MCS field indicating a maximum MCS index that the UE can use for MSG3 PUSCH transmission from a set of MCS values ​​in the TBS and MCS information.

8. 8. The apparatus of claim 1, wherein the processing circuitry is further configured to select a PRACH preamble from group A or group B to indicate a TBS or MCS value for a Msg3 PUSCH or MsgA PUSCH transmission.

9. The apparatus of claim 1 , wherein the SDT transmission from the UE is associated with a Msg3 or MsgA Physical Uplink Shared Channel (PUSCH) transmission.

10. 10. The apparatus of claim 1, wherein the message is encoded for transmission to a UE via New Radio (NR) Residual Minimum System Information (RMSI), NR Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling.

11. One or more computer-readable storage media storing instructions that, when executed by one or more processors, cause a next generation Node B (gNB) to: determining transport block size (TBS) and modulation and coding scheme (MCS) information associated with a small data transmission (SDT) from a user equipment (UE), the SDT transmission associated with a four-step random access control (RACH) procedure or a two-step RACH procedure; encoding a message for transmission to the UE, the message including the TBS and MCS information; encoding a Msg2 Random Access Response (RAR) for transmission to the UE, the Msg2 Random Access Response (RAR) including a RAR Uplink (UL) grant field; the TBS and MCS information includes a first combination of TBS and MCS and a second combination of TBS and MCS, and the gNB is configured to indicate which combination of TBS and MCS is applied based on at least one of a Physical Uplink Shared Channel (PUSCH) resource unit (PRU), a Demodulation Reference Signal (DMRS) resource, or a scrambling identifier. One or more computer-readable storage media.

12. 12. The one or more computer-readable storage media of claim 11, wherein the RAR UL grant field indicates multiple Msg3 PUSCH frequency domain resource allocations (FDRA) or multiple time domain resource allocations (TDRA).

13. 12. The one or more computer-readable storage media of claim 11, wherein the RAR UL acknowledgement field indicates a single Msg3 PUSCH FDRA and a single Msg3 PUSCH TDRA.

14. 12. The one or more computer-readable storage media of claim 11, wherein the RAR UL grant field includes a reserved MCS field, indicating that the UE should ignore the MCS field for Msg3 PUSCH transmissions.

15. 12. The one or more computer-readable storage media of claim 11, wherein the RAR UL grant field includes an MCS field indicating a maximum MCS index that the UE can use for MSG3 PUSCH transmission from a set of MCS values ​​in the TBS and MCS information.

16. 16. The one or more computer-readable storage media of claim 11, wherein the TBS and MCS information includes values ​​configured for preamble group A or preamble group B.

17. 17. The one or more computer-readable storage media of claim 11, wherein the message is encoded for transmission to the UE via New Radio (NR) Residual Minimum System Information (RMSI), NR Other System Information (OSI), or dedicated Radio Resource Control (RRC) signaling.

18. One or more computer-readable storage media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: receiving, from a next generation Node B (gNB), a configuration message including transport block size (TBS) and modulation and coding scheme (MCS) information associated with a small data transmission (SDT) from the UE, the SDT transmission associated with a four-step random access control (RACH) procedure or a two-step RACH procedure; and encoding a message for transmission to the gNB based on the configuration message; the TBS and MCS information includes a first combination of TBS and MCS and a second combination of TBS and MCS, and the UE is configured to determine which combination of TBS and MCS is applied based on at least one of a physical uplink shared channel (PUSCH) resource unit (PRU), a demodulation reference signal (DMRS) resource, or a scrambling identifier. One or more computer-readable storage media.

19. 20. The one or more computer-readable storage media of claim 18, wherein the message is an Msg3 message or an MsgA PUSCH message.

20. The RAR UL Acknowledgment field is: Multiple Msg3 PUSCH Frequency Domain Resource Allocation (FDRA); or Multiple Time Domain Resource Allocation (TDRA); or 1 shows a single Msg3 PUSCH FDRA and a single Msg3 PUSCH TDRA; 20. One or more computer-readable storage media according to claim 18.

21. 21. The one or more computer-readable storage media of claim 20, further storing instructions for causing the UE to derive one or more TBSs based on the configuration message and the FDRA or TDRA indicated in the RAR UL acknowledgement field.

22. the RAR UL grant field includes a reserved MCS field, indicating that the UE should ignore the MCS field for Msg3 PUSCH transmission; or The RAR UL grant field includes an MCS field indicating the maximum MCS index that the UE can use for MSG3 PUSCH transmission from a set of MCS values ​​in the TBS and MCS information.

20. One or more computer-readable storage media according to claim 18.

23. 23. The one or more computer-readable storage media of claim 18, further storing instructions for causing the UE to select a PRACH preamble from Group A or Group B to indicate a TBS or MCS value for a Msg3 PUSCH or a MsgA PUSCH transmission.

Images