Lower layer triggered mobility configuration verification

Abstract

The present disclosure relates to techniques for handling lower layer triggered mobility configuration verification in a wireless communication system. A wireless link may be established by a wireless device and a cellular base station. A radio resource control connection may be established for the wireless link. The wireless device may receive configuration information including lower layer triggered mobility configuration information indicating one or more lower layer triggered mobility candidate cell configurations. The wireless device may evaluate whether a lower layer triggered mobility candidate cell configuration is valid for the wireless device. The wireless device may send an indication of whether the lower layer triggered mobility candidate cell configuration is valid for the wireless device.

Description

Technical Field

[0001] This application relates to wireless communication, and more specifically to systems, apparatus, and methods for processing lower-layer triggered mobility configuration verification in wireless communication systems.

[0002] Related technical descriptions

[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices, such as smartphones and tablets, have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices (i.e., user equipment or UE) now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating complex applications that utilize these capabilities. Additionally, many different wireless communication technologies and standards exist. Some examples of wireless communication standards include GSM, UMTS (e.g., associated with WCDMA or TD-SCDMA air interfaces), LTE, LTE-A (LTE-Advanced), NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), and Bluetooth. ™ wait.

[0004] The increasing number of features and functionalities introduced into wireless communication devices has created a continuous demand for improvements in both wireless communication and the devices themselves. Specifically, it is crucial to ensure the accuracy of signals transmitted and received by user equipment (UE) devices, such as wireless devices like cellular phones, base stations, and relay stations used in wireless cellular communications. Furthermore, increasing the functionality of UE devices can significantly strain their battery life. Therefore, it is equally important to reduce the power requirements in UE device design while allowing them to maintain good transmit and receive capabilities for improved communication. Thus, improvements are expected in this area. Summary of the Invention

[0005] This paper presents implementation schemes for apparatus, systems, and methods for processing lower-layer triggered mobility (LTM) configuration verification in wireless communication systems.

[0006] According to the techniques described herein, increased processing time can be provided to a wireless device to assess the validity of the LTM configuration provided to the wireless device by the cellular base station and to respond to the cellular base station to confirm the validity of the LTM configuration. Techniques are described in which the response confirming the validity of the LTM configuration is included in the same transaction in which other configuration information is confirmed to be applied at the wireless device, and in which the response confirming the validity of the LTM configuration is included in a different transaction from the transaction in which other configuration information is confirmed to be applied at the wireless device.

[0007] This document also describes LTM configuration failure handling techniques. LTM configuration failure handling techniques may include techniques for releasing the current link based on the determination that an LTM configuration failure has occurred, and for reporting cause information for the LTM configuration failure when attempting to rebuild the link. LTM configuration failure handling techniques may also include techniques for maintaining the current link when an LTM configuration failure has occurred, and for reporting the LTM configuration failure (possibly with additional cause information) in response to LTM configuration information.

[0008] It should be noted that the technologies described herein may be implemented in several different types of devices and / or used in conjunction with such devices, including but not limited to base stations, access points, cellular phones, portable media players, tablet computers, wearable devices, unmanned aerial vehicles, unmanned flight controllers, automobiles and / or motor vehicles and various other computing devices.

[0009] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0010] A better understanding of the subject matter can be obtained by considering the following detailed description of various embodiments in conjunction with the accompanying drawings, in which:

[0011] Figure 1 Exemplary (and simplified) wireless communication systems according to some implementation schemes are shown;

[0012] Figure 2 An exemplary base station communicating with an exemplary wireless user equipment (UE) device according to some embodiments is shown;

[0013] Figure 3 An exemplary block diagram of a UE according to some implementation schemes is shown;

[0014] Figure 4 An exemplary block diagram of a base station according to some implementation schemes is shown;

[0015] Figure 5 Flowcharts illustrating aspects of exemplary possible methods for processing lower-layer triggered mobility configuration verification in a wireless communication system, according to some embodiments; and

[0016] Figure 6 Examples of scenarios are shown where LTM candidate configurations are evaluated and responded to in the same transaction, based on some implementation schemes and other RRC configuration information.

[0017] Figures 7 to 9 This illustrates example aspects of scenarios where LTM candidate configurations are evaluated and responded to in different transactions based on some implementation schemes and other RRC configuration information; and

[0018] Figures 10 to 11 Example aspects of scenarios where LTM candidate configuration failure can be reported without releasing the RRC connection are shown according to some implementations.

[0019] While the features described herein are susceptible to various modifications and alternatives, specific embodiments thereof are illustrated by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit one to the specific forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0020] acronym

[0021] Various acronyms are used throughout this disclosure. Definitions of the most frequently used acronyms that may appear throughout this disclosure are provided below:

[0022] UE: User Equipment

[0023] RF: Radio Frequency

[0024] BS: Base Station

[0025] 3GPP: Third Generation Partnership Project

[0026] LTE: Long Term Evolution

[0027] NR: New Radio

[0028] RAT: Radio Access Technology

[0029] the term

[0030] The following is a glossary of terms that may appear in this disclosure:

[0031] Memory media—any of various types of nontransitory memory devices or storage devices. The term "memory media" is intended to include mounting media, such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory; magnetic media, such as hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In a later example, the second computer system may provide program instructions to the first computer system for execution. The term "memory media" may include two or more memory media residing in different locations in different computer systems connected via, for example, a network. Memory media may store program instructions (e.g., embodied in a computer program) that can be executed by one or more processors.

[0032] Carrier medium—such as memory media as described above, and physical transmission medium, such as buses, networks, and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals, or digital signals).

[0033] Computer system (or computer) — any of various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined as any device (or combination of devices) that includes at least one processor that executes instructions from a memory medium.

[0034] User equipment (UE) (or “UE device”) — any of various types of computer systems or devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). ™ Based on Android ™ (phones), tablet computers (e.g., iPads) ™ Samsung Galaxy™ ), portable gaming devices (e.g., Nintendo DS) ™ PlayStation Portable ™ Gameboy Advance ™ iPhone ™ Wearable devices (e.g., smartwatches, smart glasses), laptops, PDAs, portable internet devices, music players, data storage devices, other handheld devices, automobiles and / or motor vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined as encompassing any electronic device, computing device, and / or telecommunications device (or a combination of these devices) that is easily transportable by the user and capable of wireless communication.

[0035] A wireless device is any of various types of computer systems or devices that perform wireless communication. A wireless device can be portable (or mobile), or it can be stationary or fixed in a location. A UE is an example of a wireless device.

[0036] A communication device is any of various types of computer systems or devices that perform communication, which may be wired or wireless. A communication device may be portable (or mobile), or it may be stationary or fixed in a location. A wireless device is one example of a communication device. A UE is another example of a communication device.

[0037] Base station (BS) — The term “base station” has the full range of its usual meaning and includes at least a wireless communication station that is installed in a fixed location and used for communication as part of a wireless telephone system or radio system.

[0038] A processing element (or processor) is a component or combination of components capable of performing the functions of a device (e.g., a user equipment device or a cellular network device). A processing element may include, for example, a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware elements such as a Field-Programmable Gate Array (FPGA), and any combination of the above.

[0039] Wi-Fi—The term “Wi-Fi” has the full range of its usual meaning and includes at least a wireless communication network or RAT that is served by and provides connectivity to the Internet through wireless LAN (WLAN) access points. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name “Wi-Fi.” Wi-Fi (WLAN) networks are different from cellular networks.

