Selecting to execute layer 1 / layer 2 triggered mobility, conditional handover, or conditional layer 1 / layer 2 triggered mobility upon a failure

Abstract

A user equipment (UE) can select to execute layer 1 / layer 2 triggered mobility ("LTM"), conditional handover ("CHO"), or conditional LTM ("CLTM") upon a failure The UE can determine (310) configuration information for a candidate cell including a plurality of candidate cell configuration types. The UE can detect (320) a radio related failure and, responsive to the radio related failure, select (330) the candidate cell as a target cell. The UE can further select (340) a first candidate cell configuration type of the plurality of candidate cell configuration types based on a rule. The UE can further apply (350) a portion of the configuration information for the candidate cell having the first candidate cell configuration type.

Description

SELECTING TO EXECUTE LAYER 1 / LAYER 2 TRIGGERED MOBILITY, CONDITIONAL HANDOVER, OR CONDITIONAL LAYER 1 / LAYER 2 TRIGGERED MOBILITY UPON A FAILURETECHNICAL FIELD

[0001] The present disclosure is related to wireless communication systems and more particularly to selecting to execute layer 1 / layer 2 triggered mobility (“LTM”), conditional handover (“CHO”), or conditional LTM (“CLTM”) upon a failure.BACKGROUND

[0002] FIG. 1 illustrates an example of a new radio (“NR”) network (e.g., a 5th Generation (“5G”) network) including a 5G core (“5GC”) network 130, network nodes 120a-b (e.g., 5G base station (“gNB”)), multiple communication devices 110 (also referred to as user equipment (“UE”)).

[0003] Layer 1 (“Ll”) / Layer 2 (“L2”)-Triggered Mobility (“LTM”) can be defined as a Primary Cell (“PCell”) (or primary secondary cell (“PSCell”)) cell switch procedure, consequently with Cell Group change (e.g., Master Cell Group (“MCG”) or Secondary Cell Group (“SCG”) that the network triggers via media access control (“MAC”) Control Element (“CE”) based on LI measurements. In that procedure, a gNodeB (“gNB”) receives the LI measurement report(s) from the UE, and on their basis the gNB changes UE’s serving cell by a cell switch command signaled via a MAC CE. The cell switch command indicates an LTM candidate cell configuration that the gNB previously prepared and provided to the UE through RRC signaling. Then the UE switches to the target cell according to the cell switch command.

[0004] LTM supports both intra-gNB -distributed unit (“DU”) and intra-gNB-central unit (“CU”) inter-gNB-DU mobility. LTM supports both intra-frequency and inter-frequency mobility, including mobility to inter-frequency cell that is not a current serving cell. LTM is supported only for licensed spectrum. A cell switch command can be conveyed in a MAC CE, which contains the necessary information to perform the LTM cell switch.SUMMARY

[0005] According to some embodiments, a method of operating a user equipment, UE, is provided. The method includes determining configuration information for a candidate cell including a plurality of candidate cell configuration types. The method further includes detecting a radio related failure. The method further includes, responsive to the radio related failure, selecting the candidate cell as a target cell. The method further includes selecting a firstcandidate cell configuration type of the plurality of candidate cell configuration types based on a rule. The method further includes applying a portion of the configuration information for the candidate cell having the first candidate cell configuration type.

[0006] According to other embodiments, a communication device, a computer program, computer program product, non-transitory computer readable medium, host, or system is provided to perform one of the above methods.

[0007] Certain embodiments may provide one or more of the following technical advantages. In some embodiments, the UE actions upon failure detection are as close as possible to the actions as if a failure would have not happened.

[0008] Without the one or more rules for selecting a suitable cell, there may be multiple suitable cells, wherein some may be LTM candidate cells, some CHO candidates, some CLTM candidates, some LTM, CLTM and CHO candidate cells, and some may not, and it is not specified which of the cells among the suitable cells the UE shall select. In other words, the criteria which configuration to apply (e.g., LTM, CLTM or CHO), if multiple are available, for a selected cell is left to UE implementation. Some embodiments herein define one or more rules that allow the UE to select a cell that is either optimal (or sub-optimal) so that further failures can be avoided and the connectivity interruption for the failure which has caused the cell selection is as short as possible.

[0009] In additional or alternative embodiments, the one or more rules enable the UE to save power / energy, by helping the UE avoid exchanging unnecessary signaling between the UE and the network (e.g., in case an LTM cell switch, CLTM, cell switch, CHO execution, or handover occurs shortly after the fast recovery, which would have indicated that the applied configuration for the selected cell was not the best). Mobility procedures shortly after fast recovery are an indication that the applied configuration for the selected cell, even though suitable, is not the best, which can mean some risk of radio link failures, handover failures, LTM cell switch failures, CLTM cell switch failures, or CHO execution failures shortly after the fast recovery.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0011] FIG. 1 is a schematic diagram illustrating an example of a 5thgeneration (“5G”) network;

[0012] FIG. 2 is a signal flow diagram illustrating an example of configuring a UE with LTM;

[0013] FIG. 3 is a flow chart illustrating an example of operations performed by a user equipment, UE, in accordance with some embodiments;

[0014] FIG. 4 is a block diagram of a communication system in accordance with some embodiments;

[0015] FIG. 5 is a block diagram of another communication system in accordance with some embodiments;

[0016] FIG. 6 is a block diagram of a user equipment in accordance with some embodiments;

[0017] FIG. 7 is a block diagram of a network node in accordance with some embodiments; and

[0018] FIG. 8 is a block diagram of a virtualization environment in accordance with some embodiments.DETAILED DESCRIPTION

[0019] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present / used in another embodiment.

[0020] FIG. 2 illustrates an example of an overall procedure for LTM. At block 210, the UE sends a MeasurementReport message to the gNB. The gNB decides to configure LTM and initiates candidate cell(s) preparation. At block 220, the gNB transmits an RRCReconfiguration message to the UE including the LTM candidate cell configurations of one or multiple candidate cells. At block 230, the UE stores the LTM candidate cell configurations and transmits an RRCReconfigurationComplete message to the gNB. At block 240a, the UE performs DL synchronization with the candidate cell(s) before receiving the cell switch command. At block 240b, the UE performs UL synchronization with the candidate cell(s) before receiving the cell switch command. At block 250, the UE performs LI measurements on the configured candidate cell(s) and transmits LI measurement reports to the gNB. LI measurement may be performed aslong as RRC reconfiguration (at block 220) is applicable. At block 260, the gNB decides to execute cell switch to a target cell and transmits a MAC CE triggering cell switch by including the candidate configuration index of the target cell. The UE switches to the target cell and applies the configuration indicated by candidate configuration index. At block 270, the UE performs the random access procedure towards the target cell, if UE does not have valid Timing Advance (“TA”) of the target cell. The UE performs Contention Free Random Access (“CFRA”) if the LTM cell switch command MAC CE contains information for CFRA. At block 280, the UE completes the LTM cell switch procedure by sending RRCReconfigurationComplete message to target cell. If the UE has performed a RA procedure (at block 270) the UE considers that LTM cell switch execution is successfully completed when the random access procedure is successfully completed. For RACH-less LTM, the UE considers that LTM cell switch execution is successfully completed when the UE determines that the network has successfully received its first UL data. The UE determines successful reception of its first UL data by receiving a PDCCH addressing the UE’s C-RNTI in the target cell, which schedules a new transmission following the first UL data. The PDCCH carries either a DL assignment or an UL grant addressing the same HARQ process as the first UL data.

[0021] A conditional LTM (“CLTM”) is described below.

