WO2018232560A1 - Transfert intercellulaire de repli pour support d'application dans des systèmes sans fil - Google Patents

Transfert intercellulaire de repli pour support d'application dans des systèmes sans fil Download PDF

Info

Publication number
WO2018232560A1
WO2018232560A1 PCT/CN2017/088981 CN2017088981W WO2018232560A1 WO 2018232560 A1 WO2018232560 A1 WO 2018232560A1 CN 2017088981 W CN2017088981 W CN 2017088981W WO 2018232560 A1 WO2018232560 A1 WO 2018232560A1
Authority
WO
WIPO (PCT)
Prior art keywords
rat
fallback
application
message
handover procedure
Prior art date
Application number
PCT/CN2017/088981
Other languages
English (en)
Inventor
Haris Zisimopoulos
Xipeng Zhu
Gavin Bernard Horn
Original Assignee
Qualcomm Incorporated
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 Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2017/088981 priority Critical patent/WO2018232560A1/fr
Publication of WO2018232560A1 publication Critical patent/WO2018232560A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • 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/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the following relates generally to wireless communication, and more specifically to fallback handover for application support in wireless systems.
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
  • multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, and orthogonal frequency division multiple access (OFDMA) systems, (e.g., a Long Term Evolution (LTE) system, or a New Radio (NR) system) .
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • LTE Long Term Evolution
  • NR New Radio
  • a wireless multiple-access communications system may include a number of base stations or access network nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE) .
  • UE user equipment
  • a wireless communication network may support a plurality of radio access technologies (RATs) that provide resource capabilities for traffic steering, link selection, traffic flows, etc.
  • RATs radio access technologies
  • Some UEs within the wireless communication network may be configured to perform system applications using multiple RATs.
  • Such UEs may be examples of multi-subscription UEs.
  • a UE may not be capable of supporting a multi-RAT configuration (e.g., due to cost or complexity) and the UE may designate a single RAT for implementing an application (e.g. voice-over Internet Protocol (IP) ) .
  • an alternate RAT of the network may not reliably provide support for the application.
  • a node of the IP multimedia subsystem (IMS) in conjunction with a radio access network (RAN) node, may perform domain reselection (e.g., handover) of the UE from a first RAT to a second RAT in order to reliably provide support for use of the application by the UE.
  • domain reselection e.g., handover
  • the reselection procedure initiated via the IMS may induce undue latency constraints at the UE and restrict application connectivity.
  • a method of wireless communication may include transmitting, by a UE, a UE capability message indicating that the UE supports an application using a first RAT, receiving a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT, determining that the application is unsupported by a second RAT, and performing a fallback handover procedure from the second RAT to the first RAT based at least in part on an application trigger and the RAT fallback support message.
  • the apparatus may include means for transmitting, by a UE, a UE capability message indicating that the UE supports an application using a first RAT, means for receiving a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT, means for determining that the application is unsupported by a second RAT, and means for performing a fallback handover procedure from the second RAT to the first RAT based at least in part on an application trigger and the RAT fallback support message.
  • the apparatus may include a processor, memory in electronic communication with the processor, and instructions stored in the memory.
  • the instructions may be operable to cause the processor to transmit, by a UE, a UE capability message indicating that the UE supports an application using a first RAT, receive a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT, determine that the application is unsupported by a second RAT, and perform a fallback handover procedure from the second RAT to the first RAT based at least in part on an application trigger and the RAT fallback support message.
  • a non-transitory computer readable medium for wireless communication may include instructions operable to cause a processor to transmit, by a UE, a UE capability message indicating that the UE supports an application using a first RAT, receive a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT, determine that the application is unsupported by a second RAT, and perform a fallback handover procedure from the second RAT to the first RAT based at least in part on an application trigger and the RAT fallback support message.
  • performing the fallback handover procedure comprises: transmitting, to the network device, a request to perform the fallback handover procedure in a non-access stratum (NAS) message.
  • NAS non-access stratum
  • the application trigger comprises: receiving a session initiation protocol (SIP) message for at least a voice over Internet Protocol (IP) session, wherein the request to perform the fallback handover procedure may be transmitted in response to the SIP message.
  • SIP session initiation protocol
  • IP voice over Internet Protocol
  • the SIP message comprises a SIP invite for one or both of voice communication or video communication.
  • the application trigger comprises: initiating a SIP message for at least a voice over IP session, wherein the request to perform the fallback handover procedure may be transmitted prior to initiating the SIP message.
  • transmitting the UE capability message comprises: reporting, to the network device, a registration update request message that indicates a UE usage type.
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for performing an application establishment procedure after performing the fallback handover procedure.
  • the application comprises voice over IP.
  • the first RAT comprises LTE or LTE-A and the second RAT comprises NR.
  • the RAT fallback support message indicates that fallback to the first RAT may be unsupported.
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for disabling a UE capability to operate according to the second RAT based at least in part on the RAT fallback support message.
  • a method of wireless communication may include receiving, from a UE, a UE capability message indicating that the UE supports an application using a first RAT, the application being unsupported by a second RAT, transmitting a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT, receiving, from the UE, a request to perform a fallback handover procedure from the second RAT to the first RAT based at least in part on the RAT fallback support message, and performing the fallback handover procedure with the UE based at least in part on the request.
  • the apparatus may include means for receiving, from a UE, a UE capability message indicating that the UE supports an application using a first RAT, the application being unsupported by a second RAT, means for transmitting a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT, means for receiving, from the UE, a request to perform a fallback handover procedure from the second RAT to the first RAT based at least in part on the RAT fallback support message, and means for performing the fallback handover procedure with the UE based at least in part on the request.
  • the apparatus may include a processor, memory in electronic communication with the processor, and instructions stored in the memory.
  • the instructions may be operable to cause the processor to receive, from a UE, a UE capability message indicating that the UE supports an application using a first RAT, the application being unsupported by a second RAT, transmit a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT, receive, from the UE, a request to perform a fallback handover procedure from the second RAT to the first RAT based at least in part on the RAT fallback support message, and perform the fallback handover procedure with the UE based at least in part on the request.
  • a non-transitory computer readable medium for wireless communication may include instructions operable to cause a processor to receive, from a UE, a UE capability message indicating that the UE supports an application using a first RAT, the application being unsupported by a second RAT, transmit a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT, receive, from the UE, a request to perform a fallback handover procedure from the second RAT to the first RAT based at least in part on the RAT fallback support message, and perform the fallback handover procedure with the UE based at least in part on the request.
  • setting the priority indicator comprises: selecting a RAT/frequency selection priority (RFSP) from a set of RFSP indices based at least in part on a local operator policy, UE capabilities, or a combination thereof.
  • RFSP RAT/frequency selection priority
  • the priority indicator comprises a RFSP indicating a UE RAT preference.
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for transmitting, to the UE, a response to the request to perform the fallback handover procedure via an N2 interface.
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for receiving, from the UE, a registration update request message that indicates a UE usage type.
  • the application comprises voice over IP.
  • the request to perform the fallback handover procedure may be received via a NAS message.
  • the fallback handover procedure may be performed based at least in part on an application trigger at the UE.
  • the first RAT comprises LTE or LTE-A and the second RAT comprises NR.
  • Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for applying a paging strategy for the application based at least in part on a paging policy differentiation configuration.
  • a method of wireless communication may include receiving a priority indicator for a UE indicating a UE preference to support an application using a first RAT, the application being unsupported by a second RAT, determining a set of idle mode priorities for the UE based at least in part on the priority indicator, and triggering a fallback handover procedure from the second RAT to the first RAT for the UE based at least in part on the set of idle mode parameters.
  • the apparatus may include means for receiving a priority indicator for a UE indicating a UE preference to support an application using a first RAT, the application being unsupported by a second RAT, means for determining a set of idle mode priorities for the UE based at least in part on the priority indicator, and means for triggering a fallback handover procedure from the second RAT to the first RAT for the UE based at least in part on the set of idle mode parameters.
  • the apparatus may include a processor, memory in electronic communication with the processor, and instructions stored in the memory.
  • the instructions may be operable to cause the processor to receive a priority indicator for a UE indicating a UE preference to support an application using a first RAT, the application being unsupported by a second RAT, determine a set of idle mode priorities for the UE based at least in part on the priority indicator, and trigger a fallback handover procedure from the second RAT to the first RAT for the UE based at least in part on the set of idle mode parameters.
  • a non-transitory computer readable medium for wireless communication may include instructions operable to cause a processor to receive a priority indicator for a UE indicating a UE preference to support an application using a first RAT, the application being unsupported by a second RAT, determine a set of idle mode priorities for the UE based at least in part on the priority indicator, and trigger a fallback handover procedure from the second RAT to the first RAT for the UE based at least in part on the set of idle mode parameters.
  • the fallback handover procedure may be triggered based at least in part on a quality of service (QoS) flow identifier (ID) .
  • QoS quality of service
  • ID flow identifier
  • the priority indicator comprises a RFSP indicating a UE RAT preference.
  • the application comprises voice over IP.
  • the fallback handover procedure may be triggered based at least in part on an application trigger at the UE.
  • the first RAT comprises LTE or LTE-A and the second RAT comprises NR.
  • FIG. 1 illustrates an example of a system for wireless communication that supports fallback handover for application support in wireless systems in accordance with one or more aspects of the present disclosure.
  • FIG. 2 illustrates an example of a wireless communications system that supports fallback handover for application support in wireless systems in accordance with one or more aspects of the present disclosure.
  • FIG. 3 illustrates an example of a process flow that supports fallback handover for application support in wireless systems in accordance with one or more aspects of the present disclosure.
  • FIG. 4 illustrates an example of a process flow that supports fallback handover for application support in wireless systems in accordance with one or more aspects of the present disclosure.
  • FIGs. 5 through 7 show block diagrams of a device that supports fallback handover for application support in wireless systems in accordance with one or more aspects of the present disclosure.
  • FIG. 8 illustrates a block diagram of a system including a UE that supports fallback handover for application support in wireless systems in accordance with one or more aspects of the present disclosure.
  • FIGs. 9 through 11 show block diagrams of a device that supports fallback handover for application support in wireless systems in accordance with one or more aspects of the present disclosure.
  • FIG. 12 illustrates a block diagram of a system including a wireless device that supports fallback handover for application support in wireless systems in accordance with one or more aspects of the present disclosure.
  • FIGs. 13 through 15 show block diagrams of a device that supports fallback handover for application support in wireless systems in accordance with one or more aspects of the present disclosure.
  • FIG. 16 illustrates a block diagram of a system including a base station that supports fallback handover for application support in wireless systems in accordance with one or more aspects of the present disclosure.
  • FIGs. 17 through 19 illustrate methods for fallback handover for application support in wireless systems in accordance with one or more aspects of the present disclosure.
  • a UE may be restricted to operate according to a single radio access technology (RAT) configuration such that the UE operates using only one RAT at a time.
  • the UE may camp on a cell of a RAT that does not reliably support one or more applications, which may result in latency or performance issues when the application is being utilized.
  • a UE may support a UE initiated fallback handover procedure that may be used to switch from an unsupported RAT to a RAT that supports a given application.
  • the method may include a request to perform a fallback handover procedure using the IP multimedia subsystem (IMS) within the core network (e.g., via one or more nodes of the radio access network (RAN) ) .
  • IMS IP multimedia subsystem
  • the UE when performing a network registration procedure, may indicate to an access and mobility management function (AMF) node of the IMS, a configuration of the UE.
  • the configuration may indicate the applications supported by the UE as well as various UE capabilities such as the capability to initiate a domain selection or domain switching procedure (e.g., fallback handover) .
  • the AMF may determine network support for fallback handover, and may provide one or more indications in response, which may include values for radio resource management (RRM) implementation via the RAN.
  • RRM radio resource management
  • the RAN or a node of the RAN may derive cell selection priorities for the UE based at least in part on the received indication information from the AMF.
  • the RAN may trigger a handover procedure for the UE (e.g., from an unsupported RAT to a RAT that supports the application) .
  • the RAN may determine an idle mode camping RAT and if the UE is configured in an active mode, the RAN may await additional signaling from the AMF (e.g., via NAS messaging) and subsequently redirect the UE to an alternate RAT that supports the application.
  • aspects of the disclosure are initially described in the context of a wireless communications system. Aspects are then described with respect to process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to fallback handover for application support in wireless systems.
  • FIG. 1 illustrates an example of a wireless communications system 100 in accordance with various aspects of the present disclosure.
  • the wireless communications system 100 includes base stations 105, UEs 115, and a core network 130.
  • the wireless communications system 100 may be a LTE, LTE-A network, or a NR network.
  • wireless communications system 100 may support enhanced broadband communications, ultra-reliable (i.e., mission critical) communications, low latency communications, and communications with low-cost and low-complexity devices.
  • ultra-reliable i.e., mission critical
  • Wireless communications system 100 may support UE initiated handover procedure at a UE 115 (e.g., from one RAT to another RAT supported by the wireless communication system 100) .
  • the UE 115 may communicate with one or more nodes of the core network 130 (e.g., via a RAN node such as base station 105) .
  • the UE 115 may be configured in an idle or connected mode, and may support application operation using to a single RAT of the wireless communications system 100.
  • the UE may perform a handover procedure from a RAT that does not support an application to a RAT that supports the application.
  • the handover may performed based on a determination at a node of the core network (e.g., at the AMF) and may be implemented through the use of a RAN node, such as base station 105.
  • One or more UEs 115 may support a UE initiated handover, which may serve as an indication for the AMF to trigger a handover configuration (e.g., during a registration procedure) .
  • the method may also be used redirect the camping orientation of the UE 115 from an unsupported RAT to a supported RAT.
  • the method may serve to promote RAT handover procedure (e.g., following NAS messaging between the UE 115, the RAN, and the AMF) .
  • Base stations 105 may wirelessly communicate with UEs 115 via one or more base station antennas. Each base station 105 may provide communication coverage for a respective geographic coverage area 110.
  • Communication links 125 shown in wireless communications system 100 may include uplink transmissions from a UE 115 to a base station 105, or downlink transmissions, from a base station 105 to a UE 115.
  • Control information and data may be multiplexed on an uplink channel or downlink according to various techniques. Control information and data may be multiplexed on a downlink channel, for example, using time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • TDM time division multiplexing
  • FDM frequency division multiplexing
  • hybrid TDM-FDM techniques hybrid TDM-FDM techniques.
  • the control information transmitted during a transmission time interval (TTI) of a downlink channel may be distributed between different control regions in a cascaded manner (e.g., between a common control
  • UEs 115 may be dispersed throughout the wireless communications system 100, and each UE 115 may be stationary or mobile.
  • a UE 115 may also be referred to as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
  • a UE 115 may also be a cellular phone, a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a personal electronic device, a handheld device, a personal computer, a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, a machine type communication (MTC) device, an appliance, an automobile, or the like.
  • PDA personal digital assistant
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC machine type communication
  • a UE 115 may also be able to communicate directly with other UEs (e.g., using a peer-to-peer (P2P) or device-to-device (D2D) protocol) .
  • P2P peer-to-peer
  • D2D device-to-device
  • One or more of a group of UEs 115 utilizing D2D communications may be within the coverage area 110 of a cell. Other UEs 115 in such a group may be outside the coverage area 110 of a cell, or otherwise unable to receive transmissions from a base station 105.
  • groups of UEs 115 communicating via D2D communications may utilize a one-to-many (1: M) system in which each UE 115 transmits to every other UE 115 in the group.
  • a base station 105 facilitates the scheduling of resources for D2D communications.
  • D2D communications are carried out independent of a base station 105.
  • Some UEs 115 may be low cost or low complexity devices, and may provide for automated communication between machines, i.e., Machine-to-Machine (M2M) communication.
  • M2M or MTC may refer to data communication technologies that allow devices to communicate with one another or a base station without human intervention.
  • M2M or MTC may refer to communications from devices that integrate sensors or meters to measure or capture information and relay that information to a central server or application program that can make use of the information or present the information to humans interacting with the program or application.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • an MTC device may operate using half-duplex (one-way) communications at a reduced peak rate. MTC devices may also be configured to enter a power saving “deep sleep” mode when not engaging in active communications. In some cases, MTC or IoT devices may be designed to support mission critical functions and wireless communications system may be configured to provide ultra-reliable communications for these functions.
  • Base stations 105 may communicate with the core network 130 and with one another.
  • base stations 105 e.g., eNBs, gNBs
  • backhaul links 132 e.g., S1, etc.
  • Base stations 105 e.g., eNBs, gNBs
  • backhaul links 134 e.g., X2, etc.
  • Base stations 105 may perform radio configuration and scheduling for communication with UEs 115, or may operate under the control of a base station controller (not shown) .
  • base stations 105 e.g., eNBs, gNBs
  • Base stations 105 e.g., eNBs, gNBs
  • a base station 105 may be connected by an S1 interface to the core network 130.
  • the core network may be an evolved packet core (EPC) , which may include at least one mobility management entity (MME) , at least one serving gateway (S-GW) , and at least one Packet Data Network (PDN) gateway (P-GW) .
  • the MME may be the control node that processes the signaling between the UE 115 and the EPC. All user IP packets may be transferred through the S-GW, which itself may be connected to the P-GW.
  • the P-GW may provide IP address allocation as well as other functions.
  • the P-GW may be connected to the network operators IP services.
  • the operators IP services may include the Internet, the Intranet, an IMS, and a Packet-Switched (PS) Streaming Service.
  • PS Packet-Switched
  • the core network 130 may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions.
  • the network devices such as base station 105 may include subcomponents such as an access network entity, which may be an example of an access node controller (ANC) .
  • Each access network entity may communicate with a number of UEs 115 through a number of other access network transmission entities, each of which may be an example of a smart radio head, or a transmission/reception point (TRP) .
  • TRP transmission/reception point
  • various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or consolidated into a single network device (e.g., a base station 105) .
  • Wireless communications system 100 may operate in an ultra-high frequency (UHF) frequency region using frequency bands from 700 MHz to 2600 MHz (2.6 GHz) , although some networks (e.g., a wireless local area network (WLAN) ) may use frequencies as high as 4 GHz. This region may also be known as the decimeter band, since the wavelengths range from approximately one decimeter to one meter in length.
  • UHF waves may propagate mainly by line of sight, and may be blocked by buildings and environmental features. However, the waves may penetrate walls sufficiently to provide service to UEs 115 located indoors.
  • Wireless communications system 100 may also utilize extremely high frequency (EHF) portions of the spectrum (e.g., from 30 GHz to 300 GHz) . This region may also be known as the millimeter band, since the wavelengths range from approximately one millimeter to one centimeter in length.
  • EHF antennas may be even smaller and more closely spaced than UHF antennas. In some cases, this may facilitate use of antenna arrays within a UE 115 (e.g., for directional beamforming) .
  • EHF transmissions may be subject to even greater atmospheric attenuation and shorter range than UHF transmissions.
  • wireless communications system 100 may support millimeter wave (mmW) communications between UEs 115 and base stations 105 (e.g., eNBs, gNBs) .
  • Devices operating in mmW or EHF bands may have multiple antennas to allow beamforming. That is, a base station 105 may use multiple antennas or antenna arrays to conduct beamforming operations for directional communications with a UE 115.
  • Beamforming (which may also be referred to as spatial filtering or directional transmission) is a signal processing technique that may be used at a transmitter (e.g., a base station 105) to shape and/or steer an overall antenna beam in the direction of a target receiver (e.g., a UE 115) . This may be achieved by combining elements in an antenna array in such a way that transmitted signals at particular angles experience constructive interference while others experience destructive interference.
  • MIMO wireless systems use a transmission scheme between a transmitter (e.g., a base station 105) and a receiver (e.g., a UE 115) , where both transmitter and receiver are equipped with multiple antennas.
  • Some portions of wireless communications system 100 may use beamforming.
  • base station 105 may have an antenna array with a number of rows and columns of antenna ports that the base station 105 may use for beamforming in its communication with UE 115. Signals may be transmitted multiple times in different directions (e.g., each transmission may be beamformed differently) .
  • a mmW receiver e.g., a UE 115
  • the antennas of a base station 105 or UE 115 may be located within one or more antenna arrays, which may support beamforming or MIMO operation.
  • One or more base station antennas or antenna arrays may be collocated at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a base station 105 may be located in diverse geographic locations.
  • a base station 105 may multiple use antennas or antenna arrays to conduct beamforming operations for directional communications with a UE 115.
  • wireless communications system 100 may be a packet-based network that operate according to a layered protocol stack.
  • PDCP Packet Data Convergence Protocol
  • a Radio Link Control (RLC) layer may in some cases perform packet segmentation and reassembly to communicate over logical channels.
  • RLC Radio Link Control
  • a Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer may also use Hybrid ARQ (HARQ) to provide retransmission at the MAC layer to improve link efficiency.
  • HARQ Hybrid ARQ
  • the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network device 105-c, network device 105-b, or core network 130 supporting radio bearers for user plane data.
  • RRC Radio Resource Control
  • PHY Physical
  • SFN system frame number
  • Each frame may include ten 1ms subframes numbered from 0 to 9.
  • a subframe may be further divided into two . 5ms slots, each of which contains 6 or 7 modulation symbol periods (depending on the length of the cyclic prefix prepended to each symbol) . Excluding the cyclic prefix, each symbol contains 2048 sample periods.
  • the subframe may be the smallest scheduling unit, also known as a TTI.
  • a TTI may be shorter than a subframe or may be dynamically selected (e.g., in short TTI bursts or in selected component carriers using short TTIs) .
  • a resource element may consist of one symbol period and one subcarrier (e.g., a 15 KHz frequency range) .
  • a resource block may contain 12 consecutive subcarriers in the frequency domain and, for a normal cyclic prefix in each OFDM symbol, 7 consecutive OFDM symbols in the time domain (1 slot) , or 84 resource elements.
  • the number of bits carried by each resource element may depend on the modulation scheme (the configuration of symbols that may be selected during each symbol period) . Thus, the more resource blocks that a UE receives and the higher the modulation scheme, the higher the data rate may be.
  • Wireless communications system 100 may support operation on multiple cells or carriers, a feature which may be referred to as carrier aggregation (CA) or multi-carrier operation.
  • a carrier may also be referred to as a component carrier (CC) , a layer, a channel, etc.
  • CC component carrier
  • the terms “carrier, ” “component carrier, ” “cell, ” and “channel” may be used interchangeably herein.
  • a UE 115 may be configured with multiple downlink CCs and one or more uplink CCs for carrier aggregation.
  • Carrier aggregation may be used with both FDD and TDD component carriers.
  • wireless communications system 100 may utilize enhanced component carriers (eCCs) .
  • eCC may be characterized by one or more features including: wider bandwidth, shorter symbol duration, shorter TTIs, and modified control channel configuration.
  • an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have a suboptimal or non-ideal backhaul link) .
  • An eCC may also be configured for use in unlicensed spectrum or shared spectrum (where more than one operator is allowed to use the spectrum) .
  • An eCC characterized by wide bandwidth may include one or more segments that may be utilized by UEs 115 that are not capable of monitoring the whole bandwidth or prefer to use a limited bandwidth (e.g., to conserve power) .
  • an eCC may utilize a different symbol duration than other CCs, which may include use of a reduced symbol duration as compared with symbol durations of the other CCs.
  • a shorter symbol duration is associated with increased subcarrier spacing.
  • a device such as a UE 115 or base station 105, utilizing eCCs may transmit wideband signals (e.g., 20, 40, 60, 80 MHz, etc. ) at reduced symbol durations (e.g., 16.67 microseconds) .
  • a TTI in eCC may consist of one or multiple symbols. In some cases, the TTI duration (that is, the number of symbols in a TTI) may be variable.
  • a shared radio frequency spectrum band may be utilized in an NR shared spectrum system.
  • an NR shared spectrum may utilize any combination of licensed, shared, and unlicensed spectrums, among others.
  • the flexibility of eCC symbol duration and subcarrier spacing may allow for the use of eCC across multiple spectrums.
  • NR shared spectrum may increase spectrum utilization and spectral efficiency, specifically through dynamic vertical (e.g., across frequency) and horizontal (e.g., across time) sharing of resources.
  • wireless system 100 may utilize both licensed and unlicensed radio frequency spectrum bands.
  • wireless system 100 may employ LTE License Assisted Access (LTE-LAA) or LTE Unlicensed (LTE U) radio access technology or NR technology in an unlicensed band such as the 5Ghz Industrial, Scientific, and Medical (ISM) band.
  • LTE-LAA LTE License Assisted Access
  • LTE U LTE Unlicensed
  • NR New Radio
  • unlicensed band such as the 5Ghz Industrial, Scientific, and Medical (ISM) band.
  • wireless devices such as base stations 105 (e.g., eNBs, gNBs) and UEs 115 may employ listen-before-talk (LBT) procedures to ensure the channel is clear before transmitting data.
  • LBT listen-before-talk
  • operations in unlicensed bands may be based on a CA configuration in conjunction with CCs operating in a licensed band.
  • Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, or both.
  • UEs 115 may include a UE handover manager 101, which may indicate support for a fallback handover procedure by transmitting a UE capability message (e.g., to a base station 105) .
  • the UE handover manager 101 may also be used to receive a RAT fallback support message in response to the UE capability message and based on the RATs supporting a application, the UE handover manager 101 may be used to perform the fallback handover procedure from a first RAT that does not support the application to a second RAT that supports the application.
  • One or more of base stations 105 may include a RAN manager 102, which may receive a priority indicator for a UE 115 that indicates UE preference for operating using a given RAT for an application.
  • the application may be supported by one or more RATs of the wireless communications system 100 and may be unsupported by other RATs of the wireless communications system 100.
  • the RAN manager 102 may determine idle mode parameters for the UE (e.g., based on the priority indicator) and may then trigger a fallback handover procedure based on the set of idle mode parameters.
  • the AMF which may be a node of the core network 130 or IMS, may include an AMF handover manager 103 capable of receiving a UE capability message and transmitting a RAT fallback support message in response based on whether the wireless communications system 100 supports a given RAT.
  • the AMF handover manager 103 may also be used to perform a RAT fallback handover procedure based on a request from a UE 115 to perform the RAT fallback handover procedure.
  • FIG. 2 illustrates an example of a wireless communications system 200 that supports fallback handover for application support in wireless systems in accordance with various aspects of the present disclosure.
  • wireless communications system 200 may implement aspects of wireless communication system 100.
  • Wireless communications system 200 may support UE initiated handover procedure from one RAT to another RAT and in some examples, wireless communications system 200 may support multiple RATs.
  • one RAT may be an NR network and the other RAT may be an LTE network.
  • Wireless communications system 200 may include one or more UEs 115 within a coverage area 205 of a cell corresponding to a base station 105-a.
  • Base station 105-a may communicate with the core network 130-a (e.g., through backhaul links 132-a) and may include a RAN handover manager 102-athat may be used to perform handover.
  • UEs 115-a and 115-b of wireless communications system 200 may be configured to operate according to only a single RAT at one time or may operate according to a multi-RAT configuration that supports operation of multiple RATs at a time.
  • an application may be supported by one RAT, but may not be reliably supported by another RAT.
  • UE 115-a may include a UE handover manager 101-a, which may be used to perform handover.
  • the core network 130-a may include one or more nodes such as an AMF, which may include an AMF handover manager 103-a.
  • the AMF handover manager 103-a may be used to coordinate a fallback handover procedure (e.g., with a UE 115-a) .
  • UE 115-a may initiate registration to the IMS and send a registration request to the RAN in order to gain authorization to receive services, enable mobility tracking, enable reachability, enact authentication protocol, and the like.
  • the registration request may include an initial registration (i.e., UE 115-a is moving from a resource management (RM) deregistered state to an RM registered state) , a mobility registration update (i.e., UE 115-a is in a RM registered state and initiates registration procedure due to mobility) , a periodic registration (i.e., UE 115-a is in a RM registered state and initiates registration procedure due to a timing period expiration) , or the like.
  • RM resource management
  • UE 115-a may transmit one or more indication elements, including a setting indication of the UE (i.e., whether UE 115-a behaves in a voice-centric or data-centric manner) and a capability indication of the UE.
  • the capability indication may include at least application support information, notifying one or more nodes of the core network 130-a (e.g., AMF) of RAT capabilities supported by UE 115-a.
  • the RAN corresponding to UE 115-a and the proximal base station 105-a may select a configured AMF of the core network 130-a, and direct the registration request of UE 115-a, including the indication information, to the selected AMF within an N2 message.
  • the AMF may evaluate the N2 message, including the registration request and contained context information of UE 115-a, and determine network support with regard to the capability indication of the UE.
  • the AMF may enact one or more protocols with UE 115-a and the RAN to perform registration procedure. In some cases, the AMF may also initiate NAS security functions and invoke one or more information and identity acknowledgements with the UE and additional nodes of the network.
  • the protocols may be unidirectional or bidirectional in nature, and invoked by the AMF, UE 115-a, or an alternate node of the IMS.
  • the AMF may receive a subscribed RAT/frequency selection priority (RFSP) index from a policy control function (PCF) of the IMS.
  • the AMF may select a RFSP index value in accordance with a selected procedure of the AMF and the received context information of UE 115-a.
  • the AMF may select an RFSP index value identical to the subscribed RFSP index value of the PCF.
  • the AMF may choose an RFSP index value based on the subscribed RFSP index value, the policies of the UE, and the UE related context information provided in the request message, including the UEs voice usage setting.
  • the AMF may submit at least the selected RFSP index to the RAN, via an N2 message, and provide network support indication to the UE.
  • the RAN may map the received RFSP index to a locally defined configuration and apply resource management strategies specific to UE 115-a.
  • the strategies may be based on procedure corresponding the mode configuration of the UE (e.g., idle mode, connected mode) .
  • the strategy may be initiated via a determined trigger of the RAN and the AMF.
  • UE 115-a may be configured in an idle mode, with capability of voice support over a single first RAT.
  • the UE may initiate registration to the IMS, and deliver a registration request message to the RAN.
  • the registration request may include at least a subscriber identifier, security parameters, mode preferences, as well as a usage type identifier.
  • UE 115-a may provide the usage type identifier to notify the IMS that the UE is voice-centric, and is capable of supporting voice application over the first RAT (e.g., LTE) but not a second RAT (e.g., NR) .
  • first RAT e.g., LTE
  • second RAT e.g., NR
  • the RAN may select a configured AMF of the network and forward the registration request to the AMF via an N2 message.
  • the AMF may evaluate the contained parameters of the N2 message, evaluate the registration request provided by the UE, and perform registration procedure.
  • the registration procedure may include one or more authentication protocols, identity requests, security functions, information acknowledgements, and the like, and may be initiated by UE 115-a, the selected AMF, or an alternate node of the IMS.
  • the AMF may determine usage type of UE 115-a, as provided in the registration request, an determine voice deployment at UE 115-a is limited to the first RAT (e.g., LTE) .
  • the AMF may then transmit an indicator RFSP index to the corresponding RAN via an N2 interface.
  • the RFSP index may include command instructions for the RAN to direct UE 115-a to the first RAT for idle mode camping.
  • the RAN may receive at least the RFSP index from the AMF and evaluate the index. Based on the evaluation, the RAN may derive the idle mode camping priority of the UE and the registration area of the UE 115-a to determine a target cell of the registration area that supports the first RAT. The RAN may then direct UE 115-a to camp on the determined target cell for the duration of idle mode operation. As a result, UE 115-a may capably support voice application natively over the first RAT, without necessitating a RAT reselection procedure over the network.
  • UE 115-a may be camped on a cell supporting the second RAT (e.g., NR) , and may be triggered to move to a connected mode configuration (e.g., RRC connected, connection management (CM) connected) .
  • UE 115-a may be voice-centric, support voice application singularly over the first RAT (e.g., LTE) , and may initiate a handover procedure to the first RAT for application execution.
  • UE 115-a may initiate a registration procedure, and transmit a registration request to a corresponding RAN.
  • the registration request may include at least a subscriber identifier, security parameters, mode preferences, as well as identification of usage type preferences and voice support capability at UE 115-a. Additionally, the registration request may include indication information regarding support for handover procedure initialization at UE 115-a.
  • the RAN may receive the registration request, select a configured AMF of the network, and forward the registration request to the selected AMF via an N2 message over NAS.
  • the AMF may evaluate the contained parameters of the N2 message, evaluate the registration request provided by UE 115-a, and perform registration procedure.
  • the registration procedure may include one or more authentication protocols, identity requests, security functions, information acknowledgements, and the like, initiated by UE 115-a, the AMF, or an alternate node of the IMS.
  • the AMF may determine the usage type of the UE as provided in the registration request, determine voice deployment at UE-115-a is limited to the first RAT, and determine network support for handover procedure initiated by UE 115-a.
  • the AMF may determine that UE initiated method is supported by the network, and provide indication to UE 115-a of network support for the handover procedure. In addition to the determination, the AMF may avoid RAT reselection procedure.
  • the AMF may determine an RFSP index value corresponding to at least the UE related context information and a subscribed RFSP index received from a PCF of the network, and transmit at least the determined RFSP index value to the RAN via an N2 interface.
  • the network may be configured to incorporate UE initiated handover procedure by UE 115-a, based at least on the determination of voice data and NAS signaling by the UE 115-a.
  • UE 115-a may receive a session initiation protocol (SIP) invitation for application (e.g., voice-over IP) reception from an alternate UE 115-b.
  • UE 115-a may transmit an application request to the selected AMF, via NAS, and initiate UE handover to the first RAT.
  • the UE may wish to initiate an SIP for application (e.g., voice-over IP) communication with an alternate UE 115-b.
  • UE 115-a may transmit an application request to the selected AMF, via NAS, and initiate UE handover to the first RAT.
  • the AMF may trigger a UE initiated handover procedure (fallback) and prepare N2 request messaging for the corresponding RAN.
  • the AMF may evaluate the subscription of UE 115-a and identify at least the multimedia priority service (MPS) priority of the UE. Based at least in part on the identified MPS priority, the AMF may determine if priority handling is necessary for message delivery to the RAN. In the case of priority handling (e.g., an emergency call) the AMF may set the priority indication of the message to high. The AMF may then transmit the N2 request message to the RAN, including a notification (triggering) instruction to enact voice support handover to the first RAT, at UE 115-a.
  • MPS multimedia priority service
  • the RAN may receive the N2 message from the AMF and determine, based at least in part on a quality of service (QOS) flow indication (QFI) value of the application (i.e., which may be configured by the network) , to perform handover to the first RAT.
  • QOS quality of service
  • QFI quality of service flow indication
  • the RAN may solicit a measurement report from UE 115-a to determine a target cell of the registration area for handover.
  • the RAN may then execute the handover procedure, and redirect UE 115-a to the first RAT.
  • UE 115-a may then complete establishment of the IMS application to UE 115-b via the first RAT.
  • FIG. 3 illustrates an example of a process flow 300 that supports fallback handover for application support in wireless systems in accordance with various aspects of the present disclosure.
  • process flow 300 may implement aspects of wireless communication systems 100 and 200 as described with reference to FIGs. 1 and 2.
  • process flow 300 may represent aspects of techniques performed by one or more UEs 115, base stations 105 (or other nodes of the RAN) , and one or more nodes of the core network 103 (e.g., AMF) , as described with reference to FIGs. 1 and 2.
  • UEs 115-c and 115-d may be in a connected mode.
  • UE 115-c may be camped on a cell supporting a second RAT, and may be capable of a UE initiated handover procedure from a second RAT to a first RAT.
  • the provided example is described with regard to handover deployment at UE 115-c.
  • Implementation of the described methods may incorporate UE handover manager 101-b at the UE 115-c, RAN handover manager 102-b at the corresponding base station 105-b, AMF handover manager 103-b at the core network 130-b, and UE handover manager 101-c at the UE 115-d.
  • the described operations may also be applicable for deployment at UE 115-c.
  • UE 115-c may receive a SIP invitation for application (e.g., voice-over IP) reception from UE 115-d.
  • the SIP invitation may include QoS requirement of the application.
  • UE 115-c may initiate a fallback handover procedure via core network 130-b (e.g., during a registration procedure performed using AMF handover manager 103-b) .
  • UE 115-c may transmit an application request to a selected AMF of core network 130-b, via NAS, and initiate UE handover to the first RAT.
  • the AMF handover manager 103-b may trigger UE initiated handover procedure (fallback) and prepare N2 request messaging for the corresponding RAN.
  • the AMF handover manager 103-b may evaluate the subscription of UE 115-c and identify at least the multimedia priority service (MPS) priority of the UE 115-c.
  • the AMF handover manager 103-b may then transmit the N2 request message to the RAN associated with base station 105-b and UE 115-c, including notification (triggering) instruction to enable voice support handover to the first RAT, at UE 115-c.
  • MPS multimedia priority service
  • the RAN associated with base station 105-b and UE 115-c may receive the N2 message from the AMF handover manager 103-b of core network 130-b and determine (e.g., based at least in part on a QFI value of the application which may be configured by the network) to perform handover to the first RAT.
  • the RAN handover manager 102-b may determine a target cell of the registration area of UE 115-c for handover implementation.
  • the RAN handover manager 102-b may then perform handover procedure, redirecting UE 115-c to the first RAT.
  • UE 115-c may complete establishment of the IMS application and communicate with UE 115-d via the first RAT.
  • the base station 105-b of the system, as well as one or more nodes of the core network 130-b, may sustain the communication link between UE 115-c and 115-d.
  • the communication may correspond to one or more sub-bands of the frequency spectrum supported by the first RAT, spanning one or more symbols of a TTI.
  • FIG. 4 illustrates an example of a process flow 400 that supports fallback handover for application support in wireless systems in accordance with various aspects of the present disclosure.
  • process flow 400 may implement aspects of wireless communications system 100 or 200 as described with reference to FIGs. 1 and 2.
  • process flow 400 may represent aspects of techniques performed by one or more UEs 115, base stations 105, and one or more nodes of the core network 103, as described with reference to FIGs. 1 and 2.
  • UEs 115-e and 115-f may be in a connected mode.
  • UE 115-e may be camped on a cell supporting a second RAT, and may be capable of a UE initiated handover procedure from a second RAT to a first RAT.
  • the provided example is described with regard to handover deployment at UE 115-e.
  • Implementation of the described methods may incorporate UE handover manager 101-d at the UE 115-e, RAN handover manager 102-c at the corresponding base station 105-c, AMF handover manager 103-c at the core network 130-c, and UE handover manager 101-e at the UE 115-f.
  • the described operations may also be applicable for deployment at UE 115-e.
  • UE 115-e may initiate an application (e.g., voice-over IP) supported on the first RAT.
  • Application initiation may include UE 115-e sending a SIP invitation to UE 115-f.
  • the SIP invitation may include QoS requirement of the application.
  • UE 115-c may initiate a fallback handover procedure via core network 130-c (e.g., during a registration procedure performed using AMF handover manager 103-c) .
  • UE 115-e may transmit an application request to a selected AMF of core network 130-c, via NAS, and initiate UE handover to the first RAT.
  • the AMF handover manager 103-c may trigger UE initiated handover procedure (fallback) and prepare N2 request messaging for the corresponding RAN.
  • the AMF handover manager 103-c may evaluate the subscription of UE 115-e and identify at least the MPS priority of the UE 115-e.
  • the AMF handover manager 103-c may then transmit the N2 request message to the RAN associated with base station 105-c and UE 115-e, including notification (triggering) instruction to enable voice support handover to the first RAT, at UE 115-e.
  • the RAN associated with base station 105-c and UE 115-e may receive the N2 message from the AMF handover manager 103-c of core network 130-c and determine (e.g., based at least in part on a QFI value of the application which may be configured by the network) to perform handover to the first RAT.
  • the RAN handover manager 102-c may determine a target cell of the registration area of UE 115-e for handover implementation.
  • the RAN handover manager 102-c may then perform handover procedure, redirecting UE 115-e to the first RAT.
  • UE 115-e may complete establishment of the IMS application and communicate with UE 115-f via the first RAT.
  • the base station 105-c of the system, as well as one or more nodes of the core network 130-c, may sustain the communication link between UE 115-e and 115-f.
  • the communication may correspond to one or more sub-bands of the frequency spectrum supported by the first RAT, spanning one or more symbols of a TTI.
  • FIG. 5 shows a block diagram 500 of a wireless device 505 that supports fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • Wireless device 505 may be an example of aspects of a UE 115 as described herein.
  • Wireless device 505 may include receiver 510, UE handover manager 515, and transmitter 520.
  • Wireless device 505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • Receiver 510 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to fallback handover for application support in wireless systems, etc. ) . Information may be passed on to other components of the device.
  • the receiver 510 may be an example of aspects of the transceiver 835 described with reference to FIG. 8.
  • the receiver 510 may utilize a single antenna or a set of antennas.
  • UE handover manager 515 may be an example of aspects of the UE handover manager 815 described with reference to FIG. 8.
  • UE handover manager 515 and/or at least some of its various sub-components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the UE handover manager 515 and/or at least some of its various sub-components may be executed by a general-purpose processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , an field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • the UE handover manager 515 and/or at least some of its various sub-components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices.
  • UE handover manager 515 and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • UE handover manager 515 and/or at least some of its various sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • UE handover manager 515 may transmit, by a UE, a UE capability message indicating that the UE supports an application using a first RAT, receive a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT, determine that the application is unsupported by a second RAT, and perform a fallback handover procedure from the second RAT to the first RAT based on an application trigger and the RAT fallback support message.
  • Transmitter 520 may transmit signals generated by other components of the device.
  • the transmitter 520 may be collocated with a receiver 510 in a transceiver module.
  • the transmitter 520 may be an example of aspects of the transceiver 835 described with reference to FIG. 8.
  • the transmitter 520 may utilize a single antenna or a set of antennas.
  • FIG. 6 shows a block diagram 600 of a wireless device 605 that supports fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • Wireless device 605 may be an example of aspects of a wireless device 505 or a UE 115 as described with reference to FIG. 5.
  • Wireless device 605 may include receiver 610, UE handover manager 615, and transmitter 620.
  • Wireless device 605 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • Receiver 610 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to fallback handover for application support in wireless systems, etc. ) . Information may be passed on to other components of the device.
  • the receiver 610 may be an example of aspects of the transceiver 835 described with reference to FIG. 8.
  • the receiver 610 may utilize a single antenna or a set of antennas.
  • UE handover manager 615 may be an example of aspects of the UE handover manager 815 described with reference to FIG. 8.
  • UE handover manager 615 may also include transmission component 625, reception component 630, RAT component 635, and fallback component 640.
  • Transmission component 625 may transmit, by a UE, a UE capability message indicating that the UE supports an application using a first RAT and transmit, to the network device, a request to perform the fallback handover procedure.
  • transmitting the UE capability message includes: reporting, to the network device, a registration update request message that indicates a UE usage type.
  • Reception component 630 may receive a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT and receive, from the network device, a response to the request to perform the fallback handover procedure via an N2 interface.
  • the first RAT includes LTE or LTE-A and the second RAT includes NR.
  • the RAT component 635 may determine that the application is unsupported by a second RAT and disable a UE capability to operate according to the second RAT based on the RAT fallback support message. In some cases, the RAT fallback support message indicates that fallback to the first RAT is unsupported.
  • Fallback component 640 may perform a fallback handover procedure from the second RAT to the first RAT based on an application trigger and the RAT fallback support message.
  • performing the fallback handover procedure includes: transmitting, to the network device, a request to perform the fallback handover procedure in a NAS message.
  • the application trigger includes: receiving a SIP message for at least a voice over IP session, where the request to perform the fallback handover procedure is transmitted in response to the SIP message.
  • the SIP message includes a SIP invite for one or both of voice communication or video communication.
  • the application trigger includes: initiating a SIP message for at least a voice over IP session, where the request to perform the fallback handover procedure is transmitted prior to initiating the SIP message.
  • Transmitter 620 may transmit signals generated by other components of the device.
  • the transmitter 620 may be collocated with a receiver 610 in a transceiver module.
  • the transmitter 620 may be an example of aspects of the transceiver 835 described with reference to FIG. 8.
  • the transmitter 620 may utilize a single antenna or a set of antennas.
  • FIG. 7 shows a block diagram 700 of a UE handover manager 715 that supports fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • the UE handover manager 715 may be an example of aspects of a UE handover manager 515, a UE handover manager 615, or a UE handover manager 815 described with reference to FIGs. 5, 6, and 8.
  • the UE handover manager 715 may include transmission component 720, reception component 725, RAT component 730, fallback component 735, and application component 740. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • Transmission component 720 may transmit, by a UE, a UE capability message indicating that the UE supports an application using a first RAT and transmit, to the network device, a request to perform the fallback handover procedure.
  • transmitting the UE capability message includes: reporting, to the network device, a registration update request message that indicates a UE usage type.
  • Reception component 725 may receive a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT and receive, from the network device, a response to the request to perform the fallback handover procedure via an N2 interface.
  • the first RAT includes LTE or LTE-A and the second RAT includes NR.
  • RAT component 730 may determine that the application is unsupported by a second RAT and disable a UE capability to operate according to the second RAT based on the RAT fallback support message. In some cases, the RAT fallback support message indicates that fallback to the first RAT is unsupported.
  • Fallback component 735 may perform a fallback handover procedure from the second RAT to the first RAT based on an application trigger and the RAT fallback support message.
  • performing the fallback handover procedure includes: transmitting, to the network device, a request to perform the fallback handover procedure in a NAS message.
  • the application trigger includes: receiving a SIP message for at least a voice over IP session, where the request to perform the fallback handover procedure is transmitted in response to the SIP message.
  • the SIP message includes a SIP invite for one or both of voice communication or video communication.
  • the application trigger includes: initiating a SIP message for at least a voice over IP session, where the request to perform the fallback handover procedure is transmitted prior to initiating the SIP message.
  • Application component 740 may perform an application establishment procedure after performing the fallback handover procedure.
  • the application includes voice over IP.
  • FIG. 8 shows a diagram of a system 800 including a device 805 that supports fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • Device 805 may be an example of or include the components of wireless device 505, wireless device 605, or a UE 115 as described above, e.g., with reference to FIGs. 5 and 6.
  • Device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including UE handover manager 815, processor 820, memory 825, software 830, transceiver 835, antenna 840, and I/O controller 845. These components may be in electronic communication via one or more buses (e.g., bus 810) .
  • Device 805 may communicate wirelessly with one or more base stations 105.
  • Processor 820 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a central processing unit (CPU) , a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • processor 820 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into processor 820.
  • Processor 820 may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting fallback handover for application support in wireless systems) .
  • Memory 825 may include random access memory (RAM) and read only memory (ROM) .
  • the memory 825 may store computer-readable, computer-executable software 830 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 825 may contain, among other things, a basic input/output system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic input/output system
  • Software 830 may include code to implement aspects of the present disclosure, including code to support fallback handover for application support in wireless systems.
  • Software 830 may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software 830 may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • Transceiver 835 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 835 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 835 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 840. However, in some cases the device may have more than one antenna 840, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • I/O controller 845 may manage input and output signals for device 805. I/O controller 845 may also manage peripherals not integrated into device 805. In some cases, I/O controller 845 may represent a physical connection or port to an external peripheral. In some cases, I/O controller 845 may utilize an operating system such as or another known operating system. In other cases, I/O controller 845 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, I/O controller 845 may be implemented as part of a processor. In some cases, a user may interact with device 805 via I/O controller 845 or via hardware components controlled by I/O controller 845.
  • FIG. 9 shows a block diagram 900 of a wireless device 905 that supports fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • Wireless device 905 may be an example of aspects of a node of a core network (e.g., an AMF) as described herein.
  • Wireless device 905 may include receiver 910, AMF handover manager 915, and transmitter 920.
  • Wireless device 905 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • Receiver 910 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to fallback handover for application support in wireless systems, etc. ) . Information may be passed on to other components of the device.
  • the receiver 910 may be an example of aspects of the transceiver 1235 described with reference to FIG. 12.
  • the receiver 910 may utilize a single antenna or a set of antennas.
  • AMF handover manager 915 may be an example of aspects of the wireless device handover manager 1215 described with reference to FIG. 12.
  • AMF handover manager 915 and/or at least some of its various sub-components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the wireless device handover manager 915 and/or at least some of its various sub-components may be executed by a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • the AMF handover manager 915 and/or at least some of its various sub-components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices.
  • AMF handover manager 915 and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • AMF handover manager 915 and/or at least some of its various sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • AMF handover manager 915 may receive, from a UE, a UE capability message indicating that the UE supports an application using a first RAT, the application being unsupported by a second RAT, transmit a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT, receive, from the UE, a request to perform a fallback handover procedure from the second RAT to the first RAT based on the RAT fallback support message, and perform the fallback handover procedure with the UE based on the request.
  • Transmitter 920 may transmit signals generated by other components of the device.
  • the transmitter 920 may be collocated with a receiver 910 in a transceiver module.
  • the transmitter 920 may be an example of aspects of the transceiver 1235 described with reference to FIG. 12.
  • the transmitter 920 may utilize a single antenna or a set of antennas.
  • FIG. 10 shows a block diagram 1000 of a wireless device 1005 that supports fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • Wireless device 1005 may be an example of aspects of a wireless device 905 or a node of a core network (e.g., an AMF) as described with reference to FIG. 9.
  • Wireless device 1005 may include receiver 1010, AMF handover manager 1015, and transmitter 1020.
  • Wireless device 1005 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • Receiver 1010 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to fallback handover for application support in wireless systems, etc. ) . Information may be passed on to other components of the device.
  • the receiver 1010 may be an example of aspects of the transceiver 1235 described with reference to FIG. 12.
  • the receiver 1010 may utilize a single antenna or a set of antennas.
  • AMF handover manager 1015 may be an example of aspects of the wireless device handover manager 1215 described with reference to FIG. 12. AMF handover manager 1015 may also include AMF reception component 1025, AMF transmission component 1030, AMF request component 1035, and AMF fallback component 1040.
  • AMF reception component 1025 may receive, from a UE, a UE capability message indicating that the UE supports an application using a first RAT, the application being unsupported by a second RAT and receive, from the UE, a registration update request message that indicates a UE usage type.
  • the application includes voice over IP.
  • the first RAT includes LTE or LTE-A and the second RAT includes NR.
  • AMF transmission component 1030 may transmit a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT and transmit, to the UE, a response to the request to perform the fallback handover procedure via an N2 interface.
  • AMF request component 1035 may receive, from the UE, a request to perform a fallback handover procedure from the second RAT to the first RAT based on the RAT fallback support message. In some cases, the request to perform the fallback handover procedure is received via a NAS message.
  • AMF fallback component 1040 may perform the fallback handover procedure with the UE based on the request. In some cases, the fallback handover procedure is performed based on an application trigger at the UE.
  • Transmitter 1020 may transmit signals generated by other components of the device.
  • the transmitter 1020 may be collocated with a receiver 1010 in a transceiver module.
  • the transmitter 1020 may be an example of aspects of the transceiver 1235 described with reference to FIG. 12.
  • the transmitter 1020 may utilize a single antenna or a set of antennas.
  • FIG. 11 shows a block diagram 1100 of a AMF handover manager 1115 that supports fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • the AMF handover manager 1115 may be an example of aspects of a wireless device handover manager 1215 described with reference to FIGs. 9, 10, and 12.
  • the AMF handover manager 1115 may include AMF reception component 1120, AMF transmission component 1125, AMF request component 1130, AMF fallback component 1135, AMF priority component 1140, and AMF paging component 1145. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • AMF reception component 1120 may receive, from a UE, a UE capability message indicating that the UE supports an application using a first RAT, the application being unsupported by a second RAT and receive, from the UE, a registration update request message that indicates a UE usage type.
  • the application includes voice over IP.
  • the first RAT includes LTE or LTE-A and the second RAT includes NR.
  • AMF transmission component 1125 may transmit a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT and transmit, to the UE, a response to the request to perform the fallback handover procedure via an N2 interface.
  • AMF request component 1130 may receive, from the UE, a request to perform a fallback handover procedure from the second RAT to the first RAT based on the RAT fallback support message. In some cases, the request to perform the fallback handover procedure is received via a NAS message.
  • AMF fallback component 1135 may perform the fallback handover procedure with the UE based on the request. In some cases, the fallback handover procedure is performed based on an application trigger at the UE.
  • AMF priority component 1140 may set a priority indicator based on the RAT fallback support message and transmit the priority indicator to a RAN node.
  • setting the priority indicator includes: selecting a RAT/frequency selection priority (RFSP) from a set of RFSP indices based on a local operator policy, UE capabilities, or a combination thereof.
  • the priority indicator includes a RAT/frequency selection priority (RFSP) indicating a UE RAT preference.
  • AMF paging component 1145 may apply a paging strategy for the application based on a paging policy differentiation configuration.
  • FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • Device 1205 may be an example of or include the components of node of a core network (e.g., an AMF) as described above, e.g., with reference to FIG. 1.
  • Device 1205 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including wireless device handover manager 1215, processor 1220, memory 1225, software 1230, transceiver 1235, antenna 1240, and I/O controller 1245. These components may be in electronic communication via one or more buses (e.g., bus 1210) .
  • buses e.g., bus 1210
  • Processor 1220 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • processor 1220 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into processor 1220.
  • Processor 1220 may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting fallback handover for application support in wireless systems) .
  • Memory 1225 may include RAM and ROM.
  • the memory 1225 may store computer-readable, computer-executable software 1230 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 1225 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • Software 1230 may include code to implement aspects of the present disclosure, including code to support fallback handover for application support in wireless systems.
  • Software 1230 may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software 1230 may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • Transceiver 1235 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1235 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1235 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 1240. However, in some cases the device may have more than one antenna 1240, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • I/O controller 1245 may manage input and output signals for device 1205. I/O controller 1245 may also manage peripherals not integrated into device 1205. In some cases, I/O controller 1245 may represent a physical connection or port to an external peripheral. In some cases, I/O controller 1245 may utilize an operating system such as or another known operating system. In other cases, I/O controller 1245 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, I/O controller 1245 may be implemented as part of a processor. In some cases, a user may interact with device 1205 via I/O controller 1245 or via hardware components controlled by I/O controller 1245.
  • FIG. 13 shows a block diagram 1300 of a wireless device 1305 that supports fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • Wireless device 1305 may be an example of aspects of a base station 105 as described herein.
  • Wireless device 1305 may include receiver 1310, base station handover manager 1315, and transmitter 1320.
  • Wireless device 1305 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • Receiver 1310 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to fallback handover for application support in wireless systems, etc. ) . Information may be passed on to other components of the device.
  • the receiver 1310 may be an example of aspects of the transceiver 1635 described with reference to FIG. 16.
  • the receiver 1310 may utilize a single antenna or a set of antennas.
  • Base station handover manager 1315 may be an example of aspects of the base station handover manager 1615 described with reference to FIG. 16.
  • Base station handover manager 1315 and/or at least some of its various sub-components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the base station handover manager 1315 and/or at least some of its various sub-components may be executed by a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure. The base station handover manager 1315 and/or at least some of its various sub-components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices.
  • base station handover manager 1315 and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure. In other examples, base station handover manager 1315 and/or at least some of its various sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • Base station handover manager 1315 may receive a priority indicator for a UE indicating a UE preference to support an application using a first RAT, the application being unsupported by a second RAT, determine a set of idle mode priorities for the UE based on the priority indicator, and trigger a fallback handover procedure from the second RAT to the first RAT for the UE based on the set of idle mode parameters.
  • Transmitter 1320 may transmit signals generated by other components of the device.
  • the transmitter 1320 may be collocated with a receiver 1310 in a transceiver module.
  • the transmitter 1320 may be an example of aspects of the transceiver 1635 described with reference to FIG. 16.
  • the transmitter 1320 may utilize a single antenna or a set of antennas.
  • FIG. 14 shows a block diagram 1400 of a wireless device 1405 that supports fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • Wireless device 1405 may be an example of aspects of a wireless device 1305 or a base station 105 as described with reference to FIG. 13.
  • Wireless device 1405 may include receiver 1410, base station handover manager 1415, and transmitter 1420.
  • Wireless device 1405 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • Receiver 1410 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to fallback handover for application support in wireless systems, etc. ) . Information may be passed on to other components of the device.
  • the receiver 1410 may be an example of aspects of the transceiver 1635 described with reference to FIG. 16.
  • the receiver 1410 may utilize a single antenna or a set of antennas.
  • Base station handover manager 1415 may be an example of aspects of the base station handover manager 1615 described with reference to FIG. 16.
  • Base station handover manager 1415 may also include RAN reception component 1425, RAN idle mode component 1430, and RAN fallback component 1435.
  • RAN reception component 1425 may receive a priority indicator for a UE indicating a UE preference to support an application using a first RAT, the application being unsupported by a second RAT.
  • the application includes voice over IP.
  • the first RAT includes LTE or LTE-A and the second RAT includes NR.
  • RAN idle mode component 1430 may determine a set of idle mode priorities for the UE based on the priority indicator.
  • the priority indicator includes a RFSP indicating a UE RAT preference.
  • RAN fallback component 1435 may trigger a fallback handover procedure from the second RAT to the first RAT for the UE based on the set of idle mode parameters.
  • the fallback handover procedure is triggered based on a QFI.
  • the fallback handover procedure is triggered based on an application trigger at the UE.
  • Transmitter 1420 may transmit signals generated by other components of the device.
  • the transmitter 1420 may be collocated with a receiver 1410 in a transceiver module.
  • the transmitter 1420 may be an example of aspects of the transceiver 1635 described with reference to FIG. 16.
  • the transmitter 1420 may utilize a single antenna or a set of antennas.
  • FIG. 15 shows a block diagram 1500 of a base station handover manager 1515 that supports fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • the base station handover manager 1515 may be an example of aspects of a base station handover manager 1615 described with reference to FIGs. 13, 14, and 16.
  • the base station handover manager 1515 may include RAN reception component 1520, RAN idle mode component 1525, and RAN fallback component 1530. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • RAN reception component 1520 may receive a priority indicator for a UE indicating a UE preference to support an application using a first RAT, the application being unsupported by a second RAT.
  • the application includes voice over IP.
  • the first RAT includes LTE or LTE-A and the second RAT includes NR.
  • RAN idle mode component 1525 may determine a set of idle mode priorities for the UE based on the priority indicator.
  • the priority indicator includes a RFSP indicating a UE RAT preference.
  • RAN fallback component 1530 may trigger a fallback handover procedure from the second RAT to the first RAT for the UE based on the set of idle mode parameters.
  • the fallback handover procedure is triggered based on a QFI.
  • the fallback handover procedure is triggered based on an application trigger at the UE.
  • FIG. 16 shows a diagram of a system 1600 including a device 1605 that supports fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • Device 1605 may be an example of or include the components of base station 105 as described above, e.g., with reference to FIG. 1.
  • Device 1605 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including base station handover manager 1615, processor 1620, memory 1625, software 1630, transceiver 1635, antenna 1640, network communications manager 1645, and inter-station communications manager 1650. These components may be in electronic communication via one or more buses (e.g., bus 1610) .
  • Device 1605 may communicate wirelessly with one or more UEs 115.
  • Processor 1620 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • processor 1620 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into processor 1620.
  • Processor 1620 may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting fallback handover for application support in wireless systems) .
  • Memory 1625 may include RAM and ROM.
  • the memory 1625 may store computer-readable, computer-executable software 1630 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 1625 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • Software 1630 may include code to implement aspects of the present disclosure, including code to support fallback handover for application support in wireless systems.
  • Software 1630 may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software 1630 may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • Transceiver 1635 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1635 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1635 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 1640. However, in some cases the device may have more than one antenna 1640, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • Network communications manager 1645 may manage communications with the core network (e.g., via one or more wired backhaul links) .
  • the network communications manager 1645 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • Inter-station communications manager 1650 may manage communications with other base station 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other base stations 105. For example, the inter-station communications manager 1650 may coordinate scheduling for transmissions to UEs 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, inter-station communications manager 1650 may provide an X2 interface within an LTE/LTE-A wireless communication network technology to provide communication between base stations 105.
  • FIG. 17 shows a flowchart illustrating a method 1700 for fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • the operations of method 1700 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1700 may be performed by a UE handover manager as described with reference to FIGs. 5 through 8.
  • a UE 115 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the UE 115 may perform aspects of the functions described below using special-purpose hardware.
  • the UE 115 may transmit, by a UE, a UE capability message indicating that the UE supports an application using a first RAT.
  • the operations of block 1705 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1705 may be performed by a transmission component as described with reference to FIGs. 5 through 8.
  • the UE 115 may receive a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT.
  • the operations of block 1710 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1710 may be performed by a reception component as described with reference to FIGs. 5 through 8.
  • the UE 115 may determine that the application is unsupported by a second RAT.
  • the operations of block 1715 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1715 may be performed by a RAT component as described with reference to FIGs. 5 through 8.
  • the UE 115 may perform a fallback handover procedure from the second RAT to the first RAT based at least in part on an application trigger and the RAT fallback support message.
  • the operations of block 1720 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1720 may be performed by a fallback component as described with reference to FIGs. 5 through 8.
  • FIG. 18 shows a flowchart illustrating a method 1800 for fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • the operations of method 1800 may be implemented by a node of a core network (e.g., an AMF) or its components as described herein.
  • the operations of method 1800 may be performed by a wireless device handover manager as described with reference to FIGs. 9 through 12.
  • a node of a core network e.g., an AMF
  • the node of a core network e.g., an AMF
  • the node of a core network may receive, from a UE, a UE capability message indicating that the UE supports an application using a first RAT, the application being unsupported by a second RAT.
  • the operations of block 1805 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1805 may be performed by a AMF reception component as described with reference to FIGs. 9 through 12.
  • the node of a core network may transmit a RAT fallback support message in response to the UE capability message, the RAT fallback support message indicating that a network device supports the application using the first RAT.
  • the operations of block 1810 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1810 may be performed by a AMF transmission component as described with reference to FIGs. 9 through 12.
  • the node of a core network may receive, from the UE, a request to perform a fallback handover procedure from the second RAT to the first RAT based at least in part on the RAT fallback support message.
  • the operations of block 1815 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1815 may be performed by a AMF request component as described with reference to FIGs. 9 through 12.
  • the node of a core network may perform the fallback handover procedure with the UE based at least in part on the request.
  • the operations of block 1820 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1820 may be performed by a AMF fallback component as described with reference to FIGs. 9 through 12.
  • FIG. 19 shows a flowchart illustrating a method 1900 for fallback handover for application support in wireless systems in accordance with aspects of the present disclosure.
  • the operations of method 1900 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 1900 may be performed by a base station handover manager as described with reference to FIGs. 13 through 16.
  • a base station 105 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the base station 105 may perform aspects of the functions described below using special-purpose hardware.
  • the base station 105 may receive a priority indicator for a UE indicating a UE preference to support an application using a first RAT, the application being unsupported by a second RAT.
  • the operations of block 1905 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1905 may be performed by a RAN reception component as described with reference to FIGs. 13 through 16.
  • the base station 105 may determine a set of idle mode priorities for the UE based at least in part on the priority indicator.
  • the operations of block 1910 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1910 may be performed by a RAN idle mode component as described with reference to FIGs. 13 through 16.
  • the base station 105 may trigger a fallback handover procedure from the second RAT to the first RAT for the UE based at least in part on the set of idle mode parameters.
  • the operations of block 1915 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1915 may be performed by a RAN fallback component as described with reference to FIGs. 13 through 16.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • CDMA2000 covers IS-2000, IS-95, and IS-856 standards.
  • IS-2000 Releases may be commonly referred to as CDMA2000 1X, 1X, etc.
  • IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD) , etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • WCDMA Wideband CDMA
  • a TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • GSM Global System for Mobile Communications
  • An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB) , Evolved UTRA (E-UTRA) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, etc.
  • UMB Ultra Mobile Broadband
  • E-UTRA Evolved UTRA
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS) .
  • LTE and LTE-A are releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, NR, and GSM are described in documents from the organization named “3rd Generation Partnership Project” (3GPP) .
  • 3GPP 3rd Generation
  • CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • 3GPP2 3rd Generation Partnership Project 2
  • the techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies. While aspects of an LTE or an NR system may be described for purposes of example, and LTE or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE or NR applications.
  • the term eNB may be generally used to describe the base stations.
  • the wireless communications system or systems described herein may include a heterogeneous LTE/LTE-A or NR network in which different types of eNBs provide coverage for various geographical regions.
  • each eNB, next generation NodeB (gNB) , or base station may provide communication coverage for a macro cell, a small cell, or other types of cell.
  • the term “cell” may be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., sector, etc. ) of a carrier or base station, depending on context.
  • Base stations may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, eNB, gNB, Home NodeB, a Home eNodeB, or some other suitable terminology.
  • the geographic coverage area for a base station may be divided into sectors making up only a portion of the coverage area.
  • the wireless communications system or systems described herein may include base stations of different types (e.g., macro or small cell base stations) .
  • the UEs described herein may be able to communicate with various types of base stations and network equipment including macro eNBs, small cell eNBs, gNBs, relay base stations, and the like. There may be overlapping geographic coverage areas for different technologies.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider.
  • a small cell is a lower-powered base station, as compared with a macro cell, that may operate in the same or different (e.g., licensed, unlicensed, etc. ) frequency bands as macro cells.
  • Small cells may include pico cells, femto cells, and micro cells according to various examples.
  • a pico cell for example, may cover a small geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider.
  • a femto cell may also cover a small geographic area (e.g., a home) and may provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG) , UEs for users in the home, and the like) .
  • An eNB for a macro cell may be referred to as a macro eNB.
  • An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB.
  • An eNB may support one or multiple (e.g., two, three, four, and the like) cells (e.g., component carriers) .
  • a gNB for a macro cell may be referred to as a macro gNB.
  • a gNB for a small cell may be referred to as a small cell gNB, a pico gNB, a femto gNB, or a home gNB.
  • a gNB may support one or multiple (e.g., two, three, four, and the like) cells (e.g., component carriers) .
  • a UE may be able to communicate with various types of base stations and network equipment including macro eNBs, small cell eNBs, relay base stations, and the like.
  • the wireless communications system or systems described herein may support synchronous or asynchronous operation.
  • the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time.
  • the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • Each communication link described herein including, for example, wireless communications system 100 and 200 of FIGs. 1 and 2—may include one or more carriers, where each carrier may be a signal made up of multiple sub-carriers (e.g., waveform signals of different frequencies) .
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) .
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that can be accessed by a general purpose or special purpose computer.
  • non-transitory computer-readable media may comprise RAM, ROM, electrically erasable programmable read only memory (EEPROM) , compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • RAM random access memory
  • ROM read only memory
  • EEPROM electrically erasable programmable read only memory
  • CD compact disk
  • magnetic disk storage or other magnetic storage devices or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Landscapes

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

