System and Method for Mitigating Processing Time of RedCap Devices

Abstract

Various embodiments of this specification provide techniques for reduced-capability (RedCap) user equipment (UE). For example, embodiments relate to relaxed (longer) timeline requirements associated with random access procedures and / or other communications of RedCap UE. The technology can support existing RedCap use cases and extend RedCap UE to new use cases. Other embodiments are described and may be recited in the claims.

Description

Technical Field

[0001] [Cross - Reference to Related Applications] This application claims priority to U.S. Provisional Patent Application No. 63 / 354,643, filed Jun. 22, 2022, and U.S. Provisional Patent Application No. 63 / 483,687, filed Feb. 7, 2023.

[0002] [Technical Field] Various embodiments may generally relate to the field of wireless communication. For example, some embodiments may relate to technologies for reduced capacity user equipment (UE).

Background Art

[0003] The 5th Generation (5G) New Radio (NR) specifications of the 3rd Generation Partnership Project (3GPP (registered trademark)) require support for a variety of sets of vertical markets and use cases, including enhanced mobile broadband (eMBB) and newly introduced ultra - reliable and low - latency communication (URLLC) services. Support for Low Power Wide Area (LPWA) networks and use cases for extremely low - complexity / cost devices targeting ultra - coverage and very long battery life are expected to be served by machine - type communication (MTC) (Category M user equipment (UE)) and narrow - band (NB) Internet of Things (IoT) (Category NB UE) technologies.

[0004] Through the Rel-17 NR Reduced Capacity work item, 3GPP has established a framework to enable reduced-capacity NR devices suitable for a range of use cases, including industrial sensors, video surveillance, and wearable use cases, with requirements related to low UE complexity and in some cases low UE power consumption.

Brief Description of the Drawings

[0005] Embodiments are readily understood by the following detailed description in connection with the accompanying drawings. To facilitate this description, like reference numerals indicate like structural elements. Embodiments are shown by way of example and not as a limitation in the figures of the accompanying drawings.

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Modes for Carrying Out the Invention

[0006] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details such as particular structures, architectures, interfaces, technologies, etc., are described to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art having the benefit of this disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain 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 the purposes of this document, the term "A or B" means (A), (B), or (A and B).

[0007] Embodiments of this specification provide techniques for RedCap UEs that can further reduce the complexity of reduced capacity user equipment (UE). Embodiments can improve the support for previously identified use cases and can also extend RedCap to new ranges of use cases such as smart grids. For example, embodiments can further expand the market for RedCap use cases having relatively low cost, low energy consumption, and low data rate requirements, such as use cases for industrial wireless sensor networks. Aspects of the embodiments may be adopted in 3GPP Rel-18 specifications for enhanced RedCap UEs (eRedCap UEs).

[0008] In existing NR specifications, the PDSCH processing time for PDSCH processing time capability 1, the PUSCH preparation time for PUSCH timing capability 1, and the CSI calculation delay requirement 2 are defined in the following table from 3GPP TS38.214, V17.1.0 (hereinafter, "TS38.214").

[0009] [Table 1]

[0010]

Table 2

[0011]

Table 3

[0012] Relaxing the processing time of the UE can potentially reduce the UE complexity by allowing for a longer time for the processing of the PDSCH, the preparation of the PUSCH, or the execution of CSI measurement and reporting. Various other aspects of the UE are affected by the relaxation of the PDSCH processing time, the PUSCH preparation time, and the CSI calculation delay.

[0013] To relax the timeline, multiple embodiments and examples are provided in the subsequent subsections based on multiplicative scaling by a factor greater than 1 of the minimum UE processing time of the existing processing, but note that similar timeline relaxation can be achieved by other means, such as an appropriate selection of an additive factor for the currently specified minimum UE processing time.

[0014] [Relaxed PDSCH Processing Time (N1)] According to Section 5.3 of TS38.214 in NR, if configured, the assigned HARQ-ACK timing K1 and K offset , and the first uplink symbol of the PUCCH carrying HARQ-ACK information, which is defined by the used PUCCH resource and includes the effect of the timing advance, does not start earlier than symbol L1 (where L1 is the end of the last symbol of the PDSCH carrying the TB that has been acknowledged positively, and after T proc,1 =(N1 + d 1,1 + d2)(2048 + 144)·κ2 -μ ·T C + T ext and is defined as the next uplink symbol having its CP that starts after that), the UE shall provide a valid HARQ-ACK message.

[0015] The complexity of the UE can be reduced by increasing the PDSCH processing time (N1) by a scaling factor c. The value c can be predefined or reportable by UE capabilities. For example, c is equal to 2. Note: The new N1 value after scaling may be directly specified in the specification instead of specifying the value c. Some other parameters may also increase in response to the increase in the PDSCH processing time. The increase in the processing time may only apply when processingType2Enabled in PDSCH-ServingCellConfig is set to disable for the serving cell.

[0016] In one embodiment, the values of d proc,1 and / or d2 in the formula for determining T 1,1 can be increased according to the increase in N1.

[0017] In one option, the values of d proc,1 and / or d2 in the formula for determining T 1,1 can be increased by a scaling factor c0. The value c0 can be predefined or reportable by UE capabilities. Note: The new d after scaling1,1 And / or d2 may be directly specified in the specification instead of specifying the value c0.

[0018] In another option, for the eRedCap UE, the value of N1 may increase, while proc,1 in the formula for determining T, the value of d 1,1 and / or the value of d2 may be the same as that specified in the Rel-15 NR specification.

[0019] In one embodiment, the range of the value of the slot offset (K1) from PDSCH to HARQ feedback can be increased according to the increase of N1.

[0020] In one option, for DCI format 1_1 or 1_2, the range of the value of K1 can be changed from X to Y. In one example, X > 0 and Y is the same as Rel-15, for example, Y = 15. In another example, X = 0 and Y can be increased to 16c1 - 1. In another example, X > 0 and Y can be increased to 16c1 - 1. The value c1 can be predefined or reportable according to UE capabilities.

[0021] In another option, for DCI format 1_1, when license-free operation is supported, the range of the value of K1 may increase from -1 to 16c1 - 1. The value c1 can be predefined or reportable according to UE capabilities.

[0022] Note: The new range of K1 after scaling may be directly specified in the specification instead of specifying the value c1.

[0023] In another option, for DCI format 1_0, the candidate values of K1 may be {c1, 2c1, 3c1, 4c1, 5c1, 6c1, 7c1, 8c1}. The value c1 can be predefined or reportable according to UE capabilities. Note: The new value of K1 may be directly specified in the specification instead of specifying the value c1.

[0024] In another option, for DCI format 1_1 or 1_2, the range of the value of K1 for DCI format 1_1 or 1_2 may not need to be changed for eRedCap UEs. Therefore, whether or not to configure or indicate the value of K1 that causes insufficient PDSCH processing time depends on the implementation of the gNB.

[0025] In another option, for DCI format 1_0, the candidate values of K1 may not need to be changed for eRedCap UEs, for example, it may be {1, 2, 3, 4, 5, 6, 7, 8}. Therefore, whether or not to indicate the value of K1 that causes insufficient PDSCH processing time depends on the implementation of the gNB.

[0026] In another option, for the set of values of the HARQ feedback timing indicator field in successRAR, the candidate values of K1 may be {c1, 2c1, 3c1, 4c1, 5c1, 6c1, 7c1, 8c1}. The value c1 can be pre-defined or can be reported according to UE capabilities. Note: The new value of K1 may be directly specified in the specification instead of specifying the value c1.

[0027] In another option, for the set of values of the HARQ feedback timing indicator field in successRAR, the candidate values of K1 may not need to be changed for eRedCap UEs, for example, it may be {1, 2, 3, 4, 5, 6, 7, 8}. Therefore, whether or not to indicate the value of K1 that causes insufficient PDSCH processing time depends on the implementation of the gNB.

[0028] In one embodiment, the value N3 of the HARQ-ACK multiplexing timeline may increase according to the increase of the value N1.

[0029] In section 9.2.3 of TS38.213, V17.1.0 (hereinafter referred to as "TS38.213") in NR, when the UE determines the first resource for PUCCH transmission having HARQ-ACK information corresponding only to PDSCH reception without the corresponding PDCCH, or detects the first DCI format indicating the first resource for PUCCH transmission having the corresponding HARQ-ACK information within the slot, and later in time, detects the second DCI format indicating the second resource for PUCCH transmission having the corresponding HARQ-ACK information within the slot, the PDCCH reception including the second DCI format is not earlier than N3·(2048 + 144)·κ2 -μ ·T c where κ and T c are defined in clause 4.1 of [4, TS38.211], and μ corresponds to the minimum SCS configuration among the SCS configuration of the PDCCH providing the DCI format and the SCS configuration of the PUCCH). The UE does not expect to multiplex the HARQ-ACK information corresponding to the second DCI format in the PUCCH resource within the slot. If processingType2Enabled of PDSCH-ServingCellConfig is set to enable for the serving cell having the second DCI format and for all serving cells having the corresponding HARQ-ACK information multiplexed in the PUCCH transmission within the slot, N3 = 3 for μ = 0, N3 = 4.5 for μ = 1, N3 = 9 for μ = 2; otherwise, N3 = 8 for μ = 0, N3 = 10 for μ = 1, N3 = 17 for μ = 2, N3 = 20 for μ = 3, N3 = 80 for μ = 5, N3 = 160 for μ = 6.