[0022] LTM was introduced in Rel-18 and can offer improvements in handover latency and interruption time compared to Layer 3 based mobility. However, LTM as introduced in Rel-18 also has a number of limitations compared to Layer 3 mobility. The Rel-19 work item aims to remove a number of these limitations. Layer 3 mobility has evolved over several releases. A conditional handover (“CHO”) and other conditional mobility procedures (e.g., conditional primary secondary cell (“PSCell”) addition or change (“CP AC”) or SCPAC) were developed to achieve high robustness by enabling the procedure to be executed without necessitating a signaling exchange with source cell beforehand. LTM as introduced in Rel-18 offers short interruption time but not with the same level of robustness as the conditional L3 mobility procedures. In Rel-19, enhancements can be specified so that the system can benefit from both the high robustness and short interruption.

[0023] In Release 16, CHO was specified. CHO may be defined as a handover that is executed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution condition(s) upon receiving the CHO configuration, and stops evaluating the execution condition(s) once a handover is executed.

[0024] As in LTM, the CHO configuration contains the configuration of CHO candidate cell(s) generated by the candidate gNB(s) and execution condition(s) generated by the sourcegNB. Thus, as in LTM, the UE is also configured with a so-called candidate cell, in this case, a CHO candidate cell.

[0025] A CHO candidate cell configuration may be represented by an RRC Reconfiguration message which is applied when the UE performs a CHO execution procedure, upon fulfillment of the CHO execution condition. Such CHO execution condition may consist of one or two trigger condition(s) (CHO events A3 / A5). Only single RS type is supported and at most two different trigger quantities (e.g., RSRP and RSRQ, RSRP and SINR, etc.) can be configured simultaneously for the evaluation of CHO execution condition of a single candidate cell.

[0026] Fast Failure recovery for CHO is a procedure in which a UE, configured with one or more CHO candidate cell(s), detects a failure (e.g., RLF, handover failure, CHO execution failure), initiates re-establishment, performs cell selection and, when the selected cell is a configured CHO candidate cell, the UE performs a CHO execution instead of continuing with the re-establishment procedure. The network enables that by configuring the parameter ‘attemptCHO’ in the CHO configuration.

[0027] Fast Failure recovery for LTM is a procedure in which a UE, configured with one or more LTM candidate cell(s), detects a failure (e.g., RLF, handover failure, LTM Cell Switch execution failure), initiates re-establishment, performs cell selection and, when the selected cell is a configured LTM candidate cell, the UE performs an LTM execution instead of continuing with the re-establishment procedure. The network enables that by configuring the parameter ‘attemptLTM-Switch’ in the LTM configuration.

[0028] In Release 18, RAN2 has also agreed that the UE can perform the so called “Fast failure recovery” procedure for the case in which the UE is configured with both CHO and LTM, where, upon a failure, the UE initiates an RRC re-establishment procedure, selects a cell and, if this cell is an LTM candidate cell and / or a CHO candidate, the UE can directly perform an LTM cell switch procedure or a CHO execution towards that selected cell.

[0029] Nevertheless, for the case when the same cell is configured with LTM and CHO at the same time, RAN2 in RAN2#125 meeting has agreed that what feature to select (LTM or CHO) will be up to the UE implementation.

[0030] Further, RAN2 in the RAN2#127bis meeting has made a similar agreement for when LTM is extended to the inter-gNB case, and initial discussion on whether to support fast RLF recovery for CLTM also took place, since a number of companies already proposed to support it in their contributions.

[0031] Some embodiments herein refer to the term “L1 / L2 based inter-cell mobility” as used in the Work Item Description in 3GPP, though it interchangeably also uses the terms L1 / L2mobility, Ll-mobility, LI based mobility, Ll / L2-centric inter-cell mobility, L1 / L2 inter-cell mobility Ll / L2-Triggered Mobility, Lower-layer triggered Mobility or LTM. The basic principle is that the UE receives a lower layer signaling from the network indicating to the UE a change (or switch or activation) of its serving cell (e.g., change of PCell, from a source to a target PCell), wherein a lower layer signaling is a message / signaling of a lower layer protocol, which may be referred as a L1 / 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 SCell(s) for the same cell group e.g., in case the command triggers the UE to change to another cell group configuration of the same type (e.g., another MCG configuration). Before the UE receives the LTM cell switch command, the UE is configured by the network with one or more LTM candidate cell configurations (e.g., reception of an RRC Reconfiguration message, with at least one LTM candidate cell configuration) A LTM candidate cell configuration may include parameters in the IE CellGroupConfig per candidate cell and / or an embedded RRC Reconfiguration per LTM candidate cell.

[0032] Some embodiments herein refer to the term LTM cell switch procedure refers to the process of a UE switching (or changing) its cell from a source cell to a target cell (which may be called here an LTM candidate cell or a neighbour cell), using L1 / L2 -triggered mobility (aLTM). In the context of Ll / L2-triggered mobility (LTM), an LTM cell switch procedure may sometimes also be known as L1 / L2 based inter-cell mobility execution, LTM execution, dynamic switch, LTM switch, (LTM) cell switch, (LTM) serving cell change or (LTM) cell change. In the context of the invention, switching to the LTM candidate cell configuration comprises the UE considering that an LTM candidate cell becomes its new special cell (SpCell) e.g., PCell in case of LTM being configured for a Master Cell Group (MCG) and / or PSCell in case of LTM being configured for a Secondary Cell Group (SCG); or, changing its SpCell from the current PCell to an LTM candidate cell.

[0033] 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 SpCell (e.g., change of PCell, or change of PSCell) and a change in SCells of the cell group (e.g., addition, modification and / or release of one or more SCells).

[0034] An LTM cell switch procedure may be triggered in the UE by reception of a LTM cell switch command, or alternatively, triggered by some other event, such as a condition, e,g, a triggering condition used for conditional configuration, such as conditional handover, being fulfilled, as a result of recovery from radio link failure or handover failure.

[0035] Some embodiments herein refer to a LTM candidate cell, which is a cell the UE is configured with when configured with L1 / L2 -triggered mobility. That is a cell the UE can moveto in a LTM cell switch procedure, upon reception of a LTM cell switch command. These cells may also be called candidate cell(s), candidates, mobility candidates, non-serving cells, additional cells, target candidate cell, target candidate, etc. A LTM candidate cell is a cell the UE perform measurements on (e.g., CSI measurements) so that the UE reports these measurements and network may take educated decision on which beam (e.g., TCI state) and / or cell the UE is to be switched to. An LTM candidate cell may be a candidate to be a target PCell or PSCell, or an SCell of a cell group (e.g., MCG SCell).

[0036] Some embodiments herein introduce a concept 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 CSI-RSs 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 timing advance (TA) acquisition, and link adaptation, and they aren't filtered based on Layer 3 (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 identified 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.

[0037] 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 which is not triggered by the reception of an LTM cell switch command; this may also be considered as a kind of LTM cell switch, or LTM cell switch execution, or Conditional LTM cell switch, or Conditional LTM execution, or CLTM execution, or simply cell switch. According to the methods outlined in the invention, 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, using L1 / L2 triggered mobility (LTM). In the contextof Conditional LTM execution, the text may refer to the serving cell before the LTM cell switch as source cell, old source cell, or previous source cell.

[0038] Some embodiments herein use the term “conditional LTM” or “conditional LTM candidate configuration” which is used to identify a configuration for which the UE is provided with certain criteria which the UE needs to evaluate by itself. Upon the fulfilled of these one or more criteria the UE executes autonomously a conditional LTM cell switch procedure and applies the provided conditional LTM candidate configuration without the network indicating to do so. The text also uses the term “normal LTM” or “normal LTM candidate configuration” which is used to identify a LTM candidate configuration which the UE applies only upon an indication from the network to trigger an LTM cell switch execution.

