Extended frequency hopping for data transmission

Abstract

Various embodiments herein relate to enhanced frequency hopping for data transmission, such as transmission at carrier frequencies above 52.6 gigahertz (GHz). Other embodiments may be disclosed or claimed.

Description

[Technical Field]

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 160,583, filed on 12 March 2021, and to U.S. Provisional Patent Application No. 63 / 161,334, filed on 15 March 2021.

[0002] Various embodiments may generally relate to the field of wireless communication. For example, some embodiments may relate to extended frequency hopping for data transmission, such as transmission at carrier frequencies higher than 52.6 gigahertz (GHz). [Background technology]

[0003] Mobile communications have evolved remarkably from early voice systems to today's highly sophisticated integrated communication platforms. The next-generation wireless communication system, 5G or New Radio (NR), will provide access to information and data sharing by diverse users and applications anywhere, anytime. NR is expected to be an integrated network / system aiming to meet vastly different and sometimes competing performance dimensions and services. Such diverse, multi-dimensional demands are driven by different services and applications. Generally, NR will evolve based on 3GPP® LTE Advanced, along with additional future-proof new radio access technologies (RATs), enriching people's lives with better, simpler, and more seamless wireless connectivity solutions. NR will enable everything to be wirelessly connected, delivering high-speed, rich content and services. [Brief explanation of the drawing]

[0004] Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. For the sake of this description, similar structural elements are indicated by the same reference numerals. Embodiments are shown in the figures of the accompanying drawings as examples, not as limitations. [Figure 1]An example of a long PDSCH transmission duration according to various embodiments is shown. [Figure 2] An example of early termination of PDSCH transmission according to various embodiments is shown. [Figure 3] An example of components of PDSCH transmission and required signaling according to various embodiments is shown. [Figure 4] An example of indication of the number of scheduled TBs and distinction between new transmission or retransmission according to various embodiments is shown. [Figure 5] An example of indication of the number of scheduled TBs and distinction between new transmission or retransmission according to various embodiments is shown. [Figure 6] An example of indication of the number of scheduled TBs and distinction between new transmission or retransmission according to various embodiments is shown. [Figure 7] An example of intra-slot frequency hopping for PUSCH in NR according to various embodiments is shown. [Figure 8] An example of frequency hopping in units of TB groups according to various embodiments is shown. [Figure 9] An example of frequency hopping on mixed TBs according to various embodiments is shown. [Figure 10] An example of frequency hopping in units of TBs according to various embodiments is shown. [Figure 11] An example of frequency hopping for retransmission and first transmission according to various embodiments is shown. [Figure 12] A wireless network according to various embodiments is schematically shown. [Figure 13] Components of a wireless network according to various embodiments are schematically shown. [Figure 14]This block diagram shows a component according to one of the embodiments, capable of reading instructions from a machine-readable medium or a computer-readable medium (e.g., a non-temporary machine-readable storage medium) and performing one or more of the methods described herein. [Figure 15] Figures 15, 16, and 17 illustrate examples of procedures for carrying out the various embodiments described herein. [Figure 16] Figures 15, 16, and 17 illustrate examples of procedures for carrying out the various embodiments described herein. [Figure 17] Figures 15, 16, and 17 illustrate examples of procedures for carrying out the various embodiments described herein. [Modes for carrying out the invention]

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

[0006] NR systems operate based on the concept of slots. Physical downlink shared channels (PDSCH) or physical uplink shared channels (PUSCH) are restricted within slots. Such restrictions on PDSCH or PUSCH may still apply at high frequencies. On the other hand, systems operating at carrier frequencies higher than 52.6 GHz, particularly in terahertz communications, are assumed to require larger subcarrier spacings to cope with significant phase noise. When larger subcarrier spacings, such as 1.92 MHz or 3.84 MHz, are used, slot durations can become very short. For example, with a 1.92 MHz subcarrier spacing, the duration of one slot is approximately 7.8 μs. This extremely short slot duration may not be sufficient for higher-layer processing, including the medium access layer (MAC) and radio link control (RLC). To address this problem, gNBs can schedule DL or UL data transmissions across slot boundaries with longer transmit durations. In other words, the concept of slots may not be necessary when scheduling data transmissions.

[0007] Figure 1 shows an example of a long PDSCH transmission duration. In DL transmissions, more DL traffic may arrive at the gNB when the gNB has already sent DL downlink control information (DCI) or when the previous PDSCH transmission is still in progress. The gNB must send a new DL DCI to schedule the PDSCH, which results in a delay in data transmission. One solution might be to allow the gNB to schedule more DL resources than are needed to transmit the current DL data in the buffer. As a result, when new DL traffic arrives, the gNB can continue the PDSCH transmission for that new DL traffic on the scheduled DL resources. On the other hand, if there is no new incoming DL traffic, the scheduled DL resources need to be released sooner, for example, by early termination of the PDSCH transmission. In practice, there may be other reasons besides the absence of new DL traffic that the gNB needs to terminate the DL transmission sooner. Figure 2 shows an example where the allocated DL resources can carry 10 CBs. However, the DL transmission may only be terminated after the transmission of 6 CBs.

[0008] In hybrid automatic retransmission request (HARQ)-based data transmissions with long durations, the number of transport blocks (TBs) is also increased accordingly for efficient HARQ retransmissions. Furthermore, the gNB needs to have the flexibility to control the number of TBs in data transmissions scheduled by the DCI. This embodiment provides a solution for efficiently indicating scheduling information in the DCI.

[0009] Various embodiments described herein include techniques for scheduling multiple transport block transmissions for carrier frequencies higher than 52.6 GHz.

[0010] In the following description, a downlink or uplink data transmission scheduled by DCI consists of M transport blocks (TBs) or TB groups, where M is between 1 and Mmax It can be within the range of M. max is the maximum number of TBs or TB groups scheduled by DCI. Each TB consists of one or more consecutive code blocks (CBs). Each CB is assigned a CRC. A TB may correspond to a MAC PDU. Each TB may be assigned a separate HARQ process number (HPN). A TB may be mapped to all time / frequency resources of L consecutive data symbols. For example, L is equal to 1. In this way, symbol alignment is achieved for a TB.

[0011] To schedule DL or UL transmissions using DCI, the DCI must indicate the start symbol (S) of the allocated time resource, the number of symbols for the TB or TB group (L), the total number of symbols for the allocated time resource (X), or the number of scheduled TBs or TB groups (M). Figure 3 shows an example of an allocated time resource carrying M TBs. The value of the start symbol S may be determined by an offset relative to the last symbol of the PDCCH carrying the DCI. Alternatively, the start symbol S may be determined by the start symbol index in the slot. In the latter case, the number of slots of scheduling delay from the PDCCH to the allocated time resource, such as K0 in NR, must be indicated in the DCI. Furthermore, the DCI includes a field to distinguish between new transmissions and retransmissions for each of the M scheduled TBs or TB groups. In the following description, this field will be referred to as the new transmission or retransmission indication (NRI). If early termination is enabled, fewer than M TBs or TB groups may be transmitted. The UE may simply ignore the NRI after early termination.

[0012] The aforementioned information S, L, X or M, and NRI can be represented by separate fields within the DCI. The drawback is that this can increase the overhead in the DCI. Therefore, joint coding may be necessary for some or all of the information to reduce the overhead. On the other hand, the flexibility and simplicity of configuration of gNB scheduling should also be considered.

[0013] TDRA field indicating the number of scheduled TBs or TB groups In one embodiment, the Time Domain Resource Allocation (TDRA) field in DCI may indicate the number of scheduled TBs or TB groups, for example, M, where the number of TBs in a TB group may be configured by a higher layer via RRC signaling. A TDRA table may be configured by a higher layer. Each entry in the TDRA table may have the same or different information M. The total number of symbols in the allocated time resources can be calculated, for example, X = L·M + R, where R is the number of DMRS symbols in the allocated time resources and may be derived from L, M, or X. The size of the NRI field may be determined by the maximum value of M among all entries in the TDRA table.

[0014] In one option, each entry in the TDRA field indicates information S, L, and M about the assigned data transmission. Meanwhile, information NRI is indicated by another field in DCI.

[0015] In another option, each entry in the TDRA field indicates S and M for the assigned data transmission. Meanwhile, L and NRI can be indicated by separate fields within the DCI, respectively.

[0016] In one embodiment, the Time Domain Resource Allocation (TDRA) field in DCI may represent the total number of symbols for an allocated time resource, for example, X. The TDRA table may be composed of higher layers. Each entry in the TDRA table may have the same or different information X. The total number of scheduled TBs can be calculated, for example, by M = (XR) / L, where R is the number of DMRS symbols in the allocated time resource and can be derived from X. The size of the NRI field can be determined by the maximum value of M among all entries in the TDRA table.

[0017] In another option, each entry in the TDRA field indicates information S, L, and X about the assigned data transmission. Meanwhile, information NRI is indicated by another field in DCI.

[0018] In another option, each entry in the TDRA field indicates S, X for the assigned data transmission. Meanwhile, L and NRI can be indicated by separate fields within the DCI, respectively.

[0019] The NRI field indicates the number of scheduled TBs or TB groups. The NRI field in DCI can indicate the number of scheduled TBs or TB groups, for example, M, where the number of TBs within a TB group can be configured by the upper layer via RRC signaling, and each of the M TBs or TB groups can be distinguished as a new transmission or a retransmission. The size of the NRI field can be configured by the upper layer signaling. The total number of symbols within the allocated time resource can be calculated, for example, X = L·M + R, where R is the number of DMRS symbols within the allocated time resource and can be derived from L, M, or X. One HARQ-ACK bit may be reported for a TB or TB group.

[0020] Each entry in the TDRA field indicates information S and L about the assigned data transmission. On the other hand, the information NRI is indicated by another field in the DCI. Since the number of scheduled TBs or TB groups is not indicated by each entry in the TDRA table, this simplifies the structure of the TDRA table. It is expected that the size of the TDRA table will be reduced without affecting the scheduling flexibility. Instead, the information S, L, and NRI may be indicated by separate fields in the DCI, respectively.

[0021] In one embodiment, the NRI field in the DCI can be interpreted as a bitmap of length M max and one special bit. M max is the maximum number of TBs or TB groups scheduled by the DCI. Representing the number of scheduled TBs or TB groups as M, for example, the first M bits in the bitmap where b k , k = 0, 1, …, M - 1 each indicate whether the corresponding TB or TB group is a new transmission or a retransmission, for example, by indicating either 0 or 1. The ‘M + 1’-th bit in the bitmap that does not have a corresponding TB or TB group, for example, b M is set to a different value from the ‘M’-th bit, for example, b M-1 , if it exists. The last M max - M bits in the bitmap are set to the same value as the ‘M + 1’-th bit, if they exist.

[0022] The NRI field can be directly configured to include a bitmap of length M max and one special bit.

[0023] Instead, the NRI field may be directly configured as a bitmap of length M max + 1. The last bit serves as the special bit.

[0024] Instead, M max 'may be explicitly indicated in the DCI.

[0025] Instead, the NRI field is M max The subfield may be configured to include fewer subfields than bits and one special bit. The subfield may be up to M max To enable the distinction between new transmissions and retransmissions for each TB or TB group, M max This can be interpreted as bits. For example, the subfield may represent a group of consecutive TBs that are all new transmissions or all retransmissions. In this case, the starting TB index and the number of TBs in the group may be used for indication.

