Informing the SK-counter to the mn

By allowing the UE to inform the MN about the selected sk-counter during LTM cell switch, secure key establishment is ensured, avoiding RRC re-establishment and reducing network and UE overhead.

WO2026235598A1PCT designated stage Publication Date: 2026-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/SE2026/050306
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-07
Filing Date
2026-05-05
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In the context of Layer 1/Layer 2 (L1/L2) Triggered Mobility (LTM) in 3GPP Rel-19, the Master Node (MN) cannot derive a new secondary key for the Secondary Node (SN) during an LTM cell switch procedure at the SN, as the selected sk-counter value is not reported to the MN, leading to security issues and potential RRC re-establishment procedures.

Method used

The User Equipment (UE) informs the Master Node (MN) about the selected sk-counter value during an LTM cell switch procedure, either directly or through an intermediate network node, allowing the MN to calculate and transmit a new secondary key to the Secondary Node (SN).

Benefits of technology

This approach enables secure key establishment between the UE and SN, preventing RRC re-establishment and reducing connectivity interruption and signaling overhead.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure SE2026050306_12112026_PF_FP_ABST
    Figure SE2026050306_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Methods and apparatuses are disclosed for enabling secure key refresh during Lower Layer Triggered Mobility (LTM) cell switch procedures performed at a Secondary Node (SN) in a multi-radio dual connectivity (MR-DC) wireless network A Master Node (MN) provides a User Equipment (UE) with a list of sk-counters for deriving a secondary key at the SN. Since no MN RRCReconfigurationComplete message is transmitted during an SN-initiated LTM cell switch, the UE reports the selected sk-counter to the MN through alternative signaling. In a first option, the UE transmits the selected sk-counter directly to the MN via a new or existing message other than the RRCReconfigurationComplete message. In a second option, the UE sends the selected sk-counter to the SN, which forwards it to the MN; the MN then derives and returns the new secondary key to the SN. The disclosed techniques prevent security establishment failures, avoiding RRC re-establishment, connectivity interruptions, and excessive signaling overhead.
Need to check novelty before this filing date? Find Prior Art

Description

INFORMING THE SK-COUNTER TO THE MNTECHNICAL FIELD

[0001] The present disclosure relates to methods and wireless devices and network nodes for providing and conveying security information to each other in a wireless communications system.INTRODUCTION

[0002] In Third Generation Partnership Program (3 GPP) Release 18, as part of a work item known as Further New Radio (NR) mobility enhancements, a technical area entitled Layer 1 (LI) / Layer 2 (L2) based inter-cell mobility is included. According to the Work Item Description, R2-2502534, Running RRC CR for inter-CU and conditional LTM, Ericsson, RAN2#129bis, April 2025, the goal of L1 / L2 based inter-cell mobility (also known as L1 / L2 Triggered Mobility -LTM) is to enable a serving cell change, sometimes also known as an LTM cell switch or an LTM cell switch procedure, via L1 / L2 signaling, in order to reduce the latency, overhead and interruption time.

[0003] A basic principle with L1 / L2 triggered mobility is that the User Equipment (UE) is pre-configured, by the network, with an LTM configuration which includes information such as measurement configuration and a Radio Resource Control (RRC) configuration per LTM candidate cell, sometimes also known as a LTM candidate cell configuration. Such a LTM candidate cell configuration may be an RRCReconfiguration message or one or more Information Element (IE) fields / parameters such as CellGroupConfig. The UE performs measurements on LTM candidate cells and beams in those cells, according to the measurement configuration included in the LTM configuration received by the network. The UE transmits LI measurement reports for LTM including LI - Reference Signal Received Power (RSRP) measurements for up to four LTM candidate cells and up to four beams in in each cell. When the network (e.g. a gNB or a gNB Distribited Unit - gNB-DU), receives the LI measurement report for LTM, it may use the content of this report to trigger an LTM cell switch towards one of the LTM candidate cells.

[0004] The network triggers the execution of a LTM cell switch procedure in the UE to one of these LTM candidate cells by transmitting a LTM cell switch command Medium Access Control (MAC) Control Element (MAC CE) to the UE. The LTM cell switch command includes information such as a reference to a LTM candidate cell configuration and an indication of a target beam in the LTM candidate cell. The UE then connects to the beam and switches to the LTM candidate cell configuration.

[0005] The overall procedures for LTM in Rel-18 are described in 3GPP TS 38.300 vl8.5.0 (2025-03-21), subclause 9.2.3.5, and for the gNB-CU / gNB-DU Architecture in 3GPP TS 38.401 V18.5.0 (2025-03-20), subclauses 8.2.1.4-8.2.1.6. LTM in Rel-18 is limited to intra-gNB (including intra- Central Unit (CU) intra-DU and intra-CU inter-DU) mobility.

[0006] In 3 GPP Rel-19, a work item on NR Mobility enhancements Phase 4 has started, which aims to enhance mobility features, including introducing support for inter-CU LTM according to the objective below:• Specify support for inter-CU Layerl / Layer 2 Triggered Mobility (LTM) [RAN2, RAN3]:o Prioritize the case when CU is acting as MN when DC is not configured, o As secondary priority, support the case when NR-DC is configured and CU is acting as SN and MCG is unchanged,o As secondary priority, support the case when NR-DC is configured, CU is acting as MN and SCG is unchanged or SCG is released,■ Note: The case that LTM is configured in both MCG and SCG is excluded o Specify support for subsequent LTM mobility procedures aiming to avoid RRC configuration between cell switches as per Rel-18 LTM,■ Coordination with SA3 needed with respect to security key handling o Note: Rel. 18 intra-CU LTM procedure is considered as baseline for adding inter- CU support.

[0007] The existing Sk-Counter is a numerical value used when the UE first connects to a Secondary Node (SN). The UE uses this counter to derive fresh security keys specifically for use in the SN.

[0008] As outlined in 3GPP TS 33.501, vl9.1.0, Chapter 6.10.1.2:“When the MN establishes security context between an SN and the UE for the first time for a given AS security context shared between the MN and the UE, the MN generates the KSN for the SN and sends it to the SN over the Xn-C. To generate the KSN, the MN associates a counter, called an SN Counter, with the current AS security context. The SN Counter is used as freshness input into KSN derivations as described in the clause 6.10.3.2. The MN sends the value of the SN Counter to the UE over the RRC signaling path when it is required to generate a new KSN. The KSN is used to derive further RRC and UP keys that are used between the UE and SN.”

[0009] According to 3GPP TS 38.331, vl8.5.1, Chapter 6.3.2:The IE SK-Counter is a counter used upon initial configuration of SN security for NR-DC and NE-DC, as well as upon refresh of S-KgNB or S-K6NB based on thecurrent or newly derived KSNB during RRC Resume or RRC Reconfiguration, as defined in TS 33.501 v!9.2.0 (2025-03-25).

[0010] The sk-counter is delivered to the UE via the RRCReconfiguration message and is applied when the UE processes the corresponding RRCReconfiguration. This field is determined and set by the Master Node (MN)

[0011] sk-Counter: A counter used upon initial configuration of S-KSNB or S-K6NB, as well as upon refresh of S-KSNB or S-K6NB. This field is always included either upon initial configuration of an NR SCG or upon configuration of the first RB with keyToUse set to secondary, whichever happens first. This field is absent if there is neither any NR SCG nor any RB with keyToUse set to secondary, or if the RRCReconfiguration message is contained in condRRCReconfig for subsequent CP AC.SUMMARY

