Enhanced handover process in communication network environment

By transmitting handover activation data, including key export parameters and hopping modes, in the 5G network, the problem of requiring RRC reconfiguration for multiple handovers in existing technologies is solved, improving network efficiency and security and reducing signaling overhead.

CN123125915APending Publication Date: 2026-11-17NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580027204.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-14
Filing Date
2025-04-11
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In 5G networks, existing technologies struggle to enable secure multiple handovers without reconfiguring Radio Resource Control (RRC) messages, resulting in limitations on network efficiency and security.

Method used

By transmitting handover enable data, including key export parameters and hopping modes, between user equipment and radio access nodes, user equipment can perform multiple handover operations in a single RRC message, reducing signaling overhead and enhancing security.

Benefits of technology

This enables multiple handovers in 5G networks without frequent RRC reconfiguration messages, improving network efficiency and security while reducing signaling overhead and potential attack surface.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125915A_ABST
    Figure CN123125915A_ABST
Patent Text Reader

Abstract

Techniques for enhanced handover operations in a communication network environment are disclosed. For example, from the perspective of a user equipment (UE), one method includes: receiving a reconfiguration message at the UE from a radio access node connected to the UE, the reconfiguration message including handover enable data for enabling the UE to perform two or more handover operations in response to the reconfiguration message; and the UE using the handover enable data to perform the two or more handover operations.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This field generally relates to communication networks, and more particularly, but not exclusively, to the security management of such communication networks. Background Technology

[0002] This section introduces aspects that will help in a better understanding of the invention. Therefore, the statements in this section should be read in this light and should not be construed as an admission of what is in the prior art or what is not.

[0003] Fourth-generation (4G) wireless mobile telecommunications technology, also known as Long Term Evolution (LTE) technology, is designed to provide high-capacity mobile multimedia with high data rates, particularly for human interaction. Next-generation or fifth-generation (5G) technology is designed not only for human interaction but also for machine-type communications in so-called Internet of Things (IoT) networks.

[0004] While 5G networks are designed to enable large-scale IoT services (e.g., a very large number of limited-capacity devices) and mission-critical IoT services (e.g., requiring high reliability), they also support improvements to traditional mobile communication services in the form of enhanced mobile broadband (eMBB) services, thereby providing improved wireless internet access for mobile devices.

[0005] In the example communication system, user equipment such as a mobile terminal (subscriber) (5G UE in a 5G network, or more broadly, UE) communicates via an air interface with a base station or access point of an access network in the 5G network, referred to as 5G AN. An access point (e.g., gNB) is illustratively part of the access network of the communication system.

[0006] For example, in 5G networks, the 5G Technical Specification (TS) 23.501, entitled "Technical Specification Group Services and Systems Aspects; System Architecture for 5G Systems," and TS 23.502, entitled "Technical Specification Group Services and Systems Aspects; Procedures for 5G Systems (5GS)," describe an access network known as the 5G AN, the disclosures of which are incorporated herein by reference in their entirety. Generally, an access point (e.g., a gNB) provides the UE with access to the core network (CN or 5GC), which in turn provides the UE with access to other UEs and / or data networks (such as packet data networks (e.g., the Internet)).

[0007] TS 23.501 further defines the service-based architecture (SBA) for 5G, which models services as network functions (NFs) that communicate with each other using a RESTful API.

[0008] In addition, TS 33.501, entitled “Technical Specification Group Services and Systems Aspects; Security Architecture and Processes for 5G Systems” (the contents of which are incorporated herein by reference in their entirety), further describes the security management details associated with 5G networks.

[0009] Security management is a critical consideration in any communications network environment. However, due to the ongoing efforts to improve the architecture and protocols associated with 5G and / or other networks in order to enhance network efficiency and / or subscriber convenience, security management issues related to inter-cell UE mobility (e.g., handover) in communications network environments can present significant technical challenges. Summary of the Invention

[0010] The illustrative embodiments provide techniques for enhanced handover operations in a communication network environment.

[0011] In one illustrative embodiment, from the perspective of a user equipment, a method includes: receiving a reconfiguration message at the user equipment from a radio access node connected to the user equipment, the reconfiguration message including handover enable data, the handover enable data being configured to enable the user equipment to perform two or more handover operations in response to the reconfiguration message; and having the user equipment perform the two or more handover operations using the handover enable data.

[0012] In another illustrative embodiment, from the perspective of a radio access node, a method includes: in response to receiving measurement data from a user equipment (UE) subscribed to a communication network, sending a first request from a first radio access node to a network node in the communication network; receiving a first response from the network node at the first radio access node, the first response including handover enable data for enabling the UE to perform two or more handover operations; sending a second request from the first radio access node to a candidate radio access node, the second request including at least a portion of the handover enable data; receiving a second response from the candidate radio access node at the first radio access node; identifying the candidate radio access node as a target radio access node based on the second response by the first radio access node; and sending a reconfiguration message from the first radio access node to the UE, the reconfiguration message including identification information corresponding to the target radio access node and at least a portion of the handover enable data to enable the UE to perform two or more handover operations in response to the reconfiguration message.

[0013] In yet another illustrative embodiment, from the perspective of a network node, a method includes: receiving a request at a network node of a communication network from a radio access node to which a user equipment is connected; in response to the request, generating handover enable data by the network node, the handover enable data enabling the user equipment to perform two or more handover operations in response to a reconfiguration message received by the user equipment from the radio access node; and sending the handover enable data from the network node to the radio access node.

[0014] In some illustrative embodiments, the handover enable data includes two or more sets of key derived parameters corresponding to two or more handover operations, wherein each set of key derived parameters includes a next hop (NH) parameter and a corresponding next hop chain counter (NCC) parameter. The handover enable data may also include a hopping mode corresponding to the user equipment.

[0015] In some embodiments, the user equipment receives handover enable data in multiple containers, including a non-access stratum (NAS) container and a low-layer triggered mobility (LTM) container.