[0026] In one option, the special bit is, for example, b M-1 The 'M'th bit in the bitmap is set to a different value. Therefore, UE is the last M in the bitmap that has the same value as the special bit. max -M bits are considered unscheduled if they exist. The last bit in the bitmap that has a different value from the special bits indicates the last scheduled TB or TB group.

[0027] Figure 4 shows M max =This shows a method for indicating the number of scheduled TBs (M) based on a 20-bit bitmap and special bits. New transmissions and retransmissions are indicated by the values ​​'0' and '1', respectively. In Figure 4(A), since the last scheduled TB is for a new transmission, all remaining bits in the bitmap are set to '1'. The special bits are set to '1'. The UE considers that TBs associated with the last group of bits in the bitmap that have the same value as the special bit, for example, '1', are not scheduled. For comparison, in Figure 4(B), if the last scheduled TB is for a retransmission, all remaining bits in the bitmap are set to '0'. The special bits are also set to '0'. In extreme cases, M maxAssuming that 20 TBs are scheduled by DCI, all 20 bits in the bitmap are useful. In this case, the special bit is set to a different value from the last bit of the bitmap. As shown in Figure 4(C), the last TB is a new transmission, so the special bit can be set to '1'.

[0028] In another option, a special bit indicates whether the last bit in the bitmap with the same value is valid for indicating a scheduled TB or TB group. For example, the values ​​'0' and '1' mean that the last bit is valid or invalid, respectively. Therefore, if the special bit is '1', the UE is valid for indicating the last M in the bitmap with the same value. max -M bits are considered unscheduled TBs or TB groups. The last bit in the bitmap that has a different value from the last bit in the bitmap indicates the last scheduled TB or TB group. On the other hand, if the special bit is '0', the UE considers all bits in the bitmap to indicate scheduled TBs or TB groups.

[0029] Figure 5 shows M max =This shows a method for indicating the number of scheduled TBs (M) based on a 20-bit bitmap and a special bit as an effectiveness indicator. New transmissions and retransmissions are indicated by the values ​​'0' and '1', respectively. In Figure 5(A), since the last scheduled TB is for a new transmission, all remaining bits in the bitmap are set to '1'. The special bit is set to '1' to indicate that the last consecutive '1's in the bitmap are not valid for indicating a scheduled TB. For comparison, in Figure 5(B), if the last scheduled TB is for a retransmission, all remaining bits in the bitmap are set to '0'. In this case as well, the special bit is set to '1' to indicate that the last consecutive '0's in the bitmap are not valid for indicating a scheduled TB. maxAssuming that 20 TBs are scheduled by DCI, all 20 bits in the bitmap are useful. In this case, as shown in Figure 5(C), the special bit is set to '0' to indicate that all bits in the bitmap are valid for representing scheduled TBs.

[0030] In one embodiment, the NRI field in DCI has a length M max It can be interpreted as a bitmap of +1. max This is the maximum number of TBs or TB groups scheduled by DCI. Let M be the number of scheduled TBs, for example b k The first M bits in a bitmap where k=0,1,...,M-1 indicate the corresponding TB or TB group as either a new transmission or a retransmission, for example, by each representing either 0 or 1. The 'M+1'th bit in a bitmap that does not have a corresponding TB or TB group, for example b M For example, b M-1 The 'M'th bit is set to a different value. max Each of the +1-M bits is set to the same value as the 'M+1'th bit. Thus, the UE is the last M in the bitmap that has the same value as the last bit of the bitmap. max The +1-M bit is considered not associated with a scheduled TB. The last bit in the bitmap that has a different value compared to the last bit in the bitmap indicates the last scheduled TB or TB group.

[0031] The NRI field has a length M max It can be directly constructed as a bitmap with +1.

[0032] Instead, the NRI field is M max The subfield may be configured to include fewer subfields than bits and one special bit. The subfield may be up to M max To enable the distinction between new transmissions and retransmissions for each TB or TB group, Mmax This can be interpreted as bits. For example, the subfield may represent a group of consecutive TBs that are all new transmissions or all retransmissions. In this case, the starting TB index and the number of TBs in the group may be used for indication. max The individual bits and special bits have a length M max It is combined into a bitmap with +1.

[0033] Figure 6 shows M max This shows a method for indicating the number of scheduled TBs (M) based on a +1=21-bit bitmap. New transmissions and retransmissions are indicated by the values ​​'0' and '1', respectively. In Figure 6(A), the last scheduled TB is for a new transmission, so all remaining bits in the bitmap are set to '1'. The UE considers TBs associated with the last group of bits in the bitmap that have the same value as the last bit, for example, '1', as not scheduled. For comparison, in Figure 6(B), if the last scheduled TB is for a retransmission, all remaining bits in the bitmap are set to '0'. In extreme cases, M max Assuming that 20 TBs are scheduled by DCI, all 20 bits in the bitmap are useful. In this case, the last bit is set to a different value from the last bit of the bitmap. As shown in Figure 6(C), since the last TB is a new transmission, the last bit can be set to '1'.

[0034] Enabling zero padding and potential early termination of NRI fields The NRI field within DCI has a length M. max It can be interpreted as a bitmap. max This is the maximum number of TBs or TB groups scheduled by DCI. Each bit in the bitmap indicates either 0 or 1, thereby indicating the corresponding TB or TB group as either a new transmission or a retransmission. Thus, the maximum M maxYou can send individual TBs or TB groups. However, if early termination occurs, the number of TBs or TB groups sent will be M max It may be less than X. The maximum number of symbols within the allocated time resource is, for example, X max =L·M max It can be calculated using +R, where R is the number of DMRS symbols within the allocated time resource, and L and M are also included. max , or X max This can be derived by the following. Note that one HARQ-ACK bit may be reported for TB or TB group.

[0035] The NRI field has a length M max It can be directly constructed as a bitmap of . Alternatively, the NRI field is M max It may consist of fewer than a bit. The NRI field may, in that case, be up to M. max To enable the distinction between new transmissions and retransmissions for each TB or TB group, M max It is interpreted as bits. For example, the NRI may represent a group of consecutive TBs that are all new transmissions or all retransmissions. In this case, the starting TB index and the number of TBs in the group may be used for indication.

[0036] Each entry in the TDRA field indicates information S and L about the assigned data transmission. Information NRI, on the other hand, is indicated by a separate field in the DCI. The number of scheduled TBs or TB groups is not indicated by each entry in the TDRA table, which simplifies the structure of the TDRA table. A reduction in the size of the TDRA table is expected without affecting scheduling flexibility. Alternatively, information S, L, and NRI may be indicated by separate fields in the DCI.

[0037] Extended frequency hopping for data transmission In NR Release 15, the system design targets carrier frequencies up to 52.6 GHz using cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform selection for DL ​​and UL, and further, discrete Fourier transform-spread-OFDM (DFT-s-OFDM) for UL. However, at carrier frequencies higher than 52.6 GHz, single-carrier-based waveforms are expected to be required to address issues including low power amplifier (PA) efficiency and high phase noise.

[0038] For single-carrier based waveforms, DFT-s-OFDM can be considered for both DL and UL. In OFDM-based transmission schemes, including DFT-s-OFDM, a cyclic prefix (CP) is inserted at the beginning of each block, and the last data symbol within the block is repeated as the CP. Typically, the length of the CP exceeds the maximum expected delay spread to overcome inter-symbol interference (ISI).

[0039] In NR, for non-repetitive physical uplink shared channels (PUSCH), intra-slot frequency hopping can be used to leverage the benefits of frequency diversity. For PUSCH repetition type A, inter-slot frequency hopping can also be used to improve performance, with frequency hopping performed in all slots for PUSCH repetitions. For PUSCH repetition type B, inter-repetition frequency hopping can be used, with frequency hopping performed based on nominal repetitions. Figure 7 shows an example of intra-slot frequency hopping for PUSCH in NR. In the example shown in Figure 7, frequency hopping is performed for half the duration of the PUSCH transmission within the slot.

[0040] In systems operating at carrier frequencies higher than 52.6 GHz or in 6G communication systems, larger subcarrier spacings are expected to be required to cope with significant phase noise. When larger subcarrier spacings, such as 1.92 MHz or 3.84 MHz, are used, slot durations can become very short. These extremely short slot durations may not be sufficient for higher-layer processing, including the Medium Access Layer (MAC) and Radio Link Control (RLC). To address this problem, gNBs can schedule DL or UL data transmissions across slot boundaries, indicating that the concept of slots may not be necessary.

[0041] Furthermore, for high data throughput, it can be expected that a relatively large number of transport blocks (TBs) can be scheduled using a single downlink control information (DCI) for physical downlink shared channels (PDSCHs) and physical uplink shared channels (PUSCHs). In this case, in order to take advantage of frequency diversity, it may be necessary to consider specific extensions to frequency hopping for PDSCH or PUSCH transmissions.

[0042] The various embodiments described herein provide an extended frequency hopping mechanism for systems operating at higher carrier frequencies.

[0043] Extended frequency hopping mechanism As mentioned above, systems operating at carrier frequencies higher than 52.6 GHz or 6G communication systems are expected to require larger subcarrier spacings to cope with significant phase noise. When larger subcarrier spacings, such as 1.92 MHz or 3.84 MHz, are used, slot durations can become very short. These extremely short slot durations may not be sufficient for higher-layer processing, including the Medium Access Layer (MAC) and Radio Link Control (RLC). To address this problem, gNBs can schedule DL or UL data transmissions across slot boundaries, indicating that the concept of slots may not be necessary.

[0044] Furthermore, for high data throughput, it can be expected that a relatively large number of transport blocks (TBs) can be scheduled using a single downlink control information (DCI) for physical downlink shared channels (PDSCHs) and physical uplink shared channels (PUSCHs). In this case, in order to take advantage of frequency diversity, it may be necessary to consider specific extensions to frequency hopping for PDSCHs or PUSCHs.

[0045] An extended embodiment of the frequency hopping mechanism is provided below.

[0046] In one embodiment, several transport blocks (TBs) can be grouped into a TB group. Furthermore, frequency hopping is performed within the TB group. In particular, the number of TBs in a TB group can be determined by the upper layer via Minimum System Information (MSI), Remaining Minimum System Information (RMSI), Other System Information (OSI), or Dedicated Radio Resource Control (RRC) signaling, or dynamically indicated within Downlink Control Information (DCI), or a combination thereof.

[0047] To enable frequency hopping, the first part of the TB is transmitted at the first hop, and the second part of the TB is transmitted at the second hop. In this case, the mapping order of the TB can be determined in a time-first, frequency-second manner. More specifically, in an allocated resource, the TB is mapped first in the time domain, and then in the frequency domain.

[0048] Furthermore, a dedicated DMRS symbol is assigned to each hop prior to the transmission of the first TB in a TB group, or to the entire hopping boundary where the UE performs one frequency hop. If a relatively large number of symbols are assigned to each hop, additional DMRS symbols may be assigned in the middle of the TBs at each hop.

[0049] Figure 8 shows an example of frequency hopping in units of TB groups. In this example, the TB spans four symbols. Also, the number of TBs for time-domain HARQ-ACK bundling is two. In this case, the first portion of TB0 and TB1 is transmitted at the first hop, and the second portion of TB0 and TB1 is transmitted at the second hop. This frequency hopping pattern continues until all TBs are assigned.

