Transaction identifier in LTM

By expanding the transaction ID space and adding a candidate cell configuration index, the problem of network identification confusion in L1/L2 mobility handover in wireless communication systems is solved, enabling accurate candidate cell configuration identification and handover decisions, and improving the system's mobility management efficiency.

CN123125949APending Publication Date: 2026-11-17APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580025857.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-01
Filing Date
2025-03-31
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In wireless communication systems, existing technologies suffer from insufficient transaction identifiers during L1/L2-triggered mobility handover, which prevents the network from accurately identifying which cell configuration the UE has applied. This is especially problematic in cases of radio link failure or multiple candidate cells sharing the same transaction ID, leading to confusion and incorrect handover decisions.

Method used

By expanding the transaction ID space, adding candidate cell configuration indexes, and including candidate indexes and transaction IDs in the RRC reconfiguration completion message, the problem of network identification confusion is solved, ensuring that the UE clearly identifies the applied configuration.

Benefits of technology

This enables the network to accurately identify the candidate cell configuration used by the UE during mobility handover triggered by L1/L2, reducing handover errors caused by radio link failures and improving the system's mobility management efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125949A_ABST
    Figure CN123125949A_ABST
Patent Text Reader

Abstract

This document discusses systems and methods for transaction identification in Layer 1 (L1) / Layer 2 (L2) triggered Mobility (LTM). In some implementations, a User Equipment (UE) can receive a Media Access Control (MAC) control element (CE) from a network node, which triggers an LTM handover to a candidate cell associated with a Layer 2 triggered Mobility (LTM) candidate configuration. The UE can perform the cell handover to the candidate cell by applying the LTM candidate configuration and transmitting a message including an LTM candidate identifier (ID) corresponding to the applied LTM candidate configuration.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application generally relates to wireless communication systems, including specific implementations of Layer 1 (L1) / Layer 2 (L2) triggered mobility (LTM). Background Technology

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless communication devices. Wireless communication system standards and protocols may include, for example, 3GPP Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wireless Local Area Networks (WLANs) (often referred to as Wi-Fi within the industry organization). ® ).

[0003] As envisioned by 3GPP, different wireless communication system standards and protocols can use various radio access networks (RANs) for communication between RAN base stations (sometimes referred to as RAN nodes, network nodes, or simply nodes) and wireless communication equipment called user equipment (UEs). 3GPP RANs can include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0004] Each RAN can use one or more Radio Access Technologies (RATs) to perform communication between the base station and the UE. For example, GERAN implements the GSM and / or EDGE RAT, UTRAN implements the Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RATs, E-UTRAN implements the LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements the NR RAT (sometimes referred to herein as 5GRAT, 5G NR RAT, or simply NR). In some deployments, E-UTRAN may also implement the NR RAT. In some deployments, NG-RAN may also implement the LTE RAT.

[0005] The base stations used by a RAN can be associated with that RAN. An example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as Evolved Node B, Enhanced Node B, eNodeB, or eNB). An example of an NG-RAN base station is a Next Generation Node B (sometimes also called gNode B or gNB).

[0006] The RAN provides communication services to external entities through its connection with the core network (CN). For example, E-UTRAN can utilize the evolved packet core (EPC), while NG-RAN can utilize the 5G core network (5GC).

[0007] 5G NR frequency bands can be divided into two or more distinct frequency ranges. For example, Frequency Range 1 (FR1) may include bands operating at frequencies below 6 GHz, some of which are available in previous standards and can potentially be extended to cover new spectrum offerings from 410 MHz to 7125 MHz. Frequency Range 2 (FR2) may include bands from 24.25 GHz to 52.6 GHz. It should be noted that in some systems, FR2 may also include bands from 52.6 GHz to 71 GHz (or higher). Bands in the millimeter-wave (mmWave) range of FR2 may have smaller coverage areas but potentially higher available bandwidth than bands in FR1. Those skilled in the art will recognize that these frequency ranges, presented by way of example, may change over time or in different regions. Attached Figure Description

[0008] To facilitate the identification of any particular element or action in the discussion, one or more of the most significant digits in the figure reference numerals refer to the figure number in which the element was first introduced.

[0009] Figure 1 Examples of Radio Resource Control (RRC) configurations according to some implementation schemes are illustrated.

[0010] Figure 2 Examples of RRC configurations, including configuration details, are shown according to some implementation schemes.

[0011] Figure 3 Another example of an RRC configuration based on some implementation schemes is shown.

[0012] Figure 4 An example flowchart illustrating an RRC message that can be transmitted as part of an LTM according to some implementation schemes is shown.

[0013] Figure 5 Example flowcharts are shown for communication between a UE and various candidate cells according to some implementation schemes, where the network does not know whether the RRC completion message includes the cell configuration of the first cell or the cell configuration of the fourth cell.

[0014] Figure 6 Examples of LTM candidate IEs based on some implementation schemes are shown.

[0015] Figure 7 An example of IE reconfiguration based on some implementation schemes is shown.

[0016] Figure 8 A method for a UE according to an embodiment of this document is illustrated.

[0017] Figure 9 A method for network nodes according to the implementation scheme of this paper is illustrated.

[0018] Figure 10 An example architecture of a wireless communication system according to the implementation scheme disclosed herein is illustrated.

[0019] Figure 11 A system for performing signaling transfer between a wireless device and a network device according to an embodiment disclosed herein is illustrated. Detailed Implementation

