User equipment operation in mobility scenarios

Abstract

In a mobility scenario, a user equipment (UE) may enter a flight mode in which the UE has limited connectivity or no connectivity to a network. Cell selection latency after termination of the flight mode may result in a delay in providing network or communication services. Some aspects described herein enable reduction of latency associated with cell selection after operation in a mobility scenario. For example, a UE may determine that the UE is operating in a mobility scenario, and perform a receive-only cell selection procedure. Additionally or alternatively, the UE may predict a destination associated with a mobility scenario and may identify a list of frequency bands for performing a cell selection procedure. In this manner, when the UE exits the mobility scenario, the UE reduces the time to successfully complete cell selection.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 184,464, filed March 15, 2023, entitled "USER EQUIPMENT OPERATION INMOBILITY SCENARIOS," which is assigned to the assignee of this application. The disclosure of the prior application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication, and specifically to technologies and apparatus for operating user equipment in mobile scenarios. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with network nodes via downlink and uplink communication. "Downlink" (or "DL") refers to the communication link from the network node to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, etc.).

[0006] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. 5G (which may be referred to as New Radio (NR)) is an enhancement set of the LTE mobile standard issued by 3GPP. 5G is designed to better support mobile broadband internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) (CP-OFDM) on the downlink, and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation to improve spectral efficiency, reduce costs, improve service, utilize new spectrum, and better integrate with other open standards. Further improvements to 4G, 5G, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0007] In mobility scenarios, a user equipment (UE) can enter a mobility mode, in which the UE has limited or no connectivity to a network. For example, when the UE is operating on an aircraft (e.g., an airplane), the UE can operate in "flight mode," in which the UE is not connected to a cellular network, but the UE remains powered on and can use local area network (LAN) connections, such as Wi-Fi or Bluetooth. When the mobility scenario ends, the UE can transition from mobility mode to normal operating mode. For example, when the aircraft lands at its destination, the UE can exit flight mode and attempt to connect to a cellular network at the destination. Cell selection latency can cause delays in providing network or communication services. For example, cell selection latency after the aircraft lands can cause a wait of two minutes or more before a cellular connection is established.

[0008] Similar mobility modes and cell connectivity scenarios can exist in conjunction with operations in other mobility scenarios (such as operations in vehicles, on trains, or on ships). For example, when operating on a ship in an area with limited or no cellular coverage, a user can put the UE into flight mode to reduce the use of power resources associated with attempting to identify cellular connections in areas without connectivity (e.g., when traveling at sea). In this case, when the ship arrives at port, the user can put the UE out of flight mode and attempt to acquire a cellular connection in the port. Additionally or alternatively, when traveling at high speeds on a train, repeated handovers between different cells can lead to overuse of power resources, so the user can use flight mode until the train stops at the platform to avoid drawing power from the UE.

[0009] Some aspects described herein enable the reduction of latency associated with cell selection after operation in a mobility scenario. For example, the UE may determine that it is operating in a mobility scenario (e.g., based at least in part on the determination that flight mode is active) and perform a receive-only cell selection procedure (e.g., receive-only search). In this way, when the UE exits the mobility scenario (e.g., turns off flight mode), the UE reduces the time required to complete the receive and transmit cell selection procedures. Additionally or alternatively, the UE may predict the destination associated with the mobility scenario (e.g., based at least in part on sensor data from the UE's sensors or positioning data from satellites) and may identify a list of frequency bands for performing the cell selection procedure. In this way, when the UE exits the mobility scenario, the UE reduces the time required to successfully select a frequency band for cell selection at the destination in which it is operating.

[0010] Some aspects described herein relate to a method of wireless communication performed by a UE. This method may include: receiving sensor data or other data associated with a characteristic associated with a mobility scenario. This method may also include: performing at least a portion of a cell selection process based at least in part on the characteristic associated with the mobility scenario.

[0011] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive sensor data or other data associated with characteristics identifying a mobility scenario. The one or more processors may be configured to perform at least a portion of a cell selection process based at least in part on the characteristic associated with the mobility scenario.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to receive sensor data or other data associated with characteristics identifying a mobility scenario. When executed by one or more processors of the UE, the set of instructions enables the UE to perform at least a portion of a cell selection process, at least partially based on the characteristic associated with the mobility scenario.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving sensor data or other data associated with characteristics related to a mobility scenario. The apparatus may include components for performing at least a portion of a cell selection process based at least in part on the characteristics associated with the mobility scenario.

[0014] The general terms include, as fully described with reference to the accompanying drawings and description and illustrated by reference to the accompanying drawings and description, methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment, network entities, network nodes and / or processing systems.

[0015] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and operation) and their associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Attached Figure Description

[0016] Figure 1 This is a diagram illustrating an example of a wireless network.

[0017] Figure 2 This is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network.

[0018] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0019] Figure 4 These are illustrations of examples of regenerative satellite deployment and transparent satellite deployment in non-terrestrial networks.

[0020] Figure 5A and Figure 5B This is a diagram illustrating an example of UE operation in a mobility scenario based on this disclosure.

[0021] Figure 6 This is a flowchart of an example method for wireless communication.

[0022] Figure 7 This is a diagram of an example device for wireless communication according to the present disclosure.

[0023] Figure 8 This is a diagram illustrating an example of a hardware implementation of a device for employing a processing system according to the present disclosure. Detailed Implementation

[0024] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as a representation of a configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0025] Various apparatuses and methods will now be used to present several aspects of a telecommunications system. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0026] By way of example, an element, any part of an element, or any combination of elements may be implemented using a "processing system" comprising one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic units, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system can execute software. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other names.

[0027] Therefore, in one or more example embodiments, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium accessible to a computer. By way of example, and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), compact disc ROM (CD-ROM), or other optical disc storage devices, magnetic disk storage devices, or other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures.

[0028] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0029] Figure 1 This is an illustration of an example of a wireless network 100. Wireless network 100 can be a 5G (e.g., NR) network or a 4G (e.g., LTE) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., LTE) network, etc. Wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other entities. Network node 110 is an example of a network node communicating with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0030] In some examples, network node 110 is or includes network nodes (such as RUs) that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes (such as DUs) that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes (such as CUs) that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, network node 110 may include NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, Transmit / Receive Points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 can interconnect with each other or to one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0031] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3GPP (3rd Generation Partnership Project), depending on the context in which the term is used, the term "cell" may refer to the coverage area of ​​network node 110 or a network node subsystem serving that coverage area. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, or another type of cell. A macrocell may cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a residential area) and may allow restricted access by UE 120 associated with that femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. Figure 1In the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. Network nodes can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0032] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network node" may refer to a CU, DU, RU, near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. In this way, a single device can include more than one base station.

[0033] Wireless network 100 may include one or more relay stations. A relay station is a network node that receives data transmissions from an upstream node (e.g., network node 110 or UE 120) and transmits data to a downstream node (e.g., UE 120 or network node 110). A relay station may be a UE 120 capable of relaying transmissions to other UE 120s. Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 for relay communication may be referred to as a relay station, relay base station, relay network node, relay node, or relay, etc.