[0050] Furthermore, depending on the number of symbols assigned to TB, one or more TBs may be mixed into the same symbol when frequency hopping is applied, for example, when one symbol is assigned to TB.

[0051] Figure 9 shows an example of frequency hopping over mixed TBs. In this example, the number of symbols assigned to a TB is 1, and the number of TBs in the TB group for frequency hopping is 4. In this case, the first portion of TB0 and TB1 is transmitted at the first hop within the same symbol, and the second portion of TB0 and TB1 is transmitted at the second hop within the same symbol.

[0052] In another embodiment, to enable high-speed processing, TB transmissions may be aligned with symbol boundaries. In this case, frequency hopping may be performed within several symbols in a PDSCH or PUSCH transmission. The number of symbols for the entire hopping boundary on which the UE performs a single frequency hop may be configured by the upper layers via MSI, RMSI (SIB1), OSI, or RRC signaling, or dynamically indicated within DCI, or a combination thereof. The number of symbols configured or indicated for the entire hopping boundary may or may not include demodulation reference symbols (DMRS).

[0053] Similarly, a dedicated DMRS symbol is assigned to each hop prior to the transmission of the first TB in a TB group, or to the entire hopping boundary where the UE performs one frequency hop. If a relatively large number of symbols are assigned to each hop, additional DMRS symbols may be assigned in the middle of the TBs at each hop.

[0054] Figure 10 shows an example of frequency hopping in TB units. In this example, the TB spans 8 symbols. Furthermore, when frequency hopping is enabled, the TB is divided into two parts: the first 4 symbols are transmitted at the first hop, and the second 4 symbols are transmitted at the second hop. In this case, the total number of symbols across the hopping boundary is 8, which can be dynamically represented within DCI.

[0055] In another embodiment, when time-domain bundling is enabled for hybrid automatic retransmission request-delivery acknowledgment (HARQ-ACK) feedback, the number of symbols over the entire hopping boundary for frequency hopping or the number of TBs within a TB group may be determined according to the time-domain bundling size configured or indicated for HARQ-ACK feedback.

[0056] In one example, if the HARQ-ACK feedback for two TBs is bundled into a single HARQ-ACK bit, and the number of symbols for the TB is four, then the number of symbols for frequency hopping is eight, which may or may not include the demodulation reference symbol (DMRS).

[0057] In another embodiment, in the case of mixed initial and retransmissions in PDSCH or PUSCH, the gNB may schedule different modulation orders for the initial and retransmissions of the TB. In this case, one or more dedicated DMRSs are assigned to the initial and retransmissions of the TB, respectively.

[0058] In this case, when frequency hopping is enabled, the TB retransmissions are grouped first for frequency hopping, followed by the initial TB transmission on the PDSCH or PUSCH.

[0059] Figure 11 shows an example of frequency hopping for retransmission and initial transmission. In this example, two TBs are retransmitted at the beginning of either PDSCH or PUSCH. After the retransmitted TBs, four TBs are initially transmitted.

[0060] Furthermore, a similar mechanism can be directly extended when dedicated DMRS symbols are used for UCI, initial transmission, and retransmission. In this case, the UCI can be divided into two equal parts, with the first part transmitted at the first hop and the second part transmitted at the second hop. The retransmission TB then follows the UCI, followed by the initial transmission of the TB.

[0061] System and Implementation Figures 12-14 show various systems, devices, and components that can implement aspects of the disclosed embodiments.

[0062] Figure 12 shows network 1200 according to various embodiments. Network 1200 may operate in a manner consistent with the 3GPP technical specifications for LTE or 5G / NR systems. However, the examples of embodiments are not limited thereto, and the embodiments described may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems or similar systems.

[0063] Network 1200 may include UE1202, which may include any mobile or non-mobile computing device designed to communicate with RAN1204 via an over-the-air connection. UE1202 may be coupled to RAN1204 in a communicative manner via a Uu interface. UE1202 may include, but is not limited to, smartphones, tablet computers, wearable computer devices, desktop computers, laptop computers, automotive infotainment, automotive entertainment devices, instrument clusters, head-up display devices, automotive diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0064] In some embodiments, the network 1200 may include multiple UEs directly coupled to one another via sidelink interfaces. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but are not limited to, PSBCH, PSDCH, PSSCH, PSCCH, and PSFCH.

[0065] In some embodiments, UE1202 may further communicate with AP1206 via an over-the-air connection. AP1206 may manage a WLAN connection that may serve to offload some / all network traffic from RAN1204. The connection between UE1202 and AP1206 may conform to any IEEE 802.11 protocol, and AP1206 may be a Wireless Fidelity (Wi-Fi®) router. In some embodiments, UE1202, RAN1204, and AP1206 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve UE1202 being configured by RAN1204 to utilize both cellular radio resources and WLAN resources.

[0066] RAN1204 may include one or more access nodes, such as AN1208. AN1208 may terminate the air interface protocol to UE1202 by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. Thus, AN1208 may enable data / voice connectivity between CN1220 and UE1202. In some embodiments, AN1208 may be implemented as a separate device, or as one or more software entities running on a server computer as part of a virtual network, which may be referred to as CRAN or a virtual baseband unit pool, for example. AN1208 may be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN1208 may be a macrocell base station, or a low-power base station for providing femtocells, picocells, or other similar cells with smaller coverage areas, smaller user capacities, or higher bandwidths compared to macrocells.

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

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

[0069] RAN1204 may provide an air interface on the licensed or unlicensed spectrum. To operate within the unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA technology using PCell / SCell. Prior to accessing the unlicensed spectrum, a node may perform medium / carrier sensing operations based, for example, on a listen-before-talk (LBT) protocol.

[0070] In a V2X scenario, UE1202 or AN1208 may be an RSU, or fulfill that role, which may refer to any transport infrastructure entity used for V2X communication. 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 eNB as an “eNB-type RSU,” a gNB as a “gNB-type RSU,” and so on. In one example, the RSU is a roadside computing device coupled with radio frequency circuitry that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling oncoming vehicle and pedestrian traffic. The RSU may provide very low-latency communication required for high-speed events such as collision avoidance and traffic warnings. In addition, or instead, the RSU may provide other cellular / WLAN communication services. The RSU components can be packaged in a weather-resistant enclosure suitable for outdoor installation and may include a network interface controller for providing wired connectivity (e.g., Ethernet®) to a traffic signal controller or backhaul network.

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

[0072] In some embodiments, RAN1204 may be an NG-RAN1214 having a gNB such as gNB1216 or an ng-eNB such as ng-eNB1218. gNB1216 may connect to a 5G-enabled UE using a 5G NR interface. gNB1216 may connect to a 5G core via an NG interface which may include an N2 interface or an N3 interface. ng-eNB1218 may also connect to a 5G core via an NG interface, but may connect to a UE via an LTE air interface. gNB1216 and ng-eNB1218 may connect to each other via an Xn interface.

[0073] In some embodiments, the NG interface can be divided into two parts: an NG user plane (NG-U) interface (e.g., N3 interface) that carries traffic data between the NG-RAN1214 node and the UPF1248, and an NG control plane (NG-C) interface (e.g., N2 interface) that is a signaling interface between the NG-RAN1214 node and the AMF1244.

[0074] NG-RAN1214 may provide a 5G-NR air interface having the characteristics of variable SCS, CP-OFDM for DL, CP-OFDM for UL, and DFT-s-OFDM, polar, iterative, simplex, and Reed-Müller code for control, and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to an LTE air interface. The 5G-NR air interface may use PBCH DMRS for PBCH demodulation, PTRS for phase tracking for PDSCH, and a tracking reference signal for time tracking, without using CRS. The 5G-NR air interface may operate on the FR1 band, including the sub-6GHz band, or the FR2 band, including the 24.25GHz to 52.6GHz band. The 5G-NR air interface may include SSB, which is an area of ​​the downlink resource grid including PSS / SSS / PBCH.

[0075] In some embodiments, a 5G-NR air interface can utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For instance, UE1202 can be composed of multiple BWPs, each with a different SCS. When a BWP change is indicated to UE1202, the SCS for transmission is also changed accordingly. Another use case example of BWPs relates to power saving. In particular, multiple BWPs with different amounts of frequency resources (e.g., PRBs) can be configured for UE1202 to support data transmission under different traffic load scenarios. Power saving in UE1202 and, in some cases, gNB1216 can be enabled by using BWPs with fewer PRBs for data transmission with low traffic loads. For scenarios with higher traffic loads, BWPs with more PRBs can be used.

[0076] RAN1204 is communicatively coupled to CN1220, which includes network elements for providing customers / subscribers (e.g., users of UE1202) with various functions to support data and telecommunications services. The components of CN1220 may be implemented in a single physical node or in multiple separate physical nodes. In some embodiments, NFV may be used to virtualize some or all of the functions provided by the network elements of CN1220 onto physical computing / storage resources such as servers and switches. Logical instantiations of CN1220 may be referred to as network slices, and some logical instantiations of CN1220 may be referred to as network subslices.

[0077] In some embodiments, CN1220 may be LTE CN1222, which may also be referred to as EPC. LTE CN1222 may include MME1224, SGW1226, SGSN1228, HSS1230, PGW1232, and PCRF1234 coupled to each other via an interface (or “reference point”) as shown in the figure. A brief description of the functions of these elements of LTE CN1222 may be as follows:

[0078] The MME1224 can implement mobility management features to track the current location of the UE1202, facilitating paging, bearer activation / deactivation, handover, gateway selection, authentication, and more.

[0079] The SGW1226 terminates the S1 interface toward the RAN and can route data packets between the RAN and the LTE CN1222. The SGW1226 can serve as a local mobility anchor point for handovers between RAN nodes and can also provide an anchor for 3GPP-to-3GPP mobility. Other responsibilities may include lawful interception, billing, and certain policy enforcement.

[0080] The SGSN1228 can track the location of the UE1202 and perform security functions and access control. Furthermore, the SGSN1228 can perform EPC node signaling for mobility between different RAT networks, PDN and S-GW selection specified by the MME1224, MME selection for handover, etc. An S3 reference point between the MME1224 and the SGSN1228 can enable the exchange of user and bearer information for mobility between 3GPP access networks in idle / active states.

[0081] The HSS1230 may include a database for network users containing join-related information to support the processing of network entities in communication sessions. The HSS1230 can provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS1230 and the MME1224 may enable the transfer of join and authentication data for authenticating / authorizing user access to the LTE CN1220.

[0082] PGW1232 may terminate an SGi interface toward a data network (DN) 1236, which may include an application / content server 1238. PGW1232 may route data packets between LTE CN1222 and data network 1236. PGW1232 may be coupled to SGW1226 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW1232 may further include nodes (e.g., PCEF) for policy enforcement and billing data collection. The SGi reference point between PGW1232 and data network 1236 may be, for example, an operator-external public, private PDN, or operator-internal packet data network for providing IMS services. PGW1232 may be coupled to PCRF1234 via a Gx reference point.

[0083] PCRF1234 is the policy and billing control element of LTE CN1222. PCRF1234 can be communicatively coupled to the application / content server 1238 to determine appropriate QoS and billing parameters for the service flow. PCRF1234 can provision relevant rules to the PCEF (via the Gx reference point) using appropriate TFT and QCI.

[0084] In some embodiments, CN1220 may be 5GC1240. 5GC1240 may include AUSF1242, AMF1244, SMF1246, UPF1248, NSSF1250, NEF1252, NRF1254, PCF1256, UDM1258, and AF1260 coupled to each other via interfaces (or “reference points”) as shown in the figure. A brief description of the functions of these elements of 5GC1240 may be as follows:

[0085] The AUSF1242 can store data for authentication of the UE1202 and handle authentication-related functions. The AUSF1242 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC1240 via the illustrated reference point, the AUSF1242 can represent a Nausf service-based interface.

[0086] The AMF1244 can enable other functions of the 5GC1240 to communicate with the UE1202 and RAN1204, and to subscribe to notifications about mobility events related to the UE1202. The AMF1244 can be responsible for registration management (e.g., for registering the UE1202), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF1244 can provide transport for SM messages between the UE1202 and SMF1246, and can also act as a transparent proxy for routing SM messages. The AMF1244 can also provide transport for SMS messages between the UE1202 and SMSF. The AMF1244 can interact with the AUSF1242 and UE1202 to perform various security anchor and context management functions. Furthermore, the AMF1244 can be the endpoint of a RAN CP interface that includes or may include an N2 reference point between the RAN1204 and the AMF1244, and the AMF1244 can also be the endpoint of NAS(N1) signaling, enabling NAS encryption and integrity protection. The AMF1244 may also support NAS signaling with the UE1202 via an N3 IWF interface.

[0087] SMF1246 may be responsible for SM (e.g., session establishment, tunnel management between UPF1248 and AN1208), UE IP address allocation and management (including optional authorization), selection and control of UP functions, configuration of traffic steering in UPF1248 for routing traffic to appropriate destinations, termination of interfaces toward policy control functions, control of policy enforcement, billing, and QoS portions, lawful interception (for SM events and interfaces to L1 systems), termination of SM portions of NAS messages, downlink data notification, initiation of AN-specific SM information sent to AN1208 on N2 via AMF1244, and determination of the session's SSC mode. SM refers to the management of PDU sessions, and PDU session or “session” may refer to PDU connectivity services that provide or enable the exchange of PDUs between UE1202 and data network 1236.

[0088] UPF1248 can serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to data network 1236, and a branching point to support multi-homed PDU sessions. UPF1248 can also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), perform transport-level packet marking on uplinks and downlinks, and perform downlink packet buffering and downlink data notification triggering. UPF1248 may include an uplink classifier to support routing traffic flows to the data network.

[0089] The NSSF1250 can select a set of network slice instances to service the UE1202. The NSSF1250 can also determine, if necessary, the authorized NSSAIs and their mappings to the joined S-NSSAIs. The NSSF1250 can also determine, based on a preferred configuration and possibly by querying the NRF1254, a set of AMFs, or a list of candidate AMFs, to be used to service the UE1202. The selection of a set of network slice instances for the UE1202 can be triggered by the AMF1244 to which the UE1202 registers, by interacting with the NSSF1250, which may lead to a change in the AMF. The NSSF1250 can interact with the AMF1244 via the N22 reference point and can communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, the NSSF1250 can represent an Nnssf service-based interface.

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

[0091] The NRF1254 supports service discovery functionality, receiving NF discovery requests from NF instances and providing NF instances with information about discovered NF instances. The NRF1254 also maintains information about available NF instances and their supported services. Where used herein, the terms “instantiate,” “instantiate,” and similar terms can refer to the creation of an instance, and “instance” can refer to the specific occurrence of an object, for example, during the execution of program code. Furthermore, the NRF1254 can represent an Nnrf service-based interface.

[0092] The PCF1256 can provide policy rules to control plane functions and enforce them, and can also support an integrated policy framework to manage network behavior. The PCF1256 can also implement a front-end for accessing subscription information related to policy decisions within the UDR of the UDM1258. In addition to communicating with functions via the illustrated reference point, the PCF1256 exhibits an Npcf service-based interface.

[0093] The UDM1258 can process join-related information to support the processing of network entities in a communication session and can store join data for the UE1202. For example, join data may be communicated via an N8 reference point between the UDM1258 and the AMF1244. The UDM1258 may consist of two parts: an application frontend and a UDR. The UDR may store join data and policy data for the UDM1258 and PCF1256, and / or structured data for publication and application data for the NEF1252 (including a PFD for application discovery and application request information for multiple UE1202s). A Nudr service-based interface may be provided by the UDR to enable the UDM1258, PCF1256, and NEF1252 to access specific sets of stored data and to read, update (e.g., add, modify), delete, and register for notifications of changes to the relevant data in the UDR. The UDM may include a UDM-FE responsible for credential processing, location management, and enrollment management. Several different frontends may serve the same user in different transactions. The UDM-FE accesses enrollment information stored in the UDR and performs authentication certificate processing, user identification processing, access permission, enrollment / mobility management, and enrollment management. In addition to communicating with other NFs via the illustrated reference point, the UDM1258 may represent a Nudm service-based interface.

[0094] The AF1260 provides application influence over traffic routing, offers access to the NEF, and can interact with the policy framework for policy control.

[0095] In some embodiments, the 5GC1240 may enable edge computing by selecting operator / third-party services to be geographically closer to the point where the UE1202 is attached to the network. This can reduce latency and load on the network. To provide an edge computing implementation, the 5GC1240 may select the UPF1248, which is closer to the UE1202, and perform traffic steering from the UPF1248 to the data network 1236 via the N6 interface. This may be based on UE subscriber data, UE location, and information provided by the AF1260. Thus, the AF1260 may influence UPF (re)selection and traffic routing. When the AF1260 is considered a trusted entity based on operator deployment, the network operator may allow the AF1260 to directly interact with the relevant NF. In addition, the AF1260 may represent a NAF service-based interface.

[0096] The data network 1236 may represent various network operator services, internet access, or third-party services that may be provided by one or more servers, for example, including an application / content server 1238.

[0097] Figure 13 schematically illustrates the wireless network 1300 according to various embodiments. The wireless network 1300 may include a UE 1302 that wirelessly communicates with AN 1304. UE 1302 and AN 1304 are similar to and substantially interchangeable with other components of similar names described elsewhere in this document.

[0098] UE1302 can be communicatively coupled to AN1304 via connection 1306. Connection 1306 is shown as an air interface to enable communication coupling and can be matched to a cellular communication protocol such as the LTE protocol or the 5G NR protocol operating on mm wave or sub-6GHz frequencies.

[0099] UE1302 may include a host platform 1308 coupled to a modem platform 1310. The host platform 1308 may include an application processing circuit 1312, which may be coupled to a protocol processing circuit 1314 of the modem platform 1310. The application processing circuit 1312 may execute various applications for UE1302 to source / sink application data. The application processing circuit 1312 may further implement one or more layer operations for sending / receiving application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

[0100] The protocol processing circuit 1314 may implement one or more layer operations to facilitate the transmission or reception of data via the connection 1306. Layer operations implemented by the protocol processing circuit 1314 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0101] The modem platform 1310 may further include a digital baseband circuit 1316 that can implement one or more layer operations "below" the layer operations performed by the protocol processing circuit 1314 in the network protocol stack. These operations may include, for example, PHY operations that include one or more of the following: HARQ-ACK functionality, scrambling / descrambling, coding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bitmetric determination, multi-antenna port precoding / decoding which may include one or more of space-time, space-frequency, or space coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronous sequence generation / detection, control channel signal blind decoding, and other related functions.

[0102] The modem platform 1310 may further include a transmitting circuit 1318, a receiving circuit 1320, an RF circuit 1322, and an RF front end (RFFE) 1324 which may include or be connected to one or more antenna panels 1326. In short, the transmitting circuit 1318 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receiving circuit 1320 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 1322 may include a low-noise amplifier, a power amplifier, a power tracking component, etc.; and the RFFE 1324 may include filters (e.g., surface / bulk acoustic wave filters), switches, an antenna tuner, a beamforming component (e.g., a phased array antenna component), etc. The selection and arrangement of components for the transmitting circuit 1318, receiving circuit 1320, RF circuit 1322, RFFE 1324, and antenna panel 1326 (collectively referred to as the “transmitting / receiving components”) may be specific to the details of the implementation, such as whether the communication is TDM or FDM, or whether it is within the millimeter wave or sub-6 GHz frequency range. In some embodiments, the transmitting / receiving components may consist of multiple parallel transmitting / receiving chains and may be located on the same or different chips / modules.

[0103] In some embodiments, the protocol processing circuit 1314 may include one or more instances of a control circuit (not shown) for providing control functions for the transmit / receive components.

[0104] UE reception can be established by and through the antenna panel 1326, RFFE 1324, RF circuit 1322, receiving circuit 1320, digital baseband circuit 1316, and protocol processing circuit 1314. In some embodiments, the antenna panel 1326 can receive transmissions from AN1304 by receiving beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 1326.

[0105] UE transmission can be established by and through the protocol processing circuit 1314, the digital baseband circuit 1316, the transmitting circuit 1318, the RF circuit 1322, the RFFE 1324, and the antenna panel 1326. In some embodiments, the transmitting component of UE 1302 may apply a spatial filter to the data to be transmitted in order to form a transmit beam radiated by the antenna elements of the antenna panel 1326.

[0106] Similar to UE1302, AN1304 may include a host platform 1328 coupled with a modem platform 1330. The host platform 1328 may include an application processing circuit 1332 coupled with the protocol processing circuit 1334 of the modem platform 1330. The modem platform may further include a digital baseband circuit 1336, a transmit circuit 1338, a receive circuit 1340, an RF circuit 1342, an RFFE circuit 1344, and an antenna panel 1346. These components of AN1304 may be similar to similarly named components of UE1302 and may be substantially interchangeable. In addition to performing data transmission / reception as described above, the components of AN1304 may perform various logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0107] Figure 14 is a block diagram showing a component according to one embodiment, capable of reading instructions from a machine-readable medium or a computer-readable medium (e.g., a non-temporary machine-readable storage medium) and executing one or more of the methods described herein. Specifically, Figure 14 shows a schematic representation of hardware resources 1400, which include one or more processors (or processor cores) 1410, one or more memory / storage devices 1420, and one or more communication resources 1430, each of which may be communicatively coupled via a bus 1440 or other interface circuitry. In embodiments utilizing node virtualization (e.g., NFV), a hypervisor 1402 may be executed to provide an execution environment for one or more network slices / subslice to utilize the hardware resources 1400.

[0108] The processor 1410 may include, for example, processor 1412 and processor 1414. The processor 1410 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a composite instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), other processors (including those described herein), or any preferred combination thereof.

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

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