[0020] Various implementations are described with respect to the UE. However, references to the UE are provided for illustrative purposes only. The example implementations may be used with any electronic components capable of establishing a connection to a network and configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, the UE described herein is used to represent any suitable electronic component.

[0021] One of the goals of wireless communication systems is seamless handover between cells. Therefore, it is desirable to specify mechanisms and procedures for inter-cell mobility based on Layer 1 (L1) / Layer 2 (L2) to reduce mobility latency. These mechanisms and procedures may include the configuration and maintenance of multiple candidate cells to allow for rapid application of candidate cell configurations. Dynamic handover mechanisms between candidate serving cells (including secondary primary cells (SpCell) and secondary cells (SCell)) based on L1 / L2 signaling can be specified for potential applicable scenarios. L1 enhancements for inter-cell beam management, including L1 measurement and reporting and beam indication, can be specified. The possibility of further clarifying the interaction between L1 enhancements and dynamic handover mechanisms can be specified. Additionally, if needed, timing advance management supporting L1 / L2 mobility and Central Unit (CU) - Distributed Unit (DU) interface signaling delivery can be specified.

[0022] Please note that FR2-specific enhancements (if any) may not be excluded. Additionally, please note that the L1 / L2-based inter-cell mobility procedures apply to the following scenarios: standalone, carrier aggregation (CA), and new radio dual connectivity (NR-DC) scenarios with serving cell changes within a configuration grant (CG); intra-DU, intra-CU, and inter-DU scenarios (applicable to standalone networks and CA: no new RAN interface is expected); both intra-frequency and inter-frequency scenarios; both FR1 and FR2 scenarios; the source and destination cells can be synchronous or asynchronous.

[0023] Furthermore, it may be desirable to specify mechanisms and procedures for selectively activating NR-DC for cell groups (at least for secondary cell groups (SCGs)) via Layer 3 (L3) enhancements. For example, such enhancements could include subsequent cell group changes after a CG change without reconfiguration, and could allow for the re-initiation of Conditional Primary / Secondary Cell Change (CPC) / Conditional PSCell Addition (CPA). Note that a coordinated Radio Resource Control (RRC) modeling approach may be considered.

[0024] Additionally, conditional handover (CHO) can be specified that includes the target primary cell group (MCG) and the target SCG. CHOs that include the target MCG and candidate SCGs for CPC / CPA in the NR-DC can also be specified. Furthermore, CHOs that include both the target MCG and the target SCG can be used as a baseline.

[0025] In some wireless communication systems, support for L1 / L2 triggered mobility (LTM) between CUs can be specified. For example, when dual connectivity (DC) is not configured, the case where the CU acts as the primary node (MN) can be prioritized. As a secondary priority, the case where NR-DC is configured, and the CU acts as the secondary node (SN) with the MCG unchanged, can be supported. Furthermore, as a secondary priority, the case where NR-DC is configured, where the CU acts as the MN and the SCG remains unchanged or is released, can be supported. Note that the case where LTM is configured in both the MCG and SCG can be excluded. Additionally, support for subsequent LTM mobility procedures can be specified to avoid RRC configuration between cell handovers according to Rel-18 LTM. It should be noted that coordination with SA3 may be required regarding security key handling. It should also be noted that intra-CU LTM procedures can be considered as a baseline for adding inter-CU support.

[0026] In some mechanisms, measurement-related enhancements to support LTM can be discussed and described. For example, measurement-related enhancements can be applied to intra-CU MCG / SCG LTM and inter-CU MCG / SCG LTM. Furthermore, components can be specified to support event-triggered L1 measurement reporting. RAN1 and RAN2 can be enhanced to independently advance their respective event-triggered measurement objectives for multiple-input multiple-output (MIMO) and mobility enhancements. Additionally, support for Channel State Information-Reference Signal (CSI-RS) measurements for the LTM procedure can be specified, and CSI-RS-based beam management and / or other physical layer operations on candidate cells can be implemented prior to LTM. Additional enhancements can be made. For example, some implementations can specify support for conditional LTM; specify UE evaluation conditions for triggering LTM; aim to support conditional LTM that includes subsequent LTMs; prioritize intra-CU LTMs; and specify RRM requirements related to the above objectives as needed.

[0027] In some wireless communication systems, L2 (e.g., Media Access Control (MAC) element (CE)) can trigger LTM handover. For example, before transmitting the MAC CE that triggers mobility, all candidates can be provided to the UE in the RRC configuration. The RRC can provide multiple configurations for the cell. The UE can perform measurements and report these measurements to the network. The network can transmit a MAC CE including an index indicating which configuration provided in the RRC the UE should use.

[0028] In Rel-18, the CU remains the same, with no change in security keys or context, and no change in Packet Data Convergence Protocol (PDCP). LTM handovers can also be inter-DU (i.e., Radio Link Control (RLC) and MAC reset) or intra-DU (i.e., MAC reset only), where the UE is aware of the LTM handover in advance. In some implementations, the UE may utilize L3 RRC messages (e.g., RRCReconfigComplete messages) to acknowledge L2 triggering, and the UE's RRC messages are not expected between LTM cell handovers, even for subsequent LTM handovers and only for LTM MAC CE triggering. In some cases, Rel-19 LTM introduces the use of inter-CU handovers, but all the above discussion still applies.

