A Restart Recovery Method for Evolved Packet Core

Abstract

The present invention provides a method for restarting and restoring the evolved packet core, which is characterized in that: firstly, a database is created, and the database is used to store the terminal context, the terminal context includes but not limited to the EPS mobility management context and the EPS session management context, and the evolved packet core Have read and write permissions to the database; each time the evolution packet core is restarted and initialized, read the relevant entries of the database into the context of the corresponding terminal, and at the same time, in the evolution packet core, all the relevant entries read from the database The GUTI is a set of GUTIs that have been legally used before the restart, and the GUTIs in the set of GUTIs that have been used legally before the restart are not allocated to the subsequent new access terminals. In this way, after the evolved packet core fails and restarts, terminals that have been connected normally before the restart do not need to perform IMSI query, authentication and security procedures again, which reduces the terminal access delay and the possibility of IMSI leakage.

Description

technical field [0001] The invention belongs to the communication field, and relates to a method for restarting and recovering an evolved packet core. Background technique [0002] In the Evolved Packet System (EPS), after the Evolved Packet Core (EPC) is restarted due to a failure, if there is no corresponding recovery measure, the terminal (User Equipment, UE) that has been connected normally before the restart When the EPC initiates access for the first time after restarting, since the Mobility Management Entity (MME) in the EPC no longer has the context of the UE, it needs to initiate an authentication and security process for the UE to complete both identity authentication and security context Negotiation, the UE and the EPC need at least four non-access stratum (Non-Access Stratum, NAS) signaling interactions (Authentication Request&Authentication Response, Security Mode Command&Security Mode Complete), which virtually increases the UE's access delay. Especially at th...

AI Technical Summary

Problems solved by technology

[0002] In the Evolved Packet System (EPS), after the Evolved Packet Core (EPC) is restarted due to a failure, if there is no corresponding recovery measure, the terminal (User Equipment, UE) that has been connected normally before the restart When the EPC initiates access for the first time after restarting, since the Mobility Management Entity (MME) in the EPC no longer has the context of the UE, it needs to initiate an authentication and security process for the UE to complete both identity authentication and security context Negotiation, UE and EPC need at least four non-access stratum (Non-Access Stratum, NAS) signaling interaction (Authentication Request&Authentication Response, Security Mode Command&Security Mode Complete), which virtually increases the UE's access delay

Especially at this time, when the identity carried by the UE to initiate access is not an International Mobile Subscriber Identification Number (IMSI), the EPC also needs to initiate an IMSI query process, which not only increases the access delay of the UE, And it increases the possibility of IMSI leakage

After restarting at the same time, the EPC may reassign the Globally Unique Temporary UE Identity (GUTI) assigned before the restart to other UEs, causing GUTI confusion

Images