[0111] Instruction 1450 may contain software, programs, applications, applets, apps, or other executable code that causes at least one of the processors 1410 to perform one or more of the methods described herein. Instruction 1450 may reside, whole or in part, in at least one of the processors 1410 (e.g., in the processor's cache memory), in the memory / storage device 1420, or in any preferred combination thereof. Any part of instruction 1450 may also be transferred to the hardware resource 1400 from any combination of the peripheral device 1404 or the database 1406. Thus, the memory of the processor 1410, the memory / storage device 1420, the peripheral device 1404, and the database 1406 are examples of computer-readable and machine-readable media.

[0112] Example procedure In some embodiments, one or more electronic devices, one or more networks, one or more systems, one or more chips, or one or more components, or parts or implementations thereof, shown in Figures 12–14 or some other figures herein, may be configured to perform one or more processes, techniques, or methods, or parts thereof, as described herein. One such process is shown in Figure 15. In this example, process 1500 includes, at 1505, retrieving configuration information from memory, including the number of transport blocks (TBs) for frequency hopping for data transmission related to a user device (UE), the configuration information including an indication of a TB group containing TBs, the configuration information indicating that frequency hopping for data transmission is performed within the TB group, and the configuration information indicating that a first part of a TB is transmitted at a first hop and a second part of the TB is transmitted at a second hop. The process further includes, at 1510, encoding a message containing the configuration information for transmission to the UE.

[0113] Another such process is shown in Figure 16. In this example, process 1600 includes determining, at 1605, configuration information including the number of transport blocks (TBs) for frequency hopping for data transmission related to a user device (UE), the configuration information including an indication of a TB group containing the TBs, the configuration information indicating that frequency hopping for data transmission is performed within the TB group, and the configuration information indicating that a first portion of a TB is transmitted at a first hop and a second portion of the TB is transmitted at a second hop. The process further includes encoding a message containing the configuration information for transmission to the UE at 1610.

[0114] Another such process is shown in Figure 17. In this example, process 1700 includes receiving a message from a next-generation NodeB (gNB) at 1705, the message having configuration information including the number of transport blocks (TBs) for frequency hopping for data transmission related to the UE, the configuration information including an indication of a TB group containing the TBs, the configuration information indicating that frequency hopping for data transmission is performed within the TB group, and the configuration information indicating that a first portion of a TB is transmitted at a first hop and a second portion of the TB is transmitted at a second hop. The process further includes receiving a physical downlink shared channel (PDSCH) message or encoding a physical uplink shared channel (PUSCH) message for transmission at 1710 based on the configuration information.

[0115] In one or more embodiments, at least one of the components shown in one or more of the above figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the following Examples section. For example, a baseband circuit described above in relation to one or more of the above figures may be configured to operate according to one or more of the examples described below. In another example, a circuit related to a UE, base station, network element, etc., described above in relation to one or more of the above figures may be configured to operate according to one or more of the examples described below in the Examples section.

[0116] example Example 1 may include a wireless communication method for scheduling multiple transport block transmissions for carrier frequencies higher than 52.6 GHz, and the method is: The UE detects downlink control information (DCI), The UE determines the scheduling information to be transported within DCI. It has the characteristic of having.

[0117] Example 2 may include the methods of Example 1 or any other example herein, wherein the DCI includes information regarding the start symbol (S) of the allocated time resource, the number of symbols for the TB or TB group (L), the total number of symbols for the allocated time resource (X), the number of scheduled TBs or TB groups (M), and the distinction (NRI) for new transmission or retransmission for each of the M scheduled TBs or TB groups.

[0118] Example 3 may include the methods of Example 2 or other examples here, where each entry in the Time Domain Resource Allocation (TDRA) field within the DCI indicates information S, L, M about the allocated data transmission, but NRI is a separate field within the DCI.

[0119] Example 4 may include the methods of Example 2 or other examples here, where each entry in the TDRA field indicates S and M for the assigned data transmission, but L and NRI are separate fields in DCI.

[0120] Example 5 may include the methods of Example 2 or other examples here, where each entry in the TDRA field indicates information S, L, X about the assigned data transmission, but NRI is a separate field in DCI.

[0121] Example 6 may include the methods of Example 2 or other examples here, where each entry in the TDRA field indicates S, X for the assigned data transmission, but L and NRI are separate fields in DCI.

[0122] Example 7 may include the methods of Example 1 or any other example herein, where the NRI field in DCI indicates the number of scheduled TBs or TB groups, e.g., M, and distinguishes each of the M TBs or TB groups as a new transmission or a retransmission.

[0123] Example 8 may include the method of Example 7 or any other example herein, where each entry in the TDRA field within DCI indicates information S, L about the assigned data transmission.

[0124] Example 9 may include the methods of Example 7 or other examples present, where information S and L are each represented by separate fields in the DCI.

[0125] Example 10 may include the method of Example 7 or any other example here, where the NRI field is of length M max Interpreted as a bitmap and one special bit, M max This is the maximum number of TBs or TB groups scheduled by DCI.

[0126] Example 11 may include the methods of Example 10 or any other example here, where the first M bits in the bitmap indicate whether the corresponding TB or TB group is a new transmission or a retransmission. The 'M+1'th bit in the bitmap that does not have a corresponding TB or TB group is set to a different value from the 'M'th bit, if present. The last M max The -M bit, if present, is set to the same value as the 'M+1'th bit.

[0127] Example 12 may include the methods of Example 11 or any other example here, where the special bit has a different value from the 'M'th bit in the bitmap.

[0128] Example 13 may include the method of Example 12 or any other example here, where UE is the last M in the bitmap that has the same value as the special bit. max -TBs corresponding to the M bit are considered unscheduled if they exist.

[0129] Example 14 may include the methods of Example 11 or other examples here, in which a special bit indicates whether the last bit in the bitmap having the same value is valid for indicating a scheduled TB or TB group.

[0130] Example 15 may include the methods of Example 14 or other examples here, and if the special bit is '1', then UE is the last M in the bitmap with the same value. max -If the TBs corresponding to M bits are not scheduled, the UE assumes that all bits in the bitmap represent a scheduled TB or TB group.

[0131] Example 16 may include the method of Example 7 or other examples here, where the NRI field in DCI is of length M max Interpreted as a bitmap of +1, M max This is the maximum number of TBs or TB groups scheduled by DCI.

[0132] Example 17 may include the methods of Example 16 or other examples here, where the first M bits in the bitmap indicate whether the corresponding TB or TB group is a new transmission or a retransmission. The 'M+1'th bit in the bitmap that does not have a corresponding TB or TB group is set to a different value from the 'M'th bit. The last M max Each of the +1-M bits is set to the same value as the 'M+1'th bit.

[0133] Example 18 may include the method of Example 17 or any other example here, where UE is the last M in the bitmap that has the same value as the last bit of the bitmap. max The +1-M bit is considered not to be associated with a scheduled TB.

[0134] Example 19 may include the method of Example 1 or any other example here, where the NRI field in DCI is of length M max Interpreted as a bitmap, M max This is the maximum number of TBs or TB groups scheduled by DCI. Each bit in the bitmap indicates the corresponding TB or TB group as a new transmission or retransmission.

[0135] Example 20 may include the method of Example 19 or any other example here, and if an early termination occurs, the number of TBs or TB groups sent is M max Less.

[0136] Example 21 may include a method, which is Receiving or transmitting downlink control information (DCI) that schedules the transmission of multiple transport blocks (TBs), the DCI indicating one or more of the following: the start symbol (S) of the allocated time resource, the number of symbols for the TB or TB group (L), the total number of symbols for the allocated time resource (X), the number of scheduled TBs or TB groups (M), and / or a new transmit / retransmit indicator (NRI) to indicate whether each TB is a new transmit or a retransmit. Receive or transmit transport blocks based on DCI. It has the characteristic of having.

[0137] Example 22 may include the methods of Example 21 or other examples herein, in which one or more of S, L, X, M, or NRI are included in the Time Domain Resource Allocation (TDRA) field for each TB, and one or more other of S, L, X, M, or NRI are included in separate fields within the DCI.

[0138] Example 23 may include the methods of Examples 21-22 or other examples herein, which are performed by a user device (UE) or a part thereof.

[0139] Example 24 may include the methods of Examples 21-22 or other examples herein, which are performed by a next-generation node B (gNB) or a portion thereof.

[0140] Example X1 may include a method for a user device (UE), which is: The number of transport blocks (TB) for frequency hopping is received from the gNodeB (gNB). Frequency hopping for transmission on the physical uplink shared channel (PUSCH) is performed according to the number of TBs indicated, or A physical downlink shared channel (PDSCH) is received using frequency hopping according to the number of TBs indicated above. It has the characteristic of having.

[0141] Example X2 may include the methods of Example X1 or other examples here, where frequency hopping is applied to a physical downlink shared channel (PDSCH) or PUSCH transmission.

[0142] Example X3 may include the possibility of grouping several transport blocks (TBs) into a TB group, where frequency hopping is performed within the TB group.

[0143] Example X4 may include the methods of Example X1 or other examples herein, where the number of TBs in a TB group may be configured by the upper layer via Minimum System Information (MSI), Remaining Minimum System Information (RMSI), Other System Information (OSI), or Dedicated Radio Resource Control (RRC) signaling, or dynamically indicated within Downlink Control Information (DCI), or a combination thereof.

[0144] Example X5 may include the method of Example X1 or any other example herein, in which the first part of the TB is transmitted at the first hop and the second part of the TB is transmitted at the second hop.

[0145] Example X6 may include the methods of Example X1 or other examples herein, and the mapping order of TB may be determined in the time-first, frequency-second manner.

[0146] Example X7 may include the methods of Example X1 or other examples here, where a dedicated DMRS symbol is assigned at each hop prior to the transmission of the first TB in the TB group, or across the entire hopping boundary where the UE performs one frequency hop. Example X8 may include the methods of Example X1 or any other example here, where one or more TBs may be mixed into the same symbol when frequency hopping is applied, such as when one symbol is assigned to a TB.

[0147] Example X9 may include the methods of Example X1 or other examples here, in which frequency hopping may be performed within some symbols in a physical downlink shared channel (PDSCH) or PUSCH transmit.

[0148] Example X10 may include the methods of Example X1 or other examples here, where the number of symbols for the entire hopping boundary in which the UE performs one frequency hopping may be configured by the upper layer via MSI, RMSI (SIB1), OSI, or RRC signaling, or dynamically represented within DCI, or a combination thereof.

[0149] Example X11 may include the methods of Example X1 or any other example herein, where, if time-domain bundling is enabled for hybrid automatic retransmission request-delivery acknowledgment (HARQ-ACK) feedback, the number of symbols for the entire hopping boundary for frequency hopping or the number of TBs in a TB group may be determined according to the time-domain bundling size configured or indicated for HARQ-ACK feedback.

[0150] Example X12 may include the methods of Example X1 or any other example herein, wherein, for mixed initial and retransmissions on a PDSCH or PUSCH, when frequency hopping is enabled, the retransmissions of the TB are grouped first for frequency hopping, followed by the initial transmission of the TB on the PDSCH or PUSCH.

[0151] Example X13 may include the methods of Example X1 or other examples herein, wherein for an uplink control channel (UCI) multiplexed on a PUSCH, the UCI may be divided into a first part and a second part, the first part transmitted at a first hop, the second part transmitted at a second hop, the retransmitted TB following the UCI, and then the initial transmission of the TB.

[0152] Example X14 may include a method for a user device (UE), which is: Receive an indication of the number of transport blocks (TB) for frequency hopping. According to the number of TBs indicated, encode the physical uplink shared channel (PUSCH) for transmission using frequency hopping, or A physical downlink shared channel (PDSCH) is received using frequency hopping according to the number of TBs indicated above. It has the characteristic of having.

[0153] Example X15 may include the method of Example X14 or any other example herein, in which the TBs are grouped into respective TB groups based on the aforementioned number of TBs shown, and frequency hopping is performed within each TB group.

[0154] Example X16 may include the methods of Examples X14-X15 or other examples herein, in which the indication of the number of TBs is received via Minimum System Information (MSI), Remaining Minimum System Information (RMSI), Other System Information (OSI), or Dedicated Radio Resource Control (RRC) signaling, or is dynamically indicated within Downlink Control Information (DCI), or a combination thereof.

[0155] Example X17 may include the methods of Examples X14-X16 or other examples herein, in which, as part of frequency hopping, a first portion of the TB is transmitted at a first hop and a second portion of the TB is transmitted at a second hop.

[0156] Example Y1 includes a device, and the device is A memory that stores configuration information including the number of transport blocks (TB) for frequency hopping for data transmission related to user equipment (UE), A processing circuit coupled to the memory, It has, The aforementioned processing circuit is The configuration information is retrieved from the memory, the configuration information includes an indication of a TB group including the TB, the configuration information indicates that the frequency hopping for data transmission is performed within the TB group, and the configuration information indicates that a first portion of a TB is transmitted at a first hop, and a second portion of the TB is transmitted at a second hop. The message containing the aforementioned configuration information is encoded for transmission to the UE.

[0157] Example Y2 includes the apparatus of Example Y1 or any other example herein, wherein the data transmission related to the UE is a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission.

[0158] Example Y3 includes the device of Example Y1 or any other example herein, wherein the configuration information in the message is included within Downlink Control Information (DCI), or the message is encoded for transmission via Minimum System Information (MSI), Remaining Minimum System Information (RMSI), Other System Information (OSI), or Dedicated Radio Resource Control (RRC) signaling.

[0159] Example Y4 includes the apparatus of Example Y1 or any other example herein, wherein the configuration information includes a TB mapping sequence defined in a time-first, frequency-second manner.

[0160] Example Y5 includes the apparatus of Example Y1 or any other example herein, wherein the configuration information indicates that each dedicated demodulated reference signal (DMRS) symbol is assigned at each hop prior to the transmission of the first TB in the TB group.

[0161] Example Y6 includes the apparatus of Example Y1 or any other example herein, wherein the configuration information indicates that one or more TBs are mixed into a common symbol when frequency hopping is applied.

[0162] Example Y7 includes the apparatus of Example Y1 or any other example herein, wherein the configuration information indicates the number of symbols for hopping boundaries or the number of TBs in a TB group for frequency hopping, based on the time domain bundling size for hybrid automatic retransmission request-delivery acknowledgment (HARQ-ACK) feedback.

[0163] Example Y8 includes the apparatus of any of Examples Y1 to Y7 or any other example herein, and the configuration information is For mixed initial and retransmissions on PDSCH or PUSCH, when frequency hopping is enabled, the TB retransmissions are grouped first for frequency hopping, followed by the initial transmission of the TB on PDSCH or PUSCH, or Regarding the uplink control channel (UCI) multiplexed on the PUSCH, the UCI is divided equally into a first part and a second part, the first part is transmitted at the first hop, the second part is transmitted at the second hop, the retransmitted TB follows the UCI, and the initial transmission of the TB follows the retransmitted TB. This indicates.

[0164] Example Y9 includes one or more computer-readable media containing instructions, which, when executed by one or more processors, are sent to a next-generation NodeB (gNB). The configuration information is determined, including the number of transport blocks (TBs) for frequency hopping for data transmission related to the user equipment (UE), the configuration information includes an indication of a TB group containing the TBs, the configuration information indicates that the frequency hopping for data transmission is performed within the TB group, and the configuration information indicates that a first portion of a TB is transmitted at a first hop, a second portion of the TB is transmitted at a second hop, The message containing the aforementioned configuration information is encoded for transmission to the UE.

[0165] Example Y10 includes one or more computer-readable media of Example Y9 or other examples herein, wherein the data transmission relating to the UE is a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission.

[0166] Example Y11 includes one or more computer-readable media of Example Y9 or other examples herein, wherein the configuration information in the message is included within downlink control information (DCI), or the message is encoded for transmission via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI), or dedicated radio resource control (RRC) signaling.

