Power saving optimization for high mobility scenarios

Abstract

Methods, systems, and computer-readable media are disclosed to perform operations including determining a cell for a user equipment (UE) to connect to a network using a connection in an independent (SA) mode; accessing a physical cell identifier (PCI) list associated with the UE over a period of time based on determining a bandwidth portion (BWP) of the connection; assigning a timeout value to the BWP switching timer based on the number of PCI values in the list and the duration of the time period; the BWP switching timer is started; and in response to determining that a handover of the UE to a different cell of the network occurs before the BWP handover timer reaches the timeout value, causing the UE to switch to an LTE mode.

Description

[0001] Priority claim

[0002] This application claims priority under 35 USC §119(e) to U.S. patent application serial number 63 / 409,390, filed on September 23, 2022, the entire contents of which are hereby incorporated by reference. Background Art

[0003] Wireless communication networks provide integrated communication platforms and telecommunication services to wireless user devices. Example telecommunication services include telephone, data (e.g., voice, audio and / or video data), messaging, Internet access and / or other services. Wireless communication networks have wireless access nodes that exchange wireless signals with wireless user devices using wireless network protocols (such as protocols described in various telecommunication standards promulgated by the Third Generation Partnership Project (3GPP)). Example wireless communication networks include code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal frequency division multiple access (OFDMA) networks, long term evolution (LTE) and fifth generation new radio (5G NR). Wireless communication networks use technologies such as OFDM, multiple input multiple output (MIMO), advanced channel coding, massive MIMO, beamforming and / or other features to facilitate mobile broadband services.

[0004] In order to obtain a high throughput 5G NR network, the frequency bandwidth is set to be much higher than the frequency used for LTE. Therefore, the user equipment (UE) consumes additional power. The network can be configured to switch between bandwidth parts (BWP) to save power for the UE. The network configures multiple BWPs for a given UE. When the UE needs a large throughput, the UE uses a large BWP. When the UE does not need a large throughput, the UE is switched to a small BWP to save power.

[0005] The UE may also use Smart Data Mode (SDM) to save power. The UE is configured to automatically switch between 5G Standalone (SA) mode and LTE mode depending on the service type. For high throughput scenarios, the UE stays in SA mode. If not in a high throughput scenario, the UE deprioritizes SA mode and switches to LTE. NR L1 measurements may be deleted to save power. When a high throughput scenario is needed again, the UE changes priority from LTE to SA. Summary of the invention

[0006] The user equipment (UE) is configured to operate in one of the 5G standalone (SA) mode or the non-standalone (NSA) LTE mode. When operating in the SA mode, the UE is configured to use the 5G NR network (NW) for both the transmission and reception of control information (e.g., control plane) and user data (e.g., user plane). When operating in the LTE mode, the UE is configured to use the LTE network for the transmission and reception of control information and user data. The UE is configured to switch between the SA mode and the LTE mode. In some implementations, the UE switches from the SA mode to the LTE mode to save power.

[0007] To save power, the UE downgrades priority from SA mode to LTE-only mode. The UE switches when there is no high throughput and when Smart Data Mode (SDM) is turned on. In LTE-only mode (LTE mode), 5G L1 measurements are disabled (e.g., truncated), thereby saving power. Because the bandwidth of the transmission of the 5G configuration (e.g., 100MHz / 60MHz...) is larger than the bandwidth LTE (e.g., 20MHz / 10MHz / 5MHz), power can be saved.

[0008] Generally speaking, the UE operates according to the network configuration. The UE does not activate SDM until the UE does not detect the network characteristic bandwidth part switching. The UE starts an internal bandwidth part switching timer to detect the network characteristic bandwidth part switching, as described later in this document. The bandwidth part switching timer starts when the UE is not using large throughput. The UE resets the bandwidth part timer when the physical cell identifier of the network changes. Conventionally, the UE does not fall back from SA mode to LTE mode until the bandwidth part switching timer expires.

[0009] The UE may experience high mobility scenarios. High mobility scenarios include scenarios where the UE moves in the network such that the UE moves between different cells of the network at a frequency above a threshold. When switching between cells of the network, the UE may be prevented from switching from SA mode to LTE mode because the bandwidth fraction timer is quickly reset. Therefore, the UE is prevented from switching from SA mode to LTE-only mode to save power.

[0010] The UE may experience a load balancing scenario. In this scenario, the UE may switch between two BWPs based on throughput requirements and small BPW active UE capacity. In this scenario, when the UE is not using high throughput to allocate bandwidth usage of connected devices in the network in cells of the network, the network switches the UE from a first bandwidth part (BWP) (such as a large BWP) to a second BWP (such as a small BWP). When the capacity of the small BWP is exceeded, the network may switch the UE back to the large BWP. A BWP typically includes a set of physical resource blocks (PRBs) for a given carrier. These resource blocks (RBs) are selected from a contiguous subset of common resource blocks for a given numerology.

[0011] The system and process described herein are configured to optimize the UE for switching between SA mode and LTE mode when the UE is in a high mobility scenario. In the first process, the UE is configured to optimize the switching timer when the UE detects that the UE is in a high mobility scenario. In the second process, the UE is configured to optimize the switching from SA mode to LTE mode when the UE detects that the UE is in a high mobility scenario. In the third process, the UE determines that the UE is in load balancing mode. The UE is configured to optimize the switching between SA mode and LTE mode when it is in a load balancing scenario. For each of the high mobility scenario and the load balancing scenario, the UE is configured to determine that the scenario is applicable by applying a statistical model. The statistical model describes the frequency of the UE switching between cells of the network within a time period. The UE uses data from the switching timer and the physical cell identifier (PCI) switching counter as input for the statistical model. The UE is configured to determine whether to switch between SA mode and LTE mode based on the statistical model.

[0012] One or more of the advantages described herein may be achieved by embodiments of the systems and methods described herein.

[0013] The details of one or more embodiments of these systems and methods are set forth in the following drawings and description. Other features, objects, and advantages of these systems and methods will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 A wireless network according to some embodiments is illustrated.

[0015] Figure 2 A flow chart of a process for SA switching by a UE is shown.

[0016] Figure 3A A flow chart of a process for optimizing the SA switching timer by a UE is shown.

[0017] Figure 3BA flow chart illustrating a process for optimizing the SA switching timer by a UE is shown.

[0018] Figure 4 A flow chart is shown of a process for switching from SA mode to LTE mode in response to detection of a high mobility scenario by the UE.

[0019] Figure 5A Shown according to Figure 3A or Figure 3B Example results of SA switching performed by a UE during the process.

[0020] Figure 5B Shown according to Figure 4 Example results of SA switching performed by a UE during the process.

[0021] Figure 6 A diagram showing SA switching by UE for BWP load balancing.

[0022] Fig. 7A A flow chart illustrating the process of SA switching by a UE for BWP load balancing is shown.

[0023] Figure 7B A flow chart illustrating the process of SA switching by a UE for BWP load balancing is shown.

[0024] Figure 8 A user equipment (UE) according to some embodiments is illustrated.

[0025] Fig. 9 An access node according to some embodiments is illustrated. DETAILED DESCRIPTION

[0026] The user equipment (UE) is configured to operate in one of the 5G standalone (SA) mode or the LTE mode. When operating in the SA mode, the UE is configured to use the 5G NR network (NW) for both the transmission and reception of control information (e.g., control plane) and user data (e.g., user plane). More specifically, for SA operation, the UE uses the 5G network and NR frequency (e.g., FR1, FR2, etc.) for the control plane and user data. When operating in the LTE mode, the UE is configured to use the LTE network for the transmission and reception of control information and user data. More specifically, when operating in the LTE mode, the UE is configured to use the 4G LTE infrastructure and protocols for control functions and user data.

