DE112021002457T5 - CONTROL CHANNEL TRANSMISSION TECHNIQUES FOR RADIOLESS OPERATION AND SCHEDULING OF DATA TRANSMISSIONS - Google Patents

Abstract

Systems, apparatus, methods, and computer-readable media for scheduling data transfers with support for symbol alignment and/or early termination are provided. The data transmissions can take place above a carrier frequency of 52.6 GHz. Additionally, embodiments provide control channel transmission techniques for slotless operation. Other embodiments may be described and/or claimed.

Description

CROSS REFERENCE TO RELATED APPLICATION

The present application claims the priority of the provisional U.S. Patent Application No. 63/051,561 , filed July 14, 2020, and International Application No. PCT/ CN2020/103528 , which was filed on July 22, 2020.

AREA

Various embodiments may relate generally to the field of wireless communications.

STATE OF THE ART

Mobile communications have evolved significantly from early voice systems to today's sophisticated integrated communications platform. The next generation wireless communication system, 5G or New Radio (NR), will enable access to information and data sharing anywhere and anytime by different users and applications. NR is expected to be a unified network/system aiming to meet very different and sometimes conflicting performance dimensions and services. Such diverse multidimensional requirements are driven by different services and applications. In general, NR will continue to evolve based on 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simple and seamless wireless connectivity solutions. NR enables everything wirelessly connected, delivering fast, rich content and services.

character list

• 1 FIG. 12 illustrates an example of a long transmission duration of a downlink physical shared channel (PDSCH) according to various embodiments.
• 2 12 illustrates an example of early termination of PDSCH transmission according to various embodiments.
• 3 12 illustrates an example of a code block (CB) on time/frequency resources according to various embodiments.
• 4 12 illustrates a symbol alignment unit (SAU) in a time domain resource allocation according to various embodiments.
• 5 12 illustrates a single transport block (TB) scheduled with multiple code block groups (CBGs) by downlink control information (DCI), according to various embodiments.
• 6 12 illustrates a single TB scheduled with multiple SAUs by a DCI, according to various embodiments.
• 7 12 illustrates a single TB scheduled with multiple CBGs by a DCI, according to various embodiments.
• 8th 12 illustrates an example of two TBs scheduled with multiple SAUs by a DCI, according to various embodiments.
• 9 FIG. 12 illustrates another example of two TBs scheduled with multiple SAUs by a DCI, according to various embodiments.
• 10 12 illustrates an example of two TBs scheduled with multiple CBGs by a DCI, according to various embodiments.
• 11 FIG. 12 illustrates another example of two TBs scheduled with multiple CBGs by a DCI, according to various embodiments.
• 12 FIG. 12 illustrates PDSCH scheduling with flexible duration and predetermined opportunities for downlink physical control channel (PDCCH) monitoring according to various embodiments.
• 13 12 illustrates PDSCH scheduling with flexible duration and new PDCCH monitoring after PDSCH according to various embodiments.
• 14 FIG. 12 illustrates PDSCH scheduling with flexible duration and new PDCCH monitoring in X symbols after PDSCH according to various embodiments.
• 15 12 illustrates a network according to various embodiments.
• 16 FIG. 12 schematically illustrates a wireless network according to various embodiments.
• 17 12 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some embodiments.
• 18-23 illustrate example procedures for practicing the various embodiments discussed herein.

DETAILED DESCRIPTION

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 are set forth such as specific structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present 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 various embodiments with unnecessary detail. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of various embodiments with unnecessary detail.

Various embodiments herein involve techniques to be implemented in a wireless cellular network. For example, embodiments include techniques for scheduling data transmissions for a carrier frequency greater than 52.6 GHz. Additionally, embodiments include control channel transmission techniques for slotless operation.

PLAN DATA TRANSMISSIONS FOR A CARRIER FREQUENCY ABOVE 52.6 GHZ

For a system operating above a carrier frequency of 52.6 GHz, particularly for terahertz communications, it is considered that a larger intercarrier spacing is needed to combat strong phase noise. If a larger intercarrier spacing, e.g. 1.92 MHz or 3.84 MHz, the slot duration can be very short. For example, for an intercarrier spacing of 1.92 MHz, the slot duration is approximately 7.8 µs. This extremely short slot duration may not be enough for processing higher layers, including Medium Access Layer (MAC) and Radio Link Control (RLC), etc. To solve this problem, next-generation NodeB (gNB) can use the downlink (DL) or Plan uplink (UL) data transmission over the slot boundary with long transmission times. In other words, the slot concept is not needed when scheduling the data transfer. 1 Figure 12 illustrates an example of a long transmission duration of a downlink physical shared channel (PDSCH).

In the DL transmission, more DL traffic can arrive at the gNB if the gNB has already sent a DL Downlink Control Information (DCI) or a previous PDSCH transmission is still ongoing. The gNB has to send a new DL DCI to schedule a PDSCH, which causes a delay in data transmissions. A solution could be to allow a gNB to schedule more DL resources than required to transfer the current DL data in the buffer. Consequently, when new DL traffic arrives, gNB can continue PDSCH transmission for the new DL traffic on the scheduled DL resource. On the other hand, if there is no new incoming DL traffic, the scheduled DL resources must be released earlier, e.g. B. premature termination of PDSCH transmission. In fact, besides the case of the lack of new DL traffic, there may be other reasons why gNB has to end a DL transmission earlier. 2 illustrates an example where the allocated DL resources could carry 10 CBs. However, the DL transmission can only be completed after the transmission of 6 CBs.

With the existing mapping of NR code blocks (CB) to time/frequency resources, there is no specific consideration of the symbols used to carry a CB or CB group (CBG). As a result, different numbers of symbols can be reserved for different CBs or CBGs. Furthermore, a CB tends to be broken up into multiple symbols. Such an irregular mapping between CB and the symbols results in a varying time needed in the pipeline receive processing (Rx) to decode different CBs of a transport block (TB).

On the other hand, certain CBs may require a longer wait time. For example, there is in 3 one symbol gap between the processing start of CB#1 and CB#2, but there is a two symbol gap between the processing start of CB#2 and CB#3. Erratic delays in the Rx processing pipeline can lead to inefficiency and increased latency, which is undesirable for future 5G and 6G communication system applications.

Various embodiments herein provide techniques for scheduling physical transmissions over shared channels to enable efficient symbol alignment and early termination operation. For example, detailed techniques are described herein to schedule data transmission that supports symbol alignment and early termination for a carrier frequency above 52.6 GHz.

For DL or UL transmission, a TB is transmitted from the MAC layer to the physical layer. For the Hybrid Automatic Repeat Request (HARQ) transmission of the DL transmission, a single HARQ ACK bit can be reported by the UE for a TB. Alternatively, when designing code block group (CBG) based transmission, e.g. B. a TB is divided into n CBGs, n ≤ N, a CBG from one or more Code Blocks (CB). A UE can report n or N HARQ ACK bits for the TB. A HARQ ACK bit is reported for each CBG. N is the maximum number of CBGs that can be laid out by a high layer. A CBG can be mapped to all time/frequency resources of certain consecutive symbols, e.g. B. Symbol alignment for a CBG is achieved.

Alternatively, each group of X CBs can be mapped to all time/frequency resources of Y consecutive symbols. In some embodiments, X may be relatively prime to Y. The set of Y consecutive symbols in the resource allocation is the symbol alignment unit (SAU). A CBG could be mapped to an SAU. Alternatively, a CBG can be mapped to one or more SAUs. Alternatively, a SAU can consist of one or more CBGs. A HARQ ACK bit may be reported for each CBG.

4 illustrates the use of SAU for symbol alignment. In this example each SAU is mapped onto all time/frequency resources of 2 symbols. The TB planned by a DCI is divided into 4 CBGs and each CBG consists of 2 SAUs.

Start and length indicator SLIV

In existing NR systems, a TB's Time Domain Resource Allocation (TDRA) is specified in a DCI. A row of the TDRA table indicates the start symbol S relative to the start of the slot and the number of consecutive symbols L counting from the symbol S assigned to the PDSCH or the uplink physical shared channel (PUSCH), e.g. B. the start and length indicator (SLIV). This scheme maps a TB onto L symbols, but this does not guarantee that any CB or CBG can end up on a symbol's boundary. Time domain resource allocation can be specially designed to facilitate symbol alignment. In this case, the number of CBGs per TB can be designed by high-layer signalling, indicated by DCI, or can be derived from the maximum length and number of symbols for a CBG.

In one option, SLIV specifies in the DCI the specific time resource used by a CBG. The size of a CBG could be given by the Modulation and Coding Scheme (MCS), L given by SLIV, and frequency resource allocation, if applicable. This scheme guarantees that a CBG is mapped onto a number of consecutive symbols.

In another option, SLIV specifies in the DCI the time resource used by a SAU. The number of bits transmitted on a SAU can be determined by MCS, L indicated by SLIV, and frequency resource allocation, if applicable. The consecutive symbols in a SAU carry one or more CBs. For this option, given a SLIV specification, the assignment between SAU and CBG (e.g. how many CBGs are mapped in a SAU or how many SAUs form a CBG) can be specified separately within the DCI, can be specified via radio resource control (RRC) Signaling can be designed or fixed for a specific subcarrier spacing.

Granularity for early termination

In order to support the early termination of a PDSCH or PUSCH transmission, the granularity of the early termination can be determined.

One option supports early termination at the end of the transfer of each TB or all N TBs, where N is greater than 1. Alternatively, early termination is not permitted for the first X TBs, and early termination is permitted in all Y TBs after the first X TBs. X and Y are predefined or designed by a high layer.

Note that this may apply to the case of multi-TB based scheduling where a single DCI is used to schedule one or more PDSCHs or PUSCHs.

In one option, early termination is supported at the end of transmission of each CBG or all N CBGs, where N is greater than 1. Alternatively, early termination is not permitted for the first X CBGs and early termination is permitted in any Y CBGs after the first X CBGs. X ≥ 1, Y ≥ 1. X and Y are predefined or designed by a high layer. Note that this may apply to the case of a single TB based scheduling where a single DCI is used to schedule a PDSCH or PUSCH and the PDSCH or PUSCH consists of one or more CBs/CBGs.

One option supports early termination at the end of transmission every SAU or every N SAUs, where N is greater than 1. Alternatively, early termination is not permitted for the first X SAUs and early termination is permitted in any Y SAUs after the first X SAUs. X ≥ 1, Y ≥ 1. X and Y can be predefined or designed by a high layer.

In one option, early termination is not allowed for the first X TBs and early termination is allowed in all Y CBGs after the first X TBs. X ≥ 1, Y ≥ 1. X and Y can be predefined or configured by a high layer.

In one option, early termination is not allowed for the first X TBs and early termination is allowed in all Y SAUs after the first X TBs. X ≥ 1, Y ≥ 1. X and Y can be predefined or designed by a high layer.

Single TB scheduling by a DCI

Embodiments in case of a transmission on a per TB basis scheduled by a DCI are provided as follows.

In one embodiment, a DCI can schedule a PDSCH or a PUSCH carrying only one TB. The TB is segmented into multiple CBGs. Each CBG contains one or more CBs. Symbol alignment is achieved for each CBG. In this case, SLIV can specify the time resource of a CBG in the DCI. The maximum number of CBGs of the TB can be designed by high-layer signalling. Alternatively, the maximum length of the allocated time resource is designed for a PDSCH or a PUSCH, so the number of CBGs of the TB can be derived from the maximum length and the number of symbols for a CBG. Alternatively, the maximum number of CBGs of the current TB in the DCI can be indicated dynamically or by a combination of RRC signaling and dynamic indication by DCI. The transmission of the PDSCH or PUSCH can be terminated at the symbol boundary of a CBG.

5 illustrates the case of a single TB scheduled by a DCI with multiple CBGs. In this case, SLIV specifies the time resource of a CBG, e.g. B. Each CBG is set to all time/frequency Resources mapped by 4 icons. Symbol alignment is therefore achieved for each CBG. For example, if the last CBG was not transmitted due to early termination, the TB will only consist of 3 valid CBGs. However, the UE may still need to report 4 HARQ-ACK bits for the TB to have a constant payload size of HARQ-ACK.

In one option, for HARQ ACK feedback, a UE may generate a HARQ ACK bit for each CBG. To schedule a retransmission of the corresponding TB, a CBG Transmission Indicator (CBGTI) can be used to indicate retransmission or not for each CBG. For example, if the kth bit of CBGTI is "1", a retransmission of the kth CBG is scheduled.

In another option, if the maximum number of CBGs is large, e.g. B. more than 8, the overhead of the CBGTI in a DCI quite high. In this case, the CBG-based HARQ-ACK feedback must not be used. That is, a HARQ ACK bit is reported for each TB. Within the DCI that triggers a retransmission of the TB, the actual number of CBGs transmitted by the gNB can be specified. For example, denoting the maximum number of CBGs as N, the field indicating the actual number of CBGs transmitted may have a size of [log ₂ (N)]. In this way, the UE can know the correct number of transmitted CBGs even if the UE does not recognize the correct number of transmitted CBGs in the early transmissions.

$$

