KR20230037498A - Techniques for Scheduling Control Channel Transmission and Data Transmissions for Slot-less Operation - Google Patents

Abstract

Systems, apparatuses, methods, and computer readable media for scheduling data transmissions with support for symbol alignment and/or early termination are provided. Data transmissions may be on a carrier frequency above 52.6 GHz. Additionally, embodiments provide techniques for control channel transmission for slot-less operation. Other embodiments may be described and/or claimed.

Description

Techniques for Scheduling Control Channel Transmission and Data Transmissions for Slot-less Operation

<Cross Reference to Related Applications>

This application claims priority to U.S. Provisional Patent Application No. 63/051,561, filed July 14, 2020, and International Application No. PCT/CN2020/103528, filed July 22, 2020.

<Technical field>

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

Mobile communications has evolved significantly from early voice systems to today's highly sophisticated integrated communications platforms. The next-generation wireless communication system, 5G or new radio (NR), will provide anytime, anywhere access to information and sharing of data by various users and applications. NR is expected to be an integrated network/system that aims to meet very different and sometimes conflicting performance dimensions and services. These various multi-dimensional requirements are driven by different services and applications. In general, NR will evolve based on additional potential new Radio Access Technologies (RATs) with 3GPP LTE-Advanced to enrich people's lives with better, simpler and seamless wireless connectivity solutions. will be. NR will enable everything connected by wireless and deliver fast and rich content and services.

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

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 structure, architectures, interfaces, techniques, etc. to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of this disclosure that various aspects of the various embodiments may be practiced in other instances that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this document, the phrase “A or B” means (A), (B) or (A and B).

Various embodiments herein include techniques to be implemented in a wireless cellular network. For example, embodiments include techniques for scheduling data transmissions for carrier frequencies above 52.6 GHz. Additionally, embodiments include techniques for control channel transmission for slot-less operation.

above 52.6 GHz carrier Scheduling data transmissions over frequency

Systems operating at carrier frequencies above 52.6 GHz, especially for terahertz communications, are expected to require larger subcarrier spacing to avoid significant phase noise. For example, if a larger subcarrier spacing such as 1.92 MHz or 3.84 MHz is employed, the slot duration may be very short. For example, for a 1.92 MHz subcarrier spacing, the duration of one slot is approximately 7.8 μs. This very short slot duration may not be sufficient for higher layer processing including Medium Access Layer (MAC) and Radio Link Control (RLC) and the like. To address this issue, next generation NodeBs (gNBs) will schedule downlink (DL) or uplink (UL) data transmissions across slot boundaries with long transmission durations. can In other words, when scheduling data transmission, the concept of slots may not be needed. 1 illustrates an example of a long physical downlink shared channel (PDSCH) transmission duration.

In DL transmission, when the gNB has already sent DL downlink control information (DCI) or the previous PDSCH transmission is still in progress, more DL traffic can reach the gNB. Since the gNB must transmit a new DL DCI for scheduling the PDSCH, data transmissions are delayed. One solution may be to allow the gNB to schedule more DL resources in the buffer than are currently required to transmit DL data. As a result, when new DL traffic arrives, the gNB can continue PDSCH transmission for the new DL traffic on the scheduled DL resource. On the other hand, when there is no newly incoming DL traffic, scheduled DL resources need to be released earlier, eg, early termination of PDSCH transmission. In fact, besides the case of lack of new DL traffic, there may be other reasons why the gNB also needs to end DL transmission earlier. 2 illustrates an example in which allocated DL resources can carry 10 CBs. However, DL transmission can only end after transmission of 6 CBs.

In the existing NR code block (CB) to time/frequency resource mapping, there is no special consideration for symbols used to carry a CB or CB group (CBG). As a result, different numbers of symbols may be occupied for different CBs or CBGs. Also, CBs tend to be split into multiple symbols. This irregular mapping between CBs and symbols causes pipelined receive (Rx) processing to require variable times to decode different CBs of a transport block (TB).

On the other hand, certain CBs may require longer waiting times. For example, in FIG. 3, there is a 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. Irregular stalls in the Rx processing pipeline can cause inefficiency and greater latency, which is undesirable for application in future 5G and 6G communication systems.

Various embodiments herein provide techniques for scheduling physical shared channel transmissions to allow for efficient symbol alignment and early termination operation. Detailed techniques for scheduling data transmissions supporting early termination and symbol alignment for carrier frequencies above 52.6 GHz, for example, are described herein.

For DL or UL transmission, TB from the MAC layer is transmitted at the physical layer. For hybrid automatic repeat request (HARQ) transmission of DL transmission, a single HARQ-ACK bit may be reported by the UE for the TB. Alternatively, if a code block group (CBG) based transmission is configured, e.g. a TB is divided into n CBGs (n≤N), and a CBG consists of one or multiple code blocks (CBs) . The UE may report n or N HARQ-ACK bits for the TB. One HARQ-ACK bit is reported for each CBG. N is the maximum number of CBGs that can be configured by higher layers. CBG can be mapped to all time/frequency resources of a particular contiguous symbol, e.g., symbol alignment is achieved for CBG.

Alternatively, every group of X CBs may be mapped to all time/frequency resources of Y consecutive symbols. In some embodiments, X may be prime relative to Y. The set of Y contiguous symbols in the resource allocation is a symbol ordered unit (SAU). CBG may be mapped to SAU. Alternatively, a CBG may be mapped to one or multiple SAUs. Alternatively, a SAU may consist of one or multiple CBGs. One 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 to all time/frequency resources of two symbols. A TB scheduled by DCI is divided into 4 CBGs, and each CBG consists of 2 SAUs.

Start and length indicator ( SLIV )

In existing NR systems, the time domain resource allocation (TDRA) of TB is indicated in the DCI. A row of the TDRA table is the starting symbol S for the start of the slot, and the number L of consecutive symbols counted from the symbol S allocated to the PDSCH or physical uplink shared channel (PUSCH), L, e.g. and a length indicator ( SLIV ). With this scheme, a TB is mapped to L symbols, but it is not guaranteed that any CB or CBG can end at a symbol boundary. Time domain resource allocation can be specifically designed to facilitate symbol alignment. In this case, the number of CBGs per TB can be configured by higher layer signaling, indicated through DCI, or derived by the maximum length and the number of symbols for the CBG.

In one option, the DCI's SLIV indicates the specific time resource used by the CBG. The size of the CBG may be determined by a modulation and coding scheme (MCS), L denoted SLIV , if applicable, and frequency resource allocation. By this scheme, it is guaranteed that the CBG is mapped to multiple consecutive symbols.

In another option, the DCI's SLIV indicates the time resource used by the SAU. The number of bits transmitted in the SAU may be determined by the MCS, L denoted by SLIV if applicable, and the frequency resource allocation. Consecutive symbols of SAU carry one or multiple CBs. For this option, given the SLIV indication, the association between SAU and CBG (e.g., how many CBGs map to SAU or how many SAUs form CBG) can be shown separately within the DCI, or , may be configured through radio resource control (RRC) signaling, or may be fixed for a specific subcarrier interval.

for early termination granularity (Granularity)

To support early termination of a PDSCH or PUSCH transmission, a granularity of early termination may be determined.

In one option, early termination is supported at the end of transmission of each TB or all N TBs, where N is greater than one. Alternatively, early termination is not allowed for the first X TBs, and early termination is allowed for all Y TBs after the first X TBs. X and Y are either predefined or configured by higher layers. Note that this may apply in 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 one. Alternatively, early termination is not allowed for the first X CBGs, and early termination is allowed for all Y CBGs after the first X CBGs. X≥1, Y≥1. X and Y are either preconfigured or configured by higher layers. Note that this can be applied in the case of single-TB based scheduling, where a single DCI is used to schedule one PDSCH or PUSCH, and the PDSCH or PUSCH consists of one or more CB/CBGs.

In one option, early termination is supported at the end of transmission of each SAU or all N SAUs, where N is greater than one. Alternatively, early termination is not allowed for the first X SAUs, and early termination is allowed for all Y SAUs after the first X SAUs. X≥1, Y≥1. X and Y can be predefined or configured by higher layers.

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

In one option, early termination is not allowed for the first X TBs, and early termination is allowed for all Y SAUs after the first X TBs. X≥1, Y≥1. X and Y can be predefined or configured by higher layers.

to DCI Single TB Scheduling by

Embodiments for the case of single TB based transmission scheduled by DCI are provided as follows.

In one embodiment, DCI may schedule PDSCH or PUSCH carrying only one TB. A TB is segmented into multiple CBGs. Each CBG contains one or multiple CBs. Symbol alignment is achieved for each CBG. In this case, SLIV of DCI may indicate a time resource of CBG. The maximum number of CBGs in a TB can be configured by higher layer signaling. Alternatively, the maximum length of the allocated time resource for PDSCH or PUSCH may be configured so that the number of CBGs in the TB is derived by the maximum length and the number of symbols for the CBG. Alternatively, the maximum number of CBGs of the current TB may be dynamically indicated in the DCI or a combination of RRC signaling and dynamic indication by the DCI. Transmission of PDSCH or PUSCH may end at a symbol boundary of CBG.

5 illustrates the case of a single TB scheduled with multiple CBGs by DCI. In this case, SLIV indicates the time resource of the CBG, eg, each CBG is mapped to all time/frequency resources of 4 symbols. Thus, symbol alignment is achieved for CBG. For example, if the last CBG was not transmitted due to early termination, the TB consists of only 3 valid CBGs. However, the UE may still need to report 4 HARQ-ACK bits for TB to have a constant payload size of HARQ-ACK.

In one option, for HARQ-ACK feedback, the UE can generate one HARQ-ACK bit for each CBG. To schedule retransmission of the corresponding TB, a CBG transmission indicator (CBGTI) may be used to indicate whether to retransmit for each CBG. For example, when the kth bit of CBGTI is '1', retransmission of the kth CBG is scheduled.

의 사이즈를 가질 수 있다. 이러한 방식으로, UE가 초기 송신들에서 송신된 CBG들의 정확한 수를 검출하지 못하는 때에도, UE는 송신된 CBG들의 정확한 수를 알 수 있다.In another option, if the maximum number of CBGs is large, for example more than 8, the overhead of CBGTI is significantly higher in DCI. In this case, CBG-based HARQ-ACK feedback may not be used. That is, only one HARQ-ACK bit for TB is reported. Within the DCI triggering the TB's retransmission, the actual number of CBGs transmitted by the gNB may be indicated. For example, a field denoting the maximum number of CBGs as N and indicating the actual number of CBGs transmitted is

can have the size of In this way, even when the UE does not detect the exact number of CBGs transmitted in initial transmissions, the UE can know the exact number of CBGs transmitted.

에 매핑된다. 대안적으로, 연속 CBG들은, 존재하는 경우, 동일한 HARQ-ACK 비트에 매핑될 수 있으며, 예를 들어, CBG n은 HARQ-ACK 비트

에 매핑된다.In another option, HARQ-ACK bundling of CBGs can be supported 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 mapped to HARQ-ACK bits may be predefined or configured by higher layers. Alternatively, the number of CBGs mapped to HARQ-ACK bits may be dynamically indicated in DCI or a combination of RRC signaling and dynamic indication by DCI. The last HARQ-ACK bit before the end of transmission may have fewer CBGs. The maximum number of CBGs is denoted by N, the maximum number of HARQ-ACK bits per TB is M, and the N CBGs are mapped to M HARQ-ACK bits. In case N CBGs are grouped evenly and cannot be mapped to M HARQ-ACK bits, the last group(s) may consist of slightly fewer or more CBGs. Evenly distributed CBGs, if present, can be mapped to the same HARQ-ACK bit, e.g., CBG n is the HARQ-ACK bit

is mapped to Alternatively, consecutive CBGs, if present, may be mapped to the same HARQ-ACK bit, e.g. CBG n is the HARQ-ACK bit

is mapped to