[0012] The methods and apparatus proposed in the present disclosure allow the user equipment to inform the MN about which sk-counter has selected in case an LTM cell switch procedure is performed at the SN. This enables security to be established between the UE and the SN and avoids the UE declaring failure with a consequent triggering of the RRC re-establishment procedure or any other recovery procedure. In turn, this may prevent a very long connectivity interruption and a high signaling overhead for both the network and the UE.

[0013] In one embodiment, there is provided a method performed by a user equipment for providing security information to a first network node. The method starts with the first network node receiving a mobility command from the first network node to trigger a mobility procedure, such as Layerl / Layer 2 Triggered Mobility, LTM, procedure at a second network node. The mobility procedure comprises changing of a security key at the second network node, wherein the UE has a mobility configuration from the first network node comprising a list of sk-counter values. Then, the UE is selecting an sk-counter value from the list of sk-counter values and transmitting the selected sk-counter value to the first network node as part of execution of the mobility procedure. The transmission may be direct or indirect, such as forwarded through an intermediate network node.

[0014] In another embodiment, there is provided a method performed by a first network node for receiving security information. The method starts with the first network node providing a user equipment, UE, with a mobility configuration comprising a list of sk-counter values. This is done by the network node transmitting, to the UE, a mobility command to trigger a mobility procedure at a second network node, which comprises changing a security key at the second network node.Then, the first network node is receiving, a selected sk-counter value as part of execution of the mobility procedure, determining a new secondary key for the second network node based on the selected sk-counter value, and transmitting the new secondary key to the second network node.

[0015] In another embodiment, there is provided a method performed by a second network node for conveying security information. The method starts with the second network node receiving, from a user equipment, a selected sk-counter value as part of execution of a mobility procedure. Then, the second network node is transmitting to a first network node, the received selected sk-counter value and receiving, from the first network node, a new secondary security key to be applied according to the selected sk-counter value.

[0016] Further, in other embodiments, there are provided user equipment, first network node, and second network node apparatus, configured to perform the respective methods of the disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0018] Figure 1 shows a message sequence chart of a method for conveying and providing security information in accordance with some embodiments of the present disclosure;

[0019] Figure 2 shows an example of a communication system in accordance with some embodiments of the present disclosure;

[0020] Figure 3 is another example of a communication system according to some embodiments of the present disclosure;

[0021] Figure 4 shows a wireless device, which may be configured to operate in the communication system of Figure 2 or in the communication system of Figure 3;

[0022] Figure 5 shows a network node in accordance with some embodiments of the present disclosure; and

[0023] Figure 6 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.DETAILED DESCRIPTION

[0024] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled inthe art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

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

[0026] There currently exist certain challenge(s).

[0027] According to what has been agreed for Layer 1 / Layer 2 L1 / L2 Triggered Mobility (LTM) in Rel-19, the Master Node (MN) provides to the User Equipment (UE) a list of sk-counters and, in case the security needs to be refreshed at the Secondary Node (SN), the UE will just pick one of such sk-counters and use it. According to this, the MN should be aware of which sk-counter the UE has picked because the MN needs to calculate the new secondary key (SN key) based on the selected sk-counter by the UE, and forward the newly derived SN key to the target SN to which the UE is going to perform an LTM cell switch procedure (either normal or conditional).

[0028] However, according to the agreed running CR in R2 -2502534, Running RRC CR for inter-CU and conditional LTM, Ericsson, RAN2#129bis, April 2025, one issue is that the sk-counter is reported from the UE to the MN within the MN RRCReconfigurationComplete message which carried (embedded) the SN RRCReconfigurationComplete message.

[0029] The following is an excerpt from Third Generation Partnership Program (3 GPP) Technical Specification (TS) 38.331 vl8.5.1, Chapter 6.3.2:START EXCERPT2> if this RRCReconfiguration message is applied due to an LTM cell switch execution procedure according to clause 5.3.5.18.6:3> if this RRCReconfiguration message was received via SRB 1 within the nr-SCG within mrdc- SecondaryCellGroup or via SRB3:4> include in the appliedLTM-Candidateld the LTM-Candidateld of the applied LTM candidate configuration;3> else if this RRCReconfiguration message was received via SRB 1 but not within the nr-SCG within mrdc-SecondaryCellGroup'.4> if a new sk-Counter value has been selected due to the LTM cell switch execution procedure: 5> include selectedSK-Counter and set its value to the selected sk-Counter value;END EXCERPT

[0030] However, if an LTM cell switch is performed at the SN, there is no MN RRCReconfigurationComplete message sent from the UE to the MN since the SN RRCReconfigurationComplete which belongs to the SN is delivered by the UE via the ULInformationTransferMRDC message.

[0031] In this case, the MN will not get the sk-counter selected by the UE and this means that no secondary key can be derived for the new SN. This means that security cannot be established and thus the UE will at some point trigger the Radio Resource Control (RRC) re-establishment procedure.

[0032] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The methods and solutions proposed in this disclosure rely fundamentally on two options:• In the first option, the sk-counter selected by the UE is sent by the UE to the Master Node (MN) via a new or existing message which is not the RRCReconfigurationComplete message.• In a second option, the sk-counter selected by the UE is sent by the UE first to the SN, and then the Secondary Node (SN) forwards the received sk-counter to the MNo In this option, once the MN receives the sk-counter from the SN, it calculates the new secondary key and then it sends it back to the SN.

[0033] Certain embodiments may provide one or more of the following technical advantage(s). The methods and solutions proposed in the present disclosure allow the UE to inform the MN about which sk-counter has selected in case an LTM cell switch procedure is performed at the SN. This basically allows the security to be established between the UE and the SN and will avoid that the UE declares failure with a consequent triggering of the RRC reestablishment procedure or any other recovery procedure. This in fact will avoid very long connectivity interruption and a high signaling overhead on the network and UE side.

[0034] The disclosure refers to the term “L1 / L2 based inter-cell mobility”, though it interchangeably also uses the terms L1 / L2 mobility, Ll-mobility, LI based mobility, L1 / L2-centric inter-cell mobility, L1 / L2 inter-cell mobility L1 / L2 Triggered Mobility, Lower-layer triggered Mobility or LTM. The basic principle is that the UE receives a lower layer signaling (e.g. a MAC CE) from the network indicating to the UE a change (or switch or activation) of includes 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 cells (e.g. reception of an RRC Reconfiguration message, with at least one LTM candidate cell configuration) A candidate cellconfiguration may include parameters in the IE CellGroupConfig per candidate cell and / or an embedded RRC Reconfiguration per candidate cell.

[0035] The term LTM cell switch procedure refers to the process of a UE changing its cell from a source cell to a target cell (which may be called here a candidate cell or a neighbour cell), using L1 / L2 triggered mobility (LTM). In the context of L1 / L2 triggered mobility (LTM), an LTM cell switch procedure may sometimes also be known as dynamic switch, LTM switch, (LTM) cell switch, (LTM) serving cell change or (LTM) cell change. Even if the term change of cell is used, that may comprise a change of a whole cell group configuration, which includes a change in the 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). The LTM cell switch procedure may be triggered by the UE receiving an LTM cell switch command from the network. The source and target cells in a LTM cell switch procedure may be controlled by the same gNB, which sometimes is referred to as the intra-gNB case, or when the gNB uses a distributed CU / DU RAN architecture, the intra-CU inter-DU case or the intra-CU intra-DU case (depending on whether the cells are controlled by the same DU or different DUs). When the source and target cells in a LTM cell switch procedure are controlled by different gNBs, this is sometimes referred to as the inter-gNB case, or inter-CU case, or sometimes known as an inter-CU LTM cell switch procedure

