Core network backup method applied to TD-LTE (Time Division Long Term Evolution) Internet-of-Things service isolation environment
A business isolation and Internet of Things technology, applied in the field of core network backup, can solve problems such as network impact, low cost, and ARP information loss, and achieve the effects of reducing switching time, avoiding pairing confusion, and reducing complexity
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
Embodiment 1
[0095] This embodiment describes the processing flow of the EPC failing to receive heartbeat messages from the peer for N consecutive times. The schematic diagram of the flow is as follows Figure 5 shown, including the following steps:
[0096] Step 1: EPC periodically sends a heartbeat message to the mutual backup peer;
[0097] Step 2: If the EPC fails to receive the heartbeat message from the peer for N consecutive times, check whether the network status of the machine is normal;
[0098] Step 3: If the network status of the local end is normal, the local end enters the state of HB_Host, that is, performs the work of the main server and provides external services;
[0099] Step 4: If the network status of the local end is abnormal, the local end enters or maintains the HB_Standby state, works as a standby server, and does not provide external services.
Embodiment 2
[0101] This embodiment describes the processing flow of receiving the heartbeat message from the peer end when the heartbeat states of the mutually standby EPCs are all non-HB_Host. A schematic diagram of the process is Image 6 As shown, the network status of both parties is OK, and the level of EPC-A is higher than that of EPC-B. Image 6 The process shown includes:
[0102] For EPC-A:
[0103] Step A-1: EPC-A in the HB_Initial state receives a heartbeat message from the peer EPC-B of mutual backup, and EPC-A compares the information in the heartbeat message with the information of the local end.
[0104] like Image 6 As shown, the heartbeat message contains at least three pieces of information: local heartbeat status, local network status, and local level. Among them, "0" is used for the heartbeat status of the local end to indicate the non-HB_Host status, and "1" is used to indicate the HB_Host status; "0" is used for the local network status to indicate BAD, and "1...
Embodiment 3
[0110] This embodiment describes the processing flow of receiving the heartbeat message from the peer end when the heartbeat states of the mutually standby EPCs are all non-HB_Host. A schematic diagram of the process is Figure 7 As shown, the network status of EPC-A is BAD, Figure 7 The process shown includes:
[0111] For EPC-A:
[0112]Step A-1: EPC-A in the HB_Initial state sends a heartbeat message to the mutually standby peer EPC-B, carrying the information that its own network status is BAD, that is, setting the field corresponding to the network status in the heartbeat message to 0;
[0113] Step A-2: EPC-A's own network status is BAD and cannot provide services, so it enters the HB_Standby status.
[0114] For EPC-B:
[0115] Step B-1: EPC-B in the HB_Standby state receives the heartbeat message sent by the peer EPC-A of mutual backup, and EPC-B compares the information in the heartbeat message with the information of the local end;
[0116] Step B-2: EPC-B fi...
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More 