In one embodiment, DCI may schedule PDSCH or PUSCH carrying only one TB. A TB is segmented into multiple SAUs. Each SAU contains one or multiple CBs. Symbol alignment is achieved for each SAU. In this case, SLIV of DCI may indicate the time resource of SAU. The maximum number of SAUs in TB can be configured by higher layer signaling. As an alternative, the maximum length of the allocated time resource for PDSCH or PUSCH can be configured so that the number of SAUs in TB is derived by the maximum length and the number of symbols for SAU. As a further alternative, the maximum number of SAUs of the current TB may be dynamically indicated in the DCI or indicated by a combination of RRC signaling and dynamic indication by the DCI. Transmission of PDSCH or PUSCH may end at the symbol boundary of SAU.

One or more SAUs may be grouped into CBGs. The number of SAUs for CBG may be predefined or configured by higher layers. Alternatively, the number of SAUs for CBG may be dynamically indicated in DCI or a combination of RRC signaling and dynamic indication by DCI. The last CBG before the end of transmission may have fewer SAUs. Alternatively, the SAU(s) constituting the CBG may be determined by the total number of SAUs and the number of CBGs.

에 매핑된다. 대안적으로, 연속적인 SAU들은, 존재하는 경우, 동일한 CBG에 매핑될 수 있으며, 예를 들어, SAU n은 The maximum number of SAUs is denoted by N, the maximum number of CBGs, eg, the maximum number of HARQ-ACK bits per TB is M, and N SAUs are mapped to M CBGs. If N SAUs cannot be evenly grouped into M CBGs, the last CBG(s) may consist of slightly fewer or more SAUs. Evenly distributed SAUs, if present, can be mapped to the same CBG, e.g., SAU n is

is mapped to Alternatively, consecutive SAUs, if present, may be mapped to the same CBG, e.g., SAU n is

is mapped to

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

7 illustrates the case of a single TB scheduled with multiple CBGs by DCI. In this case, SLIV indicates the time resource of SAU, for example, each SAU is mapped to all time/frequency resources of two symbols. Thus, symbol alignment is achieved for SAU. CBG k consists of two SAUs with indices k and k+4. For example, even if the last two SAUs were not transmitted due to early termination, the TB still consists of 4 CBGs. Each CBG has a reduced CBG size. However, the last two CBGs each have only one CBG. The report bits of the 4 HARQ-ACK bits are all useful indications for the 4 CBGs.

For HARQ-ACK feedback, the UE can generate one HARQ-ACK for each CBG. In this way, the number of reported HARQ-ACK bits per TB can be limited. For example, the maximum number of HARQ-ACK bits per TB is 8. To schedule retransmission of a TB, a CBG transmission indicator (CBGTI) may be used to indicate whether to retransmit for each CBG. For example, when the kth bit of CBGTI is '1', retransmission of the kth CBG is scheduled.

to DCI due to CBG Scheduling multiple TBs without

DCI can schedule transmissions to carry one or multiple TBs. However, it can be assumed that CBG-based transmission may not be supported or configured.

에 매핑된다. 대안적으로, 연속 TB들은, 존재하는 경우, 동일한 HARQ-ACK 비트에 매핑될 수 있으며, 예를 들어, TB n은 HARQ-ACK 비트 For HARQ-ACK feedback, the UE can generate one HARQ-ACK for each TB. 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 by N, the maximum number of HARQ-ACK bits per TB is M, and N TBs are mapped to M HARQ-ACK bits. In case N TBs are evenly grouped and cannot be mapped to M HARQ-ACK bits, the last group(s) may consist of slightly fewer or more TBs. Evenly distributed TBs, if present, may be mapped to the same HARQ-ACK bit, e.g., TB n is the HARQ-ACK bit

is mapped to Alternatively, consecutive TBs, if present, may be mapped to the same HARQ-ACK bit, e.g., TB n is the HARQ-ACK bit

에 매핑된다.

is mapped to

The number of NDI/RV bits in DCI is equal to the maximum number of TBs scheduled by DCI. The HARQ process number indicated by the DCI may be applied to the first scheduled TB by the DCI, and consecutive HARQ process numbers after the indicated HARQ process number are used in other scheduled TBs by the DCI.

In one embodiment, symbol alignment is achieved for each TB. In this case, SLIV of DCI may indicate the time resource of TB. The maximum number of TBs of transmission can be configured by higher layer signaling. Alternatively, the maximum length of the allocated time resource for the PDSCH or PUSCH may be configured so that the maximum number of TBs of the transmission is derived by the maximum length and the number of symbols for the TB. Alternatively, the maximum number of TBs of the current transmission may be dynamically indicated in the DCI or indicated by a combination of RRC signaling and dynamic indication by the DCI. Transmission of PDSCH or PUSCH may end at the symbol boundary of TB.

In one embodiment, symbol alignment is achieved for each SAU. SLIV of DCI may indicate time resource of SAU. The maximum number of SAUs of transmission can be configured by higher layer signaling. Alternatively, the maximum length of the allocated time resource for PDSCH or PUSCH may be configured so that the number of SAUs is derived by the maximum length and the number of symbols of the SAU. Alternatively, the maximum number of SAUs of the current transmission may be dynamically indicated in DCI or indicated by a combination of RRC signaling and dynamic indication by DCI. Transmission of PDSCH or PUSCH may end at the symbol boundary of SAU.

에 매핑된다. 대안적으로, 고르게 분포된 SAU들은, 존재하는 경우, 동일한 TB에 매핑될 수 있으며, 예를 들어, SAU n은

에 매핑된다.One or more SAUs may be grouped into TBs. The number of SAUs for a TB may be predefined or configured by higher layers. Alternatively, the number of SAUs for a TB can be dynamically indicated in the DCI. The last TB before the end of transmission may have fewer SAUs. Alternatively, the SAU(s) included in a TB may be determined by the number of SAUs and the number of TBs. Denote the maximum number of SAUs as N, the maximum number of TBs, eg, the maximum number of HARQ-ACK bits per transmission is M, and N SAUs are mapped to M TBs. If N SAUs cannot be evenly grouped into M TBs, the last TB(s) may consist of slightly fewer or more SAUs. Consecutive SAUs, if present, may be mapped to the same TB, e.g., SAU n is

is mapped to Alternatively, evenly distributed SAUs, if present, may be mapped to the same TB, e.g., SAU n is

is mapped to

8 illustrates an example of scheduling two TBs by DCI. In this case, SLIV indicates the time resource of SAU, eg, each SAU is mapped to all time/frequency resources of two symbols. Thus, symbol alignment is achieved for SAU. Each CBG consists of 4 consecutive SAUs. For example, if the last 4 SAUs were not transmitted due to early termination, there is only 1 TB transmitted in the current transmission. However, the UE may still need to report two HARQ-ACK bits for two TBs to have a constant payload size of HARQ-ACK.

9 illustrates another example of scheduling two TBs by DCI. In this case, SLIV indicates the time resource of SAU, eg, each SAU is mapped to all time/frequency resources of two symbols. Thus, symbol alignment is achieved for SAU. TB k consists of four SAUs with indices k, k+2, k+4, and k+6. For example, if the last 4 SAUs were not transmitted due to early termination, the current transmission still has 2 TBs transmitted. Each TB has a reduced TB size. Both the reported bits of the 2 HARQ-ACK bits are useful indications for 2 TBs.

to DCI due to with CBG Scheduling multiple TBs

DCI can schedule a transmission that can carry one or multiple TBs. It is also assumed that CBG-based transmission is also configured for each TB.

For HARQ-ACK feedback, the UE can generate one HARQ-ACK bit for each CBG. To schedule retransmission of a TB, a CBG transmission indicator (CBGTI) may be used to indicate whether to retransmit for each CBG of the retransmitted TB. For example, when the kth bit of CBGTI is '1', retransmission of the kth CBG is scheduled.

The number of NDI/RV bits in DCI is equal to the maximum number of TBs scheduled by DCI. The HARQ process number indicated by the DCI may be applied to the first scheduled TB by the DCI, and consecutive HARQ process numbers after the indicated HARQ process number are used in other scheduled TBs by the DCI.

In one embodiment, symbol alignment is achieved for each TB. SLIV of DCI may indicate time resource of TB. The maximum number of TBs of transmission can be configured by higher layer signaling. Alternatively, the maximum length of the allocated time resource for the PDSCH or PUSCH may be configured so that the maximum number of TBs of the transmission is derived by the maximum length and the number of symbols for the TB. Alternatively, the maximum number of TBs of the current transmission may be dynamically indicated in the DCI or indicated by a combination of RRC signaling and dynamic indication by the DCI. Transmission of PDSCH or PUSCH may end at the symbol boundary of TB.

In one embodiment, symbol alignment is achieved for each CBG. Each CBG contains one or multiple CBs. SLIV of DCI may indicate a time resource of CBG. The maximum number of CBGs in a transmission can be configured by higher layer signaling. Alternatively, the maximum length of the allocated time resource for the PDSCH or PUSCH may be configured so that the maximum number of CBGs of the transmission is derived by the maximum length and the number of symbols for the CBG. Alternatively, the maximum number of CBGs of the current transmission may be dynamically indicated in the DCI or a combination of RRC signaling and dynamic indication by the DCI. Transmission of PDSCH or PUSCH may end at a symbol boundary of CBG.

에 매핑된다. 대안적으로, 연속 CBG들은, 존재하는 경우, 동일한 TB에 매핑될 수 있으며, 예를 들어, CBG n은

에 매핑된다.One or more CBGs may be grouped into TBs. The number of CBGs for a TB can be predefined or configured by higher layers. Alternatively, the number of CBGs for a TB can be dynamically indicated in DCI or a combination of RRC signaling and dynamic indication by DCI. The last TB before the end of transmission may have fewer CBGs. Alternatively, the CBG(s) included in a TB may be determined by the number of CBGs and the number of TBs. Denote the maximum number of CBGs as N, the maximum number of TBs is M, and the N CBGs are mapped to the M TBs. In case N CBGs cannot be evenly grouped into M TBs, the last TB(s) may consist of slightly fewer or more CBGs. Evenly distributed CBGs, if present, can be mapped to the same TB, e.g., CBG n is

is mapped to Alternatively, consecutive CBGs, if present, may be mapped to the same TB, e.g., CBG n is

is mapped to

10 illustrates an example of scheduling two TBs by DCI. In this case, SLIV indicates the time resource of the CBG, eg, each CBG is mapped to all time/frequency resources of two symbols. Thus, symbol alignment is achieved for CBG. Each TB consists of 4 consecutive CBGs. For example, if the last 4 CBGs were not transmitted due to early termination, there is only 1 TB transmitted in the current transmission. However, the UE may still need to report 8 HARQ-ACK bits for 2 TBs to have a constant payload size of HARQ-ACK.

11 illustrates an example of scheduling two TBs by DCI. In this case, SLIV indicates the time resource of the CBG, eg, each CBG is mapped to all time/frequency resources of two symbols. Thus, symbol alignment is achieved for CBG. Each TB consists of 4 consecutive CBGs. TB k consists of four SAUs with indices k, k+2, k+4, and k+6. For example, if the last 4 CBGs were not transmitted due to early termination, the current transmission still has 2 TBs transmitted. Each TB has a reduced number of CBGs. However, the UE may still need to report 8 HARQ-ACK bits for 2 TB to have a constant payload size of HARQ-ACK.

In one embodiment, symbol alignment is achieved for each SAU. SLIV of DCI may indicate time resource of SAU. The maximum number of SAUs of transmission can be configured by higher layer signaling. Alternatively, the maximum length of the allocated time resource for the PDSCH or PUSCH may be configured so that the maximum number of SAUs in the transmission is derived by the maximum length and the number of symbols for the SAU. Alternatively, the maximum number of SAUs of the current transmission may be dynamically indicated in DCI or indicated by a combination of RRC signaling and dynamic indication by DCI. Transmission of PDSCH or PUSCH may end at the symbol boundary of SAU.