[0040] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In this context, "configured as" is a broad expression generally meaning "having a structure" that performs one or more tasks during operation. Therefore, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can be a broad expression generally meaning "having a circuit" that performs one or more tasks during operation. Therefore, a component can be configured to perform a task even when it is not currently powered on. Generally, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.

[0041] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are expressly intended not to invoke the interpretation of 35 U.S.C., 112(6).

[0042] Figure 1 and Figure 2 —Exemplary Communication System

[0043] Figure 1 Exemplary (and simplified) wireless communication systems that can implement various aspects of this disclosure according to some embodiments are shown. It should be noted that... Figure 1 The system described is merely one example of a possible system, and this implementation can be carried out in any system of various types as needed.

[0044] As shown in the figure, this exemplary wireless communication system includes a base station 102 that communicates with one or more (e.g., any number) user equipments 106A, 106B, etc., to 106N via a transmission medium. Each user equipment may be referred to herein as a “user equipment” (UE) or a UE device. Therefore, user equipment 106 is referred to as a UE or a UE device.

[0045] Base station 102 may be a transceiver base station (BTS) or a cell site, and may include hardware and / or software for enabling wireless communication with UEs 106A to 106N. If base station 102 is implemented in the context of LTE, it may be referred to as an "eNodeB" or "eNB". If base station 102 is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB". Base station 102 may also be equipped to communicate with network 100 (e.g., the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet, and various other possibilities). Therefore, base station 102 facilitates communication between user equipments and / or between user equipments and network 100. The communication area (or coverage area) of a base station may be referred to as a "cell". Also as used herein, in relation to a UE, a base station may sometimes be considered to represent the network, taking into account both uplink and downlink communication of the UE. Therefore, a UE communicating with one or more base stations in the network may also be understood as a UE communicating with the network.

[0046] It should be noted that, at least in some 3GPP NR contexts, base station (gNB) functionality can be split between a centralized unit (CU) and a distributed unit (DU). At least according to some implementations, in such network deployment contexts, the illustrated base station 102 may support the functionality of either a CU or a DU, or both. In some instances, base station 102 may be configured to act as an Integrated Access and Backhaul (IAB) donor (e.g., including IAB donor CU and / or IAB donor DU functionality). In some instances, base station 102 may be configured to act as an IAB node (e.g., including IAB mobile terminal (MT) and IAB-DU functionality). Other specific implementations are also possible.

[0047] Base station 102 and user equipment can be configured to communicate via a transmission medium using any of a variety of radio access technologies (RATs) (also known as wireless communication technologies or telecommunications standards, such as LTE, Advanced LTE (LTE-A), LAA / LTE-U, 5G NR, Wi-Fi, etc.).

[0048] Base station 102 and other similar base stations operating according to the same or different cellular communication standards may thus provide one or more cell networks that can provide continuous or near-continuous overlapping services to UE 106 and similar devices over a geographic area via one or more cellular communication standards.

[0049] It should be noted that UE 106 may be capable of communicating using multiple wireless communication standards. For example, UE 106 may be configured to communicate using one or more 3GPP cellular communication standards. In some implementations, UE 106 may be configured to perform techniques for handling lower-layer triggered mobility configuration failures in a wireless communication system, such as those described herein. UE 106 may also be configured, or alternatively configured, to use WLAN, Bluetooth, etc. ™ It can communicate with one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one and / or more mobile television broadcasting standards (e.g., ATSC-M / H), etc. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0050] Figure 2 An exemplary user equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 according to some embodiments is shown. UE 106 can be a device with wireless network connectivity, such as a mobile phone, handheld device, wearable device, computer or tablet computer, unmanned aerial vehicle (UAV), unmanned aerial controller (UAC), automotive, or virtually any type of wireless device. UE 106 may include a processor (processing element) configured to execute program instructions stored in memory. UE 106 can perform any method embodiment of the method embodiments described herein by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as field-programmable gate arrays (FPGAs), integrated circuits, and / or any of a variety of other possible hardware components configured to (e.g., individually or in combination) perform any method embodiment of the method embodiments described herein or any portion of any method embodiment of the method embodiments described herein. UE 106 can be configured to communicate using any of a plurality of wireless communication protocols. For example, UE 106 can be configured to use LTE, LTE-A, 5G NR, Wi-Fi, Bluetooth. TM Communication can be achieved using two or more of the GNSS standards. Other combinations of wireless communication standards are also possible.

[0051] UE 106 may include one or more antennas communicating using one or more wireless communication protocols according to one or more RAT standards. In some embodiments, UE 106 may share one or more portions of the receive chain and / or transmit chain among multiple wireless communication standards. Shared radio components may include a single antenna, or may include multiple antennas (e.g., for a multiple-input multiple-output or “MIMO” antenna system) for performing wireless communication. Generally, radio components may include any combination of baseband processors, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, radio components may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of the receive chain and / or transmit chain among multiple wireless communication technologies (such as those discussed above).

[0052] In some implementations, UE 106 may include any number of antennas and may be configured to use the antennas to transmit and / or receive directional radio signals (e.g., beams). Similarly, BS 102 may also include any number of antennas and may be configured to use the antennas to transmit and / or receive directional radio signals (e.g., beams). To receive and / or transmit such directional signals, the antennas of UE 106 and / or BS 102 may be configured to apply different “weights” to different antennas. The process of applying these different weights may be referred to as “pre-decoding”.

[0053] In some implementations, UE 106 may include independent transmit and / or receive chains (e.g., including independent antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communication using either LTE or NR, and components for communication using Wi-Fi and Bluetooth. ™ Each component communicates with its own independent radio unit. Other configurations are also possible.

[0054] Figure 3 — Block diagram of an exemplary UE device

[0055] Figure 3A block diagram of an exemplary UE 106 according to some embodiments is shown. As shown, UE 106 may include a system-on-chip (SOC) 300, which may include portions for various purposes. Some or all of the various illustrated components (and / or other device components not shown, e.g., in variants and alternative arrangements) may be “communically coupled” or “operationally coupled”, terms which may be used herein to refer to components that can communicate directly or indirectly when the device is in operation.

[0056] As shown in the figure, SOC 300 may include display circuitry 304 and one or more processors 302. The display circuitry performs graphics processing and provides display signals to a display 360, while the processors execute program instructions for UE 106. SOC 300 may also include sensor circuitry 370, which may include components for sensing or measuring any of the various possible characteristics or parameters of UE 106. For example, sensor circuitry 370 may include motion sensing circuitry configured to detect motion of UE 106, for example, using a gyroscope, accelerometer, and / or any of various other motion sensing components. Alternatively, sensor circuitry 370 may include one or more temperature sensing components, for example, for measuring the temperature of each of one or more antenna panels and / or other components of UE 106. As needed, any of the various other possible types of sensor circuitry may also or alternatively be included in UE 106. Processor 302 may also be coupled to memory management unit (MMU) 340, which may be configured to receive addresses from processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310) and / or other circuitry or devices, such as display circuitry 304, radio components 330, connector I / F 320, and / or display 360. MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, MMU 340 may be included as part of processor 302.