[0039] Some embodiments herein discuss the concept of an LTM candidate cell within the framework of Conditional LTM. The candidate cell may be referred to as a CLTM candidate cell, CLTM cell, simply candidate cell, candidate target cell, simply target cell, LTM candidate cell, LTM cell, or L1 / L2 inter-cell mobility candidate cell, depending on the context or terminology used in the invention. Essentially, it 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.

[0040] In some embodiments herein, the term CHO execution procedure refers to the process of a UE evaluating certain criteria configured by the network and, upon the fulfilling of such criteria, the UE switching (or changing) its cell from a source cell to a target cell without any network indication. In the context of the invention, switching to the CHO candidate configuration comprises the UE considering that the CHO candidate cell becomes its new special cell (SpCell) e.g., PCell in case of CHO being configured for a Master Cell Group (MCG) and / or PSCell in case of CHO being configured for a Secondary Cell Group (SCG); or, changing its SpCell from the current PCell to an CHO candidate cell. Further, for the case on when CHO is configured on the PSCell, this procedure may also be called as CPA, CPC, CP AC, or subsequent CP AC.

[0041] 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 SpCell (e.g., change of PCell, or change of PSCell) and a change in SCells of the cell group (e.g., addition, modification and / or release of one or more SCells).

[0042] Some embodiments herein refer to at least one LTM candidate cell configuration or CHO candidate configuration and that the UE has received at least one LTM candidate cell configuration or CHO candidate configuration. This is also sometimes referred to as a configuration of a LTM candidate cell or CHO candidate, which may be an RRC configuration, such as encapsulated in an RRC Reconfiguration message, that the UE receives when being configured with Ll / L2-Triggered Mobility or CHO. A LTM or CHO candidate cell configuration comprises the configuration that the UE needs to start to operate accordingly when it performs an LTM cell switch or a CHO execution procedure to that candidate cell e.g., upon reception of the LTM cell switch command indicating the UE to perform a LTM cell switch procedure to that LTM candidate cell or when certain CHO criteria have been fulfilled, which becomes the target cell and the current (new) SpCell, or an SCell in a serving frequency. The LTM or CHO 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). A LTM or CHO candidate cell configuration may in one example comprise one or more of: i) the PCell configuration and one or more SCell configuration(s) of a Master Cell Group (MCG); i) the PSCell configuration and one or more SCell configuration(s) of a secondary Cell Group (SCG). The terms (LTM or CHO) candidate configuration, LTM or CHO configuration, (LTM or CHO) candidate target cell configuration, (LTM or CHO) target candidate (cell) configuration may be used interchangeably when referring to LTM or CHO candidate cell configuration. 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 cell switch command indicating the UE to perform a LTM cell switch procedure to that LTM candidate cell. This identifier is sometimes known as the LTM candidate cell configuration identity or LTM candidate configuration index (or similar).

[0043] Some embodiments herein refer to a suitable cell and that the UE has selected a suitable cell. An example of conditions for a suitable cell is that the UE is able to camp on the cell and the cell fulfils the cell selection criteria. During the cell selection process, the UE selects a suitable cell. The selection of a suitable cell may imply the UE selects any cell which is considered as suitable cell, or selects a cell among multiple cells that all are considered as suitable. In some examples, the cell is part of the selected PLMN, the registered PLMN, or PLMN of the Equivalent PLMN list. The PLMN-ID of that PLMN can be broadcast by the cell with no associated CAG-IDs and CAG-only indication in the UE for that PLMN is absent orfalse. An allowed CAG list in the UE for that PLMN can include a CAG-ID broadcast by the cell for that PLMN. The cell selection criterion S can be fulfilled according to Srxlev > 0 AND Squal > 0. In other words, when the cell selection criterion S is fulfilled it means that the cell has good enough radio conditions in terms of Reference Signal Received Power, RSRP and Reference Signal Received Quality, RSRQ.

[0044] During the cell selection to find a suitable cell, the UE may or may use previously prior knowledge and / or stored information, such as knowledge of frequencies and / or measurement information previously obtained. This is referred to as cell selection leveraging stored information. When no such information is available or cell selection using such information resulted in that no suitable cell was found, the UE falls back to use what is referred to as initial cell selection which may include a scan of RF channels in relevant bands and searching for the strongest cell(s).

[0045] As the cell selection may result in that the UE identify multiple cells that are classified as suitable cells, it may be up to the UE implementation to select one of these cells, possible using other criteria not specified as requirements, such as a cell that is configured as an LTM candidate cell, a CLTM candidate cell, and CHO candidate cell.

[0046] Some embodiments herein refer to the phrase radio related failure. A radio related failure may be triggered for the Master Cell Group (MCG) or the Secondary Cell Group (SCG) and may be one of: A beam failure detection (BFD); A failure to execute a LTM cell switch procedure (e.g., expiry of the LTM supervision timer, like timer T304); A handover failure (HOF) or Reconfiguration with sync failure, (e.g., expiry of timer T304); A radio link failure (RLF) (e.g., expiry of timer T310 or T316); and An RLC unrecoverable error (e.g., a failure to (re)transmit a maximum number N of RLC PDU) that the maximum number of retransmissions has been reached for an RLC entity.

[0047] Some embodiments herein refer to a “network” as a network entity or network node from which the UE receives one or more configurations and / or parameters, such as LTM candidate, CLTM candidate, and CHO candidate configuration(s).

[0048] There currently exist certain challenge(s). According to what has been agreed and currently discussed in 3GPP, the network can configure CHO, LTM, and CLTM cells at the same time and, for all of them, enable the fast failure recovery procedure.

[0049] According to this, a first scenario which may occur is when the UE is configured with multiple LTM candidate cell(s), CHO candidate cell(s), and CLTM candidate cell(s), where each cell is either configured as an LTM candidate cell, or as a CHO candidate cell, or as a CLTM candidate cell. In this case, when a failure is detected (e.g., due to an LTM cell switch failure, a CHO execution failure, a CLTM cell switch failure, or due to a Radio Link Failurewhile the UE is configured with CHO, and / or LTM, and / or CLTM), upon the expiry of a supervision timer (e.g., T304) or RLF timer (e.g., T310), the UE initiates re-establishment and performs cell selection. The selected cell may either be an LTM candidate cell, a CHO candidate cell, a CLTM candidate cell, or a cell which is not a CHO candidate cell, nor an LTM candidate cell, nor a CLTM candidate cell. In other words, there can be four types of cells to select. An alternative to this scenario, is where the UE may be configured with candidate cells with different combinations of LTM, CHO, and CLTM. For example, a cell may be configured as an LTM candidate cell and as a CLTM candidate cell but not as a CHO candidate cell, whereas another cell may be configured as a CHO candidate cell and as an LTM candidate cell but not as a CLTM candidate cell, and so on.

[0050] In the described scenarios, it is only specified that the UE selects a suitable cell (e.g., while timer T311 is running), which may possibly be an LTM candidate cell, or a CHO candidate cell, or a CLTM candidate cell, or a cell which is an LTM candidate cell and also a CHO candidate cell and a CLTM candidate cell, or a cell which is simultaneously not LTM candidate cell, not a CHO candidate cell, not a CLTM candidate cell.. However, even if it is allowed for the UE to select one of those cells, is it not specified how and based on what the UE shall or may select those cells. In other words, the criteria for selecting a suitable cell when LTM candidate cell(s), CHO candidate cell(s), CLTM candidate cell(s) and cells which are simultaneously LTM candidate cells, CHO candidate cells, and CLTM candidate cells is left to the UE implementation.