[0030] In one option, the above value N3 of the HARQ-ACK multiplexing timeline may increase by only the scaling factor c2. The value c2 can be pre-defined or reportable according to UE capabilities. Note: Instead of specifying the value c2, the new value N3 may be directly specified in the specification. For example, for eRedCap, when applicable, N3 = 16 for μ = 0, N3 = 20 for μ = 1, and N3 = 34 for μ = 2.

[0031] In one embodiment, the value N of the HARQ-ACK feedback timeline for SPS PDSCH release can be increased according to the increase of N1.

[0032] In section 10.2 of TS 38.213 in NR, the UE is expected to provide HARQ-ACK information according to the SPS PDSCH release N symbols after the last symbol of the PDCCH that provides the SPS PDSCH release. When processingType2Enabled of PDSCH-ServingCellConfig is set to enable for the serving cell having the PDCCH that provides the SPS PDSCH release, N = 5 for μ = 0, N = 5.5 for μ = 1, and N = 11 for μ = 2; otherwise, N = 10 for μ = 0, N = 12 for μ = 1, N = 22 for μ = 2, N = 25 for μ = 3, N = 100 for μ = 5, N = 200 for μ = 6, where μ corresponds to the minimum SCS configuration among the SCS configuration of the PDCCH that provides the SPS PDSCH release and the SCS configuration of the PUCCH that carries HARQ-ACK information according to the SPS PDSCH release.

[0033] In one option, the above value N of the HARQ-ACK feedback timeline for SPS PDSCH release may increase by only the scaling factor c3. The value c3 can be pre-defined or reportable according to UE capabilities. Note: Instead of specifying the value c3, the new value N may be directly specified in the specification. For example, for eRedCap, when applicable, N3 = 20 for μ = 0, N3 = 24 for μ = 1, and N3 = 44 for μ = 2.

[0034] In the above embodiments, the scaling factors c0, c1, c2, c3 may each be equal to c. Alternatively, the scaling factors c0, c1, c2, c3 may be different from c.

[0035] [Relaxed scheduling delay] According to Section 6.4 of TS38.214 in NR, when configured, the slot offset K2 and K offset , and the start S and length L of the PUSCH allocation indicated by the "Time domain resource assignment" of the scheduling DCI, and including the effect of the timing advance, the first uplink symbol in the PUSCH allocation for the transport block including DM-RS does not start earlier than symbol L2 (where L2 is after the reception of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH) T proc,2 =max((N2 + d 2,1 + d2)(2048 + 144)·κ2 -μ ·T C + T ext + T switch , d 2,2For the next uplink symbol having that CP starting from , the UE is assumed to transmit a transport block. When PDCCH reception includes two PDCCH candidates from two respective search space sets as described in section 10.1 of [6, TS38.213], the PDCCH candidate that ends later in time is used for the purpose of determining the last symbol of the PDCCH carrying the DCI that schedules the PUSCH.

[0036] The complexity of the UE can be reduced by increasing the PUSCH preparation time (N2) by a scaling factor u. The value of u can be pre-defined or reportable by UE capabilities. For example, c is equal to 2. Note: The new N2 value after scaling may be directly specified in the specification instead of specifying the value of u. u may be the same as c. Alternatively, u may be different from c. In response to the increase in the PUSCH preparation time, some other parameters may also increase. The increase in the preparation time may only apply when processingType2Enabled of PUSCH-ServingCellConfig is set to disable for the serving cell.

[0037] In one embodiment, T proc,2 In the formula for determining, d 2,1 and / or the value of d2 can be increased according to the increase in N2.

[0038] In one option, T proc,2 In the formula for determining, d 2,1 and / or the value of d2 can be increased by a scaling factor u0. The value of u0 can be pre-defined or reportable by UE capabilities. Note: The new d 2,1 and / or d2 after scaling may be directly specified in the specification instead of specifying the value of u0.

[0039] In another option, T proc,2 In the formula for determining, the above value d 1,1And / or d2 may not need to be changed for the eRedCap UE. Therefore, meeting the PUSCH preparation time depends on the implementation of the gNB.

[0040] In one embodiment, the range of the value of the scheduling offset (K2) from PDCCH to PUSCH can be increased according to the increase of N2.

[0041] In one option, for DCI format 0_1 or 0_2, the range of the value of K2 can be changed from X to Y. In one example, X > 0 and Y is the same as Rel-15, for example, Y = 31. In another example, X = 0 and Y can be increased to 32u1-1. In another example, X > 0 and Y can be increased to 32u1-1. The value u1 can be pre-defined or reportable according to the UE capability. Note: The new range of K2 after scaling may be directly specified in the specification instead of specifying the value u1.

[0042] In another option, for DCI format 0_1 or 0_2, the range of the value of K2 may not need to be changed for the eRedCap UE. Therefore, whether to configure or indicate the value of K2 that results in insufficient PUSCH preparation time depends on the implementation of the gNB.

[0043] In one embodiment, the range of the value of the scheduling offset (K0) from PDCCH to PDSCH can be increased.

[0044] In one option, for DCI format 1_1 or 1_2, the range of the value of K0 can be changed from X to Y. In one example, X > 0 and Y is the same as Rel-15, for example, Y = 31. In another example, X = 0 and Y can be increased to, for example, 32u2 - 1. In another example, X > 0 and Y can be increased to, for example, 32u2 - 1. The value u2 can be pre-defined or reportable by UE capabilities. Note: The new range of K0 after scaling may be directly specified in the specification instead of specifying the value u2.

[0045] In another option, for DCI format 0_1 or 0_2, the range of the value of K2 may not be changed for eRedCap UEs. Therefore, whether or not to configure or indicate the value of K0 that results in insufficient PDSCH processing time depends on the implementation of the gNB.

[0046] In one embodiment, the maximum number of slots configured as the minimum scheduling offset (K0) / (K2), for example, the parameters maxK0 - SchedulingOffset / maxK2 - SchedulingOffset defined in TS38.331, can be increased.

[0047] In one option, the maximum number of slots configured as the minimum scheduling offset (K0) / (K2) may increase by only the scaling factor u3. The value u3 can be pre-defined or reportable by UE capabilities. Note: The new maximum number of slots configured as the minimum scheduling offset (K0) / (K2) after scaling may be directly specified in the specification instead of specifying the value u3. In another option, the maximum number of slots configured as the minimum scheduling offset (K0) / (K2) may not be changed for eRedCap UEs.

[0048] In one embodiment, the minimum scheduling offset constraint Z in section 5.3.1 of 38.214 μThe applicable delay can be increased.

[0049] In one option, parameter Z μ may only increase by scaling factor u4. The value u4 can be pre-defined or reportable by UE capabilities. Note: The new Z μ range after scaling may be directly specified in the specification instead of specifying the value u4. In another option, parameter Z μ may not be changed for eRedCap UEs.

[0050] In one embodiment, the value j for determining K2 in the default table for PUSCH time-domain resource allocation can be increased according to the increase of N2.

[0051] In section 6.1.2.1.1 of TS38.214, the default TDRA table and the value j are specified. However, the current value of j is too small, and as a result, some rows in the table become non-schedulable. For example, for SCS 1kHz using j = 1, if row 0 in the table is indicated by PDCCH in the first 3 OFDM symbols within a slot, the scheduling delay without considering uplink timing advance is 11 symbols. However, with the increase of N2, for example, for 20 symbols for SCS 15kHz assuming the existing N1 is doubled, the scheduling delay for PUSCH preparation in the UE is insufficient. In short, there are 8 out of 16 rows in the default TDRA table that are not applicable to SCS 15kHz. On the other hand, for SCS 30kHz with a timing advance greater than one OFDM symbol, 11 out of 16 rows in the default TDRA table are not applicable. Therefore, the value j of the default TDRA table should be corrected.

[0052] [Table 4]

[0053]

Table 5

[0054] In another option, the parameter j may be increased by only the scaling factor u5. The value u5 can be pre-defined or can be reported by UE capabilities. Note: The new value j after scaling may be directly specified in the specification instead of specifying the value u5. In another option, the parameter j may not be changed for eRedCap UEs.

[0055] In another option, another parameter Δ j is introduced for eRedCap UEs. Therefore, the parameter j in the current specification can be replaced by j + Δ j The value Δ jIt can be pre-defined, configured by upper layer signaling, or reported according to UE capabilities. For example, Δ j = 1.

[0056] In one embodiment, in addition to the K2 value for the UE to transmit PUSCH scheduled by DCI format 0_0 or RAR with CRC scrambled by TC-RNTI or fallbackRAR, the slot delay value Δ can be increased. The slot delay value Δ is also applied to the determination of the slot carrying the PUCCH for the HARQ-ACK feedback of Msg4 / MsgB.

[0057] In NR, with reference to the slot for PUSCH transmission scheduled by the RAR UL grant, when the UE receives a PDSCH with an RAR message that ends in slot n of the corresponding PRACH transmission from the UE, the UE transmits the PUSCH at slot n + k2 + Δ + 2 μ ·K cell,offset (where k2 and Δ are provided in [6, TS38.214], and K cell,offset is provided by CellSpecific_Koffset, and when not provided, K cell,offset = 0). Further, in NR, when the RAR message is for successRAR, for the transmission of the PUCCH with HARQ-ACK information having an ACK value, the slot for PUCCH transmission, for μ ≤ 3, is a value k from {1, 2, 3, 4, 5, 6, 7, 8}, for μ = 5, is a value k from {7, 8, 12, 16, 20, 24, 28, 32}, and for μ = 6, is a value k from {13, 16, 24, 32, 40, 48, 56, 64}, indicated by the 3-bit HARQ feedback timing indicator field in successRAR, and with reference to the slot for PUCCH transmission having a duration T slot the slot is n + k + Δ + 2 μ ·K cell,offsetdetermined as (where n is the slot for PDSCH reception, Δ is as defined for PUSCH transmission in Table 6.1.2.1.1-5 of [6, TS38.214], μ is the SCS configuration of the active UL BWP, and K cell,offset is provided by CellSpecific_Koffset and, if not provided, K cell,offset = 0). The value of Δ is specified in Table 6.1.2.1.1-5 of TS38.214. An additional slot delay Δ is introduced to account for the MAC processing time of the RAR PDSCH including the UL grant for Msg3 or MsgB PUCCH transmission.

[0058]

Table 6

[0059] In another example, the parameter Δ may be increased by a fixed number, e.g., 1, to account for longer processing times. For example, for eRedCap, if applicable, Δ = 3 for μ = 0, Δ = 4 for μ = 1, and Δ = 5 for μ = 2.

[0060] In another option, another parameter δ is introduced for eRedCap UEs. As a result, the parameter Δ in the current specification can be replaced by Δ+δ. The value of δ may be pre-definable, configurable by a higher layer, or reportable by UE capabilities.

[0061] For the above options, the increased value Δ may be applicable only to some of the rows, for example, the rows for PUSCH mapping type B, or the increased value Δ may be applicable to all rows.

[0062] In another option, the parameter Δ may not need to be changed for eRedCap UE.

[0063] In the above embodiments, the scaling factors u0, u1, u2, u3, u4, u5, u6 may each be equal to u. Alternatively, the scaling factors u0, u1, u2, u3, u4, u5, u6 may be different from u.

[0064] [Random access related timeline] Multiple timelines are defined between different messages in the random access procedure and the associated control signaling transmission. Due to the relaxed PDSCH / PUSCH processing time, the above timelines may need to be relaxed accordingly.

[0065] In one embodiment, the parameter Δ in the determination of the delay between the PDCCH order and the PRACH preamble Delay may increase.

[0066] In section 8.1 of TS38.213 in NR, when the random access procedure is started by a PDCCH order, the UE shall transmit the PRACH in the selected PRACH opportunity as described in [11, TS38.321] if required by the upper layer. For this purpose, the time between the last symbol of the PDCCH order reception and the first symbol of the PRACH transmission shall be N T,2 +Δ BWPSwitching +Δ Delay +T switch milliseconds or more. In FR1, Δ Delay = 0.5 milliseconds, and in FR2, Δ Delay = 0.25 milliseconds.

[0067] In one option, ΔDelay may only increase by the scaling factor r0. The value r0 can be predefined or reported according to UE capabilities. Note: The new Δ after scaling Delay may be directly specified in the specification instead of specifying the value r0. For example, for eRedCap, Δ Delay increases by 1 millisecond. As another option, Δ Delay may not be changed for eRedCap UEs.

[0068] In one embodiment, the additional 0.75 ms delay when the upper layer triggers the retransmission of the PRACH preamble after the RAR window may be increased for eRedCap UEs. This embodiment may be applicable to both two-step RACH and four-step RACH.

[0069] For example, for four-step RACH in section 8.2 of TS38.213 in NR, if the UE does not detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within the window, or if the UE detects DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within the window and the LSB of the SFN field in DCI format 1_0, if it is included and applicable, is not the same as the corresponding LSB of the SFN in which the UE transmitted the PRACH, or if the UE does not correctly receive the transport block in the corresponding PDSCH within the window, or if the upper layer does not identify the RAPID associated with the PRACH transmission from the UE, the upper layer can instruct the physical layer to transmit the PRACH. If requested by the upper layer, the UE is expected to transmit the PRACH no later than N T,1 +0.75 milliseconds later (where N T,1Assume μ corresponding to the minimum SCS configuration among the SCS configurations for the PDCCH carrying DCI format 1_0, the corresponding PDSCH when additional PDSCH DM-RS is configured, and the corresponding PRACH, and it is the duration of N1 symbols corresponding to the PDSCH processing time of UE processing capability 1.)

[0070] In one option, the additional delay may increase by only the scaling factor r1. The value r1 can be pre-defined or reportable according to UE capabilities. Note: The additional delay after scaling may be directly specified in the specification instead of specifying the value r1. For example, for eRedCap, the additional delay increases to 1.5 milliseconds. Alternatively, the additional delay may not be changed for eRedCap UEs.)