[0027] The UE is configured to switch between SA mode and LTE mode. In some implementations, the UE switches from SA mode to LTE mode to save power. Switching from SA mode to LTE mode is also referred to as deprioritizing SA and falling back to LTE. The UE may determine that switching to LTE mode is desired because the throughput requirement for the UE is met by the lower throughput of the LTE mode.

[0028] The UE may experience high mobility scenarios. High mobility scenarios include scenarios in which the UE moves in the network so that the UE moves between different cells of the network at a frequency higher than a threshold. The UE does not stay in the cell for longer than a given time period. This may occur if the UE is moving quickly in a vehicle such as a car or a train, or if the UE is moving in a densely populated area. For example, on a high-speed train, the UE may only be in a given cell for a few seconds (e.g., less than 15 seconds). In another example, the UE may be in a border area (e.g., a ping pong area) where the UE frequently switches between two adjacent serving cells. In some implementations, the UE may switch quickly between a large BWP and a small BWP (e.g., a load balancing area).

[0029] For several reasons, the UE can be prevented from switching from SA mode to LTE mode in high mobility scenarios. When the NW has switched the UE from a large BWP to a small BWP, the UE does not switch from SA mode to LTE mode. In the 5G SA mode for the UE, the smart data mode (SDM) deprioritization does not occur until the BWP switching timer expires. Generally speaking, the BWP switching timer default value is 15 seconds. In response to a cell handover, the UE resets the switching timer to zero. The UE detects a cell handover when the received physical cell identifier (PCI) value changes. This occurs in a situation where the UE is in high mobility in a densely populated area (e.g., a high mobility situation in a city). When moving quickly, such as when on a high-speed train, the UE can be prevented from switching between SA and LTE. When close to a cell boundary (such as a cell round-trip area) where the UE switches between a large BWP (e.g., BWP ID1) and a small BWP due to an overload on BWP ID 2 (small BWP), the UE can be prevented from switching between SA and LTE. In addition, when the PCI changes exceed a threshold frequency, the UE may be prevented from switching from SA to LTE because the switching timer never expires. As a result of staying in SA mode, the UE power consumption is unnecessarily higher than if the UE switches to LTE mode. Specifically, in order to save UE power, the network configures multiple bandwidth parts (BWPs) for the UE. When the UE is not using high throughput, the UE switches to a small BWP. When the UE is using high throughput, the UE switches to a large or high BWP.

[0030] To overcome these technical obstacles, the UE is configured to detect that a high mobility scenario is occurring and to change the criteria for switching from SA mode to LTE mode in those high mobility scenarios. The UE is configured to optimize the process for deprioritizing the UE from SA mode to LTE mode. The UE is configured to optimize the BWP switching timer. When the UE is in a high mobility scenario, the BWP switching timer is adaptive. The UE changes the length of the BWP timer based on statistics of PCI changes or BWP timer reset statistics within a given time period. In another example, once a high mobility scenario is detected, the UE switches to LTE mode and operates using the LTE network.

[0031] In the following cases, the UE may detect that the UE is in a high mobility scenario or in a load balancing scenario. For example, the UE may move quickly in a city or densely populated area. In some specific implementations, the UE may be on a high-speed train or other fast-moving vehicles. In some specific implementations, the UE may be near the BWP transition area. As a result of these scenarios, the UE is configured to adjust the process for switching from SA mode to LTE mode. This is because the UE always stays on a single PCI shorter than a given time period (e.g., 7 seconds), but the BWP with a timer is fixed to a longer time period (e.g., 15 seconds). In another example, the PCI for the UE changes too frequently, and the SA priority reduction process fails at the handover transition area. Frequent BWP switching also increases UE power consumption. The process described herein addresses these scenarios to reduce UE power consumption and enable SA mode to LTE mode switching in high mobility situations.

[0032] Figure 1 A wireless network 100 is illustrated according to some embodiments. The wireless network 100 includes UEs 102 and base stations 104 connected via one or more channels 106A, 106B across an air interface 108. The UEs 102 and base stations 104 communicate using a system that supports control for managing access of the UEs 102 to the network via the base stations 104.

[0033] For convenience and not for purposes of limitation, the wireless network 100 is described in the context of Long Term Evolution (LTE) and fifth generation (5G) New Radio (NR) communication standards, as defined by the 3rd Generation Partnership Project (3GPP) technical specifications. More specifically, the wireless network 100 is described in the context of a non-standalone (NSA) network that combines both LTE and NR (e.g., an E-UTRA (Evolved Universal Terrestrial Radio Access)-NR Dual Connectivity (EN-DC) network and a NE-DC network). However, the wireless network 100 may also be a standalone (SA) network that combines only NR. In addition, other types of communication standards are possible, including future 3GPP systems (e.g., sixth generation (6G)) systems, Institute of Electrical and Electronics Engineers (IEEE) 802.11 technologies (e.g., IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or other currently or future developed IEEE 802.11 technologies), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc. Although various aspects may be described herein using terms generally associated with 5G NR, various aspects of the present disclosure may be applied to other systems, such as 3G, 4G, and / or systems after 5G (e.g., 6G).

[0034] In the wireless network 100, UE 102 and any other UE in the system can be, for example, a laptop computer, a smart phone, a tablet computer, a machine type device such as a smart meter or a dedicated device for healthcare monitoring, remote security monitoring, an intelligent transportation system, or any other wireless device with or without a user interface. In the network 100, a base station 104 provides a network connection to a wider network (not shown) to UE 102. The UE 102 connection is provided via an air interface 108 in a base station service area provided by the base station 104. In some embodiments, this wider network can be a wide area network operated by a cellular network provider, or it can be the Internet. Each base station service area associated with the base station 104 is supported by an antenna integrated with the base station 104. The service area is divided into a plurality of sectors associated with certain antennas. Such sectors can be physically associated with fixed antennas, or can be assigned to physical areas with tunable antennas or antenna settings, which can be adjusted in a beamforming process for directing signals to a specific sector.

[0035] UE 102 includes control circuitry 110 coupled to transmit circuitry 112 and receive circuitry 114. Transmit circuitry 112 and receive circuitry 114 may each be coupled to one or more antennas. Control circuitry 110 may be adapted to perform operations associated with selection of a codec for communication and to adapt the codec for wireless communication as part of system congestion control. Control circuitry 110 may include various combinations of dedicated circuitry and baseband circuitry. Transmit circuitry 112 and receive circuitry 114 may be adapted to transmit and receive data, respectively, and may include radio frequency (RF) circuitry or front end module (FEM) circuitry, including communications using the codecs described herein.

[0036] In various embodiments, aspects of the transmitting circuit 112, receiving circuit 114, and control circuit 110 may be integrated in various ways to implement the circuits described herein. The control circuit 110 may be adapted or configured to perform various operations, such as UE-related operations described elsewhere in this disclosure. The transmitting circuit 112 may transmit multiple multiplexed uplink physical channels. The multiple uplink physical channels may be multiplexed according to time division multiplexing (TDM) or frequency division multiplexing (FDM) and carrier aggregation. The transmitting circuit 112 may be configured to receive block data from the control circuit 110 to be transmitted across the air interface 108. Similarly, the receiving circuit 114 may receive multiple multiplexed downlink physical channels from the air interface 108 and relay these physical channels to the control circuit 110. The multiple downlink physical channels may be multiplexed according to TDM or FDM and carrier aggregation. The transmitting circuit 112 and the receiving circuit 114 may transmit and receive both control data and content data (e.g., messages, images, videos, etc.) structured within the data blocks carried by the physical channels.