에 매핑된다.One or more SAUs may be grouped into CBGs. The number of SAUs for CBG may be predefined or configured by higher layers. Alternatively, the number of SAUs for CBG can be dynamically indicated in the DCI. The last CBG before the end of transmission may have fewer SAUs. Alternatively, the SAU(s) included in the CBG may be determined by the number of SAUs and the number of CBGs. The maximum number of SAUs is denoted by N, the maximum number of CBGs, eg, the maximum number of HARQ-ACK bits per TB is M, and N SAUs are mapped to M CBGs. In case N SAUs cannot be evenly grouped into M CBGs, the last CBG(s) may consist of slightly fewer or more SAUs. Consecutive SAUs, if present, may be mapped to the same CBG, e.g., SAU n is

is mapped to

에 매핑된다.Alternatively, evenly distributed SAUs, if present, can be mapped to the same CBG, e.g., SAU n is

is mapped to

Control channel transmission for slotless operation

NR supports the Physical Downlink Control Channel (PDCCH) which conveys scheduling decisions for both DL and UL via DCI. The PDCCH is transmitted through a control resource set (CORESET). CORESETs are units of 6 PRBs (e.g., one PRB contains 12 resource elements) in the frequency domain, and 1, 2, or 3 consecutive orthogonal frequency-division multiplexing ( It may consist of orthogonal frequency-division multiplexing (OFDM) symbols. Corresponding parameters are configured for the UE using frequencyDomainResources and duration parameters. An example configuration for a control resource set is as follows:

In CORESET, one resource element group (REG) may consist of one resource block and one OFDM symbol in the time domain. A Control Channel Element (CCE) may consist of 6 REGs. The actual number of CCEs for a PDCCH is determined by the PDCCH aggregation level. The UE performs blind decoding of the PDCCH for a specific set of CCEs denoted as a search space (SS). 5G NR consists of two SSs: a common common SS (CSS) set commonly monitored by a group of UEs in a cell, and a UE-specific SS (USS) set monitored by individual UEs. Set types are supported.

A UE-specific search space is constructed by RRC. The positions of the PDCCH to be monitored are defined by the monitoringSlotPeriodicityAndOffset parameter, which conveys information about slot offset as well as periodicity of monitoring. An example search space configuration is as follows:

NR supports conventional slot-level based scheduling shown in 5G NR as a Type A mapping. A slot-level transmission can start only on a specific OFDM symbol, but has a flexible duration up to 14 OFDM symbols within a slot. Type A mapping typically has a relatively long transmission time interval, which helps to increase coverage as well as reduce overhead from reference signals and control channels. However, conventional slot-level based scheduling is not efficient for all deployment scenarios. For example, for 5G NR operation in unlicensed spectrum (NR-U), it is necessary to start transmitting as soon as possible after Listen-Before-Talk (LBT). In the case of mmWave, 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 beneficial to start transmission on any OFDM symbol without constraints. To optimize system performance for these deployment scenarios, in addition to slot-based scheduling, 5G NR also supports mini-slot based transmission, denoted as Type B mapping. Mini-slot based scheduling allows a physical shared channel transmission to start on any OFDM symbol within a slot and have a flexible duration of 2, 4 or 7 OFDM symbols. To facilitate early decoding in mini-slot based scheduling, the control channel and reference signals are placed at the beginning of the transmission.

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

Therefore, under the previous schemes, control channel transmission is possible only at a specific location configured by RRC. For PDSCH transmissions with more flexible duration, unused time gaps may occur between the last symbol of a PDSCH transmission and the next PDCCH transmission opportunity.

Various embodiments herein provide techniques for PDCCH transmission at more dynamic time locations for scheduled PDSCH. Embodiments may be adapted to future specifications supporting flexible PDSCH transmission.

According to some embodiments, additional flexible PDCCH monitoring occasions can be defined from an OFDM/discrete Fourier Transform (DFT)-s(spread)-OFDM symbol followed by the last symbol of a PDSCH transmission. Note that the transmission duration of the PDSCH may be configured by higher layers, dynamically indicated by the MAC-CE, or indicated by the DCI carried by the first PDCCH. Also, in case of early termination of PDSCH transmission, the UE may start PDCCH monitoring after the last symbol of PDSCH transmission after early termination.

The techniques described herein provide additional opportunities for PDCCH transmission with a flexible/dynamic position compared to PDCCH monitoring occasions configured by higher layers. As a result, PDSCHs can be scheduled in a contiguous manner (preventing unused symbols) as illustrated in FIG. 13 .

In another example, additional PDCCH monitoring occasions may start in X > 0 symbols after last symbol of PDSCH as shown in FIG. 14 . In another option, an additional flexible PDCCH monitoring occasion may be indicated by the first PDCCH scheduling the PDSCH transmission.

Due to the more flexible PDCCH position, additional collisions of physical channels may occur. For example:

• Conflict between the PDSCH scheduled by the additional PDCCH and the PDCCH monitoring occasion configured by the RRC; and/or

• Conflict between additional PDCCH and PDCCH monitoring occasion configured by RRC.

In the case of the first collision example, priorities for processing of physical channels should be defined, for example, if the PDSCH scheduled by the additional PDCCH may collide with the PDCCH monitoring occasion configured by the RRC. For example, the UE may assume that PDSCH transmissions are prioritized and potential PDCCHs are dropped in the corresponding OFDM symbols. In another example, the UE may assume that PDCCH monitoring is prioritized and PDSCH transmissions in corresponding symbols are dropped or rate-matched around PDCCH transmissions in corresponding PDCCH monitoring occasions. .

In another example, when a PDSCH transmission uses a different transmission control indicator (TCI) state (beam) than the PDCCH configured by RRC and the UE has the ability to receive more than one TCI state (beam). , the UE can detect the PDCCH configured by RRC and detect PDSCH reception at the same time.

In case of the second collision example, eg collision of additional PDCCH and PDCCH monitoring occasion configured by RRC, priorities for processing of physical channels should be defined. In one example, more priority is given to monitoring of the additional PDCCH compared to the PDCCH configured by RRC. In another example, more priority is given to monitoring of PDCCHs configured by RRC over additional PDCCHs. In another example, priority is given by the CORESET's associated ID.

In another example, if the additional PDCCH uses a different TCI state (beam) than the PDCCH configured by RRC and the UE has the ability to receive two or more TCI states (beams), the UE is configured by the additional PDCCH and RRC All PDCCHs can be detected simultaneously.

Systems and Implementations

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

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

Network 1500 will include UE 1502, which can include any mobile or non-mobile computing device designed to communicate with RAN 1504 over an over-the-air connection. can The UE 1502 is a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster ), head-up display device, onboard diagnostic device, dashboard mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system , sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc., but are not limited thereto.

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

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

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

In embodiments where RAN 1504 includes multiple ANs, they couple to each other via an X2 interface (if RAN 1504 is an LTE RAN) or an Xn interface (if RAN 1504 is a 5G RAN). can be ringed X2/Xn interfaces, which in some embodiments can be separated into control/user plane interfaces, allow ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc. can be allowed

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

The RAN 1504 can provide an air interface via licensed spectrum or unlicensed spectrum. To operate in unlicensed spectrum, nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing unlicensed spectrum, nodes may perform medium/carrier-sensing operations, for example based on a listen-before-talk (LBT) protocol.

In V2X scenarios, UE 1502 or AN 1508 may be or act as an RSU, which may refer to any transport infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable AN or stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", and an RSU implemented in or by a gNB An implemented RSU may be referred to as a "gNB-type RSU", and so forth. In one example, an RSU is a computing device coupled with roadside located radio frequency circuitry 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, as well as applications/software for sensing and controlling on-going vehicle and pedestrian traffic. The RSU can provide very low latency communications required for high-speed events such as collision 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 traffic signaling controller or network interface controller to provide wired connectivity (eg Ethernet) to a backhaul network.

In some embodiments, the RAN 1504 can be an LTE RAN 1510 with eNBs, eg, eNB 1512. LTE RAN 1510 may provide an LTE air interface with the following characteristics: SCS at 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 includes CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and cell search and initial acquisition for coherent demodulation/detection at the UE, channel quality measurements, and CRS for channel estimation. The LTE air interface may operate in sub-6 GHz bands.

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

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

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

In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of SCS. For example, UE 1502 may be configured with multiple BWPs, each BWP configuration having a different SCS. When UE 1502 is indicated to change the BWP, the SCS of the transmission is also changed. Another example use case for BWP is related to power saving. In particular, multiple BWPs can be configured for UE 1502 with different amounts of frequency resources (eg, PRBs) to support data transmission under different traffic loading scenarios. A BWP with fewer PRBs can be used for data transmission with less traffic load while allowing power savings at the UE 1502 and in some cases the gNB 1516 . A BWP with a larger number of PRBs can be used in scenarios with higher traffic load.

RAN 1504 is communicably connected to CN 1520, which includes network elements for providing various functions supporting data and telecommunications services to customers/subscribers (e.g., users of UE 1502). are coupled Components of CN 1520 may be implemented on one physical node or on separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of CN 1520 into physical computing/storage resources such as servers, switches, etc. . 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, CN 1520 may be LTE CN 1522, which may also be referred to as an EPC. LTE CN 1522 includes MME 1524, SGW 1526, SGSN 1528, HSS 1530, PGW 1532, and PCRF 1534. The functions of the elements of the LTE CN 1522 can be briefly introduced as follows.

MME 1524 may implement mobility management functions to track the current location of UE 1502 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, and the like.

SGW 1526 may terminate the S1 interface to the RAN and route data packets between the RAN and LTE CN 1522 . SGW 1526 may be a local mobility anchor point for inter-RAN node handovers, and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

SGSN 1528 may track the location of UE 1502 and perform security functions and access control. SGSN 1528 also provides inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection specified by MME 1524; MME selection for handovers, etc. may be performed. The S3 reference point between the MME 1524 and the SGSN 1528 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.

HSS 1530 may include a database for network users, including subscription-related information to support the handling of communication sessions of network entities. The HSS 1530 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, and the like. there is. An S6a reference point between HSS 1530 and MME 1524 may enable transmission of subscription and authentication data to authenticate/authorize user access to LTE CN 1520 .

PGW 1532 may terminate an SGi interface to a data network (DN) 1536 , which may include an application/content server 1538 . PGW 1532 can route data packets between LTE CN 1522 and data network 1536 . PGW 1532 may be coupled with SGW 1526 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 1532 may further include a node (eg, PCEF) for policy enforcement and billing data collection. Additionally, the SGi reference point between PGW 1532 and data network 15 36 may be an operator external public, private PDN, or intra-operator packet data network, for example for provisioning of IMS services. PGW 1532 may be coupled with PCRF 1534 via a Gx reference point.

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

In some embodiments, CN 1520 may be 5GC 1540 . 5GC 1540 includes AUSF 1542, AMF 1544, SMF 1546, UPF 1548, NSSF 1550, which are coupled to each other via interfaces (or “reference points”) as shown. NEF 1552 , NRF 1554 , PCF 1556 , UDM 1558 , and AF 1560 . The functions of the elements of 5GC 1540 can be briefly introduced as follows.

AUSF 1542 may store data for authentication of UE 1502 and handle authentication-related functions. AUSF 1542 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 1540 via reference points as shown, AUSF 1542 may represent a Nausf service-based interface.

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

SMF 1546 includes SM (eg, session establishment, tunnel management between UPF 1548 and AN 1508); UE IP address allocation and management (including discretionary authorization); selection and control of UP functions; Configure traffic steering in UPF 1548 to route traffic to proper destination; termination of interfaces to policy control functions; partial control of policy enforcement, charging, and QoS; Legitimate intercept (for interface to SM events and LI system); End of SM parts of NAS messages; downlink data notification; Initiation of AN specific SM information transmitted via AMF 1544 to AN 1508 via N2; and determining the SSC mode of the session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU concatenation service that provides or enables the exchange of PDUs between UE 1502 and data network 1536 .

UPF 1548 is an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 1536, and a branch to support multi-homed PDU sessions. It can act as a branching point. UPF 1548 also performs packet routing and forwarding, performs packet inspection, enforces the user plane portion of policy rules, intercepts packets (UP collections) legitimately, performs traffic usage reporting, and Perform QoS handling for the plane (e.g. packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g. SDF-to-QoS flow mapping), It is also possible to perform transport level packet marking on the link and downlink, downlink packet buffering and downlink data notification triggering. UPF 1548 may include an uplink classifier to assist in routing traffic flows to the data network.