[0071] In one embodiment, the additional 0.5 ms delay between the PUCCH associated with the RAR message of successRAR may increase for eRedCap UEs.)

[0072] In section 8.2A of TS 38.213 in NR, when the RAR message is for successRAR, for the transmission of PUCCH with HARQ-ACK information having an ACK value, the UE does not expect the first symbol of the PUCCH transmission to be after the last symbol of the PDSCH reception by a time less than N T,1 + 0.5 milliseconds (where N T,1 is the PDSCH processing time of UE processing capability 1 [6, TS 38.214]).

[0073] In one option, the further delay may increase by a scaling factor r2, e.g., 0.5r2 ms. The value r2 can be pre-defined or reportable by UE capabilities. Note: The further delay after scaling may be directly specified in the specification instead of specifying the value r2. For example, for eRedCap, the further delay increases by 1 millisecond. For example, the further delay may increase to 0.5 + Y ms. In other words, the UE does not expect the first symbol of PUCCH transmission to occur after the last symbol of PDSCH reception by a time less than N T,1 + 0.5 + Y milliseconds. The value Y can be pre-defined, configurable by upper layer signaling, or reportable by UE capabilities. The value Y may be the same as or different from the value X in the following embodiments. Alternatively, the further delay may not be changed for eRedCap UEs.

[0074] In one embodiment, the further 0.5 ms delay between the RAR message and the corresponding PUSCH transmission scheduled by the RAR UL grant may increase for eRedCap UEs.

[0075] In section 8.3 of TS 38.213 in NR, the UE assumes that the minimum time between the last symbol of PDSCH reception carrying the RAR message with the RAR UL grant and the first symbol of the corresponding PUSCH transmission scheduled by the RAR UL grant is N T,1 + N T,2 + 0.5 milliseconds (where N T,1 corresponds to the duration of N1 symbols of the UE processing capability 1 PDSCH processing time when additional PDSCH DM-RS is configured, and N T,2 corresponds to the duration of N2 symbols of the UE processing capability 1 PUSCH preparation time [6, TS 38.214]). To determine the minimum time, the UE considers that N1 and N2 correspond to the smaller of the SCS configurations for PDSCH and PUSCH. For μ = 0, the UE assumes N 1,0Assume it is equal to 14 [6, TS38.214].

[0076] In one option, the further delay may increase by a scaling factor r3, for example, 0.5r3 ms. r3 can be pre - definable or reportable by UE capabilities. r3 may be equal to u. Alternatively, r3 may be different from u. Note: The further delay after scaling may be directly specified in the specification instead of specifying the value r3. For example, for eRedCap, the further delay increases by 1 millisecond. For example, the further delay may increase to 0.5 + X ms. In other words, the UE assumes that the minimum time between the last symbol of PDSCH reception that carries a RAR UL grant or fallbackRAR and the first symbol of the corresponding PUSCH transmission scheduled by the RAR UL grant or fallbackRAR is N T,1 +N T,2 +0.5 + X milliseconds. The value X can be pre - definable, configurable by upper - layer signaling, or reportable by UE capabilities. The value X may be the same as or different from the value Y in the above embodiments. Alternatively, the further delay may not be changed for eRedCap UEs.

[0077] In one embodiment, the additional 0.5 - ms delay between Msg4 or MsgB and the corresponding HARQ - ACK transmission on PUCCH may be increased for eRedCap UEs.

[0078] In section 8.4 of TS38.213 in NR, in response to PDSCH reception with a UE contention resolution identity, the UE transmits HARQ - ACK information on the PUCCH. The minimum time between the last symbol of PDSCH reception and the first symbol of the corresponding PUCCH transmission with HARQ - ACK information is N T,1 +0.5 milliseconds. Similarly, in section 8.2A of 3GPP TS38.213, the UE has the first symbol of PUCCH transmission as N T,1It is not expected to occur after the last symbol of PDSCH reception by a time less than +0.5 milliseconds (where N T,1 is the PDSCH processing time of UE processing capability 1 [6, TS38.214]).

[0079] In one option, the further delay may increase by a scaling factor r4, e.g., 0.5r4 ms. The value r4 can be pre-defined or reportable by UE capabilities. Note: The further delay after scaling may be directly specified in the specification instead of specifying the value r4. For example, for eRedCap, the further delay increases to 1 millisecond. For example, the further delay may increase to 0.5 + Z ms. In other words, the UE may assume that the minimum time between the last symbol of PDSCH reception carrying Msg4 and the first symbol of the corresponding PUCCH transmission with HARQ-ACK information is N T,1 equal to +0.5 + Z milliseconds. The value Z can be pre-defined, configurable by upper layer signaling, or reportable by UE capabilities. The value Z may be the same as or different from the value X or Y in the above two embodiments. Alternatively, the further delay may not be changed for eRedCap UEs.

[0080] In one embodiment, the minimum gap between PRACH transmission and PUSCH / PUCCH / SRS may increase for eRedCap UEs.