[0057] As shown in the figure, the SOC 300 can be coupled to various other circuits of the UE 106. For example, the UE 106 may include various types of memory (e.g., including NAND flash memory 310), connector interface 320 (e.g., for coupling to computer systems, docking stations, charging stations, etc.), display 360, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, Bluetooth). ™(e.g., Wi-Fi, GPS, etc.). UE device 106 may include or be coupled to at least one antenna (e.g., 335a), and may include multiple antennas (e.g., shown by antennas 335a and 335b) for performing wireless communication with a base station and / or other devices. Antennas 335a and 335b are shown by way of example, and UE device 106 may include fewer or more antennas. Generally, one or more antennas are collectively referred to as antenna 335. For example, UE device 106 may use antenna 335 to perform wireless communication via radio circuitry 330. The communication circuitry may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration. As indicated above, in some embodiments, the UE may be configured to use multiple wireless communication standards for wireless communication.

[0058] UE 106 may include hardware and software components, such as those described further herein, for implementing methods for handling lower-layer triggered mobility configuration failures in a wireless communication system. The processor 302 of UE device 106 may be configured to implement some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). In other embodiments, processor 302 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or configured as an ASIC (Application-Specific Integrated Circuit). Furthermore, as... Figure 3 As shown, processor 302 may be coupled to and / or interoperable with other components to perform techniques for handling lower-layer triggered mobility configuration failures in a wireless communication system, according to various embodiments disclosed herein. Processor 302 may also implement various other applications and / or end-user applications running on UE 106.

[0059] In some implementations, radio component 330 may include a separate controller dedicated to controlling communications for various corresponding RAT standards. For example, such as Figure 3 As shown, the radio component 330 may include a Wi-Fi controller 352, a cellular controller (e.g., an LTE and / or LTE-A controller) 354, and Bluetooth. ™ Controller 356, and in at least some embodiments, one or more of these controllers may be implemented as corresponding integrated circuits (referred to as ICs or chips), which communicate with each other and with the SOC 300 (and more specifically, with the processor 302). For example, the Wi-Fi controller 352 may communicate with the cellular controller 354 via a cell-ISM link or a WCI interface, and / or Bluetooth. ™Controller 356 can communicate with cellular controller 354 via a cell-ISM link or the like. Although three separate controllers are shown within radio component 330, other implementations with fewer or more similar controllers for various different RATs can be implemented in UE device 106.

[0060] Furthermore, implementations in which the controller can perform functionality associated with a variety of radio access technologies are envisioned. For example, according to some implementations, in addition to hardware and / or software components for performing cellular communications, the cellular controller 354 may also include hardware and / or software components for performing one or more activities associated with Wi-Fi, such as Wi-Fi preamble detection, and / or the generation and transmission of Wi-Fi physical layer preamble signals.

[0061] Figure 4 — Block diagram of an exemplary base station

[0062] Figure 4 A block diagram of an exemplary base station 102 according to some implementation schemes is shown. It should be noted that... Figure 4 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include processor 404, which executes program instructions for base station 102. Processor 404 may also be coupled to memory management unit (MMU) 440, which may be configured to receive addresses from processor 404 and translate these addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450), or to other circuitry or devices.

[0063] Base station 102 may include at least one network port 470. Network port 470 may be configured to be coupled to a telephone network and provide access to multiple devices, such as UE device 106, as described above. Figure 1 and Figure 2 Access to the telephone network described herein. Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 470 may be coupled to the telephone network via the core network, and / or the core network may provide the telephone network (e.g., between other UE devices served by the cellular service provider).

[0064] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or "gNB". In such implementations, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transmit and receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0065] Base station 102 may include at least one antenna 434, and may include multiple antennas. Antenna 434 may be configured to operate as a wireless transceiver and may also be configured to communicate with UE device 106 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio component 430 may be designed to communicate via various wireless telecommunication standards, including but not limited to 5G NR, 5G NR SAT, LTE, LTE-A, Wi-Fi, etc.

[0066] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some instances, base station 102 may include multiple radio components that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, 5G NR SAT and Wi-Fi, LTE and Wi-Fi, etc.).

[0067] As further described herein, BS 102 may include hardware and software components for implementing or supporting specific implementations of the features described herein. The processor 404 of base station 102 may be configured, for example, to implement and / or support specific implementations of the methods described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 404 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. In the case of certain RATs (e.g., Wi-Fi), base station 102 may be designed as an access point (AP), in which case network port 470 may be implemented to provide access to a wide area network and / or one or more local area networks; for example, it may include at least one Ethernet port, and radio component 430 may be designed to communicate according to the Wi-Fi standard.

[0068] Furthermore, as described herein, processor 404 may include one or more processing elements. Therefore, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 404.

[0069] Furthermore, as described herein, radio component 430 may include one or more processing elements. Therefore, radio component 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio component 430. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio component 430.

[0070] Figure 5 - Handling of lower-level triggered mobility configuration failures