[0051] Therefore, selecting a suitable cell, or rather any suitable cell, as required, means that the cell has good enough radio conditions in terms of Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ). However, the selected cell may not be the optimal cell as the optimal cell may depends on multiple factors which may change over time and depending e.g., on the mobility of the UE, traffic of the UE, and what feature the UE is capable to support or to be configured with.

[0052] In other words, in scenarios where a UE could select multiple suitable cells, and the suitable cells are candidate cells for LTM, or for CHO, of for CLTM or simultaneously for LTM, CHO and CLTM this may still lead to problems if no further criteria are specified by 3GPP.

[0053] Various embodiments herein address the above challenges. In some embodiments, a UE selects a cell to perform fast recovery from radio related features and the selected cell is an LTM candidate cell, a CHO candidate cell, and a CLTM candidate cell.

[0054] In additional or alternative embodiments, the UE, in response to detecting a radio related failure (e.g., LTM cell switch failure, CHO execution failure, CLTM cell switch failureor RLF), initiates an RRC re-establishment procedure and selects a cell. The cell being an LTM candidate cell, a CHO candidate cell, and a CLTM candidate cell. The UE selectively applies the LTM candidate cell configuration, the CHO candidate configuration, or the CLTM candidate configuration according to one or more rules.

[0055] In some examples, the UE performs a CHO execution, an LTM Cell Switch, or a CLTM cell switch. In response, the UE selectively performs: i) one or more steps of an LTM cell switch procedure when the selected cell the UE has determined to use an LTM candidate cell configuration; ii) one or more steps of a CHO execution procedure when the selected cell the UE has determined to use a CHO candidate configuration; iii) one or more step of a CLTM cell switch procedure when the selected cell the UE has determined to use a CLTM candidate cell configuration; or iv) a re-establishment procedure when the selected cell has been determined to be a cell which is not an LTM candidate cell, a CHO candidate cell, or a CLTM candidate cell for which the UE is configured.

[0056] Potential rules for selecting between execution as a LTM, CHO, or CLTM are described below.

[0057] In some embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to the number of LTM candidate cells, CHO candidate cells, and CLTM candidate cells configured.

[0058] In some examples, the UE selects the configuration according to the overall number of LTM candidate cell, CLTM candidate cell, and CHO configuration stored at the UE. For instance, the UE selective performs the procedure (CHO execution, CLTM execution, or LTM execution) for which the highest number of candidates are configured. One of the benefits is that the UE would follow what the network would believe to be the most appropriate procedure, assuming that the network prefers the UE to perform CHO when more CHO candidate cells are configured, or to perform LTM when more LTM candidate cells are configured, or to perform CLTM when more CLTM candidate cells are configured.

[0059] In additional or alternative examples, the number of LTM candidate cells, CLTM candidate cells, and CHO candidate cells configured is related to the cell that has been selected by the UE. For instance, for the same selected cell there could be 2 LTM candidate cell configurations, 1 CLTM candidate cell configuration, and 1 CHO configuration, so in such a case the UE may select to apply 1 of the LTM candidate cell configurations (and this can be done according to one or more of the rules described in this section).

[0060] In additional or alternative examples, the number of LTM candidate cell, CLTM candidate cell, and CHO candidate cells configured is the overall number of configuration thatUE has stored and thus that can be associated with one or more cell in addition to the selected cell.

[0061] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to the availability of a Time Alignment and / or a Timing Advance.

[0062] In some examples, the UE selects to apply the configuration for which the UE has already a valid Timing Advance (TA) value. In such a case, the TA value may have been received by the UE in an LTM Cell Switch Command, according to the LTM-related early UL synchronization procedure and thus the UE may decide to apply the LTM candidate cell configuration (instead of the CHO candidate configuration). When RACH-less is supported for LTM and not for CHO, or CLTM (because no TA value has been received for any CLTM candidate cell(s)), and the TA value is valid and / or the UE is UL synchronized with the selected cell, the UE selectively applies the LTM candidate configuration and performs LTM.

[0063] In additional or alternative examples, the UE may have received a TA value to apply for a CLTM candidate cell configuration via a lower layer signaling for the network before the failure was experienced. In such a case, as far as the received TA value is still valid the UE may decide to select the CLTM candidate cell configuration for which the TA value was received.

[0064] A benefit of selecting a configuration which the UE has available coverage is that the access may be much faster, since when there is a valid TA, the UE may avoid random access procedure towards that cell.

[0065] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to the availability of a DL synchronization.

[0066] In some examples, when the UE has performed DL synchronization to the selected cell (e.g., pre-activation of one or more beams and / or TCI states of the selected cell), the UE performs LTM, or CLTM instead of CHO. A benefit of this methodologies includes that the access towards a cell for which the UE has established DL synchronization is faster as it avoids the delay to establish the DL sync.

[0067] In additional or alternative examples, the UE has been provided with a command (e.g., MAC CE) to pre-activate a TCI state towards the cell before the failure event has happened.

[0068] In additional or alternative examples, if UE has TCI state activated for both CLTM and LTM, the UE may select CLTM or LTM based on when the TCI state has been activated. If TCI states for CLTM have been activated later than LTM, the UE may select the CLTMcandidate cell as the TCI state activated are more timely than the ones activated for LTM (and vice versa if TCI states for LTM are activated more recently than the ones for CLTM).

[0069] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether the failure which triggered the fast recovery procedure happened for an LTM cell switch procedure, a CHO execution procedure, or a CLTM cell switch procedure.

[0070] In some examples, the UE may decide to select a configuration which is related to what procedure caused the failure event in the previous cell. For instance, if the failure was due to an LTM cell switch procedure, the UE selectively applies the LTM candidate cell configuration in the selected cell. Otherwise, if the failure was due to a CHO execution procedure or CLTM cell switch procedure, the UE may decide to select to apply the CHO candidate configuration or the CLTM candidate cell configuration, respectively, in the selected cell.

[0071] One benefit is that if the UE detected a failure during an LTM cell switch procedure or CLTM cell switch procedure, this means that e.g., UE may be already pre-synchronized to other cells than the one where the failure happened. In case the UE is synchronized toward an LTM or a CLTM candidate cell, the UE selects the cell to which the UE is already synchronized. Alternatively, if UE is already synchronized to both a LTM and CLTM candidate cell, the UE may select the candidate cell to which has been synchronized more recently.

[0072] Another benefit is that the UE executes fast recovery with the same mobility procedure which was executing when the failure occurred.

[0073] In additional or alternative examples, if the failure was due to an LTM cell switch procedure or CLTM cell switch, the UE may decide to selectively apply the CHO candidate configuration in the selected cell (because maybe a RACH-less LTM or CLTM execution has failed, while in CHO execution the UE always performs random access).

[0074] In additional or alternative examples, if the failure was due to an LTM cell switch procedure, or CLTM cell switch, or a CHO, the UE considers that the cell for which the failure occurred is not to be used for a certain time (i.e., further attempts towards the same cell are inhibited for a certain time).

[0075] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether the cell in which the failure which triggered the fast recovery procedure was an LTM cell, a CHO cell, or a CLTM cell.

[0076] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to which order the LTM candidate configuration, the CHO candidate configuration, and the CLTM candidate configuration has been provided to the UE.

[0077] In some examples, the UE is configured with at least one LTM candidate cell configuration, one CLTM candidate cell configuration, and one CHO candidate cell configuration. If the UE has first received the LTM candidate cell configuration, the UE considers the LTM candidate cell configuration is the first position of the list as the configuration with the highest priority.

[0078] In additional or alternative examples, if the UE has received at least one LTM candidate cell configuration, at least one CLTM candidate cell configuration, and at least one CHO candidate cell configuration within the same message, the UE will consider the configuration as the one which the highest priority based on the order in which the ASN.1 fields or IES are received by the network.