[0029] Figure 1 An example of RRC configuration 102 according to some implementation schemes is illustrated. For L2 MAC CE triggering, the network may transmit RRC configuration 102 to the UE to provide the UE with candidates that can be indicated when a handover is triggered.

[0030] As shown in the figure, RRC configuration 102 may include LTM candidate configuration 104. Each LTM candidate configuration in LTM candidate configuration 104 may indicate a potential configuration that can be applied when LTM is triggered. As illustrated, LTM candidate configuration 104 may have a candidate identifier (ID) (i.e., index) (e.g., index 110), a transaction ID (e.g., transaction ID 106), and an associated cell configuration (e.g., configuration details 108) applied by the UE during LTM handover.

[0031] An index can be an identifier for an LTM candidate, used to distinguish multiple candidates. For example, the network can transmit a MAC CE to trigger a first candidate configuration by indicating index 110 in the MAC CE, and the UE will apply configuration details 108 to perform LTM. Once LTM is complete and the UE has successfully applied the associated cell LTM configuration, the UE can trigger an RRCReconfigComplete message with the applied configuration and send the message to the target (now source) LTM cell.

[0032] Figure 2 Examples of RRC configurations, including configuration details, are illustrated according to some implementation schemes. As shown in the illustrated examples, the network can configure multiple candidate configurations for the same cell. For example, in the illustrated implementation scheme, first candidate 202, third candidate 204, and fifth candidate 206 are each configured with the same candidate cell (PCI x).

[0033] However, it is possible that the configuration details of the same cell can change based on various factors, including UE reports or location. Configuration details can also be changed, for example, to send a Configuration Indicator (TCI) to allow the network to use different beams based on the UE's location. Configuration details can also change based on the type of NCell beam reported by the UE in the current situation. For example, although first candidate 202, third candidate 204, and fifth candidate 206 include the same cell (PCI x), they include different measurement beams and reporting configurations. When inter-CUs are introduced, the network may not be able to know which candidate the UE is using based on the cell. Figure 3 An example of an RRC configuration with CHO configuration 302 is illustrated according to some implementation schemes. In such an example, the network may also configure R16 or R17 configurations (e.g., CHO, CPC) to the same cell as LTM. This may result in the same transaction ID ("0" in this example) being used twice for the same cell, but from different configuration perspectives.

[0034] For example, in the illustrated implementation, both the CHO configuration 302 and the first candidate 304 of the LTM candidate configuration have transaction IDs of zero. This can lead to some confusion at the network level. For instance, when the UE transmits RRCReconfigComplete, if the UE uses the transaction ID to identify the applied configuration, the network may not know whether it is based on the CHO configuration or the LTM candidate configuration.

[0035] Figure 4 An example flowchart illustrating an RRC message that can be transmitted as part of LTM according to some implementation schemes is shown. As shown, base station 402 can transmit an RRC reconfiguration message 406. The RRC reconfiguration message 406 may include candidate configurations. UE 404 can transmit an RRC reconfiguration complete message 408 with the applied configuration.

[0036] In some implementations, up to four transaction IDs may be defined. The purpose of the transaction IDs is to track which reconfiguration / acknowledgment is being used, thus allowing the network to know which reconfiguration UE 404 is currently acknowledging in the RRC reconfiguration completion message 408. In some implementations, it is not possible for more than four transactions to run concurrently.

[0037] However, LTM has an impact on this situation because in the examples discussed in this paper (i.e., in...) Figure 1 , Figure 2 and Figure 3 For example, for the same cell / physical cell identifier (PCI) itself, there may be three transaction IDs. If the UE applies a specific transaction ID (e.g., transaction ID 2), then when the LTM handover is completed, the UE will use "2".

[0038] Additionally, an RRC procedure can be defined and provided for this interaction. For example, the UE may be able to handle several simultaneous RRC procedures. After receiving a message invoking a procedure, the UE may be prepared to receive another message that can invoke a second procedure and act upon it. An example RRC reconfiguration information element (IE) used may be provided as follows:

[0039]

[0040] Furthermore, some wireless communication systems may encounter various issues in the context of transaction identification in LTM. For example, the network may be restricted to only four different configurations per cell, and even if there are (up to) four different configurations per cell, the UE may only be configured for a maximum of two cells.

[0041] Another problem arises when more than one candidate cell has the same transaction ID, and if a radio link failure (RLF) exists, and the UE applies the configuration of a better cell with the same transaction ID. The base station-CU may not know whether the UE has applied the cell configuration of the first cell or the cell configuration of the new cell, such as... Figure 5 Further discussion is given in the illustrated flowchart.

[0042] Another problem may arise when the network is forced to use the same transaction ID for the same cell but with different configurations. For these reasons, the transaction ID may be insufficient for the network to identify which configuration the UE has applied. The implementation scheme in this paper provides a way for the UE to successfully identify to the network which configuration it has applied.

[0043] Figure 5An example signaling flow diagram is illustrated for UE 502 and various candidate cells according to some implementation schemes, where the network does not know whether the RRC completion message includes the cell configuration of the first cell or the cell configuration of the fourth cell. In the illustrated implementation scheme, LTM is configured 504 with candidate cells 0, 1, 2, 3, and 4. In the illustrated implementation scheme, the configuration of cell 1 includes transaction ID 0, the configuration of cell 2 includes transaction ID 1, the first configuration of cell 3 includes transaction ID 2, the second configuration of cell 3 includes transaction ID 3, and the configuration of cell 4 includes transaction ID 0.

