Mobile communication methods

Abstract

This disclosure provides a mobile communication method. The mobile communication method includes a processor of the device determining whether a capability is enabled; if the capability is enabled, the processor applying scheduling restrictions to K symbols preceding a Synchronization Signal Block (SSB) symbol and K symbols following the SSB symbol; and the processor transmitting uplink symbols other than those with scheduling restrictions or receiving downlink symbols other than those with scheduling restrictions, wherein the K symbols are greater than one symbol. The mobile communication method of this disclosure can achieve better performance in high-frequency bands.

Description

[0001] Cross-referencing of related applications

[0002] This invention claims priority to U.S. Provisional Patent Application No. 63 / 297,249, filed January 7, 2022, and U.S. Provisional Patent Application No. 63 / 297,269, filed January 7, 2022. The contents of the above applications are incorporated herein by reference. [Technical Field]

[0003] This disclosure generally relates to mobile communications, and more specifically to scheduling restrictions for user equipment and network devices in mobile communications with high subcarrier spacing (SCS). [Background Technology]

[0004] Unless otherwise stated herein, the methods described in this section are not prior art to the appended claims and are not admitted as prior art by virtue of their inclusion in this section.

[0005] In New Radio (NR), higher frequency bands are supported for higher data throughput or new applications. For example, higher frequency bands may include Frequency Range 2 (FR2), which encompasses the band from 24.25 GHz to 71.0 GHz. In some even higher bands, such as 60 GHz to 70 GHz (i.e., Frequency Range 2-2), higher SCS (Sequential Channel Counter) is supported to overcome phase noise. Higher SCS may include 120 kHz, 480 kHz, or 960 kHz. Higher SCS can be used for synchronization signal block (SSB) symbol data symbols.

[0006] Traditionally, strict synchronization between cells is required, coverage areas are small, and interference should be avoided. However, timing differences between cells can affect more symbols at higher SCS (Simultaneous Cross-Sectional Values). Several factors can cause timing differences. For example, timing alignment errors (TAEs) can occur between different cells / base stations. Timing differences received by the UE can reach several symbols and may lead to data reception conflicts.

[0007] Therefore, avoiding / reducing interference in higher frequency bands with higher SCS has become a crucial issue for high-frequency transmission in newly developed wireless communication networks. Consequently, appropriate solutions are needed to improve data reception and achieve better performance in high-frequency bands. [Summary of the Invention]

[0008] The following overview is illustrative only and is not intended to be limiting in any way. That is, it is provided to introduce the concepts, highlights, benefits, and advantages of the novel and non-obvious techniques described herein. Choices, but not all, of implementations are further described in the detailed description below. Therefore, the following overview is not intended to identify the essential characteristics of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0009] Some embodiments of this disclosure provide a mobile communication method, including a processor of a device determining whether a capability is enabled; if the capability is enabled, the processor applying scheduling restrictions to K symbols preceding a synchronization signal block (SSB) symbol and K symbols following the SSB symbol; and the processor transmitting uplink symbols other than those with scheduling restrictions or receiving downlink symbols other than those with scheduling restrictions, wherein the K symbols are greater than 1 symbol.

[0010] Some embodiments of this disclosure also provide a mobile communication method, including: transmitting uplink timing accuracy capability from a processor of a device to a network node; receiving an instruction to enable scheduling restrictions from the network node by the processor; determining at least one uplink time slot based on a time slot configuration from the network node; applying the scheduling restrictions to at least one symbol within the uplink time slot if the scheduling restrictions are enabled; and transmitting the uplink symbol outside the symbol with the scheduling restrictions.

[0011] Some embodiments of this disclosure also provide a mobile communication method, including: enabling a capability by a processor of a network node to a user equipment (UE); when the capability is enabled, applying scheduling restrictions to K symbols preceding a synchronization signal block (SSB) symbol and K symbols following the SSB symbol; and transmitting downlink symbols other than the symbols with the scheduling restrictions or receiving uplink symbols other than the symbols with the scheduling restrictions by the processor, wherein the K symbols are greater than 1 symbol.

[0012] The mobile communication method disclosed herein can achieve better performance in the high-frequency band. [Attached Image Description]

[0013] The accompanying drawings are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure. It will be understood that the drawings are not necessarily drawn to scale, as in actual implementations, some components may be shown out of proportion to clearly illustrate the concepts of the present disclosure.

[0014] Figure 1-7 The illustrations depict various example scenarios under the schemes of embodiments according to this disclosure.

[0015] Figure 8 An example communication system having an example communication device and an example network device according to an embodiment of the present disclosure is illustrated.

[0016] Figure 9-11 The illustrations depict various example processes according to embodiments of the present disclosure.

Detailed Implementation Methods

[0017] This document discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which can be embodied in various forms. This disclosure may be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that the description of this disclosure is thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0018] Overview

[0019] Embodiments of this disclosure relate to various techniques, methods, schemes, and / or solutions related to scheduling limitations with higher SCS for user equipment and network devices in mobile communications. According to the invention, multiple possible schemes can be implemented individually or in combination. That is, while these possible solutions may be described individually below, two or more of these possible solutions may be implemented in one or another combination.

[0020] In New Radio (NR), higher frequency bands are supported to achieve higher data throughput and new applications. For example, higher frequency bands may include Frequency Range 2 (FR2), which encompasses a band from 24.25 GHz to 71.0 GHz. In some even higher bands, such as 60 GHz to 70 GHz (i.e., Frequency Range 2-2), higher SCS (Sequential Signal Block) is supported to overcome phase noise. Higher SCS may include 120 kHz, 480 kHz, or 960 kHz. Higher SCS can be used for both Synchronization Signal Block (SSB) symbols and data symbols.