[0071] To support low-latency and high-reliability mobile services, the importance of being able to rapidly shift cells as needed to maintain service quality is increasing. According to some implementations, technologies for achieving such cell shifts via lower-layer signaling (such as 3GPP Release 18 LTM (“Lower-Layer Triggered Mobility” or “Layer 1 (L1) Layer 2 (L2) Triggered Mobility”) are under development and are expected to reduce latency and improve the reliability of at least some radio devices.

[0072] One aspect of supporting LTM handover may include providing LTM configuration information via Radio Resource Control (RRC) signaling prior to a potential LTM handover. Such configuration may include cell configuration information indicating one or more candidate cells to which a radio device may be directed to perform an LTM handover. Therefore, another aspect of supporting LTM handover may include determining whether the cell configuration information indicated for LTM candidate cells for a given radio device is valid for the radio device, including possible scenarios where one or more LTM candidate cell configurations are invalid for the radio device. In various implementations, there may be multiple ways to perform this operation.

[0073] Therefore, specifying techniques for handling lower-level triggered mobility configuration verification (including for handling configuration failure scenarios) may be beneficial. To illustrate a set of such possible techniques, Figure 5 A flowchart is provided to illustrate a method for processing lower-layer triggered mobility configuration verification in a wireless communication system, according to at least some embodiments.

[0074] Figure 5 The aspects of the method can be implemented by a wireless device, for example, in conjunction with one or more cellular base stations (such as UE 106 and BS 102 shown and described with respect to the various figures herein), or more generally, in conjunction as needed with any of the computer circuits, systems, devices, elements, or components shown in the aforementioned figures. For example, the processor (and / or other hardware) of such a device can be configured to cause the device to perform any combination of the illustrated method elements and / or other method elements.

[0075] It should be noted that, although described in a manner involving the use of communication technologies and / or features associated with 3GPP and / or NR specification documents Figure 5 This method describes at least some elements, but this description is not intended to limit this disclosure and can be used in any suitable wireless communication system as needed. Figure 5 The method encompasses various aspects. In various implementation schemes, some elements of the method shown may be executed simultaneously in a different order than those shown, may be replaced by other method elements, or may be omitted. Additional method elements may also be executed as needed. As shown in the figure, Figure 5 The method can be operated as follows.

[0076] In section 502, a wireless device can establish a radio link with a cellular base station. According to some implementations, the radio link may include a 5G NR-based cellular link. For example, the wireless device may establish a session with an AMF entity of the cellular network via one or more gNBs that provide radio access to the cellular network. Alternatively, the radio link may include an LTE-based cellular link. For example, the wireless device may establish a session with a mobility management entity of the cellular network via an eNB that provides radio access to the cellular network. Other types of cellular links are also possible according to various implementations, and the cellular network may also, or alternatively, operate according to another cellular communication technology.

[0077] Establishing a radio link may include, at least according to some implementation schemes, establishing an RRC connection with a serving cellular base station. Establishing a first RRC connection may include configuring various parameters for communication between the radio device and the cellular base station, establishing context information for the radio device, and / or any of various other possible characteristics, such as establishing an air interface for the radio device to communicate with a cellular network associated with the cellular base station. After establishing an RRC connection, the radio device may operate in an RRC connected state. In some instances, the RRC connection may also be released (e.g., after a period of inactivity relative to data communication), in which case the radio device may operate in an RRC idle state or an RRC inactive state. In some instances, for example due to radio device mobility, changed radio medium conditions, and / or any other possible reasons, the radio device may perform a handover (e.g., when in RRC connected mode) or cell reselection (e.g., when in RRC idle mode or RRC inactive mode) to a new serving cell.

[0078] According to at least some implementations, a wireless device can establish multiple wireless links with multiple TRPs in a cellular network, for example, based on a multi-TRP configuration. In this case, the wireless device can be configured (e.g., via RRC signaling) to have one or more Transmission Control Indicators (TCIs), which may correspond to various beams available for communication with the TRPs. Alternatively, it may be possible that one or more configured TCI states can be activated at a specific time by the wireless device's Media Access Control (MAC) control element (CE).

[0079] In at least some instances, establishing a wireless link may include the wireless device providing information about its capabilities. This capability information may include information related to any one of several types of wireless device capabilities.

[0080] In 504, the radio device may receive LTM configuration information. The LTM configuration information may be provided via RRC signaling, for example, in an RRC reconfiguration message along with other (e.g., non-LTM) RRC configuration information. The LTM configuration information may include information indicating the configuration of one or more LTM candidate cells. In some implementations, this may include providing a reference configuration along with a list of LTM candidate cells and incremental configuration information for each such cell. In this scenario, the radio device can derive the LTM candidate cell configuration for each of these cells by applying the incremental configuration information to the reference configuration information. Other ways of providing the LTM candidate cell configuration are also possible, such as by providing complete configuration information for each LTM candidate cell.

[0081] In 506, the radio device can evaluate the LTM candidate cell configuration for validity. This may include checking whether the cell configuration for the LTM candidate cell (e.g., in some implementations, as derived from a reference configuration) is within the capabilities of the radio device, and various other possible aspects. In some implementations, a validation check may be performed on the LTM candidate configuration derived from the LTM configuration information of the LTM candidate cell (e.g., applied only to the serving cell), for example, such that the LTM candidate configuration derived from the LTM configuration information is not used to check the configuration for the secondary cell used for carrier aggregation (CA) or dual connectivity (DC) configurations. In this scenario, it may be assumed that the CA or DC configuration is applied from the current configuration (e.g., the reference configuration may not include a CA configuration). As another possibility, it is possible to perform a validation check on the LTM candidate configuration (e.g., applied to the entire CA / DC configuration), where the current CA / DC configuration is transferred to the target LTM candidate configuration.

[0082] In 508, the radio device may provide the cellular base station with an indication of whether the LTM candidate cell configuration is valid. In some implementations, the radio device may also provide the cellular base station with an indication confirming that the radio device has applied non-LTM configuration information. According to various implementations, it is possible that the indication of whether the LTM candidate cell configuration is valid is provided in the same transaction as the indication confirming that the radio device has applied non-LTM configuration information, or that these indications are provided in different transactions (e.g., and may be sent at different times).

[0083] For scenarios where the indication of whether the LTM candidate cell configuration is valid is provided in the same transaction as the indication confirming that the radio device has applied non-LTM configuration information, it is possible that, for example, the cellular base station provides increased RRC processing time compared to a scenario where no LTM candidate cell configuration is provided. For example, the cellular base station may select a timer value for the radio device's response to the RRC configuration information based at least in part on whether the RRC configuration information includes LTM configuration information, where the timer value may be longer when the RRC configuration information includes LTM configuration information compared to when the RRC configuration information does not. If the radio device determines that all LTM configuration information is valid, it is possible that the radio device responds to the RRC configuration information using an RRC configuration complete message, and the indication of whether the LTM candidate cell configuration is valid for the radio device may be included in the RRC configuration complete message.

[0084] If the radio device determines that the LTM configuration information is not entirely valid (e.g., at least one LTM candidate cell configuration is invalid for the radio device), it is possible that the radio device releases the RRC connection and sends an RRC reconstruction message due to the configuration failure. In this scenario, an indication of whether the LTM candidate cell configuration is valid for the radio device can be included in the RRC reconstruction message. Alternatively, the radio device may report the LTM configuration failure without releasing the RRC connection. For example, if the radio device determines that the LTM configuration information is not entirely valid, it is possible that the radio device responds to the RRC configuration information with an RRC configuration completion message, which may indicate that at least one LTM candidate cell configuration is invalid for the radio device. When at least one LTM candidate cell configuration is invalid for the radio device, it is possible that failure reason information is provided to the cellular base station, indicating that at least one LTM candidate cell configuration is invalid for the radio device, and may include information specifically indicating one or more LTM candidate cells on which an LTM configuration failure has occurred. It should be noted that this failure reason information may be provided in either a scenario in which the radio device releases the RRC connection or in a scenario in which the radio device reports that at least one LTM candidate cell configuration is invalid for the radio device without releasing the RRC connection, or both scenarios.

[0085] In a scenario where the indication of whether the LTM candidate cell configuration is valid is provided in a different transaction than the indication confirming that the radio device has applied non-LTM configuration information, the radio device may send a first RRC configuration complete message to the cellular base station in response to RRC configuration information. The first RRC configuration complete message may indicate that the radio device has applied non-LTM configuration information from the RRC configuration information. In this scenario, it is possible that the cellular base station selects the same timer value used by the radio device to provide the first RRC configuration complete message in response to the RRC configuration information, regardless of whether the LTM configuration information is included in the RRC configuration information. If the radio device determines that all LTM configuration information is valid, it is possible that the radio device (e.g., at a later time, due to the processing time used to evaluate the validity of the LTM configuration information) responds to the RRC configuration information again with a second RRC configuration complete message, and the indication of whether the LTM candidate cell configuration is valid for the radio device may be included in the second RRC configuration complete message. It is possible that, for example, the cellular base station provides an increased RRC processing time for the second RRC configuration complete message compared to the processing time provided for the first RRC configuration complete message. For example, the cellular base station may select a timer value associated with acknowledging the LTM configuration information for the wireless device to send a second RRC configuration completion message, wherein the timer value associated with acknowledging the LTM configuration information may be longer than the timer value selected for the first response to the RRC configuration information. Alternatively, it may be possible that there are no explicit processing time constraints for evaluating the validity of the LTM configuration information.

[0086] If the radio device determines that the LTM configuration information is not entirely valid (e.g., at least one LTM candidate cell configuration is invalid for the radio device), it is possible that the radio device releases the RRC connection and sends an RRC reconstruction message due to the configuration failure. In this scenario, an indication of whether the LTM candidate cell configuration is valid for the radio device can be included in the RRC reconstruction message. Alternatively, the radio device may report the LTM configuration failure without releasing the RRC connection. For example, if the radio device determines that the LTM configuration information is not entirely valid, it is possible that the radio device responds to the RRC configuration information with a second RRC configuration completion message, which may indicate that at least one LTM candidate cell configuration is invalid for the radio device. When at least one LTM candidate cell configuration is invalid for the radio device, it is possible that failure reason information is provided to the cellular base station, indicating that at least one LTM candidate cell configuration is invalid for the radio device, and may include information specifically indicating one or more LTM candidate cells on which an LTM configuration failure has occurred. It should be noted that this failure reason information may be provided in either a scenario in which the radio device releases the RRC connection or in a scenario in which the radio device reports that at least one LTM candidate cell configuration is invalid for the radio device without releasing the RRC connection, or both scenarios.

[0087] It should be noted that in scenarios where a second RRC configuration completion message is provided from the radio device to the cellular base station (e.g., to confirm the validity of LTM configuration information or to report that one or more LTM cell configurations are invalid for the radio device without releasing the RRC connection), it is possible that the second RRC configuration completion message uses the same transaction identifier (e.g., RRC-TransactionIdentifier ID) as the first RRC configuration completion message. This use of the same transaction identifier may indicate to the cellular base station that a second RRC configuration completion message is also provided in response to RRC configuration information and / or that the second RRC configuration completion message is used to indicate whether the LTM candidate cell configuration is valid for the radio device. Alternatively (e.g., if a different transaction identifier is used) or further, it is possible that additional signaling may be provided along with the second RRC configuration completion message to indicate that the second RRC configuration completion message is used for LTM configuration confirmation.

[0088] In some implementations, it is possible that the cellular base station will not use additional LTM configuration information to reconfigure the radio device before receiving an LTM configuration information acknowledgment from the radio device. In a multi-transaction framework, it is possible that the cellular base station may reconfigure non-LTM configuration parameters before receiving a second RRC configuration complete message, or it is possible that the cellular base station will not use any additional RRC configuration information to reconfigure the radio device before receiving an LTM configuration information acknowledgment from the radio device.

[0089] Therefore, at least according to some implementation schemes, Figure 5 The method can be used to provide a framework for handling LTM configuration verification, including handling LTM configuration failure scenarios, which can help improve the ability of cellular networks to provide low-latency and high-reliability mobile services, and in at least some cases, other potential benefits.

[0090] Figures 6 to 11 and additional information

[0091] Figures 6 to 11 It shows that it can be used with, if needed. Figure 5 Another aspect of using this method. However, it should be noted that, in Figures 6 to 11 The exemplary details shown and described with respect to these figures are not intended to limit this disclosure as a whole: many variations and alternatives to the details provided herein are possible and should be considered within the scope of this disclosure.

[0092] 3GPP objectives for mobility enhancement may include introducing and extending mechanisms and processes for inter-cell mobility in Layer 1 (L1) and Layer 2 (L2) environments, for example, to provide reduced mobility latency compared to RRC / Layer 3 (L3) based mobility technologies.

[0093] In this type of lower-layer triggered mobility (LTM) handover (HO), it is possible that the centralized cell (CU) will still be the control node even when the distributed cell (DU) triggers the HO. In some implementations, media access control (MAC) control element (CE) signaling can be used to trigger the HO. The MAC CE may contain target cell configuration information for reference. The UE may have multiple candidate configurations (e.g., provided via RRC signaling). There are several possibilities regarding how and when the UE verifies these configurations (e.g., during the time of receiving RRC configuration information for LTM handover or during the LTM MAC CE reception).

[0094] It is possible that when a UE is configured with a candidate LTM configuration, there may be situations where the UE cannot follow the configuration or at least some parts thereof (e.g., due to a mismatch between UE capabilities and configuration parameters). Notifying the network when this occurs may be important for effective operation, but performing such verification can be time-consuming, and there may potentially be many candidate configurations to be verified. Therefore, providing techniques to support such LTM candidate configuration verification and to report any errors or problems detected with LTM candidate configurations based on this verification may be useful. Depending on various implementations, aspects that could potentially improve the efficiency and effectiveness of the RRC process may include any or all of the following: whether an invalid LTM candidate configuration is considered a failure condition; whether a UE detecting an invalid LTM candidate configuration should release its current connection; whether the UE can perform such verification and reporting in the background; how the UE processing time used to perform LTM candidate configuration verification is accounted for; and what actions the network can and cannot perform given the UE's LTM candidate configuration verification activity; and other possible considerations.

[0095] Figures 6 to 11 A signal flow diagram is provided to illustrate example aspects of various possible methods for handling such considerations, etc., according to various implementation schemes. Figure 6 In particular, aspects of a scenario in which LTM candidate configurations are evaluated and responded to in the same transaction as any other RRC configuration information provided in the RRC reconfiguration message are illustrated.

[0096] As shown in the figure, in 606, gNB 604 can provide RRCReconfiguration messages to UE 602. RRCReconfiguration messages may include LTM candidate cell configuration information, such as a reference configuration and a list of LTM candidate cells, as well as incremental configuration information for deriving the LTM candidate configuration for each LTM candidate cell. RRCReconfiguration messages may also potentially include other RRC configuration information (e.g., related to the current RRC configuration for UE 602 and the serving cell provided by gNB 604).

[0097] In 608, the UE can verify configuration information for the current cell and also verify each LTM candidate configuration in the LTM candidate configurations. In some implementations, the UE can evaluate LTM candidate configurations derived from a reference configuration (e.g., for each LTM candidate cell) without checking the current configuration. In some implementations, the UE can evaluate LTM candidate configurations derived from the reference configuration for each LTM candidate cell only for the serving cell. In this scenario, it can be assumed that a Carrier Glass Aggregation (CA) or Dual Connectivity (DC) configuration is applied from the current configuration (e.g., the reference configuration may not include CA / DC configuration).

[0098] In 610, if the UE cannot follow at least one of the candidate configurations, the UE may consider the LTM configuration to have failed and trigger an RRC rebuild. In 612, the UE 602 may continue to send an RRCReestablishment message to the gNB 604. The RRCReestablishment message may include failure reason information. In some cases, the failure may be reported using reason information indicating a reconfigurationFailure, and the UE 602 may release the configuration and apply the default configuration for RRC rebuild (e.g., similar to techniques used to handle RRC reconfiguration failures unrelated to LTM configuration failures). Alternatively, the failure may be reported using new reason information (e.g., as a possibility, indicating ltm-config-failure), and the UE 602 may release the configuration and apply the default configuration for RRC rebuild. In some cases, additional information may be provided to indicate which candidate cell(s) the failure occurred for.

[0099] exist Figure 6 In this scenario, the network may wait for confirmation from the UE before attempting further reconfiguration, possibly using a different timer than that used for RRC reconfiguration without LTM configuration information, to determine how long to wait for the confirmation before determining that the RRC reconfiguration has failed. In other words, gNB 604 may give UE 602 additional RRC processing time to perform LTM candidate configuration verification. The timer used to respond to the RRCReconfiguration message may have a fixed value, or may depend at least in part on the amount of LTM candidate configuration information provided, and various other possibilities.

[0100] It should be noted that in alternative scenarios where UE 602 verifies all LTM candidate configurations, at least in some implementations, it is possible that the UE provides an RRCReconfigurationComplete message to gNB 604 in response to the RRCReconfiguration message, instead of performing an RRC reconstruction.

[0101] Figure 7This illustrates various aspects of a scenario where LTM candidate configurations are evaluated and responded to in a separate transaction from non-LTM configuration information. As shown in Figure 706, gNB 704 can provide an RRCReconfiguration message to UE 702. The RRCReconfiguration message may include LTM candidate cell configuration information, such as a reference configuration and a list of LTM candidate cells, as well as incremental configuration information for deriving the LTM candidate configuration for each LTM candidate cell. The RRCReconfiguration message may also potentially include other RRC configuration information (e.g., related to the current RRC configuration for UE 702 and the serving cell provided by gNB 704).

[0102] In 708, UE 702 can apply any non-LTM configuration element from RRC reconfiguration information.

[0103] In 710, UE 702 can provide an RRCReconfigurationComplete message to gNB 704. UE 702 can send this message without performing verification on any LTM configuration information provided by gNB 704; such verification can be deferred. In this scenario, it is possible that gNB 704 uses the same timer as for RRC reconfiguration without LTM configuration information to determine how long to wait for this confirmation before determining that the RRC reconfiguration has failed.

[0104] In 712, the network may assume that UE 702 has deferred the application of the LTM configuration, and that, for other aspects, UE 702 has applied the configuration. In 714, UE 702 may perform verification of the LTM candidate configuration. In some implementations, the UE may evaluate LTM candidate configurations derived from a reference configuration (e.g., for each LTM candidate cell) and not check the current configuration. In some implementations, the UE may evaluate LTM candidate configurations derived from the reference configuration for each LTM candidate cell only. In this scenario, it may be assumed that CA or DC configurations are applied from the current configuration (e.g., the reference configuration may not include CA / DC configurations).

[0105] In 716, if the UE cannot follow at least one of the candidate configurations, the UE may consider the LTM configuration to have failed and trigger an RRC rebuild. In 718, the UE 702 may continue to send an RRCReestablishment message to the gNB 704. The RRCReestablishment message may include failure reason information. In some cases, the failure may be reported using reason information indicating a reconfigurationFailure, and the UE 702 may release the configuration and apply the default configuration for RRC rebuild (e.g., similar to techniques used to handle RRC reconfiguration failures unrelated to LTM configuration failures). Alternatively, the failure may be reported using new reason information (e.g., as a possibility, indicating ltm-config-failure), and the UE 702 may release the configuration and apply the default configuration for RRC rebuild. In some cases, additional information may be provided to indicate which candidate cell(s) the failure occurred for.

[0106] exist Figure 7 In this scenario, at least for non-LTM configurations, the network does not need to wait for confirmation of successful LTM configuration verification from UE 702 before attempting further reconfiguration. Alternatively, it is possible that the network does need to wait for a response from UE 702 regarding LTM configuration information before performing any further RRC reconfiguration. In either case, there may be no explicit processing time constraints (e.g., no timer for providing a second RRCReconfigurationComplete message to confirm verification of the LTM configuration). Therefore, in Figure 7 In this scenario, gNB 704 can also provide UE 702 with additional RRC processing time to perform LTM candidate configuration verification.

[0107] Figure 8 This illustrates aspects of a scenario where LTM candidate configurations are evaluated and responded to in a separate transaction from non-LTM configuration information, a scenario similar to... Figure 7 In some scenarios, successful LTM configuration verification exists. As shown in the figure, in 806, gNB 804 can provide RRCReconfiguration messages to UE 802. The RRCReconfiguration message may include LTM candidate cell configuration information, and may also include other RRC configuration information.

[0108] In 808, UE 802 can apply any non-LTM configuration element from the RRC reconfiguration information. In 810, UE 802 can provide an RRCReconfigurationComplete message to gNB 804, for example, to confirm that UE 802 has applied the non-LTM configuration portion from the RRC reconfiguration information.

[0109] In 812, the network may assume that UE 802 has deferred the application of the LTM configuration, and that, for other reasons, UE 802 has already applied the configuration. Therefore, it is possible that gNB 804 can provide further non-LTM reconfiguration, but cannot perform further LTM reconfiguration until it receives confirmation of the most recent LTM configuration. Alternatively, it is possible that the network needs to wait for UE 802 to respond with LTM configuration information before performing any further RRC reconfiguration (e.g., including non-LTM configuration).

[0110] In step 814, UE 802 can perform verification of the LTM candidate configuration. In step 816, the UE can successfully verify the LTM configuration. In step 818, UE 802 can continue to send another RRCReconfigurationComplete message to gNB 804. The second RRCReconfigurationComplete message 818 may include the same RRC-TransactionIdentifier ID as the previous RRCReconfigurationComplete message 810, for example, enabling gNB 804 to determine that this message is used to confirm the LTM configuration portion of RRCReconfiguration message 806. Alternatively, a new transaction identifier may be used, and additional signaling may be used to indicate that the message is used to confirm the LTM configuration. Note that in Figure 8 In such scenarios, there may be no explicit processing time constraints (e.g., no timer for providing a second RRCReconfigurationComplete message 818 to confirm the verification of the LTM configuration).

[0111] Figure 9 It shows something similar to Figure 8 The scenario covers various aspects, but with additional RRC processing time requirements. As shown in the figure, in 906, gNB 904 can provide RRCReconfiguration messages to UE 902. The RRCReconfiguration message may include LTM candidate cell configuration information, and may also include other RRC configuration information.

[0112] In 908, UE 902 can apply any non-LTM configuration element from the RRC reconfiguration information. In 910, UE 902 can provide an RRCReconfigurationComplete message to gNB 904, for example, to confirm that UE 902 has applied the non-LTM configuration portion from the RRC reconfiguration information.

[0113] In 912, the network may assume that UE 902 has deferred the application of the LTM configuration, and that, in other respects, UE 902 has applied the configuration. Therefore, it is possible that gNB 904 can provide further non-LTM reconfiguration, but cannot perform further LTM reconfiguration until it receives confirmation of the most recent LTM configuration. Alternatively, it is possible that the network needs to wait for UE 902 to respond with LTM configuration information before performing any further RRC reconfiguration (e.g., including non-LTM configuration).

[0114] In 914, UE 902 can perform verification of the LTM candidate configuration. In 916, the UE can successfully verify the LTM configuration. In 918, UE 902 can continue to send another RRCReconfigurationComplete message to gNB 904. The same RRC-TransactionIdentifier ID can be used, or a new transaction identifier can be used with additional signaling included to indicate that the message is used to confirm the LTM configuration.

[0115] As shown in the figure, with Figure 8 In contrast to the previous scenario, new processing time constraints can be implemented to complete the verification of the LTM configuration. For example, a timer can be defined and used to limit the amount of time that the UE 902 has to confirm the verification of the LTM configuration by providing a second RRCReconfigurationComplete message 918, or if the gNB 902 determines that the LTM configuration has failed. The timer used for LTM configuration confirmation can have a fixed value, or it can depend at least in part on the amount of LTM candidate configuration information provided, and various other possibilities.

[0116] As previously noted, it is possible that when LTM authentication fails, the UE releases the link and performs RRC reconstruction, for example, as in Figures 6 to 7 In such scenarios, it is also possible that when LTM verification fails, as long as the failure is only for the LTM configuration, the UE can maintain its current link and report using a new RRC message or use an existing RRC reconfiguration completion message with new information about the failure.

[0117] Figure 10An example aspect of this scenario is illustrated where LTM candidate configurations are evaluated and responded to within the same transaction as non-LTM configuration information. As shown in Figure 1006, gNB 1004 may provide an RRCReconfiguration message to UE 1002. The RRCReconfiguration message may include LTM candidate cell configuration information, such as a reference configuration and a list of LTM candidate cells, as well as incremental configuration information for deriving the LTM candidate configuration for each LTM candidate cell. The RRCReconfiguration message may also potentially include other RRC configuration information (e.g., related to the current RRC configuration for UE 1002 and the serving cell provided by gNB 1004).

[0118] In 1008, the UE can verify the configuration information for the current cell, as well as each LTM candidate configuration in the LTM candidate configuration list, and can determine if the UE cannot follow the LTM configuration. In 1010, even if the UE cannot follow at least one candidate configuration, the UE may not rebuild the current link, but instead may report the LTM configuration failure using new information in a new RRC message or an RRCReconfigurationComplete message.

[0119] In 1012, UE 1002 can continue to send a new RRC message or an RRCReconfigurationComplete message with new information to gNB 1004. The new RRC message or RRCReconfigurationComplete message may include failure reason information, which indicates that LTM verification failed, and may indicate which candidate cell(s) LTM verification failed.

[0120] exist Figure 10 In this scenario, the network may wait for confirmation from the UE before attempting further reconfiguration, possibly using a different timer than that used for RRC reconfiguration without LTM configuration information, to determine how long to wait for the confirmation before determining that the RRC reconfiguration has failed. In other words, gNB 1004 may give UE 1002 additional RRC processing time to perform LTM candidate configuration verification. The timer used to respond to the RRCReconfiguration message may have a fixed value, or may depend at least in part on the amount of LTM candidate configuration information provided, and various other possibilities.

[0121] Figure 11This illustrates aspects of another scenario where LTM candidate configurations are evaluated and responded to in a separate transaction from non-LTM configuration information, in which the current link can be maintained even if LTM verification fails. As shown in Figure 1106, gNB 1104 can provide an RRCReconfiguration message to UE 1102. The RRCReconfiguration message may include LTM candidate cell configuration information and may also include other RRC configuration information.

[0122] In 1108, UE 1102 can apply any non-LTM configuration element from the RRC reconfiguration information. In 1110, UE 1102 can provide an RRCReconfigurationComplete message to gNB 1104, for example, to confirm that UE 1102 has applied the non-LTM configuration portion from the RRC reconfiguration information.

[0123] In 1112, the network may assume that UE 1102 has postponed the application of the LTM configuration, and that, in other respects, UE 1102 has applied the configuration. Therefore, it is possible that gNB 1104 can provide further non-LTM reconfiguration, but cannot perform further LTM reconfiguration until it receives confirmation of the most recent LTM configuration. Alternatively, it is possible that the network needs to wait for UE 1102 to respond with LTM configuration information before performing any further RRC reconfiguration (e.g., including non-LTM configuration).

[0124] In step 1114, UE 1102 can verify the LTM candidate configuration and determine if the UE cannot follow the LTM configuration. In step 1116, even if the UE cannot follow at least one of the candidate configurations, the UE may not rebuild the current link, but instead may report the LTM configuration failure using new information in a new RRC message or an RRCReconfigurationComplete message. In step 1118, UE 1102 may continue to send a new RRC message or an RRCReconfigurationComplete message with new information to gNB 1104. The new RRC message or RRCReconfigurationComplete message may include failure reason information indicating that the LTM verification failed, and may indicate for which candidate cell(s) the LTM verification failure occurred.

[0125] for Figures 11 to 1In scenario 2 and / or for other implementations where the current link can be maintained in the event of an LTM authentication failure, it is possible that the UE does not save any LTM configuration information after an LTM configuration failure. In this case, the network may need to provide complete LTM configuration information again (e.g., possibly including reference configuration information). Alternatively, in some implementations, the UE does not simply save the LTM configuration information of the reported "index" in the event of its failure. In this case, the network may only need to provide that specific LTM configuration information again.

[0126] Further exemplary implementations are provided below.

[0127] One set of implementations may include a method comprising: a radio device receiving radio resource control (RRC) configuration information, the RRC configuration information including LTM configuration information indicating one or more lower-layer triggered mobility (LTM) candidate cell configurations; evaluating whether the LTM candidate cell configuration is valid for the radio device; and sending an indication of whether the LTM candidate cell configuration is valid for the radio device.

[0128] According to some implementations, the indication indicates that at least one LTM candidate cell configuration is invalid for the radio device by using failure reason information provided by the radio device in the RRC reconstruction message.

[0129] According to some implementations, this indication is sent via an RRC configuration complete message to indicate that at least one LTM candidate cell configuration is invalid for the radio device.

[0130] According to some implementations, the method also includes the wireless device sending an indication of one or more LTM candidate cells on which LTM configuration failure has occurred.

[0131] According to some implementations, the method further includes the wireless device: sending a first RRC configuration complete message to a cellular base station in response to the RRC configuration information, wherein the first RRC configuration complete message indicates that the wireless device has applied non-LTM configuration information from the RRC configuration information; and sending a second RRC configuration complete message to the cellular base station in response to the RRC configuration information, wherein the second RRC configuration complete message indicates whether the LTM candidate cell configuration is valid for the wireless device.

[0132] According to some implementation schemes, the second RRC configuration completion message includes information indicating that the second RRC configuration completion message is used for LTM configuration confirmation.

[0133] According to some implementations, the method further includes the wireless device sending an RRC configuration complete message to the cellular base station in response to the RRC configuration information, wherein the RRC configuration complete message indicates that the wireless device has applied non-LTM configuration information from the RRC configuration information, and also indicates whether the LTM candidate cell configuration is valid for the wireless device.

[0134] According to some implementation schemes, evaluating whether the LTM candidate cell configuration is effective for the radio device includes evaluating the LTM candidate configurations for all LTM candidate cells derived from the LTM configuration information.

[0135] According to some implementation schemes, evaluating whether the LTM candidate cell configuration is effective for the radio device includes evaluating the LTM candidate configuration derived from the LTM configuration information that is only for the serving cell LTM candidate cell.

[0136] Another set of embodiments may include an apparatus comprising a processor configured to cause a wireless device to perform the steps of the method according to any one of the foregoing examples.

[0137] Another set of embodiments may include a wireless device comprising: an antenna; a radio component operatively coupled to the antenna; and one or more processors operatively coupled to the radio component; wherein the wireless device is configured to perform the steps of the method according to any one of the foregoing examples.

[0138] Another set of implementations may include a method comprising: a cellular base station: transmitting Radio Resource Control (RRC) configuration information, the RRC configuration information including LTM configuration information indicating one or more lower-layer triggered mobility (LTM) candidate cell configurations; and receiving an indication of whether the LTM candidate cell configuration is valid for the radio device.

[0139] According to some implementations, the indication indicates that at least one LTM candidate cell configuration is invalid for the radio device by using failure reason information provided by the radio device in the RRC reconstruction message.

[0140] According to some implementations, this indication is sent via an RRC configuration complete message to indicate that at least one LTM candidate cell configuration is invalid for the radio device.

[0141] According to some implementations, the method also includes the cellular base station receiving an indication of one or more LTM candidate cells on which LTM configuration failure has occurred.

[0142] According to some implementations, the method further includes the cellular base station: receiving a first RRC configuration complete message from the radio device in response to the RRC configuration information, wherein the first RRC configuration complete message indicates that the radio device has applied non-LTM configuration information from the RRC configuration information; and receiving a second RRC configuration complete message from the radio device in response to the RRC configuration information, wherein the second RRC configuration complete message indicates whether the LTM candidate cell configuration is valid for the radio device.

[0143] According to some implementation schemes, the second RRC configuration completion message includes information indicating that the second RRC configuration completion message is used for LTM configuration confirmation.

[0144] According to some implementations, the method further includes the cellular base station receiving an RRC configuration complete message from the radio device in response to the RRC configuration information, wherein the RRC configuration complete message indicates that the radio device has applied non-LTM configuration information from the RRC configuration information, and also indicates whether the LTM candidate cell configuration is valid for the radio device.

[0145] According to some implementations, the method also includes the cellular base station selecting one or more timer values ​​for the wireless device to respond to the RRC configuration information, at least in part based on the RRC configuration information including LTM configuration information.

[0146] Another set of embodiments may include a cellular base station comprising: one or more processors; and a memory having instructions stored thereon that, when executed by the one or more processors, perform the steps of the method according to any one of the foregoing examples.

[0147] Further exemplary implementations may include a method comprising: performing any or all of the foregoing examples by a wireless device.

[0148] Another exemplary embodiment may include a device comprising: an antenna; a radio component coupled to the antenna; and a processor operatively coupled to the radio component, wherein the device is configured to implement any or all of the foregoing examples.

[0149] Another set of exemplary embodiments may include a non-transitory computer-accessible memory medium that includes program instructions that, when executed at the device, cause the device to implement any or all of the foregoing examples.

[0150] Another set of exemplary embodiments may include a computer program that includes instructions for performing any or all portions of any of the examples in the foregoing examples.

[0151] Another set of exemplary embodiments may include an apparatus comprising components for performing any or all of the elements of any of the examples in the foregoing examples.

[0152] Another set of exemplary embodiments may include an apparatus comprising a processor configured to cause a wireless device to execute any or all of the elements of any of the examples in the foregoing examples.

[0153] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0154] By interpreting each message / signal X received by the user equipment (UE) in the downlink as a message / signal X sent by the base station, and interpreting each message / signal Y sent by the UE in the uplink as a message / signal Y received by the base station, any of the methods described herein for operating the UE can serve as the basis for a corresponding method for operating the base station.