[0081] In section 8.1 of TS38.213 in NR, for single cell operation or for operation using carrier aggregation within the same frequency band, the UE shall not transmit PRACH and PUSCH / PUCCH / SRS within the same slot or when the gap between the first and last symbols of the PRACH transmission in the first slot is separated from the last symbol or the first symbol of the PUSCH / PUCCH / SRS transmission in the second slot by less than N symbols respectively (where N = 2 for μ = 0 or μ = 1, N = 4 for μ = 2 or μ = 3, N = 16 for μ = 5, and N = 32 for μ = 6, and μ is the SCS configuration for the active UL BWP). For PUSCH transmissions with repetition type B, this applies to each actual repetition for PUSCH transmission [6, TS38.214].

[0082] In one option, the eRedCap UE shall not transmit PRACH and PUSCH / PUCCH / SRS within g consecutive slots. The value of g can be pre - definable or reportable by UE capabilities. For example, for eRedCap, g = 2. Alternatively, the restriction of no PRACH and PUSCH / PUCCH / SRS transmission within the same slot shall not be changed for eRedCap UE.

[0083] In another option, the minimum gap of N symbols between PRACH transmission and PUSCH / PUCCH / SRS may be increased by a scaling factor g. The value of g can be pre - definable or reportable by UE capabilities. Note: The new value of N after scaling may be directly specified in the specification instead of specifying the value of g. For example, for eRedCap, when applicable, g = 4 for μ = 0, g = 4 for μ = 1, and g = 8 for μ = 2. Alternatively, the minimum gap of N symbols between PRACH transmission and PUSCH / PUCCH / SRS shall not be changed for eRedCap UE.

[0084] In the above embodiment, the scaling factors r0, r1, r2, r3, r4, and g may each be equal to c and / or u. Alternatively, the scaling factors r0, r1, r2, r3, r4, and g may be different from c and / or u.

[0085] [Relaxed CSI calculation delay] The complexity of the UE can be reduced by increasing the CSI calculation delay (Z&Z' in Section 5.4 of TS38.214) by only the scaling factor z. The value z can be pre-defined or reportable by UE capabilities. For example, z is equal to 2. Note: Instead of specifying the value z, the new value of Z&Z' after scaling may be directly specified in the specification. Some other parameters may also increase in response to the increase in CSI calculation delay.

[0086] In one embodiment, n used to determine the CSI reference resource for the serving cell CSI_ref can be adjusted according to the increase in Z&Z'.

[0087] In Section 5.2.2.5 of TS38.214, the CSI reference resource in the time domain of the serving cell for CSI reporting in the uplink slot n' is a single downlink slot

[0088] [Number] is defined by. Here, K offset is a parameter configured by the upper layer as specified in Section 4.2 of [6 TS38.213], and μ Koffset has a value of 0 for frequency range 1 and is the subcarrier spacing configuration of K offset , and for periodic and semi-persistent CSI reporting, · When a single CSI-RS / SSB resource is configured for channel measurement, n CSI_ref is the minimum value of 4·2 μDL or more, and as a result, this corresponds to a valid downlink slot. Alternatively, · When multiple CSI-RS / SSB resources are configured for channel measurement, n CSI_ref is the minimum value of 5·2 μDL or more, and as a result, this corresponds to a valid downlink slot.

[0089] In one option, in the determination of CSI reference resources, for periodic and semi-persistent CSI reporting, · When a single CSI-RS / SSB resource is configured for channel measurement, n CSI_ref is the minimum value of 4z0·2 μDL or more, and as a result, this corresponds to a valid downlink slot. Alternatively, · When multiple CSI-RS / SSB resources are configured for channel measurement, n CSI_ref is the minimum value of 5z0·2 μDL or more, and as a result, this corresponds to a valid downlink slot.

[0090] The value z0 can be pre-defined or reportable by UE capabilities. The scaling factor z0 may be equal to z. Alternatively, the scaling factor z0 may be different from z.

[0091] [System and Implementation] Figures 1 to 3 show various systems, devices, and components that can implement aspects of the disclosed embodiments.

[0092] Figure 1 shows a network 100 according to various embodiments. The network 100 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the exemplary embodiments are not limited in this regard, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems and the like.

[0093] Network 100 may include UE102, and UE102 may include any mobile or non-mobile computing device designed to communicate with RAN104 via an over-the-air connection. UE102 may be communicatively coupled to RAN104 by the Uu interface. UE102 may be a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-vehicle entertainment device, instrument cluster, head-up display device, on-board diagnostic device, dash-top mobile device, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine type communication device, M2M or D2D device, IoT device, etc., and is not limited thereto.

[0094] In some embodiments, network 100 may include a plurality of UEs directly coupled to each other via a sidelink interface. The UEs may be, but are not limited to, M2M / D2D devices that communicate using physical sidelink channels such as PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0095] In some embodiments, UE102 may further communicate with AP106 via a wireless connection. AP106 may manage a WLAN connection, which may serve to offload some / all of the network traffic from RAN104. The connection between UE102 and AP106 may be compliant with any IEEE802.11 protocol, and AP106 may be a Wireless Fidelity (Wi-Fi (registered trademark)) router. In some embodiments, UE102, RAN104, and AP106 may utilize cellular WLAN aggregation (e.g., LWA / LWIP). Cellular WLAN aggregation may include UE102 configured by RAN604 to utilize both cellular radio resources and WLAN resources.

[0096] RAN104 may include one or more access nodes, such as AN108. AN108 may terminate an air interface protocol for UE102 by providing an access layer protocol that includes RRC, PDCP, RLC, MAC, and L1 protocols. Thus, AN108 may enable a data / voice connection between CN120 and UE102. In some embodiments, AN108 may be implemented as a separate device or as one or more software entities running on a server computer as part of a virtual network, also referred to as a virtual baseband unit pool, such as CRAN. AN108 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN108 may be a macrocell base station or a low-power base station for providing a femtocell, picocell, or other similar cell having a smaller coverage area, a smaller user capacity, or a higher bandwidth compared to a macrocell.

[0097] In embodiments where RAN104 includes a plurality of ANs, these may be coupled to each other via an X2 interface (when RAN104 is an LTE RAN) or an Xn interface (when RAN104 is a 5G RAN). The X2 / Xn interface may be separated into a control / user plane interface in some embodiments, enabling ANs to communicate information regarding handover, data / context transfer, mobility, load management, interference coordination, etc.

[0098] Each AN of RAN104 may manage one or more cells, cell groups, component carriers, etc., to provide an air interface for UE102 to access the network. UE102 may be simultaneously connected to a plurality of cells provided by the same AN or different ANs of RAN104. For example, UE102 and RAN104 may use carrier aggregation to enable UE102 to connect to a plurality of component carriers corresponding to Pcell or Scell respectively. In a dual connectivity scenario, the first AN may be a master node providing MCG, and the second AN may be a secondary node providing SCG. The first AN / second AN may be any combination of eNB, gNB, ng-eNB, etc.

[0099] RAN104 may provide an air interface on a licensed spectrum or an unlicensed spectrum. To operate within the unlicensed spectrum, the node may use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCell / Scell. Before accessing the unlicensed spectrum, the node may perform media / carrier sensing operations based on, for example, the listen-before-talk (LBT) protocol.

[0100] In a V2X scenario, UE102 or AN108 may be or operate as an RSU, and the RSU may represent any transport infrastructure entity used for V2X communication. The RSU may be implemented within or by a suitable AN or a stationary (or relatively stationary) UE. The RSU implemented within or by the UE may be referred to as a "UE-type RSU", the eNB may be referred to as an "eNB-type RSU", the gNB may be referred to as a "gNB-type RSU", and so on hereinafter. In one example, the RSU is a computing device coupled with a radio frequency circuit located roadside that provides connection support to passing vehicle UEs. The RSU may also include an internal data storage circuit that stores intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling the traffic of ongoing vehicles and pedestrians. The RSU may provide very low latency communication required for high-speed events such as collision avoidance, traffic warnings, etc. Further or alternatively, the RSU may provide other cellular / WLAN communication services. The components of the RSU may be packaged within a weather-resistant enclosure suitable for outdoor installation and may include a network interface controller for providing a wired connection (e.g., Ethernet (registered trademark)) to a traffic signal controller or a backhaul network.

[0101] In some embodiments, RAN 104 may be an LTE RAN 110 having an eNB, e.g., eNB 112. The LTE RAN 110 may provide an LTE air interface having the following characteristics, i.e., 15 kHz SCS, CP-OFDM waveform for DL and SC-FDMA waveform for UL, turbo code for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management, PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation, and CRS for cell search and initial acquisition, channel quality measurement and channel estimation in the UE for coherent demodulation / detection. The LTE air interface may operate in a band below 6 GHz.

[0102] In some embodiments, RAN 104 may be an NG-RAN 114 having a gNB, e.g., gNB 116 or an ng-eNB, e.g., ng-eNB 118. The gNB 116 may connect to a 5G-capable UE using a 5G NR interface. The gNB 116 may also connect to a 5G core through an NG interface, and the NG interface may include an N2 interface or an N3 interface. The ng-eNB 118 may also connect to a 5G core through an NG interface, but may connect to a UE through an LTE air interface. The gNB 116 and the ng-eNB 118 may be connected to each other on an Xn interface.