Abstract

L'invention concerne des procédés, des systèmes et des dispositifs de communication sans fil. Les procédés, les systèmes et les dispositifs peuvent comprendre la transmission, par un équipement utilisateur (UE), un message de capacité d'UE indiquant que l'UE prend en charge une application à l'aide d'une première technologie d'accès radio (RAT), la réception d'un message de support de repli de RAT en réponse au message de capacité d'UE. Le message de support de repli de RAT indique qu'un dispositif de réseau prend en charge l'application en utilisant la première RAT déterminant que l'application n'est pas prise en charge par une seconde RAT. Les procédés, les systèmes et les dispositifs peuvent en outre effectuer une procédure de transfert intercellulaire de repli de la seconde RAT à la première RAT sur la base, au moins en partie, d'un déclencheur d'application et du message de support de repli RAT.
PCT/CN2017/088981 2017-06-19 2017-06-19 Transfert intercellulaire de repli pour support d'application dans des systèmes sans fil WO2018232560A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/088981 WO2018232560A1 (fr) 2017-06-19 2017-06-19 Transfert intercellulaire de repli pour support d'application dans des systèmes sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/088981 WO2018232560A1 (fr) 2017-06-19 2017-06-19 Transfert intercellulaire de repli pour support d'application dans des systèmes sans fil