[0034] The wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different effects on interference in the wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0035] Network controller 130 may be coupled to or communicate with a group of network nodes 110, and may provide coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul or midhaul link. Network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul link. In some aspects, network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0036] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), an in-vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, a UE function of a network node, or any other suitable device configured to communicate via wireless or wired media.

[0037] Some UEs 120 may be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, or location tags that can communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UEs 120 may be included within a housing that houses the components of the UE 120, such as processor components or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0038] Generally, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology or air interface. A frequency can also be referred to as a carrier or frequency channel. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0039] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary for communication with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0040] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. A similar naming issue sometimes occurs with FR2, which is often (interchangeably) referred to in documents and articles as the "millimeter wave" band, although this is different from the Extremely High Frequency (EHF) band (30GHz-300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0041] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands for these IF bands as the frequency range designation FR3 (7.125GHz-24.25GHz). Bands falling within FR3 can inherit FR1 or FR2 characteristics, thus effectively extending the features of FR1 or FR2 into the IF band. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6GHz. For example, three higher operating bands have been designated as the frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0042] In light of these examples, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include intermediate frequency bands. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that may include intermediate frequency bands, frequencies within FR2, FR4, FR4-a, FR4-1, or FR5, or frequencies within the EHF band. It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0043] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive sensor data or other data associated with characteristics that identify mobility scenarios; and perform at least a portion of the cell selection process based at least in part on the characteristics associated with the mobility scenarios. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0044] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0045] Figure 2 This is a diagram illustrating example 200 of communication between network node 110 and UE 120 in wireless network 100. Network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). Network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and modems 232. In some examples, network node 110 may include an interface, communication components, or another component facilitating communication with UE 120 or another network node. Some network nodes 110 may not include radio frequency components facilitating direct communication with UE 120, such as one or more CUs or one or more DUs.

[0046] At network node 110, transmitting processor 220 can receive data from data source 212 intended for use by UE 120 (or a group of UEs 120). Transmitting processor 220 can use one or more Channel Quality Indicators (CQIs) received from UE 120 to select one or more Modulation and Decoding Schemes (MCSs) for that UE 120. Network node 110 can use the MCS selected for UE 120 to process (e.g., encode and modulate) the data for UE 120 and can provide data symbols to UE 120. Transmitting processor 220 can process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 220 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, where applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream to obtain a downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0047] At UE 120, an array of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 or other network nodes 110, and can provide a set of received signals (e.g., R received signals) to an array of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal to obtain an input sample. Each modem 254 can use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. The receive (RX) processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine Reference Signal Received Power (RSRP) parameters, Received Signal Strength Indicator (RSSI) parameters, Reference Signal Received Quality (RSRQ) parameters, or CQI parameters, etc. In some examples, one or more components of UE 120 may be included in housing 284.

[0048] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, for example, in a core network. Network controller 130 may communicate with network node 110 via communication unit 294.

[0049] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or be included in the following: one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, collections of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), coplanar antenna element collections, non-coplanar antenna element collections, or coupled to one or more transmitting or receiving components (such as...). Figure 2 One or more antenna elements (one or more components).

[0050] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, or CQI) from controller / processor 280. The transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 can be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, the modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the processes described herein.

[0051] At network node 110, uplink signals from UE 120 or other UEs may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected by MIMO detector 236 where applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted via UE 120. Receiver processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the processes described herein.

[0052] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120 and / or Figure 2Any other components may perform one or more techniques associated with UE operation in mobility scenarios, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 6 The operation of method 600 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions may, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, transformation, and / or interpretation), cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example... Figure 6 Method 600 and / or other procedures as described herein. In some examples, execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, etc.

[0053] In some aspects, the UE (e.g., UE 120) includes components for receiving sensor data or other data associated with characteristics related to mobility scenarios; and / or components for performing at least a portion of a cell selection process based at least in part on characteristics associated with mobility scenarios. Components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0054] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above for these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described for transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0055] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0056] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in aggregated or decomposed architectures. For example, base stations (such as Node B (NB), evolved NB (eNB), NR base stations, 5G NB, access points (APs), TRPs, or cells, etc.) or one or more units (or components) performing base station functions can be implemented as aggregated base stations (also known as standalone base stations or monolithic base stations) or decomposed base stations. "Network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0057] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0058] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed individually. Decomposed base stations can include functionality implemented by two or more units across various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0059] Figure 3This is an illustration of an example disaggregated base station architecture 300 according to this disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0060] Each unit in the cells (including CU 310, DU 330, RU 340), as well as the near-RT RIC 325, non-RT RIC 315, and SMO frame 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cell, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more units in other cells via transmission media. In some examples, each unit in the cell may include a wired interface and a wireless interface configured to receive signals or transmit signals to one or more units in other cells via a wired transmission media, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more units in other cells via a wireless transmission media, or both.

[0061] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). The CU 310 can be implemented to communicate with the DU 330 for network control and signaling purposes, as needed.

[0062] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0063] Each RU 340 can implement lower-layer functionality. In some deployments, an RU 340 controlled by a DU 330 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splitting (e.g., function splitting defined by 3GPP) (such as lower-layer function splitting). In this architecture, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as vRAN architecture).

[0064] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTTRIC 325. In some implementations, the SMO framework 305 may communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0065] The non-RT RIC 315 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data collection and actions through an interface (e.g., via an E2 interface) that connects one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0066] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0067] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0068] Figure 4 These are illustrations of Example 400, which illustrates the deployment of regenerative satellites in a non-terrestrial network, and Example 410, which illustrates the deployment of transparent satellites.

[0069] Example 400 illustrates a regenerative satellite deployment. In Example 400, UE 120 is served by satellite 420 via serving link 430. For example, satellite 420 may include network node 110 (e.g., network node 110a) or gNB. In some aspects, satellite 420 may be referred to as a non-terrestrial base station, a regenerative repeater, or an onboard processing repeater. In some aspects, satellite 420 may demodulate uplink radio frequency signals and may modulate baseband signals derived from uplink radio signals to generate downlink radio frequency transmissions. Satellite 420 may transmit downlink radio frequency signals over serving link 430. Satellite 420 may provide cell coverage for UE 120.

[0070] Example 410 illustrates a transparent satellite deployment, which may also be referred to as a bend-tube satellite deployment. In Example 410, UE 120 is served by satellite 440 via serving link 430. Satellite 440 may be a transparent satellite. Satellite 440 may relay signals received from gateway 450 via feed link 460. For example, the satellite may receive uplink RF transmissions and may transmit downlink RF transmissions without demodulating the uplink RF transmissions. In some aspects, the satellite may convert the frequency of the uplink RF transmissions received on serving link 430 to the frequency of the uplink RF transmissions on feed link 460, and may amplify and / or filter the uplink RF transmissions. In some aspects, UE 120 shown in Examples 400 and 410 may be associated with Global Navigation Satellite System (GNSS) capability or Global Positioning System (GPS) capability, but not all UEs have such capabilities. Satellite 440 may provide cell coverage for UE 120.