[0037] Figure 1 A base station 104 is also illustrated. In an embodiment, the base station 104 may be an NG radio access network (RAN) or a 5G RAN, an E-UTRAN, a non-terrestrial cell, or a traditional RAN such as a UTRAN or a GERAN. As used herein, the term "NG RAN" or the like may refer to a base station 104 operating in an NR or 5G wireless network 100, and the term "E-UTRAN" or the like may refer to a base station 104 operating in an LTE or 4G wireless network 100. The UE 102 utilizes connections (or channels) 106A, 106B, each of which includes a physical communication interface or layer.

[0038] Base station 104 circuitry may include control circuitry 116 coupled to transmit circuitry 118 and receive circuitry 120. Transmit circuitry 118 and receive circuitry 120 may each be coupled to one or more antennas that may be used to enable communications over air interface 108.

[0039] The control circuit 116 may be adapted to perform the following operations: analyze and select a codec, manage congestion control and bandwidth limit communications from a base station, determine whether a base station is aware of a codec, and communicate with a base station that is aware of a codec to manage codec selection for various communication operations described herein. The transmit circuit 118 and the receive circuit 120 may be adapted to transmit and receive data, respectively, to any UE connected to the base station 104 using data generated by the various codecs described herein. The transmit circuit 118 may transmit a downlink physical channel including a plurality of downlink subframes. The receive circuit 120 may receive a plurality of uplink physical channels from various UEs including the UE 102.

[0040] In this example, one or more channels 106A, 106B are illustrated as air interfaces that implement communication coupling, and may conform to cellular communication protocols, such as GSM protocols, CDMA network protocols, PTT protocols, POC protocols, UMTS protocols, 3GPP LTE protocols, Advanced Long Term Evolution (LTE-A) protocols, LTE-based unlicensed spectrum access (LTE-U), 5G protocols, NR protocols, NR-based unlicensed spectrum access (NR-U) protocols, and / or any other communication protocols discussed herein. In an implementation scheme, UE 102 may directly exchange communication data via a ProSe interface. The ProSe interface may alternatively be referred to as a SL interface, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0041] Figure 2 The method for use by a UE such as Figure 1 102) performs SA switching. The UE operation is based on the state of the UE. If the UE is being used by a user, the UE is configured to determine whether the data usage by the user is sufficiently low throughput so that the UE can be switched to LTE mode without adversely affecting the performance of the UE.

[0042] Generally speaking, the UE determines whether to change from SA mode to LTE mode based on the current bandwidth. In a first case, the UE determines that the 5G NR bandwidth is less than or equal to a certain threshold. For example, the bandwidth threshold can be 20 megahertz (MHz), 25MHz...40MHz, or a similar value. If the bandwidth is less than or equal to the threshold, the UE remains (206) in SA mode because the operating bandwidth is similar to LTE. In a second case, if the UE determines that the 5G NR bandwidth is above the threshold (e.g., 40MHz) and does not have high throughput usage, the UE switches to LTE mode and uses the LTE network (e.g., Figure 1 base station 104) to operate.

[0043] In the first case, the UE determines that the FR1 or FR2 bandwidth is less than or equal to a certain threshold. For example, the bandwidth threshold may be 20 megahertz (MHz), 25 MHz, ... 40 MHz, or similar values. If the bandwidth is less than or equal to the threshold and the UE does not have high throughput usage, the UE remains in SA mode.

[0044] In the second case, the UE determines that the 5G NR bandwidth is above a threshold (e.g., 40MHz). The UE determines whether the UE is in a high confidence scenario or a low confidence scenario. The confidence level of the UE is the result of a statistical test with a performance requirement for throughput. A signal or a combination of signals is provided to the RX port of the UE's receiver. The ability of the receiver to demodulate / decode the signal is verified by measuring the throughput achieved by the UE. The UE is referred to as the device under test (DUT). The confidence level is determined by a percentage of the maximum throughput achieved by the UE. If the UE determines that the UE is in a high throughput, high confidence scenario, the UE remains in SA mode. If the UE determines that the UE is in a high throughput, low confidence mode, the UE starts a switching timer. The UE determines whether a BWP switch occurs from the network within a threshold time period. In some implementations, the threshold period is static and can be vendor-specific (e.g., accessed in a lookup table). In some implementations, the threshold period is adjustable. For example, the bandwidth timer can be 15 seconds, 10 seconds, 5 seconds, or another time length. If the UE determines that the switching timer exceeds the threshold, the UE switches to LTE mode and uses the LTE network (eg, Figure 1 base station 104) to operate.

[0045] For process 200 describing baseline operation of a UE, the UE operates as now described. The UE detects that the network is load balancing the UE on the network. The UE operates in SA mode (202). The UE is configured to determine whether to change from SA mode to LTE mode based on the current bandwidth. In a first case, the UE determines (204) that the FR1 or FR2 bandwidth is less than or equal to a specific threshold. For example, the bandwidth threshold may be 20 megahertz (MHz), 25MHz...40MHz, or a similar value. If the bandwidth is less than or equal to the threshold, the UE determines whether the UE is operating in high throughput mode or low throughput mode. If the UE determines (206) that the UE is operating in high throughput mode, the UE is configured to perform (208) a BWP switch to a large BWP. If the UE determines (210) that the UE is operating in low throughput mode, the UE is configured to keep the UE in SA mode (218) and use a small BWP. However, if the UE determines (210) that the UE is operating in low throughput mode, the UE is configured to perform a BWP switch to a large BWP, as indicated by the network for load balancing. The small BWP threshold (40 MHz) is a configurable value. In this example, the default value is 40 MHz. In general, the level for high throughput usage is defined by the service type and data usage, and is case specific.

[0046] In some embodiments, the UE determines (220) that the UE is operating using a large BWP. For example, the UE determines in SA mode that the FR1 / FR2 bandwidth is above a threshold (e.g., 40 MHz). If the UE determines (222) that the UE is operating in high throughput mode, the UE remains (224) in SA mode using the large BWP. If the UE determines (226) that the UE is not using a high throughput service or is not in high throughput mode, the UE is configured to start or restart (228) a BWP switching timer (e.g., under 15 seconds). The UE determines (230) whether to stay in SA mode or switch to LTE mode. If the network switches the UE to a small BWP before the UE switching timer expires or the UE is handed over to a new cell by the network, the UE does not switch to the LTE network, but instead stays in SA mode. The UE determines the throughput scenario again (e.g., by returning to step 202). If the BWP switching timer expires, the UE switches (232) to LTE mode and uses the LTE network.

[0047] Figure 3A A method for optimizing a UE (eg, Figure 1Flowchart of process 300 of SA switching timer of UE 102). In process 300, the UE is configured to optimize the SA deprioritization process when the UE detects that the UE is in a high mobility scenario. When the UE detects that a high mobility scenario is occurring, the UE enters a high mobility mode for performing process 300. For process 300, the UE is configured to optimize the BWP switching timer of the UE. When the UE is in high mobility mode, the BWP switching time may be set to an adaptive or static value. When in static mode, the value is determined based on global statistics of many UE devices. The UE has a set switching timer that ensures that the UE switches from SA mode to LTE mode during a high mobility scenario. For example, the timer may be set to 3 seconds or 5 seconds instead of the usual 15 seconds.

[0048] In adaptive mode, the UE is configured to set a switching timer based on data collected during a time period in which the UE has detected high mobility of the UE. For example, the UE detects that the UE is in a high mobility scenario because the UE experiences a frequently changing PCI. In some specific implementations, the UE uses other data to make this determination, such as global positioning system (GPS) data. The UE may monitor the PCI value within a time period (such as 40 seconds). In some specific implementations, the time period is less than 40 seconds (e.g., 0 to 40 seconds). In some specific implementations, the period is longer than 40 seconds. The UE sets the value for the BWP switching timer based on the PCI value and / or the BWP switching timer reset statistics during the measurement period. The value of the switching timer is set so that the timer will expire before the PCI changes for the UE. The time may be set to the average length of time spent by the UE in a given cell during a high mobility scenario. For example, in order to set the timer value, the UE receives data from a centralized unit high-speed train log. In this example, the UE determines that the PCI value changes 16 times in 40 seconds. The UE optimizes the BWP switching timer to 3 seconds.