[0155] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, in some embodiments, the subject matter may be implemented as a computer-implemented method, a computer-readable storage medium, or a computer system. In other embodiments, the subject matter may be implemented using one or more custom-designed hardware devices such as ASICs. In still other embodiments, the subject matter may be implemented using one or more programmable hardware elements such as FPGAs.

[0156] In some implementations, a non-transitory computer-readable storage medium (e.g., a non-transitory memory element) may be configured to store program instructions and / or data, wherein if these program instructions are executed by a computer system, the computer system performs a method, such as any method implementation of the method implementations described herein, or any combination of method implementations described herein, or any subset of any method implementations described herein, or any combination of such subsets.

[0157] In some implementations, the device (e.g., UE) may be configured to include a processor (or a set of processors) and a memory medium (or memory element), wherein the memory medium stores program instructions, and the processor is configured to read from and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any method implementation (or any combination of method implementations described herein, or any subset of any method implementations described herein, or any combination of such subsets) of the various method implementations described herein. The device may be implemented in any of the various forms.

[0158] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A method, the method comprising: By wireless devices: Receive Radio Resource Control (RRC) configuration information, the RRC configuration information including LTM configuration information indicating the configuration of one or more lower-layer triggered mobility (LTM) candidate cells; Evaluate whether the LTM candidate cell configuration is effective for the wireless device; as well as Send an indication of whether the LTM candidate cell configuration is valid for the radio device.