[0021] Traditionally, strict synchronization between cells is required, coverage areas are small, and interference should be avoided. However, timing differences between cells can affect more symbols with higher SCS. Figure 1An example scenario 100 under an embodiment of this disclosure is illustrated. Scenario 100 involves at least one UE and multiple network nodes, which may be part of a wireless communication network (e.g., an LTE network, a 5G network, an NR network, an IoT network, or a 6G network). Figure 1 As shown, each cell can schedule data symbols (e.g., symbols 6-8) and synchronization signal block (SSB) symbols (e.g., symbols 2-5). Timing differences may occur between the first cell / network node (e.g., cell #1) and the second cell / network node (e.g., cell #2). When the time slots / symbols from cell #1 and cell #2 are out of sync, the UE cannot receive data symbols that overlap with the SSB symbols.

[0022] Several factors can cause timing discrepancies. For example, timing alignment errors can occur between different cells / base stations. Since a cell phase synchronization accuracy of 3 microseconds (μs) is defined and unchanged, the time interval between cells (TAE) can be as high as 3μs, which is almost 3 symbols for a higher SCS of 960kHz. Therefore, the timing discrepancy received by the UE can reach several symbols and may lead to data reception conflicts.

[0023] In another example, the UE can apply different receive (RX) beams for the SSB and data. While the UE needs to measure the SSB of cell #1, it cannot receive date symbols (e.g., symbols 6-8 of cell #2). It also needs to consider RX beam switching. The UE will need additional time to switch its RX beam. For example, after measuring the SSB, the UE needs to switch its RX beam to receive data symbols. UE RX beam switching may take several symbols. Therefore, the UE cannot receive data symbols immediately after the SSB symbol.

[0024] In another example, propagation delays between cells can also cause timing differences at the UE. Typically, different cells / base stations do not coexist in the same area. The propagation paths of different cell base stations may differ. This can lead to different arrival times at the UE, resulting in timing differences at the UE.

[0025] In view of this, this disclosure proposes several schemes related to scheduling constraints for user equipment and network equipment in mobile communications, specifically addressing higher SCS (Search Counterscore). According to the schemes of this disclosure, scheduling constraints can be introduced to resolve the aforementioned timing discrepancies. Scheduling constraints can also be considered as uplink (UL) transmission gaps or downlink (DL) reception gaps. During UL transmission gaps, UE transmission of UL symbols is not permitted or expected. During DL reception gaps, UE reception of DL symbols is not permitted or expected. The length / duration of the scheduling constraint can be determined based on the SCS. After determining the scheduling constraint, the UE can apply it to SSB symbols, symbols preceding SSB symbols, or symbols following SSB symbols. Therefore, the UE may have sufficient time to perform measurements (e.g., reference signal / SSB measurements) and switch RX beams. Scheduling conflicts between different cells due to timing discrepancies can also be resolved. Therefore, UE measurement processes and mobility performance in higher frequency bands / higher SCS (e.g., FR2-2) can be ensured.

[0026] Specifically, the UE can be configured to determine whether a capability is enabled. This capability can be enabled by a parameter / indicator (e.g., deriveSSB-IndexFromCell) in higher-layer signaling configured by the network node. The parameter / indicator deriveSSB-IndexFromCell can indicate whether the UE can derive the index of an SSB transmitted by a neighboring cell using the serving cell timing. If this field is enabled (e.g., set to true), the UE can assume that the system frame number (SFN) and the frame boundaries across cells on the serving frequency are aligned within a certain tolerance (e.g., two orthogonal frequency division multiplexing (OFDM) symbols). Higher-layer signaling may include radio resource control (RRC) signaling.

[0027] In some implementations, the UE can determine whether the capability is enabled when operating in licensed bands within a higher frequency band (e.g., FR2-2). For example, the UE can assume that the parameter / indicator deriveSSB_IndexFromCell is always enabled for licensed bands within a higher frequency band (e.g., FR2-2). In some implementations, the UE can determine whether the parameter / indicator deriveSSB_IndexFromCell is enabled based on the SCS and whether the operating band is operating within a licensed band. For example, the UE can consider enabling deriveSSB_IndexFromCell for a 120 kHz SCS within a licensed band.

[0028] When the parameter / indicator `deriveSSB_IndexFromCell` is enabled, the UE can determine which symbols can be scheduled (i.e., have scheduling availability) or which symbols cannot be scheduled (i.e., have scheduling restrictions). Scheduling availability means that the UE is allowed or expected to transmit UL symbols or receive DL symbols. Scheduling restrictions mean that the UE is not allowed or expected to transmit UL symbols or receive DL symbols. Specifically, with the parameter / indicator `deriveSSB_IndexFromCell` enabled, the UE can be configured to determine K symbols for scheduling restrictions. The UE can then apply scheduling restrictions to at least one of the SSB symbols, the K symbols preceding the SSB symbols, and the K symbols following the SSB symbols. After applying the scheduling restrictions, the UE can be configured to transmit UL symbols or receive DL symbols outside of the symbols with scheduling restrictions.

[0029] The UE can determine the number of K symbols based on the SCS. The SCS can include at least one of 480kHz and 960kHz. The K symbols can be greater than one symbol. For example, for data symbols in a 480kHz SCS, the K symbols are greater than or equal to two symbols, and for data symbols in a 960kHz SCS, the K symbols are greater than or equal to three symbols. The UE ignores or skips scheduling within symbols with scheduling restrictions.

[0030] When the parameter / indicator `deriveSSB_IndexFromCell` is not enabled, the UE can apply scheduling restrictions to all symbols within the SSB-based Radio Resource Management (RRM) Measurement Timing Configuration (SMTC) window. The UE can apply scheduling availability to symbols outside the SMTC window. After applying scheduling restrictions, the UE can be configured to transmit UL symbols or receive DL symbols outside of the symbols with scheduling restrictions.

[0031] In some implementations, the UL symbol may include at least one of the Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), and Sounding Reference Signal (SRS). The DL symbol may include the Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Tracking Reference Signal (TRS), and Channel State Information-Reference Signal (CSI-RS) for Channel Quality Indicator (CQI). Therefore, if deriveSSB-IndexFromCell is enabled, and the UE is not expected to transmit PUCCH / PUSCH / SRS or receive PDCCH / PDSCH / TRS / CSI-RS for CQI on the K data symbols preceding and following each consecutive SSB symbol to be measured, on the SSB symbol to be measured, and outside the SMTC window duration. Scheduling constraints are applied to the measurement of synchronization signal-reference signal received power (SS-RSRP) or synchronization signal-signal to interference plus noise ratio (SS-SINR) on cells within frequency range 2 (FR2).