[0049] The UE performs process 300 by determining (302) whether the UE is staying in SA mode or considering switching to LTE mode. The UE is configured to determine whether to change from SA mode to LTE mode based on the current bandwidth. In a first case, the UE determines (304) that the bandwidth (e.g., for FR1 or FR2) is less than or equal to a specific threshold. For example, the bandwidth threshold can be 20 megahertz (MHz), 25MHz...40MHz or a similar value. If the bandwidth is less than or equal to the threshold and the UE determines that the UE is not using high throughput, the UE remains (306) in SA mode. In other words, when the UE determines that the UE is operating in high throughput mode, the network switches the UE to a large BWP. In a second case, the UE determines (308) that the FR1 / FR2 bandwidth is above a threshold (e.g., 40MHz). The UE then determines whether the UE is in a high throughput or low throughput scenario. If the UE determines (312) that the UE is in a high throughput scenario, the UE remains (312) in SA mode. If the UE determines (314) that the UE is in a low throughput scenario, the UE checks the mobility scenario of the UE. As previously described, the UE determines (316) whether the UE is in a high mobility scenario. If the UE is in a high mobility scenario, the UE switches to a high mobility mode. In the high mobility mode, the UE sets (322) a BWP switching timer based on an evaluation period (T) and the number of PCI values ​​detected during the time period (N). The UE sets a value (X) of the BWP switching timer in seconds based on the values ​​T and N. As previously described, the value X may be based on both the values ​​T and N. For example, the value X may be a ratio of T and N. Specifically, the value X may be as follows: X=roundup(T / N), where roundup(T / N) is the ratio of T:N rounded up. If N exceeds a threshold (e.g., 3) during a time period T (e.g., 40 seconds), the UE transitions to a high mobility mode (also known as a high speed mode). This is in contrast to simply starting a static timer when a large BWP is detected and when the UE is not using high throughput. In this case, if the network switches the UE to a small BWP before the UE switching timer expires or the UE is handed over to a new cell by the network, the UE does not switch to the LTE network. However, the UE does not adjust the switching timer. If in a high mobility scenario with a nominal switching timer value, the timer will never expire and the UE will not switch to LTE mode. In this process 300, the timer value is changed for the high mobility mode. The UE starts (320) the timer with the updated value. If the UE is not in high mobility mode, the UE sets (318) the BWP switching timer to a nominal value (e.g., 15 seconds). Table 1 shows example values ​​for N, T, and X.

[0050] Table 1: Example timer length values ​​X in high mobility scenarios.

[0051]

[0052] Once the UE sets the switching timer to the initial value, the timer counts down. The UE determines (324) whether to stay in SA mode or switch to LTE mode. If the network switches to a small BWP by the network before the UE switching timer expires or the UE is handed over to a new cell by the network, the UE does not switch to the LTE network, but stays in SA mode. The UE may determine a new updated timer value (e.g., by returning to step 302) or reset the timer to the current set point value (e.g., by returning to step 320). In some embodiments, the UE resets the timer with a new time based on the last 40 second period of the high mobility mode. When the timer expires, the UE switches (326) to LTE mode.