[0079] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration according to whether an early ASN.1 decoding has been done to a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration.

[0080] In some examples, the UE may have already performed the ASN.1 decoding for a LTM candidate cell configuration, or CLTM candidate cell configuration, or CHO candidate configuration. This means that either the UE has performed the ASN.1 decoding when has received such configurations (in this case called early ASN.l decoding) or because the UE has already performed a LTM cell switch procedure or a CLTM cell switch procedure. In this case, if the UE has already done the ASN.1 decoding on a CLTM candidate cell configuration, the UE selects the CLTM candidate cell and performs a CLTM cell switch procedure.

[0081] A benefit of this can be that the interruption time and delay of the mobility procedure can be shorter, as the UE has already processed and validated the RRC configuration which is related to the LTM candidate cell configuration or the CLTM candidate cell configuration.

[0082] In additional or alternative embodiment, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether a LTM candidate cell configuration, a CHO candidate cell configuration, or a CLTM candidate cell configuration requires a security key change or not.

[0083] In some examples, the LTM candidate cell configuration, CLTM candidate cell configuration, or CHO candidate configuration may instruct the UE perform a security change procedure. In this case, if there is at least one configuration (among the LTM candidate cell configuration, CLTM candidate cell configuration, or CHO candidate configuration) which does not require a change of the security, the UE select this candidate configuration.

[0084] A benefit of this is the that the interruption time, the delay of the mobility procedure, and the user plane delay can be shorter, as the UE would not need to change the security parameters and re-establish all the radio bearer (both SRBs and DRBs) with related PDCP entities.

[0085] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether a time alignment timer is running for a TA which is for a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration.

[0086] In some examples, the UE may have received a TA value to apply for a CLTM candidate cell configuration via a lower layer signaling for the network before the failure was experienced. In such a case, as far as the received TA value is still valid the UE may decide to select the CLTM candidate cell configuration for which the TA value was received. How the UE understands that the received TA value is still valid is according to the time alignment timer which is started when the UE either receives a TA value or starts to use a TA value. For example, is the UE has a time alignment timer which is still running for a CLTM candidate cell configuration, the UE selects this configuration and executes a CLTM cell switch procedure.

[0087] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to which event has been configured for performing measurements on the LTM candidate cell configuration, CHO candidate configuration, or CLTM candidate cell configuration.

[0088] In some examples, the UE may be configured by the LTM candidate cell configuration, CLTM candidate cell configuration, or CHO candidate configuration to evaluate different events. Each event may serve a different purpose and use case and the selection may be according to what is the current traffic which the UE has.

[0089] In additional or alternative examples, if the UE is configured to evaluate event A4 for the LTM candidate cell, event A3 for the CLTM candidate cell, and event A3 and A5 for the CHO configuration, the UE may select the CHO configuration as evaluating event A3 and A5gives a more comprehensive understanding of the current channel conditions of the CHO configuration.

[0090] In additional or alternative examples, if the UE is configured to evaluate event A4 for LTM candidate cell, event A3 for the CLTM candidate cell, and event A3 and A5 for the CHO configuration, the UE may select the LTM candidate cell or the CLTM candidate cell, as evaluating the event A4 (for LTM) or evaluating the event A3 (for CLTM) can be considered by the UE as a faster way to gain connectivity.

[0091] In additional or alternative examples, the UE may be configured by the LTM candidate cell configuration, CLTM candidate cell configuration, or CHO candidate configuration to evaluate events related to different measurement types (LI measurements and / or L3 measurements). In one case, the UE selectively applies the configuration that has event configured for LI measurements. If more than one of the LTM / CLTM / CHO configurations contain events configured for LI measurements, the UE selectively applies one configuration according to a random number associated to each one of the configurations, or any of the other conditions indicated by the other embodiments / options in the invention.

[0092] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether a vertical or horizontal key security derivation should be performed in case the LTM candidate cell configuration, CHO candidate configuration, or CLTM candidate configuration is selected.

[0093] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to the reference signal type that UE should measure for the LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration.

[0094] In some examples, the UE may be configured to measure different reference signal types for the LTM candidate cell configuration, CLTM candidate cell configuration, or CHO candidate configuration. For instance, the UE may be configured to measure SSBs for the CLTM candidate cell, and CSI-RS for the LTM candidate cell and CHO candidate cell. In this case, the UE may decide to select the CLTM candidate cell configuration as the SSB reference signal are always broadcasted by the network whereas the CSI-RS may be broadcasted sporadically or on-demand (and thus may not be available to be measure at the time the UE needs to select a suitable cell).

[0095] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cellconfiguration for the selected cell according to whether LI measurements or L3 measurements are configured to measure and report for the LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration.

[0096] In some examples, if one only among the LTM candidate cell configuration and / or CLTM candidate configuration and / or CHO candidate configuration (e.g., the LTM configuration) has LI measurements configured to measure and report while L3 measurements are configured to measure and report for the others (e.g., for CLTM and / or for CHO candidate configurations), the UE selectively applies the configuration with LI measurements configured to be measured and reported.

[0097] In additional or alternative examples, if more than one among the LTM candidate cell configuration and / or CLTM candidate configuration and / or CHO candidate configuration (e.g., the LTM configuration and CLTM configuration) have LI measurements configured to measure and report and L3 measurements are configured to measure and report for the other (e.g., for CHO candidate configuration), the UE selectively applies one of the configuration with LI measurements configured to be measured and reported based on random numbers associated to the configurations with LI measurements configured to be measured and reported.

[0098] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether a special scheduling request configuration is available for the LTM candidate cell configuration, CHO candidate configuration, or CLTM candidate cell configuration.

[0099] In some examples, the UE may be configured with special scheduling request resources for the LTM candidate cell configuration, CLTM candidate cell configuration, or CHO candidate configuration. For instance, if the UE has special scheduling resources configured for the LTM candidate cell configuration, the LTM candidate cell is selected and an LTM cell switch procedure is performed.

[0100] A benefit of this is that the network is able to identify early what procedure the UE is executing and thus optimizing certain procedures, such as providing a UL grant in a faster way. The outcome can be that the interruption time, the delay of the mobility procedure, and the user plane delay can be shorter, as the UE can be able to transmit faster with the selected cell.

[0101] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether a measurement report has been sent within a certain period of time before the failure was detected according to what is configuredby the LTM candidate cell configuration, CHO candidate configuration, or CLTM candidate cell configuration.

[0102] In some examples, there is an L1 / L3 measurement report have been sent within a certain period of time before measurement for a LTM candidate, a CHO candidate or a CLTM candidate. The UE will selectively apply the LTM candidate configuration, the CHO candidate configuration or a CLTM candidate configuration.

[0103] A benefit of this is that the UE can select a LTM candidate or the CHO candidate or the CLTM candidate with shared measurement results to the network. The UE can be prepared to act upon the network action after receiving the measurement for example activation of the TCI state and switch to the candidate cell etc.

[0104] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, or a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to according to the reference signal Es / Io above certain threshold within a certain period of time before the failure was detected according to what is configured by the LTM candidate cell configuration, the CHO candidate configuration, or the CLTM candidate cell configuration.

[0105] In some examples, the UE have been continuously doing measurement on a LTM candidate or a CHO candidate or a CLTM candidate, the detected SNR of the reference symbols of the LTM candidate, or a CHO candidate, or a CLTM candidate is known to the UE, the UE will selectively applies a LTM candidate configuration or a CHO candidate configuration or a CLTM candidate cell configuration based on the highest SNR of the reference symbol it has been measured on.

