WO2024065673A1 - Systèmes, procédés et dispositifs pour un transfert air-sol (atg) amélioré - Google Patents

Systèmes, procédés et dispositifs pour un transfert air-sol (atg) amélioré Download PDF

Info

Publication number
WO2024065673A1
WO2024065673A1 PCT/CN2022/123265 CN2022123265W WO2024065673A1 WO 2024065673 A1 WO2024065673 A1 WO 2024065673A1 CN 2022123265 W CN2022123265 W CN 2022123265W WO 2024065673 A1 WO2024065673 A1 WO 2024065673A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
distance
target base
serving base
implementations
Prior art date
Application number
PCT/CN2022/123265
Other languages
English (en)
Inventor
Jie Cui
Yang Tang
Qiming Li
Manasa RAGHAVAN
Haitong Sun
Xiang Chen
Yuexia Song
Rolando E. BETTANCOURT ORTEGA
Dawei Zhang
Hong He
Original Assignee
Apple Inc.
Qiming Li
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Inc., Qiming Li filed Critical Apple Inc.
Priority to PCT/CN2022/123265 priority Critical patent/WO2024065673A1/fr
Publication of WO2024065673A1 publication Critical patent/WO2024065673A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H04W36/362—Conditional handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/326—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by proximity to another entity