[0044] In the illustrated implementation, both the cell 1 configuration and the cell 4 configuration share transaction ID 0. As shown, the old source cell (cell 0) can transmit an LTM MAC CE 506 to trigger UE 502 to move to candidate cell 1. The UE can transmit an RRC completion message 508 including transaction ID 0 to indicate successful receipt of the MAC CE for handover to cell 1. However, radio link failures or LTM handover failures may occur.

[0045] The UE can discover that candidate cell 4 is better than candidate cell 1 and configure itself to switch to candidate cell 4. The UE can transmit an RRC completion message 510 with transaction ID 0 to indicate the switch to candidate cell 4. However, the base station does not know whether this is a cell configuration from cell 1 or cell 4, because they both share transaction ID 0.

[0046] The implementations described in this paper provide solutions to this type of confusion. In some implementations described herein, the UE can more clearly inform the network of the applied configuration.

[0047] In some implementations, the transaction ID space can be increased. For example, instead of limiting the transaction ID space to four, an additional transaction ID space can be used.

[0048] In some other implementations, a candidate cell configuration index can be used. For example, the UE can include the cell configuration index along with the transaction ID in the RRCReconfigComplete message. This can be advantageous because it is bound at the UE level. Additionally, the UE can be configured to use up to "8" candidate configurations, where these configurations are indexed by a unique index. In some implementations, the index can also be extended to inter-CU LTM cases. For example, the index can be used if the candidate index is considered unique across all candidate cells (e.g., intra-node / inter-node partial candidate cells). Where candidate indices cannot be identical across inter-CU candidates, the UE can report inter-CU candidate information along with the cell configuration index.

[0049] In some examples of implementation schemes, the transaction ID space can be increased. For example, the transaction ID range can be increased from, for example, a range of 0-3 to a larger range including a range of 0-8 or a range of 0-16.

[0050] In some implementations, the UE can only use a new transaction ID if the network transaction ID is a new version. In some implementations, the UE can notify the network that the new transaction ID is only possible as a UE capability. If the UE does not support the new capability, the network can restrict the range of transaction IDs to 0-3.

[0051] In some implementations that support increasing the transaction ID space, the network can use two RRC messages with two different transaction IDs. Each RRC message then has a candidate list, and the network includes the same cell configuration where the ID needs to be reused to be wrapped in different RRC configurations. The UE can then use the wrapped transaction ID when performing a report.

[0052] An example RRC configuration IE for this implementation is provided as follows:

[0053] In some examples of implementations that use candidate cell configuration indexes, the UE may include a transaction ID (e.g., by traditional procedure) for the applied configuration. The UE may also include the candidate index of the applied configuration in the RRC completion message.

[0054] In some cases, the configuration index can be overridden by UE capabilities. For example, if the UE does not support the configuration candidate index applied to the report, the network can be limited to a configuration that avoids duplication (or ambiguity at the network level where transaction IDs are used). In some implementations, any UE supporting Rel-18 LTM can support the report without any explicit capabilities.

[0055] In some implementations, the configuration identification signaling transmission may include one or more of the following: In some implementations, instead of providing a candidate index, the UE may provide a cell identifier-cell PCI. In some implementations, the UE provides a global cell identifier-cell GCI instead of a candidate index. In some implementations, the UE may provide both a PCI and a candidate cell index.

[0056] In some implementations, where candidate cell configuration is available, the LTM-Candidate-r18 IE may include LTM-CandidateId-r18 (i.e., configuration ID), and wherein ltm-candidateConfig-r18 includes an eight-bit string containing RRCReconfiguration (e.g., transaction ID).

[0057] For example, Figure 6 An LTM candidate IE 602 according to some implementation schemes is illustrated. A network node can transmit the LTM candidate IE 602 to the UE to add or modify LTM candidate configurations. As shown, the LTM candidate IE 602 may include an LTM candidate ID field 604 and an RRCReconfiguration field 606. The LTM candidate ID field 604 may include a configuration ID (e.g., an LTM candidate index used for configuration). The RRCReconfiguration field 606 may include a transaction ID.

[0058] If the UE applies an LTM candidate associated with an LTM candidate ID and a transaction ID, the UE can report the LTM candidate ID and transaction ID to the network node. For example, Figure 7 An example RRC reconfiguration completion IE 702 according to some implementation schemes is illustrated. The UE may transmit the RRC reconfiguration completion IE 702 to the network node to indicate which LTM candidate configuration was applied. As shown, the RRC reconfiguration completion IE 702 may include an applied candidate ID field 704. The applied candidate ID field 704 provides the LTM candidate ID (e.g., candidate index value) of the applied LTM candidate. The UE may transmit the RRC reconfiguration completion IE 702 to the network via an RRC message, which confirms the successful completion of the RRC connection reconfiguration and indicates the candidate ID of the applied LTM candidate. Note that the transaction ID may also be reported by the UE to the network node.

[0059] In some implementations where the index can also be extended to inter-CU LTM scenarios, if the UE is provided with information about whether the candidate cell set belongs to a specific CU, the UE report may include the transaction ID (in the traditional procedure) for the applied configuration, the base station-CU configuration ID (e.g., gNB-CU configuration ID), and the candidate index for the applied configuration. This can be advantageous where the serving CU does not act as a coordinator of the configuration, and each CU can freely reuse the transaction ID and cell configuration ID, provided that the source CU uniquely assigns the base station-CU index.