2. The method according to claim 1, The indication wherein the failure reason information provided by the radio device in the RRC reconstruction message indicates that at least one LTM candidate cell configuration is invalid for the radio device.

3. The method according to claim 1, The indication is given via an RRC configuration completion message to indicate that at least one LTM candidate cell configuration is invalid for the radio device.

4. The method of claim 1, wherein the method further comprises the wireless device: Sends an indication of one or more LTM candidate cells on which an LTM configuration failure has occurred.

5. The method of claim 1, wherein the method further comprises the wireless device: In response to the RRC configuration information, a first RRC configuration complete message is sent to the cellular base station, wherein the first RRC configuration complete message indicates that the wireless device has applied non-LTM configuration information from the RRC configuration information; and In response to the RRC configuration information, a second RRC configuration completion message is sent to the cellular base station, wherein the second RRC configuration completion message indicates whether the LTM candidate cell configuration is valid for the radio device.

6. The method according to claim 5, The second RRC configuration completion message includes information indicating that the second RRC configuration completion message is used for LTM configuration confirmation.

7. The method of claim 1, wherein the method further comprises the wireless device: In response to the RRC configuration information, an RRC configuration complete message is sent to the cellular base station, wherein the RRC configuration complete message indicates that the radio device has applied non-LTM configuration information from the RRC configuration information, and also indicates whether the LTM candidate cell configuration is valid for the radio device.