abgebildet.In another option, HARQ ACK bundling can be supported by CBGs to limit the number of HARQ ACK bits. For example, the maximum number of HARQ ACK bits per TB may be 8. The number of CBGs associated with a HARQ ACK bit can be predefined or designed by a high layer. Alternatively, the number of CBGs mapped to a HARQ ACK bit can be specified dynamically in the DCI or by a combination of RRC signaling and dynamic indication by DCI. The last HARQ ACK bit before terminating the transmission may have a smaller number of CBGs. The maximum number of CBGs is denoted as N, the maximum number of HARQ ACK bits per TB is M, the N CBGs are mapped to the M HARQ ACK bits. If the N CBGs cannot be grouped evenly and mapped to M HARQ ACK bits, the last group(s) may be composed of a slightly smaller or larger number of CBGs. The evenly distributed CBGs, if any, can be mapped to the same HARQ ACK bit, e.g. B. CBG n is mapped to the HARQ ACK bit b _n = mod(n,M), n=0,1,...,N-1. Alternatively, the consecutive CBGs, if any, can be mapped to the same HARQ ACK bit, e.g. B. CBG n becomes the HARQ ACK bit $b_n=\{\begin{array}{cc}flOO\mathrm{right}\left(n/\lceil \frac{N}{M}\rceil \right)& n<mO\mathrm{i.e}\left(N,M\right)\cdot \lceil \frac{N}{M}\rceil \\ flOO\mathrm{right}\left(\left(n-mO\mathrm{i.e}\left(N,M\right)\right)/\lfloor \frac{N}{M}\rfloor \right)& OtHe\mathrm{right}wise\end{array}$

$$

pictured.

In one embodiment, a DCI can schedule a PDSCH or a PUSCH carrying only one TB. The TB is segmented into multiple SAUs. Each SAU includes one or more CBs. Symbol alignment is achieved for each SAU. In this case, SLIV can specify the time resource of an SAU in the DCI. The maximum number of SAU of the TB can be designed by high-layer signaling. As an alternative, the maximum length of the allocated time resource for a PDSCH or a PUSCH is designed so that the number of SAU of the TB can be derived from the maximum length and the number of symbols for a SAU. As an additional alternative, the maximum number of SAUs of the current TB in the DCI can be indicated dynamically or by a combination of RRC signaling and dynamic indication by DCI. The transmission of the PDSCH or PUSCH can be terminated at the symbol boundary of a SAU.

One or more SAU can be grouped in a CBG. The number of SAUs for a CBG can be predefined or designed by a high layer. Alternatively, the number of SAUs for a CBG can be indicated dynamically in the DCI or by a combination of RRC signaling and dynamic indication by DCI. The last CBG before the transmission ends may have a smaller number of SAUs. Alternatively, the SAU(s) that make up a CBG can be determined by the total number of SAUs and the number of CBGs.

abgebildet.The maximum number of SAU is denoted as N, the maximum number of CBG, e.g. B. Maximum number of HARQ ACK bits per TB is M, the N SAUs are mapped to the M CBGs. If the N SAUs cannot be evenly grouped and mapped to M CBGs, the last CBG(s) may be composed of a slightly smaller or larger number of SAUs. The evenly distributed th SAUs, if any, can be mapped to the same CBG, e.g. e.g., SAU n is mapped to CBG b _n = moden, M), n = 0,1,...,N-1. Alternatively, the consecutive SAUs, if any, can be mapped to the same CBG, e.g. B. SAU becomes n on CBG $b_n=\{\begin{array}{cc}flOO\mathrm{right}\left(n/\lceil \frac{N}{M}\rceil \right)& n<mO\mathrm{i.e}\left(N,M\right)\cdot \lceil \frac{N}{M}\rceil \\ flOO\mathrm{right}\left(\left(n-mO\mathrm{i.e}\left(N,M\right)\right)/\lfloor \frac{N}{M}\rfloor \right)& OtHe\mathrm{right}wise\end{array}$

pictured.

6 illustrates the case of a single TB scheduled by a DCI with multiple CBGs. In this case, SLIV indicates the time resource of a SAU, e.g. B. each SAU is mapped to all time/frequency resources of 2 symbols. Symbol alignment is therefore achieved for each SAU. Each CBG consists of 2 consecutive SAUs. For example, if the last 2 SAUs were not transferred due to early termination, the TB will only consist of 3 valid CBGs. However, the UE may still need to report 4 HARQ-ACK bits for the TB to have a constant payload size of HARQ-ACK.

7 illustrates the case of a single TB scheduled by a DCI with multiple CBGs. In this case, SLIV indicates the time resource of a SAU, e.g. B. each SAU is mapped to all time/frequency resources of 2 symbols. Symbol alignment is therefore achieved for each SAU. CBG k consists of 2 SAUs with index k and k+4. For example, if the last 2 SAUs were not transferred due to early termination, the TB will still consist of 4 CBGs. Each CBG has a reduced CBG size. However, the last 2 CBGs only have one CBG each. The 4 HARQ ACK bits reported are all useful indications for the four CBGs.

A UE can generate a HARQ-ACK for each CBG for the HARQ-ACK feedback. This can limit the number of HARQ ACK bits reported per TB. For example, the maximum number of HARQ ACK bits per TB is 8. To schedule a TB retransmission, a CBG Transmission Indicator (CBGTI) can be used to indicate retransmission or not for each CBG. For example, if the kth bit of CBGTI is "1", a retransmission of the kth CBG is scheduled.

Multiple TB schedules without CBG through a DCI

A DCI can schedule a transfer to transport one or more TBs. However, it can be assumed that a CBG-based transmission may not be supported or interpreted.

abgebildet.A UE can generate a HARQ-ACK for each TB for the HARQ-ACK feedback. Alternatively, HARQ ACK bundling of TBs can be used to limit the number of HARQ ACK bits. For example, the maximum number of HARQ ACK bits per TB is 8. The maximum number of TBs is denoted as N, the maximum number of HARQ ACK bits per TB is M, the N TBs are mapped to the M HARQ ACK -Bits pictured. If the N TBs cannot be grouped evenly and mapped to M HARQ ACK bits, the last group(s) may be composed of a slightly smaller or larger number of TBs. The evenly distributed TBs, if any, can be mapped to the same HARQ ACK bit, e.g. TB n is mapped to the HARQ ACK bit b _n = mod (n,M), n=0,1,...,N-1. Alternatively, the consecutive TBs, if any, can be mapped to the same HARQ ACK bit, e.g. B. becomes TB n on that $HARQ-ACK-Bit{b}_n=\{\begin{array}{cc}flOO\mathrm{right}\left(n/\lceil \frac{N}{M}\rceil \right)& n<mO\mathrm{i.e}\left(N,M\right)\cdot \lceil \frac{N}{M}\rceil \\ flOO\mathrm{right}\left(\left(n-mO\mathrm{i.e}\left(N,M\right)\right)/\lfloor \frac{N}{M}\rfloor \right)& OtHe\mathrm{right}wise\end{array}$

pictured.

The number of NDI/RV bits in the DCI is equal to the maximum number of TBs scheduled by the DCI. The HARQ process number specified by the DCI may apply to the first scheduled TB by the DCI, while the sequential HARQ process number after the specified HARQ process number is used in other scheduled TBs by the DCI.

In one embodiment, symbol alignment is accomplished for each TB. In this case, SLIV can specify the time resource of a TB in the DCI. The maximum number of TBs of transmission can be designed by high-layer signaling. Or the maximum length of the allocated time resource is designed for a PDSCH or a PUSCH, so the maximum number of TBs of transmission can be derived from the maximum length and the number of symbols for a TB. Alternatively, the maximum number of TBs of current transfer in the DCI can be indicated dynamically or by a combination of RRC signaling and dynamic indication by DCI. The transmission of the PDSCH or PUSCH can be terminated at the symbol boundary of a TB.

In one embodiment, symbol alignment is accomplished for each SAU. SLIV in the DCI can indicate the time resource of a SAU. The maximum number of SAUs of transmission can be designed by high-layer signalling. Or the maximum length of the allocated time resource is designed for a PDSCH or a PUSCH, so the number of SAU can be derived from the maximum length and the number of symbols in a SAU. Alternatively, the maximum number of SAUs of the current transmission in the DCI can be indicated dynamically or by a combination of RRC signaling and dynamic indication by DCI. The transmission of the PDSCH or PUSCH can be terminated at the symbol boundary of a SAU.

abgebildet. Alternativ können die gleichmäßig verteilten SAUs, falls vorhanden, auf den gleichen TB abgebildet werden, z. B. wird SAU n auf TBb_n = moden, M), n = 0,1, ..., N - 1 abgebildet.One or more SAU can be grouped in a TB. The number of SAUs for a TB can be predefined or designed by a high layer. Alternatively, the number of SAUs for a TB can be dynamically specified in the DCI. The last TB before the transmission ends may have a smaller number of SAUs. Alternatively, the SAU(s) included in a TB can be determined by the number of SAUs and the number of TBs. The maximum number of SAU is denoted as N, the maximum number of TB, e.g. B. Maximum number of HARQ ACK bits per transmission is M, the N SAUs are mapped to the M TBs. If the N SAUs cannot be evenly grouped and mapped to M TBs, the last TB(s) may be composed of a slightly smaller or larger number of SAUs. The consecutive SAUs, if any, can be mapped to the same TB, e.g. B. SAU n becomes on TB $b_n=\{\begin{array}{cc}flOO\mathrm{right}\left(n/\lceil \frac{N}{M}\rceil \right)& n<mO\mathrm{i.e}\left(N,M\right)\cdot \lceil \frac{N}{M}\rceil \\ flOO\mathrm{right}\left(\left(n-mO\mathrm{i.e}\left(N,M\right)\right)/\lfloor \frac{N}{M}\rfloor \right)& OtHe\mathrm{right}wise\end{array}$

pictured. Alternatively, the evenly distributed SAUs, if any, can be mapped to the same TB, e.g. B. SAU n is mapped to TBb _n = moden, M), n = 0,1, ..., N - 1.

8th illustrates an example of how a DCI schedules two TBs. In this case, SLIV indicates the time resource of a SAU, e.g. B. each SAU is mapped to all time/frequency resources of 2 symbols. Symbol alignment is therefore achieved for each SAU. Each CBG consists of 4 consecutive SAUs. For example, if the last 4 SAUs were not transmitted due to premature termination, only 1 TB is transmitted in the current transmission. However, the UE may still need to report 2 HARQ-ACK bits for the two TBs to have a constant payload size of HARQ-ACK.

9 illustrates another example of how a DCI schedules two TBs. In this case, SLIV indicates the time resource of a SAU, e.g. B. each SAU is mapped to all time/frequency resources of 2 symbols. Symbol alignment is therefore achieved for each SAU. TB k consists of 4 SAUs with index k, k+2, k+4, k+6. For example, if the last 4 SAUs were not transmitted due to premature termination, two TBs will still be transmitted in the current transmission. Each TB has a reduced TB size. The 2 HARQ ACK bits reported are all useful indications for the 2 TBs.

Multiple TB scheduling with CBG by a DCI

A DCI can schedule a transfer to transport one or more TBs. Further, it is assumed that CBG-based transmission is also designed for each TB.

For the HARQ ACK feedback, the UE can generate a HARQ ACK bit for each CBG. To schedule a retransmission of the TB, a CBG Transmission Indicator (CBGTI) can be used to indicate retransmission for each CBG of a retransmitted TB or not. For example, if the kth bit of CBGTI is "1", a retransmission of the kth CBG is scheduled.

The number of NDI/RV bits in the DCI equals the maximum number of TBs scheduled by the DCI. The HARQ process number specified by the DCI may apply to the first scheduled TB by the DCI, while the sequential HARQ process number after the specified HARQ process number is used in other scheduled TBs by the DCI.

In one embodiment, symbol alignment is accomplished for each TB. SLIV in the DCI can indicate the time resource of a TB. The maximum number of TBs of transmission can be designed by high-layer signaling. Or the maximum length of the allocated time resource is designed for a PDSCH or a PUSCH, so the maximum number of TBs of transmission can be derived from the maximum length and the number of symbols for a TB. Alternatively, the maximum number of TBs of current transfer in the DCI can be indicated dynamically or by a combination of RRC signaling and dynamic indication by DCI. The transmission of the PDSCH or PUSCH can be terminated at the symbol boundary of a TB.

In one embodiment, symbol alignment is accomplished for each CBG. Each CBG contains one or more CBs. SLIV in the DCI can indicate the time resource of a CBG. The maximum number of CBGs of the transmission can be designed by high-layer signalling. Or the maximum length of the allocated time resource is designed for a PDSCH or a PUSCH, so the maximum number of CBGs of the transmission can be derived from the maximum length and the number of symbols for a CBG. Alternatively, the maximum number of CBGs of the current transmission in the DCI can be indicated dynamically or by a combination of RRC signaling and dynamic indication by DCI. The transmission of the PDSCH or PUSCH can be terminated at the symbol boundary of a CBG.

$$

abgebildet.One or more CBGs can be grouped in a TB. The number of CBGs for a TB can be predefined or designed by a high layer. Alternatively, the number of CBGs for a TB can be specified dynamically in the DCI or by a combination of RRC signaling and dynamic indication by DCI. The last TB before the transmission ends may have a smaller number of CBGs. Alternatively, the CBG(s) included in a TB can be determined by the number of CBGs and the number of TBs. The maximum number of CBGs is denoted as N, the maximum number of TBs is M, the N CBGs are mapped to the M TBs. If the N CBGs cannot be evenly grouped and mapped to M TBs, the last TB(s) may be composed of a slightly smaller or larger number of CBGs. The evenly distributed CBGs, if any, can be mapped to the same TB, e.g. e.g., CBG n is mapped to TB b _n = moden, M), n = 0,1,...,N-1. Alternatively, the consecutive CBGs, if any, can be mapped to the same TB, e.g. B. CBG n becomes TB $b_n=\{\begin{array}{cc}flOO\mathrm{right}\left(n/\lceil \frac{N}{M}\rceil \right)& n<mO\mathrm{i.e}\left(N,M\right)\cdot \lceil \frac{N}{M}\rceil \\ flOO\mathrm{right}\left(\left(n-mO\mathrm{i.e}\left(N,M\right)\right)/\lfloor \frac{N}{M}\rfloor \right)& OtHe\mathrm{right}wise\end{array}$

$$

pictured.

10 illustrates an example of how a DCI schedules two TBs. In this case, SLIV specifies the time resource of a CBG, e.g. B. each CBG is mapped to all time/frequency resources of 2 symbols. Symbol alignment is therefore achieved for each CBG. Each TB consists of 4 consecutive CBGs. For example, if the last 4 CBGs were not transmitted due to premature termination, only 1 TB will be transmitted in the current transmission. However, the UE may still need to report 8 HARQ-ACK bits for the two TBs to have a constant payload size of HARQ-ACK.

11 illustrates an example of how a DCI schedules two TBs. In this case, SLIV specifies the time resource of a CBG, e.g. B. each CBG is mapped to all time/frequency resources of 2 symbols. Symbol alignment is therefore achieved for each CBG. Each TB consists of 4 consecutive CBGs. TB k consists of 4 SAUs with index k, k+2, k+4, k+6. For example, if the last 4 CBGs were not transmitted due to premature termination, two TBs will still be transmitted in the current transmission. Each TB has a reduced number of CBGs. However, the UE may still need to report 8 HARQ-ACK bits for the two TBs to have a constant payload size of HARQ-ACK.

In one embodiment, symbol alignment is accomplished for each SAU. SLIV in the DCI can indicate the time resource of a SAU. The maximum number of SAUs of transmission can be designed by high-layer signalling. Or the maximum length of the allocated time resource is designed for a PDSCH or a PUSCH, so the maximum number of SAUs of the transmission can be derived from the maximum length and the number of symbols for a SAU. Alternatively, the maximum number of SAUs of the current transmission in the DCI can be indicated dynamically or by a combination of RRC signaling and dynamic indication by DCI. The transmission of the PDSCH or PUSCH can be terminated at the symbol boundary of a SAU.

$$

abgebildet.One or more SAU can be grouped in a CBG. The number of SAUs for a CBG can be predefined or designed by a high layer. Alternatively, the number of SAUs for a CBG can be dynamically specified in the DCI. The last CBG before the transmission ends may have a smaller number of SAUs. Alternatively, the SAU(s) included in a CBG can be determined by the number of SAUs and the number of CBGs. The maximum number of SAU is denoted as N, the maximum number of CBG, e.g. B. Maximum number of HARQ ACK bits per TB is M, the N SAUs are mapped to the M CBGs. If the N SAUs cannot be evenly grouped and mapped to M CBGs, the last CBG(s) may be composed of a slightly smaller or larger number of SAUs. The consecutive SAUs, if any, can be mapped to the same CBG, e.g. B. SAU becomes n on CBG $b_n=\{\begin{array}{cc}flOO\mathrm{right}\left(n/\lceil \frac{N}{M}\rceil \right)& n<mO\mathrm{i.e}\left(N,M\right)\cdot \lceil \frac{N}{M}\rceil \\ flOO\mathrm{right}\left(\left(n-mO\mathrm{i.e}\left(N,M\right)\right)/\lfloor \frac{N}{M}\rfloor \right)& OtHe\mathrm{right}wise\end{array}$

$$

pictured.

Alternatively, the evenly distributed SAUs, if any, can be mapped onto the same CBG, e.g. e.g., SAU n is mapped to CBGb _n = moden, M), n = 0,1,...,N-1.

CONTROL CHANNEL TRANSMISSION FOR NO-SLOT OPERATION

NR supports the downlink physical control channel (PDCCH) that conveys the scheduling decision for both DL and UL over DCI. PDCCH is sent over a control resource record (CORESET). CORESETs can be laid out in units of six PRBs (e.g. with a PRB containing 12 resource elements) in the frequency domain and one, two or three consecutive orthogonal frequency division multiplex (OFDM) symbols in the time domain. The corresponding parameters are designed for the UE using frequencyDomainResources and duration parameters. An example of a control resource set configuration is as follows:

In CORESET, a resource element group (REG) can consist of a resource block and an OFDM symbol in the time domain. A control channel element (CCE) can consist of six REGs. The actual number of CCEs for a PDCCH is determined by the PDCCH aggregation level. The UE performs a blind decoding of the PDCCH for the specific set of CCEs designated as a search space (SS). 5G NR supports two SS sentence types: common SS (CSS) sentence, traditionally monitored by a group of UEs in the cell, and UE-specific SS (USS) sentence, monitored by a single UE.

The UE specific search space is laid out by RRC. The monitored positions of the PDCCH are defined by a monitoringSchlitzPeriodicityAndOffset parameter, which conveys information about the periodicity of the monitoring as well as the slot offset. An example search space configuration is as follows:

NR supports conventional slot-level based planning, referred to as Type-A mapping in 5G NR. Slot-level transmission can only start at a specific OFDM symbol, but has a flexible duration of up to 14 OFDM symbols within a slot. Type-A mapping typically has a relatively long transmission time interval, which helps reduce reference signal and control channel overhead as well as increase coverage. However, conventional slot-level planning is not efficient for all deployment scenarios. For example, for 5G NR operation in an unlicensed spectrum (NR-U), it is necessary to start transmission as early as possible after Listen Before Talk (LBT). In the case of mmWave, a high payload transmission can already be realized within a few OFDM symbols due to the use of large bandwidth sizes. Finally, in the case of low-latency transmission required for time-critical data applications, it is advantageous to start transmission on any OFDM symbol without restrictions. To optimize system performance for such deployment scenarios, 5G NR also supports mini-slot-based transmission called Type-B mapping in addition to slot-based scheduling. Minislot-based scheduling allows transmission of a physical shared channel to start at any OFDM symbol within a slot and have a flexible duration of two, four, or seven OFDM symbols. To enable early decoding in minislot based scheduling, the control channel and reference signals are at the beginning of the transmission.

To provide further flexibility to the scheduling procedure, future systems may support more flexible duration transmission spanning a large number of OFDM symbols spanning multiple slots. The actual duration of the transmission may be variable and not aligned with the periodicity of PDCCH monitoring opportunities. As a result, unused time gaps can occur between the last symbol of the PDSCH transmission and the next PDCCH transmission opportunity. The problem is in 12 illustrated in detail.

Accordingly, in previous schemes, control channel transmission is only possible at a specific location designed by RRC. For a PDSCH transmission with more flexible duration, unused time gaps can occur between the last symbol of the PDSCH transmission and the next PDCCH transmission opportunity.

Various embodiments herein provide techniques for PDCCH transmission at a more dynamic time location relative to the scheduled PDSCH. Embodiments can be adopted in future specifications that support flexible PDSCH transmission.

According to some embodiments, additional flexible PDCCH monitoring opportunities can be defined from OFDM/DFT-s-OFDM (Discrete Fourier Transform Spread OFDM) symbol followed by a last symbol of the PDSCH transmission. It should be noted that the transmission duration of the PDSCH can be designed by higher layers, dynamically indicated by MAC-CE or indicated by DCI carried by a first PDCCH. Furthermore, in case of early termination of the PDSCH transmission, the UE can start to monitor the PDCCH after the last symbol of the PDSCH transmission after the early termination.

The techniques described herein provide an additional PDCCH transmission opportunity with a flexible/dynamic position compared to PDCCH monitoring opportunities laid out by higher layers. As a result, PDSCHs can be scheduled in a contiguous manner (avoiding idle symbols), as in 13 is illustrated.

In another example, the additional PDCCH monitoring opportunities can start at X > 0 symbols after the last symbol of the PDSCH, as in FIG 14 is shown. In another option, an additional flexible PDCCH monitoring opportunity can be indicated by a first PDCCH scheduling the PDSCH transmission.

• • Eine Kollision zwischen PDSCH, der durch einen zusätzlichen PDCCH geplant wird, und PDCCH-Überwachungsgelegenheit, die durch RRC ausgelegt wird; und/oder
• • Kollision zwischen zusätzlichem PDCCH und PDCCH-Überwachungsgelegenheit, die durch RRC ausgelegt ist.

It should be noted that due to a more flexible PDCCH position, the additional physical channel collisions may occur. For example:

• • A collision between PDSCH scheduled by an additional PDCCH and PDCCH monitoring opportunity laid out by RRC; and or
• • Collision between additional PDCCH and PDCCH monitoring opportunity laid out by RRC.

For the first collision example, e.g. B., PDSCH scheduled by an additional PDCCH may collide with a PDCCH monitoring opportunity designed by RRC should the priorities for the processing of the physical channels be defined. For example, the UE can assume that the PDSCH transmission is prioritized in the corresponding OFDM symbols and a potential PDCCH is discarded. In another example, the UE may assume that PDCCH monitoring is prioritized and PDSCH transmission in the corresponding symbols is discarded or rate matching around the PDCCH transmission around the corresponding PDCCH monitoring opportunity.

In another example, if the PDSCH transmission uses a different Transmission Control Indicator (TCI) state (beam) from the RRC designed PDCCH and the UE has the capability to receive two or more TCI states (beams), the UE can use the recognize PDCCH laid out by RRC and at the same time perform PDSCH reception.

For the second collision example, e.g. B. a collision of an additional PDCCH with a PDCCH monitoring opportunity designed by RRC, the priorities for processing the physical channels should be defined. In one example, more priority is given to monitoring the additional PDCCH compared to the RRC designed PDCCH. In another example, more priority is given to monitoring the PDCCH designed by RRC compared to the additional PDCCH. In another example, the priority is given by the associated ID of the CORESET.

In another example, if the additional PDCCH uses a different TCI state (beam) than the PDCCH designed by RRC and the UE has the capability to receive two or more TCI states (beams), the UE can both recognize the additional PDCCH as well as the PDCCH laid out by RRC at the same time.

SYSTEMS AND IMPLEMENTATIONS

15 until 17 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

15 15 illustrates a network 1500 according to various embodiments. The network 1500 can operate in a manner that is compliant with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems or the like.

The network 1500 may include a UE 1502, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1504 over an over-the-air connection. The UE 1502 may include a smartphone, a tablet computer, a wearable computer, a desktop computer, a laptop computer, an in-vehicle infotainment system, an in-vehicle entertainment system, an instrument cluster, a head-up display device, a Onboard diagnostic device, mobile dashboard device, mobile terminal device, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked device, machine type communication device , an M2M or D2D device, an IoT device, etc.

In some embodiments, network 1500 may include multiple UEs that are directly coupled to each other via a sidelink interface. The UEs may be M2M/D2D devices that communicate using Physical Sidelink Channels such as PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc., among others.

In some embodiments, the UE 1502 may additionally communicate with an AP 1506 via an over-the-air connection. The AP 1506 can manage a WLAN connection, which can be used to offload some/all network traffic from the RAN 1504 . The connection between the UE 1502 and the AP 1506 may be consistent with any IEEE 802.11 protocol, where the AP 1506 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 1502, the RAN 1504, and the AP 1506 may utilize cellular WLAN aggregation (e.g., LWA/LWIP). Cellular WLAN aggregation may involve the UE 1502 being configured by the RAN 1504 to utilize both cellular radio resources and WLAN resources.

The RAN 1504 may include one or more access nodes, such as the AN 1508. The AN 1508 can terminate air interface protocols for the UE 1502 by providing access stratum protocols including RRC, PDCP, RLC, MAC and L1 protocols. In this way, the AN 1508 can enable data/voice connectivity between the CN 1520 and the UE 1502. In some embodiments, AN 1508 may be implemented in a discrete device or as one or more software entities running on server computers, for example, as part of a virtual network, which may be referred to as a CRAN or baseband unit virtual pool. The AN 1508 can be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 1508 may be a macrocell base station or a low power base station for providing femtocells, picocells, or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macrocells.

In embodiments where the RAN 1504 includes multiple ANs, they may be coupled together via an X2 interface (if the RAN 1504 is an LTE RAN) or an Xn interface (if the RAN 1504 is a 5G RAN). The X2/Xn interfaces, which in some embodiments may be separated into control/user plane interfaces, may allow ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, and so on.

The ANs of the RAN 1504 can each manage one or more cells, cell groups, component carriers, etc. to provide the UE 1502 with an air interface for network access. The UE 1502 may be simultaneously connected to a plurality of cells provided by the same or different RAN 1504 ANs. For example, the UE 1502 and the RAN 1504 may use carrier aggregation to allow the UE 1502 to communicate with a variety of components like to connect, each corresponding to a pcell or scell. In dual connectivity scenarios, a first AN may be a master node providing an MCG and a second AN may be a secondary node providing an SCG. The first/second AN can be any combination of eNB, gNB, ng-eNB, etc.

The RAN 1504 can provide the air interface over licensed spectrum or unlicensed spectrum. To operate in the unlicensed spectrum, the nodes can use LAA, eLAA and/or feLAA mechanisms based on CA technology with PCells/Scells. Before accessing the unlicensed spectrum, the nodes may perform medium/carrier acquisition operations based on, for example, a Listen Before Talk (LBT) protocol.

In V2X scenarios, the UE 1502 or AN 1508 may be or act as an RSU, which may refer to any transport infrastructure entity used for V2X communications. An RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. RSU implemented in or by: a UE may be referred to as a "UE-type RSU"; an eNB may be referred to as an "eNB-type RSU"; a gNB may be referred to as a "gNB-type RSU"; and the same. In one example, an RSU is a computing device coupled to radio frequency circuitry located at a roadside that provides connectivity support for passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, and applications/software to capture and control ongoing vehicle and pedestrian traffic. The RSU can provide very low latency communications required for high speed events such as crash avoidance, traffic alerts, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communication services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired (e.g., Ethernet) connection to a traffic signal controller or backhaul network.

In some embodiments, the RAN 1504 may be an LTE RAN 1510 with eNBs, for example the eNB 1512. The LTE-RAN 1510 can provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; Turbo codes for data and TBCC for control etc. The LTE air interface can be switched to CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH-DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial detection, channel quality measurements and channel estimation for coherent demodulation/detection at the UE. The LTE air interface can work on sub-6 GHz bands.

In some embodiments, the RAN 1504 may be an NG-RAN 1514 with gNBs, e.g. gNB 1516 or ng-eNBs, e.g. the ng-eNB 1518. The gNB 1516 can connect to 5G-enabled UEs using a 5G NR interface. The gNB 1516 can connect to a 5G core via an NG interface, which can include an N2 interface or an N3 interface. The ng-eNB 1518 can also connect to the 5G core via an NG interface, but can connect to a UE via an LTE air interface. The gNB 1516 and the ng-eNB 1518 can connect to each other via an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface that carries traffic data between the nodes of the NG RAN 1514 and a UPF 1548 (e.g., N3 interface). , and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG RAN 1514 and an AMF 1544 (e.g., N2 interface).

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

In some embodiments, the 5G NR air interface may utilize BWPs for various purposes. For example, BWP can be used to dynamically adjust the SCS. For example, the UE 1502 may be configured with multiple BWPs, with each BWP configuration having a different SCS. When a BWP change is indicated to the UE 1502, the SCS of the transmission is also changed. Another use case example for BWP is related to power conservation. In particular, multiple BWPs can be designed for the UE 1502 with a different amount of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP containing a reduced number of PRBs can be used for data transmission with low traffic load while allowing power savings at the UE 1502 and in some cases at the gNB 1516. A BWP containing a larger number of PRBs can be used for higher traffic load scenarios.

The RAN 1504 is communicatively coupled to the CN 1520, which includes network elements to provide various functions to support data and telecommunications services for customers/subscribers (e.g., users of the UE 1502). The components of the CN 1520 can be implemented in one physical node or separate physical nodes. In some embodiments, NFV can be used to virtualize any or all of the functions provided by the network elements of CN 1520 onto physical compute/storage resources in servers, switches, and so on. A logical instantiation of CN 1520 may be referred to as a network slice, and a logical instantiation of a portion of CN 1520 may be referred to as a network sub-slice.

In some embodiments, the CN 1520 may be an LTE CN 1522, which may also be referred to as an EPC. The LTE-CN 1522 may include MME 1524, SGW 1526, SGSN 1528, HSS 1530, PGW 1532, and PCRF 1534 coupled together via interfaces (or "reference points") as shown. Functions of the elements of the LTE-CN 1522 can be briefly introduced as follows.

The MME 1524 may implement mobility management functions to track a current location of the UE 1502 to enable paging, bearer activation/deactivation, handovers, gateway selection, authentication, and so on.

The SGW 1526 can terminate an S1 interface towards the RAN and route data packets between the RAN and the LTE CN 1522. The SGW 1526 can be a local mobility anchor for inter-RAN node handover and can also provide an anchor for inter-3GPP mobility. Other jurisdictions may include lawful interception, billing, and some policy enforcement.

The SGSN 1528 can track a location of the UE 1502 and perform security functions and admission control. In addition, the SGSN 1528 can provide inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 1524; Perform MME selection for handovers etc. The S3 reference point between the MME 1524 and the SGSN 1528 can enable user and bearer information exchange for Inter-3GPP access network mobility in idle/active states.

The HSS 1530 may include a network user database that includes subscription-related information to support the network entities' handling of communication sessions. The HSS 1530 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 1530 and the MME 1524 may enable the transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 1520.

The PGW 1532 may terminate an SGi interface to a data network (DN) 1536 that may include an application/content server 1538 . The PGW 1532 can route data packets between the LTE-CN 1522 and the data network 1536. The PGW 1532 may be coupled to the SGW 1526 through an S5 reference point to enable user-level tunneling and tunnel management. The PGW 1532 may also include a policy enforcement and billing data collection node (e.g., PCEF). In addition, the SGi reference point between PGW 1532 and data network 1536 may be an off-carrier public, a private PDN, or an on-carrier packet data network, for example to provide IMS services. The PGW 1532 may be coupled to a PCRF 1534 via a Gx reference point.

The PCRF 1534 is the policy and charging control element of the LTE-CN 1522. The PCRF 1534 may be communicatively coupled to the app/content server 1538 to determine appropriate QoS and charging parameters for service flows. The PCRF 1532 can provide associated rules into a PCEF (via a Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 1520 may be a 5GC 1540. The 5GC 1540 may include an AUSF 1542, AMF 1544, SMF 1546, UPF 1548, NSSF 1550, NEF 1552, NRF 1554, PCF 1556, UDM 1558, and AF 1560 that interface with each other (or "reference points") as shown are coupled. Functions of the elements of the 5GC 1540 can be briefly introduced as follows.

The AUSF 1542 may store data for authentication of the UE 1502 and handle authentication related functionality. The AUSF 1542 can enable a common authentication framework for different access types. In addition to communicating with other elements of the 5GC 1540 via reference points as shown, the AUSF 1542 may have a NausF service-based interface.

The AMF 1544 may allow other functions of the 5GC 1540 to communicate with the UE 1502 and the RAN 1504 and subscribe to notifications of mobility events related to the UE 1502. The AMF 1544 may also be responsible for registration management (e.g. for registering the UE 1502), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 1544 can provide transport for SM messages between the UE 1502 and the SMF 1546 and acts as a transparent proxy for routing SM messages. The AMF 1544 can also provide transport for SMS MESSAGES between the UE 1502 and an SMSF. AMF 1544 may interact with AUSF 1542 and UE 1502 to perform various security anchor and context management functions. Furthermore, the AMF 1544 may be an endpoint of a RAN-CP interface, which may include or be an N2 reference point between the RAN 1504 and the AMF 1544; and the AMF 1544 can be a termination point of NAS (N1) signaling and perform NAS encryption and integrity protection. The AMF 1544 can also support NAS signaling with the UE 1502 over an N3 IWF interface.

The SMF 1546 may be responsible for SM (e.g. session establishment, tunnel management between the UPF 1548 and an AN 1508); UE IP address allocation and management (including optional authorization); selection and control of a UP function; configure traffic routing at UPF 1548 to route traffic to an appropriate destination; completion of interfaces to policy control functions; Controlling some policy enforcement, billing, and QoS; lawful interception (for SM events and interface to LI system); Completion of SM parts of NAS messages; downlink data notification; initiating specific SM information sent via AMF 1544 via N2 to AN 1508; and determining an SSC mode of a session. SM can refer to the management of a PDU session, and a PDU session or "session" can refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 1502 and the data network 1536 .

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

The NSSF 1550 can select a set of network slice entities that serve the UE 1502. The NSSF 1550 can also determine permissible NSSAI and the mapping to the subscribed S-NSSAIs, if necessary. The NSSF 1550 may also determine an AMF set to be used to serve the UE 1502 or a list of candidate AMFs based on appropriate configuration and possibly by querying the NRF 1554 . The selection of a set of network slice entities for the UE 1502 can be triggered by the AMF 1544 with which the UE 1502 is registered, by interacting with the NSSF 1550, which can result in a change in the AMF. The NSSF 1550 can interact with the AMF 1544 via an N22 reference point; and can communicate with another NSSF in a visited network via an N31 reference point (not shown). In addition, the NSSF 1550 may have a service-based Nnssf interface.

The NEF 1552 can securely discover services and capabilities provided by 3GPP network functions for third parties, internal discovery/rediscovery, AFs (e.g. AF 1560), edge computing or fog computing systems, etc. In such embodiments, the NEF 1552 may authenticate, authorize, or throttle the AFs. The NEF 1552 can also translate information exchanged with the AF 1560 and information exchanged with internal network functions. For example, the NEF 1552 can translate between an AF service identifier and internal 5 GC information. The NEF 1552 may also receive information from other NFs based on revealed capabilities of other NFs. This information can be stored at the NEF 1552 as structured data or at a data storage NF using standardized interfaces. The stored information can then be rediscovered by the NEF 1552 other NFs and AFs or used for other purposes such as analytics. In addition, the NEF 1552 may have a service-based Nnef interface.

The NRF 1554 may support service discovery functions, receive NF discovery requests from NF entities, and provide the information of the discovered NF entities to the NF entities. The NRF 1554 also holds information of available NF entities and their supported services. As used herein, the terms "instantiate," "instantiation," and the like may refer to the creation of an instance, and "instance" may refer to a tangible occurrence of an object that may occur, for example, during the execution of program code. In addition, the NRF 1554 may have a service-based Nrf interface.

The PCF 1556 can provide policy rules to control layer functions to enforce them, and can also support a unified policy framework to govern network behavior. The PCF 1556 may also implement a front end to access subscription information relevant to policy decisions in a UDM 1558 UDR. In addition to communicating with functions via reference points as shown, the PCF 1556 has a service-based Npcf interface.

The UDM 1558 may handle subscription-related information to support the handling of communication sessions by the network entities and may store UE 1502 subscription data. For example, subscription data can be communicated between the UDM 1558 and the AMF 1544 via an N8 reference point. The UDM 1558 can include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 1558 and the PCF 1556 and/or structured data for discovery and application data (including PFDs for application detection, application request information for multiple UEs 1502) for the NEF 1552. The service-based Nudr interface may be exhibited by the UDR 221 to allow the UDM 1558, the PCF 1556 and the NEF 1552 to access a specific set of stored data, as well as to read notification of relevant data changes in the UDR update (e.g. add, modify), delete and subscribe. The UDM may include a UDM FE responsible for credential processing, location management, subscription management, and so on. Several different frontends can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown, the UDM 1558 may have the Nudm service-based interface.

The AF 1560 can provide application influence on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

In some embodiments, the 5GC 1540 may enable edge computing by selecting the operator/third party service provider to be geographically close to a point where the UE 1502 is connected to the network. This can reduce latency and load on the network. To provide edge computing implementations, the 5GC 1540 may select a UPF 1548 near the UE 1502 and route traffic from the UPF 1548 to the data network 1536 over the N6 run interface. This may be based on the UE subscription data, UE location and information provided by the AF 1560. In this way, the AF 1560 can affect UPF (Re)selection and traffic routing. Based on the operator deployment, if the AF 1560 is considered a trusted entity, the network operator can allow the AF 1560 to directly interact with relevant NFs. Additionally, the AF 1560 may have a service-based Naf interface.

Data network 1536 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including application/content server 1538, for example.

16 16 schematically illustrates a wireless network 1600 according to various embodiments. The wireless network 1600 may include a UE 1602 in wireless communication with an AN 1604 . The UE 1602 and AN 1604 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

The UE 1602 may be communicatively coupled to the AN 1604 via link 1606 . Link 1606 is illustrated as an air interface to enable communicative coupling and may conform to cellular communication protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies.

The UE 1602 may include a host platform 1608 coupled to a modem platform 1610 . Host platform 1608 may include application processing circuitry 1612 that may be coupled to protocol processing circuitry 1614 of modem platform 1610 . The application processing circuitry 1612 may execute various applications for the UE 1602 that yield/ingest application data. Application processing circuitry 1612 may also implement one or more layered operations to transmit/receive application data to/from a data network. These layer operations may include transport (e.g. UDP) operations and Internet (e.g. IP) operations.

Protocol processing circuitry 1614 may implement one or more layer operations to enable transmission or reception of data over link 1606 . The layer operations implemented by the protocol processing circuitry 1614 may include MAC, RLC, PDCP, RRC, and NAS operations, for example.

The modem platform 1610 may further include digital baseband circuitry 1616 that may implement one or more layer operations that are "below" layer operations performed by the protocol processing circuitry 1614 in a 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, receive symbol/bit metric determination, multi-antenna port precoding/decoding, which may involve one or more of spatiotemporal, spatial frequency, or spatial encoding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

The modem platform 1610 may further include transmit circuitry 1618, receive circuitry 1620, RF circuitry 1622, and RF front end (RFFE) 1624, which may include or be connected to one or more antenna arrays 1626. Briefly, transmit circuitry 1618 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc.; receive circuitry 1620 may include analog-to-digital converters, mixers, IF components, etc.; RF circuitry 1622 may include a low noise amplifier, a power amplifier, power tracking components, etc.; RFFE 1624 may include filters (e.g., surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), and so on. The selection and arrangement of the components of transmit circuitry 1618, receive circuitry 1620, RF circuitry 1622, RFFE 1624, and antenna arrays 1626 (commonly referred to as "transmit/receive components") may be specific to details of a specific implementation, such as whether the communication is TDM or FDM, in mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit/receive components may be in multiple parallel Transmit/receive chains may be located on the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 1614 may include one or more instances of control circuitry (not shown) for providing control functions to the transmit/receive components.

UE reception may be established through and through antenna panels 1626, RFFE 1624, RF circuitry 1622, receive circuitry 1620, digital baseband circuitry 1616, and protocol processing circuitry 1614. In some embodiments, the antenna panels 1626 may receive a transmission from the AN 1604 through receive beamforming signals received by multiple antennas/antenna elements of the one or more antenna panels 1626 .

UE transmission may be established through and via protocol processing circuitry 1614, digital baseband circuitry 1616, transmit circuitry 1618, RF circuitry 1622, RFFE 1624, and antenna panels 1626. In some embodiments, the transmit components of the UE 1604 may apply a spatial filter to the data to be transmitted to form a transmit beam that is emitted by the antenna elements of the antenna panels 1626 .

Similar to the UE 1602, the AN 1604 may include a host platform 1628 coupled to a modem platform 1630. Host platform 1628 may include application processing circuitry 1632 coupled to protocol processing circuitry 1634 of modem platform 1630 . The modem platform may further include digital baseband circuitry 1636, transmit circuitry 1638, receive circuitry 1640, RF circuitry 1642, RFFE circuitry 1644, and the antenna panels 1646. The components of the AN 1604 may be similar to, and substantially interchangeable with, the like-named components of the UE 1602. In addition to performing data transmission/reception as described above, the AN 1608 components 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.

17 12 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some embodiments. In particular shows 17 17 is a schematic representation of hardware resources 1700 including one or more processors (or processor cores) 1710, one or more memory/storage devices 1720, and one or more communication resources 1730, each of which may be communicatively coupled via a bus 1740 or other interface circuitry. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 1702 may execute to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1700 .

The processors 1710 may include a processor 1712 and a processor 1714, for example. The processors 1710 can 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 processor (including those discussed herein), or any suitable combination thereof.

Storage/storage devices 1720 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1720 may include any type of volatile, non-volatile, or semi-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory, among others. Read-only memory (EEPROM), flash memory, solid-state memory, etc.

Communications resources 1730 may include interconnect or network interface controls, components, or other suitable devices for communicating with one or more ren peripheral devices 1704 or one or more databases 1706 or other network elements over a network 1708 include. For example, communication resources 1730 may include wired communication components (e.g., to interface via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (e.g., Bluetooth® Low Energy) components, Wi-Fi® Components and other communication components include.

Instructions 1750 may include software, a program, application, applet, app, or other executable code to cause at least any one of processors 1710 to perform one or more of the methodologies discussed herein. Instructions 1750 may reside in whole or in part within at least one of processors 1710 (e.g., within the processor's cache memory), memory/storage devices 1720, or any suitable combination thereof. Furthermore, any portion of instructions 1750 may be transferred to hardware resources 1700 from any combination of peripheral devices 1704 or databases 1706 . Likewise, memory of processors 1710, memory/storage devices 1720, peripheral devices 1704, and databases 1706 are examples of computer-readable and machine-readable media.

EXEMPLARY PROCEDURES

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s) or portions or implementations thereof may be provided by 15-17 or any other figure herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. Such a process 1800 is in 18 shown. For example, the process 1800 may include, at 1802, receiving downlink control information (DCI) to indicate a resource allocation for transmission of a transport block, the resource allocation including one or more code block groups (CBGs) that are mapped to one or more symbol alignment units (SAUs) of a or more symbols are shown.

At 1804, the process 1800 may further include causing transmission or reception of the transport block based on the DCI. In some embodiments, the process 1800 may be performed by a UE or a portion thereof.

19 19 illustrates another process 1900 according to various embodiments. The process may include, at 1902, receiving downlink control information (DCI) to indicate respective resource allocations for two or more transport blocks, the resource allocations including one or more symbol alignment units (SAUs), the SAUs all including time-frequency resources of one or more contain symbols.

At 1904, the process 1900 may further include causing transmission or reception of the transport blocks based on the DCI. In some embodiments, the process 1900 may be performed by a UE or a portion thereof.

20 10 illustrates another process 2000 according to various embodiments. The process 2000 may include, at 2002, encoding, for transmission to a UE, downlink control information (DCI) to indicate a resource allocation for transmission of a transport block, the resource allocation including one or more code block groups (CBGs) that reference one or more symbol alignment units (SAUs) of one or more symbols are depicted.

At 2004, the process 2000 may further include causing the transport block to be transmitted to the UE or receiving the transport block from the UE based on the DCI. In some embodiments, the process 2000 may be performed by a gNB or a portion thereof.

21 FIG. 2 illustrates another process 2100 according to various embodiments. The process 2100 may include, at 2102, encoding, for transmission to a UE, downlink control information (DCI) to indicate respective resource allocations for two or more transport blocks, the resource allocations including one or more symbol alignment units (SAUs), the SAUs all include time-frequency resources of one or more symbols.

At 2104, the process 2100 may further include causing the transport blocks to be transmitted to the UE or receiving the transport blocks from the UE based on the DCI. In some embodiments, the process 2100 may be performed by a gNB or a portion thereof.

22 FIG. 2 illustrates another process 2200 according to various embodiments. In some embodiments, the process 2200 may be performed by a UE or a portion thereof. For example, the process 2200 may include, at 2202, determining a last character of a PDSCH (e.g., a PDSCH received from the UE).

At 2204, the process 2200 may further include determining a PDCCH monitoring opportunity for a PDCCH based on the last symbol of the PDSCH. For example, the PDCCH monitoring opportunity may be determined to begin a number of symbols after the last symbol (e.g., the next symbol after the last symbol, or a different number of symbols after the last symbol).

At 2206, the process 2200 may further include monitoring for a PDCCH in the particular PDCCH monitoring opportunity. In some embodiments, the process may further include receiving the PDCCH in the PDCCH monitoring opportunity. The PDCCH may schedule another communication for the UE, such as a downlink communication (e.g., another PDSCH) and/or an uplink communication (e.g., a PUSCH and/or PUCCH).

23 FIG. 23 illustrates another process 2300 according to various embodiments. In some embodiments, the process 2300 may be performed by a gNB or a portion thereof.

At 2302, the process 2300 may include encoding a PDSCH for transmission (e.g., to a UE).

At 2304, the process may further include determining a PDCCH monitoring opportunity for a PDCCH based on a last symbol of the PDSCH. For example, the PDCCH monitoring opportunity may be determined to begin a number of symbols after the last symbol (e.g., the next symbol after the last symbol, or a different number of symbols after the last symbol).

At 2306, the process may further include encoding the PDCCH for transmission in the particular PDCCH monitoring occasion (e.g., to the UE or another UE). The PDCCH may schedule another communication for a UE, such as a downlink communication (e.g., another PDSCH) and/or an uplink communication (e.g., a PUSCH and/or PUCCH).

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

EXAMPLES

Example 1 may include a wireless communication method for scheduling data transmissions for a carrier frequency above 52.6 GHz.

Example 2 may include the method of example 1 or any other example herein, wherein a CBG is mapped onto all time/frequency resources of certain consecutive symbols.

Example 3 may include the method of example 1 or another example herein, wherein a CBG is mapped to a symbol alignment unit (SAU); or a CBG is mapped to one or more SAUs; or a SAU consists of one or more CBGs.

Example 4 may include the method of example 1 or another example herein, where the start and length indicator (SLIV) in the DCI indicates the time resource of a CBG.

Example 5 may include the method of Example 1 or any other example herein, where SLIV in the DCI indicates the time resource of a SAU.

Example 6 may include the method of Example 1 or any other example herein, supporting early termination of a PDSC or PUSCH transmission with the granularity of a TB, a CBG, or a SAU.

Example 7 may include the method of Example 1 or any other example herein, where a DCI schedules a PDSCH or a PUSCH carrying only one TB with multiple CBGs.

Example 8 may include the method of Example 7 or any other example herein, where SLIV in the DCI indicates the time resource of a CBG.

Example 9 may include the method of Example 1 or another example herein, where a DCI schedules a PDSCH or a PUSCH carrying only a TB with one or more SAUs.

Example 10 may include the method of Example 9 or any other example herein, where SLIV in the DCI indicates the time resource of a SAU.

Example 11 may include the method of example 10 or any other example herein, wherein the evenly distributed SAUs are mapped to the same CBG or the consecutive SAUs are mapped to the same CBG.

Example 12 may include the method of Example 1 or any other example herein, where a DCI schedules a transmission carrying multiple TBs with no CBGs.

Example 13 may include the method of Example 12 or any other example herein, where SLIV in the DCI indicates the time resource of a SAU.

Example 14 may include the method of example 13 or any other example herein wherein the consecutive SAUs are mapped to the same TB or the evenly distributed SAUs are mapped to the same TB.

Example 15 may include the method of Example 1 or any other example herein wherein a DCI schedules a transmission carrying multiple TBs with CBGs.

Example 16 may include the method of Example 15 or any other example herein, where SLIV in the DCI indicates the time resource of a CBG.

Example 17 may include the method of Example 16 or any other example herein, wherein the evenly distributed CBGs are mapped to the same TB, or the consecutive CBGs are mapped to the same TB.

Example 18 may include the method of Example 15 or any other example herein, where SLIV in the DCI indicates the time resource of a SAU.

Example 19 may include the method of Example 18 or any other example herein, wherein the consecutive SAUs are mapped to the same CBG or the evenly distributed SAUs are mapped to the same CBG.

• Empfangen von Downlink-Steuerinformationen (DCI), um eine Ressourcenzuweisung zur Übertragung eines Transportblocks anzugeben, wobei die Ressourcenzuweisung eine oder mehrere Codeblockgruppen (CBGs) beinhaltet, die auf eine oder mehrere Symbolausrichtungseinheiten (SAUs) eines oder mehrerer Symbole abgebildet werden; und
• Übertragen oder Empfangen des Transportblocks basierend auf den DCI.

Example 20 may include a method comprising:

• receiving downlink control information (DCI) to indicate a resource allocation for transmission of a transport block, the resource allocation including one or more code block groups (CBGs) mapped to one or more symbol alignment units (SAUs) of one or more symbols; and
• Transmit or receive the transport block based on the DCI.

Example 21 may include the method of Example 20 or any other example herein, wherein individual CBGs are mapped to all time-frequency resources of the one or more symbols of the respective one or more SAUs.

Example 22 may include the method of Examples 20-21 or any other example herein, wherein the DCI includes a start length indicator value (SLIV) to indicate a time resource of a first CBG of the one or more CBGs.

Example 23 may include the method of Examples 20-21 or any other example herein, wherein the DCI includes a SLIV for indicating a time resource of a first SAU of the one or more SAUs.

Example 24 may include the method of Examples 20-23 or any other example herein, further comprising determining an early termination of the transmission, wherein the early termination is determined at a granularity of a transport block, a CBG, or a SAU.

Example 25 may include the method of Examples 20-24 or any other example herein wherein the DCIs schedule the transmission of the single transport block.

Example 26 may include the method of example 25 or any other example herein, where the transport block includes multiple CBGs.

Example 27 may include the method of Example 25 or any other example herein, where the transport block includes multiple SAUs.

Example 28 may include the method of Examples 20-24 or any other example herein, wherein the DCI schedules the transmission of multiple transport blocks.

Example 29 may include the method of example 28 or any other example herein, wherein the resource allocations for individual transport blocks correspond to consecutive time-frequency resources.

Example 30 may include the method of example 28 or any other example herein, wherein the CBGs and/or SAUs of the multiple transport blocks are interleaved with each other in the time domain.

Example 31 may include the method of Examples 20-30 or any other example herein, where respective CBGs include multiple SAUs.

Example 32 may include the method of Example 31 or any other example herein, wherein the multiple SAUs are consecutive in the time domain.

Example 33 may include the method of Example 31 or any other example herein, where the multiple SAUs are interleaved in the time domain with other SAUs of the resource allocation.

Example 34 may include the method of Examples 20-33, further comprising generating or receiving HARQ feedback for individual CBGs of the resource allocation.

Example 35 may include the method of Examples 20-34 or any other example herein, wherein the transport block is a PUSCH.

Example 36 may include the method of Examples 20-34 or any other example herein, wherein the transport block is a PDSCH.

Example 37 may include the method of Examples 20 to 36 or any other example herein, wherein the method is performed by a UE or a portion thereof.

• Empfangen von Downlink-Steuerinformationen (DCI), um jeweilige Ressourcenzuweisungen für zwei oder mehr Transportblöcke anzugeben, wobei die Ressourcenzuweisungen eine oder mehrere Symbolausrichtungseinheiten (SAUs) beinhalten, wobei die SAUs alle Zeit-Frequenz-Ressourcen eines oder mehrerer Symbole beinhalten; und
• Übertragen oder Empfangen der Transportblöcke basierend auf den DCI.

Example 38 may include a method comprising:

• receiving downlink control information (DCI) to indicate respective resource allocations for two or more transport blocks, the resource allocations containing one or more symbols alignment units (SAUs), the SAUs including all time-frequency resources of one or more symbols; and
• Transmitting or receiving the transport blocks based on the DCI.

Example 39 may include the method of Example 38 or any other example herein, where the individual resource allocations include multiple SAUs.

Example 40 may include the method of Examples 38-39 or any other example herein, wherein the multiple SAUs are contiguous in the time domain.

Example 41 may include the method of Examples 38-39 or any other example herein, wherein the multiple SAUs are interleaved in the time domain with the SAUs of one or more other resource allocations.

Example 42 may include the method of Examples 38-41, further comprising generating or receiving a HARQ response for individual SAUs of the resource allocations.

Example 43 may include the method of Examples 38-42 or any other example herein, wherein the transport blocks are transmitted on a PUSCH.

Example 44 may include the method of Examples 38-42 or any other example herein, wherein the transport blocks are transmitted on a PDSCH.

Example 45 may include the method of Examples 38-44 or any other example herein, the method being performed by a UE or portion thereof.

• Codieren, zur Übertragung an ein UE, von Downlink-Steuerinformationen (DCI), um eine Ressourcenzuweisung zur Übertragung eines Transportblocks anzugeben, wobei die Ressourcenzuweisung eine oder mehrere Codeblockgruppen (CBGs) beinhaltet, die auf eine oder mehrere Symbolausrichtungseinheiten (SAUs) eines oder mehrerer Symbole abgebildet werden; und
• Veranlassen einer Übertragung des Transportblocks an das UE oder eines Empfangs des Transportblocks von dem UE basierend auf den DCI.

Example 46 may include a method comprising:

• Encoding, for transmission to a UE, downlink control information (DCI) to indicate a resource allocation for transmission of a transport block, the resource allocation including one or more Code Block Groups (CBGs) pointing to one or more Symbol Alignment Units (SAUs) of one or more symbols to be mapped; and
• Cause transmission of the transport block to the UE or receipt of the transport block from the UE based on the DCI.

Example 47 may include the method of Example 46 or any other example herein, wherein individual CBGs are mapped to all time-frequency resources of the one or more symbols of the respective one or more SAUs.

Example 48 may include the method of Examples 46-47 or any other example herein, wherein the DCI includes a start length indicator value (SLIV) to indicate a time resource of a first CBG of the one or more CBGs.

Example 49 may include the method of Examples 46-47 or any other example herein, wherein the DCI includes a SLIV for indicating a time resource of a first SAU of the one or more SAUs.

Example 50 may include the method of Examples 46-49 or any other example herein, further comprising determining an early termination of the transmission, wherein the early termination is determined at a granularity of a transport block, a CBG, or a SAU.

Example 51 may include the method of Examples 46-50 or any other example herein wherein the DCIs schedule the transmission of the single transport block.

Example 52 may include the method of example 51 or any other example herein, where the transport block includes multiple CBGs.

Example 53 may include the method of Example 51 or any other example herein, where the transport block includes multiple SAUs.

Example 54 may include the method of Examples 46 through 50 or any other example herein, wherein the DCI schedules the transmission of multiple transport blocks.

Example 55 may include the method of example 54 or any other example herein, wherein the resource allocations for individual transport blocks correspond to consecutive time-frequency resources.

Example 56 may include the method of Example 54 or any other example herein, wherein the CBGs and/or SAUs of the multiple transport blocks are interleaved with each other in the time domain.

Example 57 may include the method of Examples 46-56 or any other example herein, where respective CBGs include multiple SAUs.

Example 58 may include the method of example 57 or any other example herein, wherein the multiple SAUs are consecutive in the time domain.

Example 59 may include the method of Example 57 or any other example herein, where the multiple SAUs are interleaved in the time domain with other SAUs of the resource allocation.

Example 60 may include the method of Examples 46-59, further comprising generating or receiving HARQ feedback for individual CBGs of the resource allocation.

Example 61 may include the method of Examples 46-60 or any other example herein, wherein the transport block is a PUSCH.

Example 62 may include the method of Examples 46-60 or any other example herein, wherein the transport block is a PDSCH.

Example 63 may involve the method of Examples 46 to 62 or any other example herein wherein the method is performed by a gNB or portion thereof.

• Codieren, zur Übertragung an ein UE, von Downlink-Steuerinformationen (DCI), um jeweilige Ressourcenzuweisungen für zwei oder mehr Transportblöcke anzugeben, wobei die Ressourcenzuweisungen eine oder mehrere Symbolausrichtungseinheiten (SAUs) beinhalten, wobei die SAUs alle Zeit-Frequenz-Ressourcen eines oder mehrerer Symbole beinhalten; und
• Veranlassen einer Übertragung der Transportblöcke an das UE oder eines Empfangs der Transportblöcke von dem UE basierend auf den DCI.

Example 64 may include a method comprising:

• Encoding, for transmission to a UE, downlink control information (DCI) to indicate respective resource allocations for two or more transport blocks, the resource allocations including one or more symbol alignment units (SAUs), the SAUs all time-frequency resources of one or more include symbols; and
• Cause transmission of the transport blocks to the UE or receipt of the transport blocks from the UE based on the DCI.

Example 65 may include the method of example 64 or any other example herein, where the individual resource allocations include multiple SAUs.

Example 66 may include the method of Examples 64-65 or any other example herein, wherein the multiple SAUs are contiguous in the time domain.

Example 67 may include the method of Examples 64-65 or any other example herein, wherein the multiple SAUs are interleaved in the time domain with the SAUs of one or more other resource allocations.

Example 68 may include the method of Examples 64-67, further comprising generating or receiving a HARQ response for individual SAUs of the resource allocations.

Example 69 may include the method of examples 64 through 68 or any other example herein, wherein the transport blocks are transmitted on a PUSCH.

Example 70 may include the method of examples 64 to 68 or any other example herein, wherein the transport blocks are transmitted on a PDSCH.

Example 71 may involve the process of Examples 64 to 70 or any other example herein, wherein the process is performed by a gNB or portion thereof.

Example 72 may include the method of Examples 20-71 or any other example herein, wherein the one or more transport blocks are transmitted on a carrier frequency greater than 52.6 GHz.

• Semistatische Konfiguration von physischen Downlink-Steuerkanal-(PDCCH)-Überwachungsgelegenheiten unter Verwendung höherer Schichten;
• Planen des gemeinsam genutzten physischen Downlink-Kanals (PDSCH) unter Verwendung von Downlink-Steuerinformationen (DCI), die in einem PDCCH übertragen werden, der durch eine höhere Schicht ausgelegt ist; und
• Konfiguration einer zusätzlichen PDCCH-Überwachungsgelegenheit gefolgt von PDSCH.

Example B1 may include a method for downlink control channel transmission, the method including:

• Semi-static configuration of downlink physical control channel (PDCCH) monitoring opportunities using higher layers;
• scheduling the downlink physical shared channel (PDSCH) using downlink control information (DCI) transmitted in a PDCCH laid out by a higher layer; and
• Configuration of an additional PDCCH monitoring opportunity followed by PDSCH.

Example B2 may include the method of Example B1 or any other example herein, wherein an additional PDCCH is scheduled in the next symbol after the last symbol of the PDSCH.

Example B3 may include the method of example B1 or another example herein, wherein an additional PDCCH is scheduled in the X symbols after the last symbol of the PDSCH, where X is one, two, three or more symbols depending on the configuration.

Example B4 may include the method of example B1 or another example herein, where a PDSCH scheduled by an additional PDCCH collides with a PDCCH monitoring opportunity designed by higher layers, a UE may assume that a PDSCH Transmission is prioritized in the corresponding OFDM symbols, and a potential PDCCH is discarded.

Example B5 may include the method of example B1 or another example herein, where a PDSCH scheduled by an additional PDCCH collides with a PDCCH monitoring opportunity designed by higher layers, the UE may assume that a PDCCH Transmission is prioritized in the corresponding OFDM symbols, and a PDSCH is discarded.

Example B6 may include the method of example B1 or another example herein, where an additional PDCCH collides with a PDCCH monitoring opportunity designed by higher layers, the UE may assume that an additional PDCCH transmission in the corresponding OFDM symbols is prioritized and a PDCCH designed by higher layers is discarded.

Example B7 may include the method of example B1 or another example herein, where an additional PDCCH collides with a PDCCH monitoring opportunity designed by higher layers, the UE may assume that an additional PDCCH transmission in the corresponding OFDM symbols is discarded and a PDCCH designed by higher layers is prioritized.

Example B8 may include the method of Example B1 or another example herein, wherein an additional PDCCH collides with a PDCCH monitoring opportunity designed by higher layers, the UE is processing an additional PDCCH transmission and a PDCCH designed by higher layers is, is prioritized.

Example B9 may include the method of Example B1 or another example herein, wherein a PDSCH scheduled by an additional PDCCH collides with a PDCCH monitoring opportunity designed by higher layers, a UE is processing a PDCCH transmission that by higher layers and a PDSCH scheduled by an additional PDCCH.

Example B10 may include the method of Example B1 or any other example herein, wherein an additional PDCCH may be transmitted after the last PDSCH symbol indicated by early termination.

Example B11 may include the method of example B1 or another example herein, where higher layers are RRC or MAC signalling.

• Bestimmen eines letzten Symbols eines PDSCH;
• Bestimmen einer PDCCH-Überwachungsgelegenheit für einen PDCCH basierend auf dem letzten Symbol des PDSCH; und
• Überwachen auf einen PDCCH in der bestimmten PDCCH-Überwachungsgelegenheit

Example B12 may include a method comprising:

• determining a last symbol of a PDSCH;
• determining a PDCCH monitoring opportunity for a PDCCH based on the last symbol of the PDSCH; and
• Monitor for a PDCCH in the designated PDCCH monitor opportunity

Example B13 may include the method of example B12 or another example herein, where the PDCCH monitoring opportunity includes an earliest symbol after the last symbol of the PDSCH.

Example B14 may include the method of example B12 to B13 or another example herein, wherein the PDCCH monitoring opportunity starts in a symbol that is X symbols after the last symbol of the PDSCH.

Example B15 may involve the method of example B14 or any other example herein, wherein a value of X is 1, 2, 3 or 4.

Example B16 may include the method of example B14 to B15 or any other example herein, further comprising receiving an indication of a value of X.

Example B17 may include the method of Examples B12 to B16 or any other example herein, further comprising receiving the PDCCH.

Example B18 may include the method of example B17 or any other example herein, where the PDSCH is a first PDSCH and where the PDCCH schedules a second PDSCH.

Example B19 may include the method of example B12 to B18 or any other example herein, wherein the PDCCH monitoring opportunity is a first PDCCH monitoring opportunity, the second PDSCH collides with a second PDCCH monitoring opportunity, and the method further comprises: determining a relative priority of the second PDSCH compared to the second PDCCH monitoring opportunity; and selecting one of decoding the second PDSCH or monitoring for a second PDCCH in the PDCCH monitoring opportunity based on the determined relative priority.

Example B20 may include the method of example B19 monitoring opportunity of another example herein, wherein the second PDCCH monitoring opportunity is laid out via RRC signaling.

Example B21 may include the method of example B12-B20 or any other example herein, wherein the PDCCH monitoring opportunity is a first PDCCH monitoring opportunity, the first PDCCH monitoring opportunity overlaps with a second PDCCH monitoring opportunity, and wherein the monitoring is based on the PDCCH is performed in the first PDCCH monitoring opportunity based on a relative priority of the first PDCCH monitoring opportunity compared to the second PDCCH monitoring opportunity.

Example B22 may include the method of Examples B12 to B21 or any other example herein, where the PDCCH includes DCI for an uplink or downlink communication.

Example B23 may include the method of Example B22 or another example herein, wherein the communication occurs on unlicensed spectrum, in 5G FR2, and/or for ultra-reliable and low-latency communications (URLLC).

Example B24 may include the method of example B12 to B23 or any other example herein, the method being performed by a UE or part thereof.

• Codieren eines PDSCH zur Übertragung;
• Bestimmen einer PDCCH-Überwachungsgelegenheit für einen PDCCH basierend auf einem letzten Symbol des PDSCH; und
• Codieren des PDCCH zur Übertragung in der bestimmten PDCCH-Überwachungsgelegenheit.

Example B25 may include a method comprising:

• encoding a PDSCH for transmission;
• determining a PDCCH monitoring opportunity for a PDCCH based on a last symbol of the PDSCH; and
• Encoding the PDCCH for transmission in the particular PDCCH monitoring occasion.

Example B26 may include the method of example B25 or another example herein, where the PDCCH monitoring opportunity includes an earliest symbol after the last symbol of the PDSCH.

Example B27 may include the method of example B25 to B26 or another example herein, wherein the PDCCH monitoring opportunity starts in a symbol that is X symbols after the last symbol of the PDSCH.

Example B28 may involve the method of example B27 or any other example herein, wherein a value of X is 1, 2, 3 or 4.

Example B29 may include the method of example B27-B28 or any other example herein, further comprising encoding an indication of a value of X for transmission.

Example B30 may include the method of example B29 or any other example herein, where the PDSCH is a first PDSCH and where the PDCCH schedules a second PDSCH.

Example B31 may include the method of examples B25 to B30 or any other example herein, where the PDCCH includes DCI for an uplink communication.

Example B32 may include the method of example B31 or any other example herein, further comprising receiving the uplink communication.

Example B33 may include the method of examples B25 to B32 or any other example herein, where the PDCCH includes DCI for scheduling a downlink communication.

Example B34 may include the method of example B33 or any other example herein, further comprising encoding the downlink communication for transmission.

Example B35 may include the method of example B33-B34 or another example herein, where the downlink communication is another PDSCH.

Example B36 may include the method of example B25 to B35 or another example herein, wherein the PDCCH is to schedule communication on unlicensed spectrum, in 5G FR2 and/or for ultra-reliable and low-latency communications (URLLC).

Example B37 may include the method according to example B25 to B36 or any other example herein, wherein the PDSCH and the PDCCH are transmitted to the same UE.

Example B38 may include the method of example B25 to B37 or any other example herein, the method being performed by a gNB or part thereof.

Example C1 may include one or more non-transitory computer-readable media (NTCRM) having instructions stored thereon that, when executed by one or more processors, cause a user equipment (UE) to: determine a last symbol of a downlink physical shared channel (PDSCH); determining a downlink physical control channel (PDCCH) monitoring opportunity for a PDCCH based on the last symbol of the PDSCH; and monitoring for a PDCCH in the determined PDCCH monitoring opportunity.

Example C2 may include the one or more NTCRM of Example C1 or any other example herein, wherein the PDCCH monitoring opportunity starts in a symbol that is a number of one or more symbols after the last symbol of the PDSCH.

Example C3 may include the one or more NTCRMs of Example C2 or any other example herein, wherein the instructions, when executed, further cause the UE to receive an indication of the count.

Example C4 may include the one or more NTCRM of Example C1 to C3 or any other example herein, wherein the PDSCH is a first PDSCH and wherein the instructions, when executed, are intended to further cause the UE to include the PDCCH in the PDCCH - receives monitoring opportunity, where the PDCCH schedules a second PDSCH or an Uplink Physical Shared Channel (PUSCH).

Example C5 may include the one or more NTCRM of Example C4 or any other example herein, wherein the PDCCH monitoring opportunity is a first PDCCH monitoring opportunity, the second PDSCH collides with a second PDCCH monitoring opportunity, and the instructions when executed shall further cause the UE to: determine a relative priority of the second PDSCH compared to the second PDCCH monitoring opportunity; and selecting either decoding the second PDSCH or monitoring for another PDCCH in the PDCCH monitoring opportunity based on the determined relative priority.

Example C6 may include the one or more NTCRM of Example C1 through C5 or any other example herein, wherein the PDCCH monitoring opportunity is a first PDCCH monitoring opportunity, the first PDCCH monitoring opportunity overlaps with a second PDCCH monitoring opportunity, and where the monitoring for the PDCCH in the first PDCCH monitoring opportunity is performed based on a relative priority of the first PDCCH monitoring opportunity compared to the second PDCCH monitoring opportunity.

Example C7 may include the one or more NTCRM of example C1 to C6 or any other example herein, wherein the instructions, when executed, are intended to further cause the UE to receive the PDCCH in the PDCCH monitoring opportunity, the PDCCH a plans uplink or downlink communications in an unlicensed spectrum, in a 5G Frequency Range 2 (FR2), or for ultra-reliable and low-latency communications (URLLC).

Example C8 may include the one or more non-transitory computer-readable media (NTCRM) having instructions stored thereon that, when executed by one or more processors, cause a next-generation NodeB (gNB) to: determine a last symbol of a physical downlink shared channel (PDSCH) transmitted to a user equipment (UE); determining a downlink physical control channel (PDCCH) monitoring opportunity for a PDCCH based on the last symbol of the PDSCH; and encoding a PDCCH for transmission to the UE in the determined PDCCH monitoring opportunity.

Example C9 may include the one or more NTCRM of example C8 or any other example herein, wherein the PDCCH monitoring opportunity starts in a symbol that is a number of one or more symbols after the last symbol of the PDSCH.

Example C10 may include the one or more NTCRM of Example C9 or any other example herein, wherein the instructions, when executed, further cause the gNB to encode a message for transmission to the UE that includes an indication of the count.

Example C11 may include the one or more NTCRM of example C8 through C10 or any other example herein wherein the PDCCH is to schedule a downlink transmission.

Example C12 may include the one or more NTCRM of Example C11 or any other example herein, where THE PDSCH is a first PDSCH and where the downlink transmission includes a second PDSCH.

Example C13 may include the one or more NTCRM of Example C11 or any other example herein wherein the PDCCH is to schedule an uplink communication and wherein the instructions, when executed, are to further cause the gNB to receive the uplink communication .

Example C14 may include the one or more NTCRM of Example C8 through C13 or any other example herein, wherein the instructions wherein the PDCCH is an uplink or downlink communication in an unlicensed spectrum, in a 5G Frequency Band 2 (FR2) or for ultra-reliable communications and low-latency communications (URLLC).

Example C15 may include one or more non-transitory computer-readable media (NTCRM) having instructions stored thereon that, when executed by one or more processors, cause a user equipment (UE) to: receive downlink control information (DCI) to generate a specify resource allocation for one or more transport blocks, the resource allocation including one or more symbol alignment units (SAUs); and transmitting or receiving the one or more transport blocks based on the DCI.

Example C16 may include the one or more NTCRM of Example C15 or any other example herein, wherein the resource allocation includes one or more code block groups (CBGs) mapped to one or more SAUs of one or more symbols.

Example C17 may include the one or more NTCRMs of examples C15 through C16 or any other example herein, where the SAUs include all time-frequency resources of one or more symbols.

Example C18 may include the one or more NTCRMs of example C15 through C17 or another example herein, wherein the DCI includes a start and length indicator value (SLIV) to indicate a time resource of a first SAU of the one or more SAUs .

Example C19 may include the one or more NTCRM of example C16 through C18 or any other example herein, wherein the DCI include a start and length indicator value (SLIV) to indicate a time resource of a first CBG of the one or more CBGs .

Example C20 may include the one or more NTCRM of example C15 through C19 or any other example herein, wherein the DCI schedules the transmission of multiple transport blocks, and wherein the resource allocations for individual transport blocks of the multiple transport blocks correspond to consecutive time-frequency resources.

Example C21 may include the one or more NTCRM of any of Examples C16 through C20, wherein the DCI schedules transmission of multiple transport blocks, and wherein resource allocations for individual CBGs of the multiple transport blocks correspond to consecutive time-frequency resources.

Example C22 may include the one or more NTCRMs of example C15 through C21 or any other example herein, wherein the DCI schedules the transmission of multiple transport blocks, and wherein the SAUs of the multiple transport blocks are interleaved with each other in a time domain.

Example C23 may include the one or more NTCRMs of any of Examples C16 through C22, wherein the DCI schedules transmission of multiple transport blocks, and wherein the CBGs of the multiple transport blocks are interleaved in a time domain.

Example Z01 may include equipment having means for performing one or more elements of a method described in or related to any of Examples 1 to 72, B1 to B38, C1 to C23, or any other method or Process described here includes.

Example Z02 may include one or more non-transitory computer-readable media comprising instructions for causing an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in any of Examples 1 to 72 , B1 to B38, C1 to C23 or associated with them, or any other method or process described herein.

Example Z03 may include apparatus comprising logic, modules, or circuitry for performing one or more elements of a method described in or related to any of Examples 1-72, B1-B38, C1-C23, or a any other method or process described herein.

Example Z04 may involve a method, technique or process as described in or related to any of Examples 1 to 72, B1 to B38, C1 to C23 or portions or parts thereof.

Example Z05 may include a device, comprising: one or more processors, and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to A method performing the technique or process as described in or related to any of Examples 1 to 72, B1 to B38, C1 to C23 or parts thereof.

Example Z06 may include a signal as described in or related to any of Examples 1 to 72, B1 to B38, C1 to C23 or portions or parts thereof.

Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message, as in any of Examples 1 through 72, B1 through B38, C1 through C23, or portions or portions thereof, or otherwise in described in or related to the present disclosure.

Example Z08 may include a signal encoded with data as described in or related to any of Examples 1-72, B1-B38, C1-C23, or portions or parts thereof, or otherwise in the present disclosure.

Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message, as in any of Examples 1 through 72, B1 through B38, C1 through C23, or portions or portions thereof, or otherwise described in or related to the present disclosure.

Example Z10 may include an electromagnetic signal bearing computer-readable instructions, execution of the computer-readable instructions by one or more processors to cause the one or more processors to perform the method, technique, or process as in any of Examples 1 to 72, B1 to B38, C1 to C23 or parts thereof or related thereto.

Example Z11 may include a computer program comprising instructions, execution of the program by a processing element to cause the processing element to perform the method, technique or process as in any of Examples 1 to 72, B1 to B38, C1 to C23 or parts thereof described or related to them.

Example Z12 may include a signal in a wireless network as shown and described herein.

Example Z13 may include a method of communicating in a wireless network as shown and described herein.

Example Z14 may include a system for providing wireless communications as shown and described herein.

Example Z15 may include an apparatus for providing wireless communication as shown and described herein.

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

abbreviations

3GPP

Partnerschaftsproj ekt der dritten Generation

4G

Vierte Generation

5G

Fünfte Generation

5GC

5G-Kemnetzwerk

ACK

Bestätigung

AF

Anwendungsfunktion

AM

Bestätigter Modus

AMBR

Aggregierte maximale Bitrate

AMF

Zugangs- und Mobilitätsmanagementfunktion

AN

Zugangsnetzwerk

ANR

Automatische Nachbarbeziehung

AP

Anwendungsproto koll,Antennenport, Zugangspunkt

API

Anwendungsprogr ammierschnittstelle

APN

Zugangspunktname

ARP

Zuordnungs- und Haltepriorität

ARQ

Automatische Wiederholungsanforderung

AS

Zugangsstratum

ASN.1

Abstrakte Syntaxnotation Eins

AUSF

Authentifizierungs serverfunktion

AWGN

Additives weißes gaußsches Rauschen

BAP

Backhaul-Anpassungsprotokoll

BCH

Broadcast-Kanal

BER

Bitfehlerverhältnis

BFD

Strahlausfalldetekt ion

BLER

Blockfehlerrate

BPSK

Binäre Phasenumtastung

BRAS

Breitband-Fernzugangsserver

BSS

Unternehmensunt erstützungssystem

BS

Basisstation

BSR

Pufferstatusberich t

BW

Bandbreite

BWP

Bandbreitenteil

C-RNTI

Temporäre Zellfunknetzwerksidentitä t

CA

Trägeraggregation , Zertifizierungsstelle

CAPEX

Investitionsaufwa nd

CBRA

Konkurrenzbasiert er Direktzugriff

CC

Komponententräg er, Ländercode, kryptografische Prüfsumme

CCA

Freier-Kanal-Bewertung

CCE

Steuerkanaleleme nt

CCCH

gemeinsamer Steuerkanal

CE

Abdeckungsverstä rkung

CDM

Inhaltslieferungsn etzwerk

CDMA

Codemultiplexzug riff

CFRA

Konkurrenzfreier Direktzugriff

CG

Zellengruppe

CI

Zellidentität

CID

Zell-ID (z. B. Positionsbestimmungsver fahren)

CIM

Gemeinsames Informationsmodell

CIR

Träger-Zu-Interferenz-Verhältnis

CK

Chiffreschlüssel

CM

Verbindungsmana gement, bedingt obligatorisch

CMAS

Kommerzieller mobiler Benachrichtigungsdienst

CMD

Befehl

CMS

Cloud-Managementsystem

CO

Bedingt optional

CoMP

Koordinierter Mehrpunkt CORESET Steuerressourcens atz

COTS

Gewöhnlicher kommerzieller Standard

CP

Steuerebene, zyklisches Präfix, Verbindungspunkt

CPD

Verbindungspunkt deskriptor

CPE

Gerät am Kundestandort

CPICH

Gemeinsamer Pilotkanal

CQI

Kanalqualitätsindi kator

CPU

CSI-Verarbeitungseinheit, zentrale Verarbeitungseinheit

C/R

Befehls-/Antwortfeld-Bit

CRAN

Cloud-Funkzugangsnetzwerk, Cloud-RAN

CRB

Gemeinsamer Ressourcenblock

CRC

Zyklische Redundanzprüfung

CRI

Kanalzustandsinfo rmationen-Ressourcenindikator,

CSI-RS

Ressourcenindikator

C-RNTI

Zell-RNTI

CS

Leitungsvermittelt

CSAR

Cloud-Dienstarchiv CSI-analzustandsinfo rmationen

CSI-IM

CSI-Interferenzmessung

CSI-RS

CSI-Referenzsignal

CSI-RSRP

CSI-Referenzsignalempfangsl eistung

CSI-RSRQ

CSI-Referenzsignalempfangsq ualität

CSI-SINR

CSI-Signal-Rausch- und Interferenzverhältnis

CSMA

Carrier Sense Multiple Access

CSMA/CA

CSMA mit Kollisionsvermeidung

CSS

Gemeinsamer Suchraum, zellspezifischer Suchraum

CTS

Sendebereitschaft

CW

Codewort

CWS

Konkurrenz-Fenstergröße

D2D

Vorrichtung-zu-Vorrichtung

DC

Dual Connectivity, Gleichstrom, Gleichspannung

DCI

Downlink-Steuerinformationen

DF

Einsatzflavor

DL

Downlink

DMTF

Verteilte Management-Arbeitsgruppe

DPDK

Datenebenenentwi cklungssatz

DM-RS, DMRS

Demodulationsref erenzsignal

DN

Datennetzwerk

DRB

Datenfunkträger

DRS

Entdeckungsrefere nzsignal

DRX

Diskontinuierliche r Empfang

DSL

Domänenspezifisc he Sprache digitale Teilnehmerleitung

DSLAM

DSL-Zugangsmultiplexer

DwPTS

Downlink-Pilotzeitschlitz E-LANLokales Ethernet-Netzwerk

E2E

Ende-zu-Ende

ECCA

Erweiterte Freier-Kanal-Bewertung, erweiterte CCA

ECCE

Erweitertes Steuerkanalelement, erweitertes CCE

ED

Energiedetektion

EDGE

Enhanced Datarates for GSM Evolution (GSM Evolution)

EGMF

Freigabe-Regelungs-Managementfunktion

EGPRS

Erweiterter GPRS

EIR

Geräteidentitätsregister

eLAA

Erweiterter lizenzierter unterstützter Zugang, erweiterter LAA

EM

Elementmanager

eMBB

erweitertes mobiles Breitband

EMS

Elementemanage mentsystem

eNB

Evolved NodeB, E-UTRAN-Node B

EN-DC

E-UTRA-NR Dual Connectivity

EPC

Evolved Packet Core

EPDCCH

Erweiterter PDCCH, erweiterter physischer Downlink-Steuerkanal

EPRE

Energie pro Ressourcenelement

EPS

Evolved Packet System

EREG

Erweiterte REG, erweiterte Ressourcenelementegrup pen

ETSI

European Telecommunications Standards Institute

ETWS

Erdbeben- und Tsunamiwarnsystem

eUICC

eingebettete

UICC,

eingebettete universelle integrierte Schaltungskarte E-UTRA Evolved

UTRA

E-UTRAN Evolved UTRAN

EV2X

Erweitertes V2X

FIAP

F1-Anwendungsprotokoll

F1-C

F1-Steuerebenenschnittstelle

F1-U

F1-Benutzerebenenschnittstel le

FACCH

Schneller assoziierter Steuerkanal

FACCH/F

Schneller assoziierter Steuerkanal/volle Rate

FACCH/H

Schneller assoziierter Steuerkanal/halbe Rate

FACH

Vorwärts- Zugangskanal

FAUSCH

Schneller Uplink-Signalisierungskanal

FB

Funktionsblock

FBI

Rückmeldeinform ationen

FCC

Federal Communications Commission

FCCH

Frequenzkorrektur kanal

FDD

Frequenzduplex

FDM

Frequenzmultiple x

FDMA

Frequenzmultiple x zugang

FE

Frontend

FEC

Vorwärtsfehlerkor rektur

FFS

zur weiteren Untersuchung

FFT

Fast-Fourier- Transformation

feLAA

weiter erweiterter lizenzierter unterstützter Zugang, weiter erweiterter LAA

FN

Framenummer

FPGA

Field Programmable Gate Array

FR

Frequenzbereich

G-RNTI

Temporäre GERAN- Funknetzwerkidentität

GERAN

GSM- EDGE-RAN, GSM-EDGE-Funkzugangsnetzwerk

GGSN

Gateway-GPRS- Unterstützungsknoten

GLONASS

Globales Satellitennavigationssyste m (Engl.: Global Navigation Satellite System)

gNB

NodeB der nächsten Generation

gNB-CU

gNB- Zentraleinheit, NodeB- Zentraleinheit der nächsten Generation

gNB-DU

verteilte gNB-Einheit, verteilte NodeB-Einheit der nächsten Generation

GNSS

Globales Navigationssatellitensyste m

GPRS

General Packet

Radio

Service

GSM

Globales System fürMobilkommunikationen,

Groupe

Spécial Mobile

GTP

GPRS- Tunnelprotokoll GTP-UGPRS-Tunnelprotokoll für Benutzerebene

GTS

Ausschaltsignal (bezogen auf WUS)

GUMMEI

Global eindeutige MME- Kennung

GUTI

Global eindeutige temporäre UE-Identität

HARQ

Hybrid-ARQ, hybride automatische Wiederholungsanforderung

HANDO

Handover

HFN

Hyper-Frame- Nummer

HO

Hartes Handover

HLR

Home Location Register

HN

Heimnetzwerk

HO

Handover

HPLMN

Öffentliches terrestrisches Mobilfunknetzwerk

HSDPA

Hochgeschwindig keits-Downlink-Paketzugang

HSN

Hopping-Sequenznummer

HSPA

Hochgeschwindig keits-Paketzugang

HSS

Home Subscriber Server

HSUPA

Hochgeschwindig keits-Uplink-Paketzugang

HTTP

Hypertext Transfer Protocol

HTTPS

Hypertext Transfer Protocol Secure (https ist http/1.1 über SSL, d. h. Port 443) 1-Block Informationsblock

ICCID

Integrierte-Schaltungs-Kartenidentifikation

IAB

Integrierter Zugang und Backhaul

ICIC

Zwischen-Zellen-Interferenzkoordination

ID

Identität, Kennung

IDFT

Inverse diskrete Fourier-Transformation

IE

Informationselement

IBE

In-Band-Emission

IEEE

Institute of Electrical and Electronics Engineers

IEI

Informationselem ente kennung

IEIDL

Informationselem entekennungsdatenlänge

IETF

Internet Engineering Task Force

IF

Infrastruktur

IM

Interferenzmessung, Intermodulation, IP-Multimedia

IMC

IMS-Berechtigungsnachweise

IMEI

Internationale Mobilgeräteidentität

IMGI

Internationale Mobilgruppenidentität

IMPI

IP-Multimedia-Privatidentität

IMPU

IP Multimedia Public Identity

IMS

IP-Multimedia-Subsystem

IMSI

Internationale Mobilfunk-Teilnehmeridentität

IoT

Internet der Dinge

IP

Internetprotokoll

Ipsec

IP-Sicherheit, Internetprotokollsicherheit

IP-CAN

IP-Connectivity Access Network

IP-M

IP-Multicast

IPv4

Internetprotokoll Version 4

IPv6

Internetprotokoll Version 6

IR

Infrarot

IS

Synchron

IRP

Integrationsrefere nzpunkt

ISDN

Integrated Services Digital Network

ISIM

IM-Dienstidentitätsmodul

ISO

International Organization for Standardization

ISP

Internetdienstanbi eter

IWF

Interworking Function

I-WLAN

Interworking

WLAN

Beschränkungslänge des Faltungscodes, individueller USIM-Schlüssel

kB

Kilobyte (1000 Byte)

kbps

Kilobit pro Sekunde

Kc

Chiffrierschlüssel

Ki

Individueller Teilnehmerauthentifizieru ngsschlüssel

KPI

Schlüsselleistungs indikator

KQI

Schlüsselqualitätsi ndikator

KSI

Schlüsselsatzkenn ung

ksps

Kilo-Symbole pro Sekunde

KVM

Virtuelle Kernel-Maschine

L1

Schicht 1 (Bitübertragungsschicht)

L1-RSRP

Schicht-1-Referenzsignalempfangsleistung

L2

Schicht 2 (Datenlinkschicht)

L3

Schicht 3 (Netzwerkschicht)

LAA

Lizenzierter unterstützter Zugriff

LAN

Local Area Network

LBT

Listen Before Talk

LCM

Lebenszyklusman agement

LCR

niedrige Chiprate

LCS

Standortdienste

LCID

Logikkanal-ID

LI

Schichtindikator

LLC

Logiklinksteuerung, Kompatibilität mit niedrigen Schichten

LPLMN

Local PLMN

LPP

LTE-Positionsbestimmungspro tokoll

LSB

Niedrigstwertiges Bit

LTE

Long Term Evolution

LWA

LTE-WLAN-Aggregation

LWIP

LTE/WLAN-Funklevelintegration mit IPsec-Tunnel

LTE

Long Term Evolution

M2M

Maschine-zu-Maschine

MAC

Medienzugangsste uerung(Protokollschichtkontext)

MAC

Nachrichtenauthe ntifizierungscode (Sicherheits-/Verschlüsselungskontext )

MAC-A

MAC zur Authentifizierung und Schlüsselvereinbarung (Kontext TSG T WG3)

MAC-IMAC

zur Datenintegrität von Signalisierungsnachrichten (Kontext TSG T WG3)

MANO

Management und Orchestrierung

MBMS

Multimedia Broadcast and Multicast Service

MBSFN

Multimedia Broadcast Multicast Service Single Frequency Network

MCC

Mobilfunklandescode

MCG

Masterzellengruppe

MCOT

Maximale Kanalbelegungszeit

MCS

Modulations- und Codierungsschema

MDAF

Managementdaten analysefunktion

MDAS

Managementdaten analysedienst

MDT

Minimierung von Drive Tests

ME

Mobilgerät

MeNB

Master-eNB

MER

Nachrichtenfehler verhältnis

MGL

Messlückenlänge

MRP

Messlückenwieder holperiode

MIB

Master-Informationsblock, Managementinformationsbasis

MIMO

Mehrfacheingang-Mehrfachausgang

MLC

Mobilstandortzent rum

MM

Mobilitätsmanage ment

MME

Mobilitätsmanage mententität

MN

Master-Knoten

MnS

Managementdiens t

MO

Messobjekt, mobilen Ursprungs

MPBCH

MTC Physical BroadcastChannel

MPDCCH

MTC Physical Downlink Control Channel

MPDSCH

MTC Physical Downlink Shared Channel

MPRACH

MTC Physical Random Access Channel

MPUSCH

MTC Physical Uplink Shared Channel

MPLS

MultiProtocol Label Switching

MS

Mobilstation

MSB

Höchstwertiges Bit

MSC

Mobilfunkvermittl ungsstelle

MSI

Minimale Systeminformationen, MCH-Planungsinformationen

MSID

Mobilstationskenn ung

MSIN

Mobilstations-Identifikationsnummer

MSISDN

Mobilteilnehmer-ISDN-Nummer

MT

Mobil abgeschlossen, Mobilabschluss

MTC

Maschinentypkom munikation mMTCMassive MTC, massive Maschinentypkommunika tion

MU-MIMO

Mehrbenutzer-MIMO

MWUS

MTC-Wecksignal, MTC-WUS

NACK

Negative Bestätigung

NAI

Netzwerkzugangs kennung

NAS

Non-Access-Stratum, Non-Access-Stratum-Layer

NCT

Netzwerkkonnekti vitätstopologie

NC-JT

Nichtkohärente gemeinsame Übertragung

NEC

Netzwerkfähigkeit enaufdeckung

NE-DC UTRA

NR-E-Dual Connectivity

NEF

Netzwerkaufdeck ungsfunktion

NF

Netzwerkfunktion

NFP

Netzwerkweiterlei tungspfad

NFPD

Netzwerkweiterlei tungspfaddeskriptor

NFV

Netzwerkfunktion svirtualisierung

NFVI

NFV-Infrastruktur

NFVO

NFV-Orchestrator

NG

Nächste Generation, Next-Gen

NGEN-DC

NG-RAN-E-UTRA-NR-Dualkonnektivität

NM

Netzwerkmanager

NMS

Netzwerkmanage mentsystem N-PoP Netzwerk-Präsenzpunkt

NMIB, N-MIB

Schmalband-MIB

NPBCH

Narrowband Physical Broadcast Channel

NPDCCH

Narrowband Physical Downlink Control Channel

NPDSCH

Narrowband Physical Downlink Shared Channel

NPRACH

Narrowband Physical Random Access Channel

NPUSCH

Narrowband Physical Uplink Shared Channel

NPSS

Schmalband-Primärsynchronisationssi gnal

NSSS

Schmalband-Sekundärsynchronisations signal

NR

New-Radio, Nachbarschaftsbeziehung

NRF

NF-Repository-Funktion

NRS

Schmalbandrefere nzsignal

NS

Netzwerkdienst

NSA

Nicht-eigenständiger Betriebsmodus

NSD

Netzwerkdienstde skriptor

NSR

Netzwerkdienstau fzeichnung

NSSAI

Netzwerk-Slice-Auswahlassistenzinforma tionen

S-NNSAI

Single-NSSAI

NSSF

Netzwerk-Slice-Auswahlfunktion

NW

Netzwerk

NWUS

Schmalband-Wecksignal, Schmalband-WUS

NZP

Nicht-Null-Leistung

O&M

Betrieb und Wartung

ODU2

Optische Kanaldateneinheit - Typ 2

OFDM

Orthogonales Frequenzmultiplexing

OFDMA

Orthogonalfreque nzmultiplexzugang

OOB

Out-of-band

OOS

Out-of-Sync

OPEX

Betriebskosten

OSI

Andere Systeminformationen

OSS

Betriebsunterstütz ungssystem

OTA

Over-the-Air PAPR Spitzenleistung zu Durchschnittsleistung

PAR

Spitze zu Mittelwert

PBCH

Physical Broadcast Channel

PC

Leistungssteuerung, Personal Computer

PCC

Primärkomponent enträger, Primär-CC

PCell

Primärzelle

PCI ID,

Physische Zellen-physische Zellenidentität

PCEF

Richtlinien- und Verrechnungsdurchsetzun gsfunktion

PCF

Richtliniensteuerf unktion

PCRF

Richtliniensteueru ngs- und Verrechnungsregelfunktio n

PDCP

Paketdatenkonver genzprotokoll, Paketdatenkonvergenzpro tokollschicht

PDCCH

Physical Downlink Control Channel

PDCP

Paketdatenkonver genzprotokoll

PDN

Paketdatennetzwe rk, öffentliches Datennetzwerk

PDSCH

Physical Downlink Shared Channel

PDU

Protokolldatenein heit

PEI

Permanente Gerätekennungen

PFD

Paketflussbeschrei bung

P-GW

PDN-GATEWAY

PHICH

Physical hybrid-ARQ indicator channel

PHY

Physische Schicht

PLMN

Öffentliches terrestrisches Mobilfunknetzwerk

PIN

Persönliche Identifikationsnummer

PM

Leistungsmessung

PMI

Vorcodierungsmat rixindikator

PNF

Physische Netzwerkfunktion

PNFD

Physischer Netzwerkfunktionsdeskri ptor

PNFR

Physische Netzwerkfunktionsaufzei chnung

POC

PTT over Cellular

PP, PTP

Punkt-zu-Punkt

PPP

Punkt-zu-Punkt-Protokoll

PRACH

Physischer RACH

PRB

Physischer Ressourcenblock

PRG

Physische Ressourcenblockgruppe

ProSe

Proximity Services, Proximity-Based Service

PRS

Positionsbestimm ungsreferenzsignal

PRR

Paketempfangsfun k

PS

Paketdienste

PSBCH

Physical Sidelink Broadcast Channel

PSDCH

Physical Sidelink Downlink Channel

PSCCH

Physical Sidelink Control Channel

PSFCH

Physical Sidelink Feedback Channel

PSSCH

Physical Sidelink Shared Channel PSCell Primär-SCell

PSS

Primärsynchronisa tionssignal

PSTN

Festnetz

PT-RS

Phasenverfolgung sreferenzsignal

PTT

Push-to-Talk

PUCCH

Physical Uplink Control Channel

PUSCH

Physical Uplink Shared Channel

QAM

Quadraturamplitu denmodulation

QCI

QoS-Klasse der Kennung

QCL

Quasi-Kolokalisierung

QFI

QoS-Fluss-ID, QoS-Flusskennung

QoS

Dienstgüte

QPSK

Quadratur (quaternäre) Phasenumtastung

QZSS

Quasi-Zenith-Satellitensystem

RA-RNTI

Random Access RNTI

RAB

Funkzugangsträge r, Direktzugangs-Burst

RACH

Random Access Channel

RADIUS

Remote Authentication Dial In User Service

RAN

Funkzugangsnetz werk

RAND

RANDom-Zahl (zur Authentifizierung verwendet)

RAR

Direktzugriffsant wort

RAT

Funkzugangstechn ologie

RAU

Routingbereichsak tualisierung

RB

Ressourcenblock, Funkträger

RBG

Ressourcenblockg ruppe

REG

Ressourcenelemen tgruppe

Rel

Freigabe

REQ

Anforderung

RF

Funkfrequenz

RI

Rangindikator

RIV

Ressourcenindikat orwert

RL

Funklink

RLC

Funklinksteuerung ,Funklinksteuerungsschicht

RLC

AM Bestätigter RLC-Modus

RLC

UM Unbestätigter RLC-Modus

RLF

Funklinkausfall

RLM

Funklinküberwach ung

RLM-RS

Referenzsignal für RLM

RM

Registrierungsma nagement

RMC

Referenzmesskana 1

RMSI

Verbleibende MSI, verbleibende minimaleSysteminformationen

RN

Relaisknoten

RNC

Funknetzwerksteu erung

RNL

Funknetzwerkschi cht

RNTI

Temporäre Funknetzwerkkennung

ROHC

Robuste Header- Kompression

RRC

Funkressourcenste uerung,Funkressourcensteuerschi cht

RRM

Funkressourcenm anagement

RS

Referenzsignal

RSRP

Referenzsignalem pfangsleistung

RSRQ

Referenzsignalem pfangsqualität

RSSI

Empfangssignalst ärkeindikator

RSU

Straßenrandeinhei t

RSTD

Referenzsignalzeit differenz

RTP

Echtzeitprotokoll

RTS

sendebereit

RTT

Umlaufzeit

Rx

Empfang, Empfangen, Empfänger

S1AP

S1- Anwendungsprotokoll

S1-MME

S1 für die Steuerebene

S1-U

S1 für die Benutzerebene

S-GW

Serving-Gateway

S-RNTI

Temporäre SRNC-Funknetzwerkidentität

S-TMSI

Temporäre SAE-Mobilstationskennung

SA

Eigenständiger Betriebsmodus

SAE

Systemarchitektur entwicklung

SAP

Dienstzugangspun kt

SAPD

Dienstzugangspun ktdeskriptor

SAPI

Dienstzugangspun ktkennung

SCC

Sekundärkompone ntenträger, Sekundär-CC

SCell

Sekundärzelle

SC-FDMA

Einzelträger- Frequenzmultiplexzugang

SCG

Sekundärzellengru ppe

SCM

Sicherheitskontext management

SCS

Unterträgerabstan d

SCTP

Datenstromsteuer ungs-Übertragungsprotokoll

SDAP

Dienstdatenanpass ungsprotokoll, Dienstdatenanpassungspr otokollschicht

SDL

Zusatz-Downlink

SDNF

Netzwerkfunktion mit strukturierter Datenspeicherung

SDP

Sessionbeschreibu ngsprotokoll

SDSF

Strukturdatenspeic herungsfunktion

SDU

Dienstdateneinheit

SEAF

Sicherheitsankerfu nktion

SeNB

Sekundär-eNB

SEPP

Sicherheits-Edge-Schutz-Proxy

SFI

Schlitzformatanga be

SFTD

Raumfrequenz-Zeitdiversität, SFN und Frame-Zeitdifferenz

SFN

System-Frame-Nummer

SgNB

Sekundär-gNB

SGSN

Serving GPRS Support Node

S-GW

Serving-Gateway

SI

Systeminformationen

SI-RNTI

Systeminformatio ns-RNTI

SIB

Systeminformatio nsblock

SIM

Teilnehmeridentit ätsmodul

SIP

Sessioninitiiertes Protokoll

SIP

System im Package

SL

Sidelink

SLA

Dienstgütevereinb arung

SM

Sessionmanageme nt

SMF

Sessionmanageme ntfunktion

SMS

Kurznachrichtendi enst

SMSF

SMS-Funktion

SMTC

SSB-basierte Messzeitkonfiguration

SN

Sekundärknoten, Sequenznummer

SOC

System-on-Chip

SON

Selbstorganisieren des Netzwerk SpCell Spezialzelle

SP-CSI-RNTI

Semi-Persistente CSI-RNTI

SPS

Semi-persistente Planung

SQN

Sequenznummer

SR

Planungsanforder ung

SRB

Signalisierungsfun kträger

SRS

Sondierungsrefere nzsignal

SS

Synchronisationss ignal

SSB

SS-BLOCK SSBRI SSB-Ressourcenindikator

SSC

Session- und Dienstkontinuität

SS-RSRP

Synchronisationss ignalbasierte Referenzsignalempfangsl eistung

SS-RSRQ

Synchronisationss ignalbasierte Referenzsignalempfangsq ualität

SS-SINR

Synchronisationss ignalbasiertes Signal-zu-Rausch- und Interferenzverhältnis

SSS

Sekundärsynchron isationssignal

SSSG

Suchraum-Satzgruppe

SSSIF

Suchraum-Satzindikator

SST

Slice-/Diensttypen

SU-MIMO

Einzelbenutzer-MIMO

SUL

Zusatz-Uplink

TA

Timing-Advance, Verfolgungsbereich

TAC

Verfolgungsbereic hscode

TAG

Timing-Advance-Gruppe

TAU

Verfolgungsbereic hsaktualisierung

TB

Transportblock

TBS

Transportblockgrö ße

TBD

Noch zu definieren

TCI

Übertragungskonf igurationsindikator

TCP

Übertragungskom munikationsprotokoll

TDD

Zeitduplex

TDM

Zeitmultiplex

TDMA

Zeitmultiplex-Mehrfachzugang

TE

Endgerät

TEID

Tunnelendpunktke nnung

TFT

Verkehrsflussvorl age

TMSI

Temporäre Mobilteilnehmeridentität

TNL

Netzwerktransport schicht

TPC

Sendeleistungsste uerung

TPMI

Übertragener Vorcodierungsmatrixindi kator

TR

Technischer Bericht

TRP, TRxP

Übertragungsempf angspunkt

TRS

Verfolgungsrefere nzsignal

TRX

Transceiver

TS

Technische Spezifikationen, Technischer Standard

TTI

Übertragungszeiti ntervall

Tx

Übertragung, Übertragen, Sender

U-RNTI

Temporäre UTRAN-Funknetzwerkidentität

UART

Universeller asynchroner Empfänger und Sender

UCI

Uplink-Steuerinformationen

UE

Benutzergerät

UDM

Einheitliches Datenmanagement

UDP

Benutzer-Datagrammprotokoll

UDR

Einheitliches Datenrepositorium

UDSF

Netzwerkfunktion für unstrukturierte Datenspeicherung

UICC

Universal Integrated Circuit Card

UL

Uplink

UM

Unbestätigter Modus

UML

Einheitliche Modellierungssprache

UMTS

Universal Mobile Telecommunications System

UP

Benutzerebene

UPF

Benutzerebenenfu nktion

URI

Uniform Resource Identifier

URL

Uniform Resource Locator

URLLC

Ultrazuverlässige und niedrige Latenz

USB

Universal Serial Bus

USIM

Universelles Teilnehmeridentitätsmod ul

USS

UE-spezifischer Suchraum

UTRA

Terrestrischer UTRA-Funkzugang

UTRAN

Universelles terrestrisches Funkzugangsnetzwerk

UwPTS

Uplink-Pilotzeitschlitz

V2I

Fahrzeug-zu-Infrastruktur

V2P

Fahrzeug-zu-Fußgänger

V2V

Fahrzeug-zu-Fahrzeug

V2X

Fahrzeug-zu-X

VIM

Virtualisierter Infrastrukturmanager

VL

Virtueller Link

VLAN

Virtuelles LAN,

Virtual

Local Area Network

VM

Virtuelle Maschine

VNF

Virtualisierte Netzwerkfunktion

VNFFG

VNF-Forwarding-Graph

VNFFGD

VNF-Forwarding-Graph-Descriptor

VNFM

VNFM-Manager

VoIP

Voice-over-IP, Voice-over-Internetprotokoll

VPLMN

Besuchtes öffentliches terrestrisches VPLMN-Mobilfunknetzwerk

VPN

Virtuelles privates Netzwerk

VRB

Virtueller Ressourcenblock

WiMAX

Worldwide Interoperability for Microwave Access WLANDrahtloses lokales Netzwerk

WMAN

Drahtloses Metropolitan Area NetworkWPANDrahtloses Personal Area Network

X2-C

X2-Steuerebene

X2-U

X2-Benutzerebene

XML

Extensible Markup Language

XRES

Expected User Response

XOR

Exklusiv ODER

ZC

Zadoff-Chu

ZP

Nullleistung

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

3GPP

Third generation partnership project

4G

fourth generation

5G

Fifth generation

5GC

5G core network

ACK

Confirmation

AF

application function

AT THE

Confirmed mode

AMBR

Aggregated maximum bit rate

AMF

Access and mobility management function

AT

access network

NO

Automatic neighbor relationship

AP

Application protocol, antenna port, access point

API

Application programming interface

APN

access point name

ARP

Allocation and Hold Priority

ARQ

Automatic retry request

AS

access stratum

ASN.1

Abstract Syntax Notation One

EXEC

authentication server function

AWGN

Additive white Gaussian noise

BAP

Backhaul Adjustment Protocol

BCH

broadcast channel

BER

Bit Error Ratio

BFD

Beam failure detection

BLER

block error rate

BPSK

Binary phase shift keying

BRASS

Broadband remote access server

BSS

company support system

B.S

base station

BSR

Buffer Status Report

BW

bandwidth

BWP

bandwidth part

C-RNTI

Temporary cellular network identity

APPROX

Carrier Aggregation, Certificate Authority

CAPEX

capital expenditure

CBRA

Competition-based direct access

CC

Device carrier, country code, cryptographic checksum

CCA

Free Channel Rating

CCE

control channel element

CCCH

common control channel

CE

coverage boost

CDM

Content Delivery Network

CDMA

code division access

CFRA

Non-competitive direct access

cg

cell group

CI

cell identity

CID

Cell ID (e.g. positioning method)

CIM

Common information model

CIR

Carrier to Interference Ratio

CK

cipher key

CM

Connection management, conditionally mandatory

CMAS

Commercial mobile notification service

CMD

command

CMS

cloud management system

CO

Conditionally optional

CoMP

Coordinated Multipoint CORESET Control Resource Record

COTS

Ordinary commercial standard

CP

Control plane, cyclic prefix, connection point

CPD

connection point descriptor

CPE

Device at customer site

CPICH

Common pilot channel

CQI

channel quality indicator

CPU

CSI processing unit, central processing unit

C/R

Command/Response Field Bit

CRAN

Cloud Radio Access Network, Cloud RAN

CRB

Common resource block

CRC

Cyclic redundancy check

CRI

channel status information resource indicator,

CSI RS

resource indicator

C-RNTI

cell RNTI

CS

circuit switched

CSAR

Cloud service archive CSI anal condition information

CSI IM

CSI interference measurement

CSI RS

CSI reference signal

CSI RSRP

CSI reference signal reception performance

CSI RSRQ

CSI reference signal reception quality

CSI SINR

CSI signal-to-noise and interference ratio

CSMA

Carrier Sense Multiple Access

CSMA/CA

CSMA with collision avoidance

CSS

Common search space, cell-specific search space

CTS

readiness to send

cw

code word

CWS

Competition window size

D2D

device-to-device

DC

Dual connectivity, direct current, direct voltage

DCI

Downlink Control Information

DF

use flavor

DL

downlink

DMTF

Distributed Management Working Group

DPDK

Data plane development kit

DM-RS, DMRS

demodulation reference signal

DN

data network

DRB

data carrier

DRS

Discovery reference signal

DRX

Discontinuous r reception

broadband

Domain specific language digital subscriber line

DSLAM

DSL access multiplexer

DwPTS

Downlink Pilot Slot E-LANEthernet local network

E2E

end-to-end

ECCA

Enhanced Free Channel Rating, Enhanced CCA

ECCE

Extended control channel element, extended CCE

ED

energy detection

EDGE

Enhanced Data Rates for GSM Evolution (GSM Evolution)

EGMF

Release Rules Management Function

EGPRS

Advanced GPRS

EIR

Device Identity Register

eLAA

Enhanced Licensed Assisted Access, Enhanced LAA

EM

element manager

eMBB

advanced mobile broadband

EMS

element management system

eNB

Evolved NodeB, E-UTRAN Node B

EN-DC

E-UTRA-NR Dual Connectivity

EPC

Evolved Packet Core

EPDCCH

Enhanced PDCCH, Enhanced Downlink Physical Control Channel

EPRE

Energy per resource element

EPS

Evolved Packet System

EREG

Extended REG, extended resource element groups

ETSI

European Telecommunications Standards Institute

SOMETHING

Earthquake and tsunami warning system

eUICC

embedded

UICC,

embedded general purpose integrated circuit board E-UTRA Evolved

UTRA

E-UTRAN Evolved UTRAN

EV2X

Advanced V2X

FIAP

F1 application log

F1-C

F1 control plane interface

F1-U

F1 user level interface

FACCH

Fast associated control channel

FACCH/F

Fast Associated Control Channel/Full Rate

FACCH/H

Fast Associated Control Channel/Half Rate

ACADEMIC SUBJECT

Forward Access Channel

FAUCH

Fast uplink signaling channel

FB

function block

FBI

feedback information

FCC

Federal Communications Commission

FCCH

frequency correction channel

FDD

frequency duplex

FDM

frequency multiple x

FDMA

Frequency multiple x access

FE

front end

FEC

forward error correction

FFS

for further investigation

FFT

Fast Fourier Transform

feLAA

further enhanced licensed assisted access, further enhanced LAA

FN

frame number

FPGA

Field Programmable Gate Array

FR

frequency range

G-RNTI

Temporary GERAN radio network identity

GERAN

GSM EDGE RAN, GSM EDGE radio access network

GGSN

Gateway GPRS support node

GLONASS

Global Navigation Satellite System

gNB

Next-gen NodeB

gNB CU

gNB central processing unit, NodeB central processing unit of the next generation

gNB-DU

distributed gNB unit, next generation distributed NodeB unit

GNSS

Global Navigation Satellite System

GPRS

general packet

radio

service

GSM

Global system for mobile communications,

group

Special Mobile

GTP

GPRS tunnel protocol GTP UGPRS tunnel protocol for user plane

GTS

Switch-off signal (related to WUS)

RUBBER

Globally unique MME identifier

GOOD

Globally unique temporary UE identity

HARQ

Hybrid ARQ, hybrid automatic repeat request

HANDO

handover

HFN

Hyper Frame Number

HO

Hard handover

HLR

Home location register

HN

home network

HO

handover

HPLMN

Public terrestrial mobile network

HSDPA

High speed downlink packet access

HSN

hopping sequence number

HSPA

High speed packet access

HSS

Home Subscriber Server

HSUPA

High speed uplink packet access

HTTP

Hypertext Transfer Protocol

HTTPS

Hypertext Transfer Protocol Secure (https is http/1.1 over SSL, ie port 443) 1-block information block

ICCID

Integrated circuit card identification

IAB

Integrated access and backhaul

ICIC

Inter-Cell Interference Coordination

ID

identity, identifier

IDFT

Inverse Discrete Fourier Transform

ie

information element

IBE

in-band emission

IEEE

Institute of Electrical and Electronics Engineers

IEI

Information element identifier

IEIDL

Information item identification data length

IETF

Internet Engineering Task Force

IF

infrastructure

IN THE

Interference measurement, intermodulation, IP multimedia

IMC

IMS Credentials

IMEI

International Mobile Identity

IMGI

International mobile group identity

IMPI

IP multimedia private identity

IMPU

IP multimedia public identity

IMs

IP multimedia subsystem

IMSI

International mobile subscriber identity

Internet of Things

internet of things

IP

internet protocol

IPsec

IP Security, Internet Protocol Security

IP CAN

IP connectivity access network

IP M

IP multicast

IPv4

Internet protocol version 4

IPv6

Internet protocol version 6

IR

Infrared

IS

Synchronous

IRP

integration reference point

ISDN

Integrated Services Digital Network

ISIM

IM service identity module

ISO

International Organization for Standardization

ISP

internet service provider

IMF

Interworking function

I-WLAN

interworking

WIRELESS INTERNET ACCESS

Convolutional code constraint length, unique USIM key

kB

kilobytes (1000 bytes)

kbps

kilobits per second

Kc

encryption key

Ki

Individual subscriber authentication key

KPI

key performance indicator

KQI

key quality indicator

ASI

key set identifier

ksps

Kilo symbols per second

KVM

Virtual kernel machine

L1

Layer 1 (physical layer)

L1 RSRP

Layer 1 reference signal received power

L2

Layer 2 (data link layer)

L3

Layer 3 (network layer)

LAA

Licensed Assisted Access

LAN

Local Area Network

LBT

Listen Before Talk

LCM

life cycle management

LCR

low chip rate

LCS

location services

LCID

Logic Channel ID

LI

shift indicator

LLC

Logic link control, low layer compatibility

LPLMN

Local PLMN

LPP

LTE positioning protocol

LSB

Least Significant Bit

LTE

Long Term Evolution

LWA

LTE WiFi Aggregation

LWIP

LTE/WLAN radio level integration with IPsec tunnel

LTE

Long Term Evolution

M2M

machine-to-machine

MAC

Media access control (protocol layer context)

MAC

Message authentication code (security/encryption context)

MAC-A

MAC for authentication and key agreement (context TSG T WG3)

MAC IMAC

on data integrity of signaling messages (context TSG T WG3)

MANO

management and orchestration

MBMS

Multimedia Broadcast and Multicast Service

MBSFN

Multimedia Broadcast Multicast Service Single Frequency Network

MCC

Cellular Country Code

MCG

master cell group

MCOT

Maximum channel occupancy time

MCS

Modulation and Coding Scheme

MDAF

Management data analysis function

MDAs

Management data analysis service

MDT

Drive test minimization

ME

mobile device

MeNB

Master eNB

MER

message error ratio

MGL

measurement gap length

MRP

Measurement gap repeat period

MIB

Master information block, management information base

MIMO

Multiple input multiple output

MLC

Mobile location center

mm

mobility management

MME

mobility management entity

MN

master node

MnS

management service t

MON

Measurement object, mobile origin

MPBCH

MTC Physical Broadcast Channel

MPDCCH

MTC Physical Downlink Control Channel

MPDSCH

MTC physical downlink shared channel

MPRACH

MTC Physical Random Access Channel

MPUSCH

MTC Physical Uplink Shared Channel

MPLS

Multi-protocol label switching

MS

mobile station

MSB

Most Significant Bit

MSC

mobile phone exchange

MSI

Minimum system information, MCH planning information

MSID

mobile station identifier

MSIN

mobile station identification number

MSISDN

Mobile subscriber ISDN number

MT

Mobile completed, mobile completed

MTC

Machine type communication mMTCMassive MTC, massive machine type communication

MU-MIMO

Multi-user MIMO

MWUS

MTC wake-up signal, MTC-WUS

NAKED

Negative Confirmation

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 detection

NE-DC UTRA

NR-E Dual Connectivity

NEF

network discovery function

NF

network function

NFP

Network forwarding path

NFPD

Network forwarding path descriptor

NFV

Network function virtualization

NFVI

NFV infrastructure

NFVO

NFV Orchestrator

NG

Next generation, next gen

NGEN DC

NG-RAN-E-UTRA-NR dual connectivity

NM

network manager

NMS

Network Management System N-PoP network point of presence

NMIB, N-MIB

Narrowband MIB

NPBCH

Narrowband Physical Broadcast Channel

NPDCCH

Narrowband physical downlink control channel

NPDSCH

Narrowband physical downlink shared channel

NPRACH

Narrowband Physical Random Access Channel

NPUSCH

Narrow band physical uplink shared channel

NPSS

Narrowband primary synchronization signal

NSSS

Narrowband secondary synchronization signal

NO

New radio, neighborhood relationship

NRF

NF repository function

NRS

Narrowband reference signal

NS

network service

NSA

Non-standalone mode of operation

NSD

Network service descriptor

NSR

Network Service Record

NSSAI

Network slice selection assistant information

S-NNSAI

Single NSSAI

NSSF

Network slice selection function

NW

network

NWUS

Narrowband wake-up signal, Narrowband WUS

NZP

non-zero performance

O&M

Operation and maintenance

ODU2

Optical Channel Data Unit - Type 2

OFDM

Orthogonal Frequency Division Multiplexing

OFDMA

Orthogonal frequency division multiplex access

OOB

Out of band

OOS

Out of sync

OPEX

operating cost

OSI

Other system information

OSS

operational support system

OTA

Over-the-Air PAPR Peak performance to average performance

PAR

peak to mean

PBCH

Physical Broadcast Channel

personal computer

Power Control, Personal Computer

PCC

Primary component carrier, primary CC

PCell

primary cell

PCI ID,

Physical cell-physical cell identity

PCEF

Policy and Billing Enforcement Function

PCF

policy control function

PCRF

Policy control and billing rule functionality

PDCP

packet data convergence protocol, packet data convergence protocol layer

PDCCH

Physical Downlink Control Channel

PDCP

Packet data convergence protocol

PDN

Packet data network, public data network

PDSCH

Physical Downlink Shared Channel

PDU

log data unit

PEI

Permanent device identifiers

PFD

packet flow description

P-GW

PDN GATEWAY

PHICH

Physical hybrid ARQ indicator channel

PHY

physical layer

PLMN

Public terrestrial mobile network

pin code

Personal identification number

p.m

performance measurement

PMI

Precoding matrix indicator

PNF

Physical Network Function

PNFD

Physical network function descriptor

PNFR

Physical network function record

POC

PTT over Cellular

PP, PTP

point to point

PPP

point-to-point protocol

PRACH

Physical RACH

PRB

Physical resource block

PRG

Physical resource block group

ProSe

Proximity Services, Proximity-Based Service

PRS

positioning reference signal

PRR

Packet reception radio

hp

parcel services

PSBCH

Physical Sidelink Broadcast Channel

PSDCH

Physical Sidelink Downlink Channel

PSCCH

Physical Sidelink Control Channel

PSFCH

Physical Sidelink Feedback Channel

PSSCH

Physical Sidelink Shared Channel PSCell Primary SCell

PSS

Primary synchronization signal

PSTN

landline

PT RS

Phase tracking reference signal

PTT

Push to talk

PUCCH

Physical Uplink Control Channel

PUSH

Physical uplink shared channel

QAM

quadrature amplitude modulation

QCI

QoS class of identifier

QCL

quasi-colocalization

QFI

QoS Flow ID, QoS Flow Identifier

QoS

quality of service

QPSK

Quadrature (quaternary) phase shift keying

QZSS

Quasi-zenith satellite system

RA-RNTI

Random access RNTI

RAB

Radio access bearer, direct access burst

RACH

Random Access Channel

RADIUS

Remote Authentication Dial-In User Service

RAN

radio access network

EDGE

RANDom number (used for authentication)

RARE

Direct Access Response

ADVICE

radio access technology

ROUGH

Routing area update

RB

Resource block, radio bearer

RBG

resource block group

REG

Resource item group

rel

Release

REQ

Requirement

RF

radio frequency

RI

rank indicator

RIV

Resource indicator value

RL

wireless link

RLC

Radio Link Control ,Radio Link Control Layer

RLC

AM Confirmed RLC mode

RLC

UM Unconfirmed RLC mode

RLF

radio link failure

RLM

radio link monitoring

RLM-RS

Reference signal for RLM

rm

Registration Management

RMC

Reference measuring channel 1

RMSI

Remaining MSI, remaining minimal system information

RN

relay node

RNC

wireless network control

RNL

wireless network layer

RNTI

Temporary wireless network identifier

ROHC

Robust header compression

RRC

Radio resource control, radio resource control layer

RRM

radio resource management

RS

reference signal

RSRP

Reference signal reception performance

RSRQ

Reference signal reception quality

RSSI

Received signal strength indicator

RSU

roadside unit

RSTD

reference signal time difference

RTP

real-time log

RTS

ready to broadcast

RTT

orbital period

Rx

Receiving, receiving, receiver

S1AP

S1 application protocol

S1 MME

S1 for the control plane

S1-U

S1 for the user level

S-GW

serving gateway

S-RNTI

Temporary SRNC radio network identity

S-TMSI

Temporary SAE mobile station identifier

SA

Stand alone mode of operation

SAE

System architecture development

SAP

service access point

SAPD

Service access point descriptor

SAPI

Service Access Point Identifier

SCC

Secondary component carrier, secondary CC

SCell

secondary cell

SC-FDMA

Single carrier frequency division multiplex access

SCG

secondary cell group

SCM

Security context management

SCS

subcarrier spacing d

SCTP

Flow Control Transmission Protocol

SDAP

Service data adaptation protocol, service data adaptation protocol layer

SDL

Additional downlink

SDNF

Network function with structured data storage

SDP

Session Description Log

SDSF

Structure data storage function

SDU

service data unit

SEAF

Safety anchor function

SeNB

Secondary eNB

SEPP

Security Edge Protection Proxy

SFI

Slot format specification be

SFTD

Spatial Frequency Time Diversity, SFN and Frame Time Difference

SFN

System frame number

SgNB

Secondary gNB

SGSN

Serving GPRS Support Node

S-GW

serving gateway

S.I

system information

SI RNTI

System information RNTI

SIB

System information block

SIM

Subscriber identity module

SIP

Session-Initiated Protocol

SIP

system in the package

SL

side link

SLA

Service Level Agreement

SM

session management

SMF

Session management function

SMS

short message service

SMSF

SMS function

SMTC

SSB-based measurement time configuration

SN

Secondary node, sequence number

SOC

system on chip

SUN

Self-organizing the network SpCell special cell

SP-CSI-RNTI

Semi-persistent CSI RNTI

SPS

Semi-persistent scheduling

SQN

sequence number

SR

planning requirement

SRB

signaling radio bearer

SRS

Probing reference signal

ss

synchronization signal

SSB

SS-BLOCK SSBRI SSB resource indicator

SSC

Session and Service Continuity

SS RSRP

Synchronization signal-based reference signal reception performance

SS RSRQ

Synchronization signal-based reference signal reception quality

SS SINR

Synchronization signal-based signal-to-noise and interference ratio

SSS

Secondary synchronization signal

SSSG

search space set group

SSIF

Search Space Sentence Indicator

SST

Slice/Service Types

SU MIMO

Single-user MIMO

SUL

additional uplink

TA

Timing advance, tracking range

TAC

Tracking area code

DAY

Timing Advance Group

DEW

Tracking area update

TB

transport block

TBS

transport block size

TBD

Still to define

TCI

Transmission configuration indicator

TCP

transmission communication protocol

TDD

time duplex

TDM

time division

TDMA

Time Division Multiple Access

TE

end device

TEID

Tunnel endpoint identifier

TFT

Traffic flow template

TMSI

Temporary Mobile Subscriber Identity

TNL

network transport layer

TPC

transmit power control

TPMI

Transmitted precoding matrix indicator

TR

technical report

TRP, TRxP

transmission reception point

TRS

Tracking reference signal

TRX

transceivers

TS

Technical Specifications, Technical Standard

TTI

transmission time interval

tx

Transmission, transmitting, transmitter

U-RNTI

Temporary UTRAN radio network identity

UART

Universal asynchronous receiver and transmitter

UCI

Uplink Control Information

UE

user device

UDM

Uniform data management

UDP

User Datagram Log

UDR

Unified data repository

UDSF

Network function for unstructured data storage

UICC

Universal Integrated Circuit Card

UL

uplink

AROUND

Unconfirmed mode

UML

Uniform modeling language

UMTS

Universal Mobile Telecommunications System

UP

user level

UPF

User level function

URI

Uniform Resource Identifier

URL

Uniform resource locator

URLLC

Ultra reliable and low latency

USB

Universal Serial Bus

USIM

Universal Subscriber Identity Module

USS

UE specific search space

UTRA

Terrestrial UTRA radio access

UTRAN

Universal terrestrial radio access network

UwPTS

Uplink Pilot Timeslot

V2I

vehicle-to-infrastructure

V2P

vehicle-to-pedestrian

V2V

vehicle-to-vehicle

V2X

vehicle-to-X

VIM

Virtualized infrastructure manager

VL

virtual link

VLAN

virtual LAN,

virtual

Local Area Network

VM

Virtual machine

VNF

Virtualized network function

VNFFG

VNF forwarding graph

VNFFGD

VNF forwarding graph descriptor

VNFM

VNFM manager

VOIP

Voice over IP, Voice over Internet Protocol

VPLMN

Visited public terrestrial VPLMN mobile network

VPN

Virtual Private Network

VRB

Virtual resource block

WiMAX

Worldwide Interoperability for Microwave Access WLANWireless local area network

WMAN

Wireless Metropolitan Area NetworkWPANDWireless Personal Area Network

X2-C

X2 control plane

X2-U

X2 user level

XML

Extensible Markup Language

XRES

Expected User Response

XOR

Exclusive OR

ZC

Zadoff-Chu

ZP

zero power

terminology

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

The term "circuitry" as used herein refers to hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated or group) and/or a memory (shared, dedicated or group), a Application Specific Integrated Circuit (ASIC), a Field Programmable Device (FPD) (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 SoC), digital signal processors (DSPs), etc. designed to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the functionality described. The term "circuitry" may also refer to a combination of one or more hardware elements (or a combination of circuitry used in an electrical or electronic system) with the program code used to perform the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term "processor circuitry" as used herein refers to, forms part of, or includes circuitry capable of sequentially and automatically executing a sequence of arithmetic or logical operations or recording, storing, and/or transmitting digital data . The processing circuitry may include one or more processing cores for executing instructions and one or more memory structures for storing contain program and data information. The term "processor circuitry" 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 three-core processor, a quad-core processor, and/or any other device contained in capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. The processing circuitry may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms "application circuitry" and/or "baseband circuitry" may be considered synonymous and may be referred to as "processor circuitry".

The term "interface circuitry," as used herein, refers to, forms part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.

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

The term "network element" as used herein refers to a physical or virtualized device and/or physical or virtualized infrastructure used to provide wired or wireless communication network services. The term "network element" may be used interchangeably with and/or as a networked computer, networked hardware, network device, network node, router, switch, hub, bridge, radio network controller, RAN device, a RAN node, a gateway, a server, a virtualized VNF, NFVI and/or the like.

The term "computer system" as used herein refers to any type of interconnected electronic device, computing device, or component thereof. Additionally, the term "computer system" and/or "system" may refer to various components of a computer that are communicatively coupled to one another. Further, the term "computer system" and/or "system" may refer to multiple computing devices and/or multiple computing systems that are communicatively coupled to one another and configured to share computing and/or networking resources.

The term "device", "computing device" or the like, as used herein, refers to a computing device or computer system with program code (e.g., software or firmware) specifically designed to provide a specific computing resource. A "virtual device" is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates or is otherwise dedicated to a computing device to provide a specific computing resource.

The term "resource" as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a specific device, such as computing devices, mechanical devices, storage space, processor /CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A "hardware resource" may refer to compute, storage, and/or network resources provided by one or more physical hardware elements. A "virtualized resource" may refer to compute, storage, and/or network resources provided by a virtualization infrastructure for an application, device tion, a system, etc. are provided. The term "network resource" or "communications resource" may refer to resources that computing devices/systems can access over a communications network. The term system resources can refer to any type of shared entity for providing services and can include computing and/or network resources. System resources can be viewed as a set of coherent functions, network data objects, or services that are accessible through a server, where such system resources reside on a single host or multiple hosts and are uniquely identifiable.

The term "channel" as used herein refers to any transmission medium, tangible or intangible, used to communicate data or a data stream. The term "channel" may be synonymous with and/or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", " radio frequency carrier” and/or any other similar term denoting a path or any medium over which data is communicated. Additionally, as used herein, the term "link" refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

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

The terms "coupled", "communicatively coupled", along with derivatives thereof, are used herein. The term "coupled" can mean that two or more elements are in direct physical or electrical contact with each other, can mean that two or more elements contact indirectly but still co-operate or interact with each other, and/or can mean that one or more other elements are coupled or connected between the elements, referred to as being coupled together. The term "directly coupled" can mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with one another through a means of communication, including through a wire or other interconnection connection, through a wireless communication channel or link, and/or the like.

The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to individual content of an information item or a data item that contains content.

The term "SMTC" refers to an SSB-based measurement timing configuration designed by SSB-MeasurementTimingConfiguration.

The term "SSB" refers to an SS/PBCH BLOCK.

The term "a primary cell" refers to the MCG cell operating on the primary frequency in which the UE either performs the initial connection establishment procedure or initiates the connection restoration procedure.

The term "SCG primary cell" refers to the SCG cell in which the UE performs random access when performing the reconfiguration-with-sync procedure for DC operation.

The term "secondary cell" refers to a cell that provides additional radio resources on a special purpose cell for a UE designed with CA.

The term "secondary cell group" refers to the subset of serving cells, which includes the PSCell and zero or more secondary cells for a UE configured with DC.

The term "serving cell" refers to the primary cell for a UE in RRC_CONNECTED not designed with CA/DC, where there is only one serving cell comprising the primary cell.

The term "serving cell" or "serving cells" refers to the set of cells comprising the special cell(s) and all secondary cells for a UE in RRC_CONNECTED designed with CA/.

The term "special cell" refers to the MCG's PCell or the SCG's PSCell for DC operation; otherwise, the term "special cell" refers to the Pcell.

QUOTES INCLUDED IN DESCRIPTION

This list of documents cited by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent Literature Cited

• US63051561 [0001]
• CN2020103528 [0001]

Claims (23)

One or more non-transitory computer-readable media (NTCRM) having instructions stored thereon that, when executed by one or more processors, cause a user equipment (UE) to: determining a last symbol of a downlink physical shared channel (PDSCH); determining a downlink physical control channel (PDCCH) monitoring opportunity for a PDCCH based on the last symbol of the PDSCH; and Monitoring a PDCCH in the particular PDCCH monitoring occasion. One or more NTCRM after claim 1 , where the PDCCH monitoring opportunity begins in a symbol that is a number of one or more symbols after the last symbol of the PDSCH. One or more NTCRM after claim 2 wherein the instructions, when executed, further cause the UE to receive an indication of the number. One or more NTCRM after one of Claims 1 until 3 wherein the PDSCH is a first PDSCH and wherein the instructions, when executed, are to further cause the UE to receive the PDCCH in the PDCCH monitoring opportunity, the PDCCH scheduling a second PDSCH or an uplink physical shared channel (PUSCH). One or more NTCRM after claim 4 wherein the PDCCH monitoring opportunity is a first PDCCH monitoring opportunity, the second PDSCH collides with a second PDCCH monitoring opportunity, and wherein the instructions, when executed, are to further cause the UE to: determine a relative priority of the second PDSCH in the comparison to the second PDCCH monitoring opportunity; and selecting one of decoding the second PDSCH or monitoring another PDCCH in the PDCCH monitoring opportunity based on the determined relative priority. One or more NTCRM after one of Claims 1 until 5 , wherein the PDCCH monitoring opportunity is a first PDCCH monitoring opportunity, wherein the first PDCCH monitoring opportunity overlaps with a second PDCCH monitoring opportunity, and wherein the monitoring of the PDCCH in the first PDCCH monitoring opportunity is compared based on a relative priority of the first PDCCH monitoring opportunity performed with the second PDCCH monitoring opportunity. One or more NTCRM after one of Claims 1 until 6 , wherein the instructions, when executed, are to further cause the UE to receive the PDCCH in the PDCCH monitoring opportunity, the PDCCH enabling uplink or downlink communication in an unlicensed spectrum, in a 5G frequency range 2 (FR2), or for ultra-reliable communication low latency (URLLC) plans. One or more non-transitory computer-readable media (NTCRM) having instructions stored thereon that, when executed by one or more processors, cause a next-generation NodeB (gNB) to: determining a last symbol of a downlink physical shared channel (PDSCH) transmitted to a user equipment; determining a downlink physical control channel (PDCCH) monitoring opportunity for a PDCCH based on the last symbol of the PDSCH; and Encoding a PDCCH for transmission to the UE in the particular PDCCH monitoring occasion. One or more NTCRM after claim 8 , where the PDCCH monitoring opportunity begins in a symbol that is a number of one or more symbols after the last symbol of the PDSCH. One or more NTCRM after claim 9 wherein the instructions, when executed, further cause the gNB to encode a message for transmission to the UE that includes an indication of the number. One or more NTCRM after one of Claims 8 until 10 , where the PDCCH is to schedule a downlink transmission. One or more NTCRM after claim 11 , where PDSCH is a first PDSCH and where the downlink transmission includes a second PDSCH. One or more NTCRM after claim 11 wherein the PDCCH is to schedule an uplink communication and wherein the instructions, when executed, are further to cause the gNB to receive the uplink communication. One or more NTCRM after one of Claims 8 until 13 , wherein the instructions whereby the PDCCH shall schedule an uplink or downlink communication in an unlicensed spectrum, in a 5G frequency range 2 (FR2) or for ultra-reliable low latency communication (URLLC). One or more non-transitory computer-readable media (NTCRM) having instructions stored thereon that, when executed by one or more processors, cause a user equipment (UE) to: receiving downlink control information (DCI) to indicate a resource allocation for one or more transport blocks, the resource allocation including one or more symbol alignment units (SAUs); and Transmitting or receiving the one or more transport blocks based on the DCI. One or more NTCRM after claim 15 , wherein the resource allocation includes one or more code block groups (CBGs) mapped to one or more SAUs of one or more symbols. One or more NTCRM after one of Claims 15 until 16 , where the SAUs contain all the time-frequency resources of one or more symbols. One or more NTCRM after one of Claims 15 until 17 , wherein the DCI includes a start and length indicator value (SLIV) to indicate a time resource of a first SAU of the one or more SAUs. One or more NTCRM after one of Claims 16 until 18 , wherein the DCI includes a start and length indicator value (SLIV) to indicate a time resource of a first CBG of the one or more CBGs. One or more NTCRM after one of Claims 15 until 19 , wherein the DCI schedules the transmission of multiple transport blocks and wherein the resource allocations for individual transport blocks of the multiple transport blocks correspond to consecutive time-frequency resources. One or more NTCRM after one of Claims 16 until 20 , wherein the DCI schedules the transmission of multiple transport blocks and wherein the resource allocations for individual CBGs of the multiple transport blocks correspond to consecutive time-frequency resources. One or more NTCRM after one of Claims 15 until 21 wherein the DCI schedules the transmission of multiple transport blocks and wherein the SAUs of the multiple transport blocks are interleaved with each other in a time domain. One or more NTCRM after one of Claims 16 until 22 wherein the DCI schedules the transmission of multiple transport blocks and wherein the CBGs of the multiple transport blocks are interleaved with each other in a time domain.

Images