[0060] Additionally, the implementation of the index for inter-CU LTM scenarios can be covered by UE capabilities, wherein if the UE does not support this (of the configuration candidate index to which the report applies), the network is restricted to ensure that there is no duplicate (or ambiguity at the network using transaction ID) configuration. Furthermore, in some implementations, any UE supporting Rel-18 LTM can support the report without any explicit capabilities.

[0061] Figure 8A method 800 for a UE according to an embodiment of this document is illustrated. The illustrated method 800 includes receiving from a network node 802 a MAC CE triggering an LTM handover to a candidate cell associated with an LTM candidate configuration. Method 800 further includes performing 804 a cell handover to the candidate cell by applying the LTM candidate configuration. Method 800 also includes transmitting to the network node 806 a message including an LTM candidate ID corresponding to the applied LTM candidate configuration.

[0062] In some implementations, method 800 further includes receiving configurations for one or more LTM candidates from a network node, wherein the LTM candidate configurations are associated with one or more transaction IDs and a plurality of LTM candidate IDs. In some such implementations, the plurality of LTM candidate IDs includes a unique LTM candidate ID for each of the one or more LTM candidates.

[0063] In some implementations of method 800, the LTM candidate ID is a configuration index corresponding to the applied LTM candidate configuration. In some such implementations, the configuration index is unique across all candidate cells, including intra-node and inter-node cells.

[0064] In some implementations of method 800, the message transmitted to the network node also includes a transaction ID corresponding to the applied LTM candidate configuration.

[0065] In some implementations of method 800, the message transmitted to the network node is an RRC reconfiguration complete message.

[0066] Figure 9 A method 900 for a network node according to an embodiment of this document is illustrated. The illustrated method 900 includes transmitting to a UE 902 a MAC CE triggering an LTM handover to a candidate cell associated with an LTM candidate configuration, wherein the MAC CE causes the UE to handover to the candidate cell by applying the LTM candidate configuration. Method 900 also includes receiving from the UE 904 a message including an LTM candidate ID corresponding to the applied LTM candidate configuration.

[0067] In some implementations, method 900 further includes transmitting to the UE a configuration for one or more LTM candidates, wherein the LTM candidate configuration is associated with one or more transaction IDs and a plurality of LTM candidate IDs. In some such implementations, the plurality of LTM candidate IDs includes a unique LTM candidate ID for each of the one or more LTM candidates.

[0068] In some implementations of method 900, the LTM candidate ID is a configuration index corresponding to the applied LTM candidate configuration.

[0069] In some implementations of method 900, the message transmitted to the network node also includes a transaction ID corresponding to the applied LTM candidate configuration.

[0070] In some implementations of method 900, the message transmitted to the network node is an RRC reconfiguration complete message.

[0071] Figure 10 An example architecture of a wireless communication system 1000 according to an embodiment disclosed herein is illustrated. The following description is provided for an example wireless communication system 1000 operating in conjunction with LTE system standards and / or 5G or NR system standards provided by 3GPP technical specifications.

[0072] like Figure 10 As shown, the wireless communication system 1000 includes UE 1002 and UE 1004 (but any number of UEs may be used). In this example, UE 1002 and UE 1004 are exemplified as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.

[0073] UE 1002 and UE 1004 can be configured to communicatively couple with RAN 1006. In an implementation, RAN 1006 can be NG-RAN, E-UTRAN, etc. UE 1002 and UE 1004 utilize connections (or channels) with RAN 1006 (shown as connection 1008 and connection 1010, respectively), each of these connections including a physical communication interface. RAN 1006 may include one or more base stations (such as base station 1012 and base station 1014) implementing connection 1008 and connection 1010.

[0074] In this example, Connection 1008 and Connection 1010 are the air interfaces that enable this communication coupling and are compliant with the RAT used by RAN 1006, such as LTE and / or NR.

[0075] In some implementations, UE 1002 and UE 1004 may also exchange communication data directly via sidelink interface 1016. UE 1004 is shown configured to access an access point (shown as AP 1018) via connection 1020. For example, connection 1020 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, while AP 1018 may include Wi-Fi. ® Router. In this example, AP 1018 can connect to another network (e.g., the Internet) without going through CN 1024.

[0076] In the implementation, UE 1002 and UE 1004 may be configured to communicate with each other or with base station 1012 and / or base station 1014 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication technologies, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication) , but the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0077] In some implementations, all or some of the base stations in base station 1012 or base station 1014 may be implemented as one or more software entities running on a server computer as part of a virtual network. Furthermore, or in other implementations, base station 1012 or base station 1014 may be configured to communicate with each other via interface 1022. In implementations where the wireless communication system 1000 is an LTE system (e.g., when CN 1024 is an EPC), interface 1022 may be an X2 interface. This X2 interface may be defined between two or more base stations (e.g., two or more eNBs, etc.) connected to the EPC and / or between two eNBs connected to the EPC. In implementations where the wireless communication system 1000 is an NR system (e.g., when CN 1024 is a 5GC), interface 1022 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs, etc.) connected to the 5GC, between base station 1012 (e.g., a gNB) connected to the 5GC and an eNB, and / or between two eNBs connected to the 5GC (e.g., CN 1024).

[0078] RAN 1006 is shown communicatively coupled to CN 1024. CN 1024 may include one or more network elements 1026 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 1002 and UE 1004) connected to CN 1024 via RAN 1006. Components of CN 1024 may be implemented in a single physical device or a separate physical device including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media).