[0032] In some implementations, the values ​​of the K symbols can be predetermined or pre-stored in the UE based on the SCS. For example, for a serving cell with a 120kHz SCS data symbol, K = 1. For a serving cell with a 480kHz SCS data symbol and an SSB symbol with a 120kHz or 480kHz SCS, K = 4. For a serving cell with a 480kHz SCS data symbol and an SSB symbol with a 960kHz SCS, K = 3. For a serving cell with a 960kHz SCS data symbol and an SSB symbol with a 120kHz or 480kHz SCS, K = 7. For a serving cell with a 960kHz SCS data symbol and an SSB symbol with a 960kHz SCS, K = 4.

[0033] In some implementations, the values ​​of the K symbols can be predetermined or pre-stored in the UE based on the SCS of the target cell. For example, for an FR2-1 intra-frequency cell or an FR2-2 intra-frequency cell with 120kHz SCS data symbols, K = 1. For an FR2-2 intra-frequency cell with 480kHz SCS data symbols, K = 2. For an FR2-2 intra-frequency cell with 960kHz SCS data symbols, K = 3.

[0034] On the other hand, the same scheduling restrictions described above can also be applied on the network side. Specifically, network nodes (e.g., gNBs or base stations) can be configured to enable the UE's capability. The network node can enable this capability via higher-layer signaling (e.g., RRC signaling) through parameters / indicators (e.g., deriveSSB-IndexFromCell). The network node can use the parameter / indicator deriveSSB-IndexFromCell to indicate to the UE whether it can utilize the serving cell timing to derive the index of the SSB transmitted by neighboring cells. When operating in licensed frequency bands within frequency range 2-2 (FR2-2), the network node can be configured to enable this capability.

[0035] With the parameter / indicator `deriveSSB_IndexFromCell` enabled, a network node can determine which symbols can be scheduled (i.e., have scheduling availability) or which symbols cannot be scheduled (i.e., have scheduling restrictions). Scheduling availability means the network node can schedule UL or DL ​​symbols. Scheduling restrictions mean the network node should not schedule UL or DL ​​symbols. After enabling this capability, a network node can be configured to determine K symbols for scheduling restrictions. The network node can then apply scheduling restrictions to at least one of the SSB symbol, the K symbols preceding the SSB symbol, and the K symbols following the SSB symbol. The network node can determine the number of K symbols based on the SCS. The SCS can include at least one of 480kHz and 960kHz. After applying the scheduling restrictions, the network node can be configured to transmit DL symbols or receive UL symbols outside of the symbols with scheduling restrictions.

[0036] Network nodes can determine the number of K symbols based on the SCS. The SCS can include at least one of 480kHz and 960kHz. The K symbols can be greater than one symbol. For example, for data symbols with a 480kHz SCS, the K symbols are greater than or equal to two symbols, and for data symbols with a 960kHz SCS, the K symbols are greater than or equal to three symbols. Network nodes should not schedule DL or UL transmissions within symbols with scheduling restrictions.