NSSF 1550 may select a set of network slice instances serving UE 1502 . NSSF 1550 may also determine the mapping for allowed NSSAIs and subscribed S-NSSAIs, if necessary. NSSF 1550 may also determine a list of candidate AMFs based on the set of AMFs used to serve UE 1502, or a suitable configuration, and possibly querying NRF 1554. Selection of a set of network slice instances for UE 1502 may be triggered by AMF 1544, whereby UE 1502 interacts with and registers with NSSF 1550, which may lead to changes in AMF. there is. NSSF 1550 can interact with AMF 1544 via the N22 reference point, and can communicate with other NSSFs in the visited network via the N31 reference point (not shown). Additionally, NSSF 1550 may represent a Nnssf service-based interface.

NEF 1552 is a third party, internal exposure/re-exposure, AFs (e.g. AF 1560), edge computing or fog computing system. systems) and the like to securely expose services and capabilities provided by 3GPP network functions. In these embodiments, NEF 1552 may authenticate, authorize, or throttle AFs. NEF 1552 may also translate information exchanged with AF 1560 and information exchanged with internal network functions. For example, NEF 1552 can translate between AF-Service-Identifier and internal 5GC information. NEF 1552 may also receive information from other NFs based on their exposed capabilities. This information may be stored in the NEF 1552 as structured data or stored in the data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 1552 to other NFs and AFs, or used for other purposes such as analytics. Additionally, NEF 1552 may represent a Nnef service-based interface.

The NRF 1554 may support service discovery functions, receive NF discovery requests from NF instances, and provide information on discovered NF instances to NF instances. NRF 1554 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like can refer to the creation of an instance, and “instance” means, for example, of program code. It can refer to specific occurrences of objects that may occur during execution. Additionally, NRF 1554 may represent a Nnrf service-based interface.

PCF 1556 may provide policy rules to control plane functions to enforce them, and may support a unified policy framework to manage network behavior. PCF 1556 may also implement a front end to access subscription information related to policy decisions in the UDR of UDM 1558. In addition to communicating functions via reference points as shown, PCF 1556 represents an Npcf service-based interface.

UDM 1558 may handle subscription-related information to support handling of communication sessions of network entities, and may store subscription data of UE 1502 . For example, subscription data may be communicated over N8 reference points between UDM 1558 and AMF 1544. UDM 1558 may include two parts: an application front end and a UDR. UDR includes subscription data and policy data for UDM 1558 and PCF 1556, and/or structured data for exposure and application data for NEF 1552 (PFDs for application detection, multiple UEs ( 1502) may be stored. The Nudr service-based interface accesses the specific set of data stored by UDM 1558, PCF 1556, and NEF 1552 by UDR 221, as well as reading, updating notifications of related data changes in the UDR. (e.g. add, edit), delete, and subscribe. The UDM may include a UDM-FE responsible for credential processing, location management, subscription management, and the like. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR, and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs via reference points as shown, UDM 1558 may represent a Nudm service-based interface.

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

In some embodiments, 5GC 1540 may enable edge computing by selecting operator/third party services to be geographically close to the point at which UE 1502 attaches to the network. This can reduce the load and latency of the network. To provide edge-computing implementations, the 5GC 1540 selects a UPF 1548 close to the UE 1502 and provides traffic steering from the UPF 1548 to the data network 1536 over the N6 interface. can run This may be based on UE subscription data, UE location, and information provided by AF 1560 . In this way, AF 1560 can influence UPF (re)selection and traffic routing. Based on the operator deployment, when AF 1560 is considered a trusted entity, the network operator may authorize AF 1560 to interact directly with the associated NFs. Additionally, AF 1560 may represent a Naf service-based 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, for example, application/content server 1538 .

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

UE 1602 can be communicatively coupled with AN 1604 via connection 1606 . Connection 1606 is illustrated as an air interface enabling communication coupling, and may conform to cellular communication protocols such as mmWave or LTE protocol or 5G NR protocol operating at frequencies below 6 GHz.

The UE 1602 can include a host platform 1608 coupled with a modem platform 1610 . The host platform 1608 can include application processing circuitry 1612 that can be coupled with the protocol processing circuitry 1614 of the modem platform 1610 . Application processing circuitry 1612 can run various applications on UE 1602 that source/sink application data. Application processing circuitry 1612 may further implement one or more layer operations to send/receive application data to/from a data network. These layer operations may include transport (eg UDP) and Internet (eg IP) operations.

Protocol processing circuitry 1614 can implement one or more of the layer operations to facilitate sending or receiving data over connection 1606 . Layer operations implemented by protocol processing circuitry 1614 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

Modem platform 1610 may further include digital baseband circuitry 1616 that may implement one or more layer operations “below” the layer operations performed by protocol processing circuitry 1614 in the network protocol stack. can These operations may include, for example, HARQ-ACK functions, scrambling/desscrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, space-time, space-frequency or space Among multi-antenna port precoding/decoding, which may include one or more of coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions. It may include PHY operations including one or more.

The modem platform 1610 includes an RF front end (RFFE) that may include or connect to transmit circuitry 1618, receive circuitry 1620, RF circuitry 1622, and one or more antenna panels 1626. (1624) may be further included. Briefly, transmit circuitry 1618 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, and the like, and receive circuitry 1620 may include an analog-to-digital converter, mixer, IF components, and the like. etc., the RF circuitry 1622 can include low-noise amplifiers, power amplifiers, power tracking components, etc., and the RFFE 1624 can include filters (e.g., surface/bulk acoustic wave ( surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (eg, phased-array antenna components), and the like. selection of transmit circuitry 1618, receive circuitry 1620, RF circuitry 1622, RFFE 1624, and components of antenna panels 1626 (referred to generally as “transmit/receive components”); and The arrangement may be specific to particular implementation details, such as whether the communication is TDM or FDM, for example at mmWave or sub-6 gHz frequencies. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains and may be disposed in the same or different chips/modules, etc.

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

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

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

Similar to UE 1602 , AN 1604 can include a host platform 1628 coupled with a modem platform 1630 . Host platform 1628 can include application processing circuitry 1632 coupled with 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 antenna panels 1646 . Components of AN 1604 may be similar to and substantially interchangeable with like-named components of UE 1602 . In addition to performing data transmission/reception as described above, the components of AN 1608 may also perform RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling, for example. It can perform various logical functions, including

17 illustrates some exemplary instructions capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein. A block diagram illustrating components, according to embodiments. Specifically, FIG. 17 shows 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. and each of these may be communicatively coupled via bus 1740 or other interface circuitry. For embodiments in which node virtualization (eg, NFV) is utilized, hypervisor 1702 may be implemented to provide an execution environment for one or more network slices/sub-slices to utilize hardware resources 1700. there is.

Processors 1710 may include, for example, processor 1712 and processor 1714 . The processors 1710 may include, 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, It may be an ASIC, FPGA, radio-frequency integrated circuit (RFIC), other processor (including those discussed herein), or any suitable combination thereof.

Memory/storage devices 1720 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1720 may include dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory. memory), solid-state storage, and the like, any type of volatile, non-volatile, or semi-volatile memory, but is not limited thereto.

Communications resources 1730 may be interconnection or network interface controllers, components, or other components for communicating with one or more peripheral devices 1704 or with one or more databases 1706 or other network elements over network 1708. Suitable devices may be included. For example, communication resources 1730 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions 1750 may be software, programs, applications, applets, apps, or programs for causing at least any of processors 1710 to perform any one or more of the methodologies discussed herein. May contain other executable code. Instructions 1750 may be fully or partially within at least one of processors 1710 (e.g., within a cache memory of a processor), memory/storage devices 1720, or any suitable combination thereof. can reside as Also, any portion of instructions 1750 may be sent to hardware resources 1700 from any combination of peripheral devices 1704 or databases 1706 . Accordingly, the 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) of FIGS. 15-17 or some other diagram herein, or part thereof The implementations or implementations may be configured to perform one or more processes, techniques, or methods, or portions thereof, described herein. One such process 1800 is shown in FIG. 18 . For example, process 1800 can include, at step 1802, receiving downlink control information (DCI) to indicate resource allocation for transmission of a transport block, where the resource allocation is It includes one or more code block groups (CBGs) that are mapped to one or more symbol alignment units (SAUs) of one or more symbols.

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

19 illustrates another process 1900 according to various embodiments. The process may include, at step 1902, receiving downlink control information (DCI) to indicate individual resource assignments for two or more transport blocks, where the resource assignments are one or more symbol alignments. unit (SAU), which includes all time-frequency resources of one or more symbols.

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

20 illustrates another process 2000 according to various embodiments. Process 2000 may include, at step 2002, encoding downlink control information (DCI) for transmission to a UE to indicate resource allocation for transmission of a transport block, where the resource An assignment includes one or more code block groups (CBGs) that are mapped to one or more symbol alignment units (SAUs) of one or more symbols.

At step 2004 , process 2000 may further include causing transmission of a transport block to or reception of a transport block from a UE based on the DCI. In some embodiments, process 2000 may be performed by a gNB or part thereof.

21 illustrates another process 2100 according to various embodiments. Process 2100 may include, at step 2102, encoding downlink control information (DCI) to indicate individual resource assignments for two or more transport blocks for transmission to a UE; Here, resource allocations include one or more symbol alignment units (SAUs), and SAUs include all time-frequency resources of one or more symbols.

At step 2104 , process 2100 may further include causing transmission of transport blocks to or reception of transport blocks from the UE based on the DCI. In some embodiments, process 2100 may be performed by a gNB or part thereof.

22 illustrates another process 2200 according to various embodiments. In some embodiments, process 2200 may be performed by a UE or part thereof. For example, process 2200 may include, at step 2202, determining a last symbol of a PDSCH (eg, a PDSCH received by the UE).

At step 2204, process 2200 may further include determining a PDCCH monitoring location for the PDCCH based on the last symbol of the PDSCH. For example, the PDCCH monitoring occasion is a number of symbols after the last symbol (e.g., in the next symbol after the last symbol or another number of symbols after the last symbol). symbols later).

At step 2206, process 2200 may further include monitoring for a PDCCH at the determined PDCCH monitoring occasion. In some embodiments, the process may further include receiving a PDCCH at a PDCCH monitoring occasion. The PDCCH may schedule another communication for the UE, such as downlink communication (eg, another PDSCH) and/or uplink communication (eg, PUSCH and/or PUCCH).

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

At step 2302 , process 2300 can include encoding the PDSCH for transmission (eg, to a UE).

At step 2304, the process may further include determining a PDCCH monitoring occasion for the PDCCH based on the last symbol of the PDSCH. For example, a PDCCH monitoring occasion may be determined as starting a certain number of symbols later from the last symbol (e.g., in the next symbol after the last symbol or another number of symbols later from the last symbol). can

At step 2306 , the process may further include encoding the PDCCH for transmission at the determined PDCCH monitoring occasion (eg, to the UE or another UE). The PDCCH may schedule other communications for the UE, such as downlink communications (eg, another PDSCH) and/or uplink communications (eg, PUSCH and/or PUCCH).

For one or more embodiments, at least one of the components presented 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 described above in connection with one or more of the previous figures may be configured to operate according to one or more of the examples presented below. For another example, circuitry associated with a UE, base station, network element, etc., as described above with respect to one or more of the previous figures, may be configured to operate according to one or more of the examples set forth below in the Examples section.

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 some other example herein, where the CBG is mapped to all time/frequency resources of particular contiguous symbols.

Example 3 may include the method of example 1 or some other example herein, wherein CBG is mapped to a symbol alignment unit (SAU); or CBG is mapped to one or multiple SAUs; Or, the SAU is composed of one or multiple CBGs.

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

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

Example 6 may include the method of example 1 or some other example herein, wherein early termination of a PDSCH or PUSCH transmission is supported with a granularity of one TB, one CBG, or one SAU. do.

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

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

Example 9 may include the method of example 1 or some other example herein, wherein the DCI schedules a PDSCH or PUSCH carrying only one TB with one or multiple SAUs.