[0079] In the implementation scheme, CN 1024 may be an EPC, and RAN 1006 may be connected to CN 1024 via S1 interface 1028. In the implementation scheme, S1 interface 1028 may be divided into two parts: an S1 user plane (S1-U) interface, which carries service data between base station 1012 or base station 1014 and the service gateway (S-GW); and an S1-MME interface, which is the signaling interface between base station 1012 or base station 1014 and the mobility management entity (MME).

[0080] In the implementation scheme, CN 1024 may be a 5GC, and RAN 1006 may be connected to CN 1024 via NG interface 1028. In the implementation scheme, NG interface 1028 may be divided into two parts: an NG user plane (NG-U) interface, which carries service data between base station 1012 or base station 1014 and user plane function (UPF); and an S1 control plane (NG-C) interface, which is the signaling interface between base station 1012 or base station 1014 and access and mobility management function (AMF).

[0081] Generally, application server 1030 may be an element that provides Internet Protocol (IP) bearer resources (e.g., packet-switched data services) for use with CN 1024. Application server 1030 may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for UE 1002 and UE 1004 via CN 1024. Application server 1030 can communicate with CN 1024 via IP communication interface 1032.

[0082] Figure 11 A system 1100 for performing signaling transfer 1134 between a wireless device 1102 and a network device 1118 according to an embodiment disclosed herein is illustrated. System 1100 may be part of a wireless communication system as described herein. Wireless device 1102 may be, for example, a UE of a wireless communication system. Network device 1118 may be, for example, a base station (e.g., an eNB or gNB) of a wireless communication system.

[0083] Wireless device 1102 may include one or more processors 1104. Processor 1104 is executable instructions that cause various operations of wireless device 1102 to be performed as described herein. Processor 1104 may include one or more baseband processors, which are implemented using, for example, a central processing unit (CPU), digital signal processor (DSP), application-specific integrated circuit (ASIC), controller, field-programmable gate array (FPGA) device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0084] Wireless device 1102 may include memory 1106. Memory 1106 may be a non-transitory computer-readable storage medium that stores instructions 1108, which may include, for example, instructions executed by processor 1104. Instructions 1108 may also be referred to as program code or a computer program. Memory 1106 may also store data used by processor 1104 and results calculated by the processor.

[0085] Wireless device 1102 may include one or more transceivers 1110, which may include radio frequency (RF) transmitter circuitry and / or receiver circuitry, which use antenna 1112 of wireless device 1102 to facilitate signaling to and / or from wireless device 1102 and other devices (e.g., network device 1118) according to a corresponding RAT (e.g., signaling transmission 1134).

[0086] Wireless device 1102 may include one or more antennas 1112 (e.g., one, two, four or more). In embodiments with multiple antennas 1112, wireless device 1102 may fully utilize the spatial diversity of such multiple antennas 1112 to transmit and / or receive multiple different data streams on the same time-frequency resources. This behavior may be referred to as, for example, multiple-input multiple-output (MIMO) behavior (referring to multiple antennas used at each of the transmitting and receiving devices to implement this aspect). MIMO transmission by wireless device 1102 may be implemented according to pre-decoding (or digital beamforming) applied to wireless device 1102, which multiplexes the data streams among antennas 1112 based on known or assumed channel characteristics, such that each data stream is received with appropriate signal strength relative to the other streams at a desired location in the spatial domain (e.g., the location of the receiver associated with that data stream). Some implementations may use a single-user MIMO (SU-MIMO) approach (where all data streams are directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) approach (where individual data streams may be directed to individual (different) receivers at different locations in the airspace).

[0087] In some implementations with multiple antennas, wireless device 1102 can implement analog beamforming technology, whereby the phase of the signal transmitted by antenna 1112 is relatively adjusted so that the (joint) transmission of antenna 1112 can be directed (this is sometimes referred to as beam control).

[0088] Wireless device 1102 may include one or more interfaces 1114. Interfaces 1114 can be used to provide input to or output to wireless device 1102. For example, wireless device 1102 as a UE may include interfaces 1114, such as microphones, speakers, touchscreens, buttons, etc., to allow input and / or output from a user of the UE to the UE. Other interfaces of such UEs may consist of transmitters, receivers, and other circuitry that allow the UE to communicate with other devices (e.g., in addition to the transceiver 1110 / antenna 1112 already described), and may be based on known protocols (e.g., Wi-Fi). ® and Bluetooth ® (etc.) to perform the operation.

