Modifying a mobility procedure for low latency traffic in a wireless network
Patent Information
- Application Number
- PCT/CN2023/093189
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-10
- Publication Date
- 2024-11-14
Smart Images

Figure CN2023093189_14112024_PF_FP_ABST
Abstract
Description
MODIFYING A MOBILITY PROCEDURE FOR LOW LATENCY TRAFFIC IN A WIRELESS NETWORK
[0001] FIELD OF THE DISCLOSURE
[0002] Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for modifying a mobility procedure for low latency traffic in a wireless network.BACKGROUND
[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like) . Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE) . LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP) .
[0004] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL” ) refers to a communication link from the network node to the UE, and “uplink” (or “UL” ) refers to a communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL) , a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples) .
[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate on a municipal, national, regional, and / or global level. New Radio (NR) , which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) ) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful.SUMMARY
[0006] More and more low latency applications are being implemented on mobile platforms. Gaming, live video streaming, and / or other low latency applications are being developed for use on user equipments (UEs) , which enables these low latency applications to be consumed while associated users are traveling or otherwise mobile. However, mobility events associated with a UE may cause increased latency for a low latency application during a cell switching procedure (e.g., a handover or cell reselection procedure) , which may cause gaming lag or buffering in a live video stream, among other examples. The increased latency may occur, for example, due to an interruption in service during the cell switching procedure, which can result in increased delay for low latency traffic flows associated with the low latency application. Moreover, mobility events associated with the UE may cause increased latency for the low latency application in that the UE may prioritize criteria other than latency in a mobility procedure for determining whether to request a cell switching procedure or whether to transmit a measurement report. For example, the UE may prioritize signal strength or throughput over latency, which may result in the UE switching to (or remaining in) a cell in which the UE experiences (or may experience) sustained high latency for the low latency application, thereby resulting in increased delay for the low latency traffic flows associated with the low latency application.
[0007] In some aspects described herein, a UE may modify a mobility procedure to achieve and maintain a low latency for a traffic flow associated with a low latency application executed by the UE. The UE may modify the mobility procedure to reduce the frequency of and / or likelihood of cell switching from a serving cell to a target cell if latency in the serving cell is low and / or to quickly switch to a target cell if latency in the serving cell is high. The UE may modify the mobility procedure by adjusting the parameters that the UE considers when performing the mobility procedure. The UE may adjust the parameters by adding conditions that are required to be satisfied before the UE transmits a measurement report to trigger a handover of the UE if latency in the serving cell is low (e.g., the UE suppresses the measurement report, which may effectively block handover from the serving cell) , or by adding optional conditions that can trigger handover of the UE (e.g., thereby increasing the options for more quickly triggering handover of the UE) if latency in the serving cell is high. In this way, the UE may better control cell switching of the UE to tightly control latency for low latency applications associated with the UE.
[0008] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include determining an application type associated with a traffic flow associated with the UE. The method may include determining, in association with the application type, an application link state associated with an access link on which the UE is to communicate the traffic flow with a network node. The method may include modifying a mobility procedure for the UE in association with the application link state.
[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to determine an application type associated with a traffic flow associated with the UE. The one or more processors may be configured to determine, in association with the application type, an application link state associated with an access link on which the UE is to communicate the traffic flow with a network node. The one or more processors may be configured to modify a mobility procedure for the UE in association with the application link state.
[0010] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to determine an application type associated with a traffic flow associated with the UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to determine, in association with the application type, an application link state associated with an access link on which the UE is to communicate the traffic flow with a network node. The set of instructions, when executed by one or more processors of the UE, may cause the UE to modify a mobility procedure for the UE in association with the application link state.
[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for determining an application type associated with a traffic flow associated with the apparatus. The apparatus may include means for determining, in association with the application type, an application link state associated with an access link on which the apparatus is to communicate the traffic flow with a network node. The apparatus may include means for modifying a mobility procedure for the apparatus in association with the application link state.
[0012] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, wireless communication device, and / or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.
[0013] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.
[0014] While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices) . Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers) . It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of varying size, shape, and constitution.BRIEF DESCRIPTION OF THE DRAWINGS
[0015] So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.
[0016] Fig. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.
[0017] Fig. 2 is a diagram illustrating an example of a network node in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.
[0018] Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.
[0019] Fig. 4 is a diagram illustrating an example of a handover procedure, in accordance with the present disclosure.
[0020] Fig. 5 is a diagram of an example mobility procedure, in accordance with the present disclosure.
[0021] Figs. 6A-6C are diagrams of examples of modifying a mobility procedure for low latency traffic in a wireless network, in accordance with the present disclosure.
[0022] Fig. 7 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.
[0023] Fig. 8 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.DETAILED DESCRIPTION
[0024] More and more low latency applications are being implemented on mobile platforms. Gaming, live video streaming, and / or other low latency applications are being developed for use on user equipments (UEs) , which enables these low latency applications to be consumed while associated users are traveling or otherwise mobile. However, mobility events associated with a UE may cause increased latency for a low latency application during a cell switching procedure (e.g., a handover or cell reselection procedure) , which may cause gaming lag or buffering in a live video stream, among other examples. The increased latency may occur, for example, due to an interruption in service during the cell switching procedure, which can result in increased delay for low latency traffic flows associated with the low latency application. Moreover, mobility events associated with the UE may cause increased latency for the low latency application in that the UE may prioritize criteria other than latency in a mobility procedure for determining whether to request a cell switching procedure or whether to transmit a measurement report. For example, the UE may prioritize signal strength or throughput over latency, which may result in the UE switching to (or remaining in) a cell in which the UE experiences (or may experience) sustained high latency for the low latency application, thereby resulting in increased delay for the low latency traffic flows associated with the low latency application.
[0025] In some aspects described herein, a UE may modify a mobility procedure to achieve and maintain a low latency for a traffic flow associated with a low latency application executed by the UE. The UE may modify the mobility procedure to reduce the frequency of and / or likelihood of cell switching from a serving cell to a target cell if latency in the serving cell is low and / or to quickly switch to a target cell if latency in the serving cell is high. The UE may modify the mobility procedure by adjusting the parameters that the UE considers when performing the mobility procedure. The UE may adjust the parameters by adding conditions that are required to be satisfied before the UE transmits a measurement report to trigger a handover of the UE if latency in the serving cell is low (e.g., to UE suppresses the measurement , which may effectively block handover from the serving cell) , or by adding optional conditions that can trigger handover of the UE (e.g., thereby increasing the options for more quickly triggering handover of the UE) if latency in the serving cell is high.
[0026] Modifying the mobility procedure associated with the UE may enable the UE to better control cell switching of the UE to tightly control latency for low latency applications associated with the UE. Thus, modifying the mobility procedure associated with the UE may enable the UE to achieve a relatively low latency for traffic flows associated with the low latency applications, thereby reducing latency for the low latency applications and increasing the performance of the low latency applications. For example, modifying the mobility procedure associated with the UE may decrease gaming ping, may decrease the amount of and / or the likelihood of buffering in a live video stream, and / or may decrease lag between movement of a user associated with the UE and extended reality video displayed on the UE where the extended reality video is based on the movement of the user.
[0027] The UE may determine whether latency in a serving cell is high or low in association with determining an application link state associated with an access link on which the UE is to communicate a traffic flow associated with a low latency application in the serving cell (e.g., with a network node providing the serving cell) . The application link state may include a parameter that represents a quantitative assessment of one or more parameters that primarily impact or are indicators of latency on the access link of the serving cell, such as signal-to-noise ratio (SNR) , block error rate (BLER) , protocol data unit (PDU) miss rate, and / or packet data convergence protocol (PDCP) discard rate, among other examples. This application link state may enable the UE to determine whether latency on the access link in the serving cell is low, medium, or high (or another set of qualitative categories) , which enables the UE to quickly determine whether to suppress the measurement report (thereby effectively blocking handover from the serving cell) if latency in the serving cell is low, as indicated by the application link state, or to quickly facilitate handover from the serving cell if latency in the serving cell is high, as indicated by the application link state. Thus, the application link state enables the UE to maintain or quickly achieve low latency for the low latency applications associated with the UE.
[0028] Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.
[0029] Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, or the like (collectively referred to as “elements” ) . These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
[0030] While aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT) , aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G) .
[0031] Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE) ) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as a network node 110a, a network node 110b, a network node 110c, and a network node 110d) , a UE 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e) , and / or other entities. A network node 110 is a network node that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes. For example, a network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit) . As another example, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station) , meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs)) .
[0032] In some examples, a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU. In some examples, a network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. A network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G) , a gNB (e.g., in 5G) , an access point, a transmission reception point (TRP) , a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and / or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.
[0033] In some examples, a network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP) , the term “cell” can refer to a coverage area of a network node 110 and / or a network node subsystem serving this coverage area, depending on the context in which the term is used. A network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG) ) . A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In the example shown in Fig. 1, the network node 110a may be a macro network node for a macro cell 102a, the network node 110b may be a pico network node for a pico cell 102b, and the network node 110c may be a femto network node for a femto cell 102c. A network node may support one or multiple (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a network node 110 that is mobile (e.g., a mobile network node) .
[0034] In some aspects, the terms “base station” or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, “base station” or “network node” may refer to a CU, a DU, an RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) , or a Non-Real Time (Non-RT) RIC, or a combination thereof. In some aspects, the terms “base station” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110. In some aspects, the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the terms “base station” or “network node” may refer to any one or more of those different devices. In some aspects, the terms “base station” or “network node” may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.
[0035] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110) . A relay station may be a UE 120 that can relay transmissions for other UEs 120. In the example shown in Fig. 1, the network node 110d (e.g., a relay network node) may communicate with the network node 110a (e.g., a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, or the like.
[0036] The wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, or the like. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, macro network nodes may have a high transmit power level (e.g., 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts) .
[0037] A network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.
[0038] The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. A UE 120 may be a cellular phone (e.g., a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet) ) , an entertainment device (e.g., a music device, a video device, and / or a satellite radio) , a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device that is configured to communicate via a wireless or wired medium.
[0039] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE and / or an eMTC UE may include, for example, a robot, an unmanned aerial vehicle, a remote device, a sensor, a meter, a monitor, and / or a location tag, that may communicate with a network node, another device (e.g., a remote device) , or some other entity. Some UEs 120 may be considered Internet-of-Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered a Customer Premises Equipment. A UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.
[0040] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, an air interface, or the like. A frequency may be referred to as a carrier, a frequency channel, or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
[0041] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using a network node 110 as an intermediary to communicate with one another) . For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol) , and / or a mesh network. In such examples, a UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the network node 110.
[0042] Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) . It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
[0043] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz –24.25 GHz) . Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend features of FR1 and / or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz –71 GHz) , FR4 (52.6 GHz –114.25 GHz) , and FR5 (114.25 GHz –300 GHz) . Each of these higher frequency bands falls within the EHF band.
[0044] With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and techniques described herein are applicable to those modified frequency ranges.
[0045] In some aspects, a UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may determine an application type associated with a traffic flow associated with the UE; determine, in association with the application type, an application link state associated with an access link on which the UE is to communicate the traffic flow with a network node; and modify a mobility procedure for the UE in association with the application link state. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.
[0046] As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.
[0047] Fig. 2 is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1) . The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1) . The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, a network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.
[0048] At the network node 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120) . The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS (s) selected for the UE 120 and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI) ) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS) ) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) ) . A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) , shown as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) , shown as antennas 234a through 234t.
[0049] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive the downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) , shown as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) a received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller / processor 280. The term “controller / processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other examples. In some examples, one or more components of the UE 120 may be included in a housing 284.
[0050] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.
[0051] One or more antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, and / or an antenna array may include one or more antenna elements (within a single housing or multiple housings) , a set of coplanar antenna elements, a set of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmission and / or reception components, such as one or more components of Fig. 2.
[0052] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM) , and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna (s) 252, the modem (s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and / or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller / processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 4-8) .
[0053] At the network node 110, the uplink signals from UE 120 and / or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232) , detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of the antenna (s) 234, the modem (s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and / or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller / processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 4-8) .
[0054] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or any other component (s) of Fig. 2 may perform one or more techniques associated with modifying a mobility procedure for low latency traffic in a wireless network, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or any other component (s) of Fig. 2 may perform or direct operations of, for example, process 700 of Fig. 7, and / or other processes as described herein. The memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively. In some examples, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and / or interpreting) by one or more processors of the network node 110 and / or the UE 120, may cause the one or more processors, the UE 120, and / or the network node 110 to perform or direct operations of, for example, process 700 of Fig. 7, and / or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.
[0055] In some aspects, the UE 120 includes means for determining an application type associated with a traffic flow associated with the UE 120; means for determining, in association with the application type, an application link state associated with an access link on which the UE 120 is to communicate the traffic flow with the network node 110; and / or means for modifying a mobility procedure for the UE 120 in association with the application link state. The means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.
[0056] While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.
[0057] As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.
[0058] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB) , an evolved NB (eNB) , an NR base station, a 5G NB, an access point (AP) , a TRP, or a cell, among other examples) , or one or more units (or one or more components) performing base station functionality, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. “Network entity” or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof) .
[0059] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit) . A disaggregated base station (e.g., a disaggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs) . In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other network nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) , among other examples.
[0060] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.
[0061] Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both) . A CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through F1 interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be simultaneously served by multiple RUs 340.
[0062] Each of the units, including the CUs 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305, may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
[0063] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, PDCP functions, or service data adaptation protocol (SDAP) functions, among other examples. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (for example, Central Unit –User Plane (CU-UP) functionality) , control plane functionality (for example, Central Unit –Control Plane (CU-CP) functionality) , or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.
[0064] Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT) , an inverse FFT (iFFT) , digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.
[0065] Each RU 340 may implement lower-layer functionality. In some deployments, an RU 340, controlled by a DU 330, may correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 3GPP) , such as a lower layer functional split. In such an architecture, each RU 340 can be operated to handle over the air (OTA) communication with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
[0066] The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective O1 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.
[0067] The Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.
[0068] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 325, the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies) .
[0069] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.
[0070] Fig. 4 is a diagram illustrating an example 400 of a handover procedure, in accordance with the present disclosure. As shown in Fig. 4, a handover procedure may involve a UE 405, a serving network node 410, a target network node 415, a user plane function (UPF) device 420, and / or an access and mobility management function (AMF) device 425, among other examples. In some aspects, the UE 405, the serving network node 410, the target network node 415, the UPF device 420, and / or the AMF device 425 may perform another type of cell switching procedure, such as a cell reselection procedure, a redirection procedure, or a radio link failure (RLF) procedure, among other examples.
[0071] The UE 405 may correspond to the UE 120 described elsewhere herein. The serving network node 410 and / or the target network node 415 may correspond to a network node 110 described elsewhere herein. The UPF device 420 and / or the AMF device 425 may correspond to network controllers 130 described elsewhere herein. The UE 405 and the serving network node 410 may be connected (e.g., may have an RRC connection) via a serving cell 430 or a source cell (e.g., a cell 102) , and the UE 405 may undergo a handover to the target network node 415 via a target cell 435 (e.g., another cell 102) . The UPF device 420 and / or the AMF device 425 may be located within a core network. The serving network node 410 and the target network node 415 may be in communication with the core network for mobility support and user plane functions.
[0072] The handover procedure may include a handover preparation phase, a handover execution phase, and a handover completion phase. During the handover preparation phase, the UE 405 may report measurements that cause the serving network node 410 and / or the target network node 415 to prepare for handover and trigger execution of the handover. During the handover execution phase, the UE 405 may execute the handover by performing a random access procedure with the target network node 415 and establishing an RRC connection with the target network node 415. During the handover completion phase, the serving network node 410 may forward stored communications associated with the UE 405 to the target network node 415, and the UE 405 may be released from a connection with the serving network node 410.
[0073] At 440, the UE 405 may determine an event that triggers a mobility measurement report at 445. Examples of events are described in connection with Fig. 5 below. The event determined at 440 may trigger the UE 405 to provide a measurement report at 445 for the purpose of providing the serving network node 410 with information to determine whether to proceed with handover of the UE 405 from the serving cell 430 to the target cell 435. The UE 405 may perform one or more measurements, and may transmit a measurement report to the serving network node 410 based at least in part on or otherwise in association with performing the one or more measurements (e.g., serving cell measurements and / or neighbor cell measurements) . The measurement report may indicate, for example, an RSRP parameter, an RSRQ parameter, an RSSI parameter, an SNR parameter, and / or a signal-to-interference-plus-noise ratio (SINR) parameter (e.g., for the serving cell and / or one or more neighbor cells) , among other examples. The serving network node 410 may use the measurement report to determine whether to trigger a handover to the target network node 415. For example, if one or more measurements satisfy a condition, then the serving network node 410 may trigger a handover of the UE 405 to the target network node 415.
[0074] As shown by reference number 450, the serving network node 410 and the target network node 415 may communicate with one another to prepare for a handover of the UE 405. As part of the handover preparation, the serving network node 410 may transmit a handover request to the target network node 415 to instruct the target network node 415 to prepare for the handover. The serving network node 410 may communicate RRC context information associated with the UE 405 and / or configuration information associated with the UE 405 to the target network node 415. The target network node 415 may prepare for the handover by reserving resources for the UE 405. After reserving the resources, the target network node 415 may transmit an acknowledgement (ACK) to the serving network node 410 in response to the handover request.
[0075] As shown by reference number 455, the serving network node 410 may transmit an RRC reconfiguration message to the UE 405. The RRC reconfiguration message may include a handover command instructing the UE 405 to execute a handover procedure from the serving network node 410 to the target network node 415. The handover command may include information associated with the target network node 415, such as a random access channel (RACH) preamble assignment for accessing the target network node 415. Reception of the RRC reconfiguration message, including the handover command, by the UE 405 may trigger the start of the handover execution phase.
[0076] As shown by reference number 460, during the handover execution phase of the handover, the UE 405 may execute the handover by performing a random access procedure with the target network node 415 (e.g., including synchronization with the target network node 415) while continuing to communicate with the serving network node 410. For example, while the UE 405 is performing the random access procedure with the target network node 415, the UE 405 may transmit uplink data, uplink control information, and / or an uplink reference signal (e.g., a sounding reference signal) to the serving network node 410, and / or may receive downlink data, downlink control information, and / or a downlink reference signal from the serving network node 410.
[0077] As shown by reference number 465, upon successfully establishing a connection with the target network node 415 (e.g., via a random access procedure) , the UE may transmit an RRC reconfiguration completion message to the target network node 415. Reception of the RRC reconfiguration message by the target network node 415 may trigger the start of the handover completion phase.
[0078] As shown by reference number 470, the serving network node 410 and the target network node 415 may communicate with one another to prepare for release of the connection between the serving network node 410 and the UE 405. In some aspects, the target network node 415 may determine that a connection between the serving network node 410 and the UE 405 is to be released, such as after receiving the RRC reconfiguration complete message from the UE 405. In this case, the target network node 415 may transmit a handover connection setup completion message to the serving network node 410. The handover connection setup completion message may cause the serving network node 410 to stop transmitting data to the UE 405 and / or to stop receiving data from the UE 405. Additionally, or alternatively, the handover connection setup completion message may cause the serving network node 410 to forward communications associated with the UE 405 to the target network node 415 and / or to notify the target network node 415 of a status of one or more communications with the UE 405. For example, the serving network node 410 may forward, to the target network node 415, buffered downlink communications (e.g., downlink data) for the UE 405 and / or uplink communications (e.g., uplink data) received from the UE 405. Additionally, or alternatively, the serving network node 410 may notify the target network node 415 regarding a packet data convergence protocol (PDCP) status associated with the UE 405 and / or a sequence number to be used for a downlink communication with the UE 405.
[0079] As shown by reference number 475, the target network node 415 may transmit an RRC reconfiguration message to the UE 405 to instruct the UE 405 to release the connection with the serving network node 410. Upon receiving the instruction to release the connection with the serving network node 410, the UE 405 may stop communicating with the serving network node 410. For example, the UE 405 may refrain from transmitting uplink communications to the serving network node 410 and / or may refrain from monitoring for downlink communications from the serving network node 410.
[0080] As shown by reference number 480, the UE may transmit an RRC reconfiguration completion message to the target network node 415 to indicate that the connection between the serving network node 410 and the UE 405 is being released or has been released.
[0081] As shown by reference number 485, the target network node 415, the UPF device 420, and / or the AMF device 425 may communicate to switch a user plane path of the UE 405 from the serving network node 410 to the target network node 415. Prior to switching the user plane path, downlink communications for the UE 405 may be routed through the core network to the serving network node 410. After the user plane path is switched, downlink communications for the UE 405 may be routed through the core network to the target network node 415. Upon completing the switch of the user plane path, the AMF device 425 may transmit an end marker message to the serving network node 410 to signal completion of the user plane path switch. As shown by reference number 490, the target network node 415 and the serving network node 410 may communicate to release the serving network node 410.
[0082] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.
[0083] Fig. 5 is a diagram of an example 500 of a mobility procedure, in accordance with the present disclosure. The mobility procedure may include a determination by the UE 405 (or a UE 120) of an event that triggers a measurement report for a cell switching procedure. As shown in Fig. 5, a UE 405 (or a UE 120) may determine an event at 440 of the example handover procedure described in connection with Fig. 4. Additionally and / or alternatively, the UE 405 (or a UE 120) may determine an event for transmitting a measurement report in association with another type of cell switching procedure, such as a cell reselection procedure, a redirection procedure, and / or an RLF procedure, among other examples.
[0084] As shown in Fig. 5, one or more types of events, referred to as “A / B events, ” may involve the UE 405 performing one or more measurements and determining whether results of the one or more measurements satisfy one or more thresholds. For example, an A2 event may include an event associated with the UE 405 determining that an RSRP (e.g., in association with an RSRP measurement) of a serving cell 430 associated with a serving network node 410 satisfies a threshold (e.g., an RSRP threshold) . The UE 405 may transmit a measurement report to the serving network node 410 if the A2 event condition or threshold is satisfied (consistently) for a time to trigger (TTT) duration.
[0085] As another example, an A3 event may include an event associated with the UE 405 determining that a difference, between an RSRP (e.g., in association with an RSRP measurement) of a target cell 435 associated with a target network node 415 and an RSRP (e.g., in association with an RSRP measurement) of a serving cell 430 associated with a serving network node 410, satisfies a threshold (e.g., a difference threshold) . The UE 405 may transmit a measurement report to the serving network node 410 if the A3 event condition or threshold is satisfied (consistently) for a TTT duration.
[0086] As another example, events such as an A4 event, an A5 event, a B1 event, and / or a B2 event may include events associated with the UE 405 determining that a plurality of conditions are satisfied. For example, the UE 405 may determine that an RSRP (e.g., in association with an RSRP measurement) of a serving cell 430 associated with a serving network node 410 does not satisfy a first threshold (e.g., a first RSRP threshold, indicated in Fig. 5 as Threshold 1) , and that an RSRP (e.g., in association with an RSRP measurement) of a target cell 435 associated with a target network node 415 and an RSRP (e.g., in association with an RSRP measurement) satisfies a second threshold (e.g., a second RSRP threshold, indicated in Fig. 5 as Threshold 2) . The UE 405 may transmit a measurement report to the serving network node 410 if the A4 event, the A5 event, the B1 event, and / or the B2 event conditions or thresholds are satisfied (consistently) for a TTT duration.
[0087] In some aspects, the UE 405 may rule out target cells that have very low SNR, to avoid triggering handovers to those target cells. For example, the UE 405 determine that one or more of the events described above have occurred, but may still refrain from transmitting a measurement report (that would otherwise trigger a handover of the UE 405) in association with determining that an SNR (e.g., in association with an SNR measurement) of a target cell 435 associated with a target network node 415 does not satisfy an SNR threshold. The SNR threshold may correspond to a minimum SNR (e.g., -9 decibels, or another value) for successful decoding of a system information block (e.g., SIB1) associated with the target cell 435. This enables the UE 405 to avoid being handed over to a target cell 435 having a high likelihood that handover will fail.
[0088] As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.
[0089] Figs. 6A-6C are diagrams of examples 600 of modifying a mobility procedure for low latency traffic in a wireless network, in accordance with the present disclosure. As shown in Figs. 6A-6C, the examples 600 may include operations performed by a UE 405. The UE 405 may correspond to the UE 120 described elsewhere herein. The UE 405 may communicate with a serving network node 410 and / or the target network node 415 may correspond to a network node 110 described elsewhere herein. The UE 405 and the serving network node 410 may be connected (e.g., may have an RRC connection) via a serving cell 430 or a source cell.
[0090] The UE 405 may perform the mobility procedure to determine whether to initiate or request a handover to the target network node 415 via a target cell 435. The mobility procedure may be a standard mobility procedure 605, such as the mobility procedure described above in connection with Fig. 5. Alternatively, the mobility procedure may include a low latency application mobility procedure 610, which may include a modified version of the standard mobility procedure 605. The UE 405 may modify the standard mobility procedure 605 to perform the low latency application mobility procedure 610 for a particular type of application, such as a low latency application. The UE 405 may modify the standard mobility procedure 605 to prioritize low latency for the low latency application to provide a high quality user experience for the low latency application and / or to reduce the likelihood of performance impacts for the low latency application (e.g., gaming lag, video stuttering) due to high latency.
[0091] The low latency application mobility procedure 610 may include modifications to the parameters and / or conditions that trigger the transmission of a measurement report from the UE 405 to the serving network node 410 (and thus, a handover of the UE 405 to the target network node 415) . The UE 405 may modify the combination of parameters and / or conditions that, when satisfied, trigger the transmission of the measurement report. Accordingly, the UE 405 may modify the combination of parameters and / or conditions to suppress the transmission of the measurement report (e.g., to reduce the likelihood that the measurement report will be transmitted) to initiate blocking of handover of the UE 405 if latency in the serving cell 430 is good or satisfactory, and / or to facilitate quick handover of the UE 405 if latency in the serving cell 430 is bad or unsatisfactory. This enables the UE 405 to achieve and / or maintain a low latency for the low latency application, particularly in scenarios in which the UE 405 is at or near the edge of multiple cells and is prone to frequent handovers between the multiple cells (which might increase latency for the low latency application) .
[0092] As an example, a user associated with the UE 405 may be waiting for a train or a bus for a daily commute in an urban area in which multiple cells provide overlapping coverage for the UE 405. While the user is waiting, the user may be playing a video game on the UE 405, and the video game may rely on a traffic flow (e.g., uplink and / or downlink gaming data exchange) with a gaming server. The UE 405 may modify the standard mobility procedure 605 such that the low latency application mobility procedure 610 includes additional conditions that can be considered for the handover (e.g., conditions that do not need to be satisfied, but are sufficient to trigger a handover) if latency for the video game in the serving cell 430 of the UE 405 is high, thereby increasing the likelihood that the handover will be triggered. Alternatively, the UE 405 may modify the standard mobility procedure 605 such that the low latency application mobility procedure 610 includes additional conditions that must be considered for the handover (e.g., additional conditions that are required to be satisfied to trigger a handover) if latency for the video game in the serving cell 430 of the UE 405 is low, thereby suppressing (e.g., decreasing the likelihood of) the transmission of a measurement report that might otherwise trigger the handover. In this way, the UE 405 may modify the standard mobility procedure 605 to initiate blocking of handover of the UE 405.
[0093] As another example, a user associated with the UE 405 may be exploring an art gallery in which multiple cells provide overlapping coverage for the UE 405. The user may be using an extended reality application (e.g., an augmented reality application) on the UE 405 to observe or to learn about various artistic works in the art gallery, where the extended reality application communicates a traffic flow with an application server to provide uplink head pose information and to receive a downlink rendered video overlay. The UE 405 may modify the standard mobility procedure 605 such that the low latency application mobility procedure 610 includes additional conditions that can be considered for the handover (e.g., conditions that do not need to be satisfied, but are sufficient to trigger a handover) if latency for the extended reality application in the serving cell 430 of the UE 405 is high, thereby increasing the likelihood that the handover will be triggered. Alternatively, the UE 405 may modify the standard mobility procedure 605 such that the low latency application mobility procedure 610 includes additional conditions that must be considered for the handover (e.g., additional conditions that are required to be satisfied to trigger a handover) if latency for the extended reality application in the serving cell 430 of the UE 405 is low, thereby suppressing (e.g., decreasing the likelihood of) the transmission of a measurement report that might otherwise trigger the handover. In this way, the UE 405 may modify the standard mobility procedure 605 to initiate blocking of handover of the UE 405.
[0094] In the above scenarios (and in other low latency application scenarios) , performing the standard mobility procedure 605 may result in frequent cell switching or less than optimal cell switching for prioritizing latency for the low latency application of the UE 405. For example, fluctuations in RSRP for multiple cells near the UE 405 may result in frequent handover or cell switching, thereby increasing the latency for the low latency application of the UE 405. As another example, the UE 405 may determine that a target cell 435 has a greater signal strength relative to a signal strength of the serving cell 430 (e.g., in association with a RSRP measurements for the serving cell 430 and for the target cell 435) and may transmit a measurement report to the serving network node 410 to trigger a handover of the UE 405 from the serving cell 430 to the target cell 435, even though the serving cell 430 may provide lower latency for the low latency application relative to the target cell 435. As a result, the UE 405 may switch to a higher latency cell (e.g., the target cell 435) , which provides worse latency performance for the low latency application. As another example, the UE 405 may determine that the serving cell 430 has a greater signal strength relative to a signal strength of a target cell 435 (e.g., in association with RSRP measurements for the serving cell 430 and for the target cell 435) and may refrain from triggering a handover of the UE 405 from the serving cell 430 to the target cell 435 even though the target cell 435 may provide lower latency for the low latency application relative to the serving cell 430. As a result, the UE 405 may remain in a higher latency cell (e.g., the serving cell 430) , which provides worse latency performance for the low latency application. The use of the low latency application mobility procedure 610 in these scenarios may instead enable the UE 405 to effectively block handover of the UE 405 to a higher latency cell (e.g., by suppressing the transmission of a measurement report that might otherwise trigger the handover) if the serving cell 430 provides better latency performance, or to more quickly initiate handover to a lower latency cell (and then to suppress measurement reports to initiate blocking of subsequent handovers once the handover is complete) if the serving cell 430 provides worse latency performance.
[0095] As shown in Fig. 6A, at 615, the low latency application mobility procedure 610 may include determining whether an application associated with the UE 405 is a particular application type. The UE 405 may determine the application type in association with a traffic flow associated with the application. For example, the UE 405 may determine that the traffic flow (which may include uplink data and / or downlink data communicated between the UE 405 and the serving network node 410) carries gaming data or live video stream data, among other examples, and may therefore determine the application type to be a low latency application type. Examples of low latency application types include, but are not limited to, gaming applications, live video streaming applications, voice call applications, video call applications, and / or extended reality applications (e.g., augmented reality applications, virtual reality applications) , among other examples.
[0096] If the UE 405 determines that the application is not associated with a particular application type (e.g., is not a low latency application type: 615 -No) , the UE 405 may instead perform the standard mobility procedure 605 for the traffic flow associated with the application. If the UE 405 determines that the application is associated with a particular application type (e.g., is a low latency application type: 615 -Yes) , the UE 405 may continue with performing the low latency application mobility procedure 610 to modify the standard mobility procedure 605.
[0097] At 620, the UE 405 determine an application link state associated with an access link on which the UE 405 is to communicate the traffic flow with the serving network node 410. The access link may include downlink communication and / or uplink communication. At 625, the UE 405 may modify the mobility procedure performed by the UE 405 in association with the application link state. The UE 405 may determine the application link state and / or may modify the mobility procedure at a plurality of times according to a particular time interval T. In other words, the UE 405 may determine the application link state and / or may modify the mobility procedure every T occasion or every T seconds that the application of the particular application type is in use on the UE 405.
[0098] Fig. 6B illustrates various examples of determining an application link state for a traffic flow associated with an application (e.g., a low latency application or another particular type of application) . As shown in Fig. 6B, at 630, the UE 405 may determine a radio bearer associated with the traffic flow associated with the application. “Radio bearer” may refer to a layer 2 logical communication channel that is provided for the transfer of data between the UE 405 and the serving network node 410. Some radio bearers may be control plane radio bearers that are configured for the exchange of control plane data, and some other radio bearers may be user plane radio bearers that are configured for the exchange of user plane data. A radio bearer may further be classified for particular types of traffic flows and / or for supporting a particular quality of service (QoS) . A radio bearer for a video gaming application may be an Internet radio bearer (e.g., a QCI9 relevant radio bearer) with a low layer mobility (LLM) indication. A voice call radio bearer may be referred to as a QCI1 radio bearer. Other types of Internet traffic flows (e.g., non-low-latency application traffic flows) may be associated with QCI9 relevant radio bearers without an LLM indication.
[0099] At 635 and 640, the UE 405 may determine one or more layer 2 parameters associated with the access link between the UE 405 and the serving network node 410. The UE 405 may determine the one or more layer 2 parameters in association with wireless communication conditions on the radio bearer associated with the traffic flow of the application. At 635, the UE 405 may determine one or more downlink layer 2 parameters associated with a downlink of the access link (e.g., in association with the radio bearer associated with the traffic flow of the application) . At 640, the UE 405 may determine one or more uplink layer 2 parameters associated with an uplink of the access link (e.g., in association with the radio bearer associated with the traffic flow of the application) .
[0100] Examples of downlink layer 2 parameters include, but are not limited to, a downlink throughput on a downlink of the access link (e.g., a downlink Tputs per second parameter) , a downlink radio link control (RLC) BLER on the downlink, and / or a downlink PDU miss rate on the downlink, among other examples. “PDU miss rate” may refer to a rate of missed or unreceived PDUs on the downlink at the UE 405. The UE 405 may determine the one or more downlink layer 2 parameters by monitoring downlink traffic from the serving network node 410, by performing one or more measurements of the downlink traffic, and / or using another technique.
[0101] Examples of uplink layer 2 parameters include, but are not limited to, a quantity of uplink grants per second received from the serving network node 410 (e.g., during a time duration, such as at every time interval T) , an uplink buffer size rate of the uplink, and / or an uplink PDCP discard rate on the uplink, among other examples. “Uplink PDCP discard rate” may refer to a rate of discarded or unreceived PDCP packets on the uplink at the serving network node 410. The UE 405 may determine the one or more uplink layer 2 parameters by monitoring uplink traffic to the serving network node 410, by performing one or more measurements of the uplink traffic, by receiving an indication of the one or more uplink layer 2 parameters from the serving network node 410, and / or using another technique.
[0102] At 645, the UE 405 may determine the application link state in association with the one or more downlink layer 2 parameters and / or the one or more uplink layer 2 parameters. The application link state may be an indicator of whether conditions on the access link between the UE 405 and the serving network node 410 provide sufficient service for the application (e.g., a low latency application or another particular type of application) . The application link state may include a plurality of link state categories corresponding to unsatisfactory (or “poor” ) conditions or satisfactory (or “good” ) conditions on the access link. These categories may be assigned to respective values, such as 0 for unsatisfactory conditions and 1 for satisfactory conditions on the access link, among other examples.
[0103] In some aspects, the UE 405 may determine the application link state to indicate that satisfactory conditions are provided on the access link in association with the UE 405 determining that satisfactory conditions are provided on the downlink in association with the one or more downlink layer 2 parameters, and determining that satisfactory conditions are provided on the uplink in association with the one or more uplink layer 2 parameters (e.g., that both the downlink and the uplink provide satisfactory conditions) . In some aspects, the UE 405 may determine the application link state to indicate that unsatisfactory conditions are provided on the access link in association with the UE 405 determining that unsatisfactory conditions are provided on the access link in association with the UE 405 determining that satisfactory conditions are provided on the downlink in association with the one or more downlink layer 2 parameters, and / or determining that unsatisfactory conditions are provided on the uplink in association with the one or more uplink layer 2 parameters (e.g., that at least one of the downlink or the uplink provides unsatisfactory conditions) .
[0104] In some aspects, the UE 405 may determine that conditions on the downlink are satisfactory or unsatisfactory by comparing the one or more downlink layer 2 parameters with one or more associated thresholds. Similarly, the UE 405 may determine that conditions on the uplink are satisfactory or unsatisfactory by comparing the one or more uplink layer 2 parameters with one or more associated thresholds.
[0105] As an example, if the UE 405 determines that the downlink throughput on the downlink satisfies a throughput threshold, the downlink RLC BLER satisfies a BLER threshold, and the downlink PDU miss rate satisfies a miss rate threshold, the UE 405 may determine that the conditions on the downlink are satisfactory. As another example, if the UE 405 determines that at least one of the downlink throughput on the downlink does not satisfy the throughput threshold, the downlink RLC BLER does not satisfy the BLER threshold, or the downlink PDU miss rate does not satisfy the miss rate threshold, the UE 405 may determine that the conditions on the downlink are unsatisfactory.
[0106] As another example, if the UE 405 determines that the uplink grants per second satisfies a grants per second threshold, the uplink buffer size rate satisfies a buffer size rate threshold, and the uplink PDCP discard rate satisfies a discard rate threshold, the UE 405 may determine that the conditions on the uplink are satisfactory. As another example, if the UE 405 determines that at least one of the uplink grants per second does not satisfy the grants per second threshold, the uplink buffer size rate does not satisfy the buffer size rate threshold, or the uplink PDCP discard rate does not satisfy the discard rate threshold, the UE 405 may determine that the conditions on the uplink are unsatisfactory.
[0107] In some aspects, the UE 405 may use different thresholds for a particular layer 2 parameter to determine whether the downlink, the uplink, and / or the access link provide satisfactory or unsatisfactory conditions. As an example, the UE 405 may compare the downlink throughput parameter ( “DL1” ) with an upper throughput threshold ( “DLhigh1” ) and a lower throughput threshold ( “DLlow1” ) . The UE 405 may compare the downlink RLC BLER parameter ( “DL2” ) with an upper BLER threshold ( “DLhigh2” ) and a lower BLER threshold ( “DLlow2” ) . The UE 405 may compare the downlink PDU miss rate parameter ( “DL3” ) with an upper miss rate threshold ( “DLhigh3” ) and a lower miss rate threshold ( “DLlow3” ) . The UE 405 may compare the uplink grants per second parameter ( “UL1” ) with an upper grants per second threshold ( “ULhigh3” ) and a lower grants per second threshold ( “ULlow1” ) . The UE 405 may compare the uplink buffer size rate parameter ( “UL2” ) with an upper buffer size rate threshold ( “ULhigh2” ) and a lower buffer size rate threshold ( “ULlow2” ) . The UE 405 may compare the uplink PDCP discard rate parameter ( “UL3” ) with an upper discard rate threshold ( “ULhigh3” ) and a lower discard rate threshold ( “ULlow3” ) .
[0108] If the UE 405 determines that the following conditions are satisfied: If {Dl1> DLhigh1 &&DL2< DLlow2 &&DL3< DLlow3} && {UL1 >ULhigh1 &&UL2<ULlow2 &&UL3<ULlow3 } ,
[0109] the UE 405 may determine the application link state to indicate that conditions on the access link are satisfactory for the traffic flow associated with the application. In other words, the UE 405 may determine the application link state to indicate that conditions on the access link are satisfactory in association with determining that the downlink throughput parameter (DL1) satisfies the upper throughput threshold (DLhigh1) , the downlink RLC BLER parameter (DL2) satisfies the lower BLER threshold (DLlow2) , the downlink PDU miss rate parameter (DL3) satisfies the lower miss rate threshold (DLlow3) , the uplink grants per second parameter (UL1) satisfies the upper grants per second threshold (ULhigh3) , the uplink buffer size rate parameter (UL2) satisfies the upper buffer size rate threshold (ULhigh2) , and the uplink PDCP discard rate parameter (UL3) satisfies the lower discard rate threshold (ULlow3) .
[0110] If the UE 405 determines that the following conditions are satisfied: If {DL1< DLlow1 || DL2>DLhigh2 || DL3> DLhigh3} || {UL1 <ULlow1 || UL2>ULhigh2 || UL3> ULhigh3} ,
[0111] the UE 405 may determine the application link state to indicate that conditions on the access link are unsatisfactory for the traffic flow associated with the application. In other words, the UE 405 may determine the application link state to indicate that conditions on the access link are unsatisfactory in association with determining at least one of: the downlink throughput parameter (DL1) satisfies the lower throughput threshold (DLlow1) , the downlink RLC BLER parameter (DL2) satisfies the upper BLER threshold (DLhigh2) , the downlink PDU miss rate parameter (DL3) satisfies the upper miss rate threshold (DLhigh3) , the uplink grants per second parameter (UL1) satisfies the lower grants per second threshold (ULlow3) , the uplink buffer size rate parameter (UL2) satisfies the lower buffer size rate threshold (ULlow2) , or the uplink PDCP discard rate parameter (UL3) satisfies the upper discard rate threshold (ULhigh3) .
[0112] In some aspects, additional categories of conditions on the uplink, the downlink, and / or the access link may be indicated by the application link state. For example, the UE 405 may determine the application link state to indicate one of a “low, ” “medium, ” or “high” for the conditions on the uplink, the downlink, and / or the access link. In these aspects, additional thresholds may be configured for the one or more downlink layer 2 parameters and / or for the one or more uplink layer 2 parameters. For example, the UE 405 may compare the downlink throughput parameter (DL1) with a lower throughput threshold (DLlow1) , a medium throughput threshold (DLmed1) , and an upper throughput threshold (DLhigh1) . The UE 405 may compare other layer parameters to thresholds in a similar manner. Additional categories for the application link state enable the UE 405 to bias the modifications for the mobility procedure associated with the UE 405 to further resist handover of the UE 405 to a target cell 435 when conditions are highly satisfactory in the serving cell 430 for low latency applications, to further promote handover of the UE 405 to a target cell 435 when conditions are highly unsatisfactory in the serving cell 430 for low latency applications, or to offer an intermediate level of influence for determining whether to handover the UE 405.
[0113] Fig. 6C illustrates various examples of modifying the mobility procedure performed by the UE 405 in association with the application link state for the traffic flow associated with the application (e.g., a low latency application or another particular type of application) . As shown in Fig. 6C, at 650, the UE 405 may modify the mobility procedure for the UE 405 to trigger (or increase a likelihood of) a handover of the UE 405 from a serving cell 430 of the UE 405 to a target cell 435 of the UE 405 in association with the application link state indicating unsatisfactory conditions on the access link for the traffic flow associated with the application. For example, the UE 405 may modify the mobility procedure by removing required conditions and / or parameters, and / or by adding additional optional conditions and / or parameters that can trigger a measurement report for triggering a handover. This effectively makes triggering the handover less difficult and more likely. In some aspects, the UE 405 may add additional optional conditions and / or parameters for every T interval that the UE 405 determines the application link state to indicate unsatisfactory conditions on the access link for the traffic flow associated with the application. Additionally and / or alternatively, the UE 405 may decrease the associated threshold values for the additional optional conditions and / or parameters for every T interval that the UE 405 determines the application link state to indicate unsatisfactory conditions on the access link for the traffic flow associated with the application.
[0114] The additional optional conditions and / or parameters may include an event_link parameter. The UE 405 may determine to transmit a measurement report to trigger a handover of the UE 405 in association with determining that at least one of the event_link parameter is satisfied or that an event described above in connection with Fig. 5 has occurred for triggering the measurement report, thereby providing more opportunities to trigger a handover. In some aspects, the UE 405 may determine to transmit a measurement report to trigger a handover of the UE 405 in association with determining that the event_link parameter is satisfied for a TTT, and / or determining that an event described above in connection with Fig. 5 has occurred for triggering the measurement report for the TTT. The UE 405 may determine the TTT based on an evaluation timer for events (e.g., a TTT_NW parameter) , where the TTT_NW parameter is configured by the serving network node 410. The UE 405 may determine the TTT in association with a timing parameter that may be increased or decreased for every T interval. In particular, the UE 405 may determine the TTT as a product of the TTT_NW parameter and the timing parameter.
[0115] The event_link parameter may be configured as: Event_Link=TargetRSRP –ServingRSRP ≥ Threshold 1 &&TargetSNR –ServingSNR≥Threshold 2 &&TargetSNR≥Threshold 3,
[0116] where TargetRSRP corresponds to the RSRP of the target cell 435, ServingRSRP corresponds to the RSRP of the serving cell 430, TargetSNR corresponds to the SNR of the target cell 435, and ServingSNR corresponds to the SNR of the serving cell 430. Accordingly, the UE 405 may determine that the event_link parameter is satisfied if the difference between the RSRP of the target cell 435 and the RSRP of the serving cell 430 satisfies a first threshold (Threshold 1) , the difference between the SNR of the target cell 435 and the SNR of the serving cell 430 satisfies a second threshold (Threshold 2) , and the SNR of the target cell 435 satisfies a third threshold (Threshold 3) .
[0117] As further shown in Fig. 6C, at 655, the UE 405 may modify the mobility procedure for the UE 405. The UE 405 may modify the mobility procedure to suppress the transmission of a measurement report to initiate blocking (or to reduce a likelihood of) a handover of the UE 405 from a serving cell 430 of the UE 405 to a target cell 435 of the UE 405 in association with the application link state indicating satisfactory conditions on the access link for the traffic flow associated with the application. For example, the UE 405 may modify the mobility procedure by adding additional conditions and / or parameters that are required to be satisfied before a measurement report is transmitted from the UE 405 to the serving network node 410 to trigger a handover. This effectively makes triggering the handover more difficult and less likely. In some aspects, the UE 405 may add additional conditions and / or parameters for every T interval that the UE 405 determines the application link state to indicate satisfactory conditions on the access link for the traffic flow associated with the application. Additionally and / or alternatively, the UE 405 may increase the associated threshold values for the additional conditions and / or parameters for every T interval that the UE 405 determines the application link state to indicate satisfactory conditions on the access link for the traffic flow associated with the application.
[0118] The additional conditions and / or parameters may include the event_link parameter described above. The UE 405 may determine to transmit a measurement report to trigger a handover of the UE 405 in association with determining that the event_link is satisfied, in addition to determining that an event described above in connection with Fig. 5 has occurred for triggering the measurement report. In some aspects, the UE 405 may determine to transmit a measurement report to trigger a handover of the UE 405 in association with determining that the event_link is satisfied for a TTT, in addition to determining that an event described above in connection with Fig. 5 has occurred for triggering the measurement report for the TTT. The UE 405 may determine the TTT based on an evaluation timer for events (e.g., a TTT_NW parameter) , where the TTT_NW parameter is configured by the serving network node 410. The UE 405 may determine the TTT in association with a timing parameter that may be increased or decreased for every T interval. In particular, the UE 405 may determine the TTT as a product of the TTT_NW parameter and the timing parameter.
[0119] As further shown in Fig. 6C, at 660, the UE 405 may determine an “else” condition for the application link state and may perform the standard mobility procedure described above in connection with Fig. 5 for the traffic flow associated with the application. This may occur, for example, in scenarios in which latency conditions in the serving cell 430 and in the target cell 435 are comparable and satisfactory.
[0120] In some aspects, the UE 405 may modify the mobility procedure to avoid or to initiate blocking of handover of the UE 405 to achieve power saving for the UE 405. For example, If the UE 405 is experiencing low data rates and no downlink stall conditions on the downlink, the UE 405 may modify the mobility procedure to avoid or initiate blocking of handover of the UE 405 to so that handover does not prevent the UE 405 from transitioning to a power saving mode or to an inactive mode. The UE 405 may maintain an inactivity timer (e.g., a 10 second timer or another time duration) after expiration of which the UE 405 may transition to the power saving mode or the inactive mode if there is data inactivity on the access link between initiation and expiration of the inactivity timer. A handover of the UE 405 initiates the establishment of a new RRC connection for the UE 405, which causes the inactivity timer to be restarted, there by delaying the ability of the UE 405 to transition to the power saving mode or to the inactive mode. Accordingly, the UE 405 may modify the mobility procedure to avoid or initiate blocking of handover of the UE 405 to so that handover of the UE 405 does cause a restart of the inactivity timer, thereby enabling the UE 405 to more quickly transition to the power saving mode or to the inactive mode. This may reduce power consumption of the UE 405 and / or increase power efficiency of the UE 405.
[0121] In some aspects, the UE 405 may modify the mobility procedure to avoid or to initiate blocking of handover of the UE 405 by initiating modification of one or more thresholds associated with one or more events of the standard mobility procedure 605 in association with the application link state. For example, the UE 405 may transmit a UE assistance information (UAI) communication to the serving network node 410 to indicate that low latency traffic with a reduced bandwidth requirement (e.g., the traffic flow associated with the application) is active. The indication in the UAI communication may enable the serving network node 410 to configure one or more modified thresholds for the one or more events of the standard mobility procedure such that the low latency mobility procedure 610 includes the one or more modified thresholds. The serving network node 410 may receive the UAI communication and may modify a configuration (e.g., a measurement configuration or handover configuration) for the UE 405, and may provide the modified configuration to the UE 405. The UE 405 may receive the modified configuration and may use the modified configuration to determine whether to transmit a measurement report to trigger a handover of the UE 405.
[0122] Additionally and / or alternatively, the serving network node 410 may proactively modify the one or more thresholds associated with one or more events of the standard mobility procedure 605. For example, the serving network node 410 may determine that the traffic flow associated with the application is low latency traffic with a reduced bandwidth requirement and may proactively modify the one or more thresholds associated with one or more events of the standard mobility procedure 605 in association with determining that the traffic flow associated with the application is low latency traffic with a reduced bandwidth requirement. The serving network node 410 may determine that the traffic flow associated with the application is low latency traffic with a reduced bandwidth requirement by performing techniques such as deep packet in section of the traffic flow, by identifying a QoS (e.g., in association with a 5G QoS identifier (5QI) or another QoS identifier) associated with the traffic flow, and / or by identifying a QoS class identifier (QCI) associated with the traffic flow, among other examples. The serving network node 410 may modify a configuration (e.g., a measurement configuration or handover configuration) for the UE 405 in association with determining that the traffic flow is low latency traffic with a reduced bandwidth requirement, and may provide the modified configuration to the UE 405. The UE 405 may receive the modified configuration and may use the modified configuration to determine whether to transmit a measurement report to trigger a handover of the UE 405.
[0123] As indicated above, Figs. 6A-6C is provided as examples. Other examples may differ from what is described with respect to Figs. 6A-6C.
[0124] Fig. 7 is a diagram illustrating an example process 700 performed, for example, by a UE, in accordance with the present disclosure. Example process 700 is an example where the UE (e.g., a UE 120, a UE 405) performs operations associated with modifying a mobility procedure for low latency traffic in a wireless network.
[0125] As shown in Fig. 7, in some aspects, process 700 may include determining an application type associated with a traffic flow associated with the UE (block 710) . For example, the UE (e.g., using communication manager 806, depicted in Fig. 8) may determine an application type associated with a traffic flow associated with the UE, as described above.
[0126] As further shown in Fig. 7, in some aspects, process 700 may include determining, in association with the application type, an application link state associated with an access link on which the UE is to communicate the traffic flow with a network node (block 720) . For example, the UE (e.g., using communication manager 806, depicted in Fig. 8) may determine, in association with the application type, an application link state associated with an access link on which the UE is to communicate the traffic flow with a network node, as described above.
[0127] As further shown in Fig. 7, in some aspects, process 700 may include modifying a mobility procedure for the UE in association with the application link state (block 730) . For example, the UE (e.g., using communication manager 806, depicted in Fig. 8) may modify a mobility procedure for the UE in association with the application link state, as described above.
[0128] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.
[0129] In a first aspect, determining the application type comprises determining the application type to be a low latency application type.
[0130] In a second aspect, alone or in combination with the first aspect, the low latency application type comprises at least one of a gaming application, a live video streaming application, or a voice call application.
[0131] In a third aspect, alone or in combination with one or more of the first and second aspects, determining the application link state comprises determining the application link state at a plurality of times according to a particular time interval.
[0132] In a fourth aspect, alone or in combination with one or more of the first through third aspects, modifying the mobility procedure comprises modifying the mobility procedure at a plurality of times according to the particular time interval.
[0133] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, determining the application link state comprises determining the application link state in association with one or more layer 2 parameters associated with the access link.
[0134] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, determining the application link state in association with the one or more layer 2 parameters associated with the access link comprises determining one or more first layer 2 parameters associated with a downlink of the access link, determining one or more second layer 2 parameters associated with an uplink of the access link, and determining the application link state in association with the one or more first layer 2 parameters and the one or more second layer 2 parameters.
[0135] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, determining the application link state comprises determining a radio bearer associated with the traffic flow, and determining the application link state in association with one or more layer 2 parameters associated with the radio bearer.
[0136] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the one or more layer 2 parameters comprise at least one of a downlink throughput on a downlink of the access link, a downlink RLC BLER on the downlink, a downlink PDU miss rate on the downlink, a quantity of uplink grants per second for an uplink of the access link, an uplink buffer size rate of the uplink, or an uplink PDCP discard rate on the uplink.
[0137] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, determining the application link state in association with the one or more layer 2 parameters associated with the access link comprises determining whether the one or more layer 2 parameters satisfy one or more associated thresholds, and determining the application link state in association with whether the one or more layer 2 parameters satisfy the one or more associated thresholds.
[0138] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, a layer 2 parameter of the one or more layer 2 parameters is associated with a plurality of thresholds, wherein the application link state is associated with a first threshold of the plurality of thresholds, wherein another application link state is associated with a second threshold of the plurality of thresholds, and wherein determining the application link state in association with the one or more layer 2 parameters associated with the access link comprises determining that the layer 2 parameter satisfies the first threshold and not the second threshold, and determining the application link state in association with determining that the layer 2 parameter satisfies the first threshold and not the second threshold.
[0139] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, modifying the mobility procedure for the UE comprises modifying the mobility procedure for the UE to initiate blocking of handover of the UE from a serving cell of the UE to a target cell of the UE in association with the application link state.
[0140] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, modifying the mobility procedure for the UE comprises modifying the mobility procedure to suppress transmission of a measurement report to initiate blocking of handover of the UE.
[0141] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, modifying the mobility procedure for the UE comprises increasing a quantity of conditions that are to be satisfied before a handover of the UE is triggered.
[0142] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, modifying the mobility procedure for the UE comprises increasing threshold values for the conditions that are to be satisfied before the handover of the UE is triggered.
[0143] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, modifying the mobility procedure for the UE comprises modifying the mobility procedure for the UE to trigger a handover of the UE from a serving cell of the UE to a target cell of the UE in association with the application link state.
[0144] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, modifying the mobility procedure for the UE comprises increasing a quantity of conditions that can trigger the handover of the UE.
[0145] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, modifying the mobility procedure for the UE comprises reducing threshold values for the conditions that can trigger the handover of the UE.
[0146] Although Fig. 7 shows example blocks of process 700, in some aspects, process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 7. Additionally, or alternatively, two or more of the blocks of process 700 may be performed in parallel.
[0147] Fig. 8 is a diagram of an example apparatus 800 for wireless communication, in accordance with the present disclosure. The apparatus 800 may be a UE (e.g., a UE 120, a UE 405) , or a UE may include the apparatus 800. In some aspects, the apparatus 800 includes a reception component 802, a transmission component 804, and / or a communication manager 806, which may be in communication with one another (for example, via one or more buses and / or one or more other components) . In some aspects, the communication manager 806 is the communication manager 140 described in connection with Fig. 1. As shown, the apparatus 800 may communicate with another apparatus 808, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 802 and the transmission component 804.
[0148] In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with Figs. 4-6C. Additionally, or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 700 of Fig. 7. In some aspects, the apparatus 800 and / or one or more components shown in Fig. 8 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 8 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.
[0149] The reception component 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 808. The reception component 802 may provide received communications to one or more other components of the apparatus 800. In some aspects, the reception component 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 800. In some aspects, the reception component 802 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.
[0150] The transmission component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 808. In some aspects, one or more other components of the apparatus 800 may generate communications and may provide the generated communications to the transmission component 804 for transmission to the apparatus 808. In some aspects, the transmission component 804 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 808. In some aspects, the transmission component 804 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 804 may be co-located with the reception component 802 in a transceiver.
[0151] The communication manager 806 may support operations of the reception component 802 and / or the transmission component 804. For example, the communication manager 806 may receive information associated with configuring reception of communications by the reception component 802 and / or transmission of communications by the transmission component 804. Additionally, or alternatively, the communication manager 806 may generate and / or provide control information to the reception component 802 and / or the transmission component 804 to control reception and / or transmission of communications.
[0152] The communication manager 806 may determine an application type associated with a traffic flow associated with the apparatus 800. The communication manager 806 may determine, in association with the application type, an application link state associated with an access link on which the apparatus 800 is to communicate the traffic flow with the apparatus 808. The communication manager 806 may modify a mobility procedure for the apparatus 800 in association with the application link state.
[0153] The number and arrangement of components shown in Fig. 8 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 8. Furthermore, two or more components shown in Fig. 8 may be implemented within a single component, or a single component shown in Fig. 8 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 8 may perform one or more functions described as being performed by another set of components shown in Fig. 8.
[0154] The following provides an overview of some Aspects of the present disclosure:
[0155] Aspect 1: A method of wireless communication performed by a user equipment (UE) , comprising: determining an application type associated with a traffic flow associated with the UE; determine, in association with the application type, an application link state associated with an access link on which the UE is to communicate the traffic flow with a network node; and modifying a mobility procedure for the UE in association with the application link state.
[0156] Aspect 2: The method of Aspect 1, wherein determining the application type comprises: determining the application type to be a low latency application type.
[0157] Aspect 3: The method of Aspect 2, wherein the low latency application type comprises at least one of: a gaming application, a live video streaming application, or a voice call application.
[0158] Aspect 4: The method of any of Aspects 1-3, wherein determining the application link state comprises: determining the application link state at a plurality of times according to a particular time interval.
[0159] Aspect 5: The method of Aspect 4, wherein modifying the mobility procedure comprises: modifying the mobility procedure at a plurality of times according to the particular time interval.
[0160] Aspect 6: The method of any of Aspects 1-5, wherein determining the application link state comprises: determining the application link state in association with one or more layer 2 parameters associated with the access link.
[0161] Aspect 7: The method of Aspect 6, wherein determining the application link state in association with the one or more layer 2 parameters associated with the access link comprises: determining one or more first layer 2 parameters associated with a downlink of the access link; determining one or more second layer 2 parameters associated with an uplink of the access link; and determining the application link state in association with the one or more first layer 2 parameters and the one or more second layer 2 parameters.
[0162] Aspect 8: The method of Aspect 6 or 7, wherein determining the application link state comprises: determining a radio bearer associated with the traffic flow; and determining the application link state in association with one or more layer 2 parameters associated with the radio bearer.
[0163] Aspect 9: The method of any of Aspects 6-8, wherein the one or more layer 2 parameters comprise at least one of: a downlink throughput on a downlink of the access link, a downlink radio link control (RLC) block error rate (BLER) on the downlink, a downlink protocol data unit (PDU) miss rate on the downlink, a quantity of uplink grants per second for an uplink of the access link, an uplink buffer size rate of the uplink, or an uplink packet data convergence protocol (PDCP) discard rate on the uplink.
[0164] Aspect 10: The method of any of Aspects 6-9, wherein determining the application link state in association with the one or more layer 2 parameters associated with the access link comprises: determining whether the one or more layer 2 parameters satisfy one or more associated thresholds; and determining the application link state in association with whether the one or more layer 2 parameters satisfy the one or more associated thresholds.
[0165] Aspect 11: The method of any of Aspects 6-10, wherein a layer 2 parameter of the one or more layer 2 parameters is associated with a plurality of thresholds; wherein the application link state is associated with a first threshold of the plurality of thresholds; wherein another application link state is associated with a second threshold of the plurality of thresholds; and wherein determining the application link state in association with the one or more layer 2 parameters associated with the access link comprises: determining that the layer 2 parameter satisfies the first threshold and not the second threshold; and determining the application link state in association with determining that the layer 2 parameter satisfies the first threshold and not the second threshold.
[0166] Aspect 12: The method of any of Aspects 1-11, wherein modifying the mobility procedure for the UE comprises: modifying the mobility procedure for the UE to initiate blocking of handover of the UE from a serving cell of the UE to a target cell of the UE in association with the application link state.
[0167] Aspect 13: The method of Aspect 12, wherein modifying the mobility procedure for the UE comprises modifying the mobility procedure to suppress transmission of a measurement report to initiate blocking of handover of the UE.
[0168] Aspect 14: The method of Aspect 12 or 13, wherein modifying the mobility procedure for the UE comprises: increasing a quantity of conditions that are to be satisfied before a handover of the UE is triggered.
[0169] Aspect 15: The method of any of Aspects 12-14, wherein modifying the mobility procedure for the UE comprises: increasing threshold values for the conditions that are to be satisfied before the handover of the UE is triggered.
[0170] Aspect 16: The method of any of Aspects 1-15, wherein modifying the mobility procedure for the UE comprises: modifying the mobility procedure for the UE to trigger a handover of the UE from a serving cell of the UE to a target cell of the UE in association with the application link state.
[0171] Aspect 17: The method of Aspect 16, wherein modifying the mobility procedure for the UE comprises: increasing a quantity of conditions that can trigger the handover of the UE.
[0172] Aspect 18: The method of Aspect 17, wherein modifying the mobility procedure for the UE comprises: reducing threshold values for the conditions that can trigger the handover of the UE.
[0173] Aspect 19: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-18.
[0174] Aspect 20: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-18.
[0175] Aspect 21: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-18.
[0176] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-18.
[0177] Aspect 23: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-18.
[0178] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed.
[0179] Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.
[0180] As used herein, the term “component” is intended to be broadly construed as hardware and / or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein may be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and / or methods based, at least in part, on the description herein.
[0181] As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.
[0182] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (e.g., a + a, a + a + a, a + a + b, a +a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c) .
[0183] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more. ” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more. ” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more. ” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has, ” “have, ” “having, ” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B) . Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or, ” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of” ) .
Claims
1.A user equipment (UE) for wireless communication, comprising:one or more memories; andone or more processors, coupled to the one or more memories, configured to:determine an application type associated with a traffic flow associated with the UE;determine, in association with the application type, an application link state associated with an access link on which the UE is to communicate the traffic flow with a network node; andmodify a mobility procedure for the UE in association with the application link state.2.The UE of claim 1, wherein the one or more processors, to determine the application type, are configured to:determine the application type to be a low latency application type.3.The UE of claim 2, wherein the low latency application type comprises at least one of:a gaming application,a live video streaming application, ora voice call application.4.The UE of claim 1, wherein the one or more processors, to determine the application link state, are configured to:determine the application link state at a plurality of times according to a particular time interval.5.The UE of claim 4, wherein the one or more processors, to modify the mobility procedure, are configured to:modify the mobility procedure at a plurality of times according to the particular time interval.6.The UE of claim 1, wherein the one or more processors, to determine the application link state, are configured to:determine the application link state in association with one or more layer 2 parameters associated with the access link.7.The UE of claim 6, wherein the one or more processors, to determine the application link state in association with the one or more layer 2 parameters associated with the access link, are configured to:determine one or more first layer 2 parameters associated with a downlink of the access link; anddetermine one or more second layer 2 parameters associated with an uplink of the access link; anddetermine the application link state in association with the one or more first layer 2 parameters and the one or more second layer 2 parameters.8.The UE of claim 6, wherein the one or more processors, to determine the application link state, are configured to:determine a radio bearer associated with the traffic flow; anddetermine the application link state in association with one or more layer 2 parameters associated with the radio bearer.9.The UE of claim 6, wherein the one or more layer 2 parameters comprise at least one of:a downlink throughput on a downlink of the access link,a downlink radio link control (RLC) block error rate (BLER) on the downlink,a downlink protocol data unit (PDU) miss rate on the downlink,a quantity of uplink grants per second for an uplink of the access link,an uplink buffer size rate of the uplink, oran uplink packet data convergence protocol (PDCP) discard rate on the uplink.10.The UE of claim 6, wherein the one or more processors, to determine the application link state in association with the one or more layer 2 parameters associated with the access link, are configured to:determine whether the one or more layer 2 parameters satisfy one or more associated thresholds; anddetermine the application link state in association with whether the one or more layer 2 parameters satisfy the one or more associated thresholds.11.The UE of claim 6, wherein a layer 2 parameter of the one or more layer 2 parameters is associated with a plurality of thresholds;wherein the application link state is associated with a first threshold of the plurality of thresholds;wherein another application link state is associated with a second threshold of the plurality of thresholds; andwherein the one or more processors, to determine the application link state in association with the one or more layer 2 parameters associated with the access link, are configured to:determine that the layer 2 parameter satisfies the first threshold and not the second threshold; anddetermine the application link state in association with determining that the layer 2 parameter satisfies the first threshold and not the second threshold.12.The UE of claim 1, wherein the one or more processors, to modify the mobility procedure for the UE, are configured to:modify the mobility procedure for the UE to initiate blocking of handover of the UE from a serving cell of the UE to a target cell of the UE in association with the application link state.13.The UE of claim 12, wherein the one or more processors, to modify the mobility procedure for the UE, are configured to:modify the mobility procedure to suppress transmission of a measurement report to initiate blocking handover of the UE.14.The UE of claim 12, wherein the one or more processors, to modify the mobility procedure for the UE, are configured to:increase a quantity of conditions that are to be satisfied before a handover of the UE is triggered.15.The UE of claim 12, wherein the one or more processors, to modify the mobility procedure for the UE, are configured to:increase threshold values for conditions that are to be satisfied before the handover of the UE is triggered.16.The UE of claim 1, wherein the one or more processors, to modify the mobility procedure for the UE, are configured to:modify the mobility procedure for the UE to trigger a handover of the UE from a serving cell of the UE to a target cell of the UE in association with the application link state.17.The UE of claim 16, wherein the one or more processors, to modify the mobility procedure for the UE, are configured to:increase a quantity of conditions that can trigger the handover of the UE.18.The UE of claim 17, wherein the one or more processors, to modify the mobility procedure for the UE, are configured to:reduce threshold values for the conditions that can trigger the handover of the UE.19.A method of wireless communication performed by a user equipment (UE) , comprising:determining an application type associated with a traffic flow associated with the UE;determining, in association with the application type, an application link state associated with an access link on which the UE is to communicate the traffic flow with a network node; andmodifying a mobility procedure for the UE in association with the application link state.20.The method of claim 18, wherein determining the application type comprises:determining the application type to be a low latency application type.21.The method of claim 19, wherein the low latency application type comprises at least one of:a gaming application,a live video streaming application, ora voice call application.22.The method of claim 18, wherein determining the application link state comprises:determining the application link state at a plurality of times according to a particular time interval.23.The method of claim 22, wherein modifying the mobility procedure comprises:modifying the mobility procedure at a plurality of times according to the particular time interval.24.The method of claim 19, wherein modifying the mobility procedure for the UE comprises:modifying the mobility procedure for the UE to initiate blocking of handover of the UE from a serving cell of the UE to a target cell of the UE in association with the application link state.25.The method of claim 24, wherein modifying the mobility procedure for the UE comprises:modifying the mobility procedure to suppress transmission of a measurement report to initiate blocking handover of the UE.26.A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising:one or more instructions that, when executed by one or more processors of a user equipment (UE) , cause the UE to:determine an application type associated with a traffic flow associated with the UE;determine, in association with the application type, an application link state associated with an access link on which the UE is to communicate the traffic flow with a network node; andmodify a mobility procedure for the UE in association with the application link state.27.The non-transitory computer-readable medium of claim 26, wherein the one or more instructions, that cause the UE to determine the application link state, cause the UE to:determine the application link state in association with one or more layer 2 parameters associated with the access link.28.The non-transitory computer-readable medium of claim 27, wherein the one or more instructions, that cause the UE to determine the application link state in association with the one or more layer 2 parameters associated with the access link, cause the UE to:determine one or more first layer 2 parameters associated with a downlink of the access link; anddetermine one or more second layer 2 parameters associated with an uplink of the access link; anddetermine the application link state in association with the one or more first layer 2 parameters and the one or more second layer 2 parameters.29.The non-transitory computer-readable medium of claim 27, wherein the one or more instructions, that cause the UE to determine the application link state, cause the UE to:determine a radio bearer associated with the traffic flow; anddetermine the application link state in association with one or more layer 2 parameters associated with the radio bearer.30.An apparatus for wireless communication, comprising:means for determining an application type associated with a traffic flow associated with the apparatus;means for determining, in association with the application type, an application link state associated with an access link on which the apparatus is to communicate the traffic flow with a network node; andmeans for modifying a mobility procedure for the apparatus in association with the application link state.31.The apparatus of claim 30, wherein the means for modifying the mobility procedure for the apparatus comprises:means for modifying the mobility procedure for the apparatus to block handover of the apparatus from a serving cell of the apparatus to a target cell of the apparatus in association with the application link state.32.The apparatus of claim 31, wherein the means for modifying the mobility procedure for the apparatus comprises:means for increasing a quantity of conditions that are to be satisfied before a handover of the apparatus is triggered.33.The apparatus of claim 28, wherein the means for modifying the mobility procedure for the apparatus comprises:means for increasing threshold values for conditions that are to be satisfied before the handover of the apparatus is triggered.
Citation Information
Patent Citations
Dynamic handoff parameters in a wireless network
US20130065632A1
Dynamic low latency configuration
WO2018188481A1
Enhancement for low latency service
WO2019041168A1
Mitigation of excessive handovers in a wireless communication system
WO2021257441A1
Cited By
Smart and dynamic cell reselection based on ran slicing
US20260032542A1