[0036] The disclosure refers to at least one LTM candidate cell configuration. This is also sometimes referred to as a configuration of a LTM candidate cell, which may be an RRC configuration, such as encapsulated in an RRC Reconfiguration message, that the UE receives when being configured with L1 / L2 Triggered Mobility. A LTM candidate cell configuration comprises the configuration which the UE needs to start to operate accordingly when it performs an LTM cell switch procedure to that LTM 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, which becomes the target cell and the current (new) SpCell, or an sCell in a serving frequency. The LTM candidate cell configuration comprises parameters of a serving cell (or multiple serving cells, such as a cell group), comprising one or more of the groups of parameters, such as an RRCReconfiguration message, an IE CellGroupConfig or an IE SpCellConfig (or the IE sCellConfig, in the case of a Secondary Cell).

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

[0038] An inter-CU LTM cell switch procedure, sometimes also referred to as inter-CU LTM or inter-gNB LTM, is an LTM cell switch procedure resulting in a change of serving cell, e.g. change of SpCell, PCell, PSCell, to an LTM candidate cell controlled by a different gNB than the source gNB or serving gNB of the UE when the execution LTM cell switch procedure was triggered (e.g. upon reception of the LTM cell switch command). From UE point of view, the actions performed during an inter-CU LTM cell switch procedure may be the same type of actions of an LTM cell switch procedure, but may also include additional actions, such as change of security key(s).

[0039] The disclosure refers to inter Secondary Node L1 / L2 Triggered Mobility, inter-SN LTM, configuration of inter-SN LTM, execution of inter-SN LTM and an inter-SN LTM cell switch procedure. In the context of this disclosure, inter-SN LTM refers to inter-CU LTM, sometimes also referred to as inter-gNB LTM, handover or SCG mobility, when the UE is configured with dual connectivity, such as NR-DC, and where the source cell and target cell are both part of the source and target SCG, respectively, and controlled by different CUs or different gNBs.

[0040] The term conditional LTM refers to L1 / L2 Triggered Mobility where the execution of the LTM cell switch is triggered by the UE when an execution condition, such as a layer 1, layer 2 or a layer 3 event, criterion or condition related to, for example, a radio measurement, is fulfilled. Upon the cell switch the UE applies a stored LTM candidate cell configuration.

[0041] The disclosure refers to an inter-CU LTM candidate cell configuration. An inter-CU LTM candidate cell configuration is an LTM candidate cell configuration which contains the configuration which the UE needs to start to operate accordingly when it performs an LTM cell switch procedure to an LTM candidate cell which is controlled by a different base station, e.g. gNB, from the current source base station e.g. serving gNB of the UE. In some cases, the UE may receive an inter-CU LTM candidate cell configuration during configuration of inter-MN LTM. In some cases, the UE may apply an inter-CU LTM candidate cell configuration during execution of inter-MN LTM.

[0042] An inter-CU LTM candidate cell configuration may be the same as an LTM candidate cell configuration but it may also include additional information than what is included in the LTM candidate cell configuration used for inter-CU cell switch.. This additional information may be, for example:• Information to perform security key refresh, e.g. the RRC IE MasterKeyUpdate or a RRC IE RadioBearerConfig that includes SecurityConfig with Security AlgorithmConfig• Indication to perform PDCP re-establishment• Indication to perform a full configuration, e.g. the RRC field fullConfig

[0043] The disclosure refers to a mobility procedure, configuration of a mobility procedure or execution of a mobility procedure. In the context of this disclosure, a mobility procedure may be L1 / L2 Triggered Mobility, LTM, inter-CU LTM, inter-SN LTM, L3 handover, PCell handover, conditional handover (CHO), conditional LTM, PSCell change or conditional PSCell Addition or Change (CP AC). The solutions described in the disclosure sometimes uses the inter-SN LTM as the example. However, many of the examples may also be applied for other mobility procedures, for example, LTM, inter-CU LTM, conditional LTM or CHO.

[0044] The disclosure refers to a mobility configuration. When the UE has been configured with a mobility configuration, it may use the mobility configuration during preparation of a mobility procedure, including measurements (such as RSRP measurements on neighbor or serving cells), triggering and transmission of measurement reports, synchronization towards neighbor cells, evaluation of conditions (for conditional mobility, e.g. CHO), and during the execution of a mobility procedure (e.g. execution of an LTM cell switch procedure, execution of an inter-MN LTM cell switch procedure or execution of handover).

[0045] A mobility configuration may include one or multiple of the following type of elements where each element contains a configuration of one aspect of LTM, for example as follows:• LTM candidate cell configuration(s),• inter-CU LTM candidate cell configuration(s),• lower layer information, such as physical layer configuration, MAC layer configuration or RLC layer configuration, Cell Group configuration, serving cell configuration• higher layer information, such as RRC protocol parameters, such as timer values, PDCP layer configuration, radio bearer configuration or measurement configuration• Configuration of measurements for LTM• Configuration for measurement reports for LTM• CSI resource configuration(s) for LTM• CSI report configuration for LTM• Configurations of early synchronization procedures, such aso Configurations for DL pre-sync for LTM, such as configurations for early TCI state activationo Configurations for UL pre-sync for LTM, such as configurations for reception of PDCCH ordered triggered preamble transmission and reception of TA• Configurations for the execution of an LTM cell switch procedure for a given LTM candidate cell configuration or inter-CU LTM candidate cell configuration (e.g., whether to perform random access procedure, whether to perform RLC reestablishment, or MAC reset, or PDCP recovery), a timer value, configured UL grants, dedicated RA preambles .• A configuration which the UE needs to start to operate accordingly when it performs an LTM cell switch procedure to an LTM candidate cell which is controlled by a different base station, e.g. gNB, from the current source base station e.g. serving gNB of the UE.• Information to perform security key refresh, e.g. the RRC IE MasterKeyUpdate or a RRC IE Radi oB ear erConfig that includes SecurityConfig with Security AlgorithmConfig.• Indication to perform a full configuration, e.g. the RRC field fullConfig.• Indication to perform L2 re-establishment, such as an indication to perform PDCP reestablishment for one or multiple bearers.• One or more lists of sk-counters values.

[0046] The term “subsequent LTM”, sometimes also referred to a “subsequent LTM cell switch (procedures)” refers to that the UE performs a first LTM cell switch procedure from a source cell to a first target cell, then performs a second LTM cell switch procedure from the first target cell (which is now the new source cell) to a second target cell, and between the first and second LTM cell switch procedures there is no RRC reconfiguration of the UE. This implies also that the network does not add / remove / modify the LTM candidate cell configuration(s) or inter-CU LTM candidate cell configuration(s) in the UE between the two LTM cell switch procedures.