Example 10 may include the method of Example 9 or some other example herein, wherein the SLIV of the DCI indicates the time resource of the SAU.

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

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

Example 13 may include the method of example 12 or some other example herein, wherein the SLIV of the DCI indicates the time resource of the SAU.

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

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

Example 16 may include the method of Example 15 or some other example herein, wherein the SLIV of the DCI indicates the time resource of the CBG.

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

Example 18 may include the method of example 15 or some other example herein, wherein the SLIV of the DCI indicates the time resource of the SAU.

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

Example 20 is a method,

Receiving downlink control information (DCI) for indicating resource allocation for transmission of a transport block, wherein the resource allocation comprises one or more code block groups (CBGs) mapped to one or more Symbol Aligned Units (SAUs) of one or more symbols. including -; and

Transmitting or receiving a transport block based on DCI

It may include a method including.

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

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

Example 23 may include the method of examples 20 or 21 or some other example herein, wherein the DCI includes a SLIV to indicate a time resource of a first SAU of the one or more SAUs.

Example 24 may include the method of examples 20-23 or some other examples herein, further comprising determining an early termination of the transmission, where the early termination includes one transport block, one CBG, Or it is determined by the granularity of one SAU.

Example 25 may include the method of examples 20-24 or some other examples herein, wherein the DCI schedules transmission of a single transport block.

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

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

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

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

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

Example 31 may include the method of examples 20-30 or some other example herein, wherein individual CBGs include multiple SAUs.

Example 32 may include the method of Example 31 or some other example herein, wherein the number of SAUs are contiguous in the time domain.

Example 33 may include the method of Example 31 or some other example herein, wherein multiple SAUs are interlaced 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 some other examples herein, where the transport block is a PUSCH.

Example 36 may include the method of examples 20-34 or some other examples herein, where the transport block is a PDSCH.

Example 37 may include the method of examples 20-36 or some other examples herein, where the method is performed by a UE or a portion thereof.

Example 38 is a method comprising:

Receiving downlink control information (DCI) for indicating individual resource allocations for two or more transport blocks, the resource allocations comprising one or more Symbol Alignment Units (SAUs), the SAUs all the time of one or more symbols -includes frequency resources-; and

Transmitting or receiving transport blocks based on DCI

It may include a method including.

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

Example 40 may include the method of examples 38 or 39 or some other example herein, wherein the plurality of SAUs are contiguous in the time domain.

Example 41 may include the method of examples 38 or 39 or some other example herein, wherein multiple SAUs are interlaced in the time domain with SAUs of one or more other resource allocations.

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

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

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

Example 45 may include the method of examples 38-44 or some other examples herein, where the method is performed by a UE or a portion thereof.

Example 46 is a method comprising:

Encoding, for transmission to a UE, downlink control information (DCI) for indicating resource allocation for transmission of a transport block, the resource allocation being mapped to one or more Symbol Alignment Units (SAUs) of one or more symbols. Contains Code Block Group (CBG) -; and

Causing transmission of a transport block to or reception of a transport block from the UE based on the DCI;

It may include a method including.

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

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

Example 49 may include the method of examples 46 or 47 or some other examples herein, wherein the DCI includes a SLIV to indicate a time resource of a first SAU of the one or more SAUs.

Example 50 may include the method of examples 46-49 or some other examples herein, further comprising determining an early termination of the transmission, where the early termination includes one transport block, one CBG, Or it is determined by the granularity of one SAU.

Example 51 may include the method of examples 46-50 or some other examples herein, wherein the DCI schedules transmission of a single transport block.

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

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

Example 54 may include the method of examples 46-50 or some other example herein, wherein the DCI schedules transmission of multiple transport blocks.

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

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

Example 57 may include the method of examples 46-56 or some other example herein, wherein individual CBGs include multiple SAUs.

Example 58 may include the method of example 57 or some other example herein, wherein the plurality of SAUs are contiguous in the time domain.

Example 59 may include the method of example 57 or some other example herein, wherein multiple SAUs are interlaced 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 some other examples herein, where the transport block is a PUSCH.

Example 62 may include the method of examples 46-60 or some other examples herein, where the transport block is a PDSCH.

Example 63 may include the method of examples 46-62 or some other examples herein, where the method is performed by the gNB or a portion thereof.

Example 64 is a method comprising:

Encoding, for transmission to a UE, downlink control information (DCI) to indicate individual resource allocations for two or more transport blocks, the resource allocations comprising one or more Symbol Alignment Units (SAUs), the SAUs contains all time-frequency resources of one or more symbols; and

Causing transmission of transport blocks to or reception of transport blocks from the UE based on the DCI.

It may include a method including.

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

Example 66 may include the method of examples 64 or 65 or some other example herein, wherein the plurality of SAUs are contiguous in the time domain.

Example 67 may include the method of examples 64 or 65 or some other example herein, wherein multiple SAUs are interlaced in the time domain with SAUs of one or more other resource allocations.

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

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

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

Example 71 may include the method of examples 64-70 or some other examples herein, where the method is performed by the gNB or a portion thereof.

Example 72 may include the method of examples 20-71 or some other examples herein, wherein the transport block(s) are transmitted at a carrier frequency greater than 52.6 GHz.

Example B1 is a method of downlink control channel transmission,

Semi-static configuration of physical downlink control channel (PDCCH) monitoring occasions using higher layers;

Scheduling a physical downlink shared channel (PDSCH) using downlink control information (DCI) transmitted in a PDCCH configured by an upper layer; and

Additional PDCCH monitoring occasion followed by PDSCH configuration

It may include a method including.

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

Example B3 may include the method of Example B1 or some other example herein, wherein the additional PDCCH is scheduled X symbols after the last symbol of the PDSCH, where X is 1, 2, 3 depending on the configuration. It is one or more symbols.

Example B4 may include the method of example B1 or some other example herein, wherein the PDSCH scheduled by the additional PDCCH collides with a PDCCH monitoring occasion configured by higher layers, and the UE determines that the PDSCH transmission corresponds It can be assumed that the prioritized and potential PDCCH is dropped in the OFDM symbols that

Example B5 may include the method of example B1 or some other example herein, wherein the PDSCH scheduled by the additional PDCCH collides with a PDCCH monitoring occasion configured by higher layers, and the UE determines that the PDCCH transmission corresponds It can be assumed that the OFDM symbols are prioritized and the PDSCH is dropped.

Example B6 may include the method of example B1 or some other example herein, wherein the additional PDCCH collides with a PDCCH monitoring occasion configured by higher layers, and the UE determines the OFDM symbols to which the additional PDCCH transmission corresponds. It can be assumed that the PDCCH prioritized in and configured by higher layers is dropped.

Example B7 may include the method of example B1 or some other example herein, wherein the additional PDCCH collides with a PDCCH monitoring occasion configured by higher layers, and the UE determines the OFDM symbols to which the additional PDCCH transmission corresponds. It can be assumed that the PDCCH dropped in and configured by higher layers is prioritized.

Example B8 may include the method of Example B1 or some other example herein, wherein the additional PDCCH collides with a PDCCH monitoring occasion configured by higher layers, and the UE processes the additional PDCCH transmission and the higher layers The PDCCH configured by is prioritized.

Example B9 may include the method of example B1 or some other example herein, wherein the PDSCH scheduled by the additional PDCCH collides with a PDCCH monitoring occasion configured by higher layers, and the UE reports to higher layers. Processes PDCCH transmissions configured by and PDSCHs scheduled by additional PDCCHs.

Example B10 may include the method of Example B1 or some other example herein, where 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 some other examples herein, where higher layers are RRC or MAC signaling.

Example B12 is a method comprising:

Determining the last symbol of the PDSCH;

Determining a PDCCH monitoring occasion for the PDCCH based on the last symbol of the PDSCH; and

Monitoring for a PDCCH in the determined PDCCH monitoring location

It may include a method including.

Example B13 may include the method of Example B12 or some other example herein, where the PDCCH monitoring occasion includes the earliest symbol after the last symbol of the PDSCH.

Example B14 may include the method of examples B12 or example B13 or some other example herein, wherein the PDCCH monitoring occasion is a symbol that is X symbols later than the last symbol of the PDSCH. symbols after the last symbol of the PDSCH).

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

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

Example B17 may include the method of Examples B12 through B16 or some other examples herein, further comprising receiving the PDCCH.

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

Example B19 may include the methods of Examples B12 through B18 or some other examples herein, wherein the PDCCH monitoring occasion is a first PDCCH monitoring occasion and the second PDSCH collides with the second PDCCH monitoring occasion. and determining a relative priority of a second PDSCH in comparison with a second PDCCH monitoring occasion; and selecting one of decoding the second PDSCH or monitoring for the second PDCCH in the PDCCH monitoring occasion based on the determined relative priority.

Example B20 may include the method of Example B19 or some other example herein, wherein the second PDCCH monitoring occasion is configured via RRC signaling.

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

Example B22 may include the method of Examples B12-B21 or some other examples herein, where the PDCCH includes a DCI for uplink or downlink communication.

Example B23 may include the method of Example B22 or some other example herein, wherein the communication is in unlicensed spectrum, in 5G FR2, and/or for Ultra High Reliability Low Latency Communications (URLLC).

Example B24 may include the method of Examples B12-B23 or some other example herein, where the method is performed by a UE or a portion thereof.

Example B25 is a method comprising:

encoding the PDSCH for transmission;

Determining a PDCCH monitoring occasion for the PDCCH based on the last symbol of the PDSCH; and

Encoding the PDCCH for transmission at the determined PDCCH monitoring occasion.

It may include a method including.

Example B26 may include the method of example B25 or some other example herein, where the PDCCH monitoring occasion includes the earliest symbol after the last symbol of the PDSCH.

Example B27 may include the method of examples B25 or example B26 or some other example herein, where the PDCCH monitoring occasion starts on a symbol that is X symbols after the last symbol of the PDSCH.

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

Example B29 may include the method of Examples B27 or B28 or some other examples herein, further comprising encoding the indication of the value of X for transmission.

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

Example B31 may include the methods of Examples B25-B30 or some other examples herein, where PDCCH includes a DCI for uplink communication.

Example B32 may include the method of Example B31 or some other examples herein, further including receiving the uplink communication.

Example B33 may include the method of Examples B25-B32 or some other examples herein, where the PDCCH includes a DCI for scheduling downlink communications.

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

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

Example B36 may include the method of Examples B25 through B35 or some other example herein, wherein the PDCCH communicates in unlicensed spectrum, in 5G FR2, and/or for Ultra High Reliability Low Latency Communications (URLLC). schedule

Example B37 may include the methods of Examples B25-B36 or some other examples herein, where the PDSCH and PDCCH are transmitted to the same UE.

Example B38 may include the method of examples B25 through B37 or some other example herein, where the method is performed by the gNB or a portion thereof.

Example C1 is one or more non-transitory computer readable media (NTCRM) stored with instructions that, when executed by one or more processors, cause a user equipment (UE) to read the last symbol of a physical downlink shared channel (PDSCH). determine a PDCCH monitoring location for a physical downlink control channel (PDCCH) based on the last symbol of the PDSCH, and monitor for the PDCCH at the determined PDCCH monitoring location. .

Example C2 may include one or more NTCRMs of Example C1 or some other example herein, wherein the PDCCH monitoring occasion is a symbol that is any number of one or more symbols later from the last symbol of the PDSCH. is a number of one or more symbols after the last symbol).

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

Example C4 may include one or more NTCRMs of Examples C1-C3 or some other examples herein, wherein PDSCH is a first PDSCH, and the instructions, when executed, further cause the UE to: receive a PDCCH, and the PDCCH schedules a second PDSCH or Physical Uplink Shared Channel (PUSCH).

Example C5 may include one or more NTCRMs of Example C4 or some other example herein, wherein the PDCCH monitoring occasion is a first PDCCH monitoring occasion and the second PDSCH collides with the second PDCCH monitoring occasion and , the instructions, when executed, further cause the UE to determine a relative priority of the second PDSCH compared to a second PDCCH monitoring occasion, and to decode the second PDSCH based on the determined relative priority; or In the PDCCH monitoring case, one of monitoring for other PDCCHs is selected.