[0089] Wireless device 1102 may include LTM module 1116. LTM module 1116 may be implemented via hardware, software, or a combination thereof. For example, LTM module 1116 may be implemented as a processor, circuitry, and / or instructions 1108 stored in memory 1106 and executed by processor 1104. In some examples, LTM module 1116 may be integrated within processor 1104 and / or transceiver 1110. For example, LTM module 1116 may be implemented via a combination of software components (e.g., software components executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within processor 1104 or transceiver 1110.

[0090] LTM module 1116 can be used in various aspects of this disclosure, such as Figure 1 , Figure 2 , Figure 3 , Figure 4 , Figure 5 , Figure 6 , Figure 7 and Figure 8 The LTM module 1116 is configured to enable the radio device 1102 to receive a MAC CE from the network device 1118, which triggers an LTM handover to a candidate cell associated with an LTM candidate configuration. The LTM module 1116 is also configured to enable the radio device 1102 to perform a cell handover to a candidate cell by applying the LTM candidate configuration. The LTM module 1116 is further configured to enable the radio device 1102 to transmit a message to the network device 1118 including an LTM candidate ID corresponding to the applied LTM candidate configuration.

[0091] Network device 1118 may include one or more processors 1120. Processor 1120 is executable instructions to perform various operations of network device 1118 as described herein. Processor 1120 may include one or more baseband processors, which are implemented using, for example, a CPU, DSP, ASIC, controller, FPGA device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0092] Network device 1118 may include memory 1122. Memory 1122 may be a non-transitory computer-readable storage medium that stores instructions 1124, which may include, for example, instructions executed by processor 1120. Instructions 1124 may also be referred to as program code or a computer program. Memory 1122 may also store data used by processor 1120 and results calculated by the processor.

[0093] Network device 1118 may include one or more transceivers 1126, which may include RF transmitter circuitry and / or receiver circuitry that uses the antenna 1128 of network device 1118 to facilitate signaling to and / or from network device 1118 and other devices (e.g., wireless device 1102) according to a corresponding RAT (e.g., signaling transmission 1134).

[0094] Network device 1118 may include one or more antennas 1128 (e.g., one, two, four or more). In embodiments having multiple antennas 1128, network device 1118 may perform MIMO, digital beamforming, analog beamforming, beam control, etc., as described.

[0095] Network device 1118 may include one or more interfaces 1130. Interface 1130 can be used to provide input to or output to network device 1118. For example, network device 1118 as a base station may include interface 1130 consisting of transmitters, receivers and other circuitry (e.g., in addition to the transceiver 1126 / antenna 1128 already described), which enable the base station to communicate with other equipment in the core network and / or enable the base station to communicate with external networks, computers and databases, etc., for the purpose of performing operations, management and maintenance of the base station or other equipment operatively connected to the base station.