Definitions

  • This disclosure relates to wireless communication networks and mobile device capabilities.
  • Wireless communication networks and wireless communication services are becoming increasingly dynamic, complex, and ubiquitous.
  • some wireless communication networks may be developed to implement fifth generation (5G) or new radio (NR) technology, sixth generation (6G) technology, and so on.
  • 5G fifth generation
  • NR new radio
  • 6G sixth generation
  • Such technology may include solutions for enabling user equipment (UE) to maintain service while moving throughout a network.
  • UE user equipment
  • Fig. 1 is a diagram of an example overview according to one or more implementations described herein.
  • Fig. 2 is a diagram of an example network according to one or more implementations described herein.
  • Fig. 3 is a diagram of an example process for a serving base station making a handover decision based on user equipment (UE) distances according to one or more implementations described herein.
  • UE user equipment
  • Fig. 4 is a diagram of an example process for a serving base station making a handover decision based on a UE flight path according to one or more implementations described herein.
  • Fig. 5 is a diagram of an example process for a serving base station making a handover decision based on a distance report from a UE according to one or more implementations described herein.
  • Fig. 6 is a diagram of an example process for a serving base station making a handover decision based on a signal strength and quality report from a UE according to one or more implementations described herein.
  • Fig. 7 is a diagram of an example process for a UE making a handover decision based on UE distances according to one or more implementations described herein.
  • Fig. 8 is a diagram of an example process for a UE making a handover decision based on a UE flight path according to one or more implementations described herein.
  • Fig. 9 is a diagram of an example process for a serving base station making a handover decision based on a UE reaching a flight path checkpoint according to one or more implementations described herein.
  • Fig. 10 is a diagram of an example of components of a device according to one or more implementations described herein.
  • Fig. 11 is a block diagram illustrating components, according to one or more implementations described herein, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • Wireless networks may include user equipment (UEs) capable of communicating with base stations, wireless routers, satellites, and other network nodes. Such devices may operate in accordance with one or more communication standards, such as 2nd generation (2G) , 3rd generation (3G) , 4th generation (4G) (e.g., long-term evolution (LTE) ) , and/or 5th generation (5G) (e.g., new radio (NR) ) communication standards of the 3rd generation partnership project (3GPP) .
  • a UE may refer to a smartphone, tablet computer, wearable wireless device, a vehicle capable of wireless communications, and/or another type of a broad range of wireless-capable device.
  • a UE may also include UE-capable objects and devices.
  • a UE-capable device may include a car, truck, or train with suitable components for operating as a UE.
  • Currently available technologies may include adequate solutions for enabling lower velocity UEs to maintain network connections as they move from one cell to another.
  • currently available technologies fail to provide adequate solutions for high-velocity UEs.
  • UEs may include UE-capable machines and devices capable of very high-velocity travel (e.g., around 1200 kilometers per hour) , such as drones, helicopters, airplanes, jets, rockets, etc.
  • Such devices may include UE components (e.g., antennas, processors, memory, storage, software, data, power source, etc. ) for communicating with terrestrial or ground-based base stations having extremely large cell coverage ranges (e.g., up to 300 kilometers) .
  • UE components e.g., antennas, processors, memory, storage, software, data, power source, etc.
  • terrestrial or ground-based base stations having extremely large cell coverage ranges (e.g., up to 300 kilometers) .
  • UE also referred to herein as “UE”
  • the techniques described herein provide solutions for enabling enhanced air-to-ground (ATG) handover procedures for high-velocity UEs.
  • Fig. 1 is an example overview 100 according to one or more implementations described herein.
  • example overview 100 may include UE 110, serving base station 120-1, and target base station 120-2.
  • UE 110 may be an airplane or another type of UE-capable device or object capable of traveling at a very high velocity (e.g., 1,200 kilometers per hour) .
  • Base stations 120-1 and 120-2 may be long-range base stations capable of projecting a cell with a large radial signal distance (e.g., 300 kilometers) .
  • the techniques described herein include solutions for a handover decision to be made by UE 110 or base station 120-1, which may be based on one or more types of triggers, conditions, reports, or information.
  • UE 110 or serving base station 120-1 may make a handover decision based on distances between UE 110 and base stations 120-1 and 120-2 (at 1.1) .
  • UE 110 or serving base station 120-1 may make a handover decision based on a UE flight path, including changes in a UE flight path and a current position of UE 1120 or UE 110 reaching a flight path checkpoint (e.g., a location identified along the flightpath) (at 1.2) .
  • a flight path checkpoint e.g., a location identified along the flightpath
  • UE 110 may make the handover decision based on one or more signals (e.g., a reference signal received power (RSRP) , a reference signal received quality (RSRQ) , etc., and corresponding signal thresholds (at 1.3) .
  • a handover decision may be based one or more of the foregoing conditions (e.g., a distance between UE 110 and base stations 120-1 and 120-2, a UE flight path and location, and/or a received signal from base stations 120-1 or 120-2) .
  • the techniques described herein are not limited to UEs 110 of a particular type or travel velocity, nor are they limited to base stations of a certain cell size or coverage area. Additional details and examples of these and other implementations are described below with reference to the Figures.
  • Fig. 2 is an example network 200 according to one or more implementations described herein.
  • Example network 200 may include UEs 210-1, 210-2, etc. (referred to collectively as “UEs 210” and individually as “UE 210” ) , a radio access network (RAN) 220, a core network (CN) 230, application servers 240, and external networks 250.
  • RAN radio access network
  • CN core network
  • application servers 240 application servers 240
  • external networks 250 external networks
  • the systems and devices of example network 200 may operate in accordance with one or more communication standards, such as 2nd generation (2G) , 3rd generation (3G) , 4th generation (4G) (e.g., long-term evolution (LTE) ) , and/or 5th generation (5G) (e.g., new radio (NR) ) communication standards of the 3rd generation partnership project (3GPP) .
  • 3G 3rd generation
  • 4G e.g., long-term evolution (LTE)
  • 5G e.g., new radio (NR)
  • 3GPP 3rd generation partnership project
  • 3GPP 3rd generation partnership project
  • one or more of the systems and devices of example network 200 may operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc. ) , institute of electrical and electronics engineers (IEEE) standards (e.g., wireless metropolitan area network (WMAN)
  • UEs 210 may include smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more wireless communication networks) . Additionally, or alternatively, UEs 210 may include other types of mobile or non-mobile computing devices capable of wireless communications, such as personal data assistants (PDAs) , pagers, laptop computers, desktop computers, wireless handsets, etc. In some implementations, UEs 210 may include internet of things (IoT) devices (or IoT UEs) that may comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • IoT internet of things
  • an IoT UE may utilize one or more types of technologies, such as machine-to-machine (M2M) communications or machine-type communications (MTC) (e.g., to exchanging data with an MTC server or other device via a public land mobile network (PLMN) ) , proximity-based service (ProSe) or device-to-device (D2D) communications, sensor networks, IoT networks, and more.
  • M2M or MTC exchange of data may be a machine-initiated exchange
  • an IoT network may include interconnecting IoT UEs (which may include uniquely identifiable embedded computing devices within an Internet infrastructure) with short-lived connections.
  • IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc. ) to facilitate the connections of the IoT network.
  • UEs 210 may communicate and establish a connection with one or more other UEs 210 via one or more wireless channels 212, each of which may comprise a physical communications interface /layer.
  • the connection may include an M2M connection, MTC connection, D2D connection, SL connection, etc.
  • the connection may involve a PC5 interface.
  • UEs 210 may be configured to discover one another, negotiate wireless resources between one another, and establish connections between one another, without intervention or communications involving RAN node 222 or another type of network node.
  • discovery, authentication, resource negotiation, registration, etc. may involve communications with RAN node 222 or another type of network node.
  • UEs 210 may use one or more wireless channels 212 to communicate with one another.
  • UE 210-1 may communicate with RAN node 222 to request SL resources.
  • RAN node 222 may respond to the request by providing UE 210 with a dynamic grant (DG) or configured grant (CG) regarding SL resources.
  • DG may involve a grant based on a grant request from UE 210.
  • a CG may involve a resource grant without a grant request and may be based on a type of service being provided (e.g., services that have strict timing or latency requirements) .
  • UE 210 may perform a clear channel assessment (CCA) procedure based on the DG or CG, select SL resources based on the CCA procedure and the DG or CG; and communicate with another UE 210 based on the SL resources.
  • the UE 210 may communicate with RAN node 222 using a licensed frequency band and communicate with the other UE 210 using an unlicensed frequency band.
  • CCA clear channel assessment
  • UEs 210 may communicate and establish a connection with (e.g., be communicatively coupled) with RAN 220, which may involve one or more wireless channels 214-1 and 214-2, each of which may comprise a physical communications interface /layer.
  • a UE may be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC) , where a multiple receive and transmit (Rx/Tx) capable UE may use resources provided by different network nodes (e.g., 222-1 and 222-2) that may be connected via non-ideal backhaul (e.g., where one network node provides NR access and the other network node provides either E-UTRA for LTE or NR access for 5G) .
  • DC dual connectivity
  • multi-RAT multi-radio access technology
  • MR-DC multi-radio dual connectivity
  • Rx/Tx multiple receive and transmit
  • one network node may operate as a master node (MN) and the other as the secondary node (SN) .
  • the MN and SN may be connected via a network interface, and at least the MN may be connected to the CN 230.
  • at least one of the MN or the SN may be operated with shared spectrum channel access, and functions specified for UE 210 can be used for an integrated access and backhaul mobile termination (IAB-MT) .
  • IAB-MT integrated access and backhaul mobile termination
  • the IAB-MT may access the network using either one network node or using two different nodes with enhanced dual connectivity (EN-DC) architectures, new radio dual connectivity (NR-DC) architectures, or the like.
  • a base station (as described herein) may be an example of network node 222.
  • UEs 210-3 and 210-4 may include UE-capable vehicles or devices capable of high-velocity travel (e.g., around 1200 kilometers per hour) .
  • UEs 210-3 and 210-4 may include drones, helicopters, airplanes, jets, rockets, or other vehicles or devices capable of flight.
  • UEs 210-3 and 210-4 may also, or alternatively, include high-velocity vehicles or devices that may travel over land, over water, or under water.
  • Such devices may include UE components (e.g., antennas, processors, memory, storage, software, data, power sources, etc. ) suitable for communicating with terrestrial or ground-based RAN nodes 222 (also referred to herein as “base station 222” or “base stations 222” ) having extremely large cell coverage ranges (e.g., up to 300 kilometers) .
  • UE 210 or serving base station 222 may make a handover decision based on distances between UE 210 and serving base stations 222 and target base station 222.
  • UE 210 or serving base station 222 may make a handover decision based on a UE flight path, including changes in a UE flight path or UE 210 reaching a flight path checkpoint (e.g., a location identified along the flightpath) .
  • serving base station 222 may make a handover decision based on a distance report from UE 210 or UE 110 may make the handover decision based on a signal strength and/or quality from target base station 222. Additional details and examples of these and other implementations are described below with reference to the Figures.
  • UE 210 may also, or alternatively, connect to access point (AP) 216 via connection interface 218, which may include an air interface enabling UE 210 to communicatively couple with AP 216.
  • AP 216 may comprise a wireless local area network (WLAN) , WLAN node, WLAN termination point, etc.
  • the connection 216 may comprise a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and AP 216 may comprise a wireless fidelity router or other AP. While not explicitly depicted in Fig. 2, AP 216 may be connected to another network (e.g., the Internet) without connecting to RAN 220 or CN 230.
  • another network e.g., the Internet
  • UE 210, RAN 220, and AP 216 may be configured to utilize LTE-WLAN aggregation (LWA) techniques or LTE WLAN radio level integration with IPsec tunnel (LWIP) techniques.
  • LWA may involve UE 210 in RRC_CONNECTED being configured by RAN 220 to utilize radio resources of LTE and WLAN.
  • LWIP may involve UE 210 using WLAN radio resources (e.g., connection interface 218) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) communicated via connection interface 218.
  • IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.
  • RAN 220 may include one or more RAN nodes 222-1 and 222-2 (referred to collectively as RAN nodes 222, and individually as RAN node 222) that enable channels 214-1 and 214-2 to be established between UEs 210 and RAN 220.
  • RAN nodes 222 may include network access points configured to provide radio baseband functions for data and/or voice connectivity between users and the network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, 6G, WiFi, etc. ) .
  • a RAN node may be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc.
  • RAN nodes 222 may include a roadside unit (RSU) , a transmission reception point (TRxP or TRP) , and one or more other types of ground stations (e.g., terrestrial access points) .
  • RSU roadside unit
  • TRxP transmission reception point
  • RAN node 222 may be a dedicated physical device, such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or the like having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • LP low power
  • RAN nodes 222 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a centralized RAN (CRAN) and/or a virtual baseband unit pool (vBBUP) .
  • CRAN centralized RAN
  • vBBUP virtual baseband unit pool
  • the CRAN or vBBUP may implement a RAN function split, such as a packet data convergence protocol (PDCP) split wherein radio resource control (RRC) and PDCP layers may be operated by the CRAN/vBBUP and other Layer 2 (L2) protocol entities may be operated by individual RAN nodes 222; a media access control (MAC) /physical (PHY) layer split wherein RRC, PDCP, radio link control (RLC) , and MAC layers may be operated by the CRAN/vBBUP and the PHY layer may be operated by individual RAN nodes 222; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer may be operated by the CRAN/vBBUP and lower portions of the PHY layer may be operated by individual RAN nodes 222.
  • This virtualized framework may allow freed-up processor cores of RAN nodes 222 to perform or execute other virtualized applications.
  • an individual RAN node 222 may represent individual gNB-distributed units (DUs) connected to a gNB-control unit (CU) via individual F1 or other interfaces.
  • the gNB-DUs may include one or more remote radio heads or radio frequency (RF) front end modules (RFEMs)
  • RFEMs radio frequency front end modules
  • the gNB-CU may be operated by a server (not shown) located in RAN 220 or by a server pool (e.g., a group of servers configured to share resources) in a similar manner as the CRAN/vBBUP.
  • one or more of RAN nodes 222 may be next generation eNBs (i.e., gNBs) that may provide evolved universal terrestrial radio access (E-UTRA) user plane and control plane protocol terminations toward UEs 210, and that may be connected to a 5G core network (5GC) 230 via an NG interface.
  • gNBs next generation eNBs
  • E-UTRA evolved universal terrestrial radio access
  • 5GC 5G core network
  • any of the RAN nodes 222 may terminate an air interface protocol and may be the first point of contact for UEs 210.
  • any of the RAN nodes 222 may fulfill various logical functions for the RAN 220 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • UEs 210 may be configured to communicate using orthogonal frequency-division multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 222 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a single carrier frequency-division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink (SL) communications) , although the scope of such implementations may not be limited in this regard.
  • the OFDM signals may comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 222 to UEs 210, and uplink transmissions may utilize similar techniques.
  • the grid may be a time-frequency grid (e.g., a resource grid or time-frequency resource grid) that represents the physical resource for downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block may comprise a collection of resource elements (REs) ; in the frequency domain, this may represent the smallest quantity of resources that currently may be allocated.
  • REs resource elements
  • RAN nodes 222 may be configured to wirelessly communicate with UEs 210, and/or one another, over a licensed medium (also referred to as the “licensed spectrum” and/or the “licensed band” ) , an unlicensed shared medium (also referred to as the “unlicensed spectrum” and/or the “unlicensed band” ) , or combination thereof.
  • a licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed band or spectrum may include the 5 GHz band.
  • an unlicensed spectrum may include the 5 GHz unlicensed band, a 6 GHz band, a 60 GHz millimeter wave band, and more.
  • a licensed spectrum may correspond to channels or frequency bands selected, reserved, regulated, etc., for certain types of wireless activity (e.g., wireless telecommunication network activity)
  • an unlicensed spectrum may correspond to one or more frequency bands that are not restricted for certain types of wireless activity.
  • Whether a particular frequency band corresponds to a licensed medium or an unlicensed medium may depend on one or more factors, such as frequency allocations determined by a public-sector organization (e.g., a government agency, regulatory body, etc. ) or frequency allocations determined by a private-sector organization involved in developing wireless communication standards and protocols, etc.
  • UEs 210 and the RAN nodes 222 may operate using stand-alone unlicensed operation, licensed assisted access (LAA) , eLAA, and/or feLAA mechanisms.
  • LAA licensed assisted access
  • UEs 210 and the RAN nodes 222 may perform one or more known medium-sensing operations or carrier-sensing operations to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum.
  • the medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the LAA mechanisms may be built upon carrier aggregation (CA) technologies of LTE-Advanced systems.
  • CA carrier aggregation
  • each aggregated carrier is referred to as a component carrier (CC) .
  • CC component carrier
  • individual CCs may have a different bandwidth than other CCs.
  • TDD time division duplex
  • the number of CCs as well as the bandwidths of each CC may be the same for DL and UL.
  • CA also comprises individual serving cells to provide individual CCs. The coverage of the serving cells may differ, for example, because CCs on different frequency bands will experience different pathloss.
  • a primary service cell or PCell may provide a primary component carrier (PCC) for both UL and DL and may handle RRC and non-access stratum (NAS) related activities.
  • PCC primary component carrier
  • NAS non-access stratum
  • the other serving cells are referred to as SCells, and each SCell may provide an individual secondary component carrier (SCC) for both UL and DL.
  • SCC secondary component carrier
  • the SCCs may be added and removed as required, while changing the PCC may require UE 210 to undergo a handover.
  • some or all the SCells may operate in the unlicensed spectrum (referred to as “LAA SCells” ) , and the LAA SCells are assisted by a PCell operating in the licensed spectrum.
  • LAA SCells When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different physical uplink shared channel (PUSCH) starting positions within a same subframe.
  • PUSCH physical uplink shared channel
  • UEs 210 and the RAN nodes 222 may also operate using stand-alone unlicensed operation where the UE may be configured with a PCell, in addition to any SCells, in unlicensed spectrum.
  • the PDSCH may carry user data and higher layer signaling to UEs 210.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things.
  • the PDCCH may also inform UEs 210 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel.
  • HARQ hybrid automatic repeat request
  • downlink scheduling e.g., assigning control and shared channel resource blocks to UE 210-2 within a cell
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of UEs 210.
  • the PDCCH uses control channel elements (CCEs) to convey the control information, wherein several CCEs (e.g., 6 or the like) may consists of a resource element groups (REGs) , where a REG is defined as a physical resource block (PRB) in an OFDM symbol.
  • CCEs control channel elements
  • REGs resource element groups
  • PRB physical resource block
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching, for example.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as REGs.
  • QPSK quadrature phase shift keying
  • Some implementations may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some implementations may utilize an extended (E) -PDCCH that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more ECCEs. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements known as an EREGs. An ECCE may have other numbers of EREGs in some situations.
  • the RAN nodes 222 may be configured to communicate with one another via interface 223.
  • interface 223 may be an X2 interface.
  • interface 223 may be an Xn interface.
  • SA standalone
  • interface 223 may be an Xn interface.
  • NSA non-standalone
  • interface 223 may represent an X2 interface and an XN interface.
  • the X2 interface may be defined between two or more RAN nodes 222 (e.g., two or more eNBs /gNBs or a combination thereof) that connect to evolved packet core (EPC) or CN 230, or between two eNBs connecting to an EPC.
  • EPC evolved packet core
  • the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C) .
  • the X2-U may provide flow control mechanisms for user data packets transferred over the X2 interface and may be used to communicate information about the delivery of user data between eNBs or gNBs.
  • RAN 220 may be connected (e.g., communicatively coupled) to CN 230.
  • CN 230 may comprise a plurality of network elements 232, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs 210) who are connected to the CN 230 via the RAN 220.
  • CN 230 may include an evolved packet core (EPC) , a 5G CN, and/or one or more additional or alternative types of CNs.
  • EPC evolved packet core
  • the components of the CN 230 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
  • network function virtualization may be utilized to virtualize any or all the above-described network node roles or functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below) .
  • a logical instantiation of the CN 230 may be referred to as a network slice, and a logical instantiation of a portion of the CN 230 may be referred to as a network sub-slice.
  • NFV Network Function Virtualization
  • NFV systems and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches.
  • NFV systems may be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.
  • CN 230, application servers 240, and external networks 250 may be connected to one another via interfaces 234, 236, and 238, which may include IP network interfaces.
  • Application servers 240 may include one or more server devices or network elements (e.g., virtual network functions (VNFs) offering applications that use IP bearer resources with CM 230 (e.g., universal mobile telecommunications system packet services (UMTS PS) domain, LTE PS data services, etc. ) .
  • Application servers 240 may also, or alternatively, be configured to support one or more communication services (e.g., voice over IP (VoIP sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc. ) for UEs 210 via the CN 230.
  • external networks 250 may include one or more of a variety of networks, including the Internet, thereby providing the mobile communication network and UEs 210 of the network access to a variety of additional services, information, interconnectivity, and other network features.
  • Air traffic control (ATC) servers 270 may include one or more servers, server devices, or network elements (e.g., VNFs) configured to send, receive, process, and/or store information.
  • ATC servers 270 may communicate with CN via connection or interface 272, which may include IP network interfaces.
  • ATC servers 270 may be operated by one or more air traffic control departments, organizations, or entities.
  • ATC servers 270 may include information about airplanes, jets, helicopters, drones, and/or other types of ariel transportation devices, including departure locations and times, flight patterns, current locations, updated flight patterns, arrival locations and times, altitudes, velocities, weather conditions, and more.
  • ATC servers 270 may receive information about UEs 222-3 and 222-4 from base stations 222, air traffic control towers or an air traffic control network (not shown) , etc., about changes in a current location and/or current flight path of UEs 222-3 and 222-4. ATC servers 270 may store such information and provide such information to base stations 222 (e.g., upon request, in accordance with an update schedule, etc. ) .
  • Figs. 3-9 are diagrams of example processes 300-900 according to one or more implementations described herein.
  • Processes 300-900 may be implemented by UE 210, serving base station 222-1, and target base station 222-2.
  • UE 210 and base stations 222-1 and 222-2 may be configured to implement one or more of processes 300-900 depending on, for example, a condition, trigger, scenario, or configuration of one or more of UE 210 and base stations 222-1 and 222-2.
  • some or all of processes 300 may be performed by one or more other systems or devices, including one or more of the devices of Fig. 2.
  • any of processes 300-900 may include one or more fewer, additional, differently ordered and/or arranged operations than those shown in any of Figs.
  • any of processes 300-900 may include operations preceding, performed in parallel with, and/or following one or more of the depicted operations. Some or all the operations of any of processes 300-900 may be performed independently, successively, simultaneously, etc., of one or more of the other operations of another of processes 300-900. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in any of Figs. 3-9.
  • Fig. 3 is a diagram of an example process 300 for a serving base station making a handover decision based on UE distances according to one or more implementations described herein.
  • process 300 may include serving base station 222-1 receiving location information from UE 210 (at 310) .
  • UE 210 may report location information (e.g., its current location) to base station 222-1.
  • base station 222-1 may use a DL channel to send UE 210 a request for location information, and UE 210 may provide the information in response to the request.
  • UE 210 may provide or report its location, with a time stamp and movement information (e.g., a speed and direction) .
  • base station 222-1 may use such information to determine or predict a current location of UE 210 based on the location information, timestamp or transmission time, movement information, and a current or reception time.
  • UE 210 may also provide a validity timer, such that base station 222 may use the location information, timestamp, and movement information, for the duration of the timer, to accurately or reliably determine or predict the location of UE 210.
  • Base station 222-1 may also receive location information for one or more base stations 222 in the area, such as target base station 222-2 (at 320) .
  • base station 222-1 may use a backhaul or Xn interface to send a request for location information to base station 222-2, and base station 222-2 may respond with the location information via the interface.
  • location information may be requested and received using higher layer node, such as an access and mobility function (AMF) or a location management function (LMF) .
  • AMF access and mobility function
  • LMF location management function
  • Process 300 may include serving base station 222-1 determining distances 1 and 2 based on the location information from UE 210 and base station 222-1 (at 330) .
  • a distance between UE 210 and serving base station 222-1 may be distance 1
  • a distance between base stations 222-1 and 222-2 may be distance 2.
  • Serving base station 222-1 may determine distances 1 and 2 based on a location of base station 222-1 and the location information received from UE 210 and base station 222-2.
  • Process 300 may also include base station 222-1 determining that distances 1 and distance 2 satisfy one or more distance threshold (at 340) .
  • distances 1 and 2 may satisfy the distance thresholds when distance 1 is greater than a first threshold distance and distance 2 is less than a threshold distance. Additionally, or alternatively, distances 1 and 2 may satisfy the distance thresholds when distance 1 exceeds distance 2 by at least a preselected or configured different (e.g., a preconfigured number (X) of meters) .
  • X preconfigured number
  • Process 300 may include serving base station 222-1 providing timing advance (TA) information to UE 210 and performing a handover procedure (block 350) .
  • the TA information may be to enable UE 210 to communicate with target base station 222-2.
  • serving base station 222-1 may provide UE 210 with location information of target base station 222-2, and UE 210 may derive the TA based on a current location of UE 210 and the location information of target base station 222-2.
  • the handover procedure may include an inter-frequency handover procedure or an intra-frequency handover procedure. Additionally, the handover procedure may include base station 222-1 sending a handover request to target base station 222-2, target base station 222-2 performing admission control, and base station 222-1 receiving a handover request acknowledgement from base station 222-2. The handover procedure may also include serving base station 222-1 sending UE 210 a handover trigger message and detaching from the serving base station 222-1, discovering, synchronizing, and connecting to target base station 222-2, etc. In some implementations, base station 222-1 may provide TA information to UE 210 regarding target base station 222-2. UE 210 may use the TA to transmit a random access channel (RACH) message to target base station 222-2.
  • RACH random access channel
  • the RACH Tx timing may be based on a DL reception time (from target base station 222-2) minus the TA.
  • UE 210 may use the TA information to contact and begin communicating with target base station 222-2 as part of the handover procedure. Additional and/or alternative operations (e.g., messages, types of information, etc. ) may be involved in performing the handover procedure.
  • Fig. 4 is a diagram of an example process 400 for serving base station 222-1 making a handover decision based on a UE flight path according to one or more implementations described herein.
  • process 400 may include serving base station 222-1 receiving location information from UE 210 (at 410) .
  • UE 210 may report location information (e.g., its current location) to base station 222-1.
  • base station 222-1 may use a DL channel to send UE 210 a request for location information, and UE 210 may provide the information in response to the request.
  • UE 210 may provide or report its location, with a time stamp and movement information (e.g., a speed and direction) .
  • base station 222-1 may use such information to determine or predict a current location of UE 210 based on the location information, timestamp or transmission time, movement information, and a current or reception time.
  • UE 210 may also provide a validity timer, such that base station 222 may use the location information, timestamp, and movement information, for the duration of the timer, to accurately or reliably determine or predict the location of UE 210.
  • Process 400 may include serving base station 222-1 obtaining a flight plan for UE 210 and compare a location of UE 210 with the flight plan (block 420) .
  • base station 222-2 may obtain a flight path for UE 210.
  • base station 222-2 may obtain the flight path by sending a request to UE 210 for the flight path and receiving the flight path in response thereto.
  • base station 222-1 may also, or alternatively, obtain the flight path by contacting another device, such as ATC servers 270 (see, Fig. 2) .
  • UE 210 may proactively provide base station 222-1 with a new or updated flight path upon diverting from or changing a previous flight path. Additionally, or alternatively, UE 210 may proactively update ATC servers 270, and ATC servers 270 may proactively update base station 222-1.
  • Base station 222-2 may determine a current location of UE 210 and compare the current location to the flight path. Based on the comparison, base station 222-2 may determine whether there has been a sudden change (e.g., unplanned) in flight pant for UE 210. When a sudden change to the flight path (e.g., UE 210 is not traveling consistent with the most recent flight path obtained by base station 222-1) , process 400 may proceed to implement one or more of examples 300, 500, or 600 of Figs. 3, 5, or 6 to detect and trigger a handover procedure for UE 210. When the flight plan has not suddenly changed, process 400 may include base station 222-2 comparing a current location of UE with a distance threshold relative to a flight path check point (at 430) .
  • a sudden change e.g., unplanned
  • the flight path may include one or more check points, and each check point may correspond to a handover procedure to be performed when UE 210 is within a threshold distance of the check point.
  • base station 222-1 may determine a distance between a current location of UE 210 and a check point of the flight path and compare the determined distance to a threshold distance. When the determined distance is greater than the threshold distance, process 400 may proceed by base station 222-1 continuing to monitor UE 210 for changes in the flight plan and changes in a distance between the UE 210 and the check point.
  • process 400 may proceed by base station 222-1 providing TA information to UE 210 and performing a handover procedure (block 440) .
  • the TA information may be to enable UE 210 to communicate with target base station 222-2.
  • serving base station 222-1 may provide UE 210 with location information of target base station 222-2, and UE 210 may derive the TA based on a current location of UE 210 and the location information of target base station 222-2.
  • the handover procedure may include an inter-frequency handover procedure or an intra-frequency handover procedure. Additionally, the handover procedure may include base station 222-1 sending a handover request to target base station 222-2, target base station 222-2 performing admission control, and base station 222-1 receiving a handover request acknowledgement from base station 222-2. The handover procedure may also include serving base station 222-1 sending UE 210 a handover trigger message and detaching from the serving base station 222-1, discovering, synchronizing, and connecting to target base station 222-2, etc. In some implementations, base station 222-1 may provide TA information to UE 210 regarding target base station 222-2. UE 210 may use the TA to transmit a random access channel (RACH) message to target base station 222-2.
  • RACH random access channel
  • the RACH Tx timing may be based on a DL reception time (from target base station 222-2) minus the TA.
  • UE 210 may use the TA information to contact and begin communicating with target base station 222-2 as part of the handover procedure. Additional and/or alternative operations (e.g., messages, types of information, etc. ) may be involved in performing the handover procedure.
  • Fig. 5 is a diagram of an example process 500 for a serving base station making a handover decision based on a distance report from a UE according to one or more implementations described herein.
  • process 500 may include serving base station 222-1 providing UE 210 with location information of one or more target base stations 222-2 (at 510) .
  • Base station 222-1 may have this information stored locally and/or may obtain it from other base stations 222 as describe above.
  • the location information may be a preconfigured list of base stations 222 or a list of base stations 222 that are identified based on a current position, direction, and speed of UE 210, a travel path, and/or one or more factors.
  • Process 500 may include base station 222-1 providing UE 210 with configuration information about distances and/or conditions related to handover procedures (at 520) .
  • the configuration information may define a first distance (distance 1) as a distance between serving base station 222-1 and UE 210.
  • the configuration information may define a second distance (distance 2) as a distance between UE 210 and one or more target base stations 222-2. This may include target base stations 222-2 identified by the location information of target base stations provided to UE 210 previously.
  • the configuration information about distances and/or conditions may include a first threshold (threshold 1) for distance 1, a second threshold (threshold 2) , and a third threshold (threshold 3) for a difference between distance 1 and distance 2.
  • Process 500 may include UE 210 determining or calculating distance 1 and distance 2 (at 530) .
  • Process 500 may also include UE 210 comparing distances 1 and 2 to thresholds 1 and 2, respectively.
  • UE 210 may return to determining or calculating distances 1 and distance 2 (at 530) and comparing them to thresholds 1 and 2, respectively.
  • process 500 may proceed with UE 210 reporting or communicating to base station 222-1 that distance condition has been met (at 550) .
  • UE 210 may determine that the distance condition has been met when distance 1 is above threshold 1 and distance 2 is blow threshold 2. Additionally, or alternatively, UE 210 may determine that the distance condition has been met when distance 1 minus distance 2 is greater than threshold 3.
  • Process 500 may include base station 222-1 responding by base station 222-1 providing TA information to UE 210 and performing a handover procedure (block 560) .
  • the TA information may be to enable UE 210 to communicate with target base station 222-2.
  • serving base station 222-1 may provide UE 210 with location information of target base station 222-2, and UE 210 may derive the TA based on a current location of UE 210 and the location information of target base station 222-2.
  • the handover procedure may include an inter-frequency handover procedure or an intra-frequency handover procedure. Additionally, the handover procedure may include base station 222-1 sending a handover request to target base station 222-2, target base station 222-2 performing admission control, and base station 222-1 receiving a handover request acknowledgement from base station 222-2. The handover procedure may also include serving base station 222-1 sending UE 210 a handover trigger message and detaching from the serving base station 222-1, discovering, synchronizing, and connecting to target base station 222-2, etc. In some implementations, base station 222-1 may provide TA information to UE 210 regarding target base station 222-2. UE 210 may use the TA to transmit a random access channel (RACH) message to target base station 222-2.
  • RACH random access channel
  • the RACH Tx timing may be based on a DL reception time (from target base station 222-2) minus the TA.
  • UE 210 may use the TA information to contact and begin communicating with target base station 222-2 as part of the handover procedure. Additional and/or alternative operations (e.g., messages, types of information, etc. ) may be involved in performing the handover procedure.
  • Fig. 6 is a diagram of an example process 600 for a serving base station making a handover decision based on a signal strength and quality report from a UE according to one or more implementations described herein.
  • process 600 may include serving base station 222-1 providing UE 210 with a distance threshold for serving base station 222-1 (at 610) .
  • the distance threshold may pertain to a distance (distance 1) between UE 210 and serving base station 222-1.
  • the distance threshold may be preconfigured or preselected (e.g., stored in a local memory as a configuration setting) .
  • base station 222-1 may determine the distance threshold based on location, velocity, travel pattern, trajectory, device type, etc., of UE 210.
  • Process 600 may also include serving base station 222-1 providing location information for one or more target base stations 222-2 and RSRP and/or RSRQ conditions (at 620) .
  • RSRP and/or RSRQ condition may depend on a network configuration. For example, when the network relies on HO signal strength, then an RSRP condition may be used. By contrast, when the network relies on HO signal quality (quality being different from pure strength because an interference level may also be included in a quality indicator) then an RSRQ condition may be used.
  • Process 600 may include UE 210 determining that distance 1 satisfies the distance threshold (at 630) .
  • UE 210 may determine a distance between UE 210 and serving base station 222-1 and may compare the determined distance to the threshold distance received from base station 222-1.
  • UE 210 may determine the distance (distance 1) based on a location of UE 210 and a location of serving base station 222-1, signal delays (e.g., a delay between a Tx time and a Rx time) between signals from UE 210 and base station 222-1, etc.
  • signal delays e.g., a delay between a Tx time and a Rx time
  • the UE 210 may compare the RSRP and/or RSRQ signal values or measurements to the signal threshold (s) to determine whether the threshold (s) are satisfied.
  • the signaling conditions may be satisfied when an RSRP and/or RSRQ signal of target base station 222-2 satisfies a corresponding threshold (s) .
  • the signaling conditions may be satisfied when an RSRP and/or RSRQ signal of serving base station 222-1 and/or target base station 222-2 satisfy corresponding thresholds-for instance when an RSRP and/or RSRQ signal of serving base station 222-1 is below a first threshold and an RSRP and/or RSRQ signal of target base station 222-2 is above second threshold.
  • the signaling conditions may be satisfied when a difference between an RSRP and/or RSRQ signal of serving base station 222-1 and an RSRP and/or RSRQ signal of target base station 222-2 is larger than a corresponding threshold (e.g., a threshold number (N) of dB) .
  • a corresponding threshold e.g., a threshold number (N) of dB.
  • process 600 may return to UE 210 calculating, monitoring, and/or determining whether distance 1 satisfies the distance threshold (at 630) .
  • process 600 may proceed by UE 210 reporting to serving base station 222-1 that the RSRP and/or RSRQ condition has been satisfied (at 650) .
  • process 600 may proceed by serving base station 222-1 responding by base station 222-1 providing TA information to UE 210 and performing a handover procedure (block 660) .
  • the TA information may be to enable UE 210 to communicate with target base station 222-2.
  • serving base station 222-1 may provide UE 210 with location information of target base station 222-2, and UE 210 may derive the TA based on a current location of UE 210 and the location information of target base station 222-2.
  • the handover procedure may include an inter-frequency handover procedure or an intra-frequency handover procedure. Additionally, the handover procedure may include base station 222-1 sending a handover request to target base station 222-2, target base station 222-2 performing admission control, and base station 222-1 receiving a handover request acknowledgement from base station 222-2. The handover procedure may also include serving base station 222-1 sending UE 210 a handover trigger message and detaching from the serving base station 222-1, discovering, synchronizing, and connecting to target base station 222-2, etc. In some implementations, base station 222-1 may provide TA information to UE 210 regarding target base station 222-2. UE 210 may use the TA to transmit a random access channel (RACH) message to target base station 222-2.
  • RACH random access channel
  • the RACH Tx timing may be based on a DL reception time (from target base station 222-2) minus the TA.
  • UE 210 may use the TA information to contact and begin communicating with target base station 222-2 as part of the handover procedure. Additional and/or alternative operations (e.g., messages, types of information, etc. ) may be involved in performing the handover procedure.
  • Fig. 7 is a diagram of an example process 700 for UE 210 making a handover decision based on UE distances according to one or more implementations described herein.
  • process 700 may include serving base station 222-1 providing UE 210 with location information of one or more target base stations 222-2 (at 710) .
  • Base station 222-1 may have this information stored locally and/or may obtain it from other base stations 222 as describe above.
  • the location information may be a preconfigured list of base stations 222 or a list of base stations 222 that are identified based on a current position, direction, and speed of UE 210, a travel path of UE 210, and/or one or more factors.
  • Process 700 may include base station 222-1 providing UE 210 with configuration information about distances and/or conditions related to handover procedures (at 720) .
  • the configuration information may define a first distance (distance 1) as a distance between serving base station 222-1 and UE 210.
  • the configuration information may define a second distance (distance 2) as a distance between UE 210 and one or more target base stations 222-2. This may include target base stations 222-2 identified by the location information of potential target base stations provided to UE 210 previously.
  • the configuration information about distances and/or conditions may include a first threshold (threshold 1) for distance 1, a second threshold (threshold 2) , and a third threshold (threshold 3) for a difference between distance 1 and distance 2.
  • Process 700 may include UE 210 determining or calculating distance 1 and distance 2 (at 730) .
  • Process 700 may also include UE 210 comparing distances 1 and 2 to thresholds 1 and 2, respectively.
  • UE 210 may return to a previous operation, such as serving base station 222-1 providing UE 210 with location information of one or more target base stations 222-2 (at 710) .
  • process 700 may proceed with UE 210 triggering a handover procedure toward target base station 222-2, where UE 210 may use a UE-specific TA to communicate with target base station 222-2 (at 750) .
  • UE 210 may determine the UE-specific TA based on a distance between UE 210 and target base station 222-2.
  • a UE-specific TA may include a round-trip-time (RRT) derived from a propagation delay from target base station 222-2 to UE 210. So, the TA may equal RTT, which may equal two times the propagation delay or two times a distance between target base station 222-2 to UE 210 divided the speed of light.
  • the handover procedure may include an inter-frequency handover procedure or an intra-frequency handover procedure.
  • the handover procedure triggered by UE 210 may include UE 210 detaching from an original serving cell and transmitting a RACH message directly to the target cell.
  • the RACH transmission timing may be based on a DL reception timing of the target cell minus the UE-specific TA. There may be no additional information exchange between base stations 222 after UE 210 satisfies the HO condition.
  • Fig. 8 is a diagram of an example process 800 for a UE making a handover decision based on a UE flight path according to one or more implementations described herein.
  • process 800 may include UE 210 determining a current flight path and location of UE 210 (at 810) .
  • UE 210 may obtain a current flight path by communicating (via base station 222-1) a request to ATC servers 270 for a flight path for UE 210 and receiving a flight path in response thereto.
  • UE 210 may obtain a current flight path from a local or internal system (e.g., an on-board computerized system of the airplane, drone, etc. ) .
  • UE 210 may determine a current location of UE 210 via self-positioning.
  • Self-positioning may include UE 210 determining its location using a global positioning system (GPS) , a Global navigation satellite system (GNSS) , etc.
  • GPS global positioning system
  • GNSS Global navigation satellite system
  • Process 800 may include UE 210 comparing a current flight path with a current location of UE 210 (at 820) .
  • UE 210 may determine a current location of UE 210 and compare the current location with the flight path to determine whether a sudden change in the flight path has occurred.
  • UE 210 may determine this by comparing a distance from a flight path coordinate to the current location and determining whether the differential exceeds a preconfigured threshold.
  • process 800 may proceed to evaluate and/or perform a handover procedure in accordance with one or more of the operations of Fig. 7.
  • UE 210 may request and receive an updated flight path from, for example, serving base station 222-1 or ATC servers 270 (not shown) .
  • the updated flight path may be viewed or used as a current flight path.
  • process 800 may proceed by UE 210 determining whether a current location of UE 210 is within a threshold distance of a flight path check point.
  • the flight path may include one or more check points, and each check point may correspond to a handover procedure to be performed when UE 210 is within a threshold distance of the check point.
  • UE 210 may determine a distance between a current location of UE 210 and a check point of the flight path and compare the determined distance to a threshold distance. When the determined distance is greater than the threshold distance, process 800 may proceed by UE 210 continuing to monitor changes in the flight plan and changes in a distance between the UE 210 and the check point (at 820 and 830) .
  • process 800 may proceed by UE 210 triggering a handover procedure toward target base station 222-2, where UE 210 may use a UE-specific TA to communicate with target base station 222-2 (at 850) .
  • UE 210 may determine the UE-specific TA based on a distance between UE 210 and target base station 222-2.
  • the handover procedure may include an inter-frequency handover procedure or an intra-frequency handover procedure.
  • the handover procedure triggered by UE 210 may include UE 210 detaching from an original serving cell and transmitting a RACH message directly to the target cell.
  • the RACH transmission timing may be based on a DL reception timing of the target cell minus the UE-specific TA. There may be no additional information exchange between base stations 222 after UE 210 satisfies the HO condition.
  • Fig. 9 is a diagram of an example process 900 for serving base station 222-1 making a handover decision based on UE 210 reaching a flight path checkpoint according to one or more implementations described herein.
  • process 900 may include UE 210 determining a current flight path and location of UE 210 (at 910) .
  • UE 210 may obtain a current flight path by communicating (via base station 222-1) a request to ATC servers 270 for a flight path for UE 210 and receiving a flight path in response thereto.
  • UE 210 may obtain a current flight path from a local or internal system (e.g., an on-board computerized system of the airplane, drone, etc. ) .
  • UE 210 may determine a current location of UE 210 via self-positioning.
  • Self-positioning may include UE 210 determining its location using a global positioning system (GPS) , a Global navigation satellite system (GNSS) , etc.
  • GPS global positioning system
  • Process 900 may include UE 210 comparing a current flight path with a current location of UE 210 (at 920) .
  • UE 210 may determine a current location of UE 210 and compare the current location with the flight path to determine whether a sudden change in the flight path has occurred.
  • UE 210 may determine this by comparing a distance from a flight path coordinate to the current location and determining whether the differential exceeds a preconfigured threshold.
  • process 900 may proceed to evaluate and/or perform a handover procedure in accordance with one or more of the operations of Figs. 3, 5, 6, and/or 7) .
  • UE 210 may request and receive an updated flight path from, for example, serving base station 222-1 or ATC servers 270 (not shown) .
  • the updated flight path may be viewed or used as a current flight path.
  • process 900 may proceed by UE 210 determining whether a current location of UE 210 is within a threshold distance of a flight path check point.
  • the flight path may include one or more check points, and each check point may correspond to a handover procedure to be performed when UE 210 is within a threshold distance of the check point.
  • UE 210 may determine a distance between a current location of UE 210 and a check point of the flight path and compare the determined distance to a threshold distance. When the determined distance is greater than the threshold distance, process 900 may proceed by UE 210 continuing to monitor changes in the flight plan and changes in a distance between the UE 210 and the check point (at 920 and 930) . When the determined distance is less than the threshold distance (at 940) , process 900 may proceed by UE 210 reporting or communicating to base station 222-1 that distance condition has been met (at 950) .
  • Process 900 may include base station 222-1 responding by base station 222-1 providing triggering a handover procedure (block 960) .
  • the handover procedure may include an inter-frequency handover procedure or an intra-frequency handover procedure. Additionally, the handover procedure may include base station 222-1 sending a handover request to target base station 222-2, target base station 222-2 performing admission control, and base station 222-1 receiving a handover request acknowledgement from base station 222-2.
  • the handover procedure may also include serving base station 222-1 sending UE 210 a handover trigger message and detaching from the serving base station 222-1, discovering, synchronizing, and connecting to target base station 222-2, etc.
  • UE 210 may use a TA to communicate (e.g., to transmit a RACH message) with target base station 222-2.
  • the TA may be based on a distance between UE 210 and target base station 222-2.
  • the TA may be a preconfigured TA (e.g., preconfigured by the network) according to each check point along a flight path.
  • Fig. 10 is a diagram of an example of components of a device according to one or more implementations described herein.
  • the device 1000 can include application circuitry 1002, baseband circuitry 1004, RF circuitry 1006, front-end module (FEM) circuitry 1008, one or more antennas 1010, and power management circuitry (PMC) 1012 coupled together at least as shown.
  • the components of the illustrated device 1000 can be included in a UE or a RAN node.
  • the device 1000 can include fewer elements (e.g., a RAN node may not utilize application circuitry 1002, and instead include a processor/controller to process IP data received from a CN or an Evolved Packet Core (EPC) ) .
  • EPC Evolved Packet Core
  • the device 1000 can include additional elements such as, for example, memory/storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device 1000, etc. ) , or input/output (I/O) interface.
  • additional elements such as, for example, memory/storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device 1000, etc. ) , or input/output (I/O) interface.
  • the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for Cloud-RAN (C-RAN) implementations) .
  • C-RAN Cloud-RAN
  • the application circuitry 1002 can include one or more application processors.
  • the application circuitry 1002 can include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor (s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc. ) .
  • the processors can be coupled with or can include memory/storage and can be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 1000.
  • processors of application circuitry 1002 can process IP data packets received from an EPC.
  • the baseband circuitry 1004 can include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 1004 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 1006 and to generate baseband signals for a transmit signal path of the RF circuitry 1006.
  • Baseband circuity 1004 can interface with the application circuitry 1002 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1006.
  • the baseband circuitry 1004 can include a 3G baseband processor 1004A, a 4G baseband processor 1004B, a 5G baseband processor 1004C, or other baseband processor (s) 1004D for other existing generations, generations in development or to be developed in the future (e.g., 5G, 6G, etc. ) .
  • the baseband circuitry 1004 e.g., one or more of baseband processors 1004A-D
  • some or all the functionality of baseband processors 1004A-D can be included in modules stored in the memory 1004G and executed via a Central Processing Unit (CPU) 1004E.
  • CPU Central Processing Unit
  • the radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 1004 can include Fast-Fourier Transform (FFT) , precoding, or constellation mapping/de-mapping functionality.
  • encoding/decoding circuitry of the baseband circuitry 1004 can include convolution, tail-biting convolution, turbo, Viterbi, or Low-Density Parity Check (LDPC) encoder/decoder functionality. Implementations of modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other implementations.
  • memory 1004G may receive and store one or more configurations, instructions, and/or other types of information for enabling enhanced ATG handover procedures for high-velocity UEs, as described herein with respect to Figs. 3-9.
  • the enhanced ATG handover procedures may include a UE 210 or serving base station 222 making a handover decision based on distances between UE 210 and serving base stations 222 and target base station 222.
  • UE 210 or serving base station 222 may make a handover decision based on a UE flight path, including changes in a UE flight path or UE 210 reaching a flight path checkpoint (e.g., a location identified along the flightpath) .
  • flight path checkpoint e.g., a location identified along the flightpath
  • serving base station 222 may make a handover decision based on a distance report from UE 210 or UE 110 may make the handover decision based on a signal strength and/or quality from target base station 222. Additional details and examples of these and other implementations are described below with reference to the Figures.
  • the baseband circuitry 1004 can include one or more audio digital signal processor (s) (DSP) 1004F.
  • the audio DSPs 1004F can include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other implementations.
  • Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some implementations.
  • some or all the constituent components of the baseband circuitry 1004 and the application circuitry 1002 can be implemented together such as, for example, on a system on a chip (SOC) .
  • SOC system on a chip
  • the baseband circuitry 1004 can provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 1004 can support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) , etc.
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • RF circuitry 1006 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 1006 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 1006 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 1008 and provide baseband signals to the baseband circuitry 1004.
  • RF circuitry 1006 can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by the baseband circuitry 1004 and provide RF output signals to the FEM circuitry 1008 for transmission.
  • the receive signal path of the RF circuitry 1006 can include mixer circuitry 1006A, amplifier circuitry 1006B and filter circuitry 1006C.
  • the transmit signal path of the RF circuitry 1006 can include filter circuitry 1006C and mixer circuitry 1006A.
  • RF circuitry 1006 can also include synthesizer circuitry 1006D for synthesizing a frequency for use by the mixer circuitry 1006A of the receive signal path and the transmit signal path.
  • the mixer circuitry 1006A of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 1008 based on the synthesized frequency provided by synthesizer circuitry 1006D.
  • the amplifier circuitry 1006B can be configured to amplify the down-converted signals and the filter circuitry 1006C can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals can be provided to the baseband circuitry 1004 for further processing.
  • the output baseband signals can be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 1006A of the receive signal path can comprise passive mixers, although the scope of the implementations is not limited in this respect.
  • the mixer circuitry 1006A of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1006D to generate RF output signals for the FEM circuitry 1008.
  • the baseband signals can be provided by the baseband circuitry 1004 and can be filtered by filter circuitry 1006C.
  • the mixer circuitry 1006A of the receive signal path and the mixer circuitry 1006A of the transmit signal path can include two or more mixers and can be arranged for quadrature down conversion and up conversion, respectively.
  • the mixer circuitry 1006A of the receive signal path and the mixer circuitry 1006A of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection) .
  • the mixer circuitry 1006A of the receive signal path and the mixer circuitry 1406A can be arranged for direct down conversion and direct up conversion, respectively.
  • the mixer circuitry 1006A of the receive signal path and the mixer circuitry 1006A of the transmit signal path can be configured for super-heterodyne operation.
  • the output baseband signals, and the input baseband signals can be analog baseband signals, although the scope of the implementations is not limited in this respect.
  • the output baseband signals, and the input baseband signals can be digital baseband signals.
  • the RF circuitry 1006 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1004 can include a digital baseband interface to communicate with the RF circuitry 1006.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the implementations is not limited in this respect.
  • the synthesizer circuitry 1006D can be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the implementations is not limited in this respect as other types of frequency synthesizers can be suitable.
  • synthesizer circuitry 1006D can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 1006D can be configured to synthesize an output frequency for use by the mixer circuitry 1006A of the RF circuitry 1006 based on a frequency input and a divider control input.
  • the synthesizer circuitry 1006D can be a fractional N/N+1 synthesizer.
  • frequency input can be provided by a voltage-controlled oscillator (VCO) , although that is not a requirement.
  • VCO voltage-controlled oscillator
  • Divider control input can be provided by either the baseband circuitry 1004 or the applications circuitry 1002 depending on the desired output frequency.
  • a divider control input e.g., N
  • N can be determined from a look-up table based on a channel indicated by the applications circuitry 1002.
  • Synthesizer circuitry 1006D of the RF circuitry 1006 can include a divider, a delay-locked loop (DLL) , a multiplexer and a phase accumulator.
  • the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA) .
  • the DMD can be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 1006D can be configured to generate a carrier frequency as the output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency can be a LO frequency (fLO) .
  • the RF circuitry 1006 can include an IQ/polar converter.
  • FEM circuitry 1008 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 1010, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1006 for further processing.
  • FEM circuitry 1008 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 1006 for transmission by one or more of the one or more antennas 1010.
  • the amplification through the transmit or receive signal paths can be done solely in the RF circuitry 1006, solely in the FEM circuitry 1008, or in both the RF circuitry 1006 and the FEM circuitry 1008.
  • the FEM circuitry 1008 can include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry can include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry can include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1006) .
  • the transmit signal path of the FEM circuitry 1008 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1006) , and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1010) .
  • PA power amplifier
  • the PMC 1012 can manage power provided to the baseband circuitry 1004.
  • the PMC 1012 can control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 1012 can often be included when the device 1000 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 1012 can increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • Fig. 10 shows the PMC 1012 coupled only with the baseband circuitry 1004.
  • the PMC 1012 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 1002, RF circuitry 1006, or FEM circuitry 1008.
  • the PMC 1012 can control, or otherwise be part of, various power saving mechanisms of the device 1000. For example, if the device 1000 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it can enter a state known as discontinuous reception mode (DRX) after a period of inactivity. During this state, the device 1000 can power down for brief intervals of time and thus save power.
  • DRX discontinuous reception mode
  • the device 1000 can transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 1000 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 1000 may not receive data in this state; in order to receive data, it can transition back to RRC_Connected state.
  • An additional power saving mode can allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours) . During this time, the device is unreachable to the network and can power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 1002 and processors of the baseband circuitry 1004 can be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 1004 alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the baseband circuitry 1004 can utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers) .
  • Layer 3 can comprise a RRC layer, described in further detail below.
  • Layer 2 can comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 can comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • Fig. 11 is a block diagram illustrating components, according to some example implementations, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Fig. 11 shows a diagrammatic representation of hardware resources 1100 including one or more processors (or processor cores) 1110, one or more memory/storage devices 1120, and one or more communication resources 1130, each of which may be communicatively coupled via a bus 1140.
  • node virtualization e.g., NFV
  • a hypervisor may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1100
  • the processors 1110 may include, for example, a processor 1112 and a processor 1114.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the memory/storage devices 1120 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1120 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random-access memory (DRAM) , static random-access memory (SRAM) , erasable programmable read-only memory (EPROM) , electrically erasable programmable read-only memory (EEPROM) , Flash memory, solid-state storage, etc.
  • DRAM dynamic random-access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • memory/storage devices 1120 may receive and store one or more configurations, instructions, and/or other type of information 1155 for enabling ATG handover procedures for high-velocity UEs.
  • UE 210 or serving base station 222 may make a handover decision based on distances between UE 210 and serving base stations 222 and target base station 222.
  • UE 210 or serving base station 222 may make a handover decision based on a UE flight path, including changes in a UE flight path or UE 210 reaching a flight path checkpoint (e.g., a location identified along the flightpath) .
  • serving base station 222 may make a handover decision based on a distance report from UE 210 or UE 110 may make the handover decision based on a signal strength and/or quality from target base station 222. Additional details and examples of these and other implementations are described below with reference to the Figures.
  • the communication resources 1130 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1104 or one or more databases 1106 via a network 1108.
  • the communication resources 1130 may include wired communication components (e.g., for coupling via a universal serial bus (USB) ) , cellular communication components, NFC components, components (e.g., low energy) , components, and other communication components.
  • Instructions 1150 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1110 to perform any one or more of the methodologies discussed herein.
  • the instructions 1150 may reside, completely or partially, within at least one of the processors 1110 (e.g., within the processor’s cache memory) , the memory/storage devices 1120, or any suitable combination thereof.
  • any portion of the instructions 1150 may be transferred to the hardware resources 1100 from any combination of the peripheral devices 1104 or the databases 1106. Accordingly, the memory of processors 1110, the memory/storage devices 1120, the peripheral devices 1104, and the databases 1106 are examples of computer-readable and machine-readable media.
  • Examples herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor (e.g., processor , etc. ) with memory, an application-specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to implementations and examples described.
  • a machine e.g., a processor (e.g., processor , etc. ) with memory, an application-specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , or the like
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • a user equipment may comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the UE to: receive, from a serving base station, a distance threshold corresponding to the serving base station; receive, from the serving base station, a location information and signal condition of a target base station; determine that a distance, between the UE and the serving base station, satisfies the distance threshold; determine that signaling, from the target base station, satisfies the signal condition; and report, to the serving base station, that the signaling condition is satisfied to trigger a handover procedure.
  • the signal condition comprises a reference signal received power (RSRP) threshold.
  • the signal condition comprises a reference signal received quality (RSRQ) threshold.
  • the signal condition comprises an RSRP/RSRQ threshold.
  • the signal condition comprises when an RSRP/RSRQ of the serving base station being below a first signal threshold and an RSRP/RSRQ of the target base station is above a second signal threshold.
  • the signal condition comprises a difference between an RSRP/RSRQ of the serving base station and an RSRP/RSRQ of the target base station being greater than a threshold difference.
  • the UE is to determine that the signaling satisfies the signal condition upon determining that the distance satisfies the distance threshold.
  • the UE is to receive, from the serving base station, a timing advance (TA) value for communicating with the target base station.
  • TA timing advance
  • the UE is to participate in the handover procedure by communicating with the target base station based on the TA value.
  • the UE is to: receive, from the serving base station, location information of the target base station; derive, based on a location of the UE and the target base station, a timing advance (TA) value for communicating with the target base station; and participate in the handover procedure by communicating with the target base station based on the TA value.
  • a user equipment may comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the UE to: receive, from a serving base station, location information of a target base station; receive, from the serving base station, configuration information for one or more distance conditions, determine a first distance from the UE to the serving base station; determine, based on the location information, a second distance from the UE to the target base station; and when the first distance and the second distance satisfy the one or more distance conditions, trigger a handover procedure toward the target base station.
  • the one or more distance conditions comprise a first distance threshold and a second distance threshold that is different from the first distance threshold.
  • the first distance threshold corresponds to the serving base station and the second distance threshold corresponds to the target base station.
  • the one or more distance conditions comprises a difference between the first distance and the second distance.
  • the UE is to trigger the handover procedure when the difference between the first distance and the second distance satisfies a third distance threshold.
  • the UE is to participate in the handover procedure based on a timing advance (TA) value for communicating with the target base station.
  • TA timing advance
  • the UE is to derive the TA value based on a distance between the UE and the target base station.
  • a method, performed, by a user equipment may comprise: receiving, from a serving base station, a distance threshold corresponding to the serving base station; receiving, from the serving base station, a location information and signal condition of a target base station; determining that a distance, between the UE and the serving base station, satisfies the distance threshold; determining that signaling, from the target base station, satisfies the signal condition; and reporting, to the serving base station, that the signaling condition is satisfied to trigger a handover procedure.
  • the term “or” is intended to mean an inclusive “or” rather than an exclusive “or. ” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances.
  • the articles “a” and “an” as used in this application and the appended claims should be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Techniques permettant d'activer des procédures de transfert air-sol (ATG) amélioré pour un équipement utilisateur (UE) à grande vitesse, tel qu'un avion, un jet, un drone, etc. Un UE ou une station de base de desserte peuvent prendre une décision de transfert sur la base de distances entre l'UE et les stations de base de desserte et une station de base cible. Dans certains scénarios, l'UE ou la station de base de desserte peut prendre une décision de transfert sur la base d'un trajet de vol d'UE, comprenant des changements dans le trajet de vol d'UE, ou l'UE atteignant un point de contrôle de trajet de vol (par exemple, un emplacement identifié le long du trajet de vol). Dans certains scénarios, la station de base de desserte peut prendre une décision de transfert sur la base d'un rapport de distance à partir de l'UE, ou l'UE peut prendre la décision de transfert sur la base d'une intensité et/ou d'une qualité de signal à partir d'une station de base cible. Des détails et des exemples supplémentaires de ces derniers et de nombreuses autres caractéristiques et techniques sont décrits ici.