[0016] Advantageously, the illustrative embodiments provide an enhanced LTM handover procedure that enables the user equipment to perform subsequent handovers without sending a new reconfiguration message (e.g., a Radio Resource Control (RRC) reconfiguration message) from the source radio access node to the user equipment. That is, the user equipment receives key derivation data in an RRC message, enabling the user equipment to derive a new key for subsequent handovers.

[0017] Further illustrative embodiments are provided in the form of a non-transitory computer-readable medium in which executable program code is embodied, which, when executed by a processor, causes the processor to perform the above-described and / or other steps, operations, etc. Further illustrative embodiments include an apparatus having a processor and memory, configured to perform the above-described and / or other steps, operations, etc. Some illustrative embodiments include a system configured to perform the above-described and / or other steps, operations, etc. Furthermore, some illustrative embodiments include an apparatus or system comprising components for performing the above-described and / or other steps, operations, etc.

[0018] These and other features and advantages of the embodiments described herein will become more apparent from the accompanying drawings and the following detailed description. Attached Figure Description

[0019] Figure 1 A communication network environment in which one or more illustrative embodiments can be implemented is shown.

[0020] Figure 2 User equipment and entities that can implement one or more illustrative embodiments are shown.

[0021] Figure 3 The key chain process in a communication network environment is illustrated.

[0022] Figure 4 The handover process in a communication network environment is illustrated.

[0023] Figure 5 An enhanced handover process in a communication network environment according to an illustrative embodiment is shown.

[0024] Figure 6 A table showing use cases of an enhanced handover process in a communication network environment according to an illustrative embodiment. Detailed Implementation

[0025] This document will illustrate embodiments in conjunction with example communication systems and related techniques for security management in communication systems. However, it should be understood that the scope of the claims is not limited to the specific types of communication systems and / or processes disclosed. Embodiments can be implemented in a wide variety of other types of communication systems using alternative processes and operations. For example, although illustrated in the context of a wireless cellular system utilizing 3GPP (3rd Generation Partnership Project) system elements such as 3GPP Next Generation System (5G), the disclosed embodiments are directly applicable to a wide variety of other types of communication systems, such as 6G communication systems.

[0026] According to illustrative embodiments implemented in a 5G communication system environment, one or more 3GPP Technical Specifications (TS) and Technical Reports (TRs) (e.g., 3GPP TS 23.501, TS 23.502, and TS 33.501 mentioned above) can provide further explanation of network elements / functions and / or operations that can interact with parts of the solutions of this invention. Other 3GPP TS / TR documents can provide additional details that will be recognized by those skilled in the art, such as TS 38.401 entitled "Technical Specification Group Radio Access Network; NG-RAN; Architecture Description", TS 38.300 entitled "Technical Specification Group Radio Access Network; NR; General Description of NR and NG-RAN; Phase 2", TS 38.331 entitled "Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) Protocol Specification", and RP-234036 entitled "New WID: NR Mobility Enhancement Phase 4", the disclosures of which are incorporated herein by reference in their entirety. Note that 3GPP TS / TR documents are non-limiting examples of communication network standards (e.g., specifications, procedures, reports, requirements, recommendations, etc.). However, while well-suited for 3GPP standards related to 5G, implementations are not necessarily intended to be limited to any particular standard.

[0027] It should be understood that in some illustrative embodiments, the terms 5G network, etc. (e.g., 5G system, 5G communication system, 5G environment, 5G communication environment, etc.) can be understood to include all or part of the access network and all or part of the core network. However, without loss of generality, the terms 5G network, etc. may occasionally be used interchangeably with the terms 5GC network, etc., as any distinction will be understood by those skilled in the art.

[0028] Before describing the illustrative embodiments, the following will be... Figure 1 and Figure 2 In the context of this, a general description of some of the key components of a 5G network is provided.

[0029] Figure 1 A communication system 100 in which illustrative embodiments are implemented is shown. It should be understood that the elements shown in the communication system 100 are intended to represent some of the main functions provided within the system, such as control plane functions, user plane functions, etc. Therefore, Figure 1 The boxes shown refer to specific elements in a 5G network that provide some of these key functions. However, some or all of the indicated key functions can be implemented using other network elements. Furthermore, it should be understood that... Figure 1 Not all the functions of a 5G network are depicted here. Instead, at least some functions are shown to facilitate explanation of illustrative embodiments. Subsequent figures may depict additional elements / functions (i.e., network entities).

[0030] Therefore, as shown in the figure, the communication system 100 includes a user equipment (UE) 102 communicating with an access point 104 via an air interface 103. It should be understood that the UE 102 can communicate with the 5GC network using one or more other types of access points besides a gNB (e.g., access functions, networks, etc.). By way of example only, the access point 104 can be any 5G access network (gNB), an untrusted non-3GPP access network using non-3GPP interoperability functions (N3IWF), a trusted non-3GPP network using trusted non-3GPP gateway functions (TNGF), or a wired access using wired access gateway functions (W-AGF), or it can correspond to a traditional access point (e.g., an eNB). Furthermore, the access point 104 can be a wireless local area network (WLAN) access point, as will be further explained in the illustrative embodiments described herein.

[0031] UE 102 may be a mobile station, and such a mobile station may include, for example, a mobile phone, a computer, an IoT device, or any other type of communication device. Therefore, the term "user equipment" as used herein is intended to be interpreted broadly to encompass various types of mobile stations, user stations, or more generally, communication devices, including examples such as combinations of data cards inserted into a laptop computer or other devices such as a smartphone. Such communication devices are also intended to encompass devices commonly referred to as access terminals.

[0032] In one illustrative embodiment, UE 102 includes a Universal Integrated Circuit Card (UICC) portion and a Mobile Equipment (ME) portion. The UICC is the user-related portion of the UE and includes at least one Universal Subscriber Identity Module (USIM) and appropriate application software. The USIM securely stores a persistent subscription identifier and its associated key, which is used to uniquely identify and authenticate the subscriber to the access network. The ME is the user-independent portion of the UE and includes Terminal Equipment (TE) functionality and various Mobile Terminal (MT) functions. Alternative illustrative embodiments may not use UICC-based authentication, such as a Non-Public (NPN) network.