[0103] In some embodiments, the NG interface may be split into two parts, i.e., an NG user plane (NG-U) interface (e.g., N3 interface) that carries traffic data between nodes of the NG-RAN 114 and the UPF 148, and an NG control plane (NG-C) interface (e.g., N2 interface) that is a signaling interface between nodes of the NG-RAN 114 and the AMF 144.

[0104] NG-RAN114 may provide a 5G-NR air interface with the following characteristics, namely, variable SCS, CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL, polar, repetition, simplex and Reed-Muller code for control, and LDPC for data. Similar to the LTE air interface, the 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for phase tracking of PDSCH, and tracking reference signals for time tracking. The 5G-NR air interface may operate in the FR1 band including bands below 6 GHz or the FR2 band including bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB which is an area of the downlink resource grid including PSS / SSS / PBCH.

[0105] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For example, UE102 can be composed of multiple BWPs, and each BWP configuration has a different SCS. When a BWP change is indicated to UE102, the SCS of the transmission is similarly changed. Another use case example of BWPs is related to power saving. In particular, multiple BWPs can be configured for UE102 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with low traffic load while enabling power saving in UE102 and in some cases in gNB116. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic loads.

[0106] RAN104 is communicatively coupled to a CN120 that includes network elements that provide various functions for supporting data and telecommunications services to a customer / subscriber (e.g., the user of UE102). Components of CN120 may be implemented within one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize some or all of the functions provided by the network elements of CN120 onto physical computing / storage resources within servers, switches, etc. The logical instantiation of CN120 may be referred to as a network slice, and some logical instantiations of CN120 may be referred to as network sub-slices.

[0107] In some embodiments, CN120 may be an LTE CN122, which may also be referred to as an EPC. As shown in the figure, LTE CN122 may include an MME124, an SGW126, an SGSN128, an HSS130, a PGW132, and a PCRF134 that are coupled to each other on an interface (or “reference point”). The functions of the elements of LTE CN122 can be briefly introduced as follows.

[0108] The MME124 may implement a mobility management function that tracks the current location of the UE102 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0109] The SGW126 may terminate the S1 interface to the RAN and route data packets between the RAN and the LTE CN122. The SGW126 may be a local mobility anchor point for RAN node - to - RAN node handover and may also provide an anchor for inter - 3GPP mobility. Other roles may include lawful intercept, charging, and any policy enforcement.

[0110] The SGSN 128 may track the location of the UE 102 and perform security functions and access control. Further, the SGSN 128 may perform EPC node - to - node signaling for mobility between different RAT networks, PDN and S - GW selection specified by the MME 124, MME selection for handover, etc. The S3 reference point between the MME 124 and the SGSN 128 may enable user and bearer information exchange for mobility between 3GPP access networks in idle / active states.

[0111] The HSS 130 may include a database for network users, which contains subscription - related information to support the processing of communication sessions by network entities. The HSS 130 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location - dependency, etc. The S6a reference point between the HSS 130 and the MME 124 may enable the transfer of subscription data and authentication data for authenticating / authorizing user access to the LTE CN 120.

[0112] The PGW 132 may terminate the SGI interface to a data network (DN) 136, which may include the application / content server 138. The PGW 132 may route data packets between the LTE CN 122 and the data network 136. The PGW 132 may be coupled to the SGW 126 by the S5 reference point to facilitate user - plane tunneling and tunnel management. The PGW 132 may further include a node (e.g., PCEF) for policy enforcement and charging data collection. Further, the SGi reference point between the PGW 132 and the data network 136 may be, for example, an operator - external public, private PDN or an intra - operator packet data network for the provision of IMS services. The PGW 132 may be coupled to the PCRF 134 via the Gx reference point.

[0113] PCRF 134 is a policy and charging control element of LTE CN 122. PCRF 134 may be communicatively coupled to application / content server 138 to determine appropriate QoS and charging parameters for a service flow. PCRF 132 may provision related rules to PCEF (via the Gx reference point) using appropriate TFT and QCI.

[0114] In some embodiments, CN 120 may be 5GC 140. 5GC 140 may include, as shown, AUSF 142, AMF 144, SMF 146, UPF 148, NSSF 150, NEF 152, NRF 154, PCF 156, UDM 158, and AF 160 coupled to each other on an interface (or "reference point"). The functions of the elements of 5GC 140 can be briefly introduced as follows.

[0115] AUSF 142 may store data for the authentication of UE 102 and process functions related to authentication. AUSF 142 may facilitate a common authentication framework for various access types. As shown, in addition to communicating with other elements of 5GC 140 on a reference point, AUSF 142 may present an Nausf service-based interface.

[0116] AMF 144 may also enable other functions of the 5GC 140 to communicate with the UE 102 and the RAN 104 and subscribe to notifications regarding mobility events related to the UE 102. AMF 144 may serve functions of registration management (e.g., for registering the UE 102), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. AMF 144 may provide transport for SM messages between the UE 102 and the SMF 146 and function as a transparent proxy for routing SM messages. AMF 144 may also provide transport for SMS messages between the UE 102 and the SMSF. AMF 144 may interact with the AUSF 142 and the UE 102 to perform various security anchor and context management functions. Further, AMF 144 may be an end point of the RAN CP interface, which may include or be the N2 reference point between the RAN 104 and the AMF 144, and AMF 144 may be an end point of the NAS (N1) signaling and may perform NAS encryption and integrity protection. AMF 144 may also support NAS signaling with the UE 102 on the N3 IWF interface.

[0117] SMF 146 may serve to establish a session between SMs (e.g., between UPF 148 and AN 108), tunnel management, assign and manage UE IP addresses (including optional permissions), select and control the UPF function, configure traffic steering in UPF 148 to route traffic to appropriate destinations, terminate the interface towards the policy control function, enforce policies, perform charging and part of QoS control, lawful interception (for SM events and the interface to the LI system), terminate the SM part of NAS messages, downlink data notification, initiate AN-specific SM information sent to AN 108 via AMF 144 on N2, and determine the SSC mode of the session. SM may refer to the management of PDU sessions, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between UE 102 and data network 136.

[0118] UPF 148 may function as an anchor point for RAT-internal and RAT-interworking mobility, an external PDU session point of interconnection to data network 136, and a branching point to support multi-home PDU sessions. UPF 148 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), perform transport-level packet marking on the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 148 may include an uplink classifier to support routing traffic flows to the data network.

[0119] The NSSF 150 may select a set of network slice instances to serve the UE 102. The NSSF 150 may also determine, if necessary, the permitted NSSAI and the mapping to the subscribed S-NSSAI. The NSSF 150 may also determine the set of AMFs to be used to serve the UE 102, or, based on the appropriate configuration, may determine a list of candidate AMFs, in some cases by querying the NRF 154. The selection of the set of network slice instances for the UE 102 may be triggered by the AMF 144 in which the UE 102 is registered by interacting with the NSSF 150, which may result in a change of the AMF. The NSSF 150 may interact with the AMF 144 via the N22 reference point and may communicate with another NSSF within the visited network via an N31 reference point (not shown). Further, the NSSF 150 may present an Nnssf service-based interface.

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

[0121] NRF154 may support a service discovery function, receive NF discovery requests from NF instances, and provide information on the discovered NF instances to the NF instances. NRF154 may also maintain information on available NF instances and the services they support. As used herein, terms such as "instantiate," "instantiation," etc. may indicate the creation of an instance, and "instance" may indicate a specific occurrence of an object that may occur during the execution of program code. Further, NRF154 may present an Nnrf service-based interface.

[0122] PCF156 may provide policy rules to the control plane function to enforce policy rules and may also support a unified policy framework for managing network behavior. PCF156 may also implement a front end to access subscription information related to policy decisions in the UDR of UDM158. In addition to functioning and communicating at the reference points as shown, PCF156 presents an Npcf service-based interface.

[0123] The UDM158 may process subscription-related information to support the handling of communication sessions by network entities and may store the subscription data of the UE102. For example, the subscription data may be communicated via the N8 reference point between the UDM158 and the AMF144. The UDM158 may include two parts: an application front-end and a UDR. The UDR may store structured data for subscription data and policy data for the UDM158 and the PCF156, and / or public and application data for the NEF152 (including PFDs for application detection, application request information for multiple UEs102). The Nudr service-based interface is presented by the UDR121, enabling the UDM158, the PCF156, and the NEF152 to access a specific set of stored data, read notifications of relevant data changes within the UDR, update (e.g., add, modify), delete, and subscribe. The UDM may include a UDM-FE, which is responsible for processing credentials, 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 identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs on the reference points as shown, the UDM158 may present a Nudm service-based interface.

[0124] The AF160 may provide the influence of the application in traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0125] In some embodiments, 5GC 140 may enable edge computing by selecting an operator / third-party service such that the point at which UE 102 attaches to the network is geographically close. This may reduce latency and load in the network. To provide an implementation of edge computing, 5GC 140 may select a UPF 148 close to UE 102 and perform traffic steering from UPF 148 to data network 136 via the N6 interface. This may be based on UE subscription data, UE location, and information provided by AF 160. Thus, AF 160 may influence UPF (re)selection and traffic routing. Based on the operator's placement, when AF 160 is considered a trustworthy entity, the network operator may permit AF 160 to interact directly with the relevant NF. Further, AF 160 may present a Naf service-based interface.

[0126] Data network 136 may represent various network operator services, Internet access, or third-party services that may be provided by one or more servers, including, for example, application / content server 138.