[0096] Network device 1118 may include LTM module 1132. LTM module 1132 may be implemented via hardware, software, or a combination thereof. For example, LTM module 1132 may be implemented as a processor, circuitry, and / or instructions 1124 stored in memory 1122 and executed by processor 1120. In some examples, LTM module 1132 may be integrated within processor 1120 and / or transceiver 1126. For example, LTM module 1132 may be implemented via a combination of software components (e.g., software components executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within processor 1120 or transceiver 1126.

[0097] LTM module 1132 can be used in various aspects of this disclosure, such as Figure 1 , Figure 2 , Figure 3 , Figure 4 , Figure 5 , Figure 6 , Figure 7 and Figure 9 The LTM module 1132 can be configured to cause the network device 1118 to transmit a MAC CE to the radio device 1102, which triggers an LTM handover to a candidate cell associated with an LTM candidate configuration, wherein the MAC CE causes the UE to hand over to the candidate cell by applying the LTM candidate configuration. The LTM module 1132 is also configured to cause the network device 1118 to receive from the radio device 1102 a message including an LTM candidate ID corresponding to the applied LTM candidate configuration.

[0098] The embodiments contemplated herein include an apparatus comprising components for performing one or more elements of method 800. This apparatus may be, for example, a UE (such as wireless device 1102 as a UE, as described herein).

[0099] The embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 800. The non-transitory computer-readable media may be, for example, the memory of a UE (such as memory 1106 of a wireless device 1102 serving as a UE, as described herein).

[0100] The embodiments contemplated herein include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of method 800. This apparatus may be, for example, a UE (such as wireless device 1102 as a UE, as described herein).

[0101] The embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 800. The apparatus may be, for example, a UE (such as wireless device 1102 as a UE, as described herein).

[0102] The implementation scheme envisioned herein includes a signal as described in or related to one or more elements of method 800.

[0103] The embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution by a processor causes the processor to perform one or more elements of method 800. The processor may be a processor of the UE (such as processor 1104 as a wireless device 1102 of the UE, as described herein). These instructions may, for example, reside in the processor and / or in the memory of the UE (such as memory 1106 as a wireless device 1102 of the UE, as described herein).

[0104] The embodiments contemplated herein include an apparatus comprising components for performing one or more elements of method 900. This apparatus may be, for example, a base station (such as network device 1118 as a base station, as described herein).

[0105] The embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 900. The non-transitory computer-readable medium may be, for example, the memory of a base station (such as memory 1122 of network device 1118 as a base station, as described herein).

[0106] The embodiments contemplated herein include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of method 900. This apparatus may be, for example, a base station (such as network device 1118 as a base station, as described herein).

[0107] The embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 900. The apparatus may be, for example, an apparatus for a base station (such as network device 1118 as a base station, as described herein).

[0108] The implementation scheme envisioned herein includes a signal as described in or related to one or more elements of method 900.

[0109] The embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution by a processing element causes the processing element to perform one or more elements of method 900. The processor may be a processor of a base station (such as processor 1120 of network device 1118 as a base station, as described herein). These instructions may, for example, reside in the processor and / or in the memory of the base station (such as memory 1122 of network device 1118 as a base station, as described herein).

[0110] For one or more embodiments, at least one of the components illustrated in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a baseband processor as described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples illustrated herein. Similarly, circuitry associated with a UE, base station, network element, etc., as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples illustrated herein.

[0111] Unless otherwise explicitly stated, any of the embodiments described above may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustrative and descriptive information, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice with various embodiments.

[0112] Implementations and specific embodiments of the systems and methods described herein may include various operations embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components, including specific logical parts for performing the operations; or may include a combination of hardware, software, and / or firmware.

[0113] It should be recognized that the systems described herein include descriptions of specific implementations. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters, attributes, aspects, etc., of one implementation in one implementation. For clarity, these parameters, attributes, aspects, etc., are described only in one or more implementations, and it should be recognized that, unless expressly stated herein, these parameters, attributes, aspects, etc., may be combined with or substituted for parameters, attributes, aspects, etc., of another implementation.

[0114] 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.

[0115] Although the foregoing has been described in considerable detail for clarity, it will be apparent that certain changes and modifications can be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and apparatus described herein. Therefore, embodiments of the invention should be considered illustrative rather than restrictive, and this specification is not limited to the details given herein, but can be modified within the scope and equivalents of the appended claims.

Claims

1. A method for a user equipment (UE), the method comprising: The network node receives a Media Access Control (MAC) control element (CE), which triggers an LTM handover to a candidate cell associated with a Layer 2 triggered mobility (LTM) candidate configuration; Cell handover to the candidate cell is performed by applying the LTM candidate configuration; as well as A message is transmitted to the network node, the message including an LTM candidate identifier (ID) corresponding to the applied LTM candidate configuration.

2. The method of claim 1, further comprising receiving configuration for one or more LTM candidates from the network node, wherein the LTM candidate configuration is associated with one or more transaction IDs and a plurality of LTM candidate IDs.

3. The method of claim 2, wherein the plurality of LTM candidate IDs includes a unique LTM candidate ID for each of the one or more LTM candidates.

4. The method of claim 1, wherein the LTM candidate ID is a configuration index corresponding to the applied LTM candidate configuration.

5. The method of claim 4, wherein the configuration index is unique across all candidate cells, including intra-node cells and inter-node cells.

6. The method of claim 1, wherein the message transmitted to the network node further includes a transaction ID corresponding to the applied LTM candidate configuration.

7. The method of claim 1, wherein the message transmitted to the network node is an RRC reconfiguration complete message.

8. A computing device, the computing device comprising: processor; and The memory stores instructions that, when executed by the processor, configure the device to: The network node receives a Media Access Control (MAC) control element (CE), which triggers an LTM handover to a candidate cell associated with a Layer 2 triggered mobility (LTM) candidate configuration; Cell handover to the candidate cell is performed by applying the LTM candidate configuration; as well as A message is transmitted to the network node, the message including an LTM candidate identifier (ID) corresponding to the applied LTM candidate configuration.

9. The computing apparatus of claim 8, wherein the instructions further configure the apparatus to receive configurations for one or more LTM candidates from the network node, wherein the LTM candidate configurations are associated with one or more transaction IDs and a plurality of LTM candidate IDs.

10. The computing device of claim 9, wherein the plurality of LTM candidate IDs includes a unique LTM candidate ID for each of the one or more LTM candidates.

11. The computing device of claim 8, wherein the LTM candidate ID is a configuration index corresponding to the applied LTM candidate configuration.

12. The computing device of claim 11, wherein the configuration index is unique across all candidate cells, including intra-node cells and inter-node cells.

13. The computing device of claim 8, wherein the message transmitted to the network node further includes a transaction ID corresponding to the applied LTM candidate configuration.

14. The computing device of claim 8, wherein the message transmitted to the network node is an RRC reconfiguration complete message.

15. A method for a network node, the method comprising: A Media Access Control (MAC) control element (CE) is transmitted to the User Equipment (UE), which triggers an LTM handover to a candidate cell associated with a Layer 2 triggered Mobility (LTM) candidate configuration. The MAC CE enables the UE to switch to the candidate cell by applying the LTM candidate configuration; as well as The UE receives a message including an LTM candidate identifier (ID) corresponding to the applied LTM candidate configuration.

16. The method of claim 15, further comprising transmitting to the UE a configuration for one or more LTM candidates, wherein the LTM candidate configuration is associated with one or more transaction IDs and a plurality of LTM candidate IDs.

17. The method of claim 16, wherein the plurality of LTM candidate IDs includes a unique LTM candidate ID for each of the one or more LTM candidates.

18. The method of claim 15, wherein the LTM candidate ID is a configuration index corresponding to the applied LTM candidate configuration.

19. The method of claim 15, wherein the message transmitted to the network node further includes a transaction ID corresponding to the applied LTM candidate configuration.

20. The method of claim 15, wherein the message transmitted to the network node is an RRC reconfiguration complete message.

21. An apparatus comprising components for performing the method according to any one of claims 1 to 7 and 15 to 20.

22. A computer-readable medium comprising instructions for causing the electronic device to perform the method according to any one of claims 1 to 7 and 15 to 20 when executed by one or more processors of the electronic device.

23. An apparatus comprising a logic component, module, or circuit for performing the method according to any one of claims 1 to 7 and 15 to 20.

24. An apparatus comprising a logic component, module, or circuit for performing the method according to any one of claims 1 to 7 and 15 to 20.

25. A baseband processor for a user equipment (UE), the baseband processor being configured to cause the UE to perform one or more elements according to any one of claims 1 to 7.

26. A baseband processor for a base station, the baseband processor being configured to cause the base station to perform one or more elements according to any one of claims 15 to 20.