[0047] The disclosure refers also to “handling of the configuration of the mobility procedure”. This is the case where a network node indicates to another network node either an indication to configuration or not configure a certain procedure (e.g., a mobility procedure) where this indication is in the form of a suggestion. Alternatively, this indication is in a form of a restriction, and in this case a network node indicates to another network node whether the another network node is allowed or not to configure a certain procedure (e.g., a mobility procedure).

[0048] The disclosure uses the term “cell” to identify a location (or coverage) on which the UE is located. However, the term “cell” can also be exchanged without any loss of meaning with the terms “radio resources”, “beams”, “TCI state”, or “TRS”. This is just to clarify that this disclosure does not target specifically a scenario where there is a cell, but rather when a UE uses a set of source radio resources and need to switch to a target set of radio resources. In such a case,radio resource can also identify a set of configurations, field, parameters, or ASN.l structures or IES.

[0049] The disclosure further uses the term MCG to identify a first network node that provides a first connectivity link to the UE and SCG to identify e second network node that provides a second connectivity link to the UE. However, the terms “MCG” and “MN” can be exchanged without any loss of meaning as well as the terms “SCG” and “SN”.

[0050] The term “LTM” or “L1 / L2 triggered mobility” include also the case of Conditional LTM (CLTM), which can be viewed as a form of conditional reconfiguration. In CLTM, the UE is configured with at least one LTM candidate cell (denoted as a CLTM candidate cell), by receiving an LTM candidate cell configuration, as in legacy LTM, and called herein a Conditional LTM candidate cell configuration, and an associated execution condition, denoted as CLTM execution condition. The evaluation of CLTM execution condition associated to a CLTM candidate cell is performed by the assessment of lower layer measurements, such as Layer 1 reference signal received power (Ll-RSRP) and / or SS-RSRP, derived from SSBs and / or CSLRSs of either the source cell and / or an LTM candidate cell. Lower layer measurements, in this context, are measurements reported to support lower layer procedures like beam management, candidate cell TCI state activation / deactivation, early 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.

[0051] 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 disclosure, upon satisfaction of the execution condition(s), the UE initiates an LTM cell switch.

[0052] 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 context of Conditional LTMexecution, the text may refer to the serving cell before the LTM cell switch as source cell, old source cell, or previous source cell.

[0053] The disclosure also discusses 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 disclosure. 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.

[0054] In the method outlined, the UE receives an LTM candidate cell configuration for Conditional LTM, typically through an RRC Reconfiguration message, which is stored in the UE and applied upon fulfillment of the associated CLTM execution conditions. An LTM candidate cell configuration comprises the configuration which the UE needs to start to operate accordingly when it performs a Conditional LTM execution to that LTM candidate cell e.g., upon the fulfilment of CLTM execution conditions. A candidate cell configuration may include parameters in the information element (IE) CellGroupConfig per LTM candidate cell and / or an embedded RRC Reconfiguration per candidate cell. An LTM candidate cell configuration is associated with an identifier which is used in the signaling when referring to a certain LTM candidate cell configuration, such as when performing the early UL or DL synchronization with that LTM cell. This identifier is sometimes known as the LTM candidate cell configuration identifier (ID) or LTM candidate configuration index (or similar).

[0055] Figure 1 shows a message sequence chart of a method for conveying and providing security information in accordance with some embodiments of the present disclosure.

[0056] In Figure 1, at step 108, the first network node 106 can send a mobility configuration comprising a list of sk-counter values to UE 102.

[0057] At step 110, the first network node 108 sends to the UE 102 a a mobility command to trigger a mobility procedure at a second network node (104) which comprises changing a security key at the second network.

[0058] At step 112, the UE 102 selects an sk-counter value from the list of sk-counter values.

[0059] In an embodiment, the selecting the sk-counter value is performed in response to fulfillment of execution conditions that are part of the mobility configuration and not upon reception of the mobility command.

[0060] At steps 114 and 116, the UE 102 may alternately transmit the selected sk-counter balue to the first network node 106 either directly (step 114) or via the second network node 104 at steps 116, and then the second network node 104 can convey the selected sk-counter value to the first network node at step 118. At step 118, the the message received from the second network node (104) is received via a new or existing XnAP message or a new or existing F1AP message.

[0061] In an embodiment, the selected sk-counter value is transmitted at step 114 by the UE 102 to the first network node 106 within a message that contains a message for the second network node 104 to acknowledge completion of the mobility procedure.

[0062] In an embodiment, a message that includes the selected sk-counter value is not a message sent to the first network node 106 to acknowledge completion of the mobility procedure.

[0063] In an embodiment, the selected sk-counter value is transmitted at step 116 to the first network node 106 via a second network node 104 within a message that is used to acknowledge completion of the mobility procedure.

[0064] In an embodiment, the message to the second network node 104 is a new message.

[0065] In an embodiment, the transmitting the selected sk-counter value comprises transmitting a message to either the first network node 106 directly or via a second network node (04, and the transmitting is via one of a radio resource control, RRC, message; a Medium Access Control (MAC) Control Element (CE); or a LI message.

[0066] In an embodiment, the message sent to the first network node 106 is a ULInformationTransferMRDC message.

[0067] In an embodiment, the message sent to the second network node 104 is a RRCReconfigurationComplete message.

[0068] In an embodiment, the first network node 106 is a source gNB Distributed Unit (gNB-DU) or source gNB Central Unit (gNB-CU) or a source gNB. Likewise, the second network node 104 could be a target gNB Distributed Unit (gNB-DU) or target gNB Central Unit (gNB-CU) or a target gNB. The first network node 106 could be is a Master Node (MN) or a Master Cell Group (MCG) while the second network node 104 is a Secondary Node (SN) or Secondary Cell Group (SCG).

[0069] At step 120, the first network node 108 determines a new secondary key for the second network node (104) based on the selected sk-counter value, and at step 122, the first network node 108 transmits the new secondary key to the second network node 104.

[0070] Also disclosed herein is a proposed modification to TS 38.331 vl8.5.1 where the underlined text is the additional proposed text to section 5.3.5.3 “Reception of an RRCReconfiguration by the UE”:START EXCERPT2> if this RRCReconfiguration message is applied due to an LTM cell switch execution procedure according to clause 5,3.5.18.6:3>if WAs RRCReconfiguration message was received via SRB1 within the nr-SCG within mrdc-SecondaryCellGroup or via SRB3:4> include in the appliedLTM-Candidateld LTM-Candidateld of the applied LTM candidate configuration;3>else if this RRCReconfiguration message was received via SRB1 but not within the nr-SCG within mrdc-SecondaryCellGroup'.4> if a new sk-Counter value has been selected due to the LTM cell switch execution procedure:5> include selectedSK-Counter and set its value to the selected sk-Counter value within the ULInformationTransferMRDC message;END EXCERPT

[0071] Also disclosed herein is a proposed modification to TS 38.331 vl8.5.1 where the underlined text is the additional proposed text to section 6.2.2 “Message Definitions”:START EXCERPTThe ULInformationTransferMRDC message is used for the uplink transfer of MR-DC dedicated information (e.g. for transferring the NR or E-UTRA RRC MeasurementReport message, the Failureinformation message, the UEAssistancelnformation message, the RRCReconfigurationComplete message, the lABOtherlnformation message or the NR or E-UTRA RRC MCGFailur eInformation message).Signalling radio bearer: SRB1, SRB3RLC-SAP: AMLogical channel: DCCHDirection: UE to NetworkULInformationTransferMRDC messageiliiiillfBililiggiliiiBii lllll:laEsk:6hd:ffff:®aB;Of^h§:f6hiiiiiiiiiiiiiiiiiiiiiiiii6L^END EXCERPT

[0072] Also disclosed herein is a proposed alternative modification to TS 38.331 vl8.5.1 where the underlined text is the additional proposed text to section 5.3.5.3 “Reception of an RRCReconfiguration by the UE”:START EXCERPT2> if this RRCReconfiguration message is applied due to an LTM cell switch execution procedure according to clause 5,3.5.18.6:3>if WAs RRCReconfiguration message was received via SRB1 within the nr-SCG within mrdc-SecondaryCellGroup or via SRB3:4> include in the appliedLTM-Candidateld WIQ LTM-Candidateld of the applied LTM candidate configuration;3> if a new sk-Counter value has been selected due to the LTM cell switch execution procedure:4> include selectedSK-Counter and set its value to the selected sk-Counter value; END EXCERPT

[0073] Figure 2 shows an example of a communication system 200 in accordance with some embodiments.

[0074] In the example, the communication system 200 includes a telecommunications network 202 that includes an access network 204, such as a radio access network (RAN), and a core network 206, which includes one or more core network nodes 208. The access network 204 includes one or more access network nodes or base stations of various types, access network nodes210A and 21 OB are depicted (which may be collectively referred to as network nodes 210), or any other similar 3rdGeneration Partnership Project (3 GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 204 may include more than one access network technology. The network nodes 210 of access network 204 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 212A, 212B, 212C, and 212D (one or more of which may be generally referred to as UEs 212) to the core network 206 over one or more wireless connections.

[0075] 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 202 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 202 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 202, including one or more access network nodes 210 and / or core network nodes 208.

[0076] 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 O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0077] The network nodes 210 facilitate direct or indirect connection of one or more UEs 212 to the core network 206 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals usingelectromagnetic 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 200 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 200 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0078] The UEs 212 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 210 and other communication devices. Similarly, the network nodes 208, 210 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 202) with the UEs 212 and / or with other network nodes or equipment in the telecommunications network 202 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 202. More specifically, UEs 212 may send messages, data, and / or other signals to network nodes 208, 210 or other elements of the telecommunications network 202 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 208, 210 may send messages, data, and other signals to UEs 2122, other network nodes 208, 210, and other devices in telecommunications network 202 directly or indirectly. As one specific example, a core network node 208 may transmit a particular message to a UE 212 by transmitting the message to an access network node 210 that will then transmit the message to the intended UE 212. Similarly, a core network node 208 may receive a particular message from a UE 212 by receiving the message from an access network node 210 that itself received the message from the UE 212.