[0033] Note that in one example, the Permanent Subscription Identifier (IMSI) is a unique International Mobile Subscriber Identity (IMSI) for the UE. In one embodiment, the IMSI is a fixed 15-bit length and consists of a 3-bit Mobile Country Code (MCC), a 3-bit Mobile Network Code (MNC), and a 9-bit Mobile Station Identifier (MSIN). In 5G communication systems, the IMSI is referred to as the Subscriber Permanent Identifier (SUPI). When the IMSI is used as the SUPI, the MSIN provides the subscriber identity. Therefore, typically only the MSIN portion of the IMSI needs to be encrypted. The MNC and MCC portions of the IMSI provide routing information used by the serving network to route to the correct home network. When the MSIN of the SUPI is encrypted, it is called the Subscriber Hidden Identifier (SUCI). Another example of the SUPI uses the Network Access Identifier (NAI). NAIs are commonly used in IoT communications.

[0034] Access point 104 is illustratively part of the radio access network or RAN of communication system 100. Such a radio access network may include, for example, a 5G system with multiple base stations. More generally, components of the radio access network may be considered as “radio access entities”.

[0035] Furthermore, in this illustrative embodiment, access point 104 is operatively coupled to access and mobility management function (AMF) 106. In a 5G network, AMF 106 also supports mobility management (MM) and security anchor (SEAF) functions, among others.

[0036] In this illustrative embodiment, AMF 106 is operatively coupled to other network functions 108 (e.g., using their services). Other network functions 108 may include network functions that can act as service producers (NFp) and / or service consumers (NFc). Note that any network function can be a service producer of one service and a service consumer of another. Furthermore, when the service provided includes data, the data-providing NFp is referred to as a data producer, and the data-requesting NFc is referred to as a data consumer. A data producer can also be an NF that generates data by modifying or otherwise processing data produced by another NF. Note that more generally, an NF can be considered a "network entity," thereby a network entity that consumes one or more of the data and services can be considered a "consumer network entity," and a network entity that generates one or more of the data and services can be considered a "producer network entity."

[0037] Note that UEs such as UE 102 typically subscribe to a network known as the Home Public Land Mobile Network (HPLMN), where some or all of functions 106 and 108 reside. Alternatively, a UE (e.g., UE 102) may receive services from an NPN where these functions can reside. The HPLMN is also known as the Home Environment (HE). If a UE is roaming (not in an HPLMMN), it typically connects to a Visited Public Land Mobile Network (VPLMN) (also known as the Visited Network), and the network currently serving the UE is also known as the Serving Network. In roaming situations, some of functions 106 and 108 may reside in a VPLMN, in which case the functions in the VPLMN communicate with the functions in the HPLMMN as needed. However, in non-roaming scenarios, access and mobility management function 106 and other network functions 108 reside in the same communication network (i.e., the HPLMMN). Unless otherwise stated, the embodiments described herein are not necessarily limited to which functions reside in which PLMN (i.e., the HPLMMN or the VPLMN).

[0038] Access point 104 is also operatively coupled (via one or more of functions 106 and / or 108) to session management function (SMF) 110, which is operatively coupled to user plane function (UPF) 112. UPF 112 is operatively coupled to a packet data network, such as the Internet 114. Note that the thicker solid line in this figure represents the user plane (UP) of the communication network, compared to the thinner solid line representing the control plane (CP). It should be understood that... Figure 1The Internet 114 in the diagram may additionally or alternatively represent other network infrastructure, including but not limited to cloud computing infrastructure and / or edge computing infrastructure. Other typical operations and functions of such network elements are not described herein, as they are not the focus of this illustrative embodiment and can be found in appropriate 3GPP 5G documentation. Note that the functions shown in 106, 108, 110, and 112 are examples of network functions (NFs).

[0039] It should be understood that this particular arrangement of system elements is merely an example, and in other embodiments, other types and arrangements of additional or alternative elements may be used to implement the communication system. For example, in other embodiments, the communication system 100 may include other elements / functions not explicitly shown herein.

[0040] therefore, Figure 1 The arrangement shown is merely one example configuration for a wireless cellular system, and many alternative configurations of system components can be used. For example, although in Figure 1 The embodiments shown depict only a single element / function, but this is merely for the sake of simplicity and clarity. The given alternative embodiments may, of course, include a greater number of such system elements, as well as additional or alternative elements of the type typically associated with conventional system implementations.

[0041] It should also be noted that, although Figure 1 System components are shown as single functional blocks, but the various subnetworks that make up a 5G network are divided into so-called network slices. A network slice (network partition) is a logical network that provides specific network capabilities and characteristics to support a corresponding service type, optionally utilizing Network Function Virtualization (NFV) over a common physical infrastructure. Using NFV, network slices are instantiated as needed for a given service (e.g., eMBB service, large-scale IoT service, and mission-critical IoT service). Therefore, a network slice or function is instantiated when an instance of it is created. In some embodiments, this involves installing or otherwise running the network slice or function on one or more host devices in the underlying physical infrastructure. UE 102 is configured to access one or more of these services via access point 104.

[0042] Figure 2 This is a block diagram illustrating the computational architecture of various participants in a method according to an illustrative embodiment. More specifically, system 200 is shown as including user equipment (UE) 202 and multiple entities 204-1, ..., 204-N. For example, in the illustrative embodiment and back to Figure 1UE 202 may represent UE 102, while entities 204-1, ..., 204-N may represent functions 106 and 108 (i.e., network entities, such as but not limited to AMF) and access point 104 (i.e., radio access entities, such as but not limited to RAN nodes or gNBs). It should be understood that UE 202 and entities 204-1, ..., 204-N are configured to interact to provide security management and other technologies described herein.

[0043] User equipment 202 includes a processor 212 coupled to memory 216 and interface circuitry 210. The processor 212 of user equipment 202 includes a security management processing module 214, which may be implemented at least partially as software executed by the processor. The security management processing module 214 performs security management as described in conjunction with the following figures and otherwise herein. The memory 216 of user equipment 202 includes a security management storage module 218, which stores data generated or otherwise used during security management operations.

