Indicating candidate timing advance values to new serving cell in layer 1 / layer 2 triggered mobility
By having the UE report active TA timers to the network during cell switch procedures, the inefficiencies and overhead associated with repeated TA acquisition are mitigated, optimizing resource and energy usage in Layer 1/Layer 2 Triggered Mobility.
Patent Information
- Application Number
- PCT/IB2025/063596
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2025-12-31
- Publication Date
- 2026-11-12
AI Technical Summary
Current cell switch procedures in wireless communications, particularly in Layer 1/Layer 2 Triggered Mobility (LTM), face challenges such as unnecessary resource consumption, increased signaling overhead, and energy consumption due to the new serving cell being unaware of which Timing Advance (TA) timers are still running at the User Equipment (UE) after a cell switch, leading to repeated TA acquisition procedures.
The UE indicates to the network which Timing Advance (TA) timers are still running for candidate cells during or after the cell switch procedure, allowing the network to avoid re-triggering unnecessary TA acquisition for cells with active timers, thereby reducing resource consumption and signaling overhead.
This approach optimizes resource usage and reduces energy consumption by ensuring the network only re-triggers TA acquisition for candidate cells without active timers, thus enhancing the efficiency of cell switch procedures.
Smart Images

Figure IB2025063596_12112026_PF_FP_ABST
Abstract
Description
INDICATING CANDIDATE TIMING ADVANCE VALUES TO NEW SERVING CELL IN LAYER 1 / LAYER 2 TRIGGERED MOBILITY TECHNICAL FIELD
[0001] Embodiments of the present disclosure are directed to wireless communications and, more particularly, to methods for performing a cell switch procedure.BACKGROUND
[0002] This section is intended to provide a background to the various embodiments of the technology described in this disclosure. The description in this section may include concepts that could be pursued but are not necessarily ones that have been previously conceived or pursued. Therefore, unless otherwise indicated herein, what is described in this section is not prior art to the description and / or claims of this disclosure and is not admitted to be prior art by the mere inclusion in this section.
[0003] Layer 1 / Layer 2 Triggered Mobility (LTM) is an inter-cell mobility procedure proposed in 3rd Generation Partnership Project (3GPP) Release 18 to reduce the overall handover latency by leveraging lower layer signaling. To achieve this, the user equipment (UE) is first configured with the radio resource control (RRC) configuration of one or multiple LTM candidate cells. Then the UE performs Layer 1 (LI) reference signal received power (RSRP) measurements on the synchronization signal block (SSBs) (i.e., beams, of the configured LTM candidate cells) and reports the measurement over user control information (UCI) via physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH). The reduction in handover interruption is attained by means of early uplink (UL) and downlink (DL) synchronization with the target cell before the transmission of LTM cell switch medium access control (MAC) control element (CE) command.SUMMARY
[0004] Various computer-implemented systems, methods, and articles of manufacture related to performing cell switch procedures are described herein. In one embodiment, as part of performing a cell switch procedure, a UE can receive, from a first network node (e.g., a serving cell) a request for information about TA values for a second network node (e.g., a target cell or a candidate cell). The UE can also transmit, to the first network node, the information about the TA values for the second network node. Similarly, the first network node can transmit, to the UE, the request for information about the TA values and receive, from the UE, the information about the second network node. These communications can occur after the cell switch procedure is complete.
[0005] In another embodiment, during or after a cell switch procedure, a UE can transmit, to the first network node, the information about the TA values for the second network node. Optionally, the transmission by the UE occurs automatically (i.e., without the UE receiving a request for the information). Likewise, the first network node can receive, from the UE, the information about the TA values for the second network node.BRIEF DESCRIPTION OF THE DRAWINGS
[0006] For a better understanding of the various described embodiments, reference should be made to the Detailed Description below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
[0007] Figure 1 represents an architecture description of early timing advance acquisition in Layer 1 / Layer 2 Triggered Mobility.
[0008] Figure 2A illustrates a flow chart of steps performed by a user equipment, in accordance with some embodiments of the present disclosure.
[0009] Figure 2B illustrates a flow chart of steps performed by first network node, in accordance with some embodiments of the present disclosure.
[0010] Figure 3A illustrates a flow chart of steps performed by a user equipment, in accordance with some embodiments of the present disclosure.
[0011] Figure 3B illustrates a flow chart of steps performed by first network node, in accordance with some embodiments of the present disclosure.
[0012] Figure 4 shows an example of a communication system, in accordance with some embodiments.
[0013] Figure 5 is another example of a communication system, according to some embodiments.
[0014] Figure 6 shows a wireless device, in accordance with some embodiments.
[0015] Figure 7 shows a network node, in accordance with some embodiments.
[0016] Figure 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.DETAILED DESCRIPTION
[0017] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed,unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa.
[0018] Layer 1 / Layer 2 Triggered Mobility (LTM)reduces overall handover latency during cell switches by leveraging lower layer signaling. With LTM, a user equipment (UE) is configured with the radio resource control (RRC) configuration of one or multiple LTM candidate cells, performs Layer 1 (LI) reference signal received power (RSRP) measurements on synchronization signal blocks (SSBs), reports the measurement over user control information (UCI) via physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH). The reduction in handover interruption is attained by means of early uplink (UL) and downlink (DL) synchronization with the target cell before the transmission of a LTM cell switch medium access control (MAC) control element (CE) command.
[0019] The DL pre-synchronization refers to the pre-activation of certain transmission configuration indicator (TCI) states in the LTM candidate cells before any of those cells becomes the target cell. DL pre-synchronization reduces the overall duration required for cellsearch, fine-tracking and acquisition of SSB-based radio resource management (RRM) Measurement Timing Configuration window (SMTC), and SSB post-processing, thus facilitating a faster cell switch.
[0020] The UL pre-synchronization corresponds to the early acquisition of LTM candidate cell timing advance (TA) value before the UE switches to that cell. The early UL synchronization allows the UE to switch to the LTM candidate cell upon receiving the LTM cell switch indication, without any random-access (RA). The UL pre-synchronization procedure is summarized in Figure 1.
[0021] Figure 1 represents an architecture description of early TA acquisition in LTM.Figure 1 illustrates a UE 112, a first gNodeB (gNB) 110A, and a second gNB 110B. In Figure 1, the first gNB 110 is a serving cell, and the second gNB HOB is an LTM candidate cell. As shown, at step 1, serving cell 110A transmits an RRC Reconfiguration to UE 112, which includes the TA acquisition configuration for LTM candidate cell HOB. At step 2, UE 112 transmits an indication to serving cell 110A that the RRC Reconfiguration is complete. At step 3, serving cell 110 transmits a physical downlink control channel (PDCCH) order to UE 112. The PDCCH order can include information about the RA parameters for TA acquisition for LTM candidate cell 110B. At step 4, UE 112 transmits a physical random access channel (PRACH) preamble to LTM candidate cell 110B in accordance with the PDCCH order receivedby UE 112 at step 3. LTM candidate cell HOB calculates the TA values according to the PRACH preamble and sends the TA value to serving cell 110A. In this example, at step 5, the serving cell transmits the TA values to UE 112. This can be done via cell switch MAC CE during the eventual LTM handover execution.
[0022] It is to be noted UE 112 is not required to maintain the TA timer for LTM candidate cell 11 OB in this context. Instead, the network implementation can determine the TA validity.
[0023] Conditional handover (CHO) and the related conditional mobility procedures were introduced in new radio (NR) for improving mobility robustness by preparing the UE (and the CHO candidate cells) in advance before there are any radio link outages. During CHO, the UE is provided the RRC configuration of the candidate CHO cells (e.g., as done in LTM procedures) and some CHO execution conditions. However, unlike in LTM, during CHO, once the CHO executions are fulfilled, the UE can directly perform the handover without sending measurement report to the network. There are additional differences between the legacy CHO and LTM. For example, the CHO does not include the procedure of early synchronization in Release 18.
[0001] To facilitate both the advantages of short handover interruption as well as better robustness, Release 19 aims at introducing Conditional LTM (CLTM) as part of the mobility-related enhancements. The following CLTM-related objectives have been agreed upon in NR mobility enhancements phase 4 work item: specify support of conditional LTM (radio access network (RAN) 2, RAN3, RANI); specify UE evaluated conditions for triggering LTM; and aim to support conditional LTM, including subsequent LTM.
[0002] In CLTM, the UE is configured with the CLTM execution conditions along with the LTM candidate cell configuration. The UE may perform early UL and DL synchronization procedures before the cell switch and shall execute LTM cell switch upon the fulfillment of the provided execution conditions. The CLTM in Release 19 can also be configured with the subsequent LTM executions, in the same way as the subsequent LTM in Release 18.
[0003] There currently exist certain challenges with performing cell switch procedures. For example, upon CLTM execution, the UE performs the following for received TA values and TA timers for candidate cells other than the target candidate cell: maintain the TA value and keep the early TA timer running. That is, the UE can keep the time alignment timer (TAT), if started, for other candidates running at the time a CLTM cell switch is performed. However, even if the UE keeps the TAT running, the new serving cell (to which the cell switch was performed) is not aware of which TATs are still running at the UE and for which candidate cells. Consequently, the new serving cell may re-trigger the TA acquisition procedure for acandidate cell for which the UE has already a TAT running, which can cause unnecessary resource consumption at the network side, increased signaling overhead for both the network side and the UE, and increased energy consumption.
[0004] In accordance with this realization, the methods and systems disclosed herein allow the network, after a cell switch, to be aware of which TATs are still running at the UE and for which candidate cell(s). In particular, the UE can report this information to the network every time a cell switch is executed. In one embodiment, the UE, during the cell switch procedure, indicates to the network which TATs are still running and for which candidate cells the TATs are running. This indication can be transmitted via a message that is part of the cell switch execution procedure (e.g., a RRCReconfigurationComplete message). In another embodiment, after the cell switch procedure is completed, the network can request that the UE report such information. As a result, the network knows which TATs are still running at the UE and for which candidate cells only after the cell switch procedure is executed.
[0005] The methods and systems disclosed herein allow the new serving cell to re-trigger again the TA acquisition procedure for candidate cell(s) only if the UE does not already have a TAT running, which can mitigate the problems discussed above (i.e., the unnecessary resource consumption at the network side, the increased signaling overhead for both the network side and the UE, and the increased energy consumption).
[0006] The text refers to the term “L1 / L2 based inter-cell mobility” as used in the Work Item Description in 3GPP, though it interchangeably uses the terms L1 / L2 mobility, Ll-mobility, LI based mobility, Ll / L2-centric inter-cell mobility, L1 / L2 inter-cell mobility L1 / L2 Triggered Mobility, Lower-layer triggered Mobility, or LTM. The basic principle is that the UE receives a lower layer signaling (e.g., a MAC CE) from the network indicating to the UE a change, switch, or activation of serving cell (e.g., change of primary cell (PCell) from a source to a target PCell). The lower layer signaling is a message or signaling of a lower layer protocol, which may be referred to as a L 1 / L2 inter-cell mobility execution command or LTM cell switch command. The change of serving cell (e.g., change of PCell) may also lead to a change in secondary cells (SCells) for the same cell group — for example, in case the command triggers the UE to change to another cell group configuration of the same type (e.g., another master cell group (MCG) configuration). Before the UE receives the LTM cell switch command, the UE is configured by the network with one or more LTM candidate cells (e.g., via reception of an RRC Reconfiguration message with at least one LTM candidate cell configuration). A candidate cell configuration may include parameters in the information element (IE)CellGroupConfig per candidate cell and / or an embedded RRC Reconfiguration per candidate cell.
[0007] The term LTM cell switch procedure refers to the process of a UE changing its cell from a source cell to a target cell (which can also be referred to as a candidate cell or a neighbor cell), using LTM. In the context of LTM, an LTM cell switch procedure may sometimes also be known as dynamic switch, LTM switch, (LTM) cell switch, (LTM) serving cell change, or (LTM) cell change. Even if the term “change of cell” is used, that may comprise a change of a whole cell group configuration, which includes a change in the special cell (SpCell) (e.g., change of PCell, or change of primary secondary cell (PSCell)) and a change in SCells of the cell group (e.g., addition, modification and / or release of one or more SCells). The LTM cell switch procedure may be triggered by the UE receiving an LTM cell switch command from the network. The source and target cells in a LTM cell switch procedure may be controlled by the same gNB, which sometimes is referred to as the intra-gNB case. In some cases, when the gNB uses a distributed central unit (CU) / distributed unit (DU) RAN architecture, this is referred to as the intra-CU inter-DU case or the intra-CU intra-DU case — depending on whether the cells are controlled by the same DU or different DUs. When the source and target cells in an LTM cell switch procedure are controlled by different gNBs, this can be referred to as an inter-gNB case, an inter-CU case, or an inter-CU LTM cell switch procedure.
[0008] The text refers to at least one LTM candidate cell configuration. This can also be referred to as a configuration of an LTM candidate cell, which may be an RRC configuration, such as encapsulated in an RRC Reconfiguration message, that the UE receives when being configured with LTM. An LTM candidate cell configuration comprises the configuration which the UE needs to start to operate accordingly when the UE performs the LTM cell switch procedure to that LTM candidate cell. That is, an LTM candidate cell configuration comprises the configuration that the UE needs upon reception of the LTM cell switch command indicating the UE to perform a LTM cell switch procedure to that LTM candidate cell, which becomes the target cell and the current (or new) SpCell, or an SCell in a serving frequency. The LTM candidate cell configuration comprises parameters of a serving cell (or multiple serving cells, such as a cell group), comprising one or more of the groups of parameters, such as an RRCReconfiguration message, an IE CellGroupConfig, or an IE SpCellConfig (or the IE sCellConfig, in the case of a Secondary Cell).
[0009] An LTM candidate cell configuration is associated with an identifier which is used in the signaling when referring to a certain LTM candidate cell configuration, such as when the UE receives the LTM candidate cell configuration and when the UE receives an LTM cellswitch command indicating the UE to perform an LTM cell switch procedure to that LTM candidate cell. This identifier is sometimes known as the LTM candidate cell configuration identity, the LTM candidate configuration index, etc.
[0010] An inter-CU LTM cell switch procedure, sometimes also referred to as inter-CU LTM or inter-gNB LTM, is an LTM cell switch procedure resulting in a change of serving cell (e.g., change of SpCell, PCell, PSCell) to an LTM candidate cell controlled by a different gNB than the source gNB or serving gNB of the UE when the execution LTM cell switch procedure was triggered (e.g., upon reception of the LTM cell switch command). From a UE point of view, the actions performed during an inter-CU LTM cell switch procedure may be the same type of actions of an LTM cell switch procedure, but may also include additional actions, such as change of security key(s).
[0011] The text refers to inter Secondary Node LTM, inter-SN LTM, configuration of inter-SN LTM, execution of inter-SN LTM and an inter-SN LTM cell switch procedure. In the context of this disclosure, inter-SN LTM refers to inter-CU LTM, sometimes also referred to as inter-gNB LTM, handover or SCG mobility, when the UE is configured with dual connectivity, such as NR-DC, and where the source cell and target cell are both part of the source and target SCG, respectively, and controlled by different CUs or different gNBs.
[0012] The term conditional LTM refers to LTM where the execution of the LTM cell switch is triggered by the UE when an execution condition, such as a Layer 1, Layer 2 or a Layer 3 event, criterion or condition related to, for example, a radio measurement, is fulfilled. Upon the cell switch, the UE applies a stored LTM candidate cell configuration.
[0013] The text refers to an inter-CU LTM candidate cell configuration. An inter-CU LTM candidate cell configuration is an LTM candidate cell configuration which contains the configuration which the UE needs to start to operate accordingly when it performs an LTM cell switch procedure to an LTM candidate cell which is controlled by a different base station (e.g., gNB) from the current source base station (e.g., serving gNB of the UE). In some cases, the UE may receive an inter-CU LTM candidate cell configuration during configuration of intermaster node (inter-MN) LTM. In some cases, the UE may apply an inter-CU LTM candidate cell configuration during execution of inter-MN LTM.
[0014] An inter-CU LTM candidate cell configuration may be the same as an LTM candidate cell configuration but it may also include additional information than what is included in the LTM candidate cell configuration used for inter-CU cell switch. This additional information may include, at least, information to perform security key refresh (e.g., the RRC IE MasterKeyUpdate or a RRC IE RadioBearerConfig that includes SecurityConfig withSecurity AlgorithmConfig); an indication to perform packet data convergence protocol (PDCP) re-establishment; or an indication to perform a full configuration (e.g., the RRC field fullConfig).
[0015] The text refers to a mobility procedure, configuration of a mobility procedure or execution of a mobility procedure. In the context of this disclosure, a mobility procedure may be LTM, inter-CU LTM, inter-SN LTM, Layer 3 (L3) handover, PCell handover, CHO, CLTM, PSCell change, or conditional PSCell Addition or Change (CP AC). The embodiments described in the disclosure sometimes use the inter-SN LTM as the example. However, many of the examples may also be applied for other mobility procedures, for example, LTM, inter-CU LTM, conditional LTM, or CHO.
[0016] The text refers to a mobility configuration. When the UE has been configured with a mobility configuration, the UE may use the mobility configuration during preparation of a mobility procedure, including measurements (such as RSRP measurements on neighbor or serving cells), triggering and transmission of measurement reports, synchronization towards neighbor cells, evaluation of conditions (e.g., for conditional mobility such as CHO), and during the execution of a mobility procedure (e.g., during the execution of an LTM cell switch procedure, execution of an inter-MN LTM cell switch procedure, or execution of handover).
[0017] A mobility configuration may include one or multiple of the following type of elements, where each element contains a configuration of one aspect of LTM: LTM candidate cell configuration(s); inter-CU LTM candidate cell configuration(s); lower layer information (e.g., physical layer configuration, MAC layer configuration or radio link control (RLC) layer configuration, Cell Group configuration, or serving cell configuration); higher layer information (e.g., RRC protocol parameters such as timer values, PDCP layer configuration, radio bearer configuration, or measurement configuration); configuration of measurements for LTM; configuration for measurement reports for LTM; channel state information (CSI) resource configuration(s) for LTM; CSI report configuration for LTM; configurations of early synchronization procedures (e.g., configurations for DL pre-sync for LTM such as configurations for early TCI state activation, configurations for UL pre-sync for LTM such as configurations for reception of PDCCH ordered triggered preamble transmission and reception of TA, etc.); configurations for the execution of an LTM cell switch procedure for a given LTM candidate cell configuration or inter-CU LTM candidate cell configuration (e.g., whether to perform random access procedure, whether to perform RLC reestablishment, whether to perform MAC reset, or whether to perform PDCP recovery), a timer value, configured UL grants, dedicated RA preambles; configuration which the UE needs to start to operateaccordingly when the UE performs an LTM cell switch procedure to an LTM candidate cell which is controlled by a different base station (e.g., gNB) from the current source base station (e.g., serving gNB of the UE); information to perform security key refresh (e.g., the RRC IE MasterKeyUpdate or a RRC IE RadioBearerConfig that includes SecurityConfig with SecurityAlgorithmConfig; indication to perform a full configuration (e.g., the RRC field fullConfig); indication to perform L2 re-establishment (e.g., an indication to perform PDCP reestablishment for one or multiple bearers; or one or more lists of sk-counters values.
[0018] The term “subsequent LTM,” sometimes also referred to as “subsequent LTM cell switch (procedures),” refers to when the UE performs a first LTM cell switch procedure from a source cell to a first target cell and then performs a second LTM cell switch procedure from the first target cell (which is now the new source cell) to a second target cell, where, between the first and second LTM cell switch procedures there is no RRC reconfiguration of the UE. This implies that the network does not add, remove, or otherwise modify the LTM candidate cell configuration(s) or inter-CU LTM candidate cell configuration(s) in the UE between the two LTM cell switch procedures.
[0019] The text refers also to “handling of the configuration of the mobility procedure.” This is the case where a network node indicates to another network node to configure or not configure a certain procedure (e.g., a mobility procedure) where this indication is in the form of a suggestion. Alternatively, this indication is in the form of a restriction, in which case a network node indicates to another network node whether the another network node is allowed to configure a certain procedure (e.g., a mobility procedure).
[0020] The text uses the term “cell” to identify a location (or coverage) on which the UE is located. However, the term “cell” can also be exchanged without any loss of meaning with the terms “radio resources,” “beams,” “TCI state,” or “telecommunications relay services” (TRS). This is just to clarify that this disclosure does not specifically target a scenario where there is a cell, rather when a UE uses a set of source radio resources and need to switch to a target set of radio resources. In such a case, radio resource can also identify a set of configurations, field, parameters, or ASN.1 structures or IES.
[0021] The text further uses the term MCG to identify a first network node that provides a first connectivity link to the UE and SCG to identify e second network node that provides a second connectivity link to the UE. However, the terms “MCG” and “MN” can be exchanged without any loss of meaning. Likewise, secondary cell group (SCG) and secondary node (SN)can be exchanged without any loss of meaning.
[0022] The term “LTM” or “L1 / L2 triggered mobility” include also the case of Conditional LTM (CLTM), which can be viewed as a form of conditional reconfiguration. In CLTM, the UE is configured with at least one LTM candidate cell (denoted as a CLTM candidate cell), by receiving an LTM candidate cell configuration, as in legacy LTM, and called herein a Conditional LTM candidate cell configuration, and an associated execution condition, denoted as CLTM execution condition. The evaluation of CLTM execution condition associated to a CLTM candidate cell is performed by the assessment of lower layer measurements, such as Layer 1 reference signal received power (Ll-RSRP) and / or SS-RSRP, derived from SSBs and / or CSLRSs of either the source cell and / or an LTM candidate cell. Lower layer measurements, in this context, are measurements reported to support lower layer procedures like beam management, candidate cell TCI state activation / deactivation, early TA acquisition, and link adaptation, and they aren't filtered based on L3 parameters, though there may or may not be some filtering of these measurements based on the other lower layer parameters. The reception of CLTM execution condition may also involve receiving an indication of the condition and / or configuring it with parameters such as event identifier(s), offset(s), threshold(s), reference signal (RS) type, trigger quantity such as RSRP, reference signal received quality (RSRQ) or signal -to-interference-plus-noise ratio (SINR), time-to-trigger (TTT), and so forth.
[0023] In the context of CLTM, the UE relies on evaluating one or two condition(s), referred to as CLTM execution condition(s), LTM execution condition(s), or triggering condition(s), or a combination thereof. And, when the condition(s) for a CLTM candidate cell is fulfilled, the UE performs a cell switch, which may be seen as a kind of LTM execution that is not triggered by the reception of an LTM cell switch command. The cell switch performed by the UE may also be considered as a kind of LTM cell switch, LTM cell switch execution, Conditional LTM cell switch, Conditional LTM execution, CLTM execution, or simply cell switch. According to the methods outlined in the disclosure, upon satisfaction of the execution condition(s), the UE initiates an LTM cell switch. The term LTM cell switch refers to the process of a UE changing its cell from a source cell to a target cell, LTM. In the context of CLTM execution, the text may refer to the serving cell before the LTM cell switch as source cell, old source cell, or previous source cell.
[0024] The text also discusses the concept of an LTM candidate cell within the framework of CLTM. The candidate cell may be referred to as a CLTM candidate cell, CLTM cell, candidate cell, candidate target cell, target cell, LTM candidate cell, LTM cell, or L1 / L2 intercell mobility candidate cell, depending on the context or terminology used in the disclosure.Essentially, the candidate cell denotes a cell to which the UE is directed or switches to in the event of executing a conditional L1 / L2 inter-cell mobility procedure after meeting the associated execution condition(s) and may also be termed as new source cell or next source cell after the LTM cell switch. These cells may also be termed as candidate cells, mobility candidates, non-serving cells, additional cells, candidate target cell, simply target cell or deactivated cells. An LTM candidate cell might also pertain to a candidate cell in a 5G Radio Access Technology like NR or a future 6G Radio Access Technology.
[0025] In some of the methods outlined, the UE receives an LTM candidate cell configuration for CLTM, typically through an RRC Reconfiguration message, which is stored in the UE and applied upon fulfillment of the associated CLTM execution conditions. An LTM candidate cell configuration comprises the configuration which the UE needs to start to operate accordingly when it performs a CLTM execution to that LTM candidate cell (e.g., upon the fulfilment of CLTM execution conditions). A candidate cell configuration may include parameters in the IE CellGroupConfig per LTM candidate cell and / or an embedded RRC Reconfiguration per candidate cell. An LTM candidate cell configuration is associated with an identifier which is used in the signaling when referring to a certain LTM candidate cell configuration, such as when performing the early UL or DL synchronization with that LTM cell. This identifier is sometimes known as the LTM candidate cell configuration identifier (ID), LTM candidate configuration index, etc.
[0026] In the described disclosure, a TA value is obtained for the UE for early UL synchronization. This allows the UE to prevent the transmission of a PRACH preamble, and consequently, the reception of a corresponding Random-Access Response (RAR) message during the access to that target cell and reduce handover interruption. This acquisition facilitates the UE to execute a RACH-less access to the target cell during the handover procedure. In a RACH-less access, the UE has a valid TA for the selected LTM or CLTM candidate cell. In other words, the TA timer for the earlier acquired TA value for an LTM candidate cell is still running or not expired yet.
[0027] In one embodiment, the UE, during the cell switch procedure, indicates to the network which TATs are still running and for which candidate cells the TATs are running. This indication can be transmitted via a message that is part of the cell switch execution procedure (e.g., a RRCReconfigurationComplete message). In another embodiment, after the cell switch procedure is completed, the network can request that the UE report such information. As a result, the network knows which TATs are still running at the UE and for which candidate cells only after the cell switch procedure is executed.
[0028] Figure 2A illustrates a flow chart of steps performed by a user equipment, in accordance with some embodiments of the present disclosure. As shown, method 200A can be executed by a UE to perform a cell switch procedure. In method 200A, the UE, during the cell switch procedure, indicates to the first network node which TATs are still running and for which candidate cells the TATs are running. Accordingly, at step 202A, the UE can receive, from the first network node, a request for information about TA values for a second network node, and at step 204A, the UE can transmit, to the first network node, the information about the TA values for the second network node.
[0029] In some embodiments, steps 202A and 204A occur after the cell switch procedure is complete.
[0030] Figure 2B illustrates a flow chart of steps performed by first network node, in accordance with some embodiments of the present disclosure. As shown, method 200B can be executed by a first network node to perform a cell switch procedure. In particular, method 200B is the same as method 200A. However, method 200A discloses steps performed by the UE, while method 200B discloses steps performed by the first network node.
[0031] At step 202B, the first network node can transmit, to the UE, a request for information about TA values for a second network node. At step 204B, the first network node can receive, from the UE, the information about the TA values for the second network node. In some embodiments, steps 202B and 204B occur after the cell switch procedure is complete.
[0032] Figure 3A illustrates a flow chart of steps performed by a user equipment, in accordance with some embodiments of the present disclosure. As shown, method 300A can be executed by a UE to perform a cell switch procedure. Method 300 A can occur during the cell switch procedure or after the cell switch procedure is completed. The network can request that the UE report which TATs are still running and for which candidate cells the TATs are running. Accordingly, at step 302 A, the UE can transmit, to the first network node, the information about the TA values for the second network node.
[0033] Figure 3B illustrates a flow chart of steps performed by first network node, in accordance with some embodiments of the present disclosure. As shown, method 300B can be executed by a first network node to perform a cell switch procedure. In particular, method 300B is the same as method 300A. However, method 300A discloses steps performed by the UE, while method 300B discloses steps performed by the first network node.
[0034] At step 302B, the first network node can receive, from the UE, the information about the TA values for the second network node.
[0035] The UEs discussed with respect to the methods herein can be configured with at least a mobility configuration and receive a mobility command to perform the cell switch procedure. As will be discussed in greater detail below, the UE retains information about the TA of candidate cells as part of the mobility procedure.
[0036] In the methods discussed above with respect to Figures 2A-3B, the first network node can be a serving cell, a gNB-DU, a gNB-CU, or a gNB to which the UE is executing the cell switch procedure. Furthermore, the second network node can be a candidate cell for the cell switch procedure, such as an LTM candidate cell for an LTM cell switch procedure.
[0037] In the methods discussed herein, the information about TA values for the second network node can include the current TA value of the candidate cell, the TAT value related to the TA of the candidate cell, the current value of the running TAT (if started before the cell switch procedure was executed), or the remaining time of the TAT value (if started before the cell switch procedure was executed). The information can also include an indication that the remaining time of the TAT value is above a threshold value (e.g., in time units) or an indication that the time elapsed of the TAT value is below a threshold value (e.g., in time units). Optionally, the threshold value is received by the UE from the network (e.g., as part of an LTM configuration) and can be applicable for individual candidate cells or a set of candidate cells. Moreover, the information can include an indication that the UE can estimate the TA value for a certain LTM candidate cell by itself. Optionally, the UE is explicitly configured by the network to send this indication for a given LTM candidate cell. Other types of information about TA values for the second network node can include an indication that there is a valid TA for a candidate cell, a candidate cell identifier, an LTM candidate configuration identifier, a gNB-DU ID, an identity of the entity requesting Early RACH resources (e.g., an Early RACH Resources Requester ID, or equivalent), and an identity of the entity providing Early RACH resources (e.g., an Early RACH Resources Provider ID, or equivalent).
[0038] In some embodiments, receiving the request from the first network node for information about TA values for the second network node (e.g., in step 202A in Figure 2A), can include receiving one or more of one or more candidate cell identified s), an indication to include the current TA value of one or more candidate cell(s),an indication to include the value of the TAT for one or more candidate cell(s), an indication to include whether the TAT for one or more candidate cell(s) is still running, an indication to include the remaining time of the TAT for one or more candidate cell(s) , an indication to indicate whether the TA value for one or more candidate cell(s) is still valid,
[0039] In another embodiment, receiving the request from the first network node for information about TA values for the second network node (e.g., in step 202A in Figure 2A), can include receiving an indication to delete the TA information for one or more candidate cell(s). Optionally, the UE receives the request after the UE indicates to the first network node that it has valid TA information for other candidate cells. Optionally, the UE receives the request after a cell switch procedure is completed by the UE, regardless whether the UE has previously indicated that it has valid TA information for other candidate cells. Additionally, if the UE receives the indication to delete the TA information for a candidate cell, the UE can perform one or more of the following actions: stopping the TAT referred to the TA of the candidate cell, deleting the current TA value of the candidate cell from its memory, deleting the TAT value for the TA of the candidate cell from its memory, or determining that there is no valid TA for the candidate cell.
[0040] In some embodiments, when transmitting the information about TA values for the second network node (e.g., in steps 204A and 302A in Figures 2A and 3A), the UE can include a TA value for a candidate cell when the TAT for that candidate cell is running and the remaining time (for expiry) is above a threshold value. This is because if the remaining time is too short, there is limited value to including the TA value in the message to the target cell. In another embodiment, when transmitting the information, the UE can include a TA value for a candidate cell when the TAT for that candidate cell is running and the elapsed time is below a threshold value. This can help preserve resources because if the elapsed time is too long, there is limited value to including the TA value to the target cell.
[0041] In some embodiments, when transmitting the information about TA values for the second network node (e.g., in steps 204A and 302A in Figures 2A and 3A), the UE can include a TA value for a candidate cell when the candidate cell is not configured as a serving cell (e.g., SCell) associated to the target cell (e.g., in the same cell group as the target cell). For example, when the target cell is a PCell, the UE is going to in the LTM Cell Switch and is of MCG, and a candidate cell is one of the SCells in that same MCG, the UE would not need to send the TA value and the TAT to the first network node because the TA value and the TAT would be known or established by the network.
[0042] In other embodiments, when transmitting the information about TA values for the second network node (e.g., in steps 204A and 302A in Figures 2A and 3A), the UE can include an indication for an LTM candidate cell if the UE can estimate the TA value for the LTM candidate cell by itself after the cell switch. That is, once the UE moves to the new serving cell after LTM execution, the UE may be able to estimate the TA value for a certain LTM candidatecell by itself. In this case, the UE indicates this to the first network node. Optionally, the UE sends this indication for all the LTM candidate cells for which the UE can estimate the TA value by itself after performing the LTM execution to the new serving cell. Optionally, the UE sends this indication only for those LTM candidate cells for which the UE received TA value from the network while being in the old serving cell and the TA value is still valid. Optionally, the UE sends this indication only for those LTM candidate cells for which the UE received TA value from the network while being in the old serving cell, the TA value is still valid, and the time elapsed of the TA validity is below a pre-defined threshold. Optionally, the UE sends this indication only for those LTM candidate cells for which the UE received TA value from the network while being in the old serving cell, the TA value is still valid, and the remaining time in the expiry of TA validity is above a pre-defined threshold.
[0043] The UE consider a TA for a candidate cell still valid if one or more of the following conditions are fulfilled: the TAT for the TA of the candidate cell is still running or the remining time of the TAT for the TA of the candidate cell is not equal to less than zero.
[0044] In another embodiment, the UE determines to provide TA value and the related TAT information for an LTM candidate cell if the TA value is not equivalent to zero ( i.e., TA ^0) to update the first network node. For example, when the TA=0 for an LTM candidate cell (e.g., LTM candidate cell is a small cell), the UE is not required to send the TA value and the related TAT information for the LTM candidate cell, since the TA value and the related TAT information would likely be known by the network by implementation.
[0045] In one embodiment, when transmitting the information about TA values for the second network node (e.g., in steps 204A and 302A in Figures 2A and 3A), the UE can include information about TA value of a candidate cell (e.g., the UE would include one or more of the remaining time of the TAT value, or any combination of the above information about TA value) if the UE received an LTM Cell switch command MAC CE from the network. That is, the UE can include information about TA value of a candidate cell in case an LTM (and not a CLTM) was triggered. Optionally, the included information about TA value only refers to the candidate cell used as target for non-conditional LTM cell switch execution. Optionally, the included information about TA value refers to other candidate cells, excluding the cell towards which the LTM cell switch execution was initiated. Optionally, the included information about TA value refers to all the candidate cells, for which the TA value is not outdated, i.e., cells for which the TA value is still valid. Optionally, the included information about TA value refers to all the candidate cells, for which the TA value is not outdated, and the elapsed time is abovea threshold. Optionally, the included information about TA value refers to all the candidate cells, for which the TA value is not outdated, and the elapsed time is below a threshold.
[0046] In other embodiments, when transmitting the information about TA values for the second network node (e.g., in steps 204A and 302A in Figures 2A and 3A), the UE can include information about TA value of a candidate cell (e.g., the UE can include one or more of the remaining time of the TAT value, or any combination of the above information about TA value) if the UE initiated a CLTM Cell switch execution, and the procedure failed.
[0047] In yet other embodiments, when transmitting the information about TA values for the second network node (e.g., in steps 204A and 302A in Figures 2A and 3A), the UE can include information about TA value of a candidate cell (e.g., the UE can include one or more of the remaining time of the TAT value, or any combination of the above information about TA value) if the CLTM Cell switch execution failed, and a fast recovery is attempted.
[0048] In some embodiments, methods 200 A and 300 A further include receiving, from the first network node, an additional request for information about TA values for a third network node and transmitting, to the first network node, the information about the TA values for the third network node. Optionally, the information about the TA values for the second network node and the information about the TA values for the third network node comprise identifiers for the second network node and the third network node. Optionally, the UE sends all the information related to the TA of other candidate cells (e.g., the second network node and the third network node) to the first network node all in response to the initial request for information. In this method the UE, as part of the cell switch procedure, informs the first network node (which is the node to which the UE is performing the cell switch) about the TA information of other candidate cell autonomously. Consequently, as long as the UE has a valid TA for another candidate cell (or as long as the TA value for another candidate cell is not outdated), the UE will send this information to the first network node. In another option, the UE only indicates the availability of TA information for other candidate cells in response to the initial request for information. In this case, the UE informs the first network node that the UE has some TA values which are still valid for one or more candidate cells, but then the UE permits the first network node to choose whether to receive the information.
[0049] In embodiments where the UE receives an initial request and an additional request for information about TA values for candidate cells, the UE can transmit the requested information according to one or more of the following signaling options: a new or existing RRC message, a new or existing MAC CE, or a new or existing LI signaling (e.g., UCI).
[0050] In some embodiments disclosed herein, after the first network node receives the information about the TA values for the second network node from the UE (e.g., step 204B and step 302B in Figures 2B and 3B), the first network node can trigger, again, the TA acquisition procedure for a candidate cell at the UE. The first network node can decide to re-trigger the TA acquisition if the value of the TAT related to the TA is below a threshold, if the remaining value of the TAT related to the TA is below a threshold, if the last executed action related to mobility is an LTM cell switch (and not a CLTM cell switch), if the last executed action related to mobility is a fast recovery after a failed LTM cell switch (or after a failed CLTM cell switch), if the UE cannot estimate TA value for an LTM candidate cell by itself. Optionally, the first network node can make this decision regardless of the TA information received for the candidate cell.
[0051] In other embodiments, after the first network node receives the information about the TA values for the second network node from the UE (e.g., step 204B and step 302B in Figures 2B and 3B), the first network node can transmit, to the UE, a request to delete the TA information for one or more candidate cell. This can be applicable where, for example, the network decides not to perform a RACH-less cell switch procedure to one or more candidate cell and, thus, requests that the UE delete the TA information that the UE has stored.
[0052] In other embodiments, after the first network node receives the information about the TA values for the second network node from the UE (e.g., step 204B and step 302B in Figures 2B and 3B), the first network node does not perform any action. For instance, the network acknowledges that the UE has TA information for one or more candidate cells (and, thus, that the UE can potentially do a RACH-less cell switch procedure) but decides not to maintain such TA for the one or more candidate cells. As a result, when the TA for the one or more candidate cells expires, the network may not trigger another TA acquisition procedure and, thus, the possible cell switch will be RACH-based.
[0053] In some embodiments, the first network node transmits, to the UE, a request for information about the TA values for the second network node (e.g., in step 204B in Figure 2B) based on one or more of the following: whether the existing TA value(s) for one or more candidate cell(s) exceed a predefined threshold; whether the existing TA value(s), adjusted by a predetermined offset, exceed a predefined threshold; whether a change in cell group has occurred; whether a predetermined time interval has elapsed since the last TA report; whether TA information for one or more candidate cells is unavailable, outdated, or invalid; or whether the UE can estimate the TA value by itself.
[0054] Figure 4 shows an example of a communication system 400 in accordance with some embodiments.
[0055] In the example, the communication system 400 includes a telecommunications network 402 that includes an access network 404, such as a radio access network (RAN), and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes or base stations of various types, access network nodes 410A and 410B are depicted (which may be collectively referred to as network nodes 410), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 404 may include more than one access network technology. The network nodes 410 of access network 404 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 412A, 412B, 412C, and 412D (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections.
[0056] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 402 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 402 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 402, including one or more access network nodes 410 and / or core network nodes 408.
[0057] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network nodemay be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.
[0058] The network nodes 410 facilitate direct or indirect connection of one or more UEs 412 to the core network 406 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 400 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 400 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0059] The UEs 412 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 410 and other communication devices. Similarly, the network nodes 408, 410 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 402) with the UEs 412 and / or with other network nodes or equipment in the telecommunications network 402 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 402. More specifically, UEs 412 may send messages, data, and / or other signals to network nodes 408, 410 or other elements of the telecommunications network 402 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 408, 410 may send messages, data, and other signals to UEs 4122, other network nodes 408, 410, and other devices in telecommunications network 402 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 412 by transmitting the message to an access network node 410 that will then transmit the message to the intended UE 412. Similarly, a core network node 108 may receive a particular message from a UE 412 byreceiving the message from an access network node 410 that itself received the message from the UE 412.
[0060] In the depicted example, the core network 406 connects elements of the access network 404 (e.g., one or more of the network nodes 410) to one or more host computing systems, such as host 416. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 406 includes one or more core network nodes (e.g., core network node 408) of various types, one or more of which may be generally referred to as network nodes 408. Network nodes 408 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 408. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).
[0061] The host 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and / or the telecommunications network 402. The host 416 may be operated by the service provider or on behalf of the service provider. The host 416 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0062] As a whole, the communication system 400 of Figure 4 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 400 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical andElectronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 400 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 400 supporting different standards, protocols, or rule sets.
[0063] As one example, in certain embodiments, access network 404 may contain some access network nodes 410 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 410 support (or the same access network nodes 410 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 402 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.
[0064] Telecommunications network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 402. For example, the telecommunications network 402 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.
[0065] In some examples, one or more of the UEs 412 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404. Additionally, a UE may be configured for operating in single- or multi-RAT or multi -standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
[0066] In the example, the hub 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE 412C and / or 412D) and networknodes (e.g., network node 410B). In some examples, the hub 414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 414 may be a broadband router enabling access to the core network 406 for the UEs. As another example, the hub 414 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 410, or by executable code, script, process, or other instructions in the hub 414.
[0067] As another example, the hub 414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 414 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 414 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0068] The hub 414 may have a constant / persistent or intermittent connection to the network node 410B. The hub 414 may also allow for a different communication scheme and / or schedule between the hub 414 and UEs (e.g., UE 412C and / or 412D), and between the hub 414 and the core network 406. In other examples, the hub 414 is connected to the core network 406 and / or one or more UEs via a wired connection. Moreover, the hub 414 may be configured to connect to an M2M service provider over the access network 404 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 410 while still connected via the hub 414 via a wired or wireless connection. In some embodiments, the hub 414 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 410B. In other embodiments, the hub 414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 410B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0069] Figure 5 is another example of a communication system 500 according to some embodiments. As used herein, the communication system 500 includes multiple access points (APs) 510 (with four exemplary APs 510A, 510B, 510C, and 510D being depicted) and multiple wireless devices, referred to in the context of communication system 500 as stations(STAs) 512 (referred to individually as STA 512A, STA 512B, STA 512C, STA 512D, and STA 512E). STA 512A is served by AP 510A in a first basic service set (BSS) 520A. STA 510B and STA 510C are served by AP 510B in a second BSS, BSS 520B. STA 512D is served by AP 510C in a third BSS, BSS 520C. STA 512E is served by AP 510D in a fourth BSS, BSS 520D. Stations 512 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 512 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.
[0070] Each of STAs 512 may connect through a radio link to one of APs 510. For example, depending on location or channel conditions experienced by a given STA 512, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.
[0071] Each AP 510 may provide data connectivity to STAs 512 connected to a particular AP 510. As illustrated, APs 510 may be connected to a data network 530. In this way, APs 510 may also provide data connectivity between STAs 512 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 512 and its serving AP 510 may be used for providing various kinds of services to STA 512, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 512 and / or on a device linked to STA 512. By way of example, Figure 5 illustrates an application service platform 532 provided in data network 530. The application(s) executed on STA 512 and / or on one or more other devices linked to STA 512 may use the radio link for data communication with one or more other STA 512 and / or the application service platform 532, thereby enabling utilization of the corresponding service(s) at STA 512.
[0072] Figure 6 shows a wireless device 600, which may be configured to operate in communication system 400 of Figure 4 or in communication system 500 of Figure 5. The wireless device 600 may be alternatively referred to as a UE 600, like a UE 412 within the context of communication system 400, or as a station (STA) 600 or as a non-access-point station (non-AP STA) 600, like a STA 512 within the context of the communication system500, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop -embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0073] A wireless device 600 may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 600 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 600 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 600 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0074] In particular embodiments, wireless device 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input / output interface 606, a power source 608, a memory 610, a communication interface 612, and / or any other component, or any combination thereof. Certain embodiments of wireless device 600 may include all or a subset of the components shown in Figure 6. The level of integration between the components may vary from one embodiment of wireless device 600 to another. In general, in a particular embodiment of wireless device 600, processing circuitry 602, input / output interface 606, power source 608, memory 610, and communication interface 612 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 600. Further, certain embodiments of wireless devices 600 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0075] The processing circuitry 602 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 610. The processing circuitry 602 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 602 may include multiple central processing units (CPUs).
[0076] In the example, the input / output interface 606 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 600. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
[0077] In some embodiments, the power source 608 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 608 may further include power circuitry for delivering power from the power source 608 itself, and / or an external power source, to the various parts of wireless device 600 via input circuitry or an interface such as an electrical power cable. Power source 608 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 600 to which power is supplied.
[0078] The memory 610 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory(PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 610 includes one or more programs 614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 616. The memory 610 may store, for use by wireless device 600, any of a variety of various operating systems or combinations of operating systems.
[0079] The memory 610 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 610 may allow wireless device 600 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 610, which may be or comprise a device-readable storage medium.
[0080] The processing circuitry 602 may be configured to communicate with an access network or other network via or using the communication interface 612. The communication interface 612 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 622. The communication interface 612 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 618 and / or a receiver 620 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 618 and receiver 620 may be coupled to one or more antennas (e.g., antenna 622) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0081] In the illustrated embodiment, communication functions of the communication interface 612 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0082] In particular embodiments, wireless device 600 may provide an output of data captured via a sensor, through its communication interface 612, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 600 can be communicated through a wireless connection to a network node via another wireless device 600. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0083] As another example, wireless device 600 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 600 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
[0084] Wireless device 600, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, athermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 600 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 600 shown in Figure 6.
[0085] As yet another specific example, in an loT scenario, wireless device 600 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 600 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 600 may implement the 3 GPP NB-IoT standard. In other scenarios, wireless device 600 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.
[0086] In practice, any number of wireless devices 600 may be used together with respect to a single use case. For example, a first wireless device 600 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 600 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 600 may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 600 can also include more than one of the functionalities described above. For example, wireless device 600 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0087] Figure 7 shows a network node 700 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 700 may be configured to operate in communication system 400 of Figure 4, like networknodes 408 or 410, or in communication system 500 of Figure 5, like an AP 510 or a station 512. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, O-DU, O-CU).
[0088] Network nodes 700 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 700 may be a relay node or a relay donor node controlling a relay. Network nodes 700 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0089] Other examples of network nodes 700 include multiple transmission point (multi-TRP) 5G access nodes, multi -standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0090] In particular embodiments, network node 700 includes a processing circuitry 702, a memory 704, a communication interface 706, and a power source 708. In general, in a particular embodiment of network node 700, processing circuitry 702, memory 704, communication interface 706, and power source 708 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 700.
[0091] The network node 700 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 700 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In some embodiments, the network node 700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 704 or portions of memory 704 for different RATs) and some components may be reused (e.g., a same antenna 710 may be shared by different RATs). The network node 700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 700, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 700.
[0092] The processing circuitry 702 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 704, to provide network node 700 functionality.
[0093] In some embodiments, the processing circuitry 702 includes a system on a chip (SOC). In some embodiments, the processing circuitry 702 includes one or more of radio frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714. In some embodiments, the RF transceiver circuitry 712 and the baseband processing circuitry 714 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 712 and baseband processing circuitry 714 may be on the same chip or set of chips, boards, or units.
[0094] The memory 704 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 702. The memory 704 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 702 and utilized by the network node 700. The memory 704 may be used to store anycalculations made by the processing circuitry 702 and / or any data received via the communication interface 706. In some embodiments, the processing circuitry 702 and memory 704 is integrated.
[0095] The communication interface 706 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 706 comprises port(s) / terminal(s) 716 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 600 may be capable of wireless communication and communication interface 706 may also include radio front-end circuitry 718 that may be coupled to, or in certain embodiments a part of, an antenna 710. Particular embodiments of radio front-end circuitry 718 include filter(s) 720 and amplifier(s) 722. The radio front-end circuitry 718 may be connected to an antenna 710 and processing circuitry 702. The radio frontend circuitry may be configured to condition signals communicated between antenna 710 and processing circuitry 702. The radio front-end circuitry 718 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 718 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 720 and / or amplifiers 722. The radio signal(s) may then be transmitted via the antenna 710. Similarly, when receiving data, the antenna 710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 718. The digital data may be passed to the processing circuitry 702. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0096] In certain alternative embodiments, network node 700 may be capable of wireless communication but does not include separate radio front-end circuitry 718, instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes one or more ports or terminals 716, the radio front-end circuitry 718, and the RF transceiver circuitry 712, as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown).
[0097] The antenna 710 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 710 may be coupled to the radio front-end circuitry 718 and may be any type of antenna capable of transmitting and receiving data and / orsignals wirelessly. In certain embodiments, the antenna 710 is separate from the network node 700 and connectable to the network node 700 through one or more interfaces or ports.
[0098] The antenna 710, communication interface 706, and / or the processing circuitry 702 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 700. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 710, the communication interface 706, and / or the processing circuitry 702 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 700. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0099] The power source 708 provides power to the various components of network node 700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 700 with power for performing the functionality described herein. For example, the network node 700 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 708. As a further example, the power source 708 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0100] Embodiments of the network node 700 may include additional components beyond those shown in Figure 7 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 700 may include user interface equipment to allow input of information into the network node 700 and to allow output of information from the network node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 700.
[0101] Figure 8 is a block diagram illustrating a virtualization environment 800 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relatesto an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 800 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
[0102] Applications 802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 700 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0103] Hardware 804 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 808A and VM 808B (which may be collectively referred to as VMs 808), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 806 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 808.
[0104] The VMs 808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 806. Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of VMs 808, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
[0105] In the context of NFV, each of the VMs 808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 808, and that part of hardware 804 that executes that VM, be ithardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 808 on top of the hardware 804 and corresponds to an application 802.
[0106] Hardware 804 may be implemented in a standalone network node with generic or specific components. Hardware 804 may implement some functions via virtualization. Alternatively, hardware 804 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 810, which, among others, oversees lifecycle management of applications 802. In some embodiments, hardware 804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 812 which may alternatively be used for communication between hardware nodes and radio units.
[0107] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensivefunctions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0108] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.REFERENCESE RP-241515, New WID: NR mobility enhancements Phase 4, 3GPP TSG RAN Meeting #104, Shanghai, China, June 17-20, 2024.2. 3GPP GPP TS 38.331, V18.5.1, (2025-3); 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 18).APPENDIXAt least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).
Claims
What is claimed is:
1. A method by a user equipment, UE, for performing a cell switch procedure, the method comprising:receiving, from a first network node, a request for information about timing advance, TA, values for a second network node; andtransmitting, to the first network node, the information about the TA values for the second network node.
2. The method of Claim 1, wherein the first network node comprises a serving cell.
3. The method of either of Claims 1 or 2, wherein the first network node comprises a gNodeB distributed unitgNB-DU; a gNB central unit, gNB-CU; or a gNB to which the UE is executing the cell switch procedure.
4. The method of any of Claims 1 through 3, wherein the second network node comprises a candidate cell for the cell switch procedure.
5. The method of any of Claims 1 through 4, wherein the second network node comprises a layer 1 / layer 2 triggered mobility, LTM, candidate cell for an LTM cell switch procedure.
6. The method of any of Claims 1 through 5, wherein the information about the TA values for the second network node comprises time alignment timer, TAT, values for the second network node.
7. The method of any of Claims 1 through 6, wherein receiving, from the first network node, the request for information about TA values for the second network node and transmitting, to the first network node, the information about the TA values for the second network node occur after completion of the cell switch procedure towards the first network node.
8. The method of any of Claims 1 through 7, wherein transmitting, to the first network node, the information about the TA values for the second network node occurs whena TAT for the second network node is running and a remaining time for the TAT is above a threshold time.
9. The method of any of Claims 1 through 8, wherein transmitting, to the first network node, the information about the TA values for the second network node occurs when a TAT for the second network node is running and an elapsed time for the TAT is below a threshold value.
10. The method of any of Claims 1 through 9, wherein transmitting, to the first network node, the information about the TA values for the second network node occurs if the TA values are nonzero values.
11. The method of any of Claims 1 through 10, further comprising:before receiving, from the first network node, the request for information about the TA values for the second network node, receiving a mobility command to perform the cell switch procedure towards the second network node.
12. The method of any of Claims 1 through 11, further comprising:before receiving, from the first network node, the request for information about TA values for the second network node, transmitting, to the first network node, an indication that the UE has valid information about the TA values for the second network node.
13. The method of any of Claims 1 through 12, further comprising:receiving, from the first network node, an LTM cell switch command Medium Access Control, MAC, Control Element, CE.
14. The method of Claim 13, wherein transmitting, to the first network node, the information about the TA values for the second network node occurs in response to receiving, from the first network node, the LTM cell switch command MAC CE.
15. The method of any of Claims 1 through 14, further comprising:transmitting, to the first network node, an indication for the second network node if the UE can estimate the TA values for the second network node after performing the cell switch procedure.
16. The method of any of Claims 1 through 15, further comprising:receiving, from the first network node, an additional request for information about TA values for a third network node; andtransmitting, to the first network node, the information about the TA values for the third network node.
17. The method of Claim 16, wherein the information about the TA values for the second network node and the information about the TA values for the third network node comprise identifiers for the second network node and the third network node.
18. A method by a first network node for a cell switch procedure, the method comprising:transmitting, to a user equipment, UE, a request for information about timing advance, TA, values for a second network node; andreceiving, from the UE, the information about the TA values for the second network node.
19. The method of Claim 18, wherein the first network node comprises a serving cell.
20. The method of either of Claim 18 or 19, wherein the first network node comprises a gNodeB distributed unit, gNB-DU; a gNB central unit, gNB-CU; or a gNB to which the UE is executing the cell switch procedure.
21. The method of any of Claims 18 through 20, wherein the second network node comprises a candidate cell for the cell switch procedure.
22. The method of any of Claims 18 through 21, wherein the second network node comprises a layer 1 / layer 2 triggered mobility, LTM, candidate cell for an LTM cell switch procedure.
23. The method of any of Claims 18 through 22, wherein the information about the TA values for the second network node comprises time alignment timer, TAT, values for the second network node.
24. The method of any of Claims 18 through 23, wherein transmitting, to the UE, the request for information about TA values for the second network node and receiving, from the UE, the information about the TA values for the second network node occur after completion of the cell switch procedure towards the first network node.
25. The method of any of Claims 18 through 24, further comprising:before transmitting, to the UE, the request for information about TA values for the second network node, receiving, from the UE, an indication that the UE has valid information about the TA values for the second network node.
26. The method of any of Claims 18 through 25, further comprising:transmitting, to the UE, an LTM cell switch command medium access control element, MAC CE.
27. The method of Claim 26, wherein receiving, from the UE, the information about the TA values for the second network node occurs in response to transmitting, to the UE, the LTM cell switch command MAC CE.
28. The method of any of Claims 18 through 27, further comprising:transmitting, to the UE, an additional request for information about TA values for a third network node; andreceiving, from the UE, the information about the TA values for the third network node.
29. The method of Claim 28, wherein the information about the TA values for the second network node and the information about the TA values for the third network node comprise identifiers for the second network node and the third network node.
30. The method of Claim 28, wherein transmitting, to the UE, the request for information about TA values for the third network node occurs if the TA values for the second network node exceed a threshold.
31. The method of Claim 28, wherein transmitting, to the UE, the request for information about TA values for the third network node occurs after a time interval that follows receiving, from the UE, the information about the TA values for the second network node.
32. The method of any of Claims 18 through 31, further comprising:transmitting, to the UE, an additional request to delete the information about the TA values for the second network node.
33. A method by a user equipment, UE, for performing a cell switch procedure, the method comprising:transmitting, to a first network node, information about timing advance, TA, values for a second network node.
34. The method of Claim 33, wherein the information about the TA values for the second network node comprises an indication of availability of the information.
35. The method of either of Claims 33 or 34, wherein transmitting, to the first network node, the information about the TA values for the second network node occurs during execution of the cell switch procedure.
36. The method of any of Claims 33 through 35, wherein transmitting, to the first network node, the information about the TA values for the second network node occurs after completion of the cell switch procedure.
37. The method of any of Claims 33 through 36, further comprising:receiving, from the first network node, a request for additional information about the TA values for the second network node; andtransmitting, to the first network node, the additional information about TA values for the second network node.
38. The method of Claim 37, wherein transmitting, to the first network node, the information about the TA values for the second network node comprises transmitting the information and the additional information.
39. A method by a first network node for a cell switch procedure, the method comprising:receiving, from a user equipment, UE, information about timing advance, TA, values for a second network node.
40. The method of Claim Error! Reference source not found., wherein the i nformation about the TA values for the second network node comprises an indication of availability of the information.
41. The method of either of Claims Error! Reference source not found, or 40, w herein receiving, from the UE, the information about the TA values for the second network node occurs during execution of the cell switch procedure.
42. The method of any of Claims Error! Reference source not found, through 41, w herein receiving, from the UE, the information about the TA values for the second network node occurs after completion of the cell switch procedure towards the first network node.
43. The method of any of Claims Error! Reference source not found, through 42, f urther comprising:transmitting, to the UE, a request for additional information about the TA values for the second network node; andreceiving, from the UE, the additional information about TA values for the second network node.
44. The method of Claim 43, wherein receiving, from the UE, the information about the TA values for the second network node comprises receiving the information and the additional information.