8. The method according to claim 1, The evaluation of whether the LTM candidate cell configuration is effective for the wireless device includes evaluating the LTM candidate configuration for all LTM candidate cells derived from the LTM configuration information.

9. The method according to claim 1, The evaluation of whether the LTM candidate cell configuration is valid for the wireless device includes evaluating the LTM candidate configuration derived from the LTM configuration information that is only for the serving cell LTM candidate cell.

10. An apparatus comprising: A processor configured to cause a wireless device to perform the steps of the method according to any one of claims 1 to 9.

11. A wireless device, the wireless device comprising: antenna; A radio component, the radio component being operatively coupled to the antenna; and One or more processors, the one or more processors being operatively coupled to the radio component; The wireless device is configured to perform the steps of the method according to any one of claims 1 to 9.

12. A method, the method comprising: By cellular base stations: Transmit Radio Resource Control (RRC) configuration information, which includes LTM configuration information indicating the configuration of one or more lower-layer triggered mobility (LTM) candidate cells; as well as Receive an indication of whether the LTM candidate cell configuration is valid for the radio device.

13. The method according to claim 12, The indication wherein the failure reason information provided by the radio device in the RRC reconstruction message indicates that at least one LTM candidate cell configuration is invalid for the radio device.

14. The method according to claim 12, The indication is given via an RRC configuration completion message to indicate that at least one LTM candidate cell configuration is invalid for the radio device.