PCT/CN2022/123265 2022-09-30 2022-09-30 Systèmes, procédés et dispositifs pour un transfert air-sol (atg) amélioré WO2024065673A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/123265 WO2024065673A1 (fr) 2022-09-30 2022-09-30 Systèmes, procédés et dispositifs pour un transfert air-sol (atg) amélioré

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/123265 WO2024065673A1 (fr) 2022-09-30 2022-09-30 Systèmes, procédés et dispositifs pour un transfert air-sol (atg) amélioré

Publications (1)

Publication Number Publication Date
WO2024065673A1 true WO2024065673A1 (fr) 2024-04-04

Family

ID=83995665

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/123265 WO2024065673A1 (fr) 2022-09-30 2022-09-30 Systèmes, procédés et dispositifs pour un transfert air-sol (atg) amélioré

Country Status (1)

Country Link
WO (1) WO2024065673A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090168722A1 (en) * 2007-10-08 2009-07-02 Yousuf Saifullah Handover procedure
WO2019133049A1 (fr) * 2017-12-30 2019-07-04 Intel Corporation Technologie relative au transfert intercellulaire, appareil et procédés associés
US20200275324A1 (en) * 2017-09-21 2020-08-27 Nokia Technologies Oy Handover improvement for air-to-ground system
US20200351734A1 (en) * 2019-05-02 2020-11-05 Qualcomm Incorporated Conditional handover (cho) deconfiguration and failure handling in wireless communications
WO2021062729A1 (fr) * 2019-09-30 2021-04-08 Oppo广东移动通信有限公司 Procédé de traitement de transfert, dispositif de communication, et dispositif terminal

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090168722A1 (en) * 2007-10-08 2009-07-02 Yousuf Saifullah Handover procedure
US20200275324A1 (en) * 2017-09-21 2020-08-27 Nokia Technologies Oy Handover improvement for air-to-ground system
WO2019133049A1 (fr) * 2017-12-30 2019-07-04 Intel Corporation Technologie relative au transfert intercellulaire, appareil et procédés associés
US20200351734A1 (en) * 2019-05-02 2020-11-05 Qualcomm Incorporated Conditional handover (cho) deconfiguration and failure handling in wireless communications
WO2021062729A1 (fr) * 2019-09-30 2021-04-08 Oppo广东移动通信有限公司 Procédé de traitement de transfert, dispositif de communication, et dispositif terminal