Example C6 may include one or more NTCRMs of Examples C1-C5 or some other examples herein, wherein the PDCCH monitoring occasion is a first PDCCH monitoring occasion, and the first PDCCH monitoring occasion is a second PDCCH monitoring occasion. It overlaps with the monitoring occasion, and monitoring of the PDCCH in the first PDCCH monitoring occasion is performed based on the relative priority of the first PDCCH monitoring occasion compared to the second PDCCH monitoring occasion.

Example C7 may include one or more NTCRMs of Examples C1-C6 or some other examples herein, wherein the instructions, when executed, further cause a UE to receive a PDCCH in a PDCCH monitoring occasion, and to: schedules uplink or downlink communications in unlicensed spectrum, in 5G frequency range 2 (FR2), or for ultra-reliable low-latency communications (URLLC).

Example C8 is one or more non-transitory computer readable media (NTCRM) stored with instructions that, when executed by one or more processors, cause a Next Generation NodeB (gNB) to transmit to a user equipment (UE) a Physical Downlink Shared Channel (PDSCH) ), determine a PDCCH monitoring location for a physical downlink control channel (PDCCH) based on the last symbol of the PDSCH, and encode the PDCCH for transmission to the UE in the determined PDCCH monitoring location. may include one or more NTCRMs that

Example C9 may include one or more NTCRMs of example C8 or some other examples herein, where the PDCCH monitoring occasion starts on a symbol that is any number of one or more symbols later from the last symbol of the PDSCH.

Example C10 may include one or more NTCRMs of Example C9 or some other examples herein, wherein the instructions, when executed, further cause the gNB to transmit a message to the UE that includes an indication of the number. to encode

Example C11 may include one or more NTCRMs of Examples C8-C10 or some other examples herein, where the PDCCH schedules downlink transmissions.

Example C12 may include one or more NTCRMs of Example C11 or some other examples herein, where the PDSCH is a first PDSCH and the downlink transmission includes a second PDSCH.

Example C13 may include one or more NTCRMs of Example C11 or some other examples herein, wherein the PDCCH schedules uplink communications, and the instructions, when executed, further cause the gNB to perform uplink communications. to receive

Example C14 may include one or more NTCRMs of Examples C8-C13 or some other examples herein, wherein the instructions may include the PDCCH to transmit uplink or downlink communications in unlicensed spectrum in 5G frequency range 2 (FR2). , or for Ultra High Reliability Low Latency Communications (URLLC).

Example C15 is one or more non-transitory computer readable media (NTCRM) stored with instructions that, when executed by one or more processors, cause a user equipment (UE) to indicate resource allocation for one or more transport blocks. may include one or more NTCRMs to receive downlink control information (DCI), wherein the resource allocation includes one or more Symbol Alignment Units (SAUs), to transmit or receive one or more transport blocks based on the DCI .

Example C16 may include one or more NTCRMs of example C15 or some other examples herein, where 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 one or more NTCRMs of Examples C15 or C16 or some other examples herein, where SAUs include all time-frequency resources of one or more symbols.

Example C18 may include the one or more NTCRMs of Examples C15-C17 or some other examples herein, wherein the DCI is a start and length indicator value for indicating a time resource of a first SAU of the one or more SAUs ( SLIV).

Example C19 may include one or more NTCRMs of Examples C16-C18 or some other examples herein, wherein the DCI is a start and length indicator value for indicating a time resource of a first CBG of the one or more CBGs ( SLIV).

Example C20 may include one or more NTCRMs of Examples C15-C19 or some other examples herein, wherein the DCI schedules transmission of multiple transport blocks and transmits data for individual transport blocks of the multiple transport blocks. Resource allocations correspond to contiguous time-frequency resources.

Example C21 may include the one or more NTCRMs of any of Examples C16-C20, wherein the DCI schedules transmission of multiple transport blocks, and the resource assignments to individual CBGs of the multiple transport blocks are contiguous. Corresponds to specific time-frequency resources.

Example C22 may include one or more NTCRMs of Examples C15-C21 or some other examples herein, wherein the DCI schedules transmission of multiple transport blocks, and the SAUs of the multiple transport blocks are mutually related in the time domain. are interlaced

Example C23 may include the one or more NTCRMs of any one of Examples C16-C22, wherein the DCI schedules transmission of multiple transport blocks, and the CBGs of the multiple transport blocks are interlaced with each other in the time domain. .

Example Z01 is a method for performing one or more elements of or related to any of Examples 1-72, B1-B38, C1-C23, or any other method or process described herein. It may include a device comprising means.

Example Z02 is one or more non-transitory computer readable media containing instructions that cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, of examples 1-72, examples B1-B38, may include one or more non-transitory computer readable media that cause performance of one or more elements of a method described in or related to any of Examples C1-C23, or any other method or process described herein.

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

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

Example Z05 is an apparatus comprising one or more computer readable media comprising one or more processors and instructions that, when executed by the one or more processors, cause the one or more processors to: Example B38, any of Examples C1-C23, or portions thereof may include an apparatus that causes the method, techniques, or process to be performed.

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

Example Z07 is data described in or related to any of Examples 1-72, Examples B1-B38, Examples C1-C23, or portions or portions thereof, or otherwise described in this disclosure. It may contain a gram, packet, frame, segment, protocol data unit (PDU), or message.

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

Example Z09 is data described in or related to any of Examples 1-72, Examples B1-B38, Examples C1-C23, or parts or portions thereof, or otherwise described in this disclosure. It may contain a signal encoded as a gram, packet, frame, segment, protocol data unit (PDU), or message.

Example Z10 is an electromagnetic signal carrying computer readable instructions, wherein execution of the computer readable instructions by one or more processors causes the one or more processors to: an electromagnetic signal that causes a method, technique, or process described in or related to any of, or portions thereof, to be performed.

Example Z11 is a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to cause any of Examples 1-72, Examples B1-B38, Examples C1-C23, or a portion thereof. may include a computer program that causes the performance of a method, technique, or process described in or related thereto.

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

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

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

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

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

Abbreviations

Unless used differently herein, terms, definitions, and abbreviations may coincide 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 Acknowledgment

AF Application Function

AM Acknowledged Mode

AMBR Aggregate Maximum Bit Rate

AMF Access and Mobility Management Function

AN Access Network

ANR Automatic Neighbor Relation

AP Application Protocol, Antenna Port, Access Point

API Application Programming Interface

APNs Access Point Name

ARP Allocation and Retention Priority

ARQ Automatic Repeat Request

AS Access Stratum

ASN.1 Abstract Syntax Notation One

AUSF Authentication Server Function

AWGN Additive White Gaussian Noise

BAP Backhaul Adaptation Protocol

BCH Broadcast Channel

BER Bit Error Ratio

BFD Beam Failure Detection

BLER Block Error Rate

BPSK Binary Phase Shift Keying

BRAS Broadband Remote Access Server

BSS Business Support System

BS Base Station

BSR Buffer Status Report

BW Bandwidth

BWP Bandwidth Part

C-RNTI Cell Radio Network Temporary Identity

CA Carrier Aggregation, Certification Authority

CAPEX CAPital EXpenditure

CBRA Contention Based Random Access

CC Component Carrier, Country Code, Cryptographic Checksum

CCA Clear Channel Assessment

CCE Control Channel Element

CCCH Common Control Channel

CE Coverage Enhancement

CDM Content Delivery Network

CDMA Code-Division Multiple Access

CFRA Contention Free Random Access

CG Cell Group

CI Cell Identity

CID Cell-ID (eg, positioning method)

CIM Common Information Model

CIR Carrier to Interference Ratio

C.K. Cipher Key

CM Connection Management, Conditional Mandatory

CMAS Commercial Mobile Alert Service

CMD Command

CMS Cloud Management System

CO Conditional Optional

CoMP Coordinated Multi-Point

CORESET Control Resource Set

COTS Commercial Off-The-Shelf

CP Control Plane, Cyclic Prefix, Connection Point

CPD Connection Point Descriptor

CPE Customer Premise Equipment

CPICH Common Pilot Channel

CQI Channel Quality Indicator

CPU CSI processing unit, Central Processing Unit

C/R Command/Response field bit

CRAN Cloud Radio Access Network, Cloud RAN

CRB Common Resource Block

CRC Cyclic Redundancy Check

CRI Channel-State Information Resource Indicator, CSI-RS Resource Indicator

C-RNTI Cell RNTI

CS Circuit Switched

CSAR Cloud Service Archive

CSI Channel-State Information

CSI-IM CSI Interference Measurement

CSI-RS CSI Reference Signal

CSI-RSRP CSI reference signal received power

CSI-RSRQ CSI reference signal received quality

CSI-SINR CSI signal-to-noise and interference ratio

CSMA Carrier Sense Multiple Access

CSMA/CA CSMA with collision avoidance

CSS Common Search Space, Cell-specific Search Space

CTS Clear-to-Send

CW Codeword

CWS Contention Window Size

D2D Device-to-Device

DC Dual Connectivity, Direct Current

DCI Downlink Control Information

DF Deployment Flavor

DL Downlink

DMTF Distributed Management Task Force

DPDK Data Plane Development Kit

DM-RS, DMRS Demodulation Reference Signal

DN Data network

DRB Data Radio Bearer

DRS Discovery Reference Signal

DRX Discontinuous Reception

DSL Domain Specific Language. Digital Subscriber Line

DSLAM DSL Access Multiplexer

DwPTS Downlink Pilot Time Slot

E-LAN Ethernet Local Area Network

E2E End-to-End

ECCA Extended clear channel assessment (extended CCA)

ECCE Enhanced Control Channel Element, Enhanced CCE

ED Energy Detection

EDGE Enhanced Datarates for GSM Evolution

EGMF Exposure Governance Management Function

EGPRS Enhanced GPRS

EIR Equipment Identity Register

eLAA Enhanced Licensed Assisted Access, enhanced LAA

EM Element Manager

eMBB Enhanced Mobile Broadband

EMS Element Management System

eNB Evolved NodeB, E-UTRAN Node B

EN-DC E-UTRA-NR Dual Connectivity

EPC Evolved Packet Core

EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel

EPRE Energy per resource element

EPS Evolved Packet System

EREG Enhanced REG, enhanced resource element groups

ETSI European Telecommunications Standards Institute

ETWS Earthquake and Tsunami Warning System

eUICC Embedded UICC (embedded UICC), embedded universal integrated circuit card (embedded universal integrated circuit card)

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN (Evolved UTRAN)

EV2X Enhanced V2X

F1AP F1 Application Protocol

F1-C F1 Control plane interface

F1-U F1 User plane interface

FACCH Fast Associated Control CHannel

FACCH/F Fast Associated Control Channel/Full rate

FACCH/H Fast Associated Control Channel/Half rate

FACH Forward Access Channel

FAUSCH Fast Uplink Signaling Channel

FB Functional Block

FBI Feedback Information

FCC Federal Communications Commission

FCCH Frequency Correction CHannel

FDD Frequency Division Duplex

FDM Frequency Division Multiplex

FDMA Frequency Division Multiple Access

FE Front End

FEC Forward Error Correction

FFS For Further Study

FFT Fast Fourier Transformation

feLAA further enhanced licensed access Assisted Access), further enhanced LAA

FN Frame Number

FPGA Field-Programmable Gate Array

FR Frequency Range

G-RNTI GERAN Radio Network Temporary Identity

GERAN GSM EDGE RAN, GSM EDGE Radio Access Network

GGSN Gateway GPRS Support Node

GLONASS GLOBal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System)

gNB Next Generation NodeB

gNB-CU gNB-centralized unit, Next Generation NodeB centralized unit

gNB-DU gNB-distributed unit, Next Generation NodeB distributed unit

GNSS Global Navigation Satellite System

GPRS General Packet Radio Service

cial Mobile)Global System for Mobile Communications (GSM)

cial Mobile)

GTP GPRS Tunneling Protocol

GTP-U GPRS Tunneling Protocol for User Plane

GTS Go To Sleep Signal (WUS Related)

GUMMEI Globally Unique MME Identifier