15. The method of claim 12, wherein the method further comprises: Receives indications of one or more LTM candidate cells on which LTM configuration failure has occurred.

16. The method of claim 12, wherein the method further comprises: In response to the RRC configuration information, a first RRC configuration complete message is received from the wireless device, wherein the first RRC configuration complete message indicates that the wireless device has applied non-LTM configuration information from the RRC configuration information; and A second RRC configuration completion message is received from the radio device in response to the RRC configuration information, wherein the second RRC configuration completion message indicates whether the LTM candidate cell configuration is valid for the radio device.

17. The method according to claim 16, The second RRC configuration completion message includes information indicating that the second RRC configuration completion message is used for LTM configuration confirmation.

18. The method of claim 12, wherein the method further comprises: In response to the RRC configuration information, an RRC configuration complete message is received from the radio device, wherein the RRC configuration complete message indicates that the radio device has applied non-LTM configuration information from the RRC configuration information, and also indicates whether the LTM candidate cell configuration is valid for the radio device.

19. The method of claim 12, wherein the method further comprises: One or more timer values ​​for the wireless device to respond to the RRC configuration information are selected, at least in part, based on the RRC configuration information, which includes LTM configuration information.

20. A cellular base station, the cellular base station comprising: One or more processors; and A memory storing instructions that, when executed by the one or more processors, perform the steps of the method according to any one of claims 12 to 19.

Images