[0106] In additional or alternative examples, the have been measure on a LTM candidate or a CHO candidate or a CLTM candidate, one of the measurement occasions were disturbed due to the SNR of the reference symbol is bellow the minimum required level for maintain measurement accuracy within a certain period, the UE will avoid applying the LTM candidate configuration or the CHO candidate configuration or the CLTM candidate configuration.

[0107] A benefit can be that UE will always apply a configuration that it has done measurement and the reference signal for evaluation period will be always strong for UE to continue evaluate the LTM, CHO or the CLTM candidate.

[0108] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether CA is configured.

[0109] A benefit can be that UE will apply a configuration which already configures CA and thus UE will experience better capacity (performance will be better).

[0110] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to the number of SCells configured.

[0111] A benefit can be that UE will experience CA with a higher number of carriers aggregated and thus better latency and capacity.

[0112] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether the SCells are activated or deactivated.

[0113] A benefit for the UE can be that it will be able to operate in CA as soon as switching to the new selected cell, thus transmitting and receiving traffic over the “activated” SCells. If the SCells are deactivated the UE cannot really benefit from CA until the network does not activate one or more SCell(s) explicitly.

[0114] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether DC is configured.

[0115] A benefit can be that UE will apply a configuration which already configures DC from the moment the UE access the cell and thus UE will experience better capacity (performance will be better).

[0116] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether a L2 reset can be performed or not.

[0117] A benefit is that avoiding L2 reset may result in shorter interruption or less data loss compared to performing L2 reset.

[0118] In other words, the UE selects to perform LTM or CLTM when L2 reset is not enabled towards the selected cell, which makes the execution faster compared to CHO, in case CHO execution would imply a L2 reset.

[0119] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether is possible to perform an early ASN.1 decoding and validity check is performed.

[0120] A benefit is that, if the UE has already done the ASN.1 decoding and validity check on a configuration (when this was stored), this may result in short interruption or less data loss compared to do the ASN.1 decoding and validity check in the moment the configuration is applied by the UE. Here means that the UE is capable of doing the early ASN.l decoding and validity check, but not that the UE has already done it.

[0121] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to whether CFRA resources are available.

[0122] A benefit is that using dedicated random access resource, the UE will experience a fast random access procedure and thus shorter interruption and data loss.

[0123] For example, the UE selects to perform CHO when CFRA resources are configured for the CHO candidate cell configuration, but not for the LTM candidate cell configuration or CLTM candidate cell configuration (when both LTM and CLTM are meant to be executing with the random access procedure). In that case, since all the candidate configuration are to be using random access, the UE selects the procedure to apply with CFRA resources configured.

[0124] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according the SCG is activated or deactivated.

[0125] A benefit for the UE can be that it will be able to operate in DC as soon as switching to the new selected cell, thus transmitting and receiving traffic over the “activated” SCG. If the SCG is deactivated the UE cannot really benefit from DC until the network does not activate the SCG explicitly.

[0126] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according a certain feature is configured or not in the LTM candidate cell configuration, the CHO candidate configuration, and / or the CLTM candidate cell configuration.

[0127] In some examples, the UE decides to apply a configuration which comprise one or more feature which improve a chosen criteria. For instance, the UE may select to apply a configuration with configure a high number of MIMO layer because it improves the performance. On the other side, the UE may decide to apply a configuration configures DC, because is better from a robustness point of view.

[0128] In additional or alternative embodiments, the UE selectively applies a LTM candidate cell configuration, a CHO candidate configuration, or a CLTM candidate cell configuration for the selected cell according to a function at the UE which generate a random number, one for the LTM candidate cell configuration, one for the CHO candidate configuration, and one for the CLTM candidate cell configuration.

[0129] In additional or alternative embodiments, the UE selectively applies always the LTM candidate cell configuration, if the LTM candidate cell configuration, CHO candidate configuration, and CLTM candidate cell configuration are available for the selected cell.

[0130] One of the benefits is that LTM or CLTM execution may be performed without a random access procedure.

[0131] Another benefit is that upon CHO execution the CHO configuration of other CHO candidates are deleted, since there is no sub-sequent CHO. However, in LTM or CLTM the UE keeps both the LTM or CLTM related configuration(s) so that another LTM or CLTM may be performed after the mobility procedure is concluded.

[0132] In additional or alternative embodiments, the UE selectively applies always the CHO candidate configuration, if the LTM candidate cell configuration, CHO candidate configuration, and CLTM candidate cell configuration are available for the selected cell.

[0133] One of the benefits is that CHO execution relies on a random access procedure, instead of RACH-less, which would increase the chances of failure in a recovery procedure.

[0134] In additional or alternative embodiments, the UE selectively applies always the CLTM candidate cell configuration, if the LTM candidate cell configuration, CHO candidate configuration, and CLTM candidate cell configuration are available for the selected cell.

[0135] In some examples, if there are multiple suitable cells for which the UE is configured with a LTM candidate cell configuration and / or a CHO candidate configuration and / or a CLTM candidate configuration, the UE selectively applies the LTM candidate cell configuration or the CHO candidate configuration or the CLTM candidate configuration for the suitable cell which fulfill certain criteria, e.g., related to pathloss in the suitable cells. Some example of criteria are detailed below.

[0136] In additional or alternative examples, among the suitable cells, the UE selects the cell at the lowest carrier frequency. A rational for this can be that the UE assumes that the cell with such characteristics is the one which more likely will provide better coverage compared to the others, and with that the chances to incur in failures is reduced or avoide. The benefit at network side can be a reduced number of radio link failures or number of failures in mobility procedure.

[0137] In additional or alternative examples, among the suitable cells, the UE selects the suitable cell which operates at the lowest carrier frequency and for which one (or more) of the conditions indicated by the other embodiments is(are) fulfilled. For instance, the UE selects the suitable cell operating at the lowest carrier frequency and for which the UE has a valid TA value, or a cell for which no security key change is required.

[0138] In additional or alternative examples, among the suitable cells, the UE selects the suitable cell that operates in the lower range of frequencies (e.g., in FR1 and not in FR2)

[0139] In additional or alternative examples, among the suitable cells, the UE selects the suitable cell for which the UE is aware that it can operate with no power restriction.

[0140] Operations of a UE 600 (implemented using the structure of FIG. 6) will now be discussed with reference to the flow charts of FIG. 3 according to some embodiments of inventive concepts. For example, modules may be stored in memory 610 of FIG. 6, and these modules may provide instructions so that when the instructions of a module are executed by respective UE processing circuitry 602, UE 600 performs respective operations of the flow chart.

[0141] FIG. 3 illustrates an example of operations performed by a UE to select between a LTM, CHO, or CLTM candidate cell.

[0142] At block 310, processing circuitry 602 determines configuration information for a candidate cell including a plurality of candidate cell configuration types. In some embodiments, the configuration information includes a plurality of candidate cell configurations and multiple candidate cell configurations can have the same candidate cell configuration type. In some examples, different candidate cell configuration types include LTM, CHO, and CLTM.

[0143] In additional or alternative embodiments, determining the configuration information includes determining the configuration information for the candidate cell including at least two of: one or more LTM candidate cell configurations; one or more CHO candidate cell configurations; and one or more CLTM candidate cell configurations.

[0144] In additional or alternative embodiments, determining the configuration information includes determining the configuration information for the candidate cell including each of: one or more LTM candidate cell configurations; one or more CHO candidate cell configurations; and one or more CLTM candidate cell configurations.

[0145] In additional or alternative embodiments, determining the configuration information includes determining the configuration information for a plurality of candidate cells. Some candidate cells may only have one type of candidate cell configuration type.