[0079] In the depicted example, the core network 206 connects elements of the access network 204 (e.g., one or more of the network nodes 210) to one or more host computing systems, such as host 216. 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 206 includes one or more core network nodes (e.g., core network node 208) of various types, one or more of which may be generally referred to as network nodes 208. Network nodes 208 are structured with hardware and software components. Features of these components may besubstantially 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 208. 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).

[0080] The host 216 may be under the ownership or control of a service provider other than an operator or provider of the access network 204 and / or the telecommunications network 202. The host 216 may be operated by the service provider or on behalf of the service provider. The host 216 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0081] As a whole, the communication system 200 of Figure 2 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 200 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 200 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 200 supporting different standards, protocols, or rule sets.

[0082] As one example, in certain embodiments, access network 204 may contain some access network nodes 210 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 210 support (or the same access network nodes 210 additionallysupport) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 202 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 204 and / or a core network 206 that supports multiple different standard generations or may include multiple access networks 204 and / or multiple core networks 206 with individual networks 204, 206 supporting different standard generations.

[0083] Telecommunications network 202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 202. For example, the telecommunications network 202 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.

[0084] In some examples, one or more of the UEs 212 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 204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 204. 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).

[0085] In the example, the hub 214 communicates with the access network 204 to facilitate indirect communication between one or more UEs (e.g., UE 212C and / or 212D) and network nodes (e.g., network node 210B). In some examples, the hub 214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 214 may be a broadband router enabling access to the core network 206 for the UEs. As another example, the hub 214 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 210, or by executable code, script, process, or other instructions in the hub 214.

[0086] As another example, the hub 214 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 214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 214 then provides to the UE either directly, after performing local processing, and / or after addingadditional local content. In still another example, the hub 214 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0087] The hub 214 may have a constant / persistent or intermittent connection to the network node 210B. The hub 214 may also allow for a different communication scheme and / or schedule between the hub 214 and UEs (e.g., UE 212C and / or 212D), and between the hub 214 and the core network 206. In other examples, the hub 214 is connected to the core network 206 and / or one or more UEs via a wired connection. Moreover, the hub 214 may be configured to connect to an M2M service provider over the access network 204 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 210 while still connected via the hub 214 via a wired or wireless connection. In some embodiments, the hub 214 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 210B. In other embodiments, the hub 214 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 210B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0088] Figure 3 is another example of a communication system 300 according to some embodiments. As used herein, the communication system 300 includes multiple access points (APs) 310 (with four exemplary APs 310A, 310B, 310C, and 310D being depicted) and multiple wireless devices, referred to in the context of communication system 300 as stations (STAs) 312 (referred to individually as STA 312A, STA 312B, STA 312C, STA 312D, and STA 312E). STA 312A is served by AP 310A in a first basic service set (BSS) 320A. STA 310B and STA 310C are served by AP 310B in a second BSS, BSS 320B. STA 312D is served by AP 310C in a third BSS, BSS 320C. STA 312E is served by AP 310D in a fourth BSS, BSS 320D. Stations 312 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 312 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0089] Each of STAs 312 may connect through a radio link to one of APs 310. For example, depending on location or channel conditions experienced by a given STA 312, 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 exemptband like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0090] Each AP 310 may provide data connectivity to STAs 312 connected to a particular AP 310. As illustrated, APs 310 may be connected to a data network 330. In this way, APs 310 may also provide data connectivity between STAs 312 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 312 and its serving AP 310 may be used for providing various kinds of services to STA 312, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 312 and / or on a device linked to STA 312. By way of example, Figure 3 illustrates an application service platform 332 provided in data network 330. The application(s) executed on STA 312 and / or on one or more other devices linked to STA 312 may use the radio link for data communication with one or more other STA 312 and / or the application service platform 332, thereby enabling utilization of the corresponding service(s) at STA 312.

[0091] Figure 4 shows a wireless device 400, which may be configured to operate in communication system 200 of Figure 2 or in communication system 300 of Figure 3. The wireless device 400 may be alternatively referred to as a UE 400, like a UE 212 within the context of communication system 200, or as a station (STA) 400 or as a non-access-point station (non-AP STA) 400, like a STA 312 within the context of the communication system 300, 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.

[0092] A wireless device 400 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 400 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 400 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 400 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).

[0093] In particular embodiments, wireless device 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a power source 408, a memory 410, a communication interface 412, and / or any other component, or any combination thereof. Certain embodiments of wireless device 400 may include all or a subset of the components shown in Figure 4. The level of integration between the components may vary from one embodiment of wireless device 400 to another. In general, in a particular embodiment of wireless device 400, processing circuitry 402, input / output interface 406, power source 408, memory 410, and communication interface 412 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 400. Further, certain embodiments of wireless devices 400 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0094] The processing circuitry 402 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 410. The processing circuitry 402 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 402 may include multiple central processing units (CPUs).