[0127] FIG. 2 schematically illustrates a wireless network 200 according to various embodiments. Wireless network 200 may include a UE 202 that wirelessly communicates with an AN 204. UE 202 and AN 204 are similar to components of the same name described elsewhere herein and may be substantially interchangeable.

[0128] UE 202 may be communicatively coupled to AN 204 via a connection 206. Connection 206 is shown as an air interface to enable a communication coupling and may be compatible with a cellular communication protocol such as an LTE protocol or a 5G NR protocol operating at a frequency of mmWave or less than 6 GHz.

[0129] UE 202 may include a host platform 208 coupled to a modem platform 210. The host platform 208 may include application processing circuitry 212, and the application processing circuitry 212 may be coupled to protocol processing circuitry 214 of the modem platform 210. The application processing circuitry 212 may execute various applications for the UE 202 that source / sink application data. The application processing circuitry 212 may further implement one or more layer operations for transmitting application data to / receiving application data from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0130] The protocol processing circuitry 214 may implement one or more layer operations to facilitate the transmission or reception of data on connection 206. The layer operations implemented by the protocol processing circuitry 214 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0131] The modem platform 210 may further include a digital baseband circuit 216 that may implement one or more layer operations “below” the layer operations executed by the protocol processing circuitry 214 in the network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding (including one or more of space-time coding, space-frequency coding, or space coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals, and other related functions. The modem platform 210 may further include a transmission circuit 218, a reception circuit 220, an RF circuit 222, and an RF front end (RFFE) 224, which may include or be connected to one or more antenna panels 226. Briefly speaking, the transmission circuit 218 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc., the reception circuit 220 may include an analog-to-digital converter, a mixer, an IF component, etc., the RF circuit 222 may include a low-noise amplifier, a power amplifier, a power tracking component, etc., and the RFFE 224 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the components of the transmission circuit 218, the reception circuit 220, the RF circuit 222, the RFFE 224, and the antenna panel 226 (collectively referred to as "transmission / reception components") may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, whether the frequency is mmWave or less than 6 GHz, etc. In some embodiments, the transmission / reception components may be arranged in a plurality of parallel transmission / reception chains and may be arranged on the same or different chips / modules, etc.

[0132] In some embodiments, the protocol processing circuit 214 may include one or more instances of a control circuit (not shown) for providing control functions to the transmission / reception components.

[0133] UE reception may be established by and through the antenna panel 226, the RFFE 224, the RF circuit 222, the reception circuit 220, the digital baseband circuit 216, and the protocol processing circuit 214. In some embodiments, the antenna panel 226 may receive the transmission from AN204 by a received beamforming signal received by a plurality of antennas / antenna elements of one or more antenna panels 226.

[0134] UE transmission may be established by and through protocol processing circuitry 214, digital baseband circuitry 216, transmission circuitry 218, RF circuitry 222, RFFE 224, and antenna panel 226. In some embodiments, the transmission components of UE 204 may apply a spatial filter to the data being transmitted to form a transmission beam radiated by the antenna elements of antenna panel 226. Similar to UE 202, AN 204 may include a host platform 228 coupled to a modem platform 230. The host platform 228 may include application processing circuitry 232 coupled to protocol processing circuitry 234 of the modem platform 230. The modem platform may further include digital baseband circuitry 236, transmission circuitry 238, reception circuitry 240, RF circuitry 242, RFFE circuitry 244, and antenna panel 246. The components of AN 204 are similar to the components of UE 202 with the same name and may be substantially interchangeable. In addition to performing data transmission / reception as described above, the components of AN 208 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.

[0135] FIG. 3 is a block diagram showing components that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and execute any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, FIG. 3 shows a schematic diagram of hardware resources 300 including one or more processors (or processor cores) 310, one or more memory / storage devices 320, and one or more communication resources 330, each of which may be communicatively coupled via a bus 340 or other interface circuitry. In embodiments where network function virtualization (e.g., NFV) is utilized, a hypervisor 302 may be executed to provide an execution environment for one or more network slices / sub-slices for utilizing the hardware resources 300.

[0136] The processor 310 may include, for example, a processor 312 and a processor 314. The processor 310 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), other processors (including those discussed herein), or any suitable combination thereof.

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

[0138] The communication resource 330 may include an interconnect or network interface controller, component, or other suitable device for communicating with one or more peripheral devices 304, one or more databases 306, or other network elements via the network 308. For example, the communication resource 330 may include a wired communication component (e.g., for coupling via USB, Ethernet, etc.), a cellular communication component, an NFC component, a Bluetooth® (or Bluetooth® Low Energy) component, a Wi-Fi® component, and other communication components.

[0139] The instructions 350 may include software, a program, an application, an applet, an app, or other executable code for causing at least any one of the software, program, application, applet, app, or the processor 310 to execute any one or more of the methods discussed herein. The instructions 350 may be wholly or partially present in at least one of the processor 310 (e.g., the cache memory of the processor), the memory / storage device 320, or any suitable combination thereof. Further, any portion of the instructions 350 may be transferred from the hardware resource 300 from any combination of the peripheral devices 304 or the databases 306. Accordingly, the memory of the processor 310, the memory / storage device 320, the peripheral devices 304, and the databases 306 are examples of computer-readable and machine-readable media.

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

[0141] [Example] Some non-limiting examples of various embodiments are provided below.

[0142] Example A1, when executed by one or more processors of a Reduced Capability (RedCap) user equipment (UE), determines the timeline requirements for the RedCap UE related to random access procedures, where the timeline requirements are longer than those for non-RedCap UEs, and configures the UE to perform random access procedures based on the timeline requirements, and may include one or more non-transitory computer-readable media (NTCRMs) storing instructions for performing the above.

[0143] Example A2 may include one or more NTCRMs of Example A1, and performing random access procedures includes retransmitting a Physical Random Access Channel (PRACH) according to the timeline requirements.

[0144] Example A3 may include one or more NTCRMs of Example A2, and the instructions, when executed, further configure the RedCap UE to perform an initial transmission of the PRACH and receive a Random Access Response (RAR) Physical Downlink Shared Channel (PDSCH), and the timeline requirements correspond to the period between receiving the RAR PDSCH and retransmitting the PRACH.

[0145] Example A4 may include one or more NTCMs of Example A3. If the RedCap UE does not correctly receive the transport block of the RAR PDSCH, a retransmission of the PRACH is performed.

[0146] Example A5 may include one or more NTCMs of Example A3. If the RAPID of the RAR PDSCH is not associated with the initial transmission of the PRACH, a retransmission of the PRACH is performed.

[0147] Example A6 may include one or more NTCMs of Example A1. The timeline requirement corresponds to the minimum period between the reception of the fallback random access response (RAR) by the RedCap UE and the transmission of Msg3.

[0148] Example A7 may include one or more NTCMs of Example A6. The period is equal to N T,1 +N T,2 +0.5 + X milliseconds, where N T,1 corresponds to the duration of N1 symbols of the PDSCH processing time of UE processing capability 1 when an additional PDSCH demodulation reference signal (DM-RS) is configured, and N T,2 corresponds to the duration of N2 symbols of the physical uplink shared channel (PUSCH) preparation time of UE processing capability 1, and X is an additional time allocation for the RedCap UE.

[0149] Example A8 may include one or more NTCMs of Example A1. The timeline requirement corresponds to the period between a successful random access response (RAR) and the transmission of the corresponding hybrid automatic repeat request (HARQ)-acknowledgment (ACK) by the RedCap UE.

[0150] Example A9 may include one or more of Examples A1 - A8, and the timeline requirement is one slot for the Msg2 physical downlink shared channel (PDSCH) that is greater than 25 physical resource blocks (PRBs) for a 15 kilohertz (kHz) sub - carrier spacing (SCS), or greater than 12 PRBs for a 30 kHz SCS.

[0151] Example A10 is to determine the timeline requirement for a RedCap UE related to a random access procedure when executed by one or more processors of a next - generation node B (gNB), the timeline requirement being longer than that for a non - RedCap UE, and to configure the gNB to perform the random access procedure with a first RedCap UE based on the timeline requirement. It may include one or more non - transitory computer - readable media (NTCRMs) storing instructions.

[0152] Example A11 may include one or more of the NTCRMs of Example A10, and performing the random access procedure includes receiving re - transmissions of the physical random access channel (PRACH) according to the timeline requirement.

[0153] Example A12 may include one or more of the NTCRMs of Example A11, and the instructions further configure the gNB to transmit a random access response (RAR) physical downlink shared channel (PDSCH) to the RedCap UE when executed, and the timeline requirement corresponds to the period between the reception of the RAR PDSCH by the RedCap UE and the re - transmission of the PRACH.

[0154] Example 13 may include one or more of the NTCRMs of Example A12, and if the RedCap UE does not correctly receive the transport block of the RAR PDSCH, or if the RAPID of the RAR PDSCH is not associated with the initial transmission of the PRACH, a re - transmission of the PRACH is performed.

[0155] Example A14 may include one or more NTCRMs of Example A10, and the timeline requirement corresponds to the minimum period between the reception of a fallback random access response (RAR) by the RedCap UE and the transmission of Msg3 by the RedCap UE.

[0156] Example A15 may include one or more NTCRMs of Example A14, and the period is equal to N T,1 +N T,2 +0.5 + X milliseconds, where N T,1 corresponds to the duration of N1 symbols of the PDSCH processing time of UE processing capability 1 when an additional physical downlink shared channel (PDSCH) demodulation reference signal (DM-RS) is configured, and N T,2 corresponds to the duration of N2 symbols of the physical uplink shared channel (PUSCH) preparation time of UE processing capability 1, and X is an additional time allocation for the RedCap UE.