[0146] In additional or alternative embodiments, determining the configuration information for the candidate cell includes receiving an indication of the configuration information from a network node.

[0147] At block 320, processing circuitry 602 detects a radio related failure. In some embodiments, detecting the radio related failure includes detecting at least one of: a beam failure detection, BFD; a failure to execute a layer 1 / layer 2 triggered mobility, LTM, cell switch procedure; a handover, HO, failure; a radio link failure, RLF; and a radio link control, RLC, unrecoverable error.

[0148] At block 330, processing circuitry 602 selects the candidate cell as a target cell (e.g., for a cell switch procedure). In some embodiments, the UE selects the candidate cell from a set of nearby cells in response to detecting the radio related failure.

[0149] At block 340, processing circuitry 602 selects a first candidate cell configuration type of the plurality of candidate cell configuration types based on a rule. In some embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on a number of candidate cell configurations of each candidate cell configuration type within the configuration information for the plurality of candidate cells.

[0150] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on an availability of a time alignment and / or timing advance.

[0151] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on an availability of a downlink synchronization.

[0152] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on a type of cell switch procedure during which the radio related failure occurred.

[0153] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on a type of a serving cell for the UE at a time of the radio related failure.

[0154] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on an order in which candidate cell configurations of the configuration information were provided to the UE.

[0155] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether an early ASN.1 decoding has been done to a candidate cell configuration of the configuration information.

[0156] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a candidate cell configuration of the configuration information requires a security key change.

[0157] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a time alignment timer is running for a timing advance for a candidate cell configuration of the configuration information.

[0158] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on which event has been configured for performing measurements on a candidate cell configuration of the configuration information.

[0159] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a vertical or horizontal key security derivation should be performed if a candidate cell configuration of the configuration information.

[0160] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on a reference signal type that the UE should measure for each candidate cell configuration type of the plurality of candidate cell configuration types.

[0161] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether layer 1 measurements or layer 3 measurements are configured to measure and report for each candidate cell configuration type of the plurality of candidate cell configuration types.

[0162] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a special scheduling request configuration is available for each candidate cell configuration type of the plurality of candidate cell configuration types.

[0163] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a measurement report has been sent withing a certain period of time before the failure was detected that is associated with each candidate cell configuration type of the plurality of candidate cell configuration types.

[0164] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration typeof the plurality of candidate cell configuration types based on whether a downlink carrier to interference (“Es / Io”) ratio of a reference signal is above certain threshold within a certain period of time before the failure was detected according to what is associated with each candidate cell configuration type of the plurality of candidate cell configuration types.

[0165] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether carrier aggregation is configured at the target cell.

[0166] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on a number of secondary cells configured at the target cell.

[0167] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on a number of secondary cells at the target cell that are activated or that are deactivated.

[0168] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether dual connectivity is configured at the target cell.

[0169] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a layer 2 reset should be performed.

[0170] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether it is possible to perform an early ASN.1 decoding and validity check has been performed.

[0171] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether contention free random access, CFRA, resources are available.

[0172] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration typeof the plurality of candidate cell configuration types based on whether a secondary cell group, SCG, for the target cell is activated or deactivated.

[0173] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a certain feature is configured in each candidate cell configuration type of the plurality of candidate cell configuration types.

[0174] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on a function that generates a pseudorandom number.

[0175] In additional or alternative embodiments, selecting the first candidate cell configuration type based on the rule includes selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on the plurality of candidate cell configuration types including a second candidate cell configuration type and / or a third candidate cell configuration type.

[0176] In some examples, selecting the first candidate cell configuration type based on the rule includes selecting a layer 1 / layer 2 triggered mobility, LTM, candidate cell configuration based on the plurality of candidate cell configuration types including a conditional handover, CHO, candidate cell configuration, the LTM candidate cell configuration, and a conditional LTM, CLTM, candidate cell configuration.

[0177] In additional or alternative examples, selecting the first candidate cell configuration type based on the rule includes selecting a conditional handover, CHO, candidate cell configuration based on the plurality of candidate cell configuration types including the CHO candidate cell configuration, a layer 1 / layer 2 triggered mobility, LTM, candidate cell configuration, and a conditional LTM, CLTM, candidate cell configuration.

[0178] In additional or alternative examples, selecting the first candidate cell configuration type based on the rule includes selecting a conditional layer 1 / layer 2 triggered mobility, CLTM, candidate cell configuration based on the plurality of candidate cell configuration types including a conditional handover, CHO, candidate cell configuration, a layer 1 / layer 2 triggered mobility, LTM, candidate cell configuration, and the CLTM candidate cell configuration.

[0179] At block 350, processing circuitry 602 applies a portion of the configuration information for the candidate cell having the first candidate cell configuration type. In some embodiments, applying the portion of the configuration information includes performing a cell switch procedure to the target cell, a type of the cell switch procedure being associated with thefirst candidate cell configuration type. In some examples, if the first candidate cell configuration type is a LTM candidate cell configuration type, applying the portion of the configuration information includes performing a LTM cell switch procedure including applying one or more LTM candidate cell configurations for the target cell.

[0180] In additional or alternative examples, if the first candidate cell configuration type is a CHO candidate cell configuration type, applying the portion of the configuration information includes performing a CHO cell switch procedure including applying one or more CHO candidate cell configurations for the target cell.

[0181] In additional or alternative examples, if the first candidate cell configuration type is a CLTM candidate cell configuration type, applying the portion of the configuration information includes performing a CLTM cell switch procedure including applying one or more CLTM candidate cell configurations for the target cell.

[0182] Various operations from the flow chart of FIG. 3 may be optional with respect to some embodiments of communication devices and related methods.

[0183] FIG. 4 shows an example of a communication system 400 in accordance with some embodiments.

[0184] 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 (3 GPP) 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.

[0185] 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 networknode in the telecommunications network 402, including one or more access network nodes 410 and / or core network nodes 408.

[0186] 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 node may 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.

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

[0188] 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 sendmessages, 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 by receiving the message from an access network node 410 that itself received the message from the UE 412.

[0189] 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).

[0190] 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 withremote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0191] As a whole, the communication system 400 of FIG. 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 and Electronics 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.

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

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

[0194] 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 byan 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).

[0195] 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 network nodes (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.

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

[0197] 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 toroute communications between the UEs and network node 41 OB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0198] FIG. 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.

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

[0200] 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, FIG. 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.

[0201] FIG. 6 shows a wireless device 600, which may be configured to operate in communication system 400 of FIG. 4 or in communication system 500 of FIG. 50. 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 system 500, 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.

[0202] 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).

[0203] 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 FIG. 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 includephysical 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.

[0204] 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).

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

[0206] 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 accessiblepower suitable for the respective components of the wireless device 600 to which power is supplied.

[0207] 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 readonly 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.

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

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

[0210] 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 / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0211] 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).

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

[0213] 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, a thermostat, 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 surveillancesystem, 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 FIG. 6.

[0214] 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 3GPP 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.

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

[0216] FIG. 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 FIG. 4, like network nodes 408 or 410, or in communication system 500 of FIG. 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)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0217] 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).

[0218] 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).

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

[0220] 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 some instances 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 variousillustrated 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.

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

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

[0223] 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 computer-executable 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 any calculations 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.

[0224] 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 particularembodiments, 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 frontend 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 front-end 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.

[0225] 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).

[0226] 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 / or signals 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.

[0227] 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 operationsdescribed 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.

[0228] 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 if the external power source fails.

[0229] Embodiments of the network node 700 may include additional components beyond those shown in FIG. 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.

[0230] FIG. 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 relates to 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.

[0231] 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 Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

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

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