[0053] Figure 3B An example is shown for use by a UE (eg, Figure 1 Flowchart of process 350 for optimizing SA switching timer for UE 102 of the embodiment of the present invention. The UE is configured (352) to be in SA mode. Process 350 includes determining (354) that the UE is on a large BWP (e.g., greater than 40 MHz). The BWP size threshold can be 20 MHz, 40 MHz, 60 MHz, or other values ​​between or similar to these examples.

[0054] The process 350 includes accessing (356) a PCI record for the UE within a given time period T (such as within the last 40 seconds). A timeout value for a BWP switching timer will be set in the PCI record for the UE based on the number of different PCIs during the time period. The process 350 includes determining (358) whether the number of different PCIs in the PCI record for the UE is greater than a threshold number. In some embodiments, the threshold number is predetermined (e.g., a static, preset value). In some embodiments, the threshold number is based on network activity of the UE or one or more other UEs over a number of time periods of length T or variable length. The UE determines how long the UE is associated with each cell of the PCI record from the number of PCIs in the record and the length of the time period. If the number of PCIs meets (e.g., exceeds or equals) the threshold number, the UE is configured to set (362) a BWP timer timeout value as a function of the time period length T and the number of different PCIs N in the record. In some embodiments, the function is a ratio of N:T. If the number N does not satisfy the threshold number, the UE is configured to set (360) the BWP timer expiration value to a preset default value (eg, 15 seconds).

[0055] The process 350 includes starting or restarting a BWP timer once the BWP timer timeout value is set. The BWP timer increments over time. The UE is configured to determine (366) whether the BWP timer has expired before the UE is handed over to the new cell. If the timer has expired, the UE is configured to access (356) the PCI record again to determine an updated BWP handover timer timeout value. If the UE handover does not occur and the BWP timer reaches the timeout value (e.g., expires), the UE is configured to downgrade (368) to LTE, or switch to LTE mode.

[0056] Figure 4 A method for responding to a request by a UE (eg, Figure 1 Flowchart of process 400 of switching from SA mode to LTE mode upon detection of a high mobility scenario by a UE 102 of the present invention. When the UE detects that a high mobility scenario is occurring, the UE enters the high mobility mode for performing process 400. For process 400, the UE is configured to eliminate the BWP switching timer of the UE or set the timer value to 0. For process 400, the UE is configured to switch to LTE mode using an LTE network when a high mobility scenario is detected.

[0057] The UE performs process 400 by determining (402) whether the UE is staying in SA mode or considering switching to LTE mode. The UE is configured to determine whether to change from SA mode to LTE mode based on the current bandwidth. In the first case, the UE determines (404) that the FR1 or FR2 bandwidth is less than or equal to a specific threshold. For example, the bandwidth threshold can be 20 megahertz (MHz), 25MHz...40MHz or a similar value. If the bandwidth is less than or equal to the threshold, the UE is configured to determine (406) whether the UE is operating in a high throughput scenario. If the UE is operating in a high throughput scenario, the network switches (409) the UE to a large BWP. If the UE is not operating in a high throughput scenario (405), the UE stays (407) in SA mode and uses a small BWP.

[0058] In a second case, the UE determines (408) that the FR1 / FR2 bandwidth is above a threshold value (e.g., 40 MHz). The UE determines whether the UE is in a high throughput or low throughput scenario. If the UE determines (410) that the UE is in a high throughput scenario, the UE remains (412) in SA mode. If the UE determines (414) that the UE is in a low throughput scenario, the UE checks the mobility scenario of the UE. As previously described, the UE determines (416) whether the UE is in a high mobility scenario. If the UE is in a high mobility scenario, the UE switches to LTE mode using the LTE network.

[0059] If the PCI value for the UE changes more than a threshold number of times (e.g., 3) during a monitoring period T (e.g., 40 seconds), the UE transitions to high mobility mode (also known as high speed mode). This is in contrast to simply turning on a static timer when a large BWP is detected and when the UE is not using high throughput. For high mobility mode, the UE changes the BWP switching timer value to zero. Thus, when the UE detects that a high mobility scenario is occurring and enters high mobility mode, the UE immediately switches (418) to LTE mode. If the UE is not in high mobility mode, the UE sets (420) the BWP switching timer to a nominal value (e.g., 15 seconds). Once the UE sets the switching timer to an initial value, the timer counts down. The UE determines (422) whether to stay in SA mode or switch to LTE mode. If the network switches to a small BWP by the network before the UE switching timer expires or the UE is handed over to a new cell by the network, the UE does not switch to the LTE network, but instead stays in SA mode. The UE tests the high mobility scenario again (e.g., by returning to step 402 or step 416). If the BWP switching timer expires, the UE switches (424) to LTE mode and uses the LTE network.

[0060] Figure 5A Shown according to Figure 3A or Figure 3B 500 is an example result of SA switching performed by a UE of process 300. Result 500 shows a time period exceeding 40 seconds. For each PCI value received by the UE, the time period associated with the physical cell is also shown. After approximately 40 seconds have passed, the UE determines at a time corresponding to entry 502 that the number of changes for the PCI value indicates that high mobility mode is occurring. The BWP timer value is reset from 15 seconds to 3 seconds because the PCI value changed more than 13 times during the monitoring period. The UE uses an adjusted switching timer value of 3 in high mobility mode. At a time corresponding to entry 504, the UE remains in the same cell for at least 3 seconds. The BWP switching timer expires and the UE switches to LTE mode using the LTE network.

[0061] Figure 5B Shown according to Figure 4 400 by the UE. Result 510 shows a time period exceeding 40 seconds. For each PCI value received by the UE, the time period associated with the physical cell is also shown. After approximately 40 seconds have passed, the UE determines at a time corresponding to entry 512 that the amount of change for the PCI value indicates that high mobility mode is occurring. The UE enters high mobility mode and immediately changes to LTE mode using the LTE network. For high mobility mode, the BWP switching timer value is set to 0 seconds.

[0062] Figure 6 An example of a method for BWP load balancing includes a UE 602 (e.g., similar to Figure 1 UE 102) and network node 604 (e.g., similar to Figure 1 104). In this example, the UE is in a low throughput usage scenario, but may overload the small BWP. In some implementations, the UE will be downgraded to LTE as soon as a load balancing scenario is detected by the UE. In some implementations, a UE that is not using a high throughput BWP can switch back and forth between a large BWP and a small BWP for load balancing. The network switches the UE from a large BWP to a small BWP because the UE does not use high throughput. The UE saves power by switching to a small BWP. In some implementations, the network switches the UE from a small BWP to a large BWP because the service capacity of the small BWP is exceeded. The switching of the UE to the large BWP controls the load balancing in the network. When switching from a large BWP to a small BWP, the UE stops the BWP switching timer. When switching from a small BWP to a large BWP, the UE restarts the BWP switching timer. For scenarios where the UE is highly mobile (e.g., high-speed trains), many users stay on the same cell (e.g., on a small BWP), which triggers a load balancing process performed by the network. Even if the UE is only using low-throughput services, the UE switches from the small BWP to the large BWP. In another example, in a densely populated area (e.g., a shopping mall in a city), the UE may unintentionally stay on an overloaded cell and not switch to the small BWP to save power. To overcome this, the UE is configured to reduce priority to LTE when the NW load balancing process is initiated.

[0063] Environment 600 shows the interaction of a UE 602 and a base station 604 configured for load balancing. UE 602 is using a low throughput service 606. Base station 604 determines that an overload is occurring 608 on a small BWP. The base station transmits an instruction 612 for UE 602 to switch to the small BWP, even though the UE is not using a high throughput service. UE 602 receives instruction 612 and resets BWP switch timer 610. To load balance the BWPs, network 604 transmits instruction 616 to switch UE 602 to a large BWP. UE 602 receives instruction 616 and resets BWP switch timer 614. Because UE 602 has reset the BWP switch timer using instructions 610 and 614, the BWP switch timer does not expire and UE 602 does not switch to LTE mode. If the network 604 transmits another instruction 620 to switch the UE 602 to the small BWP before the BWP switching timer expires (e.g., within 15 seconds), the UE again resets 618 the BWP switching timer. The network 604 again transmits an instruction 624 for the UE 602 to switch to the large BWP for load balancing. The UE 602 again resets 622 the switching timer. Because the UE 602 is in a load balancing scenario, the UE 602 cannot use the LTE network to downgrade to LTE mode unless the BWP switching timer is adjusted when the UE detects the load balancing mode.

[0064] Fig. 7A An example is shown for responding to a request by a network (e.g., Figure 1 Base station 104 or Figure 6 604) and the BWP load balancing performed by the UE (e.g., Figure 1 UE 102 and / or Figure 6 602) performs SA switching. To perform process 700, the UE detects that the network is load balancing the UE on the network. The UE operates in SA mode (702). The UE is configured to determine whether to change from SA mode to LTE mode based on the current bandwidth. In a first case, the UE determines (704) that the FR1 or FR2 bandwidth is less than or equal to a specific threshold. For example, the bandwidth threshold may be 20 megahertz (MHz), 25 MHz...40 MHz, or a similar value. If the bandwidth is less than or equal to the threshold, the UE determines whether the UE is operating in high throughput mode or low throughput mode. If the UE determines (706) that the UE is operating in high throughput mode, the UE is configured to perform (708) a BWP switch to a large BWP as indicated by the network for load balancing. If the UE determines (710) that the UE is operating in low throughput mode, the UE switches (712) to a large BWP for load balancing as indicated by the network. The UE maintains a counter value (in Figure 6The counter value Y represents the number of unexpected instructions for BWP switching from a small BWP to a large BWP. In this example, the unexpected instructions represent instructions that are not included in the nominal network behavior (e.g., instructions representing abnormal network behavior). In response to each instance of an instruction to switch from a small BWP to a large BWP received from the network, the UE increments (714) the value of the counter. When the counter value exceeds a threshold value N within an evaluation time period T, the UE determines (716) that the network is performing load balancing for the UE. The value N can be configured by the UE based on a heuristic process. When the UE determines that the network is performing load balancing, the UE is configured to use the LTE network to reduce priority (718) to and switch from SA mode to LTE mode.

[0065] In some embodiments, the UE determines (720) that the UE is operating using a large BWP. For example, the UE determines in SA mode that the FR1 / FR2 bandwidth is above a threshold (e.g., 40 MHz). If the UE determines (722) that the UE is operating in high throughput mode, the UE remains (724) in SA mode using a large BWP. If the UE determines (726) that the UE is not using a high throughput service or is not in high throughput mode, the UE is configured to start or restart (728) a BWP switching timer (e.g., under 15 seconds). The UE determines (730) whether to stay in SA mode or switch to LTE mode. If the network switches to a small BWP by the network before the UE switching timer expires or the UE is handed over to a new cell by the network, the UE does not switch to the LTE network, but stays in SA mode. The UE tests the load balancing scenario again (e.g., by returning to step 702). If the BWP switching timer expires, the UE switches (732) to LTE mode and uses the LTE network.

[0066] In general, for process 700, the threshold N of the load balancing counter is configurable. The value N can be adjusted based on a machine learning model or can be trained using data collected from many instances of load balancing of UEs by the network. In general, the network supports BWP switching by the UE, and the network configures multiple BWPs for each UE.

[0067] Figure 7B An example is shown for use by a UE (eg, Figure 1102) performs SA switching for BWP load balancing. The load balancing mode is triggered for switching from a small BWP to a large BWP. Generally speaking, even in the absence of high throughput, the load balancing mode will not be triggered for BWP switching from a large BWP to a small BWP. Generally speaking, the load balancing mode is for BWP switching between a large BWP and a small BWP and occurs when the UE is in low throughput. For the load balancing mode of process 750, the network supports BWP switching and the network has configured multiple BWPs to the UE. In this process 750 and for Table 2 below, X represents the number of BWP switchings that occur from a large BWP to a small BWP. Y represents the number of BWP switchings from a small BWP to a large BWP. T represents the length of the evaluation time period (e.g., in seconds). When the function of X, Y and T is positive (e.g., F(X, Y, T)>0), the UE is configured to enter the load balancing mode. Generally speaking, the function F(X, Y, T) is dynamic and evaluates the BWP switching frequency within T.

[0068] Process 750 includes determining the BWP used by the UE when the UE is in (752) standalone mode. In process 750, if the UE is using (754) a small BWP (e.g., less than or equal to 40 MHz), the UE stays (756) in SA mode. Process 750 includes determining (758) that the UE is in a high throughput, low confidence scenario. Process 750 includes determining (760) whether the network has switched the UE from a small BWP to a large BWP. If the switch has not yet occurred, the UE is caused to stay (756) in SA mode. If the NW has switched the BWP for the UE, the process 750 includes incrementing (762) a BWP mismatch counter value Y. Process 750 includes determining (763) whether a load balancing function F(X, Y, T) is positive (e.g., >0). If the function is positive, the process 750 includes switching the UE to LTE mode (e.g., deprioritizing the UE to LTE). If the load balancing function F(X, Y, T) is not positive, process 750 monitors the BWP for the UE (at step 754).

[0069] During this process, the UE may be using a large BWP (e.g., greater than 40 MHz). If it is determined (766) that the UE is on a large BWP, process 750 includes determining (768, 772) whether the UE is in a high throughput scenario or in a low throughput scenario. If the UE is in a high throughput scenario, the UE is configured to stay (770) on SA mode (e.g., using a large BWP). If the UE is not in a high throughput scenario, process 750 includes starting or restarting (774) a BWP switching timer for the UE. Process 750 includes monitoring the UE to determine (776) whether the BWP for the UE has been switched from the network side before the BWP switching timer has expired. If the NW has switched the BWP for the UE, the BWP switching value X is incremented (780). If the NW has not yet switched the BWP for the UE, the UE is deprioritized to LTE mode (e.g., switched to LTE).

[0070] Table 2 shows example values ​​for T, X, Y, and F(X, Y, T) and the resulting actions performed by the UE. When F(X, Y, T) is non-positive, the UE is operating in non-load balancing mode. For example, if no BWP switching occurs and if the switching timer expires, the UE operates in normal mode. If there is an unexpected switching from a large BWP (BWP 2) to a small BWP (BWP 1), the UE enters load balancing mode. In addition, if there is an unexpected switching between a large BWP and a small BWP by the network, the UE enters load balancing mode.

[0071] Table 2: Scenarios of load balancing mode for UE.

[0072] Cell Mode T X Y F(X,Y,T) Notes Normal Mode 15 0 0 0 No Action Normal Mode 15 1 0 0 Currently BWP has 15 timers that are covered Load Balancing Mode 15 0 1 1 Unexpected switch from BWP#2 to BWP#1 Load Balancing Mode 15 >＝1 >＝1 1 Unexpected switch between BWP#2 and BWP#1

[0073] Figure 3A , Figure 3B , Figure 4 , Fig. 7A and Figure 7B The example processes 300, 350, 400, 700, and 750 shown may be modified or reconfigured to include additional, fewer, or different steps ( FIG. 3A to FIG. 3B , Figure 4 or FIG. 7A to FIG. 7B ), these steps may be performed in the order shown or in a different order.

[0074] Figure 8 UE 800 according to some embodiments is illustrated. UE 800 may be similar to Figure 1 UE 102 and is substantially interchangeable therewith.

[0075] UE 800 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, voltage / current meter, actuator, etc.), video monitoring / surveillance equipment (e.g., camera, camcorder, etc.), a wearable device (e.g., a smart watch), or a loose IoT device.

[0076] UE 800 may include a processor 802, an RF interface circuit 804, a memory / storage 806, a user interface 808, a sensor 810, a driver circuit 812, a power management integrated circuit (PMIC) 814, an antenna structure 816, and a battery 818. The components of UE 800 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logic component, hardware, software, firmware, or a combination thereof. Figure 8 The block diagram of UE 800 is intended to show a high-level view of certain of the components of UE 800. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0077] Components of UE 800 may be coupled to various other components via one or more interconnects 820, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connection, etc., which allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0078] The processor 802 may include processor circuits such as a baseband processor circuit (BB) 822A, a central processor unit circuit (CPU) 822B, and a graphics processor unit circuit (GPU) 822C. The processor 802 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 806) to cause the UE 800 to perform operations as described herein.

