Dual Connectivity Handover SeNB Release and Security Key Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current DC and SCE technologies face challenges in SeNB release and addition during handover, leading to issues such as resource depletion, security vulnerabilities, and increased signaling burden, with undefined security key management.
Innovation Solution
A system and method for dual connectivity that includes a source MeNB and SeNB, where the source MeNB sends information about itself and the SeNB in a Handover Request to a target MeNB, and the target MeNB acknowledges and configures a new SeNB, managing security keys and bearers to ensure seamless handover.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If SeNB Release happens too early during handover, then handover procedure can proceed, but MeNB must reconfigure SeNB which burdens control plane signaling and increases counter values
Solution Approach 1:
The patent applies preliminary action by performing SeNB Release before the handover procedure is complete. The source MeNB sends a SeNB Release Request to the SeNB during the handover process, allowing the SeNB to be released and resources prepared in advance. This prevents the need for reconfiguration after handover failure and reduces control plane signaling burden.
2Stability of the object's composition
If SeNB Release happens too late during handover, then existing SeNB configuration remains valid, but packet data transmission continues via old SeNB causing resource depletion and security vulnerabilities
Solution Approach 1:
The patent performs SeNB Release in advance during the handover procedure rather than waiting until handover completion. The source MeNB initiates SeNB Release by sending a SeNB Release Request to the SeNB, ensuring that the SeNB is properly released and resources are freed before the handover is finalized. This prevents packet data transmission via the old SeNB and eliminates security vulnerabilities.
Solution Approach 2:
The patent implements feedback mechanisms where the source MeNB receives acknowledgment from the target MeNB about the handover status, and based on this feedback, the source MeNB appropriately manages the SeNB release timing. The system monitors handover progress and adjusts SeNB release accordingly to maintain both stability and security.
3Adaptability or versatility
If M'eNB configures new SeNB by performing SeNB Addition procedure, then new SeNB can be established, but this burdens MeNB and increases control plane signaling
Solution Approach 1:
The patent applies preliminary action by having the source MeNB release the SeNB during the handover procedure rather than waiting for the target MeNB to perform a full SeNB Addition procedure after handover. This preliminary release action reduces the need for complex reconfiguration and decreases the processing burden on the MeNB.
4Duration of action of stationary object
If bearer between MeNB and UE is kept after handover, then connection is maintained, but resources are depleted and security vulnerabilities arise
Solution Approach 1:
The patent performs bearer release in advance by initiating SeNB Release during the handover procedure. The source MeNB sends a SeNB Release Request to the SeNB, which triggers the release of bearers associated with that SeNB. This ensures that bearers are properly terminated before handover completion, preventing resource depletion and security vulnerabilities while maintaining appropriate connection duration.
Data Source
AI summary
A UE (10) provides information on potential S′eNB(s). The information is forwarded from an MeNB (20_1) to an M′eNB (20_2) such that the M′eNB (20_2) can determine, before the handover happens, whether the M′eNB (20_2) will configure a new SeNB (S′eNB) and which S′eNB the M′eNB (20_2) will configure. In one of options, the MeNB (20_1) derives a key S′-KeNB for communication protection between the UE (10) and the S′eNB (30_1), and send the S′-KeNB to the M′eNB (20_2). In another option, the M′eNB (20_2) derives the S′-KeNB from a key KeNB* received from the MeNB (20_1). The M′eNB (20_2) sends the S′-KeNB to the S′eNB (30_1). Moreover, there are also provided several variations to perform SeNB Release, SeNB Addition, Bearer Modification and the like, in which the order and/or timing thereof can be different during the handover procedure.