[0037] Figure 2An example scenario 200 is illustrated under an embodiment of the present disclosure. Scenario 200 involves a UE and a network node, which may be part of a wireless communication network (e.g., an LTE network, a 5G network, an NR network, an IoT network, or a 6G network). In scenario 200, the network node (e.g., serving cell #1) operates at a 480kHz SCS for data symbols or SSB symbols. With the parameter deriveSSB-IndexFromCell enabled, the UE can be configured to determine K=4 based on the 480kHz SCS. The UE can then apply scheduling constraints to the SSB symbols (e.g., symbols #2 to #5), the four symbols preceding the SSB symbols (e.g., symbols #12 to #1 in the last time slot), and the four symbols following the SSB symbols (e.g., symbols #6 to #9). The UE is not expected to transmit PUCCH / PUSCH / SRS or receive PDCCH / PDSCH / TRS / CSI-RS for CQI on the SSB symbol to be measured, or on the four data symbols preceding and following each consecutive SSB symbol to be measured, during the SMTC window duration. If symbol #6 is scheduled to the UE, the UE can be configured to ignore the scheduling and skip symbol #6 for data transmission or reception. For symbols outside the scheduling constraints (e.g., symbols #10 to #13), the UE is able to transmit UL symbols or receive DL symbols.

[0038] Figure 3An example scenario 300 is illustrated under an embodiment of the present disclosure. Scenario 300 involves a UE and a network node, which may be part of a wireless communication network (e.g., an LTE network, a 5G network, an NR network, an IoT network, or a 6G network). In scenario 300, the network node (e.g., serving cell #1) operates at a 960kHz SCS for data symbols or SSB symbols. With the parameter deriveSSB-IndexFromCell enabled, the UE can be configured to determine K=7 based on the 960kHz SCS. The UE can then apply scheduling constraints to the SSB symbols (e.g., symbols #2 to #5), the seven symbols preceding the SSB symbols (e.g., symbols #9 to #1 from the previous time slot), and the seven symbols following the SSB symbols (e.g., symbols #6 to #12). If the UE is not expected to be within the SMTC window duration, it will transmit PUCCH / PUSCH / SRS or receive PDCCH / PDSCH / TRS / CSI-RS for CQI on the SSB symbols to be measured, the 7 data symbols preceding each consecutive SSB symbol to be measured, and the 7 data symbols following each consecutive SSB symbol to be measured. If any symbol within the scheduling constraints is scheduled to the UE, the UE can be configured to ignore the scheduling and skip the symbols used for data transmission or reception. For symbols outside the scheduling constraints (e.g., symbol #13), the UE is able to transmit UL symbols or receive DL symbols.

[0039] Figure 4 The illustration shows an example scenario 400 under an embodiment of this disclosure. Scenario 400 involves a UE and a network node, which may be part of a wireless communication network (e.g., an LTE network, a 5G network, an NR network, an IoT network, or a 6G network). In scenario 400, the network node (e.g., serving cell #1) operates at 960kHz SCS for data symbols or SSB symbols. With the parameter `deriveSSB-IndexFromCell` not enabled, the UE can be configured to apply scheduling restrictions to all symbols within the SMTC window. The UE is not expected to transmit PUCCH / PUSCH / SRS or receive PDCCH / PDSCH / TRS / CSI-RS for CQI during the duration of the SMTC window. If any symbol within the SMTC window is scheduled to the UE, the UE can be configured to ignore the scheduling and skip the symbol for data transmission or reception. For symbols outside the SMTC window, the UE is able to transmit UL symbols or receive DL symbols.

[0040] On the other hand, when operating in higher frequency bands (e.g., FR2-2) with higher SCS (e.g., 480kHz or 960kHz), UE UL transmit timing accuracy becomes very challenging. Inaccurate uplink timing can interfere with uplink reception at network nodes. For example, Figure 5 An example scenario 500 is illustrated under an embodiment of this disclosure. Scenario 500 involves at least one of multiple UEs and network nodes, which may be part of a wireless communication network (e.g., an LTE network, a 5G network, an NR network, an IoT network, or a 6G network). Ideally, UL timing is accurate, and slot / symbol boundaries are aligned or within tolerable limits. However, in real-world scenarios, UL timing may be delayed or interfered with. For higher frequency bands with higher SCS, symbol / slot lengths are often short. Timing errors may exceed the cyclic prefix (CP) of higher SCS. UL symbols may overlap, causing interference. For example, symbol #0 may cause UL interference to symbol #1. Therefore, solutions are needed to address the aforementioned timing inaccuracies.

[0041] Given the above, the UE needs to communicate with the network to align with its capabilities in terms of UL timing accuracy. If the UE cannot support accurate timing, at least one of the following methods can be applied. For example, some UL scheduling restrictions can be applied to certain symbols. Alternatively, the UE can be configured to meet relaxed accuracy requirements. Otherwise, the UE can transmit UL symbols only on component carriers configured with a 120kHz SCS. Therefore, UL interference to UL transmissions with higher SCS can be reduced / avoided.

[0042] Specifically, the UE can be configured to send uplink timing accuracy capability to the network node. The uplink timing accuracy capability can indicate a supported set of timing accuracies or a set of unsupported timing accuracies. For example, the uplink timing accuracy capability can indicate a supported SCS or an unsupported SCS. The UE can then receive an indication to enable scheduling restrictions from the network node. The UE can determine at least one uplink time slot based on the time slot configuration from the network node. With scheduling restrictions enabled, the UE can apply scheduling restrictions to at least one symbol within the uplink time slot. The UE can transmit uplink symbols outside of the symbols with scheduling restrictions. Scheduling restrictions can include uptransmitting at least one uplink symbol not in the first symbol of the uplink time slot and not in the last symbol of the uplink time slot. The uplink time slot can be a single time slot or multiple consecutive time slots.

[0043] Figure 6Example scenarios 601, 602, and 603 under embodiments of this disclosure are illustrated. Scenarios 601, 602, and 603 involve a UE and a network node, which may be part of a wireless communication network (e.g., an LTE network, a 5G network, an NR network, an IoT network, or a 6G network). Typically, additional UL scheduling restrictions may be applied to certain symbols for a higher SCS. For example, certain UL symbols with UL scheduling restrictions may be the first or last UL symbol in a scheduled time slot.

[0044] In scenario 601, scheduling restrictions are applied to the first UL symbol (e.g., symbol #0) and the last UL symbol (e.g., symbol #13) in a scheduled UL timeslot. The first and last symbols of the timeslot may not be scheduled for UL transmission. UEs are not allowed to transmit PUCCH / PUSCH / SRS on symbols #0 and #13. UEs can be configured to transmit PUCCH / PUSCH / SRS on symbols #1 through #12.

[0045] In scenario 602, scheduling restrictions are applied to the last UL symbol in a scheduled UL timeslot (e.g., symbol #13). The last symbol of the timeslot may not be scheduled for UL transmission. The UE is not allowed to transmit PUCCH / PUSCH / SRS on symbol #13. The UE can be configured to transmit PUCCH / PUSCH / SRS on symbols #0 through #12.

[0046] In scenario 603, scheduling restrictions are applied to the first UL symbol (e.g., symbol #0) in a scheduled UL timeslot. The first symbol of the timeslot may not be scheduled for UL transmission. The UE is not allowed to transmit PUCCH / PUSCH / SRS on symbol #0. The UE can be configured to transmit PUCCH / PUSCH / SRS on symbols #1 through #13.

[0047] In some implementations, the UE can be configured to signal to the network node the UL timing accuracy capabilities (e.g., SCS) that it can or cannot support. The network node can be configured to confirm whether UL scheduling restrictions are applied. The UE can receive a slot configuration as a DDDDU (i.e., slots 1 through 4 are DL and slot 5 is UL). The UE can be configured to transmit PUCCH / PUSCH / SRS on symbols 2 through 13 of slot 5.

[0048] Figure 7The illustrations depict example scenarios 701, 702, and 703 under embodiments of this disclosure. Scenarios 701, 702, and 703 involve a UE and a network node, which may be part of a wireless communication network (e.g., an LTE network, a 5G network, an NR network, an IoT network, or a 6G network). Typically, additional UL scheduling restrictions can be applied to certain symbols of consecutive UL slots with higher SCS. For example, certain UL symbols with UL scheduling restrictions may be the first UL symbol of the first uplink slot of consecutively scheduled UL slots or the last UL symbol of the last slot.

[0049] In scenario 701, n+1 time slots (e.g., UL time slots #0 to #n) are scheduled as UL time slots. Scheduling restrictions apply to the first UL symbol (e.g., symbol #0) of the first time slot (e.g., UL time slot #0) and the last UL symbol (e.g., symbol #13) of the last time slot (e.g., UL time slot #n). The first and last symbols of consecutive time slots may not be scheduled for UL transmission. The UE is not allowed to transmit PUCCH / PUSCH / SRS on symbol #0 of time slot #0 and symbol #13 of time slot #n. The UE can be configured to transmit PUCCH / PUSCH / SRS on symbols #1 to #13 of time slot #0, symbols #0 to #13 of time slots #1 to #n-1, and symbols #0 to #12 of time slot #n.

[0050] In scenario 702, n+1 time slots (e.g., UL time slots #0 to #n) are scheduled as UL time slots. Scheduling restrictions apply to the last UL symbol (e.g., symbol #13) of the last time slot (e.g., UL time slot #n). The last symbol of consecutive time slots may not be scheduled for UL transmission. The UE is not allowed to transmit PUCCH / PUSCH / SRS on symbol #13 of time slot #n. The UE can be configured to transmit PUCCH / PUSCH / SRS on symbols #0 to #13 of time slots #0 to #n-1 and symbols #0 to #12 of time slot #n.

[0051] In scenario 703, n+1 time slots (e.g., UL time slots #0 to #n) are scheduled as UL time slots. Scheduling restrictions apply to the first UL symbol (e.g., symbol #0) of the first time slot (e.g., UL time slot #0). The first symbol of consecutive time slots may not be scheduled for UL transmission. The UE is not allowed to transmit PUCCH / PUSCH / SRS on symbol #0 of time slot #0. The UE can be configured to transmit PUCCH / PUSCH / SRS on symbols #1 to #13 of time slot #0 and symbols #0 to #13 of time slots #1 to #n.

[0052] In some implementations, the UE can be configured to signal to the network node the UL timing accuracy capabilities (e.g., SCS) that it can or cannot support. The network node can be configured to confirm whether UL scheduling restrictions are applied. The UE can receive a time slot configuration as DDDUU (i.e., time slots 1-3 are DL and time slots 4-5 are UL). The UE can be configured to transmit PUCCH / PUSCH / SRS on symbols 2-14 of time slot 4 and symbols 1-13 of time slot 5.

[0053] Explanatory implementation

[0054] Figure 8 An example communication system 800 with an example communication device 810 and an example network device 820 according to an embodiment of the present disclosure is illustrated. Each of the communication device 810 and the network device 820 can perform various functions to implement the schemes, techniques, processes, and methods described herein regarding scheduling constraints of user equipment and network devices in mobile communications, including the scenarios / schemes described above and the processes 900, 1000, and 1100 described below.

[0055] The communication device 810 may be part of an electronic device, which may be a UE such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 810 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet, laptop, or notebook computer. The communication device 810 may also be part of a machine-type device, which may be an IoT, NB-IoT, or IIoT device, such as a stationary or fixed device, a home appliance, a wired communication device, or a computing device. For example, the communication device 810 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, the communication device 810 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more Reduced Instruction Set Computing (RISC) processors, or one or more Complex Instruction Set Computing (CISC) processors. The communication device 810 may include... Figure 8 At least some of the components shown, such as processor 812. Communication device 810 may also include one or more other components unrelated to the proposed embodiments of this disclosure (e.g., internal power supply, display device, and / or user interface device), and therefore, none of such one or more components of communication device 810 are included in... Figure 8 As shown in the figure, for the sake of simplicity, it will not be described further below.

[0056] Network device 820 may be part of an electronic device, such as a network node including a base station, small cell, router, or gateway. For example, network device 820 may be implemented in an eNodeB in an LTE, LTE-Advanced, or LTE-Advanced Pro network, or in a gNB in ​​a 5G, NR, IoT, NB-IoT, or IIoT network. Alternatively, network device 820 may be implemented as one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network device 820 may include... Figure 8 At least some of the components shown, such as processor 822. Network device 820 may also include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the proposed embodiments of this disclosure, and therefore, none of such one or more components of network device 820 are included in... Figure 8 As shown in the figure, for the sake of simplicity, it will not be described further below.

[0057] In one aspect, each of processors 812 and 822 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even though the singular term "processor" is used herein to refer to processors 812 and 822, according to the invention, each of processors 812 and 822 may include multiple processors in some implementations and a single processor in other implementations. In another aspect, each of processors 812 and 822 may be implemented as hardware (and optionally, firmware) having electronic components, including, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more transformers, configured and arranged to achieve a specific purpose according to the present disclosure. In other words, in at least some implementations, each of processors 812 and 822 is a dedicated machine specifically designed, arranged, and configured to perform a specific task, including autonomous reliability enhancements in the device (e.g., as represented by communication device 810) and networks according to various embodiments of the present disclosure (e.g., as represented by network device 820).

[0058] In some embodiments, the communication device 810 may further include a transceiver 816 coupled to the processor 812 and capable of wirelessly transmitting and receiving data. In some embodiments, the communication device 810 may further include a memory 814 coupled to the processor 812, accessible by the processor 812, and capable of storing data therein. In some embodiments, the network device 820 may further include a transceiver 826 coupled to the processor 822 and capable of wirelessly transmitting and receiving data. In some embodiments, the network device 820 may further include a memory 824 coupled to the processor 822, accessible by the processor 822, and capable of storing data therein. Therefore, the communication device 810 and the network device 820 may wirelessly communicate with each other via transceiver 816 and transceiver 826, respectively. To aid in better understanding, the following description of the operation, functions, and capabilities of each of the communication device 810 and the network device 820 is provided in the context of a mobile communication environment in which the communication device 810 is implemented as a communication device or a UE, or implemented in a communication device or a UE, and the network device 820 is implemented in a network node of a communication network or implemented as a network node of a communication network.

[0059] In some implementations, processor 812 can be configured to determine whether a capability is enabled. If the capability is enabled, processor 812 can apply scheduling restrictions to the K symbols preceding the SSB symbol and the K symbols following the SSB symbol. Processor 812 can transmit uplink symbols via transceiver 816 or receive downlink symbols other than those with scheduling restrictions via transceiver 816.

[0060] In some implementations, processor 812 may be configured not to transmit uplink symbols or not to receive downlink symbols on SSB symbols, the K symbols preceding the SSB symbol, and the K symbols following the SSB symbol. Processor 812 may be configured to apply scheduling restrictions to SS-RSRP or SS-SINR measurements on cells within the FR2 frequency range.

[0061] In some implementations, processor 812 may be configured to determine the number of K symbols based on SCS.

[0062] In some implementations, processor 812 may be configured to receive higher-layer signaling from network device 820 via transceiver 816 to determine whether the parameter derivedSSB-IndexFromCell is enabled.

[0063] In some implementations, processor 812 may be configured to determine whether the capability is enabled when operating in the licensed frequency band in FR2-2 or based on the SCS and the operating frequency band.

[0064] In some implementations, processor 812 can be configured to apply scheduling restrictions to all symbols within an SMTC window when the capability is not enabled. Processor 812 can also be configured to ignore or skip scheduling within symbols with scheduling restrictions.

[0065] In some implementations, processor 812 may be configured to transmit uplink timing accuracy capability to a network node via transceiver 816. Processor 812 may receive, via transceiver 816, an instruction to enable scheduling restrictions from the network node. Processor 812 may determine at least one uplink time slot based on the time slot configuration from the network node. When scheduling restrictions are enabled, processor 812 may apply scheduling restrictions to at least one symbol within the uplink time slot. Processor 812 may transmit uplink symbols other than those with scheduling restrictions via transceiver 816.

[0066] In some implementations, processor 812 may be configured to transmit uplink symbols not in the first symbol of the uplink time slot and the last symbol of the uplink time slot.

[0067] In some implementations, processor 822 may be configured to enable the capabilities of communication device 810. When the capabilities are enabled, processor 822 may apply scheduling restrictions to K symbols preceding the SSB symbol and K symbols following the SSB symbol. Processor 822 may transmit downlink symbols other than those with scheduling restrictions or receive uplink symbols other than those with scheduling restrictions via transceiver 826.

[0068] In some implementations, processor 822 may be configured not to schedule uplink symbols on SSB symbols, the K symbols before SSB symbols, and the K symbols after SSB symbols, or not to schedule downlink symbols on SSB symbols, the K symbols before SSB symbols, and the K symbols after SSB symbols.

[0069] In some implementations, processor 822 may be configured to determine the number of K symbols based on SCS.

[0070] In some implementations, processor 822 may be configured to configure the parameter deriveSSB-IndexFromCell to communication device 810 via transceiver 826 through higher-layer signaling. Processor 822 may enable this parameter when operating within the licensed frequency band in FR2-2.

[0071] Figure 9An example process 900 according to an embodiment of the present disclosure is illustrated. Process 900 may be an example implementation, either partially or completely, of the above scenarios / schemes with higher SCS (Scheduling Limits) related to the present disclosure. Process 900 may represent one aspect of the implementation of a feature of communication device 810. Process 900 may include one or more operations, actions, or functions, as shown in one or more of blocks 910, 920, and 930. Although illustrated as discrete blocks, depending on the desired implementation, a portion of process 900 may be divided into additional blocks, combined into fewer blocks, or eliminated. Furthermore, the blocks of process 900 may be arranged in... Figure 9 The process 900 may be executed in the order shown, or in a different order. Process 900 may be implemented by communication device 810 or any suitable UE or machine type device. For illustrative purposes only and not as a limitation, process 900 is described below in the context of communication device 810. Process 900 may begin at block 910.

[0072] At 910, process 900 may involve the processor 812 of communication device 810 determining whether a capability is enabled. Process 900 can proceed from 910 to 920.

[0073] At 920, process 900 may involve processor 812 applying scheduling constraints to K symbols before and K symbols after the SSB symbol, provided the capability is enabled. K symbols is greater than one symbol. Process 900 can proceed from 920 to 930.

[0074] In 930, process 900 may involve processor 812 sending uplink symbols other than those with scheduling restrictions or receiving downlink symbols.

[0075] In some implementations, process 900 may also involve processor 812 not transmitting uplink symbols or receiving downlink symbols on SSB symbols, K symbols before SSB symbols, and K symbols after SSB symbols.

[0076] In some implementations, process 900 may also involve processor 812 determining the number of K symbols based on SCS. SCS includes at least one of 480 kHz and 960 kHz.

[0077] In some implementations, process 900 may also involve processor 812 determining when the capability is enabled when operating in a licensed frequency band in FR2-2.

[0078] In some implementations, process 900 may also involve processor 812 determining whether a capability is enabled based on the SCS and the operating frequency band.

[0079] In some implementations, process 900 may also involve processor 812 applying scheduling restrictions to all symbols within the SMTC window when the capability is not enabled.

[0080] In some implementations, process 900 may also involve processor 812 ignoring scheduling within symbols with scheduling restrictions.

[0081] Figure 10 An example process 1000 according to an embodiment of the present disclosure is illustrated. Process 1000 may be an example implementation of the above scenarios / schemes with higher SCS regarding the scheduling limitations of the present disclosure, whether partially or completely. Process 1000 may represent one aspect of the implementation of features of communication device 810. Process 1000 may include one or more operations, actions, or functions, as illustrated in one or more of blocks 1010, 1020, 1030, 1040, and 1050. Although illustrated as discrete blocks, the individual blocks of process 900 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Furthermore, the blocks of process 1000 may be arranged in... Figure 10 The process can be executed in the order shown, or in a different order. Process 1000 can be implemented by communication device 810 or any suitable UE or machine type device. For illustrative purposes only and not for limitation, process 1000 is described below in the context of communication device 810. Process 1000 may begin at block 1010.

[0082] At 1010, process 1000 may involve the processor 812 of communication device 810 sending uplink timing accuracy capability to network nodes. Process 1000 can proceed from 1010 to 1020.

[0083] At 1020, process 1000 may involve processor 812 receiving an instruction from the network node to enable scheduling restrictions. Process 1000 can proceed from 1020 to 1030.

[0084] At 1030, process 1000 may involve processor 812 determining at least one uplink timeslot based on timeslot configurations from network nodes. Process 1000 can proceed from 1030 to 1040.

[0085] At 1040, process 1000 may involve processor 812 applying scheduling restrictions to at least one symbol within an uplink timeslot when scheduling restrictions are enabled. Process 1000 can proceed from 1040 to 1050.

[0086] In 1050, process 1000 may involve processor 812 sending uplink symbols outside of symbols with scheduling restrictions.

[0087] In some implementations, process 1000 may involve processor 812 uptransmitting at least one of the first symbol and the last symbol of the uplink time slot.

[0088] In some implementations, process 1000 may involve processor 812 indicating a supported set of timing precisions or a set of unsupported timing precisions, or indicating a supported SCS or an unsupported SCS.

[0089] Figure 11 An example process 1100 according to an embodiment of the present disclosure is illustrated. Process 1100 may be an example implementation of the above scenarios / solutions, whether partially or completely, with respect to the scheduling limitations of the present disclosure with higher SCS. Process 1100 may represent one aspect of an implementation of a feature of network device 820. Process 1100 may include one or more operations, actions, or functions, as illustrated in one or more of blocks 1110, 1120, and 1130. Although illustrated as discrete blocks, depending on the desired implementation, a portion of process 1100 may be divided into additional blocks, combined into fewer blocks, or eliminated. Furthermore, the blocks of process 1100 may be arranged in... Figure 11 The process 1100 may be executed in the order shown, or in a different order. Process 1100 may be implemented by network device 820 or any suitable base station or network node. For illustrative purposes only and not as a limitation, process 1100 is described below in the context of network device 820. Process 1100 may begin at block 1110.

[0090] At 1110, process 1100 may involve the processor 822 of network device 820 enabling capabilities to the UE. Process 1100 can proceed from 1110 to 1120.

[0091] At 1120, process 1100 may involve processor 822 applying scheduling constraints to K symbols before and K symbols after the SSB symbol, provided the capability is enabled. K symbols is greater than one symbol. Process 1100 can proceed from 1120 to 1130.

[0092] At 1130, process 1100 may involve processor 822 sending downlink symbols or receiving uplink symbols other than those with scheduling restrictions.

[0093] In some implementations, process 1100 may also involve processor 822 not scheduling uplink or downlink symbols on the SSB symbol, the K symbols before the SSB symbol, and the K symbols after the SSB symbol.

[0094] In some implementations, process 1100 may also involve processor 822 determining the number of K symbols based on SCS. SCS includes at least one of 480 kHz and 960 kHz.

[0095] In some implementations, process 1100 may also involve processor 822 configuring parameters deriveSSB-IndexFromCell to the UE via higher-layer signaling.

[0096] In some implementations, process 1100 may also involve enabling the capability when processor 822 operates in the licensed frequency band in FR2-2.

[0097] Some embodiments involve storing computer program instructions on a machine-readable or computer-readable medium (or, as referred to, a computer-readable storage medium, machine-readable medium, or machine-readable storage medium). Examples of such computer-readable media include RAM, ROM, read-only optical disc (CD-ROM), recordable optical disc (CD-R), rewritable optical disc (CD-RW), read-only digital versatile optical disc (e.g., DVD-ROM, dual-layer DVD-ROM), various recordable / rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD card, mini-SD card), microSD card, magnetic and / or solid-state hard disk drives, read-only and recordable... Optical discs, high-density optical discs, any other optical or magnetic media, and floppy disks. Computer-readable media may store computer programs that can be executed by at least one processing unit and include a set of instructions for performing various operations. Examples of computer programs or computer code include machine code generated by a compiler, and files that include high-level code executed by a computer, electronic components, or a microprocessor using an interpreter.

[0098] While the foregoing discussion primarily concerns microprocessors or multi-core processors that execute software, many of the aforementioned features and applications are implemented by one or more integrated circuits, such as application-specific integrated circuits (ASICs) or field-programmable gate arrays (FPGAs). In some embodiments, such integrated circuits execute instructions stored on the circuit itself. Furthermore, some embodiments execute software stored in programmable logic devices (PLDs), ROM, or RAM devices.

[0099] As used in this specification and any claim of this application, the terms "computer," "server," "processor," and "memory" refer to electronic or other technical devices. These terms do not include people or groups of people. For the purposes of this specification, the term "display" or "show" means "displayed on an electronic device." As used in this specification and any claim of this application, the terms "computer-readable medium," "computer-readable medium," and "machine-readable medium" are entirely limited to tangible physical objects that store information in a form readable by a computer. These terms do not include any wireless signals, wired download signals, or any other temporary signals.

[0100] The subjects described herein sometimes illustrate different components contained within or connected to other different components. It should be understood that the architectures depicted are merely exemplary, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components achieving the same function is effectively “associated” to achieve the desired function. Therefore, any two components combined in this document to obtain a particular function can be considered “associated” with each other to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably coupled” with each other to achieve the desired function, and any two components that can be suchly associated can also be considered “operably coupled” with each other to achieve the desired function. Specific examples of “operably coupled” include, but are not limited to: physically connectable and / or physically interacting components, and / or wirelessly interactable and / or logically interactable components.

[0101] Furthermore, regarding the use of virtually any plural and / or singular terms in this document, those skilled in the art can convert plural to singular and / or singular to plural, provided it is appropriate for the context and / or application. For clarity, various singular / plural permutations may be explicitly described herein.

[0102] Those skilled in the art will understand that, generally, the terms used herein, particularly those used in the appended claims (e.g., the subject of the appended claims), are intended as “open-ended” terms (e.g., the term “comprising” should be interpreted as “comprising but not limited to”, the term “having” should be interpreted as “having at least”, the term “comprising” should be interpreted as “comprising but not limited to”, etc.). Those skilled in the art will also understand that if a specific number of the objects of the claims is intended, such intention will be explicitly stated in the claims; in the absence of such a statement, such intention does not exist. For example, to aid understanding, the appended claims may include the use of introductory phrases such as “at least one” and “one or more” to introduce the objects of the claims. However, the use of such phrases should not be interpreted as limiting any claim containing such an indefinite article "a (a) or an" to an invention containing only one such claim, even if the same claim contains the introductory phrases "one or more" or "at least one" and indefinite articles such as "a (a)" or "an" (e.g., "a (a)" and / or "an" should generally be interpreted as meaning "at least one" or "one or more"); the same applies to the use of definite articles to introduce the claim. Furthermore, even if a specific number of the claimed claims is explicitly stated, those skilled in the art will recognize that such a statement should generally be interpreted as meaning at least the stated number (e.g., a statement containing only "two claims" without other modifiers generally means at least two claims, or two or more claims). Furthermore, when using idioms such as "at least one of A, B, and C," such a structure is generally intended to convey the meaning of the idiom as understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" would include, but is not limited to, systems having a single A, a single B, a single C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). When using idioms such as "at least one of A, B, or C," such a structure is generally intended to convey the meaning of the idiom as understood by a person skilled in the art (e.g., "a system having at least one of A, B, or C" would include, but is not limited to, systems having a single A, a single B, a single C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). Those skilled in the art will further understand that, whether in the specification, claims, or drawings, virtually arbitrary extractives and / or phrases representing two or more alternative terms should be understood to consider the possibility of including one, any, or all two terms.For example, the phrase “A or B” should be understood as including the possibility of “A”, “B”, or “A and B”.

[0103] As can be understood from the foregoing, various embodiments of this disclosure have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are indicated by the appended claims.

Claims

1. A mobile communication method, comprising: The device's processor determines whether the capability is enabled. When this capability is enabled, the processor applies scheduling constraints to the K symbols before the SSB symbol and the K symbols after the SSB symbol; as well as The processor sends uplink symbols other than those with scheduling restrictions or receives downlink symbols other than those with scheduling restrictions. K symbols are greater than 1 symbol. For serving cells with data symbols having a 480kHz subcarrier spacing and SSB symbols having a 960kHz subcarrier spacing, K=3; for serving cells with data symbols having a 960kHz subcarrier spacing and SSB symbols having a 120kHz or 480kHz subcarrier spacing, K=7.

2. The mobile communication method as described in claim 1, characterized in that, The application of this scheduling restriction includes not sending uplink symbols or receiving downlink symbols on the SSB symbol, the K symbols preceding the SSB symbol, and the K symbols following the SSB symbol.

3. The mobile communication method of claim 1, wherein the uplink symbol includes at least one of a physical uplink control channel, a physical uplink shared channel, and a probe reference signal, and wherein the downlink symbol includes at least one of a physical downlink control channel, a physical downlink shared channel, a tracking reference signal, and a channel state information reference signal for a channel quality indicator.

4. The mobile communication method of claim 1, wherein scheduling constraints are applied due to the synchronization signal-reference signal received power or synchronization signal-to-interference-plus-noise ratio measurement on the cell within frequency range 2.

5. The mobile communication method as described in claim 1, further comprising: The processor determines the number of K symbols based on the subcarrier spacing. The subcarrier spacing includes at least one of 480 kHz and 960 kHz.

6. The mobile communication method as described in claim 1, characterized in that, This capability is enabled by the parameter deriveSSB-IndexFromCell in the higher-level signaling configuration of the network node.

7. The mobile communication method as described in claim 1, characterized in that, The determination includes determining when to enable the capability when operating in the licensed frequency band of frequency range 2-2.

8. The mobile communication method as described in claim 1, wherein, The determination includes deciding whether to enable the capability based on the subcarrier spacing and operating frequency band.

9. The mobile communication method as described in claim 1, further comprising: When this capability is not enabled, the processor applies the scheduling restriction to all symbols within the SSB-based radio resource management measurement timing configuration window.

10. The mobile communication method as described in claim 1, further comprising: The processor ignores scheduling within symbols that have this scheduling restriction.

11. A mobile communication method, comprising: The network node's processor enables the capability to be transferred to the user equipment; When this capability is enabled, the processor applies scheduling constraints to the K symbols before the SSB symbol and the K symbols after the SSB symbol; as well as The processor sends downlink symbols other than those with the scheduling restrictions or receives uplink symbols other than those with the scheduling restrictions. K symbols are greater than 1 symbol. For serving cells with data symbols having a 480kHz subcarrier spacing and SSB symbols having a 960kHz subcarrier spacing, K=3; for serving cells with data symbols having a 960kHz subcarrier spacing and SSB symbols having a 120kHz or 480kHz subcarrier spacing, K=7.

12. The mobile communication method as described in claim 11, characterized in that, The application of this scheduling restriction includes not scheduling uplink symbols or not scheduling downlink symbols on the SSB symbol, the K symbols preceding the SSB symbol, and the K symbols following the SSB symbol.

13. The mobile communication method as described in claim 11, further comprising: The processor determines the number of K symbols based on the subcarrier spacing. The subcarrier spacing includes at least one of 480 kHz and 960 kHz.

14. The mobile communication method as described in claim 11, wherein, The activation includes configuring the parameter deriveSSB-IndexFromCell to the user equipment via higher-layer signaling.

15. The mobile communication method of claim 11, wherein the activation includes enabling the capability when operating in a licensed frequency band within the frequency range 2-2.

Images