[0167] Example Y12 includes one or more computer-readable media of Example Y9 or other examples herein, wherein the configuration information includes a TB mapping sequence defined in a time-first, frequency-second manner.

[0168] Example Y13 includes one or more computer-readable media of Example Y9 or other examples herein, wherein the configuration information indicates that each dedicated demodulated reference signal (DMRS) symbol is assigned at each hop prior to the transmission of the first TB in the TB group.

[0169] Example Y14 includes one or more computer-readable media of Example Y9 or other examples herein, wherein the configuration information indicates that one or more TBs are mixed into a common symbol when frequency hopping is applied.

[0170] Example Y15 includes one or more computer-readable media of Example Y9 or other examples herein, wherein the configuration information indicates the number of symbols for hopping boundaries or the number of TBs in a TB group for frequency hopping, based on the time domain bundling size for hybrid automatic retransmission request-delivery acknowledgment (HARQ-ACK) feedback.

[0171] Example Y16 includes a computer-readable medium from any of Examples Y9 to Y15 or one or more of the other examples herein, and the configuration information is For mixed initial and retransmissions on PDSCH or PUSCH, when frequency hopping is enabled, the TB retransmissions are grouped first for frequency hopping, followed by the initial transmission of the TB on PDSCH or PUSCH, or Regarding the uplink control channel (UCI) multiplexed on the PUSCH, the UCI is divided equally into a first part and a second part, the first part is transmitted at the first hop, the second part is transmitted at the second hop, the retransmitted TB follows the UCI, and the initial transmission of the TB follows the retransmitted TB. This indicates.

[0172] Example Y17 includes one or more computer-readable media containing instructions, which, when executed by one or more processors, are sent to the user device (UE). A message is received from a next-generation NodeB (gNB), the message having configuration information including the number of transport blocks (TBs) for frequency hopping for data transmission related to the UE, the configuration information including an indication of a TB group containing the TBs, the configuration information indicating that the frequency hopping for data transmission is performed within the TB group, and the configuration information indicating that a first portion of a TB is transmitted at a first hop, a second portion of the TB is transmitted at a second hop, Based on the configuration information, the system is configured to receive or encode physical downlink shared channel (PUSCH) messages for transmission.

[0173] Example Y18 includes one or more computer-readable media of Example Y17 or other examples herein, wherein the configuration information is included in downlink control information (DCI), or the configuration information is received via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI), or dedicated radio resource control (RRC) signaling.

[0174] Example Y19 includes one or more computer-readable media of Example Y17 or other examples herein, wherein the configuration information includes a TB mapping sequence defined in a time-first, frequency-second manner.

[0175] Example Y20 includes one or more computer-readable media of Example Y17 or other examples herein, wherein the configuration information indicates that each dedicated demodulated reference signal (DMRS) symbol is assigned at each hop prior to the transmission of the first TB in the TB group.

[0176] Example Y21 includes one or more computer-readable media of Example Y17 or other examples herein, wherein the configuration information indicates that one or more TBs are mixed into a common symbol when frequency hopping is applied.

[0177] Example Y22 includes one or more computer-readable media of Example Y17 or other examples herein, wherein the configuration information indicates the number of symbols for hopping boundaries or the number of TBs in a TB group for frequency hopping, based on the time domain bundling size for hybrid automatic retransmission request-delivery acknowledgment (HARQ-ACK) feedback.

[0178] Example Y23 includes a computer-readable medium from any of Examples Y17 to Y24 or one or more of the other examples herein, and the configuration information is For mixed initial and retransmissions on PDSCH or PUSCH, when frequency hopping is enabled, the TB retransmissions are grouped first for frequency hopping, followed by the initial transmission of the TB on PDSCH or PUSCH, or Regarding the uplink control channel (UCI) multiplexed on the PUSCH, the UCI is divided equally into a first part and a second part, the first part is transmitted at the first hop, the second part is transmitted at the second hop, the retransmitted TB follows the UCI, and the initial transmission of the TB follows the retransmitted TB. This indicates.

[0179] Example Z01 may include an apparatus having means for performing one or more elements of any other method or process described herein, or any method described herein, or related to any of the methods described herein.

[0180] Example Z02 may include one or more non-temporary computer-readable media having instructions such that the instructions cause an electronic device to execute one or more elements of any of the methods described in or relating to any of Examples 1-Y24 or any other method or process described herein, upon execution of the instructions by one or more processors of the electronic device.

[0181] Example Z03 may include a device having logic, modules, or circuits that perform one or more elements of any of the methods or processes described herein, or any other methods or processes described herein.

[0182] Example Z04 may include methods, techniques, or processes described or related to any or part of Examples 1-Y24.

[0183] Example Z05 may include an apparatus having one or more processors and one or more computer-readable media having instructions, wherein when the instructions are executed by the one or more processors, the apparatus causes the one or more processors to execute a method, technique, or process, or part thereof, described in or related to any of Examples 1 to Y24.

[0184] Example Z06 may include signals described or related to any of Examples 1-Y24, or any part or portion thereof.

[0185] Example Z07 may include any or part of Examples 1-Y24, or any datagram, packet, frame, segment, protocol data unit (PDU), or message described in or relating to any other example described herein.

[0186] Example Z08 may include a signal that encodes data described in or relating to any of Examples 1-Y24, or any part or portion thereof, or otherwise described herein.

[0187] Example Z09 may include any or part of Examples 1-Y24, or a datagram, packet, frame, segment, protocol data unit (PDU), or message-encoded signal described in or relating to any of these.

[0188] Example Z10 may include an electromagnetic signal that carries a computer-readable instruction, the execution of the computer-readable instruction by one or more processors causing the one or more processors to perform any or part thereof of a method, technique, or process described in or related to any of Examples 1-Y24.

[0189] Example Z11 may include a computer program having instructions, wherein the execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any or part of Examples 1-Y24.

[0190] Example Z12 may include signals within the wireless network shown and described herein.

[0191] Example Z13 may include a method of communication within the wireless network shown and described herein.

[0192] Example Z14 may include a system that provides the wireless communication shown and described herein.

[0193] Example Z15 may include equipment that provides wireless communication as shown and described herein.

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