[0044] Each of the entities (individually or collectively referred to herein as 204) includes a processor 222 (222-1, ..., 222-N) coupled to memories 226 (226-1, ..., 226-N) and interface circuitry 220 (220-1, ..., 220-N). Each processor 222 of each entity 204 includes a security management processing module 224 (224-1, ..., 224-N) that can be implemented at least partially in the form of software executed by the processor 222. The security management processing module 224 performs security management operations as described in conjunction with the following figures and other methods herein. Each memory 226 of each entity 204 includes a security management storage module 228 (228-1, ..., 228-N) that stores data generated or otherwise used during security management operations.

[0045] Processors 212 and 222 may include, for example, microprocessors, such as central processing units (CPUs), application-specific integrated circuits (ASICs), digital signal processors (DSPs), or other types of processing devices, as well as portions or combinations of these elements.

[0046] Memory 216 and 226 may be used to store one or more software programs executed by the respective processors 212 and 222 to implement at least a portion of the functions described herein. For example, the software code executed by processors 212 and 222 may be used to directly implement security management operations and other functions as described in conjunction with the following figures and otherwise described herein.

[0047] Therefore, one of the memories 216 and 226 can be considered as an example of what is more generally referred to herein as a computer program product, or more generally as a computer or processor-readable (non-transitory or storage) medium in which executable program code is embodied. Other examples of computer or processor-readable media may include any combination of magnetic disks or other types of magnetic or optical media. Illustrative embodiments may include articles of manufacture containing such computer program products or other computer or processor-readable media.

[0048] Furthermore, memories 216 and 226 may more specifically include, for example, electronic random access memory (RAM), such as static RAM (SRAM), dynamic RAM (DRAM), or other types of volatile or non-volatile electronic memory. The latter may include, for example, non-volatile memory, such as flash memory, magnetic RAM (MRAM), phase-change RAM (PC-RAM), or ferroelectric RAM (FRAM). The term “memory” as used herein is intended to be interpreted broadly and may additionally or alternatively encompass, for example, read-only memory (ROM), disk-based memory, or other types of storage devices, as well as portions or combinations thereof.

[0049] Interface circuits 210 and 220 illustratively include transceivers or other communication hardware or firmware that allow associated system elements to communicate with each other in the manner described herein.

[0050] from Figure 2 As is evident here, user equipment 202 and multiple entities 204 are configured to communicate with each other as security management participants via their respective interface circuits 210 and 220. This communication involves each participant sending data to one or more other participants and / or receiving data from one or more other participants. As used herein, the term "data" is intended to be interpreted broadly to encompass any type of information that may be sent between participants, including but not limited to identity data, key pairs, key indicators, tokens, secrets, security management messages, registration request / response messages and data, request / response messages, authorization and / or authentication request / response messages and data, metadata, control data, audio, video, multimedia, consent data, other messages, etc.

[0051] It should be understood that Figure 2 The specific arrangement of components shown is merely an example, and many alternative configurations can be used in other embodiments. For example, any given network element / function and / or access point can be configured to incorporate additional or alternative components and support other communication protocols.

[0052] Other system components, such as access point 104, SMF 110, and UPF 112, can each be configured to include components such as processors, memory, and network interfaces. Furthermore, entities such as third-party applications and network operators can participate in the methods described herein via computing devices configured to include components such as processors, memory, and network interfaces. These components and devices do not need to be implemented on separate, independent processing platforms, but can, for example, represent different functional portions of a single, common processing platform.

[0053] More generally, Figure 2 This can be considered as representing a processing device configured to provide corresponding security management functions and operatively coupled to each other in a communication system. By way of example only, all or part of each of the UE 202 and the plurality of entities 204 (e.g., processor and memory) can be considered as examples of components for performing one or more operations, one or more steps, one or more functions, one or more processes, etc., as described herein.

[0054] As stated above, 3GPP TS 23.501 defines the 5GC network architecture as service-based, such as Service-Based Architecture (SBA). This document recognizes that when deploying different NFs, there may be many situations where an NF may need to interact with entities outside the SBA-based 5GC network (e.g., including corresponding PLMNs, such as HPLMNs and VPLMNs). Therefore, as used herein, the term "internal" illustratively refers to operations and / or communications within the SBA-based 5GC network (e.g., SBA-based interfaces), and the term "external" illustratively refers to operations and / or communications outside the SBA-based 5GC network (non-SBA interfaces).

[0055] Low-layer triggered mobility (LTM) is a new 5G handover process with shorter service interruption times, in which the gNB receives a measurement report from the UE and, based on the measurement report, changes the UE's serving cell (e.g., from the source cell to the target cell). In existing LTM handover (HO), the gNB prepares one or more candidate cells and provides the candidate cell configuration to the UE via an RRC message. The gNB then triggers the LTM cell handover by selecting one of the candidate configurations as the target configuration for LTM. Candidate cell configurations can only be added, modified, and released by the network via Radio Resource Control (RRC) signaling. As used illustratively herein, a cell refers to a geographical area covered by a frequency (or frequency range) transmitted by a base station in a cellular network.

[0056] It should be recognized that, from a security and / or signaling perspective, it is desirable to achieve an LTM handover process that avoids RRC configuration between cell handovers. However, this approach would require one or more technical solutions for key processing without reconfiguration. Illustrative embodiments provide such technical solutions in the context of enhanced LTM handover processes, as will be described below. Figure 5 This is described illustratively within the context of [the relevant context]. Before illustratively describing the enhanced LTM handover process, [further details will be provided separately]. Figure 3 and Figure 4 Briefly describe the existing keychain and existing LTM switching process in the context of [the relevant context].

[0057] Figure 3 The key chain procedure (procedure 300) in a communication network environment is illustrated. As shown in procedure 300, whenever an initial access stratum (AS) security context needs to be established between the UE and gNB, the AMF and UE derive the key chain. gNB and next-hop parameters (NH). From AMF key K AMF Export K gNB And NH. NH chain counter (NCC) parameters with each K gNB Associated with the NH parameter. Each K gNB It is associated with the NCC corresponding to the NH value used to derive this KgNB.