Publications (1)

Publication Number Publication Date
WO2018232560A1 true WO2018232560A1 (fr) 2018-12-27

Family

ID=64736195

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/088981 WO2018232560A1 (fr) 2017-06-19 2017-06-19 Transfert intercellulaire de repli pour support d'application dans des systèmes sans fil

Country Status (1)

Country Link
WO (1) WO2018232560A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021087413A1 (fr) * 2019-10-31 2021-05-06 Qualcomm Incorporated Améliorations du transfert d'un appel vowi-fi d'une epdg à un réseau lte lorsque la fonction vonr n'est pas prise en charge
WO2021261843A1 (fr) * 2020-06-22 2021-12-30 Samsung Electronics Co., Ltd. Procédés et systèmes de gestion d'appel vocal sur une nouvelle radio par un équipement utilisateur
US11323936B2 (en) * 2018-01-11 2022-05-03 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Service-based processing method, terminal device, and network device
WO2022152119A1 (fr) * 2021-01-15 2022-07-21 维沃移动通信有限公司 Procédé et dispositif de notification de retour à un réseau et terminal
WO2022169535A1 (fr) * 2021-02-02 2022-08-11 Qualcomm Incorporated Techniques de déhiérarchisation de technologie d'accès radio
US11979781B2 (en) 2021-03-11 2024-05-07 Samsung Electronics Co., Ltd. Method for selecting cell using a 5G user equipment and a 5G UE

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100075665A1 (en) * 2008-09-22 2010-03-25 Telefonaktiebolaget Lm Ericsson (Publ) Radio access technology selection
WO2015149409A1 (fr) * 2014-03-31 2015-10-08 华为终端有限公司 Procédé de communication sans fil et terminal sans fil
CN105453650A (zh) * 2012-10-08 2016-03-30 高通股份有限公司 用于当分组数据网络不可接入时避免无线接入技术之间的转换的方法和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100075665A1 (en) * 2008-09-22 2010-03-25 Telefonaktiebolaget Lm Ericsson (Publ) Radio access technology selection
CN105453650A (zh) * 2012-10-08 2016-03-30 高通股份有限公司 用于当分组数据网络不可接入时避免无线接入技术之间的转换的方法和系统
WO2015149409A1 (fr) * 2014-03-31 2015-10-08 华为终端有限公司 Procédé de communication sans fil et terminal sans fil

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11323936B2 (en) * 2018-01-11 2022-05-03 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Service-based processing method, terminal device, and network device
WO2021087413A1 (fr) * 2019-10-31 2021-05-06 Qualcomm Incorporated Améliorations du transfert d'un appel vowi-fi d'une epdg à un réseau lte lorsque la fonction vonr n'est pas prise en charge
CN114731546A (zh) * 2019-10-31 2022-07-08 高通股份有限公司 当不支持VoNR时从ePDG到LTE的VoWi-Fi切换的增强
CN114731546B (zh) * 2019-10-31 2024-03-15 高通股份有限公司 当不支持VoNR时从ePDG到LTE的VoWi-Fi切换的增强
WO2021261843A1 (fr) * 2020-06-22 2021-12-30 Samsung Electronics Co., Ltd. Procédés et systèmes de gestion d'appel vocal sur une nouvelle radio par un équipement utilisateur
WO2022152119A1 (fr) * 2021-01-15 2022-07-21 维沃移动通信有限公司 Procédé et dispositif de notification de retour à un réseau et terminal
WO2022169535A1 (fr) * 2021-02-02 2022-08-11 Qualcomm Incorporated Techniques de déhiérarchisation de technologie d'accès radio
US11979781B2 (en) 2021-03-11 2024-05-07 Samsung Electronics Co., Ltd. Method for selecting cell using a 5G user equipment and a 5G UE