[0195] Abbreviation Unless otherwise used herein, terms, definitions, and abbreviations may correspond to those defined in 3GPP TR 21.905 v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may apply to the examples and embodiments described herein. 3GPP Third Generation Partnership Project 4G Fourth Generation 5G Fifth Generation 5GC 5G Core network AC Application Client ACK Acknowledgement Delivery Confirmation ACID Application Client Identification AF Application Function AM Acknowledged Mode (Acknowledged Response Mode) AMBR Aggregate Maximum Bit Rate AMF Access and Mobility Management Function AN Access Network ANR Automatic Neighbor Relation AP (Application Protocol) Antenna Port Access Point API Application Programming Interface APN Access Point Name ARP Allocation and Retention Priority ARQ Automatic Repeat Request Automatic repeat request AS Access Stratum Access Layer ASP Application Service Provider 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 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 CGF Charging Gateway Function CHF Charging Function CI Cell Identity Cell Identifier CID Cell-ID Cell ID (e.g., positioning method) CIM Common Information Model CIR Carrier-to-Interference Ratio CK 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 Cyclic Redundancy Check CRI Channel-State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI Cell RNTI CS Circuit Switched CSCF call session control function CSAR Cloud Service Archive CSI Channel-State Information CSI-IM CSI Interference Measurement CSI Interference Measurement CSI-RS CSI Reference Signal CSI reference signal CSI-RSRP CSI reference signal received power CSI reference signal received power CSI-RSRQ CSI reference signal received quality CSI reference signal received quality CSI-SINR CSI signal-to-noise and interference ratio CSMA Carrier Sense Multiple Access CSMA / CA CSMA with collision avoidance CSMA / Collision avoidance CSS Common Search Space Cell-specific search space CTF Charging Trigger Function 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 DNN Data Network Name DNAI Data Network Access Identifier 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 (GSM Evolution) EAS Edge Application Server EASID (Edge Application Server Identification) ECS Edge Configuration Server ECSP (Edge Computing Service Provider) EDN (Edge Data Network) EEC Edge Enabler Client EECID Edge Enabler Client Identification EES Edge Enabler Server EESID: Edge Enabler Server Identification EHE Edge Hosting Environment EGMF Exposure Governance Management Function EGPRS Enhanced GPRS EIR Equipment Identity Register ELaA (Enhanced Licensed Assisted Access) EM Element Manager eMBB Enhanced Mobile Broadband EMS Element Management System eNB evolved NodeB, E-UTRAN NodeB EN-DC E-UTRA-NR Dual Connectivity EPC Evolved Packet Core EPDCCH enhanced PDCCH, enhanced physical downlink control channel EPRE: Energy per resource element EPS Evolved Packet System EREG (Enable REG) - Extended REG, Extended Resource Element Group ETSI (European Telecommunications Standards Institute) ETWS Earthquake and Tsunami Warning System eUICC embedded UICC, embedded universal integrated circuit card E-UTRA Evolved UTRA Evolved UTRA E-UTRAN Evolved UTRAN Evolved UTRAN EV2X Enhanced V2X Enhanced V2X F1AP F1 Application Protocol F1 Application Protocol F1-C F1 Control plane interface F1 Control plane interface F1-U F1 User plane interface F1 User plane interface FACCH Fast Associated Control CHannel Fast Associated Control CHannel FACCH / F Fast Associated Control Channel / Full rate Fast Associated Control Channel / Full rate FACCH / H Fast Associated Control Channel / Half rate Fast Associated Control Channel / Half rate FACH Forward Access Channel Forward Access Channel FAUSCH Fast Uplink Signalling Channel Fast Uplink Signalling Channel FB Functional Block Functional Block FBI Feedback Information Feedback Information FCC Federal Communications Commission Federal Communications Commission FCCH Frequency Correction Channel Frequency Correction Channel FDD Frequency Division Duplex Frequency Division Duplex FDM Frequency Division Multiplex Frequency Division Multiplex FDMA Frequency Division Multiple Access Frequency Division Multiple Access FE Front End Front End FEC Forward Error Correction Forward Error Correction FFS For Further Study For Further Study FFT Fast Fourier Transformation Fast Fourier Transformation feLAA further enhanced Licensed Assisted Access further enhanced Licensed Assisted Access, further enhanced LAA FN Frame Number Frame Number FPGA Field-Programmable Gate Array Field-Programmable Gate Array FR Frequency Range Frequency Range FQDN Fully Qualified Domain Name Fully Qualified Domain Name G-RNTI GERAN Radio Network Temporary Identity GERAN Radio Network Temporary Identity GERAN GSM EDGE RAN GSM EDGE RAN, GSM EDGE Radio Access Network GGSN Gateway GPRS Support Node Gateway GPRS Support Node GLONASS GLObal’naya NAvigatsionnaya Sputnikovaya Sistema (English name: Global Navigation Satellite System) Global Navigation Satellite System gNB Next Generation NodeB Next Generation NodeB gNB-CU gNB-centralized unit, Next Generation NodeB centralized unit gNB centralized unit, Next Generation NodeB centralized unit gNB-DU gNB-distributed unit, Next Generation NodeB distributed unit gNB distributed unit, Next Generation NodeB distributed unit GNSS (Global Navigation Satellite System) GPRS General Packet Radio Service GPSI Generic Public Subscription Identifier GSM Global System for Mobile Communication 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 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 (Hypertext Transfer Protocol) HTTPS stands for Hypertext Transfer Protocol Secure (HTTPS is http / 1.1 over SSL, i.e., port 443). I-Block Information Block ICCID (Integrated Circuit Card Identification) IAB Integrated Access and Backhaul ICIC Inter-Cell Interference Coordination ID Identity, identifier identifier, identification 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 Interference Measurement Intermodulation IP Multimedia IMC IMS Credentials IMS Credentials IMEI (International Mobile Device 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 Security, Internet Protocol Security IP-CAN IP-Connectivity Access Network, IP Connectivity Access Network IP-M IP Multicast, IP Multicast IPv4 Internet Protocol Version 4, Internet Protocol Version 4 IPv6 Internet Protocol Version 6, Internet Protocol Version 6 IR Infrared, Infrared IS In Sync, In Sync (within synchronization) IRP Integration Reference Point, Integration Reference Point ISDN Integrated Services Digital Network, Integrated Services Digital Network ISIM IM Services Identity Module, IM Services Identity Module<000098>ISO International Organisation for Standardisation, International Organization for Standardization ISP Internet Service Provider, Internet Service Provider IWF Interworking-Function, Interworking Function I-WLAN Interworking WLAN, Interworking WLAN kB Kilobyte (1000 bytes). kbps kilo-bits per second, kilo-bits per second ​​​​KPI Key Performance Indicator KQI Key Quality Indicator KSI Key Set Identifier ksps (kilo-symbols per second) KVM (Kernel Virtual Machine) L1 Layer 1 (Physical Layer) L1-RSRP Layer 1 reference signal received power L2 Layer 2 (Data Link Layer) L3 Layer 3 (Network Layer) LAA Licensed Assisted Access LAN (Local Area Network) LADN (Local Area Data Network) LBT Listen Before Talk LCM (Life Cycle 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 Layered 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 Minimization of Drive Tests (MDT) ME Mobile Equipment MeNB master eNB 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 Centre MM Mobility Management MME Mobility Management Entity MN Master Node MNO Mobile Network Operator 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 Mobile station MSB (Most Significant Bit) MSC Mobile Switching Centre MSI Minimum System Information MCH Scheduling Information MSID Mobile Station Identifier MSIN Mobile Station Identification Number MSISDN Mobile Subscriber ISDN Number MT Mobile Termized, 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 MTC wake-up signal NACK Negative Acknowledgement NAI (Network Access Identifier) NAS Non-Access Stratum, Non-Access Stratum layer NCT Network Connectivity Topology NC-JT Non-Coherent Joint Transmission NEC Network Capability Exposure NE-DC NR-E-UTRA Dual Connectivity NEF Network Exposure Function NF Network Function NFP Network Forwarding Path NFPD Network Forwarding Path Descriptor NFV (Network Functions Virtualization) NFVI NFV Infrastructure NFV Infrastructure NFVO NFV orchestrator NFV orchestrator NG Next Generation, Next Gen Next Generation NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity 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 New Radio Neighbor Relations NRF NF Repository Function NRS Narrowband Reference Signal NS Network Service NSA Non-Standalone operation mode NSD Network Service Descriptor NSR Network Service Record NSSAI Network Slice Selection Assistance Information S-NNSAI Single-NSSAI Single NSSAI NSSF Network Slice Selection Function NW Network NWUS Narrowband wake-up signal, Narrowband WUS Narrowband Wake-up signal, Narrowband WUS NZP Non-Zero Power O&M Operation and Maintenance ODU2 Optical channel Data Unit - Type 2 OFDM (Orthogonal Frequency Division Multiplexing) OFDMA (Orthogonal Frequency Division Multiple Access) OOB: Out-of-band OOS: Out of Sync (out of synchronization) OPEX OPErating EXpense operating expenses 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 Primary Component Carrier, Primary CC P-CSCF Proxy CSCF Proxy CSCF 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 PDU Protocol Data Unit PEI Permanent Equipment Identifiers PFD Packet Flow Description P-GW PDN Gateway PHICH Physical hybrid-ARQ indicator channel PHY Physical layer PLMN Public Land Mobile Network PIN (Personal Identification Number) PM Performance Measurement Performance measurement PMI Precoding Matrix Indicator PNF (Physical Network Function) PNFD (Physical Network Function Descriptor) PNFR Physical Network Function Record POC PTT over Cellular PP, PTP (Point-to-Point) PPP (Point-to-Point Protocol) PRACH Physical RACH Physical RACH PRB Physical resource block PRG Physical resource block group ProSe Proximity Service, 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 PSSCH Physical Sidelink Shared Channel PSCell Primary SCel Primary SCell PSS Primary Synchronization Signal PSTN Public Switched Telephone Network PT-RS Phase-tracking reference signal Phase-tracking reference signal PTT Push-to-Talk PUCCH Physical Uplink Control Channel 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) RAB Radio Access Bearer Random Access Burst RACH Random Access Channel RADIUS Remote Authentication Dial-In User Service RAN Radio Access Network RAND: Random number (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 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 Delivery Confirmation Mode RLC UM RLC Unacknowledged Mode RLF Radio Link Failure RLM Radio Link Monitoring RLM-RS Reference Signal for RLM Reference signal for RLM RM Registration Management RMC Reference Measurement Channel RMSI Remaining MSI Remaining Minimum System Information RN Relay Node RNC Radio Network Controller RNL (Radio Network Layer) RNTI (Radio Network Temporary Identifier) ROHC Robust Header Compression RRC Radio Resource Control Radio Resource Control Layer RRM Radio Resource Management RS Reference Signal Reference signal RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality RSSI Received Signal Strength Indicator RSU Road Side Unit RSTD Reference Signal Time Difference RTP (Real Time Protocol) 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-CSCF serve CSCF serving CSCF S-GW Serving Gateway S-RNTI SRNC Radio Network Temporary Identity S-TMSI SAE Temporary Mobile Station Identifier SAE Temporary Mobile Station Identifier SA Standalone operation mode SAE System Architecture Evolution SAP Service Access Point SAPD Service Access Point Descriptor SAPI Service Access Point Identifier SCC Secondary Component Carrier, Secondary CC Secondary Component Carrier, Secondary CC Cell Secondary Cell SCEF Service Capability Exposure Function SC-FDMA (Single Carrier Frequency Division Multiple Access) SCG Secondary Cell Group SCM Security Context Management SCS Subcarrier Spacing SCTP Stream Control Transmission Protocol SDAP (Service Data Adaptation Protocol) Service Data Adaptation Protocol Layer SDL Supplementary Downlink SDNF (Structured Data Storage Network Function) SDP Session Description Protocol SDSF Structured Data Storage Function SDU Service Data Unit SEAF Security Anchor Function SeNB secondary eNB Secondary eNB SEPP Security Edge Protection Proxy SFI Slot Format Indication SFTD (Space-Frequency Time Diversity) SFN and frame timing difference SFN System Frame Number SGnB Secondary gNB Secondary gNB SGSN Serving GPRS Support Node S-GW Serving Gateway SI System Information SI-RNTI System Table RNTI System Information RNTI SIB System Information Block SIM Subscriber Identity Module SIP Session Initiation 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 SPS Semi-Persistent Scheduling SQN Sequence number SR Scheduling Request SRB Signaling Radio Bearer SRS Sounding Reference Signal SS Synchronization Signal Synchronization signal SSB Synchronization Signal Block SSID (Service Set Identifier) SS / PBCH Block SSBRI SS / PBCH Block SSBRI SS / PBCH Block Resource Indicator Synchronization Signal Block Resource Indicator SSC Session and Service Continuity SS-RSRP Synchronization Signal based Reference Signal Received Power SS-RSRQ Synchronization Signal based Reference Signal 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 TAI Tracking Area Identity 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 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 Quest User Device UDM Unified Data Management UDP User Datagram Protocol 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) UwPTS Uplink Pilot Time Slot V2I Vehicle-to-Infrastructure 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) VNF Forwarding Graph VNFFGD VNF Forwarding Graph Descriptor VNFM VNF Manager 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 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 exclusive OR ZC Zadoff-Chu ZP Zero Power