[0234] 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 it hardware 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.

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

[0236] 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 intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

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

Claims

CLAIMSWhat is claimed is:

1. A method of operating a user equipment, UE, the method comprising:determining (310) configuration information for a candidate cell including a plurality of candidate cell configuration types;detecting (320) a radio related failure;responsive to the radio related failure, selecting (330) the candidate cell as a target cell; selecting (340) a first candidate cell configuration type of the plurality of candidate cell configuration types based on a rule;applying (350) a portion of the configuration information for the candidate cell having the first candidate cell configuration type.

2. The method of Claim 1, wherein determining the configuration information comprises determining the configuration information for the candidate cell including at least two of: one or more Layer 1 / Layer 2 triggered mobility, LTM candidate cell configurations; one or more conditional handover, CHO, candidate cell configurations; andone or more conditional LTM, CLTM, candidate cell configurations.

3. The method of any of Claims 1-2, wherein determining the configuration information comprises determining the configuration information for the candidate cell including each of:one or more Layer 1 / Layer 2 triggered mobility, LTM candidate cell configurations; one or more conditional handover, CHO, candidate cell configurations; andone or more conditional LTM, CLTM, candidate cell configurations.

4. The method of any of Claims 1-3, wherein determining the configuration information comprises determining configuration information for a plurality of candidate cells.

5. The method of Claim 4, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on a number of candidate cell configurations of each candidate cell configuration type within the configuration information for the plurality of candidate cells.

456. The method of any of Claims 1-5, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on a number of candidate cell configurations of each candidate cell configuration type within the configuration information for the candidate cell.

7. The method of any of Claims 1-6, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on an availability of a time alignment and / or timing advance.

8. The method of any of Claims 1-7, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on an availability of a downlink synchronization.

9. The method of any of Claims 1-8, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether an early ASN.1 decoding has been done to a candidate cell configuration of the configuration information.

10. The method of any of Claims 1-9, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a candidate cell configuration of the configuration information requires a security key change.

11. The method of any of Claims 1-10, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a time alignment timer is running for a timing advance for a candidate cell configuration of the configuration information.

12. The method of any of Claims 1-11, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a vertical or horizontal keysecurity derivation should be performed if a candidate cell configuration of the configuration information.

13. The method of any of Claims 1-12, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on a reference signal type that the UE should measure for each candidate cell configuration type of the plurality of candidate cell configuration types.

14. The method of any of Claims 1-13, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether layer 1 measurements or layer 3 measurements are configured to measure and report for each candidate cell configuration type of the plurality of candidate cell configuration types.

15. The method of any of Claims 1-14, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a special scheduling request configuration is available for each candidate cell configuration type of the plurality of candidate cell configuration types.

16. The method of any of Claims 1-15, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a measurement report has been sent within a certain period of time before the failure was detected that is associated with each candidate cell configuration type of the plurality of candidate cell configuration types.

17. The method of any of Claims 1-16, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a downlink carrier to interference, Es / Io, ratio of a reference signal is above certain threshold within a certain period of time before the failure was detected according to what is associated with each candidate cell configuration type of the plurality of candidate cell configuration types.4718. The method of any of Claims 1-17, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether carrier aggregation is configured at the target cell.

19. The method of any of Claims 1-18, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on a number of secondary cells configured at the target cell.

20. The method of any of Claims 1-19, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on a number of secondary cells at the target cell that are activated or a number that are deactivated.

21. The method of any of Claims 1-20, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether dual connectivity is configured at the target cell.

22. The method of any of Claims 1-21, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a layer 2 reset should be performed.

23. The method of any of Claims 1-22, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether it is possible to perform an early ASN.1 decoding and validity check has been performed.

24. The method of any of Claims 1-23, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether contention free random access, CFRA, resources are available.

25. The method of any of Claims 1-24, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on whether a secondary cell group, SCG, for the target cell is activated or deactivated.

26. The method of any of Claims 1-25, wherein selecting the first candidate cell configuration type based on the rule comprises selecting the first candidate cell configuration type of the plurality of candidate cell configuration types based on the plurality of candidate cell configuration types including a second candidate cell configuration type and / or a third candidate cell configuration type.

27. The method of Claim 26, wherein selecting the first candidate cell configuration type based on the rule comprises selecting a layer 1 / layer 2 triggered mobility, LTM, candidate cell configuration based on the plurality of candidate cell configuration types including a conditional handover, CHO, candidate cell configuration, the LTM candidate cell configuration, and a conditional LTM, CLTM, candidate cell configuration.

28. The method of Claim 26, wherein selecting the first candidate cell configuration type based on the rule comprises selecting a conditional handover, CHO, candidate cell configuration based on the plurality of candidate cell configuration types including the CHO candidate cell configuration, a layer 1 / layer 2 triggered mobility, LTM, candidate cell configuration, and a conditional LTM, CLTM, candidate cell configuration.

29. The method of Claim 26, wherein selecting the first candidate cell configuration type based on the rule comprises selecting a conditional layer 1 / layer 2 triggered mobility, CLTM, candidate cell configuration based on the plurality of candidate cell configuration types including a conditional handover, CHO, candidate cell configuration, a layer 1 / layer 2 triggered mobility, LTM, candidate cell configuration, and the CLTM candidate cell configuration.

30. The method of any of Claims 1-29, wherein determining the configuration information for the candidate cell comprises receiving an indication of the configuration information from a network node.

31. The method of any of Claims 1-30, wherein detecting the radio related failure comprises detecting at least one of:a beam failure detection, BFD;a failure to execute a layer 1 / layer 2 triggered mobility, LTM, cell switch procedure; a handover, HO, failure;a radio link failure, RLF; anda radio link control, RLC, unrecoverable error.

32. The method of any of Claims 1-31, wherein applying the portion of the configuration information comprises performing a cell switch procedure to the target cell, a type of the cell switch procedure being associated with the first candidate cell configuration type.

33. A user equipment, UE, (600) adapted to perform operations comprising:determining (310) configuration information for a candidate cell including a plurality of candidate cell configuration types;detecting (320) a radio related failure;responsive to the radio related failure, selecting (330) the candidate cell as a target cell; selecting (340) a first candidate cell configuration type of the plurality of candidate cell configuration types based on a rule;applying (350) a portion of the configuration information for the candidate cell having the first candidate cell configuration type.

34. The UE of Claim 33, the operations further comprising any of the operations of Claims 2-32.

35. A computer program comprising program code to be executed by processing circuitry (602) of a user equipment, UE, (600), whereby execution of the program code causes the UE to perform operations comprising:determining (310) configuration information for a candidate cell including a plurality of candidate cell configuration types;detecting (320) a radio related failure;responsive to the radio related failure, selecting (330) the candidate cell as a target cell; selecting (340) a first candidate cell configuration type of the plurality of candidate cell configuration types based on a rule;applying (350) a portion of the configuration information for the candidate cell having the first candidate cell configuration type.

36. The computer program of Claim 35, the operations further comprising any of the operations of Claims 2-32.

37. A computer program product comprising a non-transitory storage medium (610) including program code to be executed by processing circuitry (602) of a user equipment, UE, (600), whereby execution of the program code causes the UE to perform operations comprising:determining (310) configuration information for a candidate cell including a plurality of candidate cell configuration types;detecting (320) a radio related failure;responsive to the radio related failure, selecting (330) the candidate cell as a target cell; selecting (340) a first candidate cell configuration type of the plurality of candidate cell configuration types based on a rule;applying (350) a portion of the configuration information for the candidate cell having the first candidate cell configuration type.

38. The computer program product of Claim 37, the operations further comprising any of the operations of Claims 2-32.

Images