[0095] In the example, the input / output interface 406 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 400. 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.

[0096] In some embodiments, the power source 408 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 408 may further include power circuitry for delivering power from the power source 408 itself, and / or an external power source, to the various parts of wireless device 400 via input circuitry or an interface such as an electrical power cable. Power source 408 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 400 to which power is supplied.

[0097] The memory 410 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 410 includes one or more programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416. The memory 410 may store, for use by wireless device 400, any of a variety of various operating systems or combinations of operating systems.

[0098] The memory 410 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 410 may allow wireless device 400 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, suchas one utilizing a communication system may be tangibly embodied as or in the memory 410, which may be or comprise a device-readable storage medium.

[0099] The processing circuitry 402 may be configured to communicate with an access network or other network via or using the communication interface 412. The communication interface 412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 422. The communication interface 412 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 418 and / or a receiver 420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 418 and receiver 420 may be coupled to one or more antennas (e.g., antenna 422) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0100] In the illustrated embodiment, communication functions of the communication interface 412 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0101] In particular embodiments, wireless device 400 may provide an output of data captured via a sensor, through its communication interface 412, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 400 can be communicated through a wireless connection to a network node via another wireless device 400. 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).

[0102] As another example, wireless device 400 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 400 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.

[0103] Wireless device 400, 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 surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 400 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 400 shown in Figure 4.

[0104] As yet another specific example, in an loT scenario, wireless device 400 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 400 may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, wireless device 400 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 400 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.

[0105] In practice, any number of wireless devices 400 may be used together with respect to a single use case. For example, a first wireless device 400 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 400 that is a remote controller operating the drone. When a user makes changes from theremote controller, the first wireless device 400 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 400 can also include more than one of the functionalities described above. For example, wireless device 400 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0106] Figure 5 shows a network node 500 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 500 may be configured to operate in communication system 200 of Figure 2, like network nodes 208 or 210, or in communication system 300 of Figure 3, like an AP 310 or a station 312. 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 NRNodeBs (gNBs)), O-RAN nodes or components of an 0-RAN node (e.g., O-RU, O-DU, O-CU).

[0107] Network nodes 500 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 500 may be a relay node or a relay donor node controlling a relay. Network nodes 500 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).

[0108] Other examples of network nodes 500 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).

[0109] In particular embodiments, network node 500 includes a processing circuitry 502, a memory 504, a communication interface 506, and a power source 508. In general, in a particular embodiment of network node 500, processing circuitry 502, memory 504, communicationinterface 506, and power source 508 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 500.

[0110] The network node 500 may be composed of multiple distinct network entities (e.g., a NodeB entity and an 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 500 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 500 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 504 or portions of memory 504 for different RATs) and some components may be reused (e.g., a same antenna 510 may be shared by different RATs). The network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, 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 500.[OHl] The processing circuitry 502 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 504, to provide network node 500 functionality.

[0112] In some embodiments, the processing circuitry 502 includes a system on a chip (SOC).In some embodiments, the processing circuitry 502 includes one or more of radio frequency (RF) transceiver circuitry 512 and baseband processing circuitry 514. In some embodiments, the RF transceiver circuitry 512 and the baseband processing circuitry 514 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 512 and baseband processing circuitry 514 may be on the same chip or set of chips, boards, or units.

[0113] The memory 504 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 502. The memory 504 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 502 and utilized by the network node 500. The memory 504 may be used to store any calculations made by the processing circuitry 502 and / or any data received via the communication interface 506. In some embodiments, the processing circuitry 502 and memory 504 is integrated.

[0114] The communication interface 506 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 506 comprises port(s) / terminal(s) 516 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 400 may be capable of wireless communication and communication interface 506 may also include radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, an antenna 510. Particular embodiments of radio front-end circuitry 518 include filter(s) 520 and amplifier(s) 522. The radio front-end circuitry 518 may be connected to an antenna 510 and processing circuitry 502. The radio front-end circuitry may be configured to condition signals communicated between antenna 510 and processing circuitry 502. The radio front-end circuitry 518 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 518 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 520 and / or amplifiers 522. The radio signal(s) may then be transmitted via the antenna 510. Similarly, when receiving data, the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518. The digital data may be passed to the processing circuitry 502. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0115] In certain alternative embodiments, network node 500 may be capable of wireless communication but does not include separate radio front-end circuitry 518, instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 512 is part of the communication interface 506. In still other embodiments, the communication interface 506 includes one or more ports or terminals 516, the radio front-end circuitry 518, and the RF transceiver circuitry 512, aspart of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).

[0116] The antenna 510 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 510 may be coupled to the radio front-end circuitry 518 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 510 is separate from the network node 500 and connectable to the network node 500 through one or more interfaces or ports.

[0117] The antenna 510, communication interface 506, and / or the processing circuitry 502 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 500. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 510, the communication interface 506, and / or the processing circuitry 502 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 500. Any information, data and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0118] The power source 508 provides power to the various components of network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein. For example, the network node 500 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 508. As a further example, the power source 508 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0119] Embodiments of the network node 500 may include additional components beyond those shown in Figure 5 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 500 may include user interface equipment to allow input of information into the network node 500 and to allow output of information from the network node 500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 500.

[0120] Figure 6 is a block diagram illustrating a virtualization environment 600 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 600 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 600 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.

[0121] Applications 602 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0122] Hardware 604 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 606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 608A and VM 608B (which may be collectively referred to as VMs 608), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 606 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 608.

[0123] The VMs 608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 606. Different embodiments of the instance of a virtual appliance 602 may be implemented on one or more of VMs 608, 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, physicalswitches, and physical storage, which can be located in data centers, and customer premise equipment.

[0124] In the context of NFV, each of the VMs 608 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 608, and that part of hardware 604 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 608 on top of the hardware 604 and corresponds to an application 602.

[0125] Hardware 604 may be implemented in a standalone network node with generic or specific components. Hardware 604 may implement some functions via virtualization. Alternatively, hardware 604 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 610, which, among others, oversees lifecycle management of applications 602. In some embodiments, hardware 604 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 612 which may alternatively be used for communication between hardware nodes and radio units.

[0126] 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 maybe 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.

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

[0128] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein. To further exemplify the solutions proposed in a more general sense, below there is provided a list of embodiments useful for understanding the invention.

[0129] A method performed by a User Equipment, UE, (102) for wireless device for providing security information to a first network node (106), the method comprising:

[0130] receiving (110) a mobility command from the first network node (106) to trigger a mobility procedure at a second network node (104) which comprises changing a security key at the second network node (104), wherein the UE (102) has a mobility configuration from the first network node (106) comprising a list of sk-counter values;selecting (112) an sk-counter value from the list of sk-counter values; andtransmitting (114, 116) the selected sk-counter value to the first network node (106) as part of execution of the mobility procedure.

[0131] The method of embodiment 2, wherein the selecting the sk-counter value is performed in response to fulfillment of execution conditions that are part of the mobility configuration and not upon reception of the mobility command.

[0132] The method of embodiment 1, wherein the selected sk-counter value is transmitted (114) by the UE (102) to the first network node (106) within a message that contains a message for the second network node (104) to acknowledge completion of the mobility procedure.