GUTI Globally Unique Temporary UE Identity

HARQ Hybrid ARQ, Hybrid Automatic Repeat Request

HANDO Handover

HFN HyperFrame Number

HHO Hard Handover

HLR Home Location Register

HN Home Network

HO Handover

HPLMN Home Public Land Mobile Network

HSDPA High Speed Downlink Packet Access

HSN Hopping Sequence Number

HSPA High Speed Packet Access

HSS Home Subscriber Server

HSUPA High Speed Uplink Packet Access

HTTP Hyper Text Transfer Protocol

HTTPS Hyper Text Transfer Protocol Secure (https is SSL i.e. http/1.1 over port 443)

I-Block Information Block

ICCID Integrated Circuit Card Identification

IAB Integrated Access and Backhaul

ICIC Inter-Cell Interference Coordination

ID Identity, identifier

IDFT Inverse Discrete Fourier Transform

IE Information element

IBE In-Band Emission

IEEE Institute of Electrical and Electronics Engineers

IEI Information Element Identifier

IEIDL Information Element Identifier Data Length

IETF Internet Engineering Task Force

IF Infrastructure

IM Interference Measurement, Intermodulation, IP Multimedia

IMC IMS Credentials

IMEI International Mobile Equipment Identity

IMGI International mobile group identity

IMPI IP Multimedia Private Identity

IMPU IP Multimedia Public identity

IMS IP Multimedia Subsystem

IMSI International Mobile Subscriber Identity

IoT Internet of Things

IP Internet Protocol

Ipsec IP Security, Internet Protocol Security

IP-CAN IP-Connectivity Access Network

IP-M IP Multicast

IPv4 Internet Protocol Version 4

IPv6 Internet Protocol Version 6

IR Infrared

IS In Sync

IRP Integration Reference Point

ISDN Integrated Services Digital Network

ISIM IM Services Identity Module

ISO International Organization for Standardization

ISP Internet Service Provider

IWF Interworking-Function

I-WLAN Interworking WLAN

Constraint length of the convolutional code, USIM Individual key

kB Kilobyte (1000 bytes)

kbps kilo-bits per second

Kc Ciphering key

Ki Individual subscriber authentication key

KPIs Key Performance Indicator

KQI Key Quality Indicator

KSI Key Set Identifier

ksps kilo-symbols per second

KVM Kernel Virtual Machine

L1 Layer 1 (physical layer)

L1-RSRP Layer 1 reference signal received power

L2 Layer 2 (data link layer)

L3 Layer 3 (network layer)

LAA Licensed Assisted Access

LAN Local Area Network

LBT Listen Before Talk

LCM Lifecycle Management

LCR Low Chip Rate

LCS Location Services

LCID Logical Channel ID

LI Layer Indicator

LLC Logical Link Control, Low Layer Compatibility

LPLMN Local PLMN (Local PLMN)

LPP LTE Positioning Protocol

LSB Least Significant Bit

LTE Long Term Evolution

LWA LTE-WLAN aggregation

LWIP LTE/WLAN Radio Level Integration with IPsec Tunnel

LTE Long Term Evolution

M2M Machine-to-Machine

MAC Medium Access Control (protocol layering context)

MAC Message authentication code (security/encryption context)

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

MAC-I MAC used for data integrity of signaling messages (TSG T WG3 context)

MANO Management and Orchestration

MBMS Multimedia Broadcast and Multicast Service

MBSFN Multimedia Broadcast multicast service Single Frequency Network

MCC Mobile Country Code

MCG Master Cell Group

MCOT Maximum Channel Occupancy Time

MCS Modulation and coding scheme

MDAF Management Data Analytics Function

MDAS Management Data Analytics Service

MDT Minimization of Drive Tests

ME Mobile Equipment

MeNB Master eNB

MER Message Error Ratio

MGL Measurement Gap Length

MGRP Measurement Gap Repetition Period

MIB Master Information Block, Management Information Base

MIMO Multiple Input Multiple Output

MLC Mobile Location Center

MM Mobility Management

MME Mobility Management Entity

MN Master Node

MnS Management Service

MO Measurement Object, Mobile Originated

MPBCH MTC Physical Broadcast CHannel

MPDCCH MTC Physical Downlink Control CHannel

MPDSCH MTC Physical Downlink Shared CHannel

MPRACH MTC Physical Random Access CHannel

MPUSCH MTC Physical Uplink Shared Channel

MPLS MultiProtocol Label Switching

MS Mobile Station

MSB Most Significant Bit

MSc Mobile Switching Center

MSI Minimum System Information, MCH Scheduling Information

MSID Mobile Station Identifier

MSIN Mobile Station Identification Number

MSISDN Mobile Subscriber ISDN Number

MT Mobile Terminated (Mobile Termination)

MTC Machine-Type Communications

mMTC Massive MTC, Massive Machine-Type Communications

MU-MIMO Multi User MIMO

MWUS MTC wake-up signal, MTC WUS

NACK Negative Acknowledgement

NAI Network Access Identifier

NAS Non-Access Stratum, Non-Access Stratum layer

NCT Network Connectivity Topology

NC-JT Non-Coherent Joint Transmission

NEC Network Capability Exposure

NE-DC NR-E-UTRA Dual Connectivity

NEF Network Exposure Function

NF Network Function

NFP Network Forwarding Path

NFPD Network Forwarding Path Descriptor

NFV Network Functions Virtualization

NFVI NFV Infrastructure

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 Narrowband Physical Uplink Shared CHannel

NPSS Narrowband Primary Synchronization Signal

NSSS Narrowband Secondary Synchronization Signal

NR New Radio, Neighbor Relation

NRF NF Repository Function

NRS Narrowband Reference Signal

NS Network Service

NSA Non-Standalone operation mode

NSD Network Service Descriptor

NSR Network Service Record

NSSAI Network Slice Selection Assistance Information

S-NNSAI Single-NSSAI

NSSF Network Slice Selection Function

NW Network

NWUS Narrowband wake-up signal, Narrowband WUS

NZP Non-Zero Power

O&M Operation and Maintenance

ODU2 Optical channel Data Unit - type 2

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OOB Out-of-band

OOS Out of Sync

OPEX Operating Expense

OSI Other System Information

OSS Operations Support System

OTA Over-the-air

PAPR Peak-to-Average Power Ratio

PAR Peak to Average Ratio

PBCH Physical Broadcast Channel

PC Power Control, Personal Computer

PCC Primary Component Carrier, Primary CC

PCell Primary Cell

PCI Physical Cell ID, Physical Cell Identity

PCEF Policy and Charging Enforcement Function

PCF Policy Control Function

PCRF Policy Control and Charging Rules Function

PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol layer

PDCCH Physical Downlink Control Channel

PDCP Packet Data Convergence Protocol

PDN Packet Data Network, Public Data Network

PDSCH Physical Downlink Shared Channel

PDUs Protocol Data Unit

PEI Permanent Equipment Identifiers

PFD Packet Flow Description

P-GW PDN Gateway

PHICH Physical hybrid-ARQ indicator channel

PHY Physical layer

PLMN Public Land Mobile Network

PIN Personal Identification Number

PM Performance Measurement

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

PS Packet Services

PSBCH Physical Sidelink Broadcast Channel

PSDCH Physical Sidelink Downlink Channel

PSCCH Physical Sidelink Control Channel

PSFCH Physical Sidelink Feedback Channel

PSSCH Physical Sidelink Shared Channel

PSCell Primary SCell

PSS Primary Synchronization Signal

PSTN Public Switched Telephone Network

PT-RS Phase-tracking reference signal

PTT Push-to-Talk

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

QAM Quadrature Amplitude Modulation

QCI QoS class of identifier

QCL Quasi co-location

QFI QoS Flow ID, QoS Flow Identifier

QoS Quality of Service

QPSK Quadrature (Quaternary) Phase Shift Keying

QZSS Quasi-Zenith Satellite System

RA-RNTI Random Access RNTI (Random Access RNTI)

RAB Radio Access Bearer, Random Access Burst

RACH Random Access Channel

RADIUS Radius (Remote Authentication Dial In User Service)

RAN Radio Access Network

RAND RANDom number (used for authentication)

RAR Random Access Response

RAT Radio Access Technology

RAU Routing Area Update

RB Resource block, Radio Bearer

RBG Resource block group

REG Resource Element Group

Rel Release

REQ REQuest

RF Radio Frequency

RI Rank Indicator

RIV Resource indicator value

RL Radio Link

RLC Radio Link Control, Radio Link Control layer

RLC AM RLC Acknowledged Mode

RLC UM RLC Unacknowledged Mode

RLF Radio Link Failure

RLM Radio Link Monitoring

RLM-RS Reference Signal for RLM

RM Registration Management

RMC Reference Measurement Channel

RMSI Remaining MSI (Remaining MSI), Remaining Minimum System Information

RN Relay Node

RNC Radio Network Controller

RNL Radio Network Layer

RNTI Radio Network Temporary Identifier

ROHC RObust Header Compression

RRC Radio Resource Control, Radio Resource Control layer

RRM Radio Resource Management

RS Reference Signal

RSRP Reference Signal Received Power

RSRQ Reference Signal Received Quality

RSSI Received Signal Strength Indicator

RSU Road Side Unit

RSTD Reference Signal Time Difference

RTP Real Time Protocol

RTS Ready-To-Send

RTT Round Trip Time

Rx Reception, Receiving, Receiver

S1AP S1 Application Protocol

S1-MME S1 for the control plane

S1-U S1 for the user plane

S-GW Serving Gateway

S-RNTI SRNC Radio Network Temporary Identity

S-TMSI SAE Temporary Mobile Station Identifier

SA Standalone operation mode

SAE System Architecture Evolution

SAP Service Access Point

SAPD Service Access Point Descriptor

SAPI Service Access Point Identifier

SCC Secondary Component Carrier, Secondary CC

SCell Secondary Cell

SC-FDMA Single Carrier Frequency Division Multiple Access

SCG Secondary Cell Group

SCM Security Context Management

SCS Subcarrier Spacing

SCTP Stream Control Transmission Protocol

SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol layer

SDL Supplementary Downlink

SDNF Structured Data Storage Network Function

SDP Session Description Protocol

SDSF Structured Data Storage Function

SDU Service Data Unit

SEAF Security Anchor Function

SeNB Secondary eNB

SEPP Security Edge Protection Proxy

SFI Slot format indication

SFTD Space-frequency time diversity, SFN and frame timing difference

SFN System Frame Number

SgNB Secondary gNB

SGSN Serving GPRS Support Node

S-GW Serving Gateway

SI System Information

SI-RNTI System Information RNTI (System Information RNTI)

SIB System Information Block

SIM Subscriber Identity Module

SIP Session Initiated Protocol

SiP System in Package

SL Sidelink

SLA Service Level Agreement

SM Session Management

SMF Session Management Function

SMS Short Message Service

SMSF SMS Function

SMTC SSB-based Measurement Timing Configuration

SN Secondary Node, Sequence Number

SoC System on Chip

SON Self-Organizing Network

SpCell Special Cell

SP-CSI-RNTI Semi-Persistent CSI RNTI (Semi-Persistent CSI RNTI)

SPS Semi-Persistent Scheduling

SQN Sequence number

SR Scheduling Request

SRB Signaling Radio Bearer

SRS Sounding Reference Signal

SS Synchronization Signal

SSB SS Block

SSBRI SSB Resource Indicator

SSC Session and Service Continuity

SS-RSRP Synchronization Signal based Reference Signal Received Power

SS-RSRQ Synchronization Signal based Reference Signal Received Quality

SS-SINR Synchronization Signal based Signal to Noise and Interference Ratio

SSS Secondary Synchronization Signal

SSSG Search Space Set Group

SSSIF Search Space Set Indicator

SST Slice/Service Types

SU-MIMO Single User MIMO

SUL Supplementary Uplink

TA Timing Advance, Tracking Area

TAC Tracking Area Code

TAG Timing Advance Group

TAU Tracking Area Update

TB Transport Block

TBS Transport Block Size

TBD To Be Defined

TCI Transmission Configuration Indicator

TCP Transmission Communication Protocol