Similar Documents

Publication Publication Date Title
WO2022082662A1 (fr) Entretien d'avance temporelle (ta) dans des réseaux non terrestres (ntn)
WO2022082632A1 (fr) Critères de sélection et resélection de cellules pour des réseaux de type réseau non terrestre (ntn)
EP4150949A1 (fr) Systèmes et procédés de reprise sur défaillance de faisceau pour mode à multiples dci
WO2024065673A1 (fr) Systèmes, procédés et dispositifs pour un transfert air-sol (atg) amélioré
US20240178962A1 (en) Systems, methods, and devices for scheduling restrictions based on needforgap capabilities of user equipment
WO2023010515A1 (fr) Systèmes, procédés et dispositifs de commande de puissance et de sélection de faisceau dans un trafic mixte
US20230370217A1 (en) Systems, methods, and devices for secondary cell activation with ue-specific reference signal
WO2023205934A1 (fr) Systèmes, procédés et dispositifs de détection d'intervalles de mesure se chevauchant
US20230318682A1 (en) Systems, methods, and devices for enhanced beam selection
US11838089B2 (en) Systems and methods for control signaling for beam searching latency reduction
WO2023206384A1 (fr) Systèmes, procédés et dispositifs d'acquisition et de mise à jour d'avance temporelle de liaison montante dans un réseau de communication sans fil
WO2023206011A1 (fr) Systèmes, procédés et dispositifs pour une transmission de données courtes (sdt) améliorée
US20240057166A1 (en) Systems, methods, and apparatuses for quasi-co-location (qcl) and spatial relation assumptions during random access procedures
WO2022213231A1 (fr) Partage de spectre dynamique (dss) amélioré dans des groupes de cellules
WO2023151061A1 (fr) Systèmes, procédés et dispositifs de coordination inter-ue (iuc) de couche de mac et d'utilisation de ressources
WO2022094754A1 (fr) Identité et radiomessagerie de cellule pour réseaux non terrestres (ntn)
WO2023130481A1 (fr) Amélioration de la sélection de ressources pour un équipement utilisateur (ue) de réception discontinue de liaison latérale (drx)
WO2023151062A1 (fr) Systèmes, procédés et dispositifs de coordination inter-ue (iuc) de couche mac
WO2023044782A1 (fr) Systèmes, procédés et dispositifs pour des transmissions de canal de commande communes dans un réseau de communication sans fil
WO2023130460A1 (fr) Systèmes, procédés et dispositifs pour une économie d'énergie améliorée par l'intermédiaire d'une signalisation de référence dynamique
WO2023201702A1 (fr) Systèmes, procédés et dispositifs pour réduire des interruptions durant la désactivation d'un groupe de cellules secondaires
WO2024000171A1 (fr) Systèmes, procédés et dispositifs de gestion de mac de mtrp pour la mobilité inter-du et intra-cu d'un ue
WO2023044728A1 (fr) Systèmes, procédés et dispositifs de signalisation d'accès initial dans un réseau de communication sans fil
WO2023044824A1 (fr) Intervalle de mesure (mg) et conception d'interruption pour lecture d'informations de système (si) dans un module d'identité d'abonné universel multiple (musim)
WO2024063889A1 (fr) Systèmes, procédés et dispositifs pour faisceaux de liaison de commande et de backhaul

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22793644

Country of ref document: EP

Kind code of ref document: A1