[0058] As further shown in process 300, during the initial setup, K gNB Directly from K AMF The exported NH value is then considered to be associated with a virtual NH parameter where the NCC value is equal to zero. Furthermore, during initial setup, the exported NH value is associated with an NCC value of 1. At the UE, the NH export associated with NCC=1 can be delayed until the first handover when performing vertical key export. The AMF sends K to the serving gNB. gNBThe determination of the key or [NH, NCC] pair is further described in detail in TS 33.501 above. The AMF does not send the NH value to the gNB during initial connection establishment. The gNB initializes the NCC value to zero upon receiving the Next Generation Application Protocol (NGAP) Initial Context Establishment Request message. Because the AMF does not send the NH value to the gNB during initial connection establishment, the NH value associated with NCC value 1 cannot be used for the next Xn handover or the next intra-gNB handover. For the next Xn handover or the next intra-gNB-CU handover, the application level key is derived. Note that CU refers to the Central Unit, which supports higher layers of the protocol stack, such as SDAP (Serving Data Adaptation Protocol), PDCP (Packet Data Convergence Protocol), and RRC (Radio Resource Control) layers, while DU refers to the Distributed Unit, which supports lower layers of the protocol stack, such as RLC (Radio Link Control), MAC (Media Access Control), and the physical layer. Note that in some examples, intra-gNB handovers occur between cells within the same gNB, while inter-gNB handovers occur between cells in different gNBs.

[0059] One of the rules specified for the AMF in TS 33.501 above states that the AMF always calculates a new [NH, NCC] pair provided to the target gNB. This means that the first [NH, NCC] pair will never be used to derive K. gNB It is only used as the initial value for the NH chain. UE and gNB use K. gNB To protect communication between them. During handover and when transitioning from RRC_INACTIVE state to RRC_CONNECTED state, K will be used between the UE and the target gNB. gNB The basis (called K) NG-RAN ) is from the currently active K gNB Or derived from the NH parameter. If K NG-RAN From the current activity K gNB If it is exported, then this is called horizontal key export, and if K NG-RAN If the NH parameter is derived from the UE, then this derivation is called vertical key derivation. Since the NH parameter can only be calculated by the UE and AMF, the following settings are made: the NH parameter is provided from the AMF to the gNB in ​​a way that enables forward security. During handover with vertical key derivation, NH is in the K of the target gNB. gNB Previously, it was further bound to the target PCI (Physical Cell Identifier) ​​and its frequency ARFCN-DL (Absolute Radio Channel Number for Downlink). During a handover with horizontal key derivation, the currently active K... gNB K in the target gNB gNBPreviously, it was further bound to the target PCI and its frequency ARFCN-DL.

[0060] Therefore, in summary, both horizontal and vertical key exports utilize PCI and DL frequencies. Horizontal key export leverages the previous key. Vertical key export is refreshed using NH. Vertical key generation is used to separate the key space for each RAN node. The NH value is provided to the RAN node by the AMF. The vertical key generated by each RAN node uses the new NH value provided by the AMF. Thus, the security domain is separated from the previous RAN node. In short, for horizontal key export, the input is the current K. gNB (Current active key), PCI and DL frequencies, and the output is K. gNB In vertical key export, the inputs are the new NH value (provided to the serving RAN node by the AMF after path switching), PCI, and DL frequency, and the output is K. gNB .

[0061] Given keychain procedure 300, Figure 4 A typical LTM handover procedure 400 (procedure 400) is illustrated, including steps 1-29 and involving UE 402, gNB1 (source gNB) 404, gNB2 (target gNB) 406, and AMF 408. In this example, it is assumed that the NCC value of UE 402 is "0", and the handover experienced by UE 402 is an intra-gNB handover, therefore the NCC value does not increment after the handover. It is assumed that the key used by UE 402 is K. gNB-A .