[0133] The method of embodiment 1, wherein a message that includes the selected sk-counter value is not a message sent to the first network node (106) to acknowledge completion of the mobility procedure.

[0134] The method of embodiment 1, wherein the selected sk-counter value is transmitted (116) to the first network node (106) via a second network node (104) within a message that is used to acknowledge completion of the mobility procedure.

[0135] The method of embodiment 5, wherein the message to the second network node (104) is a new message.

[0136] The method of any of embodiments 1 to 6, wherein the transmitting the selected sk-counter value comprises transmitting a message to either the first network node (106) directly or via a second network node (104), and the transmitting is via one of:

[0137] a radio resource control, RRC, message;a Medium Access Control, MAC, Control Element, CE; ora Layer 1, LI, message.The method of embodiment 3, wherein the message sent to the first network node (106) is a ULInformationTransferMRDC message.

[0138] The method of embodiment 5, wherein the message sent to the second network node (104) is a RRCReconfigurationComplete message.

[0139] The method of any of embodiments 1 to 9, wherein the first network node (106) is a source gNB Distributed Unit, gNB-DU, or source gNB Central Unit, gNB-CU, or a source gNB.

[0140] The method of any of embodiments 1 to 10, wherein the second network node (104) is a target gNB Distributed Unit, gNB-DU, or target gNB Central Unit, gNB-CU, or a target gNB.

[0141] The method of any of embodiments 1 to 11, wherein the first network node (106) is a Master Node, MN, or a Master Cell Group, MCG.

[0142] The method of any of embodiments 1 to 12, wherein the second network node (104) is a Secondary Node, SN, or a Secondary Cell Group, SCG.

[0143] A User Equipment, UE, (102) for providing security information to a first network node (106), the UE (102) configured to: receive (110) a mobility command from the first network node (106) to trigger a mobility procedure at a second network node (104) which comprises changing a security key at the second network node (104), wherein the UE (102) has a mobility configuration from the first network node (106) comprising a list of sk-counter values;select (112) an sk-counter value from the list of sk-counter values; andtransmit (114, 116) the selected sk-counter value to the first network node (106) as part of execution of the mobility procedure.

[0144] The UE (102) of embodiment 14, wherein the UE (102) is further configured to perform any of the embodiments 2 to 13.

[0145] A method performed by a first network node (106) for receiving security information, the method comprising:

[0146] providing (108) to a User Equipment, UE, (102) a mobility configuration comprising a list of sk-counter values;transmitting (110), to the UE (102), a mobility command to trigger a mobility procedure at a second network node (104) which comprises changing a security key at the second network node (104),receiving (114, 118), a selected sk-counter value as part of execution of the mobility procedure; determining (120) a new secondary key for the second network node (104) based on the selected sk-counter value; andtransmitting (122) the new secondary key to the second network node (104).

[0147] The method of embodiment 16, wherein the selected sk-counter value is received from either the UE (102) or the second network node (104) without transmitting a mobility command to the UE (102).

[0148] The method of any of embodiments 16 to 17, wherein the selected sk-counter value is received (114) from the UE (102) within a message which also comprises a message for the second network node (104) to acknowledge completion of the mobility procedure.

[0149] The method of embodiment 18, wherein the message that includes the selected sk-counter value is not a message to acknowledge completion of the mobility procedure.

[0150] The method of embodiment 16, wherein the selected sk-counter value is received (118) from the second network node (104) within a new or existing message.

[0151] The method of embodiment 16, wherein the receiving the selected sk-counter value comprises receiving one or more of:a radio resource control, RRC, message;a Medium Access Control, MAC, Control Element, CE; ora Layer 1, LI, message.

[0152] The method of embodiment 20, wherein the message received from the second network node (104) is received via a new or existing XnAP message.

[0153] The method of embodiment 20, wherein the message received from the second network node (104) is received via a new or existing F1AP message.

[0154] The method of embodiment 18, wherein the message received from the UE (102) is a ULInformationTransferMRDC message.

[0155] The method of any of embodiments 16 to 24, wherein the first network node (106) is a source gNB Distributed Unit, gNB-DU, or source gNB Central Unit, gNB-CU, or a source gNB.

[0156] The method of any of embodiments 16 to 25, wherein the second network node (104) is a target gNB Distributed Unit, gNB-DU, or target gNB Central Unit, gNB-CU, or a target gNB.

[0157] The method of any of embodiments 16 to 26, wherein the first network node (106) is a Master Node, MN, or a Master Cell Group, MCG.

[0158] The method of any of embodiments 16 to 27, wherein the second network node (104) is a Secondary Node, SN, or a Secondary Cell Group, SCG.

[0159] A first network node (106) for receiving security information, the first network node (106) configured to:provide (108) to a User Equipment, UE, (102) a mobility configuration comprising a list of sk-counter values;transmit (110), to the UE (102), a mobility command to trigger a mobility procedure at a second network node (104) which comprises changing a security key at the second network, receive(l 14, 116), a selected sk-counter value as part of execution of the mobility procedure; determine (120) a new secondary key for the second network node (104) based on the selected sk-counter value; and

[0160] transmit (122) the new secondary key to the second network node (104).

[0161] The first network node (106) of embodiment 29, wherein the first network node (106) is further configured to perform any of the embodiments 17 to 28.

[0162] A method performed by a second network node (104) for conveying security information, the method comprising:

[0163] receiving (116), from a User Equipment, UE, (102) a selected sk-counter value as part of execution of a mobility procedure;

[0164] transmitting (118) to a first network node (106), the received selected sk-counter value; and

[0165] receiving (122), from the first network node (106), a new secondary security key to be applied according to the selected sk-counter value.

[0166] The method of embodiment 31, wherein a new secondary key to be applied is received regardless of whether a selected sk-counter value has been received by the UE (102) or transmitted to the first network node (106).

[0167] The method of embodiment 31, wherein the selected sk-counter value is received from the UE (102) within a message which is used to acknowledge the completion of the mobility procedure.

[0168] The method of embodiment 33, wherein the message received from the UE (102) which includes the sk-counter value is a new message.

[0169] The method of embodiment 33, wherein the message received from the UE (102) is one or more of:an radio resource control, RRC, message;a Medium Access Control, MAC, Control Element, CE; ora Layer 1, LI, message.

[0170] The method of embodiment 33, wherein the message received from the UE (102) is a RRCReconfigurationComplete message.

[0171] The method of any of embodiments 31 to 36, wherein the first network node (106) is a source gNB Distributed Unit, gNB-DU, or source gNB Central Unit, gNB-CU, or a source gNB.

[0172] The method of any of embodiments 31 to 37, wherein the second network node (104) is a target gNB Distributed Unit, gNB-DU, or target gNB Central Unit, gNB-CU, or a target gNB.

[0173] The method of any of embodiments 31 to 38, wherein the first network node (106) is a Master Node, MN, or a Master Cell Group, MCG.

[0174] The method of any of embodiments 31 to 39, wherein the second network node (104) is a Secondary Node, SN, or a Secondary Cell Group, SCG.

[0175] A second network node (104) for conveying security information, the second network node (104) configured to:receive (116), from a User Equipment, UE, (102) a selected sk-counter value as part of execution of a mobility procedure;transmit (118) to a first network node (106), the received selected sk-counter value; and receive (122), from the first network node (106), a new secondary security key to be applied according to the selected sk-counter value.