TDD Time Division Duplex

TDM Time Division Multiplexing

TDMA Time Division Multiple Access

TE Terminal Equipment

TEID Tunnel End Point Identifier

TFT Traffic Flow Template

TMSI Temporary Mobile Subscriber Identity

TNL Transport Network Layer

TPC Transmit Power Control

TPMI Transmitted Precoding Matrix Indicator

TR Technical Report

TRP, TRxP Transmission Reception Point

TRS Tracking Reference Signal

TRx Transceiver

TS Technical Specifications, Technical Standard

TTI Transmission Time Interval

Tx Transmission, Transmitting, Transmitter

U-RNTI UTRAN Radio Network Temporary Identity

UART Universal Asynchronous Receiver and Transmitter

UCI Uplink Control Information

UE User Equipment

UDM Unified Data Management

UDP User Datagram Protocol

UDR Unified Data Repository

UDSF Unstructured Data Storage Network Function

UICC Universal Integrated Circuit Card

UL Uplink

UM Unacknowledged Mode

UML Unified Modeling Language

UMTS Universal Mobile Telecommunications System

UP User Plane

UPF User Plane Function

URI Uniform Resource Identifier

URL Uniform Resource Locator

URLLC Ultra-Reliable and Low Latency

USB Universal Serial Bus

USIM Universal Subscriber Identity Module

USS UE-specific search space

UTRA UMTS Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

UwPTS Uplink Pilot Time Slot

V2I Vehicle-to-Infrastruction

V2P Vehicle-to-Pedestrian

V2V Vehicle-to-Vehicle

V2X Vehicle-to-everything

VIM Virtualized Infrastructure Manager

VL Virtual Link;

VLAN Virtual LAN, Virtual Local Area Network

VM Virtual Machine

VNF Virtualized Network Function

VNFFG VNF Forwarding Graph

VNFFGD VNF Forwarding Graph Descriptor

VNFM VNF Manager

VoIP Voice-over-IP, Voice-over-Internet Protocol

VPLMN Visited Public Land Mobile Network

VPN Virtual Private Network

VRB Virtual Resource Block

WiMAX WiMAX (Worldwide Interoperability for Microwave Access)

WLAN Wireless Local Area Network

WMAN Wireless Metropolitan Area Network

WPAN Wireless Personal Area Network

X2-C X2-Control plane

X2-U X2-User plane

XML Extensible Markup Language

XRES EXpected user RESponse

XOR Exclusive OR

ZC Zadoff-Chu

ZP Zero Power

Terms

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

As used herein, the term “circuitry” refers to electronic circuits, logic circuits, processors (shared, dedicated, or groups) and/or memory (shared, dedicated, or groups) configured to provide the described functions; ASIC (Application Specific Integrated Circuit), FPD (field-programmable device) (e.g., FPGA (field-programmable gate array), PLD (programmable logic device), CPLD (complex PLD), HCPLD (high-capacity PLD), Refers to, is part of, or includes hardware components such as structured ASICs, or programmable SoCs), digital signal processors (DSPs), and the like. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of program code and one or more hardware elements (or a combination of circuits used in an electrical or electronic system) used to perform the function of the program code. In such embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuitry.

As used herein, the term "processor circuitry" refers to circuitry that sequentially and automatically performs a sequence of arithmetic or logic operations, or that can record, store, and/or transmit digital data, or is part of, or includes Processing circuitry may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term “processor circuitry” refers to one or more applications processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or program code , software modules, and/or any other device capable of executing computer-executable instructions or otherwise operating, such as functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, and 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 with “processor circuitry” and may be referred to as such.

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

As used herein, the term “user equipment” or “UE” refers to a device with radio communication capabilities and can describe a remote user of network resources of a communication network. The term “user equipment” or “UE” refers to a client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment ( radio equipment), reconfigurable radio equipment, reconfigurable mobile device, etc., and may be referred to as synonymous. Also, the term “user equipment” or “UE” can include any computing device or any type of wireless/wired device that includes a wireless communication interface.

As used herein, the term “network element” refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term "network element" is considered synonymous with networked computers, networking hardware, network equipment, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN devices, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, etc. may be and/or may be referred to as such.

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

As used herein, the terms "appliance", "computer appliance", and the like refer to a computer device or computer having program code (eg, software or firmware) specifically designed to provide specific computing resources. refers to the system A “virtual appliance” is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

As used herein, the term “resource” 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, e.g., computer devices, mechanical devices, memory 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, etc. “Hardware resource” may refer to computing, storage, and/or network resources provided by physical hardware element(s). “Virtualized resource” may refer to computing, storage, and/or network resources provided by a virtualization infrastructure to applications, devices, systems, and the like. The term “network resource” or “communication resource” can refer to resources accessible by computer devices/systems over a communications network. The term “system resources” may refer to any kind of shared entities for providing services, and may include computing and/or network resources. System resources can be considered as a set of coherent functions, network data objects or services accessible through a server, where these system resources reside on a single host or multiple hosts and are explicitly identifiable

As used herein, the term “channel” refers to any transmission medium, tangible or intangible, used to communicate data or data streams. The term "channel" includes "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 indicating a path or medium through which data is communicated and/or may be equivalent thereto. Additionally, the term “link” as used herein refers to a connection between two devices over a RAT for the purpose of transmitting and receiving information.

The terms “instantiate”, “instantiation” and the like used herein refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

The terms "coupled" and "communicatively coupled", along with their derivatives, 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 are in indirect contact with each other but still cooperate or interact with each other, and / Or it may mean that one or more other elements are coupled or connected between elements that are said to be coupled to each other. The term “directly coupled” may mean that two or more elements are in direct contact with each other. The term “communicatively coupled” can mean that two or more elements can be brought into contact with each other by communication, including through a wired or other interconnect connection, through a wireless communication channel or link, and the like.

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

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

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

The term “Primary Cell” refers to an MCG cell operating on a primary frequency, where a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

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

The term "Secondary Cell" refers to a cell that provides additional radio resources other than a special cell for a CA-configured UE.

The term "Secondary Cell Group" refers to a PSCell for a DC configured UE and a subset of serving cells that includes zero or more secondary cells.

The term "serving cell" refers to a primary cell for a UE of RRC_CONNECTED that is not configured with CA/DC, and there is only one serving cell including the primary cell.

The term “serving cell” or “serving cells” refers to a set of cells including the special cell(s) for a UE of RRC_CONNECTED configured with CA/ and all secondary cells.

The term "Special Cell" refers to the PCell of MCG or the PSCell of SCG for DC operation, otherwise the term "Special Cell" refers to the Pcell.

Claims (23)

One or more non-transitory computer-readable media (NTCRM) having stored thereon instructions, which, when executed by one or more processors, cause a user equipment (UE) to:
determine the last symbol of a physical downlink shared channel (PDSCH);
Determine a PDCCH monitoring occasion for a physical downlink control channel (PDCCH) based on the last symbol of the PDSCH;
One or more NTCRMs to monitor for a PDCCH in the determined PDCCH monitoring occasion. The method of claim 1, wherein the PDCCH monitoring occasion starts from a symbol that is a number of one or more symbols after the last symbol by any number of one or more symbols after the last symbol of the PDSCH. , one or more NTCRMs. 3. The NTCRM of claim 2, wherein the instructions, when executed, further cause the UE to receive an indication of the number. 4. The method according to any one of claims 1 to 3, wherein the PDSCH is a first PDSCH, and the instructions, when executed, further cause the UE to receive the PDCCH at the PDCCH monitoring occasion; wherein the PDCCH schedules a second PDSCH or physical uplink shared channel (PUSCH); The method of claim 4, wherein the PDCCH monitoring occasion is a first PDCCH monitoring occasion, the second PDSCH collides with a second PDCCH monitoring occasion, and the instructions, when executed, further cause the UE to:
Determine a relative priority of the second PDSCH by comparing with the second PDCCH monitoring occasion;
one or more NTCRMs to select one of decoding the second PDSCH based on the determined relative priority or monitoring for another PDCCH in the PDCCH monitoring occasion. The method according to any one of claims 1 to 5, wherein the PDCCH monitoring occasion is a first PDCCH monitoring occasion, the first PDCCH monitoring occasion overlaps with a second PDCCH monitoring occasion, and the first PDCCH monitoring occasion overlaps with a second PDCCH monitoring occasion. wherein monitoring for the PDCCH at the monitoring occasion is performed based on a relative priority of the first PDCCH monitoring occasion compared to the second PDCCH monitoring occasion. 7. The method according to any one of claims 1 to 6, wherein the instructions, when executed, further cause the UE to receive the PDCCH in the PDCCH monitoring occasion, wherein the PDCCH is uplink or downlink One that schedules communications in unlicensed spectrum, in 5G Frequency Range 2 (FR2), or for ultra-reliable and low-latency communications (URLLC) More than NTCRM. One or more non-transitory computer readable media (NTCRM) having stored thereon instructions, which, when executed by one or more processors, cause a next generation NodeB (gNB) to:
Determine the last symbol of a physical downlink shared channel (PDSCH) transmitted to user equipment (UE);
Determine a PDCCH monitoring location for a physical downlink control channel (PDCCH) based on the last symbol of the PDSCH;
One or more NTCRMs to encode a PDCCH for transmission to the UE in the determined PDCCH monitoring occasion. 9. The one or more NTCRMs of claim 8, wherein the PDCCH monitoring occasion starts with a symbol that is one or more symbols later than the last symbol of the PDSCH. 10. The one or more NTCRMs of claim 9, wherein the instructions, when executed, further cause the gNB to encode a message containing an indication of the number for transmission to the UE. 11. The NTCRM of any one of claims 8 to 10, wherein the PDCCH schedules downlink transmissions. 12. The NTCRM of claim 11, wherein the PDSCH is a primary PDSCH and the downlink transmission comprises a secondary PDSCH. 12. The one or more NTCRMs of claim 11, wherein the PDCCH schedules uplink communications and the instructions, when executed, further cause the gNB to receive the uplink communications. 14. The method of any one of claims 8 to 13, wherein the instructions include: the PDCCH is used to transmit uplink or downlink communication in unlicensed spectrum, in 5G frequency range 2 (FR2), or in ultra-reliable low-latency communications (URLLC). ), one or more NTCRMs. One or more non-transitory computer readable media (NTCRM) having stored thereon instructions, which, when executed by one or more processors, cause a user equipment (UE) to:
Receive downlink control information (DCI) for indicating resource allocation for one or more transport blocks, wherein the resource allocation includes one or more symbol alignment units (SAUs); ,
One or more NTCRMs for transmitting or receiving the one or more transport blocks based on the DCI. 16. The one or more NTCRMs of claim 15, wherein the resource allocation comprises one or more code block groups (CBGs) mapped to one or more SAUs of one or more symbols. 17. The NTCRM of claims 15 or 16, wherein the SAUs include all time-frequency resources of one or more symbols. 18. The method of any one of claims 15 to 17, wherein the DCI comprises a start and length indicator value (SLIV) for indicating a time resource of a first SAU of the one or more SAUs. , one or more NTCRMs. 19. The one or more NTCRMs of any one of claims 16 to 18, wherein the DCI comprises a start and length indicator value (SLIV) to indicate a time resource of a first CBG of the one or more CBGs. 20. The method according to any one of claims 15 to 19, wherein the DCI schedules transmission of multiple transport blocks, and resource assignments for individual transport blocks of the multiple transport blocks are performed on contiguous time-frequency resources. Correspondingly, one or more NTCRMs. 21. A method according to any one of claims 16 to 20, wherein the DCI schedules transmission of multiple transport blocks, and resource assignments to individual CBGs of the multiple transport blocks correspond to contiguous time-frequency resources. , one or more NTCRMs. 22. The NTCRM of any one of claims 15 to 21, wherein the DCI schedules transmission of multiple transport blocks, and SAUs of the multiple transport blocks are interlaced with each other in the time domain. 23. The NTCRM of any one of claims 16 to 22, wherein the DCI schedules transmission of multiple transport blocks, the CBGs of the multiple transport blocks being interlaced with each other in the time domain.

Images