[0196] Technical terms For the purposes of this document, the following terms and definitions are applicable to the Ray and embodiments described herein.

[0197] As used herein, the term “circuit” refers to, is a part of, or includes, hardware components configured to provide the described functions, such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) and / or memory (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), composite PLDs (CPLDs), high-performance PLDs (HCPLDs), structured ASICs, or programmable SoCs), and digital signal processors (DSPs). In some embodiments, a circuit may provide at least some of the described functions by executing one or more software or firmware programs. The term “circuit” may also refer to a combination of one or more hardware elements with program code used to perform the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuit.

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

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

[0200] The terms “User Equipment” or “UE” as used herein refer to equipment with wireless communication capabilities and may represent a remote user of network resources within a communication network. The terms “User Equipment” or “UE” may be considered synonymous with, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile equipment, etc.

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

[0202] As used herein, the term “computer system” refers to any type of interconnected electronic equipment, computer equipment, or its components. The terms “computer system” and / or “system” may also refer to various components of a computer that are interconnected in a communicative manner. Furthermore, the terms “computer system” and / or “system” may refer to multiple computer devices and / or computing systems that are interconnected in a communicative manner and configured to share computing and / or networking resources.

[0203] As used herein, “appliance,” “computer appliance,” or similar terms refer to computer equipment or computer systems that have program code (e.g., software or firmware) specifically designed to provide particular computing resources. A “virtual appliance” is a virtual machine image implemented by a hypervisor-based device that virtualizes or emulates a computer appliance, or otherwise is dedicated to providing particular computing resources.

[0204] As used herein, the term “resource” refers to physical or virtual devices, physical or virtual components within a computing environment, and / or physical or virtual components within a specific piece of equipment, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operation, ports or network sockets, channel / link allocation, throughput, memory usage, storage, networks, databases and applications, workload units, and / or similar items. The term “hardware resource” may refer to computing resources, storage resources, and / or network resources provided by (one or more) physical hardware elements. “Virtualization resource” may refer to computing resources, storage resources, and / or network resources provided to applications, equipment, systems, etc., by a virtualization infrastructure. The term “network resource” or “communication resource” may refer to resources accessible by computer equipment / systems via a communication network. The term “system resource” may refer to any kind of shared entity for providing services, and may include computing resources and / or network resources. System resources may be considered as a set of coherent functions, network data objects, or services accessible via a server, and such system resources reside on a single host or on multiple hosts and are clearly identifiable.

[0205] As used herein, the term “channel” refers to any tangible or intangible transmission medium used to communicate data or data streams. The term “channel” may be synonymous and / or equivalent to any other similar term that describes a path or medium through which data is communicated, such as “communication channel,” “data communication channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radio frequency carrier,” and / or any other similar term.

[0206] The terms "instantiate," "instantiate," and similar terms used here refer to the creation of an instance. An "instance" can also refer to the concrete creation of an object, such as during the execution of program code.

[0207] The terms “joined” and “communicatively joined” are used herein, along with their derivatives. The term “joined” can mean that two or more elements are in direct physical or electrical contact with each other, that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or that one or more other elements are joined or connected between elements said to be joined together. The term “directly joined” can mean that two or more elements are in direct contact with each other. The term “communicatively joined” can mean that two or more elements can come into contact with each other by means of communication, including via wires or other interconnections, via wireless communication channels or links, and / or similar means.

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

[0209] The term "SMTC" refers to an SSB-based measurement timing configuration, which is comprised of SSB-MeasurementTimingConfiguration.

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

[0211] The term “primary cell” refers to an MCG cell operating on the primary frequency, within which the UE either performs the initial connection establishment procedure or initiates the connection reconstruction procedure.

[0212] The term "primary SCG cell" refers to an SCG cell in which the UE performs random access when reconfiguration is performed using a synchronous procedure for DC operation.

[0213] The term "secondary cell" refers to a cell that provides additional radio resources to a UE (Union Engine) configured with a CA (Carrier Aggregation), in addition to the special cell.

[0214] The term "secondary cell group" refers to a subset of serving cells that have a PSCell and zero or more secondary cells, in the context of a UE composed of DCs.

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

[0216] The term “serving cell” or “serving cells” refers to a set of cells that have (one or more) special cells and all secondary cells for a UE located in RRC_CONNECTED, which is configured with CA / .

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

Claims

1. It is a device, A memory that stores configuration information including the number of transport blocks (TBs) for frequency hopping for data transmission related to user equipment (UE), A processing circuit coupled to the memory, It has, The aforementioned processing circuit is The configuration information is retrieved from the memory, the configuration information includes an indication of a TB group including the TB, the configuration information indicates that the frequency hopping for data transmission is performed within the TB group, and the configuration information indicates that a first portion of a TB is transmitted at a first hop, and a second portion of the TB is transmitted at a second hop. A message containing the aforementioned configuration information is encoded for transmission to the UE. Device.

2. The apparatus according to claim 1, wherein the data transmission related to the UE is a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission.

3. The apparatus according to claim 1, wherein the configuration information in the message is included in downlink control information (DCI), or the message is encoded for transmission via minimal system information (MSI), remaining minimal system information (RMSI), other system information (OSI), or dedicated radio resource control (RRC) signaling.

4. The apparatus according to claim 1, wherein the configuration information includes a TB mapping sequence defined in a time-first, frequency-second manner.

5. The apparatus according to claim 1, wherein the configuration information indicates that a dedicated demodulation reference signal (DMRS) symbol is assigned to each hop prior to the transmission of the first TB in the TB group.

6. The apparatus according to claim 1, wherein the configuration information indicates that one or more TBs are mixed into a common symbol when frequency hopping is applied.

7. The apparatus according to claim 1, wherein the configuration information indicates the number of symbols for a hopping boundary or the number of TBs in a TB group for frequency hopping, based on the time domain bundling size for hybrid automatic retransmission request-delivery acknowledgment (HARQ-ACK) feedback.

8. The aforementioned configuration information is, With respect to mixed initial and retransmissions on a PDSCH or PUSCH, when frequency hopping is enabled, the retransmissions of the TB are grouped first for frequency hopping, followed by the initial transmission of the TB on the PDSCH or PUSCH, or Regarding the uplink control channel (UCI) multiplexed on the PUSCH, the UCI is divided equally into a first part and a second part, the first part is transmitted at the first hop, the second part is transmitted at the second hop, the retransmitted TB follows the UCI, and the initial transmission of the TB follows the retransmitted TB. The apparatus according to any one of claims 1 to 7, which shows the following.

9. One or more computer-readable storage media storing instructions, wherein, when the instructions are executed by one or more processors, they are sent to a next-generation NodeB (gNB), The configuration information is determined, including the number of transport blocks (TBs) for frequency hopping for data transmission related to a user device (UE), the configuration information includes an indication of a TB group containing the TBs, the configuration information indicates that the frequency hopping for data transmission is performed within the TB group, and the configuration information indicates that a first portion of a TB is transmitted at a first hop, a second portion of the TB is transmitted at a second hop, The message containing the aforementioned configuration information is encoded for transmission to the UE. One or more computer-readable storage media.

10. The data transmission related to the UE is a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission, one or more computer-readable storage media according to claim 9.

11. The configuration information in the message is included in downlink control information (DCI), or the message is encoded for transmission via minimal system information (MSI), remaining minimal system information (RMSI), other system information (OSI), or dedicated radio resource control (RRC) signaling, one or more computer-readable storage media according to claim 9.

12. The configuration information includes a TB mapping sequence defined in a time-first, frequency-second manner, for one or more computer-readable storage media according to claim 9.

13. The configuration information indicates that a dedicated demodulation reference signal (DMRS) symbol is assigned to each hop prior to the transmission of the first TB in the TB group, one or more computer-readable storage media according to claim 9.

14. The configuration information indicates that when frequency hopping is applied, one or more TBs are mixed into a common symbol, as per claim 9, one or more computer-readable storage media.

15. The configuration information is one or more computer-readable storage media according to claim 9, which indicate the number of symbols for a hopping boundary or the number of TBs in a TB group for frequency hopping, based on the time domain bundling size for hybrid automatic retransmission request-delivery acknowledgment (HARQ-ACK) feedback.

16. The aforementioned configuration information is, With respect to mixed initial and retransmissions on a PDSCH or PUSCH, when frequency hopping is enabled, the retransmissions of the TB are grouped first for frequency hopping, followed by the initial transmission of the TB on the PDSCH or PUSCH, or Regarding the uplink control channel (UCI) multiplexed on the PUSCH, the UCI is divided equally into a first part and a second part, the first part is transmitted at the first hop, the second part is transmitted at the second hop, the retransmitted TB follows the UCI, and the initial transmission of the TB follows the retransmitted TB. One or more computer-readable storage media according to any one of claims 9 to 15, wherein the media are shown.

17. One or more computer-readable storage media storing instructions, wherein, when the instructions are executed by one or more processors, the user device (UE) A message is received from a next-generation NodeB (gNB), the message having configuration information including the number of transport blocks (TBs) for frequency hopping for data transmission related to the UE, the configuration information including an indication of a TB group including the TBs, the configuration information indicating that the frequency hopping for data transmission is performed within the TB group, and the configuration information indicating that a first portion of a TB is transmitted at a first hop, a second portion of the TB is transmitted at a second hop, Based on the aforementioned configuration information, receive or encode physical uplink shared channel (PUSCH) messages for transmission. One or more computer-readable storage media.

18. The configuration information is included in downlink control information (DCI), or the configuration information is received via minimum system information (MSI), remaining minimum system information (RMSI), other system information (OSI), or dedicated radio resource control (RRC) signaling, one or more computer-readable storage media according to claim 17.

19. The configuration information includes a TB mapping sequence defined in a time-first, frequency-second manner, for one or more computer-readable storage media according to claim 17.

20. The configuration information indicates that a dedicated demodulation reference signal (DMRS) symbol is assigned to each hop prior to the transmission of the first TB in the TB group, one or more computer-readable storage media according to claim 17.

21. The configuration information indicates that one or more TBs are mixed into a common symbol when frequency hopping is applied, one or more computer-readable storage media according to claim 17.

22. The configuration information is one or more computer-readable storage media according to claim 17, which indicate the number of symbols for a hopping boundary or the number of TBs in a TB group for frequency hopping, based on the time domain bundling size for hybrid automatic retransmission request-delivery acknowledgment (HARQ-ACK) feedback.

23. The aforementioned configuration information is, With respect to mixed initial and retransmissions on a PDSCH or PUSCH, when frequency hopping is enabled, the retransmissions of the TB are grouped first for frequency hopping, followed by the initial transmission of the TB on the PDSCH or PUSCH, or Regarding the uplink control channel (UCI) multiplexed on the PUSCH, the UCI is divided equally into a first part and a second part, the first part is transmitted at the first hop, the second part is transmitted at the second hop, the retransmitted TB follows the UCI, and the initial transmission of the TB follows the retransmitted TB. One or more computer-readable storage media according to any one of claims 17 to 22, wherein the media are shown.

Images