[0079] In some embodiments, the baseband processor circuit 822A can access the communication protocol stack 824 in the memory / storage device 806 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 822A can access the communication protocol stack to perform the following operations: perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some embodiments, the PHY layer operation may be additionally / alternatively performed by components of the RF interface circuit 804. The baseband processor circuit 822A may generate or process a baseband signal or waveform carrying information in a 3GPP compatible network. In some embodiments, the waveform for NR may be based on cyclic prefix OFDM ("CP-OFDM") in the uplink or downlink, and discrete Fourier transform spread OFDM ("DFT-S-OFDM") in the uplink.

[0080] The memory / storage device 806 may include one or more non-transitory computer-readable media, which include instructions (e.g., communication protocol stack 824) that can be executed by one or more processors in the processor 802 to enable the UE 800 to perform various operations described herein. The memory / storage device 806 includes any type of volatile or non-volatile memory that can be distributed throughout the UE 800. In some embodiments, some of the memory / storage devices in the memory / storage device 806 can be located on the processor 802 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 806 are located outside the processor 802 but can be accessed via a memory interface. The memory / storage device 806 may include any suitable volatile or non-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, solid-state memory, or any other type of memory device technology.

[0081] The RF interface circuit 804 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 800 to communicate with other devices through a radio access network. The RF interface circuit 804 may include various elements arranged in a transmit path or a receive path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0082] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 816 and continue to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 802.

[0083] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 816.

[0084] In various embodiments, the RF interface circuit 804 can be configured to send / receive signals in a manner compatible with NR access technology.

[0085] Antenna 816 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 816 may have an antenna panel that is omnidirectional, directional, or a combination thereof to achieve beamforming and multiple input / multiple output communications. Antenna 816 may include a microstrip antenna, a printed antenna manufactured on the surface of one or more printed circuit boards, a patch antenna, a phased array antenna, etc. Antenna 816 may have one or more panels that are designed for a specific frequency band including a band in FR1 or FR2.

[0086] The user interface 808 includes various input / output (I / O) devices designed to enable a user to interact with the UE 800. The user interface 808 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual components for accepting input, including in particular one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touch pad, a touch screen, a microphone, a scanner, or a headset, etc. The output device circuit includes any physical or virtual components for displaying information or otherwise delivering information (such as sensor readings, actuator positions, or other similar information). The output device circuit may include any number or combination of audio or visual displays, including in particular one or more simple visual outputs / indicators (e.g., binary state indicators, such as light emitting diodes (LEDs)) and multi-character visual outputs), or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays "LCDs", LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 800.

[0087] Sensor 810 may include a device, module, or subsystem that is designed to detect events or changes in its environment and send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, three-axis gyroscope, or magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

[0088] The driver circuit 812 may include software elements and hardware elements for controlling specific devices embedded in the UE 800, attached to the UE 800, or otherwise communicatively coupled to the UE 800. The driver circuit 812 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in the UE 800 or connected to the UE. For example, the driver circuit 812 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor circuit 828 and controlling and allowing access to the sensor circuit 828, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0089] The PMIC 814 may manage the power provided to various components of the UE 800. Specifically, with respect to the processor 802, the PMIC 814 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0090] In some embodiments, the PMIC 814 can control or otherwise be part of various power saving mechanisms of the UE 800, including DRX, as discussed herein. The battery 818 can power the UE 800, but in some examples, the UE 800 can be installed in a fixed location and can have a power source coupled to the power grid. The battery 818 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 818 can be a typical lead-acid automotive battery.