[0157] Example A16 may include one or more NTCRMs of Example A10, and the timeline requirement corresponds to the period between a successful random access response (RAR) and the transmission of the corresponding hybrid automatic repeat request (HARQ)-acknowledgment (ACK) by the RedCap UE.

[0158] Example A17 may include one or more NTCRMs of Examples A10 - A16, and the timeline requirement is one slot for the Msg2 physical downlink shared channel (PDSCH) that is larger than 25 physical resource blocks (PRBs) for a subcarrier spacing (SCS) of 15 kilohertz (kHz) or larger than 12 PRBs for an SCS of 30 kHz.

[0159] Example A18 may include an apparatus implemented in a Reduced Capability (RedCap) User Equipment (UE). The apparatus includes a memory for storing an indication of timeline requirements related to a random access procedure, where the timeline requirements are longer than those for non-RedCap UEs, and a processor circuit coupled to the memory. To execute the random access procedure, the processor circuit encodes a Physical Random Access Channel (PRACH) for transmission to a Next Generation Node B (gNB), receives a Random Access Response (RAR) Physical Downlink Shared Channel (PDSCH), encodes subsequent messages for transmission based on the timeline requirements, where the timeline requirements correspond to a period between the reception of the RAR PDSCH and the transmission of the subsequent messages.

[0160] Example A19 may include the apparatus of Example A18, where the subsequent message is a retransmission of Msg3 or the PRACH.

[0161] Example A20 may include the apparatus of Examples A18 - A19, where the period is equal to N T,1 +N T,2 +0.5+X milliseconds, where N T,1 is the duration of N1 symbols corresponding to the PDSCH processing time of UE processing capability 1 when additional Physical Downlink Shared Channel Demodulation Reference Signals (DM-RS) are configured, and N T,2 is the duration of N2 symbols corresponding to the Physical Uplink Shared Channel (PUSCH) preparation time of UE processing capability 1, and X is an additional time allocation for the RedCap UE.

[0162] Example B1 may include a method for relaxed processing time for a UE having a reduced bandwidth.

[0163] Example B2 may include the method of Example B1 or some other example herein, where d proc,1 and / or d2 increases in an equation for determining T. 1,1 and / or d2 increases.

[0164] Example B3 may include the method of Example B1 or some other example herein, and the range of values of the slot offset (K1) from PDSCH to HARQ feedback increases.

[0165] Example B4 may include the method of Example B1 or some other example herein, and the value N3 of the HARQ-ACK multiplexing timeline increases.

[0166] Example B5 may include the method of Example B1 or some other example herein, and the value N of the HARQ-ACK feedback timeline for SPS PDSCH release increases.

[0167] Example B6 may include the method of Example B1 or some other example herein, and d proc,2 and / or d2 increases in the formula for determining T. 2,1

[0168] Example B7 may include the method of Example B1 or some other example herein, and the range of values of the scheduling offset (K2) from PDCCH to PUSCH increases.

[0169] Example B8 may include the method of Example B1 or some other example herein, and the range of values of the scheduling offset (K0) from PDCCH to PDSCH increases.

[0170] Example B9 may include the method of Example B1 or some other example herein, and the maximum number of slots configured as the minimum scheduling offset (K0) / (K2) increases.

[0171] Example B10 may include the method of Example B1 or some other example herein, and the application delay of the minimum scheduling offset limit Z μ increases.

[0172] ​Example B11 may include the method of Example B1 or some other example in this specification, and the value j for determining K2 in the default table for PUSCH time domain resource allocation increases.

[0173] Example B12 may include the method of Example B1 or some other example in this specification, and in addition to the K2 value for the UE to transmit PUSCH scheduled by DCI format 0_0 or RAR having a CRC scrambled by TC-RNTI or fallbackRAR, the slot delay value Δ applied increases.

[0174] Example B13 may include the method of Example B1 or some other example in this specification, and the processing time between control signaling transmissions associated with different messages in the random access procedure increases.

[0175] Example B14 may include the method of Example B1 or some other example in this specification, and nCSI_ref used to determine the CSI reference resource for the serving cell is adjusted.

[0176] Example B15 may include the method for a Reduced Capability (RedCap) UE, and the method includes the step of determining the processing time specified for the RedCap UE, where the processing time is longer than that for a non-RedCap UE, and the step of communicating on a wireless cellular network based on the processing time. and includes.

[0177] Example B16 may include the method of Example B15 or some other example in this specification, and the step of determining the processing time includes determining T for the RedCap UE based on d 1,1 and / or d2 having a value larger than that for a non-RedCap UE. proc,1 and includes the step of determining.

[0178] Example B17 may include the method of Examples B15 - B16 or some other examples in this specification. The step of determining the processing time may have a value of d for the RedCap UE that is larger than that for the non - RedCap UE 2,1 and / or determine T based on d2 proc,2 including the step of doing so.

[0179] Example B18 may include the method of Examples B15 - B17 or some other examples in this specification. The processing time is the range of values of the slot offset (K1) from PDSCH to HARQ feedback, the value N3 of the HARQ - ACK multiplexing timeline, the value N of the HARQ - ACK feedback timeline for SPS PDSCH release, the range of values of the scheduling offset (K2) from PDCCH to PUSCH, the range of values of the scheduling offset (K0) from PDCCH to PDSCH, the maximum number of slots configured as the minimum scheduling offset (K0) / (K2), the minimum scheduling offset constraint Z μ the applicable delay of the value j for the determination of K2 in the default table for PUSCH time - domain resource allocation, the slot delay value Δ applied in addition to the K2 value for the UE to transmit DCI format 0_0 with a CRC scrambled by TC - RNTI or fallbackRAR or PUSCH scheduled by RAR, the processing time between the message and the associated control signaling transmission in the random access procedure, and / or nCSI_ref used to determine the CSI reference resource for the serving cell corresponding to one or more of the above.

[0180] Example B20 may include the method of Example B19 or some other examples in this specification. The step of determining the processing time may have a value of d for the RedCap UE that is larger than that for the non-RedCap UE 1,1 and / or determine T based on d2 proc,1 including the step of

[0181] Example B21 may include the method of Examples B19 - B20 or some other examples in this specification. The step of determining the processing time may have a value of d for the RedCap UE that is larger than that for the non-RedCap UE 2,1 and / or determine T based on d2 proc,2 including the step of

[0182] Example B22 may include the method of Examples B19 - B21 or some other examples in this specification. The processing time is the value range of the slot offset (K1) from PDSCH to HARQ feedback, the value N3 of the HARQ-ACK multiplexing timeline, the value N of the HARQ-ACK feedback timeline for SPS PDSCH release, the value range of the scheduling offset (K2) from PDCCH to PUSCH, the value range of the scheduling offset (K0) from PDCCH to PDSCH, the maximum number of slots configured as the minimum scheduling offset (K0) / (K2), the application delay of the minimum scheduling offset constraint Z μ the value j for determining K2 in the default table for PUSCH time domain resource allocation, the slot delay value Δ applied in addition to the K2 value for the UE to transmit PUSCH scheduled by DCI format 0_0 with a CRC scrambled by TC-RNTI or fallbackRAR or RAR ​The processing time between a message and associated control signaling transmission in a random access procedure, and / or nCSI_ref used to determine CSI reference resources for a serving cell corresponds to one or more of the above.

[0183] Example Z01 may include an apparatus including means for performing one or more elements of a method described in any of Examples A1 - A20, B1 - B22 or related thereto, or any other method or process described herein.

[0184] Example Z02 may include one or more non - transitory computer - readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in any of Examples A1 - A20, B1 - B22 or related thereto, or any other method or process described herein.

[0185] Example Z03 may include an apparatus including logic, modules or circuits for performing one or more elements of a method described in any of Examples A1 - A20, B1 - B22 or related thereto, or any other method or process described herein.

[0186] Example Z04 may include a method, technique or process described in any of Examples A1 - A20, B1 - B22 or related thereto, or a part or portion thereof.

[0187] Example Z05 may include an apparatus including one or more processors and one or more computer - readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique or process described in any of Examples A1 - A20, B1 - B22 or related thereto, or a part thereof.

[0188] Example Z06 may include a signal described in or related to any of Examples A1 to A20, B1 to B22, or a part or portion thereof.

[0189] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message described in or related to any of Examples A1 to A20, B1 to B22, or a part or portion thereof, or other things described in this disclosure.

[0190] Example Z08 may include a signal encoded with data described in or related to any of Examples A1 to A20, B1 to B22, or a part or portion thereof, or other things described in this disclosure.

[0191] Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message described in or related to any of Examples A1 to A20, B1 to B22, or a part or portion thereof, or other things described in this disclosure.

[0192] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, and the execution of the computer-readable instructions by one or more processors causes the one or more processors to execute a method, technique, or process described in or related to any of Examples A1 to A20, B1 to B22, or a part thereof.

[0193] Example Z11 may include a computer program including instructions, and the execution of the program by a processing element causes the processing element to execute a related method, technique, or process described in or related to any of Examples A1 to A20, B1 to B22, or a part thereof.

[0194] Example Z12 may include a signal in a wireless network as illustrated and described herein.

[0195] Example Z13 may include a method of communicating in a wireless network as illustrated and described herein.

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

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

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

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