[0176] The second network node (104) of embodiment 29, wherein the second network node (104) is further configured to perform any of the embodiments 32 to 40.

Claims

CLAIMS1. A method performed by a user equipment, UE (102), for providing security information to a first network node (106), the method comprising:receiving (110) a mobility command from the first network node (106) to trigger a mobility procedure at a second network node (104) which comprises changing a security key at the second network node (104), wherein the UE (102) has a mobility configuration from the first network node (106) comprising a list of sk-counter values;selecting (112) an sk-counter value from the list of sk-counter values; andtransmitting (114, 116) the selected sk-counter value to the first network node (106) as part of execution of the mobility procedure.

2. The method of claim 2, wherein the selecting the sk-counter value is performed in response to fulfillment of execution conditions that are part of the mobility configuration and not upon reception of the mobility command.

3. The method of any previous claims, wherein the selected sk-counter value is transmitted (114) by the UE (102) to the first network node (106) within a message that contains a message for the second network node (104) to acknowledge completion of the mobility procedure.

4. The method of any previous claims, wherein the selected sk-counter value is transmitted (116) to the first network node (106) via the second network node (104) within a message that is used to acknowledge completion of the mobility procedure.

5. The method of claim 3 to 4, wherein the message to the second network node (104) is a new message.

6. The method of any of claims 1 to 5, wherein the transmitting the selected sk-counter value comprises transmitting a message to either the first network node (106) directly or via a second network node (104), and the transmitting is via one of:a radio resource control, RRC, message;a Medium Access Control, MAC, Control Element, CE; ora Layer 1, LI, message.

7. The method of claims 3 to 6, wherein the message sent to the second network node (104) is a RRCReconfigurationComplete message.

8. The method of any previous claims, wherein the first network node (106) is a source gNB Distributed Unit, gNB-DU, or source gNB Central Unit, gNB-CU, or a source gNB.

9. The method of any previous claims, wherein the second network node (104) is a target gNB Distributed Unit, gNB-DU, or target gNB Central Unit, gNB-CU, or a target gNB.

10. The method of any previous claims, wherein the first network node (106) is a Master Node, MN, or a Master Cell Group, MCG.

11. The method of any previous claims, wherein the second network node (104) is a Secondary Node, SN, or a Secondary Cell Group, SCG.

12. A user equipment, UE (102), for providing security information to a first network node (106), the UE configured to:receive (110) a mobility command from the first network node to trigger a mobility procedure at a second network node (104) which comprises changing a security key at the second network node, wherein the UE has a mobility configuration from the first network node comprising a list of sk-counter values;select (112) an sk-counter value from the list of sk-counter values; andtransmit (114, 116) the selected sk-counter value to the first network node as part of execution of the mobility procedure.

13. The user equipment (102) of claim 12, wherein the UE is further configured to perform the method according to any of the claims 2 to 11.

14. A method performed by a first network node (106) for receiving security information, the method comprising:providing (108) to a user equipment, UE (102), a mobility configuration comprising a list of sk-counter values;transmitting (110), to the user equipment, a mobility command to trigger a mobility procedure at a second network node (104) which comprises changing a security key at thesecond network node,receiving (114, 118), a selected sk-counter value as part of execution of the mobility procedure;determining (120) a new secondary key for the second network node based on the selected sk-counter value; andtransmitting (122) the new secondary key to the second network node.

15. The method of claim 14, wherein the selected sk-counter value is received from either the UE (102) or the second network node (104), without transmitting a mobility command to the UE.

16. The method of claims 14 to 15, wherein the selected sk-counter value is received (114) from the UE (102) within a message which also comprises a message for the second network node (104) to acknowledge completion of the mobility procedure.

17. The method of claim 16, wherein the selected sk-counter value is received (118) from the second network node (104) within a new or existing message.

18. The method of claims 14 to 17 , wherein the receiving the selected sk-counter value comprises receiving one or more of:a radio resource control, RRC, message;a Medium Access Control, MAC, Control Element, CE; ora Layer 1, LI, message.

19. The method of claim 15 to 18, wherein the message received from the second network node (104) is received via a new or existing XnAP message.

20. The method of claims 15 to 19 , wherein the message received from the second network node (104) is received via a new or existing F1AP message.

21. The method of any of claims 14 to 20, wherein the first network node (106) is a source gNB Distributed Unit, gNB-DU, or source gNB Central Unit, gNB-CU, or a source gNB.

22. The method of any of claimsl4 to 21, wherein the second network node (104) is a target gNB Distributed Unit, gNB-DU, or target gNB Central Unit, gNB-CU, or a target gNB.

23. The method of any of claims 14 to 22, wherein the first network node (106) is a Master Node, MN, or a Master Cell Group, MCG.

24. The method of any of claims 14 to 23, wherein the second network node (104) is a Secondary Node, SN, or a Secondary Cell Group, SCG.

25. A first network node (106) for receiving security information, the first network node (106) configured to:provide (108) to a user equipment, UE (102), a mobility configuration comprising a list of sk-counter values;transmit (110), to the UE, a mobility command to trigger a mobility procedure at a second network node (104) which comprises changing a security key at the second network, receive(l 14, 116), a selected sk-counter value as part of execution of the mobility procedure;determine (120) a new secondary key for the second network node based on the selected sk-counter value; andtransmit (122) the new secondary key to the second network node.

26. The first network node (106) of claim 25, wherein the first network node is further configured to perform a method according to any of the claims 15 to 24.

27. A method performed by a second network node (104) for conveying security information, the method comprising:receiving (116), from a user equipment, UE (102), a selected sk-counter value as part of execution of a mobility procedure;transmitting (118) to a first network node (106), the received selected sk-counter value; andreceiving (122), from the first network node, a new secondary security key to be applied according to the selected sk-counter value.

28. The method of claim 27, wherein the selected sk-counter value is received from the UE (102) within a message which is used to acknowledge the completion of the mobility procedure.

29. The method of claim 28, wherein the message received from the UE (102) which includes the sk-counter value is a new message.

30. The method of claims 27 to 29, wherein the message received from the UE (102) is one or more of:an radio resource control, RRC, message;a Medium Access Control, MAC, Control Element, CE; ora Layer 1, LI, message.

31. The method of claims 27 to 30, wherein the message received from the UE (102) is a RRCReconfigurationComplete message.

32. The method of claims 27 to 31, wherein the first network node (106) is a source gNB Distributed Unit, gNB-DU, or source gNB Central Unit, gNB-CU, or a source gNB.

33. The method of claims 27 to 32, wherein the second network node (104) is a target gNB Distributed Unit, gNB-DU, or target gNB Central Unit, gNB-CU, or a target gNB.

34. The method of claims 27 to 33, wherein the first network node (106) is a Master Node, MN, or a Master Cell Group, MCG.

35. The method of claims 27 to 34, wherein the second network node (104) is a Secondary Node, SN, or a Secondary Cell Group, SCG.

36. A second network node (104) for conveying security information, the second network node configured to:receive (116), from a user equipment, UE (102), a selected sk-counter value as part of execution of a mobility procedure;transmit (118) to a first network node (106), the received selected sk-counter value; and receive (122), from the first network node, a new secondary security key to be applied according to the selected sk-counter value.

37. The second network node (104) of claim 36, wherein the second network node is further configured to perform the method of claims 28 to 35.