CN113497727A - SAE gateway fault processing method and system - Google Patents
SAE gateway fault processing method and system Download PDFInfo
- Publication number
- CN113497727A CN113497727A CN202010251202.9A CN202010251202A CN113497727A CN 113497727 A CN113497727 A CN 113497727A CN 202010251202 A CN202010251202 A CN 202010251202A CN 113497727 A CN113497727 A CN 113497727A
- Authority
- CN
- China
- Prior art keywords
- sae gateway
- dns server
- gateway
- sae
- dns
- 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
- 238000003672 processing method Methods 0.000 title description 5
- 238000000034 method Methods 0.000 claims abstract description 48
- 239000000523 sample Substances 0.000 claims abstract description 32
- 230000004044 response Effects 0.000 claims abstract description 31
- 238000004891 communication Methods 0.000 claims abstract description 25
- 238000004458 analytical method Methods 0.000 claims description 40
- 238000002955 isolation Methods 0.000 claims description 27
- 238000001514 detection method Methods 0.000 claims description 19
- 238000012544 monitoring process Methods 0.000 claims description 19
- 238000012545 processing Methods 0.000 abstract description 21
- 230000008569 process Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 9
- 230000011664 signaling Effects 0.000 description 8
- 238000010295 mobile communication Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 239000004744 fabric Substances 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
Images
Classifications
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/16—Threshold monitoring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Environmental & Geological Engineering (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention relates to the technical field of core network control, and discloses a method and a system for processing SAE gateway faults, wherein a DNS server and the SAE gateway establish communication connection through a Gn-DNS interface, and the method comprises the following steps: the DNS server sends a probe message to the SAE gateway through the Gn-DNS interface; if the DNS server receives the response message of the SAE gateway, the SAE gateway is determined to be normal, otherwise, the SAE gateway is determined to be in failure. Through the mode, the embodiment of the invention can master the state of the SAE gateway in real time, avoids the problem of analyzing the domain name to the failed SAE gateway, and greatly improves the efficiency of analyzing the system domain name.
Description
Technical Field
The embodiment of the invention relates to the technical field of core network control, in particular to a method and a system for processing SAE gateway faults.
Background
In the prior art, a mobile communication network is composed of a user terminal, an access network and a core network, wherein the user terminal accesses the mobile communication network through a wireless signal provided by the access network, and the access network obtains a network service provided by a mobile operation through the core network.
The Core network of LTE is also called epc (evolved Packet Core network), and mainly includes multiple network elements, which are: an MME (mobility Management entity) mobility Management entity, which is used for controlling related network elements through signaling and mainly used for mobility Management and session related control processing; the HSS server is mainly used for storing user information; the DNS server is used for carrying out domain name resolution; the S-GW (serving gateway) is a service gateway of a core network, is a network element of a data plane and is responsible for processing the user data of a local network; the P-gw (PDN gateway) is a PDN gateway, primarily connected to external data. When a user requests communication service, addressing and selection among the devices in the EPC are completed through domain name system resolution of a DNS (domain name system) server, and the DNS server is responsible for completing domain name to address resolution.
In the research process, the applicant finds that, for a fault scenario that a fault SAE gateway cannot continuously undertake a service when an existing network SAE (system Architecture evolution) gateway device has a major fault, a corresponding emergency plan is currently used for manually deleting an analysis record of the fault SAE gateway for a maintainer. The emergency method needs manual intervention, cannot respond immediately after a fault occurs, causes certain business influence on a user before emergency operation is completed, and the instant disaster recovery capability of the network needs to be improved.
Disclosure of Invention
In view of the foregoing problems, embodiments of the present invention provide a method and a system for processing a SAE gateway failure, so as to solve the problem in the prior art that a manual failure removal is required.
According to an aspect of the embodiments of the present invention, a method for handling a failure of an SAE gateway is provided, where the DNS server establishes a communication connection with the SAE gateway through a Gn-DNS interface, and the method includes:
the DNS server sends a probe message to the SAE gateway through the Gn-DNS interface;
if the DNS server receives the response message of the SAE gateway, the SAE gateway is determined to be normal, otherwise, the SAE gateway is determined to be in failure.
Further, if the DNS server receives the response message of the SAE gateway, it determines that the SAE gateway is normal, otherwise, it determines that the SAE gateway is faulty, including:
the DNS server circularly sends a detection message to the SAE gateway in a detection period T1, and if the number of times of not receiving the response message of the SAE gateway is larger than a first threshold value, the SAE gateway is determined to be in failure.
Further, the determining that the SAE gateway fails further comprises isolating the failed SAE gateway;
the isolating the failed SAE gateway comprises:
the DNS server acquires the analysis record of the SAE gateway with the fault and deletes the analysis record of the SAE gateway with the fault;
or the like, or, alternatively,
the DNS server reduces resolution record priority of the failed SAE gateway.
Further, after isolating the failed SAE gateway, the method further includes:
the DNS server circularly sends a probe message to the isolated SAE gateway within a probe period T1, and if all response messages of the isolated SAE gateway are received, the isolated SAE gateway is released from isolation;
the de-isolating the isolated SAE gateway includes:
the DNS server adds the analysis record of the isolated SAE gateway;
or the like, or, alternatively,
the DNS server increases resolution record priority for the isolated SAE gateway.
Another embodiment of the present invention further provides a method for handling a failure of an SAE gateway, where the DNS server establishes a communication connection with the SAE gateway through a Gn-DNS interface, and the method includes:
the DNS server receives SAE gateway state information sent by the SAE gateway through the Gn-DNS interface;
and if the SAE gateway state information is gateway failure, the DNS server determines the SAE gateway failure.
Further, if the SAE gateway status information is a gateway failure, the DNS server determines that the SAE gateway failure includes:
if the number of times that the DNS continuously receives the SAE gateway state as the fault state in the monitoring period T2 is greater than a third threshold, the DNS server determines that the SAE gateway is in fault.
Further, the DNS server determines that the SAE gateway is faulty, further comprising isolating the faulty SAE gateway;
the isolating the failed SAE gateway comprises:
the DNS server acquires the analysis record of the SAE gateway with the fault and deletes the analysis record of the SAE gateway with the fault;
or the like, or, alternatively,
the DNS server reduces resolution record priority of the failed SAE gateway.
Further, after isolating the failed SAE gateway, the method further includes:
the DNS server receives all the SAE gateway state information circularly sent by the isolated SAE gateway in a monitoring period T2, and if the SAE gateway state information is normal, the isolated SAE gateway is released from isolation;
the de-isolating the isolated SAE gateway includes:
the DNS server adds the analysis record of the isolated SAE gateway;
or the like, or, alternatively,
the DNS server increases resolution record priority for the isolated SAE gateway.
The embodiment of the invention also provides an SAE gateway fault processing system, which comprises a DNS server and an SAE gateway, wherein the DNS server and the SAE gateway establish communication connection through a Gn-DNS interface;
the DNS server is used for sending a probe message to the SAE gateway through the Gn-DNS interface;
the SAE gateway is used for sending a response message to the DNS server when receiving the probe message sent by the DNS server;
and when receiving the response message of the SAE gateway, the DNS server determines that the SAE gateway is normal, otherwise, determines that the SAE gateway is in failure.
The embodiment of the invention also provides another SAE gateway fault processing system, which comprises a DNS server and an SAE gateway, wherein the DNS server and the SAE gateway establish communication connection through a Gn-DNS interface;
the SAE gateway sends SAE gateway state information to the DNS server through the Gn-DNS interface;
the DNS server receives SAE gateway state information sent by the SAE gateway through the Gn-DNS interface; and if the SAE gateway state information is gateway failure, the DNS server determines the SAE gateway failure.
The embodiment of the invention enables the DNS server and the SAE gateway to communicate by arranging the Gn-DNS interface between the DNS server and the SAE gateway, can master the state of the SAE gateway in real time, avoids the problem of resolving the domain name to the faulty SAE gateway, and greatly improves the efficiency of resolving the domain name of the system.
The foregoing description is only an overview of the technical solutions of the embodiments of the present invention, and the embodiments of the present invention can be implemented according to the content of the description in order to clearly understand the technical means of the embodiments of the present invention, and the above and other objects, features, and advantages of the embodiments of the present invention are more clearly understood.
Drawings
The drawings are only for purposes of illustrating embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a schematic diagram of a network fabric interface provided by an embodiment of the invention;
fig. 2 is a schematic diagram illustrating a DNS server structure provided by an embodiment of the present invention;
FIG. 3 is a diagram illustrating an SAE gateway architecture provided by an embodiment of the present invention;
FIG. 4 shows an SAE gateway failure handling signal interaction diagram provided by an embodiment of the present invention;
FIG. 5 shows an SAE gateway failure handling signal interaction diagram provided by another embodiment of the present invention;
FIG. 6 is a diagram illustrating a system for handling a SAE gateway failure according to an embodiment of the present invention;
fig. 7 is a schematic diagram illustrating a DNS server structure provided by an embodiment of the present invention;
fig. 8 shows a schematic view of an SAE gateway structure provided in an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein.
Fig. 1 shows a schematic view of a structural interface of a mobile communication network provided by an embodiment of the present invention, where the mobile communication network includes a terminal side, an access network side, a core network side, and an IP service network side, and the terminal side is connected to an access network through an air interface LTE-Uu and then accesses the mobile communication network through the access network. The access network comprises base stations eNodeB, the eNodeBs are connected through an X2 interface, and the base stations and the core network are connected through an S1 interface. The core network comprises a mobile management entity MME, an SAE gateway, a DNS server, an HSS server, a policy and charging function entity PCRF and the like, wherein the SAE gateway comprises a service gateway S-GW and a PDN gateway P-SW, and in practical application, the S-GW and the P-GW can be combined together or can be separately arranged. The MME is connected with the DNS server through a Gn interface and connected with the SAE gateway through an S11 interface, and when receiving a user request, the MME carries out domain name resolution through the DNS server and then selects a proper SAE gateway for routing.
In a mobile communication network, addressing and gateway selection among devices in an EPC network are completed through a DNS (domain name system) server, and the DNS server is responsible for completing domain name to address resolution. The DNS resolution types of the EPC network include NAPTR type, SRV type, and a type. The NAPTR type is responsible for completing the resolution of a domain name to an authoritative domain name, i.e. converting one string into another string, completing the domain name rewriting. SRV types are typically used in conjunction with NAPTR types. The a record eventually completes the resolution of the domain name to address. NAPTR type query returns a domain name (Replacement) and a Service (Service) corresponding to the domain name, if the Replacement is not the final interface name supporting the Service, the NAPTR record indicates the DNS client (MME in the EPC network) to continuously initiate SRV record query by setting Flag to be S. When the Flag field of the NAPTR record is S, the MME selects a domain name (Replacement) corresponding to a Service (Service) required by the MME, initiates an SRV record query, and obtains an interface name (carried by a Target field) supporting the Service. And finally, the IP address corresponding to the interface is obtained through A record query.
Referring to the network architecture shown in fig. 1, when a 4G user attaches, an MME selects an S-GW and a P-GW for the user according to an analysis result returned by a DNS server, and the S-GW and the P-GW establish an S5 bearer, so as to provide an EPC core network access channel for the user.
In the attachment process, when the S-GW is selected according to the current location information of the user, the parsing process is generally NAPTR-SRV-NAPTR- A four-step query or NAPTR-SRV- A three-step query. Taking NAPTR-SRV-A three-step query as an example, the analysis process is briefly described as follows:
the MME constructs a complete domain name of a Tracking Area Identity (TAI), initiates a NAPTR type query request to a DNS server, and the DNS server returns a list of S-GW supporting S5/S8/S11 interface services. The MME initiates SRV type query to a DNS server by using an S-GW list returned by the NAPTR query result, and the DNS server returns a top n host domain name corresponding to the S-GW in the list to the MME; and the MME selects the domain name of the S-GW host with the S11 interface capability, selects the domain name according to the priority and the weight, selects the S-GW with high priority according to the priority, randomly selects the S-GW with high priority within the same priority according to the weight, and initiates an A query to the DNS according to the selected domain name to obtain the S11 interface address of the S-GW.
In the attachment process, when a P-GW is selected according to an access Point name (apn) (access Point name) carried by a user, the analysis process is generally a NAPTR-SRV-a three-step query, which is briefly described as follows:
the MME constructs a complete domain name of the APN, initiates an NAPTR type query request to a DNS server, and the DNS server returns a P-GW list supporting S5/S8 interface service; the MME initiates SRV type query to a DNS server by using a P-GW list returned by the NAPTR query result, and the DNS server returns a top n host domain name corresponding to the P-GW in the list to the MME; and the MME selects the domain name of the P-GW host with S5/S8 interface capability, selects the domain name according to priority and weight, selects the P-GW with high priority according to the priority, randomly selects the P-GW with high priority within the same priority according to the weight, initiates A query to the DNS server according to the selected domain name, and obtains the S5/S8 interface address of the P-GW.
In the embodiment of the invention, when the SAE gateway equipment of the current network has major faults and the SAE gateway can not continuously bear services, the Gn-DNS interface is established between the DNS server and the SAE gateway, and the SAE gateway with the faults is isolated on the DNS server, so that a user can not be distributed to the SAE gateway with the faults any more, and the user use is prevented from being influenced. As shown in fig. 1, in the embodiment of the present invention, a Gn-DNS interface is established between a DNS server and an SAE gateway, and the DNS server can directly communicate with the SAE gateway through the Gn-DNS interface to grasp the state of the SAE gateway in real time, isolate the failed SAE gateway when a failure occurs, and thus, do not cause any influence on services, and greatly shorten the response time of the failure.
As shown in fig. 2 and fig. 3, an embodiment of the present invention provides a DNS server 300 and an SAE gateway 400, where the DNS server 300 includes a probing module 301, a message receiving module 302, and a failure handling module 303; the SAE gateway 400 includes a communication module 401 and a status monitoring module 402. The DNS server 300 and SAE gateway 400 cooperate with each other to enable interaction between the two through a Gn-DNS interface.
The DNS server 300 includes a detection module 301, a message receiving module 302, and a failure handling module 303; the detection module 301 is configured to periodically detect the state of the SAE gateway through the Gn-DNS interface, and send a detection message, where the detection may be performed based on a GTP protocol; the sending of the probe message may be sent periodically. The message receiving module 302 is configured to receive a message sent by an SAE gateway, where the message may be a response message sent to a DNS server by the SAE gateway after receiving the probe message sent by the probe module 302, or may be SAE gateway status information and the like sent to the DNS server by the SAE gateway actively; the fault processing module 303 is configured to determine a state of an SAE gateway, and isolate the SAE gateway having the fault; further, the failure handling module 303 may further perform de-isolation on the SAE gateway again after the SAE gateway fails and recovers, so that the SAE gateway is activated again.
The SAE gateway 400 includes a communication module 401 and a status monitoring module 402. The communication module 401 is configured to interface with the DNS server 300, and is configured to receive a probe message sent by the DNS server, send a response message for the probe message to the DNS server, and send status information of the SAE gateway to the DNS server; the status monitoring module 402 is used to monitor the status of itself, and the common SAE gateway failure status includes: the SAE gateway address pool utilization rate reaches 100%, and the address can not be allocated to the user any more; the SAE gateway main-standby mutual-aid single board simultaneously fails; or, the SAE gateway interface board fails all, etc.
In the embodiment of the present invention, the SAE gateway fault is processed through the DNS server and the SAE gateway provided above through the Gn-DNS interface, specifically as shown in fig. 4, a method for processing an SAE gateway fault is provided in the embodiment of the present invention.
Step 501: the DNS server sends a detection message to the SAE gateway through a Gn-DNS interface;
the DNS server sends a probe message to each SAE gateway according to a preset probe period T1 through the probe module. In the embodiment of the application, a probing period T1 is set on the DNS server, the initial value may be 5min, a probing interval timer T12 is set, and the initial value is 30s, that is, the DNS server may perform 10 probing within 5 minutes, and send 10 probing messages to the SAE gateway. The above-mentioned detection period and detection interval time may be preset, and the specific setting value is not limited herein.
Step 502: the DNS server receives a response message sent by the SAE gateway to the DNS server;
if the SAE gateway is normal, a response message is returned to the DNS server, which represents that the SAE gateway has no abnormal state and the DNS server does not need to act.
If a SAE gateway does not return a response message in the whole probing period T1, the DNS server considers that the SAE gateway is unreachable, i.e. the SAE gateway is determined to be failed, and the SAE gateway is likely to have a serious failure such as power down.
Optionally, if the DNS server circularly sends the probe message to the SAE gateway in the probe period T1, but the number of times of response messages of the SAE gateway that are not received is greater than the preset first threshold, the SAE gateway is also determined to be faulty.
When the DNS server determines that the SAE gateway is in fault, the DNS server actively isolates the SAE gateway in fault, the DNS server acquires domain name information and IP address information of the SAE gateway in fault, and a fault processing module of the DNS server isolates the corresponding SAE gateway according to the domain name information and the IP address information.
In the embodiment of the present invention, the isolation operation may be to obtain the analysis record of the failed SAE gateway for the DNS server, and delete the analysis record of the failed SAE gateway, including the analysis record of the S-GW and the analysis record of the P-GW; meanwhile, because the DNS server and the MME in the current network have DNS analysis caches, the DNS server needs to clear the caches in order to enable the modified analysis records to take effect immediately; meanwhile, the DNS server can inform all the MME of clearing the cache through a Gn interface between the DNS server and the MME, namely, a cache clearing instruction is issued to the MME, and the MME clears the cache of the MME after receiving the cache clearing instruction.
Of course, the DNS may also isolate the failed SAE gateway in other manners, for example, the DNS server reduces the resolution record priority of the failed SAE gateway, so that the DNS is preferentially resolved to the gateway that has not failed when performing domain name resolution.
Furthermore, a SAE gateway can be on-line again after being isolated. When an SAE gateway recovers from a failure, the embodiment of the present invention also provides a function of automatically releasing isolation. If the DNS server receives the response information of the isolated SAE gateway again in the probing period T1 through the probing module, the DNS server considers the isolated SAE gateway to recover from the failure. The DNS server can consider the fault SAE gateway to recover when receiving response messages in all the detection periods; the failed SAE gateway may also be considered to recover from the failure when the number of received response messages is greater than a second threshold.
When the SAE gateway is determined to recover from the failure, the DNS server acquires the domain name and IP address information of the SAE gateway and releases the SAE gateway from isolation. In the embodiment of the present invention, the isolation release may be that the DNS server adds resolution records of the SAE gateway according to the domain name information of the SAE gateway, including adding resolution records of an S-GW and adding resolution records of a P-GW. The failed SAE gateway can also be de-isolated by raising the priority of the resolution record of the SAE gateway. Meanwhile, after the DNS server removes the isolation of the faulty SAE gateway, the DNS server clears the cache of the DNS server, and also informs all MME of clearing the cache through a Gn interface between the DNS server and the MME, namely, a cache clearing instruction is issued to the MME, and after the MME receives the cache clearing instruction, the MME clears the cache of the MME. Certainly, the above DNS server may also release SAE isolation manually, the system may set parameters on the DNS server, and when the DNS server is set to release isolation manually, release isolation manually; when set to automatically un-quarantine, then the DNS server can automatically un-quarantine the SAE server recovering from the failure.
As can be seen from the above, the embodiment of the invention enables the DNS server and the SAE gateway to communicate with each other by arranging the Gn-DNS interface between the DNS server and the SAE gateway, and the DNS server is provided with the active detection function, so that the active detection of the SAE gateway is realized, the state of the SAE gateway can be mastered in real time, the problem of resolving the domain name to the failed SAE gateway is avoided, and the domain name resolution efficiency of the system is greatly improved. Meanwhile, the SAE gateway fault processing method provided by the embodiment of the invention can monitor the states of all SAE gateways in an aspect and improve the monitoring convenience in an active detection mode of the DNS server without greatly modifying each SAE gateway.
In this embodiment, as shown in fig. 5, the SAE gateway monitors its own state through a state monitoring module, and periodically reports the state of the SAE gateway to a DNS server.
Step 601: SAE gateway sends Initial GW context request to DNS server;
on the SAE gateway, a state monitoring period is defined as T2, an initial value is 5min, a state reporting timer T21 has an initial value of 20s, that is, the SAE gateway reports state information of itself 15 times within 5 minutes.
The signaling reported for the first time in the monitoring period is defined as Initial GW context request, and the message includes the address, state code, etc. of SAE gateway; when the SAE gateway works normally, the state code is 1001; when the SAE gateway is in the failure state, different failure information is represented by different state codes, such as: the SAE gateway address pool utilization rate reaches 100%, and the address can not be allocated to the user any more, and at the moment, the state code in the signaling is 2001; when the SAE gateway main/standby mutual-aid type single board fails simultaneously, the state code in the signaling is 2002; when the SAE gateway interface board fails completely, the status code in the signaling is 2003, and so on.
Step 602: the DNS server sends an Initial GW context ACK to the SAE gateway;
after receiving the Initial GW context request message, DNS server replies to the Initial GW context ACK, which indicates that the status signaling of SAE gateway has been received.
Step 603: SAE gateway sends Update GW context request to DNS server;
the SAE non-first reporting signaling is an Update GW context request, which also includes the state information of the SAE gateway.
Step 604: DNS server sends Update GW context ACK to SAE gateway;
when the SAE gateway is always in a normal state, the SAE gateway status code contained in the Update GW context request reported by the SAE gateway is 1001.
When the DNS server continuously receives the signaling of the abnormal state reported by the SAE gateway and the state code of the SAE gateway is a failure in the monitoring period T2, the DNS server isolates the failed SAE gateway. In the embodiment of the present invention, when the number of times that the DNS server continuously receives the SAE gateway state as the failure state is greater than the third threshold, the SAE gateway is determined to be failed, and the SAE gateway is isolated.
When the DNS server determines that the SAE gateway is in fault, the DNS server actively isolates the SAE gateway in fault, the DNS server acquires domain name information and IP address information of the SAE gateway in fault, and a fault processing module of the DNS server isolates the corresponding SAE gateway according to the domain name information and the IP address information.
In the embodiment of the present invention, the isolation operation may be to obtain the analysis record of the failed SAE gateway for the DNS server, and delete the analysis record of the failed SAE gateway, including the analysis record of the S-GW and the analysis record of the P-GW; meanwhile, because the DNS server and the MME in the current network have DNS analysis caches, the DNS server needs to clear the caches in order to enable the modified analysis records to take effect immediately; meanwhile, the DNS server can inform all the MME of clearing the cache through a Gn interface between the DNS server and the MME, namely, a cache clearing instruction is issued to the MME, and the MME clears the cache of the MME after receiving the cache clearing instruction.
Of course, the DNS may also isolate the failed SAE gateway in other manners, for example, the DNS server reduces the resolution record priority of the failed SAE gateway, so that the DNS is preferentially resolved to the gateway that has not failed when performing domain name resolution.
Furthermore, when an SAE gateway is isolated and recovers from a fault, the embodiment of the present invention also provides a function of automatically releasing the isolation. If the DNS server receives the state information reported by the SAE gateway in the monitoring period T2, and the state of the SAE gateway is normal, the DNS server determines that the isolated SAE gateway has recovered from the failure. The DNS server may consider the failed SAE gateway to recover when all the status information received within the monitoring period T2 indicates that the SAE gateway is normal; the failed SAE gateway may also be considered to recover from the failure when the number of received status information is normal is greater than the fourth threshold.
When the SAE gateway is determined to recover from the failure, the DNS server acquires the domain name and IP address information of the SAE gateway and releases the SAE gateway from isolation. In the embodiment of the present invention, the isolation release may be that the DNS server adds resolution records of the SAE gateway according to the domain name information of the SAE gateway, including adding resolution records of an S-GW and adding resolution records of a P-GW. The failed SAE gateway can also be de-isolated by raising the priority of the resolution record of the SAE gateway. Meanwhile, after the DNS server removes the isolation of the faulty SAE gateway, the DNS server clears the cache of the DNS server, and also informs all MME of clearing the cache through a Gn interface between the DNS server and the MME, namely, a cache clearing instruction is issued to the MME, and after the MME receives the cache clearing instruction, the MME clears the cache of the MME. Certainly, the above DNS server may also release SAE isolation manually, the system may set parameters on the DNS server, and when the DNS server is set to release isolation manually, release isolation manually; when set to automatically un-quarantine, then the DNS server can automatically un-quarantine the SAE server recovering from the failure.
In summary, the SAE gateway failure processing method provided in the embodiment of the present invention enables the DNS server and the SAE gateway to communicate with each other by setting the Gn-DNS interface between the DNS server and the SAE gateway, and actively reports the state information of the SAE gateway to the DNS server, so that the DNS server can master the state of the SAE gateway, and isolate or release the isolation of the SAE gateway according to the state of the SAE gateway, thereby avoiding the problem of resolving a domain name to a failed SAE gateway, and greatly improving the efficiency of system domain name resolution. Meanwhile, compared with the method for processing the SAE gateway failure provided by the previous embodiment, the method for processing the SAE gateway failure can more refine the failure state of the SAE gateway, can process according to different failure states, and can more accurately master the state of the SAE gateway.
Of course, the two SAE gateway failure handling manners provided in the embodiment of the present invention may be implemented separately, or implemented by combining the two, for example: on one hand, the DNS server actively detects each SAE gateway, and meanwhile, the SAE gateway also actively reports the state information of the SAE gateway to the DNS server.
Another embodiment of the present invention further provides a system for handling SAE gateway failure, as shown in fig. 6, the system is an EPC core network system, and includes entity network elements such as MME, HSS, DNS server 300 and SAE gateway 400, and the DNS server establishes communication connection with the SAE gateway through Gn-DNS interface; the DNS server 300 and the SAE gateway are respectively configured to perform the SAE gateway failure handling method in the above-described embodiment.
Specifically, in one embodiment, in the system for processing SAE gateway failure, the DNS server is configured to send a probe message to the SAE gateway through the Gn-DNS interface; the SAE gateway is used for sending a response message to the DNS server when receiving the probe message sent by the DNS server; and when receiving the response message of the SAE gateway, the DNS server determines that the SAE gateway is normal, otherwise, determines that the SAE gateway is in failure.
Further, the DNS server circularly sends a probe message to the SAE gateway in a probe period T1, and if the number of times of not receiving the response message of the SAE gateway is greater than a first threshold, determines that the SAE gateway is faulty.
Further, the determining that the SAE gateway fails further comprises isolating the failed SAE gateway; the isolating the failed SAE gateway comprises:
the DNS server acquires the analysis record of the SAE gateway with the fault and deletes the analysis record of the SAE gateway with the fault; or, the DNS server reduces the resolution record priority of the failed SAE gateway.
After isolating the failed SAE gateway, the method further comprises:
the DNS server circularly sends a probe message to the isolated SAE gateway within a probe period T1, and if all response messages of the isolated SAE gateway are received, the isolated SAE gateway is released from isolation;
the de-isolating the isolated SAE gateway includes:
the DNS server adds the analysis record of the isolated SAE gateway; or, the DNS server increases resolution record priority of the isolated SAE gateway.
As can be seen from the above, the embodiment of the invention enables the DNS server and the SAE gateway to communicate with each other by arranging the Gn-DNS interface between the DNS server and the SAE gateway, and the DNS server is provided with the active detection function, so that the active detection of the SAE gateway is realized, the state of the SAE gateway can be mastered in real time, the problem of resolving the domain name to the failed SAE gateway is avoided, and the domain name resolution efficiency of the system is greatly improved. Meanwhile, the system for processing the SAE gateway failure provided by the embodiment of the invention can monitor the states of all SAE gateways in an aspect by an active detection mode of the DNS server without greatly modifying each SAE gateway, thereby improving the convenience of monitoring.
In another embodiment, in the system for processing a fault of an SAE gateway provided in the embodiment of the present invention, a DNS server receives SAE gateway status information sent by the SAE gateway through the Gn-DNS interface;
and if the SAE gateway state information is gateway failure, the DNS server determines the SAE gateway failure.
Further, if the DNS receives the SAE gateway failure status continuously for more than a third threshold within a monitoring period T2, the DNS server determines that the SAE gateway fails.
Further, the DNS server determines that the SAE gateway is faulty, further comprising isolating the faulty SAE gateway;
the isolating the failed SAE gateway comprises:
the DNS server acquires the analysis record of the SAE gateway with the fault and deletes the analysis record of the SAE gateway with the fault; or, the DNS server reduces the resolution record priority of the failed SAE gateway.
Further, the DNS server removes the isolation of the isolated SAE gateway if all the received SAE gateway status information sent by the isolated SAE gateway in a cycle within a monitoring period T2 is normal;
the de-isolating the isolated SAE gateway includes:
the DNS server adds the analysis record of the isolated SAE gateway; or, the DNS server increases resolution record priority of the isolated SAE gateway.
In summary, the SAE gateway failure processing system provided in the embodiment of the present invention enables the DNS server and the SAE gateway to communicate with each other by setting the Gn-DNS interface between the DNS server and the SAE gateway, and actively reports the state information of the SAE gateway to the DNS server, so that the DNS server can master the state of the SAE gateway, and isolate or release the isolation of the SAE gateway according to the state of the SAE gateway, thereby avoiding the problem of resolving a domain name to a failed SAE gateway, and greatly improving the efficiency of system domain name resolution. Meanwhile, compared with the system for processing the SAE gateway failure provided by the previous embodiment, the present embodiment can refine the failure state of the SAE gateway more, can process according to different failure states, and can grasp the state of the SAE gateway more accurately.
Fig. 7 is a schematic structural diagram of an embodiment of a DNS server provided in the embodiment of the present invention, and a specific embodiment of the present invention does not limit a specific implementation of the DNS server.
As shown in fig. 7, the DNS server may include: a processor (processor)702, a Communications Interface 704, a memory 706, and a communication bus 708.
Wherein: the processor 702, communication interface 704, and memory 706 communicate with each other via a communication bus 708. A communication interface 704 for communicating with network elements of other devices, such as clients or other servers. The processor 702 is configured to execute the procedure 710, and may specifically perform the relevant steps in the embodiment of the SAE gateway failure handling method described above.
In particular, the program 710 may include program code comprising computer-executable instructions.
The processor 702 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement an embodiment of the present invention. The DNS server comprises one or more processors which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.
The memory 706 stores a program 710. The memory 706 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
Specifically, the program 710 may be invoked by the processor 702 to cause the DNS server to perform the following operations:
sending a probe message to the SAE gateway through the Gn-DNS interface;
if the response message of the SAE gateway is received, the SAE gateway is determined to be normal, otherwise, the SAE gateway is determined to be in failure.
Further, the DNS server circularly sends a probe message to the SAE gateway in a probe period T1, and if the number of times of not receiving the response message of the SAE gateway is greater than a first threshold, determines that the SAE gateway is faulty.
Further, the DNS server isolates the failed SAE gateway;
the isolating the failed SAE gateway comprises:
the DNS server acquires the analysis record of the SAE gateway with the fault and deletes the analysis record of the SAE gateway with the fault; or, the DNS server reduces the resolution record priority of the failed SAE gateway.
Further, the DNS server circularly sends probe messages to the isolated SAE gateway within a probe period T1, and if all response messages of the isolated SAE gateway are received, the isolated SAE gateway is released from isolation;
the de-isolating the isolated SAE gateway includes:
the DNS server adds the analysis record of the isolated SAE gateway; or, the DNS server increases resolution record priority of the isolated SAE gateway.
Alternatively, the program 710 may be specifically invoked by the processor 702 to cause the DNS server to perform the following operations:
receiving SAE gateway state information sent by the SAE gateway through the Gn-DNS interface;
and if the SAE gateway state information is gateway failure, the DNS server determines the SAE gateway failure.
Further, if the DNS receives the SAE gateway failure status continuously for more than a third threshold within a monitoring period T2, the DNS server determines that the SAE gateway fails.
Further, the isolating the DNS server from the failed SAE gateway;
the isolating the failed SAE gateway comprises:
the DNS server acquires the analysis record of the SAE gateway with the fault and deletes the analysis record of the SAE gateway with the fault; or, the DNS server reduces the resolution record priority of the failed SAE gateway.
Further, the DNS server removes the isolation of the isolated SAE gateway if all the received SAE gateway status information sent by the isolated SAE gateway in a cycle within a monitoring period T2 is normal;
the de-isolating the isolated SAE gateway includes:
the DNS server adds the analysis record of the isolated SAE gateway; or, the DNS server increases resolution record priority of the isolated SAE gateway.
As can be seen from the above, the DNS server provided in the embodiment of the present invention can communicate with the SAE gateway through the Gn-DNS interface, and perform domain name resolution according to the state of the SAE gateway, thereby avoiding the problem of resolving a domain name to a failed SAE gateway, and greatly improving the efficiency of system domain name resolution.
Fig. 8 is a schematic structural diagram of an SAE gateway embodiment provided in the embodiment of the present invention, and the specific embodiment of the present invention does not limit the specific implementation of the SAE gateway.
As shown in fig. 8, the SAE gateway may include: a processor (processor)802, a Communications Interface 804, a memory 806, and a communication bus 808.
Wherein: the processor 802, communication interface 804, and memory 806 communicate with one another via a communication bus 808. A communication interface 804 for communicating with network elements of other devices, such as clients or other servers. Processor 802, configured to execute process 810, may specifically perform the steps described above for the SAE gateway failure handling method embodiment.
In particular, program 810 may include program code comprising computer-executable instructions.
The processor 802 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement embodiments of the present invention. The DNS server comprises one or more processors which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.
The memory 806 stores a program 810. The memory 806 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The routine 810 may be specifically invoked by the processor 802 to cause the SAE gateway to perform the following operations:
when a detection message sent by the DNS is received, a response message is returned to the DNS through a Gn-DNS interface; or sending SAE gateway state information to the DNS server through the Gn-DNS interface.
Through the SAE gateway, the communication with the DNS server can be realized through the Gn-DNS interface, and the DNS server can carry out domain name resolution according to the state of the SAE gateway, so that the problem of resolving the domain name to a fault SAE gateway is avoided, and the domain name resolution efficiency of the system is greatly improved.
An embodiment of the present invention provides a computer-readable storage medium, where the storage medium stores at least one executable instruction, and when the executable instruction runs on an SAE gateway fault handling system, the SAE gateway fault handling system is caused to execute an SAE gateway fault handling method in any method embodiment described above.
The embodiment of the invention also provides an SAE gateway fault processing device which is used for executing the SAE gateway fault processing method.
Embodiments of the present invention provide a computer program that can be invoked by a processor to cause an SAE gateway failure handling system to perform an SAE gateway failure handling method in any of the above method embodiments.
Embodiments of the present invention provide a computer program product comprising a computer program stored on a computer-readable storage medium, the computer program comprising program instructions which, when run on a computer, cause the computer to perform the method of SAE gateway failure handling in any of the above-described method embodiments.
The algorithms or displays presented herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. In addition, embodiments of the present invention are not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the embodiments of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the invention and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names. The steps in the above embodiments should not be construed as limiting the order of execution unless specified otherwise.
Claims (10)
1. An SAE gateway failure handling method, wherein the DNS server establishes a communication connection with the SAE gateway through a Gn-DNS interface, comprising:
the DNS server sends a probe message to the SAE gateway through the Gn-DNS interface;
if the DNS server receives the response message of the SAE gateway, the SAE gateway is determined to be normal, otherwise, the SAE gateway is determined to be in failure.
2. The SAE gateway failure handling method of claim 1, wherein determining the SAE gateway is normal if the DNS server receives the response message of the SAE gateway, otherwise determining the SAE gateway failure comprises:
the DNS server circularly sends a detection message to the SAE gateway in a detection period T1, and if the number of times of not receiving the response message of the SAE gateway is larger than a first threshold value, the SAE gateway is determined to be in failure.
3. The SAE gateway failure handling method of claim 1, wherein the determining the SAE gateway failure further comprises isolating the failed SAE gateway;
the isolating the failed SAE gateway comprises:
the DNS server acquires the analysis record of the SAE gateway with the fault and deletes the analysis record of the SAE gateway with the fault;
or the like, or, alternatively,
the DNS server reduces resolution record priority of the failed SAE gateway.
4. The SAE gateway failure handling method of claim 3, wherein after isolating the failed SAE gateway, further comprising:
the DNS server circularly sends a probe message to the isolated SAE gateway within a probe period T1, and if all response messages of the isolated SAE gateway are received, the isolated SAE gateway is released from isolation;
the de-isolating the isolated SAE gateway includes:
the DNS server adds the analysis record of the isolated SAE gateway;
or the like, or, alternatively,
the DNS server increases resolution record priority for the isolated SAE gateway.
5. An SAE gateway failure handling method, wherein the DNS server establishes a communication connection with the SAE gateway through a Gn-DNS interface, comprising:
the DNS server receives SAE gateway state information sent by the SAE gateway through the Gn-DNS interface;
and if the SAE gateway state information is gateway failure, the DNS server determines the SAE gateway failure.
6. The SAE gateway failure handling method of claim 5, wherein if the SAE gateway status information is a gateway failure, the DNS server determines the SAE gateway failure, comprising:
if the number of times that the DNS continuously receives the SAE gateway state as the fault state in the monitoring period T2 is greater than a third threshold, the DNS server determines that the SAE gateway is in fault.
7. The SAE gateway failure handling method of claim 5, wherein the DNS server determines the SAE gateway failure, further comprising quarantining the failed SAE gateway;
the isolating the failed SAE gateway comprises:
the DNS server acquires the analysis record of the SAE gateway with the fault and deletes the analysis record of the SAE gateway with the fault;
or the like, or, alternatively,
the DNS server reduces resolution record priority of the failed SAE gateway.
8. The SAE gateway failure handling method of claim 7, wherein after isolating the failed SAE gateway, further comprising:
the DNS server receives all the SAE gateway state information circularly sent by the isolated SAE gateway in a monitoring period T2, and if the SAE gateway state information is normal, the isolated SAE gateway is released from isolation;
the de-isolating the isolated SAE gateway includes:
the DNS server adds the analysis record of the isolated SAE gateway;
or the like, or, alternatively,
the DNS server increases resolution record priority for the isolated SAE gateway.
9. An SAE gateway fault handling system, characterized in that the system comprises a DNS server and an SAE gateway, wherein the DNS server and the SAE gateway establish a communication connection through a Gn-DNS interface;
the DNS server is used for sending a probe message to the SAE gateway through the Gn-DNS interface;
the SAE gateway is used for sending a response message to the DNS server when receiving the probe message sent by the DNS server;
and when receiving the response message of the SAE gateway, the DNS server determines that the SAE gateway is normal, otherwise, determines that the SAE gateway is in failure.
10. An SAE gateway fault handling system, characterized in that the system comprises a DNS server and an SAE gateway, wherein the DNS server and the SAE gateway establish a communication connection through a Gn-DNS interface;
the SAE gateway sends SAE gateway state information to the DNS server through the Gn-DNS interface;
the DNS server receives SAE gateway state information sent by the SAE gateway through the Gn-DNS interface; and if the SAE gateway state information is gateway failure, the DNS server determines the SAE gateway failure.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010251202.9A CN113497727B (en) | 2020-04-01 | 2020-04-01 | SAE gateway fault processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010251202.9A CN113497727B (en) | 2020-04-01 | 2020-04-01 | SAE gateway fault processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113497727A true CN113497727A (en) | 2021-10-12 |
| CN113497727B CN113497727B (en) | 2024-02-27 |
Family
ID=77994152
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010251202.9A Active CN113497727B (en) | 2020-04-01 | 2020-04-01 | SAE gateway fault processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113497727B (en) |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1925429A (en) * | 2006-09-30 | 2007-03-07 | 杭州华为三康技术有限公司 | Method and equipment for realizing fast detection |
| CN101772058A (en) * | 2008-12-30 | 2010-07-07 | 华为技术有限公司 | Method, device and system for managing path in system architecture evolution architecture |
| CN101977396A (en) * | 2010-10-22 | 2011-02-16 | 中兴通讯股份有限公司 | System and method for realizing network element service switching in multimedia messaging service |
| US20110096750A1 (en) * | 2009-10-27 | 2011-04-28 | Cisco Technology, Inc. | Dynamic gateway selection process |
| CN102045411A (en) * | 2009-10-13 | 2011-05-04 | 中国移动通信集团公司 | Method, server and system for domain name resolution |
| CN102893637A (en) * | 2011-05-18 | 2013-01-23 | 华为技术有限公司 | Network equipment failure processing method and packet data network gateway equipment |
| CN103283180A (en) * | 2011-12-02 | 2013-09-04 | 华为技术有限公司 | Fault detection method, gateway, user equipment, and communication system |
| CN105338563A (en) * | 2011-12-02 | 2016-02-17 | 华为技术有限公司 | Fault detection method, gateway, user equipment and communication system |
| CN106790469A (en) * | 2016-12-09 | 2017-05-31 | 中国联合网络通信集团有限公司 | A kind of buffer control method, device and system |
| CN106878475A (en) * | 2015-12-14 | 2017-06-20 | 中国电信股份有限公司 | Domain name addressing method and system |
| WO2017101120A1 (en) * | 2015-12-18 | 2017-06-22 | 华为技术有限公司 | Communication method and apparatus, and system |
| CN107438275A (en) * | 2016-05-26 | 2017-12-05 | 中国移动通信集团广东有限公司 | A kind of information acquisition method and device |
| CN109257787A (en) * | 2010-09-15 | 2019-01-22 | 瑞典爱立信有限公司 | Method and apparatus for relocating and restoring to unload by the connection of failed services gateway and business |
-
2020
- 2020-04-01 CN CN202010251202.9A patent/CN113497727B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1925429A (en) * | 2006-09-30 | 2007-03-07 | 杭州华为三康技术有限公司 | Method and equipment for realizing fast detection |
| CN101772058A (en) * | 2008-12-30 | 2010-07-07 | 华为技术有限公司 | Method, device and system for managing path in system architecture evolution architecture |
| CN102045411A (en) * | 2009-10-13 | 2011-05-04 | 中国移动通信集团公司 | Method, server and system for domain name resolution |
| US20110096750A1 (en) * | 2009-10-27 | 2011-04-28 | Cisco Technology, Inc. | Dynamic gateway selection process |
| CN109257787A (en) * | 2010-09-15 | 2019-01-22 | 瑞典爱立信有限公司 | Method and apparatus for relocating and restoring to unload by the connection of failed services gateway and business |
| CN101977396A (en) * | 2010-10-22 | 2011-02-16 | 中兴通讯股份有限公司 | System and method for realizing network element service switching in multimedia messaging service |
| CN102893637A (en) * | 2011-05-18 | 2013-01-23 | 华为技术有限公司 | Network equipment failure processing method and packet data network gateway equipment |
| CN103283180A (en) * | 2011-12-02 | 2013-09-04 | 华为技术有限公司 | Fault detection method, gateway, user equipment, and communication system |
| CN105338563A (en) * | 2011-12-02 | 2016-02-17 | 华为技术有限公司 | Fault detection method, gateway, user equipment and communication system |
| CN106878475A (en) * | 2015-12-14 | 2017-06-20 | 中国电信股份有限公司 | Domain name addressing method and system |
| WO2017101120A1 (en) * | 2015-12-18 | 2017-06-22 | 华为技术有限公司 | Communication method and apparatus, and system |
| CN107438275A (en) * | 2016-05-26 | 2017-12-05 | 中国移动通信集团广东有限公司 | A kind of information acquisition method and device |
| CN106790469A (en) * | 2016-12-09 | 2017-05-31 | 中国联合网络通信集团有限公司 | A kind of buffer control method, device and system |
Non-Patent Citations (3)
| Title |
|---|
| "\"C4-090068-Discussion on PDN Gateway Identity\"", 3GPP TSG_CT\\WG4_PROTOCOLLARS_EX-CN4 * |
| NTT DOCOMO: ""C4-090068-Discussion on PDN Gateway Identity"", 3GPP TSG_CT\\WG4_PROTOCOLLARS_EX-CN4 * |
| 张宗峰;: "浅谈EPC核心网络的故障应急", 数码世界, no. 10 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113497727B (en) | 2024-02-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103731918B (en) | The system and method that paging in UTRAN/GERAN/E UTRAN networks is reduced when idle signaling reduction is effective | |
| KR101503762B1 (en) | Paging processing method and system, serving gateway | |
| US10567216B2 (en) | Fault detection method, gateway, user equipment, and communications system | |
| EP2696610A2 (en) | Method and device for processing failures of mobility management device in idle mode signaling reduction activated scene | |
| US9094857B2 (en) | Method, apparatus and system for handling node failure | |
| US10165618B2 (en) | Service processing method and device | |
| CN109983736A (en) | A kind of processing method, equipment and the system of NF component exception | |
| EP3253090A1 (en) | Service disaster recovery method and related device | |
| CN105357701A (en) | LTE network gateway pool disaster tolerance method, device and system | |
| WO2018166328A1 (en) | Information processing method, apparatus, computer readable storage medium and electronic device | |
| CN104081808A (en) | MME restoration | |
| CN105814934B (en) | Handle method, mobile management entity and the home subscriber server of called service | |
| CN107872326B (en) | Method, device and system for releasing session resources | |
| KR20190038167A (en) | Method and apparatus for managing a pdn connection in a wireless communication system | |
| EP3425850B1 (en) | Method and device for processing communication path | |
| EP3300418A1 (en) | Method and system for recovering communication state after sgw failure, and mme and sgw | |
| JP6544835B2 (en) | Message processing method and apparatus | |
| CN103051484B (en) | Session service processing method, system and Session Border Controll | |
| US10225191B2 (en) | Service packet distribution method and apparatus | |
| CN113497727B (en) | SAE gateway fault processing method and system | |
| CN110087333B (en) | Method, device, equipment and storage medium for preventing service interruption | |
| WO2022084385A1 (en) | Notification of packet data network gateway (pgw) ip address change | |
| CN114629778A (en) | IP multimedia service fault processing method, electronic equipment and storage medium | |
| JP7325551B2 (en) | SERVICE CONTINUITY IMPLEMENTATION METHOD, RELATED DEVICE, AND SYSTEM | |
| CN115250438B (en) | Short message service disaster recovery method, system and computing equipment based on 5G network |
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 |