[0071] Service link 430 may include a link between satellite 440 and UE 120, and may include one or more of an uplink or a downlink. Power supply link 460 may include a link between satellite 440 and gateway 450, and may include one or more of an uplink (e.g., from UE 120 to gateway 450) or a downlink (e.g., from gateway 450 to UE 120).

[0072] Due to the movement of satellites 420 and 440, and the potential movement of UE 120, feed link 460 and service link 430 may each experience Doppler effects. These Doppler effects may be significantly greater than those in the terrestrial network. The Doppler effects on feed link 460 can be compensated for to some extent, but may still be associated with a certain amount of uncompensated frequency error. Furthermore, gateway 450 may be associated with residual frequency errors, and / or satellites 420 / 440 may be associated with onboard frequency errors. These sources of frequency errors can cause the downlink frequency received at UE 120 to deviate from the target downlink frequency.

[0073] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0074] In mobility scenarios, the UE can enter mobility mode, in which the UE has limited or no connectivity to the network. For example, when the UE is operating on an aircraft (e.g., an airplane), the UE can operate in "Airplane Mode" ("APM"), in which the UE is not connected to the cellular network, but the UE remains powered on and can use local area network (LAN) connections, such as Wi-Fi or Bluetooth. When the mobility scenario ends, the UE can transition from mobility mode to normal operating mode. For example, when the aircraft lands at its destination, the UE can exit airplane mode and attempt to connect to the cellular network at the destination. Cell selection latency can cause delays in providing network or communication services. For example, cell selection latency after the aircraft lands can cause a wait of two minutes or more before establishing a cellular connection.

[0075] Similar mobility modes and cell connectivity scenarios can exist in conjunction with operations in other mobility scenarios (such as operations in vehicles, on trains, or on ships, etc.). For example, when operating on a ship in an area with limited or no cellular coverage, a user may put the UE into flight mode to reduce the use of power resources associated with attempting to identify cellular connections in areas without connectivity (e.g., when traveling at sea). In this case, when the ship arrives at port, the user may put the UE out of flight mode and attempt to acquire a cellular connection in the port. Additionally or alternatively, when traveling at high speeds on a train or in a vehicle, repeated handovers between different cells can lead to overuse of power resources, so the user may use flight mode until the train or vehicle stops to avoid drawing power from the UE. In these examples, when flight mode (or another type of mobility mode) is deactivated, there may be excessive latency associated with identifying the set of frequency bands used for the cell selection process and performing that cell selection process.

[0076] Some specific implementations described herein provide techniques for UE operation in conjunction with mobility scenarios. For example, the UE may determine that it is operating in a mobility scenario (e.g., at least in part based on the determination that flight mode is active) and perform a receive-only cell selection procedure (e.g., receive-only search). During the receive-only cell selection procedure, the UE activates its antenna and monitors one or more signals associated with the cell selection procedure, thereby enabling the UE to perform some operations of the cell selection procedure (e.g., receive a System Information Block (SIB)) without transmitting (e.g., the transmission may be limited in conjunction with the mobility scenario). In this way, when the UE exits the mobility scenario (e.g., turns off flight mode), the UE reduces the time required to complete the receive and transmit cell selection procedures (e.g., by already performing one or more steps of the cell selection procedure).