[0091] Fig. 9An access node 900 (e.g., a base station or gNB) is shown according to some embodiments. Access node 900 may be similar to base station 104 and substantially interchangeable therewith. Access node 900 may include a processor 902, RF interface circuitry 904, core network (CN) interface circuitry 906, memory / storage circuitry 908, and antenna structures 910.

[0092] The components of the access node 900 may be coupled to various other components via one or more interconnects 912. The processor 902, RF interface circuitry 904, memory / storage circuitry 908 (including a communication protocol stack 914), antenna structures 910, and interconnects 912 may be similar to those of reference 1. Figure 8 Like-named elements are shown and described.For example, processor 902 may include processor circuits such as, for example, baseband processor circuit (BB) 916A, central processor unit circuit (CPU) 916B, and graphics processor unit circuit (GPU) 916C.

[0093] The CN interface circuit 906 may provide connectivity to a core network (e.g., a 5GC using a 5th Generation Core Network (5GC) compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol). Network connectivity may be provided to / from the access node 900 via optical fiber or wireless backhaul. The CN interface circuit 906 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 906 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0094] As used herein, the terms "access node", "access point", etc. may be described as equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node", etc. may refer to an access node 900 (e.g., a gNB) operating in an NR or 5G system, and the terms "E-UTRAN node", etc. may refer to an access node 900 (e.g., an eNB) operating in an LTE or 4G system. According to various embodiments, the access node 900 may be implemented as a dedicated physical device such as a macrocell base station and / or one or more of a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0095] In some embodiments, all or part of the access node 900 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN functional splitting, such as PDCP splitting, where the RRC and PDCP layers are operated by the CRAN / vBBUP, and other L2 protocol entities are operated by the access node 900; MAC / PHY splitting, where the RRC layer, PDCP layer, RLC layer, and MAC layer are operated by the CRAN / vBBUP, and the PHY layer is operated by the access node 900; or "lower PHY" splitting, where the RRC layer, PDCP layer, RLC layer, MAC layer, and upper portion of the PHY layer are operated by the CRAN / vBBUP, and the lower portion of the PHY layer is operated by the access node 900.

[0096] In the V2X scenario, the access node 900 may be an RSU or act as an RSU. The term "road side unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationed (or relatively stationed) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on.

[0097] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below in the example section.

[0098] Example

[0099] In the following sections, additional exemplary embodiments are provided.

[0100] Embodiment 1 includes a method having operations, the operations including: determining a cell of a network to which a user equipment (UE) uses a connection in a standalone (SA) mode; determining a bandwidth part (BWP) of the connection; based on determining the BWP of the connection, accessing a physical cell identifier (PCI) list associated with the UE within a time period, the PCI list including a number of PCI values; comparing the number of PCI values ​​with a threshold number; assigning a timeout value to a BWP switching timer based on the comparison and the duration of the time period; starting the BWP switching timer; in response to determining that the BWP switching timer has reached the timeout value without a handover of the UE to a different cell of the network, causing the UE to continue operating using the SA mode; and in response to determining that the handover of the UE to the different cell of the network occurs before the BWP switching timer reaches the timeout value, causing the UE to switch to an LTE mode (e.g., LTE).

[0101] Embodiment 2 may include operations according to embodiment 1, wherein comparing the number of PCI values ​​with a threshold number includes: in response to determining that the number of PCI values ​​is equal to or exceeds the threshold number, assigning a timeout value to the BWP switching timer based on a ratio of the number of PCI values ​​to the duration of the time period in seconds.

[0102] Embodiment 3 may include operations according to Embodiment 1 or 2, wherein comparing the number of PCI values ​​to a threshold number includes: in response to determining that the number of PCI values ​​does not equal or exceed the threshold number, assigning a standard timeout value to the BWP switch timer.

[0103] Embodiment 4 may include operations according to embodiments 1 to 3, wherein the standard timeout value is 15 seconds.

[0104] Embodiment 5 may include operations according to embodiments 1 to 4, wherein the operations further include determining that the UE is in a high throughput scenario or a high confidence scenario; and in response to determining that the UE is in a high throughput scenario or a high confidence scenario, causing the UE to continue operating in the SA mode.

[0105] Embodiment 6 may include operations according to embodiments 1 to 5, the operations further comprising determining that the UE is in a low throughput scenario or a low confidence scenario; and in response to the determination, performing the access to the PCI list.

[0106] Embodiment 7 may include operations as in Embodiments 1 to 6, wherein determining the bandwidth part (BWP) of the connection comprises determining whether the UE is connected using a small BWP or a large BWP.

[0107] Embodiment 8 may include operation according to Embodiment 7, wherein the large BWP is greater than 40 MHz, and wherein the small BWP is less than or equal to 40 MHz.

[0108] Embodiment 9 may include operations according to embodiment 7, further comprising: in response to determining that the UE is connected using a small BWP, causing the UE to continue operating in the SA mode.

[0109] Embodiment 10 may include the operation according to embodiment 9, wherein the operation further includes: determining that the UE is in a high throughput scenario; detecting an instruction to switch from the small BWP to the large BWP; incrementing a BWP mismatch counter; determining whether a load balancing function is positive, the load balancing function being based on the BWP mismatch counter; in response to determining that the load balancing function is positive, switching the UE to operate in the LTE mode; and in response to determining that the load balancing function is not positive, causing the UE to continue to operate using the SA mode.

[0110] Embodiment 11 may include operations according to embodiments 7 to 10, the operations further including: in response to determining that the UE is connected using a large BWP, determining that the UE is not in a high throughput scenario; based on the determination, starting or restarting the BWP switching timer; in response to determining that the BWP switching timer has reached the timeout value without a handover of the UE to a different cell of the network, causing the UE to continue to operate using the SA mode; and in response to determining that the handover of the UE to the different cell of the network occurs before the BWP switching timer reaches the timeout value, causing the UE to switch to LTE.

[0111] Embodiment 12 may include operations according to embodiments 1 to 11, wherein when operating in the SA mode, the UE is configured to use a new radio (NR) network to send and receive control data and user data, and wherein when operating in the LTE mode, the UE is configured to use a long term evolution (LTE) network to send and receive control information, and use the NR network to send and receive user data.

[0112] Embodiment 13 may include operations as described in Embodiments 1 to 12, wherein the connection is a radio resource control (RRC) configured connection.

[0113] Embodiment 14 may include one or more non-transitory computer-readable media, wherein the one or more non-transitory computer-readable media include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described or related to any one of Embodiments 1 to 13 or any other method or process described herein.

[0114] Embodiment 15 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of a method according to or related to any of Embodiments 1 to 13, or any other method or process described herein.

[0115] Embodiment 16 may include methods, techniques or processes as described or related to any one of Embodiments 1 to 13, or portions or components thereof.

[0116] Embodiment 17 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or part thereof, described in or related to any one of Embodiments 1 to 13.

[0117] Embodiment 18 may include a signal as described or related to any one of Embodiments 1 to 13, or a portion or component thereof.

[0118] Embodiment 19 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or associated with any of Embodiments 1 to 13 or otherwise described in the present disclosure.

[0119] Embodiment 20 may include a signal encoded with data as described in or related to any one of Embodiments 1 to 13 or otherwise described in this disclosure, or a portion or component thereof.

[0120] Embodiment 21 may include a signal as described or related to any one of Embodiments 1 to 13 or otherwise described in the present disclosure using datagram, IE, packet, frame, segment, PDU or message encoding, or a portion or component thereof.

[0121] Embodiment 22 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, as described in or related to any one of Embodiments 1 to 13.