Similar Documents

Publication Publication Date Title
US10645746B2 (en) Mechanisms for establishing user plane connectivity for non-3GPP access
US11228966B2 (en) Requesting resource allocation in a wireless backhaul network
WO2018161244A1 (fr) Négociation de décalage de radiomessagerie
EP4167642A1 (fr) Configuration et coordination d'écarts de mesure
EP3625897B1 (fr) Configuration de csi-rs pour réaccord de bande partielle
CN110249605B (zh) 对会话发起协议invite的重定向
US11452168B2 (en) Resource management, access control and mobility for grant-free uplink transmission
WO2019084758A1 (fr) Continuité d'appel vocal radio unique indirect
EP3620017B1 (fr) Commande d'admission sans autorisation à un canal partagé
WO2018232560A1 (fr) Transfert intercellulaire de repli pour support d'application dans des systèmes sans fil
US11076413B2 (en) Multiple wireless communication technology co-channel coexistence
WO2018219203A1 (fr) Conception de signalisation pour une rétroaction conjointe de données de liaison montante et d'informations d'état de canal
WO2020088382A1 (fr) Transmission de données avec temps d'expiration
EP3900467B1 (fr) Adaptation de surveillance de canal pour une opération de bande de spectre de fréquence sans licence
WO2018191916A1 (fr) Procédé d'adressage de conflits de temporisateur de canal logique et blocage de données
US10958407B2 (en) Frequency division duplexing hybrid automatic repeat request with mini-slots
US10869332B2 (en) Transmission scheme for multiple component carriers in adjacent subframes
WO2019006580A1 (fr) Fichier de règles consolidées destiné à un marché ouvert

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: 17915047

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17915047

Country of ref document: EP

Kind code of ref document: A1