[0062] Using the received measurement reports, the RAN node determines whether an inter-gNB handover is appropriate (e.g., the target cell's measurement report indicates the target cell at another gNB). The source gNB (gNB1 404) generates the target key K. gNB K gNB-B And set the current NCC value "0" and the new key K gNB-B It is sent to the target gNB (gNB2 406) along with the handover request.

[0063] The target gNB (gNB2 406) receives the NCC value "0" and embeds it into the target cell configuration. The target cell configuration is sent to the source gNB (gNB1 404) along with the handover request confirmation message. Key K gNB-B The target gNB (gNB2 406) stores the handover command for later use. Then, the source gNB (gNB1 404) forms a handover command encapsulated with the target cell configuration and sends the handover command to UE 402. UE 402 receives and decodes the handover command.

[0064] UE 402 determines that the NCC value remains unchanged at "0". Therefore, UE 402 determines to perform level key generation and uses the current key K. gNB-A And the PCI and DL frequencies of the target gNB (gNB2 406) to generate K gNB-B Since the algorithms on the UE side and the network side are the same, UE 402 and the network independently generate K that matches each other. gNB-B .

[0065] UE 402 uses K gNB-B The message is encoded and sent to gNB2 406. gNB2 406 sends a path switching request to AMF408. AMF408 increments the NCC value of UE 402. AMF408 generates a new NH value and sends the incremented NCC value and the new NH value to gNB2 406. gNB2 406 stores the NH and NCC values ​​but does not use them. At this point, gNB2 406 has become the serving gNB of UE 402.

[0066] After a certain period, UE 402 can send another measurement report. This report can indicate that another target cell in the same gNB has become a strong candidate for handover. gNB2 406 decides to trigger an intra-gNB handover. Due to the incrementing stored NCC value, gNB2 406 determines to generate the vertical key. gNB2 406 uses the NH value, PCI, and DL frequency to generate the K key. gNB-C The gNB2 406 stores this K gNB-C gNB2 406 inserts the incrementing NCC value "1" into the target cell configuration, constructs a handover command, i.e., the HO command, and sends the HO command to UE 402.

[0067] UE 402 decodes the HO command and sees the NCC value increment to "1". UE 402 uses the vertical key generation and the algorithm pre-configured for the UE by AMF 408 to generate a new NH value. Since the same algorithm is used, the NH values ​​generated by UE 402 and AMF 408 are mapped to each other. UE 402 then uses the NH value, PCI, and DL frequency to generate the target key K. gNB-C UE 402 encrypts the message with the newly generated key and then sends the encrypted message to gNB2 406. gNB2 406 uses the stored key... gNB-C To decode the UE 402 message.

[0068] Therefore, as described above in procedure 400, after each cell change, the handover command sent to UE 402 uses the NCC value to indicate the key to be generated. However, in LTM handover scenarios, it is desirable to reuse candidate cell configurations without new RRC reconfiguration messages. With repeated use of the same NCC value, only horizontal key derivation would be possible. Therefore, procedure 400 does not conform to the desired security paradigm because different gNBs require new keys with new NH values.

[0069] For example, such a non-reconfiguration solution will provide processing and overhead savings due to less signaling between components, as well as enhanced security, because less signaling between components will give malicious actors fewer opportunities to try to intercept signals or otherwise attack components in the communication network environment.

[0070] The illustrative embodiments provide the above and other technical solutions by offering an enhancement process in which the source gNB requests the UE's NH hopping pattern or sequence for subsequent LTM handovers, along with new NH values, such as an LTM container with two NCC values, one for the current LTM handover and the other for subsequent handovers. During the preparation phase of the RRC reconfiguration message, both the LTM container and the Non-Access Stratum (NAS) container are passed to the UE. The RRC module passes the NAS container to the NAS module for decryption and integrity verification. After decryption, the NH hopping pattern is passed to the RRC module. The RRC module also retrieves the two NCC values ​​from the LTM container for both the current and subsequent LTM handovers. In some illustrative embodiments, the UE may be provided with a list of NH values ​​and associated NCC values ​​to derive a new key for each subsequent handover. This can be achieved by the source gNB obtaining the list of NH values ​​and associated NCC values ​​from the AMF.

[0071] In a non-limiting example, assume the AMF sends two NCC values ​​and NH values ​​to the source gNB, for example, one key for the serving cell and the next NH value for the candidate cell, to perform vertical key derivation during inter-gNB handover. Therefore, from the UE's perspective, there are several options: (i) update the UE with the new NCC value after each inter-gNB handover; (ii) the UE knows it should perform a vertical key update for each inter-gNB handover; and (iii) the UE does not perform a key update during intra-gNB handover. From the network's perspective, path handover provides two keys, and the source gNB indicates either the vertical key prepared by the second NH value or the NH value itself to all neighboring cells. Furthermore, from the network's perspective, no key update occurs for intra-gNB handover.

[0072] Figure 5An enhanced low-layer triggered mobility (LTM) handover process (e.g., process 500) in a communication network environment according to an illustrative embodiment is shown. As will be shown below, while process 400 fails to do so, process 500 is able to achieve the aforementioned desired security paradigm in an LTM handover scenario.

[0073] Procedure 500 involves UE 502, source gNB 504, target gNB 506, and AMF 508. As shown in the decomposed architecture, source gNB 504 includes source DU (s-DU), source CU for user plane (s-DU-UP), and source CU for control plane (s-DU-CP). Similarly, target gNB 506 in the decomposed architecture includes target DU (t-DU), target CU for user plane (t-DU-UP), and target CU for control plane (t-DU-CP).

[0074] As will be described in further detail in the steps of procedure 500 below, the source gNB 504 sends a path handover request (early path handover request message) for LTM handover to the AMF 508. The AMF 508 prepares two containers, such as a NAS container and an LTM container, and both containers are sent to the source gNB 504. The NAS container includes the NH hopping pattern for UE 502 and is used for subsequent (multiple) LTM handovers. The LTM container contains two sets of NCC and NH values: one NCC for the current LTM handover and the other for the next handover immediately following. The source gNB 504 sends an LTM handover request with the LTM container and the generated security key to the target gNB 506. When a handover is triggered, the source gNB 504 sends both containers to UE 502 in a message. UE 502 obtains the NH hopping pattern from the NAS container, and UE 502 uses this pattern to generate keys in subsequent (multiple) LTM handovers.

[0075] More specifically, such as Figure 5 As shown, process 500 includes a preparation phase comprising steps 1-19, a synchronization phase comprising steps 20-22, and an execution phase comprising steps 23-39.

[0076] The UE context of UE 502 within the source gNB 504 contains information about roaming and access restrictions, which is provided during connection establishment or during the final advance timing (TA) update. During the preparation phase of procedure 500, the source gNB 504 configures the UE measurement procedure, and UE 502 reports according to the measurement configuration. The source gNB 504 determines whether to hand over UE 502 based on the measurement reports and RRM (Radio Resource Management) information. The source gNB 504 performs LTM preparation for candidate cells.

[0077] The source gNB 504 sends a path handover request (early path handover request message) for LTM handover to the AMF 508. The AMF 508 prepares two containers. Alternatively, the AMF 508 may receive an initial UE message or a separate message for LTM security key acquisition.

[0078] The NAS container contains the NH hopping pattern or sequence for UE 502, and this is used for subsequent LTM handover. The NH hopping pattern uses the NAS encryption key K of the existing UE context. NASenc Encryption is performed, and K is used. NASint The key is used for NAS integrity protection. This container is designed for use with source gNB 504.

[0079] The LTM container contains two sets of NCC and NH values ​​and is sent from AMF 508 to source gNB 504. One NH value is used for the current LTM handover, and the other is used for the next handover immediately following. As a non-limiting example, in the LTM container, AMF 508 sends NCC 0 and NCC 1 (two sets of NCC values) and the NH value to source gNB 504. After two LTM handovers, the UE does not need any NCC or NH values ​​because the pattern for incrementing NCC to 3 has already been transmitted in the NAS container. Therefore, source gNB 504 will obtain this data from AMF 508 during the third handover, while UE 502 already knows the pattern.

[0080] Source gNB 504 sends an LTM switch request for an LTM container with two NCC values ​​and a generated K to target gNB 506. NG-RAN Admission control can be performed by the target gNB 506. Slice-aware admission control is performed in response to slice information being sent to the target gNB 506.

[0081] After the bearer context is established, an LTM handover response carrying the LTM container is sent to the source gNB 504.

[0082] The source gNB 504 triggers the handover by sending a message to the UE 502 containing the information required to access the target cell, namely, at least the target cell ID, the new C-RNTI (Cell Radio Network Temporary Identifier), the target gNB security algorithm identifier for the selected security algorithm, and two containers (i.e., the LTM container and the encrypted NAS container).

[0083] The network can indicate an NCC value or a separate identifier to indicate whether the UE 502 should perform horizontal or vertical key generation.

[0084] The RRC module of UE 502 sends a NAS container to the NAS module of UE 502, and the NAS key is used to perform an integrity check on the received container content. After verification, the NAS content is decrypted. The NAS module sends an NH transition mode to the RRC module for subsequent LTM handover.

[0085] After each path handover update is completed in the target cell, each subsequent key (K) will be calculated using the NH value received from AMF 508. gNB This instruction is given to all candidate gNBs.

[0086] During the execution phase, the previously acquired NH values ​​are used in subsequent switching processes.

[0087] More specifically, consistent with the above illustrative description of the enhanced LTM process, Figure 5 The process involves 500 steps as follows.

[0088] Step 1: Begin the preparation phase.

[0089] Step 2: UE 502 sends an L3 measurement report to the s-DU of the source gNB 504 according to the measurement configuration.

[0090] Step 3: The s-DU performs a UL RRC message transmission to send an L3 measurement report to the s-CU-CP of the source gNB 504.

[0091] Step 4: The source gNB 504 performs LTM preparation for the candidate cell at s-CU-CP.

[0092] Steps 5a, 5b, 5c, and 5d: A path handover request (an “early” path handover request message introduced for the LTM HO use case) is sent from the s-CU-CP of the source gNB 504 to the AMF 508 for LTM handover. The AMF 508 then prepares two containers. The NAS container contains the NH hopping pattern or sequence for UE 502 (and for subsequent LTM handover). The hopping pattern is encrypted using the existing UE 502 context NAS key. Therefore, the AMF 508 sends a path handover response containing the LTM container and the encrypted NAS container back to the s-CU-CP of the source gNB 504. The s-CU-CP of the source gNB 504 then sends a path handover response with the LTM container and the generated K to the t-CU-CP of the target gNB 506. NG-RAN LTM switching request.

[0093] Step 6: Admission control is performed by target gNB 506 (target gNB's target CU-CP).

[0094] Steps 7 and 8: After completing the bearer context establishment request / response between t-CU-UP and t-CU-CP of the target gNB 506, establish the F1 UE 502 context.

[0095] Step 9: Then send an LTM handover response with data forwarding information and an LTM container from the t-CU-CP of the target gNB 506 to the s-CU-CP of the source gNB 504.

[0096] Step 10: Perform the F1 UE 502 context modification procedure between s-CU-CP and s-DU of the source gNB 504.

[0097] Step 11: Use data forwarding information to complete the bearer context modification request / response process between s-CU-UP and s-CU-CP in the source gNB 504.

[0098] Step 12: At source gNB 504, generate RRC configuration based on measurement configuration and prepared cell configuration.

[0099] Step 13: DL RRC message transmission with RRC message from s-CU-CP in source gNB 504 to s-DU.

[0100] Steps 14a and 14b: The s-DU sends an RRC reconfiguration message carrying the LTM container and the encrypted NAS container to UE 502. In response, UE 502's RRC module obtains the NH hopping mode from the NAS container after decryption.

[0101] Steps 15 and 16: RRC reconfiguration is complete. UE 502 sends an acknowledgment to the s-DU of the source gNB 504. The s-DU then sends a UL RRC message to the s-CU-CP in the source gNB 504.

[0102] Step 17: Send an early SN state transition from the s-CU-CP of the source gNB 504 to the t-CU-CP of the target gNB 506.

[0103] Step 18: Exchange bearer context modification requests / responses between t-CU-UP and t-CU-CP in the target gNB 506.

[0104] Step 19: Forward early data from AMF 508 to the s-CU-UP of the source gNB 504, and then to the t-CU-UP of the destination gNB 506.

[0105] Step 20: The synchronization phase of LTM switching begins.

[0106] Step 21: Send a PDCCH (Physical Downlink Control Channel) command from the s-DU of source gNB 504 to UE 502.

[0107] Step 22: UE 502 and target gNB 506 use the RACH (Random Access Channel) mechanism to obtain the target cell TA in their t-CU-UP.

[0108] Step 23: The execution phase of LTM switching begins.

[0109] Step 24: Send an L3 measurement report from UE 502 to the s-DU of source gNB 504.

[0110] Steps 25, 26, and 27: The s-DU of the source gNB 504 sends a MAC control element (MAC CE) cell change trigger to the UE 502 with the TA of the target cell. The s-DU also sends a notification for the serving cell change to the s-CU-CP in the source gNB 504. The s-CU-CP then sends a modification request / response to the s-CU-UP in the source gNB 504.

[0111] Step 28: RRC reconfiguration is complete, and an acknowledgment is sent from UE 502 to the t-DU of the target gNB 506.

[0112] Steps 29, 30, and 31: A UL RRC message and access notification are transmitted from the t-DU in the target gNB 506 to the t-CU-CP. In response, the LTM handover is completed, and an acknowledgment is sent from the t-CU-CP of the target gNB 506 to the s-CU-CP of the source gNB 504.

[0113] Step 32: Exchange bearer context modification requests / responses between the t-DU and t-CU-CP of the target gNB 506.

[0114] Step 33: Initiate a path handover process between the t-CU-CP of AMF 508 and the target gNB 506, and use the NH value for subsequent handover.

[0115] Step 34: Send the end-of-time packet from AMF 508 to the s-CU-UP of the source gNB 504, and then forward it to the t-CU-UP of the destination gNB 506.

[0116] Steps 35 and 36: Send a new path from AMF 508 to t-CU-UP of target gNB 506, and send UE 502 context release from t-CU-CP to t-DU in target gNB 506.

[0117] Steps 37 and 38: The bearer context release command is sent from the t-DU of the target gNB 506 to the s-CU-UP of the source gNB 504, and the F1 UE 502 context release process is completed between the s-DU of the source gNB 504 and the t-DU of the target gNB 506.

[0118] Step 39: Bearer context release is complete, and an acknowledgment is sent from the s-CU-UP of the source gNB 504 to the t-DU of the target gNB 506.

[0119] Figure 6 Table 600 shows a non-restricted use case of process 500 with one source gNB (gNB1) and two candidate / target gNBs (gNB2 and gNB3).

[0120] It should be understood that the specific processing operations and other system functions described in conjunction with the figures herein are presented by way of illustrative example only and should not be construed as limiting the scope of this disclosure in any way. Alternative embodiments may use other types of processing operations and messaging protocols. For example, in other embodiments, the order of steps may vary, or certain steps may be performed at least partially simultaneously rather than sequentially. Furthermore, one or more steps may be repeated periodically, or multiple instances of the method may be performed in parallel with each other.

[0121] It should be emphasized again that the various embodiments described herein are presented by way of illustrative example only and should not be construed as limiting the scope of the claims. For example, alternative embodiments may utilize different communication system configurations, user equipment configurations, base station configurations, authorization processes, messaging protocols, and message formats than those described above in the context of the illustrative embodiments. These and many other alternative embodiments within the scope of the appended claims will be apparent to those skilled in the art.

Claims

1. An apparatus comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: The device receives a reconfiguration message from a radio access node connected to it. The reconfiguration message includes handover enable data, which enables the device to perform two or more handover operations in response to the reconfiguration message.

2. The apparatus of claim 1, wherein the switching enable data includes two or more sets of key derived parameters corresponding to the two or more switching operations, respectively.

3. The apparatus of claim 2, wherein each set of key-derived parameters includes a next-hop (NH) parameter and a corresponding next-hop chain counter (NCC) parameter.

4. The apparatus of claim 2, wherein the switching enable data further includes a transition mode corresponding to the apparatus.

5. The apparatus of claim 1, wherein the switching enable data is received by the apparatus from the radio access node in a plurality of containers.

6. The apparatus of claim 5, wherein the plurality of containers includes non-access stratum (NAS) containers and low-level triggered mobility (LTM) containers.

7. The apparatus of claim 1, wherein the two or more switching operations are low-level triggered mobility (LTM) switching operations.

8. A method comprising: At the user equipment, a reconfiguration message is received from a radio access node connected to the user equipment. The reconfiguration message includes handover enable data, which enables the user equipment to perform two or more handover operations in response to the reconfiguration message. as well as The user equipment uses the handover enable data to perform the two or more handover operations.

9. An apparatus comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: In response to receiving measurement data from a user equipment in a subscribed communication network, a first request is sent to a network node in the communication network; Receive a first response from the network node, the first response including handover enable data, the handover enable data being used to enable the user equipment to perform two or more handover operations; Send a second request to the candidate radio access node, the second request including at least a portion of the handover enable data; Receive a second response from the candidate radio access node; Based on the second response, the candidate radio access node is identified as the target radio access node; as well as A reconfiguration message is sent to the user equipment, the reconfiguration message including at least a portion of the identification information corresponding to the target radio access node and the handover enable data, so that the user equipment can perform two or more handover operations in response to the reconfiguration message.

10. The apparatus of claim 9, wherein the switching enable data includes two or more sets of key derived parameters corresponding to the two or more switching operations, respectively.

11. The apparatus of claim 10, wherein each set of key-derived parameters includes a next-hop (NH) parameter and a corresponding next-hop chain counter (NCC) parameter.

12. The apparatus of claim 10, wherein the switching enable data further includes a switching mode corresponding to the user equipment.

13. The apparatus of claim 9, wherein the switching enable data is sent by the apparatus as a plurality of containers.

14. The apparatus of claim 13, wherein the plurality of containers includes non-access stratum (NAS) containers and low-level triggered mobility (LTM) containers.

15. The apparatus of claim 9, wherein the two or more switching operations are low-level triggered mobility (LTM) switching operations.

16. The apparatus of claim 9, wherein the handover operation in response to the first request is performed between the user equipment and the target radio access node.

17. A method comprising: In response to receiving measurement data from a user equipment in a subscribed communication network, a first request is sent from the first radio access node to a network node in the communication network; At the first radio access node, a first response is received from the network node, the first response including handover enable data, the handover enable data being used to enable the user equipment to perform two or more handover operations; A second request is sent from the first radio access node to the candidate radio access node, the second request including at least a portion of the handover enable data; Receive a second response from the candidate radio access node at the first radio access node; The first radio access node identifies the candidate radio access node as the target radio access node based on the second response; as well as A reconfiguration message is sent from the first radio access node to the user equipment, the reconfiguration message including identification information corresponding to the target radio access node and at least a portion of the handover enable data, so that the user equipment can perform two or more handover operations in response to the reconfiguration message.

18. An apparatus comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: Receive requests from the radio access node to which the user equipment is connected; In response to the request, handover enable data is generated, which enables the user equipment to perform two or more handover operations in response to a reconfiguration message received by the user equipment from the radio access node. as well as The handover enable data is sent to the radio access node.

19. The apparatus of claim 18, wherein the handover enable data includes two or more sets of key-derived parameters corresponding to the two or more handover operations, and each set of key-derived parameters includes a next-hop (NH) parameter and a corresponding next-hop chain counter (NCC) parameter, and wherein the handover enable data further includes a hopping mode corresponding to the user equipment.

20. A method comprising: Receive requests at the network node of the communication network from the radio access node to which the user equipment is connected; In response to the request, the network node generates handover enable data, which enables the user equipment to perform two or more handover operations in response to a reconfiguration message received by the user equipment from the radio access node. as well as The handover enable data is sent from the network node to the radio access node.