[0077] Additionally or alternatively, the UE may predict the destination associated with the mobility scenario (e.g., based at least in part on sensor data from the UE's sensors or positioning data from satellites) and may identify a list of frequency bands for performing the cell selection process. For example, when the UE predicts a first destination associated with the mobility scenario, the UE may select a first list of frequency bands used by network nodes in the first destination, and when predicting a second destination, it may select a second list of frequency bands used by network nodes in the second destination. In some aspects, the UE may use incomplete location information associated with one or more navigation satellites to predict the destination. For example, when location determination using a navigation satellite system requires a set of four satellites, the UE may use a set of fewer than four satellites (e.g., one to three satellites) to estimate the location (e.g., in conjunction with other sensor data) and obtain a list of frequency bands, thereby reducing the amount of time required to obtain the list of frequency bands compared to obtaining the complete set of four satellites. In this way, when the UE exits the mobility scenario, the UE reduces the time required to successfully select a frequency band for cell selection, thereby improving UE performance and reducing communication latency.

[0078] Figure 5A and Figure 5B This is a diagram illustrating example 500 / 500' associated with UE operation in a mobility scenario according to this disclosure. Figure 5A and Figure 5B As shown, UE 120 can communicate with network node 110 and other devices. Although this document describes some aspects based on UE operation in a mobility scenario, it is conceivable that network nodes can operate similarly in a mobility scenario. For example, RU can perform the operation of example 500 / 500' to connect with CU or DU in conjunction with a mobility scenario.

[0079] At 510, UE 120 may identify a mobility scenario. For example, UE 120 may receive an indication and determine characteristics of the mobility scenario, such as whether UE 120 is operating in a mobility scenario, whether UE 120 has activated a flight mode associated with the mobility scenario, and / or whether UE 120 is in a specific phase of the mobility scenario, as described below.

[0080] In some aspects, UE 120 may determine that UE 120 is in a mobility scenario based at least in part on received indications. In this case, the received indications may include sensor data or other data, such as information indicating the state of the UE (e.g., the cellular antenna or modem is turned off). As examples of other data, data identifying the mode of the UE (e.g., data from the modem or data from an application) may be included as other data indicating the state of the UE. In other words, when the UE transitions to flight mode, UE 120 may receive data indicating, for example, the initiation or completion of the transition (e.g., at a first component such as the processor and from a second component such as the modem). Additionally or alternatively, the received indications may include other sensor data, such as accelerometer data or barometric pressure data that may indicate that UE 120 is operating in a mobility scenario (e.g., accelerometer data identifying the speed of UE 120 or barometric pressure data identifying the altitude of UE 120). Additionally or alternatively, UE 120 may receive geofencing data indicating that UE 120 is operating in a mobility scenario (e.g., in an aircraft, ship, train, or car). Additionally or alternatively, UE 120 may determine that UE 120 is in a mobility scenario based at least in part on identifying a Wi-Fi network. For example, when UE 120 detects a Wi-Fi network associated with an aircraft (e.g., UE 120 may determine the Wi-Fi network based at least in part on a pre-configured list, one or more previous instances of using the Wi-Fi network, or by resolving the name of the Wi-Fi network), UE 120 may determine that UE 120 is on an aircraft.

[0081] In some aspects, UE 120 may determine that UE 120 has activated a flight mode associated with a mobility scenario. For example, UE 120 may determine that UE 120 has activated a flight mode based at least in part on an indication received from an application (which may be transmitted from the application based at least in part on an indication that the antenna or modem is off). Although some aspects are described in terms of using sensor data to identify a mobility scenario and determine whether to perform a receive-only cell selection procedure, it is conceivable that some UE 120 may identify a mobility scenario without sensor data (e.g., using only an indication that a flight mode is activated) and perform a receive-only cell selection procedure without sensor data (e.g., periodically when a flight mode is activated).

[0082] In some aspects, UE 120 may determine a specific phase of a mobility scenario. For example, UE 120 may predict, at least in part, whether a mobility scenario will end within a threshold time period based on sensor data. In this way, UE 120 may reduce power utilization by performing a receive-only cell selection procedure only when UE 120 is predicted to disable flight mode within the threshold time period (e.g., at the destination), as described below. In some aspects, UE 120 may determine a specific phase of a mobility scenario based, at least in part, on sensor data from one or more sensors. For example, UE 120 may use accelerometer data to identify a landing sequence or descent phase of an aircraft. In this case, UE 120 may have a model of an aircraft landing sequence and compare the accelerometer data to that model to predict whether an aircraft landing sequence is occurring. For example, accelerometer data identifying descent, a series of turns, vibrations associated with lowering or extending the landing gear, vibrations associated with wheel contact, or other types of actions such as those associated with flight mode being disabled within the threshold time period. Additionally or alternatively, UE 120 may use barometric pressure data to identify (e.g., using a model) changes in cabin pressure associated with a landing sequence or landing phase. Additionally or alternatively, UE 120 may use humidity data (e.g., identifying atmospheric changes associated with altitude changes), location data (e.g., from satellites as described below), user data (e.g., information identifying flight bookings and associated timings of the flight), and other examples to predict when flight mode may be deactivated and when the cell selection process will occur.

[0083] In some aspects, UE 120 can acquire contextual data to assist in the prediction of characteristics of location determination and / or mobility scenarios (e.g., prediction of when and / or where an aircraft flight will end). For example, when UE 120 detects that it is operating at an airport (e.g., based at least in part on location data, geofence data, or Wi-Fi network data), UE 120 can access an application server that stores flight data (e.g., departure time, flight duration, aircraft type, aircraft speed, aircraft cruising altitude, aircraft flight path, sensor data model of a specific aircraft, weather data for the aircraft's destination, etc.). In this case, UE 120 can use flight data in conjunction with timing or sensor data during flight mode to predict the destination and / or whether UE 120 is within a threshold time period for arriving at the destination and performing cell selection. For example, UE 120 can use departure time information along with information identifying when flight mode is activated to predict which flight in a set of flights UE 120 is operating on. Based at least in part on the flight prediction, UE 120 may predict the UE location (or destination), the UE destination (e.g., and a set of associated frequency bands for the country of the UE destination, as described below), and / or whether the flight mode will terminate within a threshold time period. In some aspects, UE 120 may predict the UE location, the UE destination, and / or whether the flight mode will terminate within a threshold time period based at least in part on sensor data, as described below at 550.

[0084] Additionally or alternatively, UE 120 may receive data from another application (such as an airline application (e.g., booking or flight warning), a calendar application (e.g., calendar appointment), a search application (e.g., search history), or an email application (e.g., confirmation email)) that may indicate to the user of UE 120 which flight they will be on and / or one or more other details of that flight (e.g., duration, direction, destination, etc.). Additionally or alternatively, UE 120 may acquire other information as needed, such as monitoring in-flight announcements using a microphone (e.g., announcements identifying the destination, local time (UE 120 may infer the destination from its identified time zone or the language of the announcement or another language observed on the aircraft) or temperature (UE 120 may infer the location from it), in-flight announcements using a camera (e.g., the flight path displayed on a video screen inside the aircraft), in-flight announcements using a Wi-Fi connection (e.g., which may be configured to provide location information to the UE even if the UE has not yet paid for accessing communication services via the Wi-Fi connection), or in-flight announcements using a sidelink connection (e.g., another UE 120 may transmit a sidelink broadcast identifying the location or sensor data on a licensed frequency band or V2X band for improved location determination).

[0085] At point 520, UE 120 may initiate a receive-only cell selection procedure. For example, UE 120 may perform the cell selection procedure while UE 120 remains in flight mode (e.g., and is prohibited from transmitting). In this case, UE 120 may be prepared to terminate flight mode at a predicted time and when UE 120 is predicted to have had a location change since the last successful cell selection. In some aspects, UE 120 may determine to initiate a receive-only cell selection procedure based at least in part on the fact that UE 120 is in a mobility scenario. For example, UE 120 may perform a receive-only cell selection procedure when it determines that a mobility scenario is occurring. Additionally or alternatively, UE 120 may perform a receive-only cell selection procedure when it predicts that a mobility scenario is within a threshold end period. Additionally or alternatively, UE 120 may perform a receive-only cell selection procedure when it determines that the distance or time since the last successful cell selection is greater than a threshold distance or time.

[0086] In some aspects, when performing a receive-only cell selection procedure, UE 120 may attempt to receive one or more cell selection procedure signals from network node 110. For example, UE 120 may tune its antenna and associated modem to a specific frequency band (e.g., as described in the band list below) and may attempt to receive one or more signals associated with cell selection, such as signals identifying the Synchronization Signal Block (SSB), SIB, Master Information Block (MIB), or other signals that network node 110 may periodically transmit to enable UE 120 to perform cell selection. In this case, UE 120 may parse the received information of the receive-only cell selection procedure before the termination of flight mode, so that UE 120 can complete the cell selection procedure when flight mode terminates. For example, UE 120 may identify one or more available cells at a predicted destination to enable camping on one or more available cells. In some aspects, UE 120 may perform receive-only cell selection until UE 120 RRC camps on a cell.

[0087] In some respects, UE 120 may combine the execution of a receive-only cell selection procedure to update one or more parameters. For example, UE 120 may map detected signal movement country codes (MCCs) to locations (e.g., using a table of MCCs and locations) and update UE 120's location for location services. In this case, UE 120 may update the frequency band list based at least in part on the UE's location and / or predictions of future UE locations (destination) (e.g., based at least in part on UE 120's observed travel path, as described below). Additionally or alternatively, UE 120 may adjust its clock time zone to local time based at least in part on the location determined using the receive-only cell selection procedure. Additionally or alternatively, UE 120 may predict and / or adjust the azimuth and elevation angles of communication satellites used for emergency satellite communication services. For example, when UE 120 implements satellite-based emergency (SOS) short messages, UE 120 may use the determined location to adjust the satellite azimuth and elevation angles used to send emergency short messages. Alternatively or additionally, when UE 120 provides other (non-emergency) satellite communication services, UE 120 may update the satellite azimuth and elevation angles for those services based on the determined location. Alternatively or additionally, UE 120 may update the magnetic compass deflection at least partially based on the determined location, thereby maintaining accurate compass readings while in flight mode. Alternatively or additionally, UE 120 may update the national seed location for navigation system signal search (e.g., GPS, GNSS, or another navigation system), thereby enabling satellite acquisition for satellite-based positioning.

[0088] At 530, UE 120 may perform a cell selection procedure (e.g., receiving and transmitting the cell selection procedure). For example, UE 120 may transmit and / or receive one or more communications associated with selecting a cell for communication services. In some aspects, UE 120 may perform the remainder of the cell selection procedure. For example, UE 120 may perform one or more steps of the cell selection procedure in flight mode (e.g., by detecting and parsing a signal), and once the flight mode terminates, perform one or more steps of the cell selection procedure (e.g., by transmitting and / or receiving one or more additional signals). In this case, performing the first or more steps of the cell selection procedure before the flight mode terminates reduces the amount of time required to complete the cell selection procedure once the flight mode terminates.

[0089] Additionally or alternatively, UE 120 may perform a new cell selection procedure. For example, UE 120 may perform a first receive-only cell selection procedure in flight mode, and a second receive and transmit cell selection procedure once flight mode is terminated. In this case, information from the first receive-only cell selection procedure can reduce the amount of latency associated with performing the second cell selection procedure by, for example, providing UE 120 with a limited set of frequency bands predicted to be successful for the second cell selection procedure (e.g., at least in part based on the location of the second cell selection procedure).

[0090] At 550, Figure 5B In Example 500' shown, UE 120 may identify the predicted destination. For example, UE 120 may determine characteristics of the mobility scenario, such as the mobility scenario phase, location, or predicted destination associated with the mobility scenario. In some aspects, UE 120 may determine the mobility scenario phase based at least in part on sensor data such as navigation system data (e.g., GNSS data), accelerometer data, gyroscope data, magnetometer data, barometer data, audio data (e.g., sounds associated with the aircraft landing phase), etc. For example, UE 120 may use sensor data to determine the phase of the mobility scenario, such as whether the aircraft is in the takeoff phase, ascent phase, cruise phase, descent phase, or landing phase. In this scenario, UE 120 may use the phase of the mobility scenario to determine the location of UE 120 (e.g., whether UE 120 is at the predicted destination) and / or whether to identify a list of frequency bands for UE 120 (e.g., when UE 120 is predicted to land within a threshold time period, UE 120 may identify the list of frequency bands).

[0091] Additionally or alternatively, UE 120 may determine the location of the mobility scene based at least in part on sensor data. For example, based at least in part on sensor data identifying velocity and direction (e.g., timing of velocity and direction from a known location prior to the start of the mobility scene), UE 120 may estimate the current location of UE 120.

[0092] Additionally or alternatively, UE 120 may determine the destination based at least in part on sensor data. For example, based at least in part on sensor data identifying speed and direction (e.g., and information identifying the location of an airport), UE 120 may map its position to predict the airport the aircraft is flying to. Additionally or alternatively, when UE 120 detects that the aircraft has landed (e.g., but before flight mode terminates), UE 120 may use barometric pressure information (e.g., measured barometric pressure sensor data and stored weather information, such as barometric pressure forecasts for a set of locations) to determine the airport's altitude above sea level, which allows UE 120 to identify the airport's location. Additionally or alternatively, when UE 120 predicts it is in the landing phase, UE 120 may use compass sensor data or inertial measurement unit (IMU) sensor data to determine the heading for the landing phase, comparing that heading with a set of known headings of runways at the airport's location.

[0093] In some respects, UE 120 may use multiple different sensor data sources and / or non-sensor data sources to predict a set of candidate current or destination locations. For example, UE 120 may use accelerometer and timing data to determine the distance traveled during mobility phases, compass and IMU data to determine the heading during mobility phases, barometric and weather data to determine runway altitude, and compass and IMU data to determine runway heading. In this case, based on a combination of data points from sensors and other data sources, UE 120 may predict a set of possible candidate locations and / or destinations for UE 120, thus achieving location prediction even when any one data source is relatively inaccurate. Although a specific combination of data sources has been described above, other combinations of sensors and data sources may be used to feed data into models for predicting location or destination.

[0094] In some respects, UE 120 may approximate its position based at least in part on satellite navigation system data. For example, a satellite navigation system may use a specific number of acquired satellites (such as four or more satellites) to obtain the azimuth of the position. However, UE 120 may use fewer than a specific number of acquired satellites to estimate the position. For example, acquisition from a single GNSS or communication satellite and data from that single GNSS or communication satellite may limit the UE's position to, for example, a hemisphere of the Earth. In this case, UE 120 may select a list of frequency bands used in countries within the identified hemisphere (as described below), which may reduce the size of the frequency band list. Additionally or alternatively, UE 120 may further limit the position estimate by at least in part based on, for example, the configuration or geometry of the aircraft and its windows, predicting that the edges of the identified hemisphere are more likely to be located. In this case, UE 120 may prioritize frequency bands associated with the edges of the hemisphere over, for example, frequency bands at the center of the hemisphere. UE 120 may use other data (such as measured satellite Doppler shift data and / or aircraft velocity data (e.g., identified from accelerometer sensor data)) in combination with the acquired satellite data to further limit the identified hemisphere (e.g., limit the position to a subset of the predicted distance the aircraft has traveled from its starting position to the location within the identified hemisphere).

[0095] Similarly, when acquiring two satellites, UE 120 can estimate the position as the overlap of the two hemispheres determined based on data associated with the two satellites, thereby enabling UE 120 to limit the frequency band list to those used in countries within the overlap of the two hemispheres. Additionally or alternatively, UE 120 can further limit the overlap using the increment between the pseudorange and Doppler shift of two concurrently tracked GNSS satellites. Additionally or alternatively, when UE 120 acquires multiple satellites at different times, UE 120 can use a trajectory approximation predicted from the observation sequence of multiple satellites to predict the destination of the aircraft on which UE 120 is located (e.g., using a great circle trajectory to identify airports within the predicted path of UE 120 and within the predicted range of the aircraft).

[0096] Similarly, when acquiring three satellites, UE 120 can approximate the two-dimensional position azimuth (e.g., position azimuth without an altitude component). In this case, UE 120 can infer altitude at least partially based on the mobility scenario phase (e.g., altitude during the aircraft's cruise phase can be inferred to be approximately 10 kilometers above sea level). In this case, even with relatively poor geometry for the two-dimensional satellite azimuth (e.g., relatively poor horizontal accuracy factor (HDoP) value), the approximation of the UE 120's position can be within several hundred kilometers, which allows for limiting the frequency band list to one or more countries (e.g., rather than, for example, all possible countries). In this way, UE 120 can determine its position or destination by acquiring fewer satellites than is required for position azimuth, which reduces the amount of time required to determine the position compared to waiting for that number of satellites to be acquired.

[0097] At 560, UE 120 can configure a list of frequency bands for cell selection. For example, UE 120 can configure the list of frequency bands for performing a frequency band search associated with cell selection, at least in part, based on a predicted location or destination. In this case, different continents, countries, or locations within a country may have different sets of frequency bands for, for example, 5G connectivity, and UE 120 can prioritize the set of frequency bands associated with the predicted location or destination. Additionally or alternatively, UE 120 can prompt the user for information identifying the location of UE 120. For example, when airplane mode is disabled, UE 120 can provide user interface elements to allow the user to enter or select the location of UE 120, which allows UE 120 to determine the list of frequency bands and / or prioritize the set of frequency bands in that list. In this way, UE 120 reduces the amount of time required to successfully perform a frequency band search by reducing the number of frequency bands to search (or prioritizing the order of the frequency bands to search). For example, when UE 120 predicts that UE 120 is in an aircraft and has landed in a specific country, UE 120 can prioritize frequency bands active in the specific country in order to perform a frequency band search, and can de-prioritize frequency bands that are inactive in the specific country.

[0098] At 570, UE 120 may use a configured frequency band list to perform cell selection. For example, UE 120 may perform cell selection on one or more frequency bands in the configured frequency band list. In some aspects, UE 120 may attempt to receive signals on frequency bands in the configured frequency band list in a priority order, at least in part based on a prediction of the UE's location or destination. In this way, the amount of time required to receive signals is reduced by decreasing the size of the frequency band list or prioritizing the frequency band list, at least in part based on the predicted UE location or destination.

[0099] As indicated above, Figure 5A and Figure 5B This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5A and Figure 5B The examples described are different.

[0100] Figure 6 This is a flowchart of an example method 600 for wireless communication. Method 600 can be performed by, for example, a UE (e.g., UE 120).

[0101] At 610, the UE may receive sensor data or other data associated with characteristics that identify mobility scenarios. For example, the UE (e.g., using...) Figure 7 The communication manager 140 and / or receiving component 702 described herein may receive sensor data or other data associated with characteristics that identify a mobility scenario, as described above in conjunction with, for example... Figure 5A and Figure 5B And as described accordingly at 510 and 550. In some respects, sensor data includes information identifying the descent or landing phase associated with the aircraft in which the UE is located.

[0102] In some aspects, sensor data includes information identifying a set of pre-landing turns, landing gear extensions, ground contact vibrations, pressure values, or changes in cabin pressure values. In some aspects, receiving sensor data includes receiving sensor data during the UE's flight mode. In some aspects, sensor data includes information identifying changes in the UE's position. In some aspects, sensor data comes from multiple sensors of the UE. In some aspects, sensor data includes data from satellites, including navigation system satellites.

[0103] At point 615, the UE can predict that cell selection will occur. For example, the UE (e.g., using...) Figure 7 The communication manager 140 and / or determining component 710 described herein can predict sensor data indicating that cell selection will occur, as illustrated above in conjunction with, for example... Figure 5A and Figure 5B And accordingly described at 510 and 550. In some aspects, the UE may predict, at least in part, that cell selection will occur within a threshold time period based on sensor data, and the UE may perform at least a portion of the cell selection process based at least in part on the prediction that cell selection will occur. In some aspects, the prediction that cell selection will occur is based at least in part on whether information identifying the UE's location is available and on the mapping of the UE's location to the associated set of available cells.

[0104] At position 616, the UE can identify its location. For example, the UE (e.g., using...) Figure 7The communication manager 140 and / or determining component 710 described herein can determine the association between sensor data and an indication of the UE's location, as illustrated above in conjunction with, for example... Figure 5A and Figure 5B And correspondingly described at 510 and 550. In some aspects, the UE may identify its location or a set of candidate UE locations based at least in part on sensor data, and the UE may use a priority list of a frequency band to perform at least a portion of the cell selection process, the priority list of the frequency band being based at least in part on the UE location or the set of UE locations. In some aspects, the UE location or the set of candidate UE locations is based at least in part on at least one of data associated with Wi-Fi connectivity, air pressure, temperature, travel duration, travel distance, departure location, or heading. In some aspects, the UE may predict its location based at least in part on flight data.

[0105] At points 617 and 618, in order to identify the UE's location, the UE can acquire satellite data and predict its position. For example, the UE (e.g., using...) Figure 7 The communication manager 140, satellite acquisition component 714, and / or determination component 710 depicted herein can acquire one or more satellites and use data received from the one or more satellites to predict the UE's location. In some aspects, the UE can acquire a set of satellites, wherein a threshold number of satellites is associated with the determination of the UE's location, wherein the number of satellites in the acquired set is less than the threshold number, and the UE can use the acquired set of satellites to predict its location. In some aspects, the UE can acquire multiple satellites sequentially, and the UE can predict its location at least in part based on the acquisition order of the sequentially acquired multiple satellites.

[0106] At point 620, the UE can perform at least a portion of the cell selection process. For example, the UE (e.g., using...) Figure 7 The communication manager 140 and / or cell selection component 708 described herein may perform at least a portion of the cell selection process based at least in part on characteristics associated with the mobility scenario, as described above in conjunction with, for example... Figure 5A and Figure 5B And accordingly described at 520 and 560. In some aspects, at least a portion of performing the cell selection procedure includes performing receive-only cell selection until the RRC camps on the cell. For example, the UE performs a receive-based frequency or band search portion of the cell selection procedure. In this case, the UE enables receive functionality for searching for frequencies or bands on the cellular RAT.

[0107] At point 625, the UE can perform the remainder of the cell selection process. For example, the UE (e.g., using...) Figure 7The communication manager 140 and / or cell selection component 708 described herein may perform the remainder of the cell selection process at least in part based on this at least part of the cell selection process, as described above in conjunction with, for example Figure 5A and Figure 5B And as described accordingly at 530 and 570. In this case, the UE can complete the cell selection process to camp on the cell and access communication services.

[0108] At position 626, the UE can update parameters. For example, the UE (e.g., using...) Figure 7 The communication manager 140 and / or update component 712 described herein may determine the value of the parameter at least in part based on this at least part of the cell selection process performed, as described above in conjunction with, for example Figure 5A and Figure 5B And as described accordingly at 520 and 560. In some aspects, the UE may update at least one of one or more parameters associated with the UE location, at least in part, based on at least one part of performing the cell selection procedure. In some aspects, the one or more parameters include at least one of the following: UE clock time zone, communication satellite beam information, magnetic compass deflection, or national seed location for signal search.

[0109] although Figure 6 An example box of method 600 is shown, but in some respects, method 600 may include... Figure 6 The boxes depicted may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the box of method 600 may be executed in parallel.

[0110] Figure 7 This is a diagram of an example device 700 for wireless communication according to the present disclosure. Device 700 may be a UE, or a UE may include device 700. In some aspects, device 700 includes a receiving component 702 and a transmitting component 704 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 700 can use the receiving component 702 and the transmitting component 704 to communicate with another device 706 (such as a UE, a base station, or another wireless communication device). As further shown, device 700 may include a communication manager 140. Communication manager 140 may include one or more of a cell selection component 708, a determination component 710, an update component 712, or a satellite acquisition component 714, etc.

[0111] In some respects, device 700 can be configured to perform the functions described herein. Figures 5A to 5B One or more operations described herein. Additionally or alternatively, the apparatus 700 may be configured to perform one or more processes described herein, such as Figure 6Method 600. In some respects, Figure 7 The illustrated device 700 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 7 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0112] Receiver 702 may receive communications from device 706, such as reference signals, control information, data communications, or combinations thereof. Receiver 702 may provide the received communications to one or more other components of device 700. In some aspects, receiver 702 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 700. In some aspects, receiver 702 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0113] Transmitting component 704 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 706. In some aspects, one or more other components of device 700 can generate communications and provide the generated communications to transmitting component 704 for transmission to device 706. In some aspects, transmitting component 704 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 706. In some aspects, transmitting component 704 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 704 may be co-located with the receive component 702 in a transceiver.

[0114] Receiving component 702 may receive sensor data or other data associated with characteristics related to mobility scenarios. Cell selection component 708 may perform at least a portion of the cell selection process based at least partially on characteristics associated with mobility scenarios. Determining component 710 may predict, at least partially on sensor data, that cell selection will occur within a threshold time period. Updating component 712 may update at least one of the UE location or one or more parameters associated with the UE location based at least partially on the execution of at least this portion of the cell selection process. Determining component 710 may identify the UE location or a set of candidate UE locations based at least partially on sensor data.

[0115] Satellite acquisition component 714 can acquire a set of satellites, wherein a threshold number of satellites is associated with the determination of the UE's location, and wherein the number of satellites in the acquired set is less than the threshold number. Determination component 710 can use the acquired set of satellites to predict the UE's location. Satellite acquisition component 714 can acquire multiple satellites sequentially. Determination component 710 can predict the UE's location at least in part based on the acquisition order of the multiple satellites acquired sequentially. Determination component 710 can predict the UE's location at least in part based on flight data.

[0116] Figure 7 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 7 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 7 The two or more components shown can be implemented within a single component, or Figure 7 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 7 The collection of (one or more) components shown is executable and described as being composed of Figure 7 Another set of components shown performs one or more functions.

[0117] Figure 8 This is a diagram illustrating an example 800 of a hardware implementation of a device 805 employing a processing system 810 according to the present disclosure. Device 805 may be a UE.

[0118] Processing system 810 can be implemented using a bus architecture typically represented by bus 815. Bus 815 may include any number of interconnect buses and bridges, depending on the specific application of processing system 810 and overall design constraints. Bus 815 links together various circuits including one or more processors and / or hardware components represented by processor 820, illustrated components, and computer-readable medium / memory 825. Bus 815 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and / or power management circuits.

[0119] Processing system 810 may be coupled to transceiver 830. Transceiver 830 is coupled to one or more antennas 835. Transceiver 830 provides components for communicating with various other devices via a transmission medium. Transceiver 830 receives signals from one or more antennas 835, extracts information from the received signals, and provides the extracted information to processing system 810 (specifically, receiving component 702). Furthermore, transceiver 830 receives information from processing system 810 (specifically, transmitting component 704) and generates signals to be applied to one or more antennas 835, at least in part, based on the received information.

[0120] Processing system 810 includes a processor 820 coupled to a computer-readable medium / memory 825. Processor 820 is responsible for general processing, including executing software stored on the computer-readable medium / memory 825. When executed by processor 820, the software causes processing system 810 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 825 may also be used to store data manipulated by processor 820 during software execution. The processing system also includes at least one of the illustrated components. A component may be: a software module running in processor 820, residing in / stored on computer-readable medium / memory 825, one or more hardware modules coupled to processor 820, or some combination thereof.

[0121] In some aspects, the processing system 810 may be a component of the UE 120 and may include at least one of a memory 282, and / or a TXMIMO processor 266, an RX processor 258, and / or a controller / processor 280. In some aspects, the apparatus 805 for wireless communication includes components for receiving sensor data or other data associated with characteristics associated with a mobility scenario; and components for performing at least a portion of a cell selection process based at least in part on characteristics associated with the mobility scenario. Additionally or alternatively, apparatus 805 may include components for predicting, at least partially, that cell selection will occur within a threshold time period based on sensor data; components for updating, at least partially, one or more parameters associated with the UE location based on at least a portion of the cell selection process; components for identifying the UE location or a set of candidate UE locations based at least partially on sensor data; components for acquiring a set of satellites, wherein a threshold number of satellites is associated with the determination of the UE location, wherein the number of satellites in the acquired set of satellites is less than a threshold number; components for predicting the UE location using the acquired set of satellites; components for acquiring multiple satellites sequentially; components for predicting the UE location based at least partially on the acquisition order of the multiple satellites acquired sequentially; and / or components for predicting the UE location based at least partially on flight data. The aforementioned components may be one or more of the aforementioned components of apparatus 700 and / or processing system 810 of apparatus 805, configured to perform the functions stated by the aforementioned components. As described elsewhere herein, the processing system 810 may include a TX MIMO processor 266, an RX processor 258, and / or a controller / processor 280. In one configuration, the aforementioned components may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations set forth herein.

[0122] Figure 8 This is provided as an example. Other examples can be combined with it. Figure 8 The examples described are different.

[0123] The following provides an overview of some aspects of this disclosure:

[0124] Aspect 1: A method of wireless communication performed by a user equipment (UE), the user equipment (UE) comprising: receiving sensor data or other data associated with identifying characteristics associated with a mobility scenario; and performing at least a portion of a cell selection process based at least in part on the characteristics associated with the mobility scenario.

[0125] Aspect 2: According to the method of aspect 1, wherein performing at least a portion of the cell selection process includes: performing a frequency or band search portion of the cell selection process based on the received signal.

[0126] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the sensor data includes information identifying the descent or landing phase associated with the aircraft in which the UE is located.

[0127] Aspect 4: According to the method of aspect 3, the sensor data includes information identifying a set of pre-landing turns, landing gear extensions, ground contact vibrations, or changes in cabin pressure.

[0128] Aspect 5: The method according to any one of Aspects 1 to 4, wherein receiving the sensor data includes: receiving the sensor data during flight mode of the UE.

[0129] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: predicting, at least in part, that cell selection will occur within a threshold time period based on the sensor data; and wherein performing the at least part of the cell selection process comprises: performing the at least part of the cell selection process based at least in part on the prediction that the cell selection will occur.

[0130] Aspect 7: According to the method of aspect 6, the prediction that the cell selection will occur is based at least in part on whether information identifying the UE location is available and the mapping of the UE location to the associated set of available cells.

[0131] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the sensor data includes information identifying changes in the position of the UE.

[0132] Aspect 9: The method according to any one of Aspects 1 to 8, the method further comprising: updating the UE location or at least one of one or more parameters associated with the UE location based at least in part on the at least part of performing the cell selection process.

[0133] Aspect 10: According to the method of aspect 9, the one or more parameters include at least one of the following: UE clock time zone, communication satellite beam information, magnetic compass deflection, or national seed location for signal search.

[0134] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: identifying a UE location or a set of candidate UE locations based at least in part on the sensor data; and wherein performing at least a portion of the cell selection process comprises: performing at least a portion of the cell selection process using a priority list of frequency bands, the priority list of frequency bands being at least in part based on the UE location or the set of UE locations.

[0135] Aspect 12: According to the method of aspect 11, the UE location or the set of candidate UE locations is based at least in part on at least one of the following: data associated with the Wi-Fi connection, air pressure, temperature, travel duration, travel distance, departure location, or heading.

[0136] Aspect 13: According to the method of aspect 11, the method further includes: acquiring a set of satellites, wherein a threshold number of satellites is associated with the determination of the UE location, wherein the number of satellites in the acquired set of satellites is less than the threshold number; and using the acquired set of satellites to predict the UE location.

[0137] Aspect 14: The method according to aspect 11, the method further comprising: acquiring a plurality of satellites in sequence; and predicting the UE location based at least in part on the acquisition order of the plurality of satellites acquired in the sequence.

[0138] Aspect 15: The method according to aspect 11 further includes: predicting the UE location based at least in part on flight data.

[0139] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the sensor data comes from a plurality of sensors of the UE.

[0140] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the sensor data includes data from a satellite, the satellite including a navigation system satellite.

[0141] Aspect 18: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1 to 17.

[0142] Aspect 19: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspects 1 to 17.

[0143] Aspect 20: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 17.

[0144] Aspect 21: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the methods described in one or more of aspects 1 to 17.

[0145] Aspect 22: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 17.

[0146] The foregoing disclosure provides examples and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from practice in various aspects.

[0147] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent to those skilled in the art that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting in any way. Therefore, no specific software code is referred to in this document to describe the operation and behavior of the systems and / or methods, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0148] As used in this article, depending on the context, "meets the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0149] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically set forth in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the set of claims. As used herein, the phrase “at least one of the items in the list” refers to any combination of these items (including a single member). As an example, “at least one of a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0150] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the article “a” is intended to include one or more items and is used interchangeably with “one or more”. Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in conjunction with the article “described” and is used interchangeably with “one or more”. Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are used interchangeably with “one or more”. If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “have,” “possess,” “have,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., “having” an element of A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”).

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and One or more processors coupled to the memory, the one or more processors being configured to: Receive sensor data or other data associated with characteristics related to mobility scenarios; and At least a portion of the cell selection process is performed based, at least in part, on the characteristics associated with the mobility scenario.

2. The UE of claim 1, wherein, in order to perform at least a portion of the cell selection process, the one or more processors are configured to: The frequency or band search portion of the cell selection process is performed based on the received signal.

3. The UE of claim 1, wherein the sensor data includes information identifying the descent or landing phase associated with the aircraft in which the UE is located.

4. The UE of claim 3, wherein the sensor data includes information identifying the following: A set of pre-landing turns, Landing gear extended, Ground vibration, Changes in cabin pressure, or Chamber pressure value.

5. The UE of claim 1, wherein, in order to receive the sensor data, the one or more processors are configured to: The sensor data is received during the UE's flight mode.

6. The UE of claim 1, wherein the one or more processors are further configured to: At least in part based on the sensor data, predicting that cell selection will occur within a threshold time period; and In order to perform at least a portion of the cell selection process, the one or more processors are configured to: At least a portion of the cell selection process is performed based at least in part on the prediction that the cell selection will occur.

7. The UE of claim 6, wherein, in order to predict that the cell selection will occur within the threshold time period, the one or more processors are configured to: predict that the cell selection will occur based at least in part on whether information identifying the UE location is available and the mapping of the UE location to an associated set of available cells.

8. The UE of claim 1, wherein the sensor data includes information identifying changes in the location of the UE.

9. The UE of claim 1, wherein the one or more processors are further configured to: The UE location or at least one of one or more parameters associated with the UE location is updated, at least in part, based on at least a portion of the cell selection process performed.

10. The UE of claim 9, wherein the one or more parameters include at least one of the following: UE clock time zone Communication satellite beam information Magnetic compass deflection, or National seed locations used for signal search.

11. The UE of claim 1, wherein the one or more processors are further configured to: The UE location or a set of candidate UE locations is identified at least in part based on the sensor data; and In order to perform at least a portion of the cell selection process, the one or more processors are configured to: At least a portion of the cell selection process is performed using a priority list of frequency bands, the priority list of frequency bands being at least partially based on the UE location or the set of UE locations.

12. The UE of claim 11, wherein the UE location or the set of candidate UE locations is based at least in part on at least one of the following: Data associated with Wi-Fi connection, air pressure, temperature, Duration of travel Distance traveled Starting location, or course.

13. The UE of claim 11, wherein the one or more processors are further configured to: A set of satellites is acquired, wherein a threshold number of satellites is associated with the determination of the UE's location, wherein the number of satellites in the acquired set of satellites is less than the threshold number; and the acquired set of satellites is used to predict the UE's location.

14. The UE of claim 11, wherein the one or more processors are further configured to: Acquire multiple satellites sequentially; and The UE location is predicted at least in part based on the acquisition order of the plurality of satellites acquired in the sequence.

15. The UE of claim 11, wherein the one or more processors are further configured to: The UE's location is predicted based at least in part on flight data.

16. The UE of claim 1, wherein the sensor data comes from a plurality of sensors of the UE.

17. The UE of claim 1, wherein the sensor data includes data from a satellite, the satellite including a navigation system satellite.

18. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive sensor data or other data associated with characteristics related to mobility scenarios; as well as At least a portion of the cell selection process is performed based, at least in part, on the characteristics associated with the mobility scenario.

19. The method of claim 18, wherein performing at least a portion of the cell selection process comprises: The frequency or band search portion of the cell selection process is performed based on the received signal.

20. The method of claim 18, wherein the sensor data includes information identifying the descent or landing phase associated with the aircraft in which the UE is located.

21. The method of claim 20, wherein the sensor data includes information identifying the following: A set of pre-landing turns, Landing gear extended, Ground vibration, Changes in cabin pressure, or Pressure value.

22. The method of claim 18, wherein receiving the sensor data comprises: The sensor data is received during the UE's flight mode.

23. The method according to claim 18, further comprising: The cell selection will be predicted to occur within a threshold time period, at least in part based on the sensor data. as well as The execution of at least a portion of the cell selection process includes: At least a portion of the cell selection process is performed based at least in part on the prediction that the cell selection will occur.

24. The method of claim 23, wherein the method comprises: This occurs at least in part based on whether information identifying the UE's location is available and the mapping of the UE's location to the associated set of available cells.

25. The method of claim 18, wherein the sensor data includes information identifying changes in the position of the UE.

26. The method according to claim 18, further comprising: The UE location or at least one of one or more parameters associated with the UE location is updated, at least in part, based on at least a portion of the cell selection process performed.

27. The method of claim 26, wherein the one or more parameters include at least one of the following: UE clock time zone Communication satellite beam information Magnetic compass deflection, or National seed locations used for signal search.

28. The method according to claim 18, further comprising: The UE location or a set of candidate UE locations is identified at least in part based on the sensor data. as well as The execution of at least a portion of the cell selection process includes: At least a portion of the cell selection process is performed using a priority list of frequency bands, the priority list of frequency bands being at least partially based on the UE location or the set of UE locations.

29. A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions, which, when executed by one or more processors of a user equipment (UE), cause the UE to: Receive sensor data or other data associated with characteristics related to mobility scenarios; and At least a portion of the cell selection process is performed based, at least in part, on the characteristics associated with the mobility scenario.

30. An apparatus for wireless communication, the apparatus comprising: Components for receiving sensor data or other data associated with characteristics related to mobility scenarios; as well as Components for performing at least a portion of the cell selection process based at least in part on the characteristics associated with the mobility scenario.

Images