[0122] Embodiment 23 may include a computer program including instructions, wherein execution of the program by a processing element causes the processing element to implement a method, technique, or process, or a portion thereof, as described or related to any one of embodiments 1 to 13. The operations or actions performed by the instructions executed by the processing element may include a method according to any one of embodiments 1 to 13.

[0123] Embodiment 24 may include signals in a wireless network as shown and described herein.

[0124] Embodiment 25 may include a method of communicating in a wireless network as shown and described herein.

[0125] Embodiment 26 may include a system for providing wireless communication as shown and described herein. The operations or actions performed by the system may include a method according to any one of Embodiments 1 to 13.

[0126] Embodiment 27 may include an apparatus for providing wireless communication as shown and described herein. The operations or actions performed by the apparatus may include a method according to any one of Embodiments 1 to 13.

[0127] The previously described embodiments 1 to 13 can be implemented using the following: a computer-implemented method; a non-transitory computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system comprising a computer memory interoperably coupled to a hardware processor configured to execute the computer-implemented method or instructions stored on the non-transitory computer-readable medium.

[0128] A system (e.g., a base station, a device including one or more baseband processors, etc.) may be configured to perform a specific operation or the action by having software, firmware, hardware, or a combination thereof installed on the system that causes the system to perform the action in operation. The operation or action performed by the system may include a method according to any one of embodiments 1 to 13.

[0129] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of various embodiments.

[0130] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

[0131] It is well known that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

Claims

1. A method, comprising: determining a cell to which a user equipment (UE) is connected to a network using a connection in a standalone (SA) mode; determining a bandwidth part (BWP) of the connection; accessing a physical cell identifier (PCI) list associated with the UE within a time period based on determining the BWP for the connection, the PCI list comprising a number of PCI values; comparing the number of PCI values ​​to a threshold number; assigning a timeout value to a BWP switch timer based on the comparison and a duration of the time period; Starting the BWP switching timer; in response to determining that the BWP switch timer has reached the timeout value without a handover of the UE to a different cell of the network, causing the UE to switch to a long term evolution (LTE) mode and use a LTE network; as well as In response to determining that the handover of the UE to the different cell of the network occurs before the BWP switch timer reaches the timeout value, causing the UE to continue operating using the SA network.

2. The method of claim 1 , wherein comparing the number of PCI values ​​to a threshold number comprises: In response to determining that the number of PCI values ​​equals or exceeds the threshold number, a timeout value is assigned to the BWP switch timer based on a ratio of the number of PCI values ​​to the duration of the time period in seconds.

3. The method of claim 1 or 2, wherein comparing the number of PCI values ​​to a threshold number comprises: In response to determining that the number of PCI values ​​does not equal or exceed the threshold number, a standard timeout value is assigned to the BWP switch timer.

4. The method according to any one of claims 1 to 3, wherein the standard timeout value is 15 seconds.

5. The method according to any one of claims 1 to 4, further comprising: Determining that the UE is in a high throughput scenario or a high confidence scenario; as well as In response to determining that the UE is in a high throughput scenario or a high confidence scenario, the UE is caused to continue operating in the SA mode.

6. The method according to any one of claims 1 to 5, further comprising: Determining that the UE is in a low throughput scenario or a low confidence scenario; as well as Responsive to the determining, the accessing of the PCI list is performed.

7. The method according to any one of claims 1 to 6, wherein determining the bandwidth part (BWP) of the connection comprises determining whether the UE is connected using a small BWP or a large BWP.

8. The method of claim 7, wherein the large BWP is greater than 40 megahertz (MHz), and wherein the small BWP is less than or equal to 40 MHz.

9. The method according to claim 7, further comprising: In response to determining that the UE is connected using a small BWP, causing the UE to continue operating in the SA mode.

10. The method according to claim 9, further comprising: Determining that the UE is in a high throughput scenario; detecting an instruction to switch from the small BWP to the large BWP; Increment the BWP mismatch counter; determining whether a load balancing function is positive, the load balancing function being based on the BWP mismatch counter; In response to determining that the load balancing function is positive, switching the UE to operate in the LTE mode; and In response to determining that the load balancing function is not positive, the UE is caused to continue operating using the SA mode.

11. The method according to claim 7, further comprising: In response to determining that the UE is connected using a large BWP, determining that the UE is not in a high throughput scenario; Based on the determination, starting or restarting the BWP switching timer; In response to determining that the BWP switching timer has reached the timeout value without a handover of the UE to a different cell of the network, causing the UE to switch to LTE mode and use an LTE network; as well as In response to determining that the handover of the UE to the different cell of the network occurs before the BWP switch timer reaches the timeout value, causing the UE to continue operating using the SA network.

12. A method according to any one of claims 1 to 11, wherein when operating in the SA mode, the UE is configured to use a New Radio (NR) network to send and receive control data and user data, and wherein when operating in the LTE mode, the UE is configured to use a Long Term Evolution (LTE) network to send and receive control information and user data.

13. The method according to any one of claims 1 to 12, wherein the connection is a Radio Resource Control (RRC) configured connection.

14. A system comprising one or more computing units and one or more storage units having stored thereon instructions operable when executed by the system to perform operations comprising: determining a cell to which a user equipment (UE) is connected to a network using a connection in a standalone (SA) mode; determining a bandwidth part (BWP) of the connection; accessing a physical cell identifier (PCI) list associated with the UE within a time period based on determining the BWP for the connection, the PCI list comprising a number of PCI values; comparing the number of PCI values ​​to a threshold number; assigning a timeout value to a BWP switch timer based on the comparison and a duration of the time period; Starting the BWP switching timer; In response to determining that the BWP switching timer has reached the timeout value without a handover of the UE to a different cell of the network, causing the UE to switch to an LTE network; as well as In response to determining that the handover of the UE to the different cell of the network occurs before the BWP switch timer reaches the timeout value, causing the UE to continue operating using the SA network.

15. A non-transitory computer storage medium encoded with instructions executable by one or more processors to cause the one or more processors to perform the method of any one of claims 1 to 14.

16. A device, comprising: One or more processors, and a memory storing instructions executable by the one or more processors to cause the one or more processors to perform the method according to any one of claims 1 to 14.

17. One or more processors of a first user equipment (UE), the one or more processors configured to cause the first UE to perform operations comprising: determining a cell to which a user equipment (UE) is connected to a network using a connection in a standalone (SA) mode; determining a bandwidth part (BWP) of the connection; accessing a physical cell identifier (PCI) list associated with the UE within a time period based on determining the BWP for the connection, the PCI list comprising a number of PCI values; comparing the number of PCI values ​​to a threshold number; assigning a timeout value to a BWP switch timer based on the comparison and a duration of the time period; Starting the BWP switching timer; in response to determining that the BWP switch timer has reached the timeout value without a handover of the UE to a different cell of the network, causing the UE to switch to a long term evolution (LTE) mode and use a LTE network; as well as In response to determining that the handover of the UE to the different cell of the network occurs before the BWP switch timer reaches the timeout value, causing the UE to continue operating using the SA network.

18. The one or more processors of claim 17, wherein comparing the number of PCI values ​​to a threshold number comprises: In response to determining that the number of PCI values ​​equals or exceeds the threshold number, a timeout value is assigned to the BWP switch timer based on a ratio of the number of PCI values ​​to the duration of the time period in seconds.

19. The one or more processors of claim 17 or 18, wherein comparing the number of PCI values ​​to a threshold number comprises: In response to determining that the number of PCI values ​​does not equal or exceed the threshold number, a standard timeout value is assigned to the BWP switch timer.

20. The one or more processors of any one of claims 17 to 19, the operations further comprising: Determining that the UE is in a high throughput scenario or a high confidence scenario; as well as In response to determining that the UE is in a high throughput scenario or a high confidence scenario, the UE is caused to continue operating in the SA mode.

Images