[0200] As used herein, the term "circuit" refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group), and / or a memory (shared, dedicated, or group), an application specific integrated circuit (ASIC), a field-programmable device (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable system-on-chip), a digital signal processor (DSP), etc., configured to provide the recited functionality. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the recited functionality. The term "circuit" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and program code used to execute the functions of that program code. In these embodiments, the combination of the hardware element and the program code may be referred to as a particular type of circuit.

[0201] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit that can sequentially and automatically perform a series of arithmetic or logical operations, or can record, store, and / or transfer digital data. The 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, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing computer-executable instructions such as program code, software modules, and / or functional processes or operating in some other manner. The processing circuit may include more hardware accelerators, which may be microprocessors, programmable processing devices, etc. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuit" and / or "baseband circuit" may be considered synonymous with "processor circuit" and may be referred to as "processor circuit".

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

[0203] As used herein, the term "user equipment" or "UE" may refer to a device having wireless communication capabilities, or may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with, or 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 device, reconfigurable wireless device, reconfigurable mobile device, etc. Further, the term "user equipment" or "UE" may include any type of wireless / wired device, or any computing device including a wireless communication interface.

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

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

[0206] As used herein, terms such as "appliance", "computer appliance", etc. refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide certain computing resources. A "virtual appliance" is a virtual machine image that virtualizes or emulates a computer appliance or is implemented by a hypervisor-based device dedicated to providing certain computing resources in other ways.

[0207] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, and / or physical or virtual components within a particular device, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, networks, databases and applications, workload units, etc. "Hardware resources" may refer to computing, storage, and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage, and / or network resources provided to applications, devices, systems, etc. by a virtualization infrastructure. The terms "network resources" or "communication resources" may refer to resources accessible by computer devices / systems via a communication network. The term "system resources" may refer to any kind of shared entity for providing services and may include computing and / or network resources. System resources may be considered a set of consistent functions, network data objects, or services accessible through a server, and such system resources may exist on a single host or multiple hosts and are clearly identifiable.

[0208] As used herein, the term "channel" refers to either a tangible or intangible transmission medium used to communicate data or a data stream. The term "channel" may be synonymous with, and / or equivalent to, terms such as "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier", and / or other similar terms that refer to the path or medium through which data is communicated. Further, as used herein, the term "link" refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

[0209] As used herein, terms such as "instantiate", "instantiation", etc. refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0210] The terms "coupled", "communicatively coupled" are used herein together with their derivatives. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with 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 said to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may include those through a wired or other interconnecting connection, through a wireless communication channel or link, etc., and may mean that two or more elements may be in contact with each other by means of communication means.

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

[0212] The term "SMTC" indicates an SSB-based measurement timing configuration constituted by SSB-MeasurementTimingConfiguration.

[0213] The term "SSB" indicates an SS / PBCH block.

[0214] The term "primary cell" indicates an MCG cell operating on a primary frequency, on which a UE executes an initial connection establishment procedure or starts a connection re-establishment procedure.

[0215] The term "primary SCG cell" indicates an SCG cell on which a UE performs random access when executing a reconfiguration procedure involving synchronization for DC operation.

[0216] The term "secondary cell" indicates a cell that provides additional radio resources on top of a special cell for a UE configured with CA.

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

[0218] The term "serving cell" indicates a primary cell for an RRC_CONNECTED UE not configured with CA / DC, and there is only one serving cell that constitutes the primary cell.

[0219] The term "serving cell" indicates a set of cells including a special cell and all secondary cells for an RRC_CONNECTED UE configured with CA / .

[0220] The term "special cell" indicates a PC cell of MCG or a PSCell of SCG in the case of DC operation, and in other cases, the term "special cell" indicates a P cell.

Claims

1. When executed by one or more processors of a Reduced Capability (RedCap) User Equipment (UE), determining timeline requirements for the RedCap UE related to a random access procedure, the timeline requirements being longer than those for a non-RedCap UE, and executing the random access procedure based on the timeline requirements A computer program comprising instructions for configuring the UE to perform.

2. The computer program according to claim 1, wherein executing the random access procedure includes retransmitting a Physical Random Access Channel (PRACH) according to the timeline requirements.

3. The instructions, when executed, further configure the RedCap UE to perform an initial transmission of the PRACH, and receive a Random Access Response (RAR) Physical Downlink Shared Channel (PDSCH), The computer program according to claim 2, wherein the timeline requirements correspond to a period between receiving the RAR PDSCH and retransmitting the PRACH.

4. The computer program according to claim 3, wherein the retransmission of the PRACH is performed if the RedCap UE does not correctly receive the transport block of the RAR PDSCH.

5. The computer program according to claim 3, wherein the retransmission of the PRACH is performed if the RAPID of the RAR PDSCH is not associated with the initial transmission of the PRACH.

6. The computer program according to claim 1, wherein the timeline requirements correspond to a minimum period between receiving a fallback Random Access Response (RAR) by the RedCap UE and transmitting Msg3.

7. X is an additional time allocation for the RedCap UE, the computer program according to claim 6. The said period is N T,1 +N T,2 +0.5 + X milliseconds, N T,1 N corresponds to the PDSCH processing time of UE processing capability 1 when a further Physical Downlink Shared Channel Demodulation Reference Signal (DM-RS) is configured 1 and is the duration of N symbols N T,2 is the duration of N 2 symbols corresponding to the physical uplink shared channel (PUSCH) preparation time of UE processing capability 1,

8. The computer program according to claim 1, wherein the timeline requirements correspond to a period between a successful Random Access Response (RAR) and transmission of a corresponding Hybrid Automatic Repeat reQuest (HARQ)-ACKnowledgement (ACK) by the RedCap UE.

9. ​ The time line requirement is one slot for the Msg2 physical downlink shared channel (PDSCH) that is greater than 25 physical resource blocks (PRBs) for a subcarrier spacing (SCS) of 15 kilohertz (kHz) or greater than 12 PRBs for an SCS of 30 kHz, the computer program according to any one of claims 1 to 8.

10. When executed by one or more processors of a next-generation node B (gNB), Determining a time line requirement for a RedCap UE related to a random access procedure, the time line requirement being longer than that for a non-RedCap UE, Performing a random access procedure with a first RedCap UE based on the time line requirement A computer program including instructions for configuring the gNB to do so.

11. Performing the random access procedure includes receiving a retransmission of a physical random access channel (PRACH) according to the time line requirement, the computer program according to claim 10.

12. The instructions, when executed, Further configure the gNB to transmit a random access response (RAR) physical downlink shared channel (PDSCH) to the RedCap UE, The time line requirement corresponds to a period between reception of the RAR PDSCH by the RedCap UE and the retransmission of the PRACH, the computer program according to claim 11.

13. If the RedCap UE does not correctly receive the transport block of the RAR PDSCH, or if the RAPID of the RAR PDSCH is not associated with the initial transmission of the PRACH, the retransmission of the PRACH is performed, the computer program according to claim 12.

14. The time line requirement corresponds to a minimum period between reception of a fallback random access response (RAR) by the RedCap UE and transmission of Msg3 by the RedCap UE, the computer program according to claim 10.

15. The said period is N T,1 +N T,2 +0.5 + X milliseconds, and is equal to N T,1 is the duration of N symbols corresponding to the PDSCH processing time of UE processing capability 1 when additional Physical Downlink Shared Channel Demodulation Reference Signals (DM-RS) are configured 1 and is the duration of N symbols N T,2 is the duration of N 2 symbols corresponding to the physical uplink shared channel (PUSCH) preparation time of UE processing capability 1, X is an additional time allocation for a RedCap UE, the computer program according to claim 14.

16. The computer program according to claim 10, wherein the timeline requirement corresponds to a period between a successful random access response (RAR) and the transmission of a corresponding hybrid automatic repeat request (HARQ)-acknowledgment (ACK) by the RedCap UE.

17. The computer program according to any one of claims 10 to 16, wherein the timeline requirement is one slot for the physical downlink shared channel (PDSCH) that is larger than 25 physical resource blocks (PRBs) for a subcarrier spacing (SCS) of 15 kilohertz (kHz) or larger than 12 PRBs for an SCS of 30 kHz.

18. An apparatus implemented in a reduced-capability (RedCap) user equipment (UE), a memory for storing an indication of a timeline requirement related to a random access procedure, the timeline requirement being longer than that for a non-RedCap UE, a processor circuit coupled to the memory, and wherein, to execute the random access procedure, the processor circuit encodes a physical random access channel (PRACH) for transmission to a next-generation node B (gNB), receives a random access response (RAR) physical downlink shared channel (PDSCH), encodes a subsequent message for transmission based on the timeline requirement, wherein the timeline requirement corresponds to a period between the reception of the RAR PDSCH and the transmission of the subsequent message.

19. The apparatus according to claim 18, wherein the subsequent message is Msg3 or a retransmission of the PRACH.

20. The period is N T,1 +N T,2 +0.5 + X milliseconds, N T,1 is the duration of N 1 symbols corresponding to the PDSCH processing time of UE processing capability 1 when additional PDSCH demodulation reference signals (DM-RS) are configured, N T,2 is the duration of N 2 symbols corresponding to the physical uplink shared channel (PUSCH) preparation time of UE processing capability 1, and X is an additional time allocation for the RedCap UE, the apparatus according to claim 18.

21. One or more non-transitory computer-readable media (NTCRMs) storing the computer program according to any one of claims 1 to 8.

22. One or more non-transitory computer-readable media (NTCRMs) storing the computer program according to any one of claims 10 to 16.

Images