CN107018507A - A kind of evolution block core restarts restoration methods - Google Patents
A kind of evolution block core restarts restoration methods Download PDFInfo
- Publication number
- CN107018507A CN107018507A CN201710175745.5A CN201710175745A CN107018507A CN 107018507 A CN107018507 A CN 107018507A CN 201710175745 A CN201710175745 A CN 201710175745A CN 107018507 A CN107018507 A CN 107018507A
- Authority
- CN
- China
- Prior art keywords
- terminal
- block core
- evolution block
- evolution
- contexts
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/024—Standardisation; Integration using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
- H04L41/0661—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
Abstract
The present invention provides a kind of evolution block core and restarts restoration methods, it is characterised in that：A database is created first, and the database is used to store terminal contexts, and the terminal contexts include but is not limited to EPS Mobility Management context and EPS session management contexts, and evolution block core possesses access limit to the database；When each evolution block core restarts initialization, the database relevant entries are read into the context of counterpart terminal, simultaneously in evolution block core, all GUTI read from the database relevant entries are the legal GUTI set used before restarting, it is described restart before in the legal GUTI set used GUTI be not assigned to the terminal that newly accesses below.So evolution block core breaks down restart after, the terminal to having carried out before restarting normally accessing reduces the access delay of terminal without do IMSI inquiries, authentication and safe procedures again, reduces IMSI leakage possibilities.
Description
Technical field
The invention belongs to the communications field, it is related to a kind of evolution block core and restarts restoration methods.
Background technology
In evolved packet system (Evolved Packet System, EPS), evolution block core (Evolved
Packet Core, EPC) after barrier is restarted for some reason, if without corresponding recovery measure, having carried out what is normally accessed before restarting
Terminal (User Equipment, UE) when initiating access first after the EPC is restarted, due to mobile management entity in EPC
(Mobility Management Entity, MME) context without the UE, it is therefore desirable to which authentication and safety are initiated to the UE
Flow, completes both sides' authentication and the negotiation of safe context, and UE and EPC at least needs four Non-Access Stratum (Non-
Access Stratum, NAS) Signalling exchange (Authentication Request＆Authentication Response,
Security Mode Command＆Security Mode Complete), virtually add UE access delay.Particularly
When now, UE initiates the non-international mobile subscriber identity of identity (the International Mobile that access is carried
Subscriber Identification Number, IMSI) in the case of, EPC also needs to initiate IMSI querying flows, and this is not only
UE access delay is added, and increases IMSI leakage possibilities.Restart simultaneously after, EPC has been distributed before may restarting
The unique ephemeral terminations mark (Globally Unique Temporary UE Identity, GUTI) in the whole world gone out is divided again
Other UE of dispensing, so as to cause GUTI confusion.
The content of the invention
For problem of the prior art, restoration methods are restarted the invention provides a kind of evolution block core.
To reach above-mentioned purpose, the technical proposal of the invention is realized in this way：
A kind of evolution block core restarts restoration methods, and a database is created first, and the database is used to store terminal
Context, the terminal contexts include but is not limited to EPS Mobility Management context and EPS session management contexts, evolution point
Group core possesses access limit to the database；When each evolution block core restarts initialization, the database is read related
List item is into the context of counterpart terminal, while in evolution block core, from the database relevant entries read it is all
GUTI be restart before it is legal use GUTI set, it is described restart before it is legal use GUTI set in GUTI be not assigned to
The terminal newly accessed below.
Moreover, after terminal is successfully attached to the evolution block core for the first time, will be whole in the evolution block core
End contextual information record is inserted into database table entry, it is ensured that evolution block core with database terminal contexts it is same
Step.
Moreover, when any renewal occur for terminal contexts, terminal contexts in evolution block core being updated and arrive data
In the list item of storehouse, it is ensured that the evolution block core with the database terminal contexts it is synchronous.
Moreover, when cancellation occurs for terminal, by the corresponding record of the terminal contexts of the terminal from corresponding database table entry
It is middle delete, it is ensured that evolution block core with database terminal contexts it is synchronous.
Moreover, after the evolution block core is restarted for some reason, when certain terminal initiates attach request and carries NAS integrality
When protecting security header, the identity carried by the terminal is searched whether in the terminal contexts of the evolution block core
There is the terminal, if can find and Non-Access Stratum integrity protection check success, just ensure the peace of the terminal
Full context and the evolution block core are consistent, and terminal need not do authentication security flow.
Moreover, after the evolution block core is restarted for some reason, when certain terminal initiates attach request and carries NAS integrality
When protecting security header, the identity carried by the terminal is searched whether in the terminal contexts of the evolution block core
There is the terminal, if can find and Non-Access Stratum integrity protection check success, just ensure the peace of the terminal
Full context and the evolution block core are consistent, and terminal need not do authentication security flow.
Moreover, after the evolution block core is restarted for some reason, when certain terminal launch position, which updates, asks, passing through the terminal
The identity of carrying searches whether there is the terminal in the terminal contexts of the evolution block core, if can find
And NAS integrity protection check is successful, the safe context and the evolution block core side for just ensuring the end side are
Consistent, the terminal need not do authentication security flow.
Moreover, after the evolution block core is restarted for some reason, when certain terminal initiates service request, being taken by the terminal
The identity service Temporary Mobile Subscriber Identity of band searches whether exist in the terminal contexts of the evolution block core
The terminal, if can find and Non-Access Stratum integrity protection check's success, above and below the safety for just ensuring the end side
Literary is consistent with the evolution block core side, and the terminal need not do authentication security flow.
Moreover, after the evolution block core is restarted for some reason, when certain terminal initiates attachment removal request, passing through the terminal
The identity of carrying searches whether there is the terminal in the terminal contexts of the evolution block core, if can find
And integrity protection check's success of Non-Access Stratum, just ensures the safe context and the evolution block core of the end side
Side is consistent, and the terminal is need not to do authentication security flow.
Based on above technical scheme, evolution block core of the present invention breaks down restart after, it is normal to having carried out before restarting
The terminal accessed reduces the access delay of terminal without doing IMSI inquiries, authentication and safe procedures again, reduces IMSI and lets out
Reveal possibility, be unaware to restarting for EPC for terminal, while GUTI duplicate allocation can be avoided, in the communications field
With important market value.
Brief description of the drawings
Fig. 1 is the theory diagram of the present invention.
Fig. 2 is the flow chart of processing terminal attach request of the embodiment of the present invention.
Fig. 3 is the flow chart that the embodiment of the present invention handles service request.
Fig. 4 is the flow chart that processing position of the embodiment of the present invention updates request.
Embodiment
In order to make the purpose , technical scheme and advantage of the present invention be clearer, it is right below in conjunction with drawings and Examples
The present invention is further elaborated.It should be appreciated that the specific embodiments described herein are merely illustrative of the present invention, and
It is not used in the restriction present invention.
As shown in figure 1, the invention discloses a kind of method that evolution block core restarts recovery, this method includes：
A database (102 in such as figure) is created first, and the database is used to store UE contexts, the UE contexts bag
Include but be not limited to EPS Mobility Management (EPS Mobility Management, EMM) context and EPS session managements (EPS
Session Management, ESM) context, the database can access and with access limit by EPC (101 in such as figure), often
When the secondary EPC restarts initialization, the reading database relevant entries are all to be recorded in EPC in the context of corresponding UE,
Simultaneously in EPC, all GUTI read from the database relevant entries are the legal GUTI set used before restarting,
It is described restart before in the legal GUTI set used GUTI can't distribute to the UE that newly accesses below, so can be from basic
On avoid same GUTI distributing to multiple UE.
Then in EPC is normally run, after UE is successfully attached to the EPC for the first time, by described in the EPC on UE
Hereinafter (including but is not limited to EMM contexts and ESM contexts, as follows), information record is inserted into the database table entry
In；When the UE contexts update, by UE updating contexts described in the EPC into database table entry；When UE hairs
During raw cancellation, the corresponding record of the UE contexts of the UE is deleted from affiliated database table entry.
So after the EPC is restarted for some reason, when certain UE initiates attach request (Attach Request) and carries NAS's
During integrity protection security's head, the identity (IMSI or GUTI) carried by the UE is looked into the UE contexts of the EPC
Look for the presence or absence of the UE, if can find and Non-Access Stratum integrity protection check's success, then just can ensure that institute
The safe context and the EPC for stating UE are consistent, therefore the UE need not do authentication security flow, therefore can be greatly reduced
Access delay.
So after the EPC is restarted for some reason, when certain UE launch position updates request (Tracking Area Update
When Request), the identity GUTI or IMSI carried by the UE is searched whether in the UE contexts of the EPC
In the presence of the UE, if can find and NAS integrity protection check success, then above and below the safety that just can ensure that the UE sides
Literary is consistent with the EPC sides, therefore the UE need not do authentication security flow, therefore can greatly reduce access delay.
So after the EPC is restarted for some reason, when certain UE initiates service request (Service Request), by this
Identity service Temporary Mobile Subscriber Identity (the Serving-Temporary Mobile Subscriber that UE is carried
Identity, S-TMSI) search whether there is the UE in the UE contexts of the EPC, if can find and non-
Access Layer integrity protection check success, then the safe context and the EPC sides that just can ensure that the UE sides be it is consistent,
Therefore the UE need not do authentication security flow, therefore access delay can be greatly reduced.
So after the EPC is restarted for some reason, when certain UE initiates attachment removal request (Detach Request), and UE hairs
The situation for playing attach request (Attach Request) is similar, and the identity GUTI or IMSI carried by the UE is described
Searched whether in the EPC UE contexts exist the UE, if can find and Non-Access Stratum integrity protection check
Success, then the safe context and the EPC sides that just can ensure that the UE sides are consistent, therefore the UE is need not to do authentication security
Flow, therefore the access delay that the UE initiates attachment next time can be greatly reduced.
So after the EPC is restarted for some reason, the GUTI that the EPC had been distributed before restarting can't be reassigned to newly
The UE of access, so can fundamentally avoid same GUTI distributing to multiple UE.
So after the EPC is restarted for some reason, for the successful UE of integrity protection check of Non-Access Stratum, it is not required to initiate
IMSI inquiry, so as to reduce IMSI leakage possibilities.
Accessed for the first time after EPC is restarted to illustrate how the present invention reduces the terminal being successfully accessed before EPC is restarted
Time delay, the processing strategy of the embodiment of the present invention described in detail below.
The attach request initiated for UE, the process step of the embodiment of the present invention is as follows：
Step 201：UE initiates attach request, performs step 202.
Step 202：Can judge by the identity (GUTI or IMSI) that carries in UE attach requests NAS message
Corresponding UE contexts are found in EPC, the information such as configuration, the state of the terminal of EPC internal records are obtained, if can search
To step 204 is then performed, step 203 is otherwise performed.
Step 203：Attachment refuse information is sent to UE, then terminates handling process.
Step 204：Judge whether attach request NAS message carries the complete heads that ensure safety of NAS, if the execution step 205 without if,
If then judging whether by safety check, step 206 is then performed by safety check, step 205 is otherwise performed.
Step 205：To UE initiate authentication security flow, after the completion of perform step 206.
Step 206：UE contexts are set up, i.e., is that the terminal sets up context according to agreement flow base station, performs step
207。
Step 207：Judge whether UE context changes, be then to perform step 208, otherwise terminate handling process.
For example, the interior preservation UE contexts of EPC are respectively attribute 1, attribute 2 .. attribute n, then be that each attribute is set
One is changed mark：Attribute 1 changes mark, attribute 2 and changes mark, and .. attributes n changes mark.
In step 201 to step 206, if some attribute n has change, then corresponding attribute n changes mark and is set to
1, all it is 0 if all of attribute change mark, that is, is judged as NO and (UE contexts is preserved in EPC without change), if at least
One attribute, which is changed, is designated 1, that is, needing execution step 208, (the UE contexts of the UE are written to the database, then will be all
Attribute is changed mark and reset).
Step 208：The UE contexts of the UE are written in the database, then terminate handling process.
The service request initiated for UE, the process step of the embodiment of the present invention is as follows：
Step 301：UE initiates service request, performs step 302.
Step 302：Judge that can the identity (S-TMSI) that carried by UE service requests find accordingly in EPC
UE contexts, obtain the information such as configuration, the state of the terminal of EPC internal records, step performed if it can find
304, otherwise perform step 303.
Step 303：Service Reject message is sent to UE, then terminates handling process.
Step 304：Judge that service request NAS message, whether by safety check, if it is performs step 305, otherwise
Perform step 303.
Step 305：UE contexts are set up, step 306 is performed.
Step 306：Judge whether UE context changes, be then to perform step 307, otherwise terminate handling process.
For example, the interior preservation UE contexts of EPC are respectively attribute 1, attribute 2 .. attribute n, then be that each attribute is set
One is changed mark：Attribute 1 changes mark, attribute 2 and changes mark, and .. attributes n changes mark.
In step 301 to step 305, if some attribute n has change, then corresponding attribute n changes mark and is set to
1, all it is 0 if all of attribute change mark, that is, is judged as NO and (UE contexts is preserved in EPC without change), if at least
One attribute, which is changed, is designated 1, that is, needing execution step 307, (the UE contexts of the UE are written to the database, then will be all
Attribute is changed mark and reset).
Step 307：The UE contexts of the UE are written in the database, then terminate handling process.
The position updating request initiated for UE, the process step of the embodiment of the present invention is as follows：
Step 401：UE launch positions update request, perform step 402.
Step 402：Judge that can the identity (GUTI) that carried by UE service requests find accordingly in EPC
UE contexts, obtain the information such as configuration, the state of the terminal of EPC internal records, and step 404 is performed if it can find,
Otherwise step 403 is performed.
Step 403：Location updating refuse information is sent to UE, then terminates handling process.
Step 404：Judge that position updating request NAS message, whether by safety check, if it is performs step 405,
Otherwise step 403 is performed.
Step 405：Location updating is sent to UE to receive, and then performs step 406.
Step 406：Judge whether to need to set up in position updating request NAS message to carry, be then to perform step 408, it is no
Then perform step 407.When it is implemented, there is individual bit indicating bit Active flag to be used to indicate network side in TAU NAS messages
Whether the foundation of the carrying of recovery terminal is needed：Active flag are that 1 mark network side needs to recover to set up；Active flag
Need not for 0.
Step 407：The context of the UE is discharged, step 409 is then performed.
Step 408：UE contexts are set up, step 409 is performed.
Step 409：Judge whether UE context changes, be then to perform step 410, otherwise terminate handling process.
For example, the interior preservation UE contexts of EPC are respectively attribute 1, attribute 2 .. attribute n, then be that each attribute is set
One is changed mark：Attribute 1 changes mark, attribute 2 and changes mark, and .. attributes n changes mark.
In step 401 to step 408, if some attribute n has change, then corresponding attribute n changes mark and is set to
1, all it is 0 if all of attribute change mark, that is, is judged as NO and (UE contexts is preserved in EPC without change), if at least
One attribute, which is changed, is designated 1, that is, needing execution step 410, (the UE contexts of the UE are written to the database, then will be all
Attribute is changed mark and reset).
Step 410：The UE contexts of the UE are written in told database, then terminate handling process.
When it is implemented, those skilled in the art can realize the automatic running of above flow using computer software mode.
The foregoing is only one of embodiments of the invention, be not intended to limit the invention, it is all the present invention spirit and
Any modifications, equivalent substitutions and improvements made within principle, should be included in the scope of the protection.
Claims (9)
1. a kind of evolution block core restarts restoration methods, it is characterised in that：A database is created first, and the database is used for
Terminal contexts are stored, the terminal contexts include but is not limited to above and below EPS Mobility Management context and EPS session managements
Text, evolution block core possesses access limit to the database；When each evolution block core restarts initialization, the number is read
In context according to storehouse relevant entries to counterpart terminal, while in evolution block core, being read from the database relevant entries
All GUTI taken are the legal GUTI set used before restarting, described to restart GUTI in the preceding legal GUTI set used
It is not assigned to the terminal newly accessed below.
2. evolution block core restarts restoration methods according to claim 1, it is characterised in that：When terminal, success is attached for the first time
After the evolution block core, terminal context information record in the evolution block core is inserted into database table entry
In, it is ensured that evolution block core with database terminal contexts it is synchronous.
3. evolution block core restarts restoration methods according to claim 1, it is characterised in that：When terminal contexts occur to appoint
What update when, by evolution block core terminal contexts update into database table entry, it is ensured that the evolution block core with
The synchronization of terminal contexts in the database.
4. evolution block core restarts restoration methods according to claim 1, it is characterised in that：When cancellation occurs for terminal,
The corresponding record of the terminal contexts of the terminal is deleted from corresponding database table entry, it is ensured that evolution block core and database
The synchronization of interior terminal contexts.
5. the evolution block core according to claim 1 or 2 or 3 or 4 restarts restoration methods, it is characterised in that：The evolution
After block core is restarted for some reason, when certain terminal initiates attach request and carries NAS integrity protection security's head, pass through the end
The identity that end is carried searches whether there is the terminal in the terminal contexts of the evolution block core, if can look into
Find and the integrity protection check of Non-Access Stratum is successful, the safe context and the evolution for just ensuring the terminal are grouped
Core is consistent, and terminal need not do authentication security flow.
6. the evolution block core according to claim 1 or 2 or 3 or 4 restarts restoration methods, it is characterised in that：The evolution
After block core is restarted for some reason, when certain terminal initiates attach request and carries NAS integrity protection security's head, pass through the end
The identity that end is carried searches whether there is the terminal in the terminal contexts of the evolution block core, if can look into
Find and the integrity protection check of Non-Access Stratum is successful, the safe context and the evolution for just ensuring the terminal are grouped
Core is consistent, and terminal need not do authentication security flow.
7. the evolution block core according to claim 1 or 2 or 3 or 4 restarts restoration methods, it is characterised in that：The evolution
After block core is restarted for some reason, when certain terminal launch position, which updates, asks, the identity carried by the terminal is described
Searched whether in the terminal contexts of evolution block core exist the terminal, if can find and NAS integrity protection
Verify successfully, the safe context and the evolution block core side for just ensuring the end side are consistent, and the terminal need not be done
Authentication security flow.
8. the evolution block core according to claim 1 or 2 or 3 or 4 restarts restoration methods, it is characterised in that：Drilled when described
Enter after block core restarts for some reason, when certain terminal initiates service request, the identity carried by the terminal services interim
Mobile user identification searches whether there is the terminal in the terminal contexts of the evolution block core, if can find simultaneously
And integrity protection check's success of Non-Access Stratum, just ensure the safe context of the end side and the evolution block core side
It is consistent, the terminal need not do authentication security flow.
9. the evolution block core according to claim 1 or 2 or 3 or 4 restarts restoration methods, it is characterised in that：Drilled when described
Enter after block core restarts for some reason, when certain terminal initiates attachment removal request, the identity carried by the terminal is described
Searched whether in the terminal contexts of evolution block core exist the terminal, if can find and Non-Access Stratum integrality
Protective calibration success, the safe context and the evolution block core side for just ensuring the end side are consistent, and the terminal is
Authentication security flow need not be done.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710175745.5A CN107018507B (en) | 2017-03-22 | 2017-03-22 | Method for restarting and recovering evolved packet core |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710175745.5A CN107018507B (en) | 2017-03-22 | 2017-03-22 | Method for restarting and recovering evolved packet core |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107018507A true CN107018507A (en) | 2017-08-04 |
| CN107018507B CN107018507B (en) | 2020-06-23 |
Family
ID=59440018
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710175745.5A Active CN107018507B (en) | 2017-03-22 | 2017-03-22 | Method for restarting and recovering evolved packet core |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107018507B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108924814A (en) * | 2018-06-06 | 2018-11-30 | 武汉虹信通信技术有限责任公司 | A kind of disaster recovery method based on mobile management entity pool |
| CN111143124A (en) * | 2019-12-19 | 2020-05-12 | 上海上讯信息技术股份有限公司 | Database automation recovery method and device and electronic equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6341312B1 (en) * | 1998-12-16 | 2002-01-22 | International Business Machines Corporation | Creating and managing persistent connections |
| CN1554204A (en) * | 2001-09-10 | 2004-12-08 | ����ɭ�绰�ɷ�����˾ | Recovery of mobile station(s) in connected mode upon RNC failure |
| CN101026866A (en) * | 2006-02-20 | 2007-08-29 | 华为技术有限公司 | AK context cache method for wireless communication system |
| CN102577176A (en) * | 2009-10-23 | 2012-07-11 | 英特尔公司 | Coverage loss recovery in a wireless communication network |
| CN102740266A (en) * | 2011-04-12 | 2012-10-17 | 中兴通讯股份有限公司 | Context synchronization method and system thereof |
| CN104284359A (en) * | 2014-06-17 | 2015-01-14 | 南京邮电大学 | Trans-regional disaster tolerant system under EPC network and control method |
| US20150188949A1 (en) * | 2013-12-31 | 2015-07-02 | Lookout, Inc. | Cloud-based network security |
-
2017
- 2017-03-22 CN CN201710175745.5A patent/CN107018507B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6341312B1 (en) * | 1998-12-16 | 2002-01-22 | International Business Machines Corporation | Creating and managing persistent connections |
| CN1554204A (en) * | 2001-09-10 | 2004-12-08 | ����ɭ�绰�ɷ�����˾ | Recovery of mobile station(s) in connected mode upon RNC failure |
| CN101026866A (en) * | 2006-02-20 | 2007-08-29 | 华为技术有限公司 | AK context cache method for wireless communication system |
| CN102577176A (en) * | 2009-10-23 | 2012-07-11 | 英特尔公司 | Coverage loss recovery in a wireless communication network |
| CN102740266A (en) * | 2011-04-12 | 2012-10-17 | 中兴通讯股份有限公司 | Context synchronization method and system thereof |
| US20150188949A1 (en) * | 2013-12-31 | 2015-07-02 | Lookout, Inc. | Cloud-based network security |
| CN104284359A (en) * | 2014-06-17 | 2015-01-14 | 南京邮电大学 | Trans-regional disaster tolerant system under EPC network and control method |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108924814A (en) * | 2018-06-06 | 2018-11-30 | 武汉虹信通信技术有限责任公司 | A kind of disaster recovery method based on mobile management entity pool |
| CN111143124A (en) * | 2019-12-19 | 2020-05-12 | 上海上讯信息技术股份有限公司 | Database automation recovery method and device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107018507B (en) | 2020-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101400054B (en) | Method, system and device for protecting privacy of customer terminal | |
| US8219064B2 (en) | Method, system, and apparatus for preventing bidding down attacks during motion of user equipment | |
| JP4216255B2 (en) | Processing method for service connection between wireless local area network and user terminal device | |
| US9713001B2 (en) | Method and system for generating an identifier of a key | |
| JP3686038B2 (en) | Method and system for obtaining identification information about a party monitored in a communication network | |
| US20130054611A1 (en) | Apparatus and method for processing partitioned data for securing content | |
| CN106535219B (en) | A kind of user information earth-filling method and device | |
| US20120102556A1 (en) | Method and System for Smart Card Migration | |
| CN105978748A (en) | Terminal equipment information counting method and terminal equipment information counting device based on Hash node | |
| CN107018507A (en) | A kind of evolution block core restarts restoration methods | |
| CN107005842A (en) | Method for authenticating, relevant apparatus and system in a kind of cordless communication network | |
| BRPI0305741B1 (en) | mobile terminal identity protection by modifying the local subscriber registry | |
| CN107548098A (en) | A kind of method and device of differentiated service processing | |
| CN101730095B (en) | Method, device and system for realizing message integrity protection | |
| CN106535156B (en) | Virtual subscriber identity module card migration method, terminal, server and system | |
| JP6456409B2 (en) | Method, apparatus and system for controlling the total number of users attached online | |
| US20190320482A1 (en) | Link re-establishment method, apparatus, and system | |
| CN105282819B (en) | Access method of wireless device, gateway device and wireless network | |
| CN108924814A (en) | A kind of disaster recovery method based on mobile management entity pool | |
| CN113518032B (en) | SRv 6-based user credible identification carrying method and system | |
| JP2023542225A (en) | Method and apparatus for handling non-access stratum context | |
| CN107959584B (en) | Information configuration method and device | |
| CN111163033B (en) | Message forwarding method and device, communication network element and computer readable storage medium | |
| CN106713581A (en) | Communication number identification method, terminal and system | |
| CN111698747A (en) | Roaming method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 430205 Hubei city of Wuhan province Jiangxia Hidden Dragon Island Tan lake two Road No. 1 Patentee after: CITIC Mobile Communication Technology Co., Ltd Address before: 430073 Hubei province Wuhan Dongxin East Lake high tech Development Zone, Road No. 5 Patentee before: Wuhan Hongxin Telecommunication Technologies Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 430205 No.1 tanhu 2nd Road, Canglong Island, Jiangxia District, Wuhan City, Hubei Province Patentee after: CITIC Mobile Communication Technology Co.,Ltd. Address before: 430205 No.1 tanhu 2nd Road, Canglong Island, Jiangxia District, Wuhan City, Hubei Province Patentee before: CITIC Mobile Communication Technology Co., Ltd |