CN113497727B - SAE gateway fault processing method and system - Google Patents
SAE gateway fault processing method and system Download PDFInfo
- Publication number
- CN113497727B CN113497727B CN202010251202.9A CN202010251202A CN113497727B CN 113497727 B CN113497727 B CN 113497727B CN 202010251202 A CN202010251202 A CN 202010251202A CN 113497727 B CN113497727 B CN 113497727B
- Authority
- CN
- China
- Prior art keywords
- sae gateway
- dns server
- sae
- gateway
- 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.)
- Active
Links
- 238000003672 processing method Methods 0.000 title description 10
- 238000001514 detection method Methods 0.000 claims abstract description 41
- 238000000034 method Methods 0.000 claims abstract description 37
- 230000004044 response Effects 0.000 claims abstract description 31
- 238000004891 communication Methods 0.000 claims abstract description 28
- 238000004458 analytical method Methods 0.000 claims description 23
- 238000012544 monitoring process Methods 0.000 claims description 20
- 238000002955 isolation Methods 0.000 claims description 14
- 238000012545 processing Methods 0.000 abstract description 14
- 239000000523 sample Substances 0.000 description 12
- 238000010586 diagram Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 8
- 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
- 230000003247 decreasing effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000004904 shortening Methods 0.000 description 1
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]
Abstract
The embodiment of the invention relates to the technical field of core network control and discloses a method and a system for processing faults of an SAE gateway, wherein a DNS server and the SAE gateway are in communication connection through a Gn-DNS interface, and the method comprises the following steps: the DNS server sends a detection message to the SAE gateway through the Gn-DNS interface; and if the DNS server receives the response message of the SAE gateway, determining that the SAE gateway is normal, otherwise, determining that the SAE gateway is faulty. Through the mode, the embodiment of the invention can grasp the state of the SAE gateway in real time, avoid the problem of resolving the domain name to the fault SAE gateway and greatly improve the domain name resolving efficiency of the system.
Description
Technical Field
The embodiment of the invention relates to the technical field of core network control, in particular to an SAE gateway fault processing method and system.
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 mobile operation through the core network.
The core network of LTE is also called EPC (Evolved Packet Core network), and mainly includes a plurality of network elements, which are respectively: MME (Mobility Management Entity) a mobility management entity for controlling related network elements through signaling, 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; 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 local network user data; P-GW (PDN Gateway) is a PDN gateway, mainly connected to external data. When a user requests a communication service, addressing and selection among devices in the EPC are completed through domain name system resolution of a DNS server, and the DNS server is responsible for completing domain name to address resolution.
The applicant finds that in the research process, a major fault occurs to SAE (System Architecture Evolution) gateway equipment of the existing network, the fault SAE gateway cannot continue to bear the fault scene of the service, and the corresponding emergency plan is that maintainers manually delete the analysis records of the fault SAE gateway. The emergency method needs manual intervention, cannot respond immediately after the fault occurs, causes a certain business influence to the user before the emergency operation is completed, and improves the instant disaster recovery capability of the network.
Disclosure of Invention
In view of the above problems, the embodiments of the present invention provide a method and a system for processing SAE gateway faults, which are used for solving the problem in the prior art that manual fault removal is required.
According to an aspect of the embodiment of the present invention, there is provided a method for handling a fault of an SAE gateway, where the DNS server establishes a communication connection with the SAE gateway through a Gn-DNS interface, including:
the DNS server sends a detection message to the SAE gateway through the Gn-DNS interface;
and if the DNS server receives the response message of the SAE gateway, determining that the SAE gateway is normal, otherwise, determining that the SAE gateway is faulty.
Further, if the DNS server receives the response message of the SAE gateway, determining that the SAE gateway is normal, otherwise, determining that the SAE gateway is faulty includes:
and 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 faulty.
Further, the determining the SAE gateway failure further comprises isolating the failed SAE gateway;
Said isolating said 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 alternatively, the first and second heat exchangers may be,
the DNS server reduces the priority of resolution records for the failed SAE gateway.
Further, after isolating the faulty SAE gateway, the method further includes:
the DNS server circularly sends a detection message to the isolated SAE gateway in a detection period T1, and if all response messages of the isolated SAE gateway are received, the isolated SAE gateway is isolated;
the de-isolating the isolated SAE gateway comprises:
the DNS server adds a resolution record of the isolated SAE gateway;
or alternatively, the first and second heat exchangers may be,
the DNS server increases the resolution record priority of the isolated SAE gateway.
The invention also provides a fault processing method of the SAE gateway, wherein the DNS server establishes communication connection with the SAE gateway through a Gn-DNS interface, and the fault processing method comprises the following steps:
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 a gateway fault, the DNS server determines the SAE gateway fault.
Further, if the SAE gateway status information is a gateway failure, the DNS server determines that the SAE gateway fails, including:
and if the DNS continuously receives that the SAE gateway state is in the fault state in the monitoring period T2, the number of times is larger than a third threshold value, and 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;
said isolating said 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 alternatively, the first and second heat exchangers may be,
the DNS server reduces the priority of resolution records for the failed SAE gateway.
Further, after isolating the faulty SAE gateway, the method further includes:
the DNS server receives the state information of all the SAE gateways circularly transmitted by the isolated SAE gateways in a monitoring period T2 and then de-isolates the isolated SAE gateways;
the de-isolating the isolated SAE gateway comprises:
the DNS server adds a resolution record of the isolated SAE gateway;
Or alternatively, the first and second heat exchangers may be,
the DNS server increases the resolution record priority of 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 detection 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 detection 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 faulty.
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 a gateway fault, the DNS server determines the SAE gateway fault.
According to the embodiment of the invention, the Gn-DNS interface is arranged between the DNS server and the SAE gateway, so that the DNS server and the SAE gateway can communicate, the state of the SAE gateway can be mastered in real time, the problem of resolving the domain name to the fault SAE gateway is avoided, and the domain name resolving efficiency of the system is greatly improved.
The foregoing description is only an overview of the technical solutions of the embodiments of the present invention, and may be implemented according to the content of the specification in order to further clarify the technical means of the embodiments of the present invention, and in order to make the foregoing and other objects, features and advantages of the embodiments of the present invention more obvious, the following description of the present invention will be given by way of example only.
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 designate like parts throughout the figures. In the drawings:
fig. 1 shows a schematic diagram of a network architecture interface provided by an embodiment of the present invention;
fig. 2 shows a schematic structural diagram of a DNS server according to an embodiment of the present invention;
fig. 3 shows a schematic diagram of an SAE gateway structure provided by an embodiment of the present invention;
FIG. 4 shows an SAE gateway fault handling signal interaction diagram provided by an embodiment of the present invention;
FIG. 5 is a diagram showing an SAE gateway fault handling signal interaction provided by another embodiment of the present invention;
FIG. 6 shows a schematic diagram of an SAE gateway fault handling system provided by an embodiment of the present invention;
fig. 7 is a schematic diagram of a DNS server structure according to an embodiment of the present invention;
fig. 8 shows a schematic diagram of an SAE gateway structure provided by 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 present invention are shown in the drawings, it should be understood that the present invention may be embodied in various forms and should not be limited to the embodiments set forth herein.
Fig. 1 shows a schematic diagram of a mobile communication network structure interface 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 the access network through an air interface LTE-Uu, and then is accessed to the mobile communication network through the access network. The access network comprises base station eNodeBs, all eNodeBs are connected through an X2 interface, and the base station and the core network are connected through an S1 interface. The core network comprises a mobility 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 arranged separately. The MME is connected with the DNS server through a Gn interface and is 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 an appropriate SAE gateway for routing.
In a mobile communication network, addressing and gateway selection among devices in the EPC network are performed by a DNS server, which is responsible for performing domain name to address resolution. DNS resolution types for EPC networks 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 character string into another character string, and completing the domain name rewriting. SRV types are typically used in conjunction with NAPTR types. The record A finally completes the resolution of the domain name to the address. The NAPTR type query returns a domain name (update) and a Service (Service) corresponding to the domain name, and if the update is not the final interface name of the supporting Service, the NAPTR record instructs the DNS client (MME in EPC network) to continue to initiate the SRV record query by setting Flag to "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, obtaining the IP address corresponding to the interface through the record A query.
Referring to the network architecture shown in fig. 1, when a 4G user attaches, the MME selects S-GW and P-GW for the user according to the analysis result returned by the DNS server, and the S-GW and the P-GW establish S5 bearer to provide EPC core network access for the user.
In the attachment procedure, when the S-GW is selected according to the current location information of the user, the parsing procedure is generally Sup>A NAPTR-SRV-NAPTR-Sup>A four-step query or Sup>A NAPTR-SRV-Sup>A three-step query. Taking NAPTR-SRV-A three-step query as an example, the simplified parsing process is as follows:
the MME constructs the complete domain name of the tracking area indicator TAI (Trace Area Identity), initiates a NAPTR type query request to a DNS server, and the DNS server returns an S-GW list supporting S5/S8/S11 interface services. The MME initiates SRV type inquiry to a DNS server by using an S-GW list returned by the NAPTR inquiry result, and the DNS server returns the top n host domain name of the corresponding S-GW in the list to the MME; the MME selects an S-GW host domain name with the S11 interface capability, selects according to the priority and the weight, firstly selects according to the priority, selects the S-GW with high priority, randomly selects according to the weight in the same priority, 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 flow, when the P-GW is selected according to the access point name APN (Access Point Name) carried by the user, the parsing process is generally Sup>A three-step query of NAPTR-SRV-Sup>A, and the parsing process is briefly described as follows:
MME constructs the complete domain name of APN, initiates NAPTR type query request to DNS server, DNS server returns a P-GW list supporting S5/S8 interface service; the MME initiates SRV type inquiry to a DNS server by using a P-GW list returned by the NAPTR inquiry result, and the DNS server returns the top n host domain name of the corresponding P-GW in the list to the MME; the MME selects a P-GW host domain name with S5/S8 interface capability, selects according to priority and weight, firstly selects according to priority, selects P-GW with high priority, randomly selects according to weight in the same priority, initiates A inquiry to a DNS server according to the selected domain name, and obtains the S5/S8 interface address of the P-GW.
When the SAE gateway equipment of the existing network has serious faults, the SAE gateway can not continue to bear the service, and the faulty SAE gateway is isolated on the DNS server by establishing the Gn-DNS interface between the DNS server and the SAE gateway, so that the user can not be distributed to the faulty SAE gateway any more, and the user is prevented from being influenced. As shown in FIG. 1, the embodiment of the invention establishes a Gn-DNS interface between the DNS server and the SAE gateway, and can directly communicate with the SAE gateway through the Gn-DNS interface, grasp the state of the SAE gateway in real time, isolate the fault SAE gateway when the fault occurs, and not cause any influence on the service, thereby greatly shortening the fault response time.
As shown in fig. 2 and 3, an embodiment of the present invention proposes a DNS server 300 and an SAE gateway 400, the DNS server 300 including a probing module 301, a message receiving module 302, and a fault handling module 303; the SAE gateway 400 includes a communication module 401 and a status monitoring module 402. The DNS server 300 and the SAE gateway 400 cooperate with each other to realize interaction between the two through a Gn-DNS interface.
The DNS server 300 includes a probing module 301, a message receiving module 302, and a fault handling module 303; the detection module 301 is configured to periodically detect a 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 transmission of the probe message may be periodically transmitted. 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 after the SAE gateway receives the probe message sent by the probe module 302, or may be SAE gateway status information that the SAE gateway actively sends to the DNS server, etc.; the fault handling module 303 is configured to determine a state of an SAE gateway, and isolate the faulty SAE gateway; further, the fault handling module 303 may further re-de-isolate the SAE gateway after the SAE gateway is recovered, so that the SAE gateway is re-activated.
The SAE gateway 400 includes a communication module 401 and a status monitoring module 402. The communication module 401 is configured to perform interface communication with the DNS server 300, and is configured to receive a probe message sent by the DNS server, and also configured to send a response message for the probe message to the DNS server, and further configured to send status information of the SAE gateway to the DNS server; the state monitoring module 402 is configured to monitor its own state, such as a common SAE gateway fault state: the SAE gateway address pool utilization rate reaches 100%, and addresses cannot be allocated to users any more; the SAE gateway main-standby mutual assistance single board fails at the same time; or, SAE gateway interface board failure in its entirety, etc.
The embodiment of the invention processes the SAE gateway fault through the DNS server and the SAE gateway through the Gn-DNS interface, and particularly as shown in fig. 4, the embodiment of the invention provides a SAE gateway fault processing method.
Step 501: the DNS server sends a detection message to the SAE gateway through a Gn-DNS interface;
the DNS server sends detection messages to all SAE gateways according to a preset detection period T1 through a detection module. According to the method and the system for detecting the data in the SAE gateway, the detection period T1 is set on the DNS server, the initial value can be 5min, the detection interval timer T12 is set, the initial value is 30s, namely, the DNS server can detect 10 times within 5min, and 10 detection messages are sent to the SAE gateway. The detection period and the detection interval time may be preset, and specific setting values are 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 does not need to act.
If a certain SAE gateway does not return a response message in the whole detection period T1, the DNS server considers that the SAE gateway is not reachable, i.e. recognizes that the SAE gateway is faulty, and the SAE gateway is likely to have serious faults such as power-down.
Optionally, if the DNS server sends a probe message to the SAE gateway in a probe period T1 in a circulating manner, but the number of times of the response message of the SAE gateway that is not received is greater than a preset first threshold, the SAE gateway is also determined to be faulty.
When the DNS server confirms that the SAE gateway fails, the DNS server actively isolates the SAE gateway with failure, the DNS server acquires domain name information and IP address information of the SAE gateway with failure, and a failure 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 obtain, for a DNS server, a resolution record of the faulty SAE gateway, and delete the resolution record of the faulty SAE gateway, including a resolution record of the S-GW and a resolution record of the P-GW; meanwhile, because the DNS analysis cache exists in the existing network DNS server and the MME, the DNS server needs to clear the cache in order to enable the modified analysis record to take effect immediately; meanwhile, the DNS server also informs all MMEs of clearing caches through a Gn interface between the DNS server and the MME, namely, issues a cache clearing instruction to the MME, and clears own caches after the MME receives the cache clearing instruction.
Of course, the DNS may also isolate the faulty SAE gateway by other means, such as the DNS server decreasing the priority of the resolution record of the faulty SAE gateway, so that the DNS resolves preferentially to the non-faulty SAE gateway when performing domain name resolution.
Further, a certain SAE gateway can be re-online after being isolated. The embodiment of the invention also provides a function of automatically removing isolation after a certain SAE gateway recovers from a fault. If the DNS server receives the response information of the isolated SAE gateway again in the detection period T1 through the detection module, the DNS server considers that the isolated SAE gateway recovers from the fault. The DNS server can only consider that the fault SAE gateway is recovered when receiving response messages in all detection periods; the faulty SAE gateway may also be considered to recover from the fault 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 obtains domain name and IP address information of the SAE gateway, and de-isolates the SAE gateway. In the embodiment of the present invention, the de-isolation may be that the DNS server increases the resolution record of the SAE gateway according to the domain name information of the SAE gateway, including increasing the resolution record of the S-GW and increasing the resolution record of the P-GW. The faulty SAE gateway can also be de-isolated by increasing the priority of the resolution record of the SAE gateway. Meanwhile, after the fault SAE gateway is removed from isolation, the DNS server clears the self cache, and also informs all MMEs of clearing the cache through a Gn interface between the DNS server and the MME, namely issues a cache clearing instruction to the MME, and after the MME receives the cache clearing instruction, clears the self cache. Of course, the above-mentioned mode of removing SAE from the DNS server can also be through the manual mode, the system can set up the parameter on DNS server, when set up as the manual mode to remove from the isolation, remove from the isolation manually; when set to automatically de-quarantine, then the DNS server can automatically de-quarantine the SAE server recovered from the failure.
From the above, according to the embodiment of the invention, the Gn-DNS interface is arranged between the DNS server and the SAE gateway, so that the DNS server and the SAE gateway can communicate, 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 fault SAE gateway is avoided, and the domain name resolving 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 aspect without greatly modifying all SAE gateways in a mode of actively detecting by a DNS server, thereby improving the monitoring convenience.
In another embodiment of the present invention, 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 the DNS server.
Step 601: the SAE gateway sends Initial GW context request to the DNS server;
on the SAE gateway, a state monitoring period is defined as T2, an initial value is 5min, a state report timer T21 and an initial value is 20s, namely the SAE gateway can report the state information of the SAE gateway for 15 times within 5 min.
The first reported signaling in the monitoring period is defined as Initial GW context request, and the message includes the address, status code, etc. of the SAE gateway; when the SAE gateway works normally, the state code is 1001; when the SAE gateway is in a fault state, different fault information is represented by different status codes, such as: the SAE gateway address pool utilization rate reaches 100%, the addresses cannot be allocated to the users any more, and at the moment, the state code in the signaling is 2001; when the SAE gateway main and standby mutual assistance single boards simultaneously fail, the state code in the signaling is 2002; the SAE gateway interface board fails all the time, the status code in the signaling is 2003 and so on.
Step 602: the DNS server sends Initial GW context ACK to the SAE gateway;
when the DNS server receives the Initial GW context request message, a reply Initial GW context ACK indicates that the SAE gateway's status signaling has been received.
Step 603: the SAE gateway sends Update GW context request to the DNS server;
the SAE non-first report signaling is Update GW context request, which also includes the SAE gateway's status information.
Step 604: the DNS server sends Update GW context ACK to the SAE gateway;
when the SAE gateway is always in a normal state, then the SAE gateway reported Update GW context request contains an SAE gateway status code of 1001.
When the DNS server continuously receives the signaling of the state exception reported by the SAE gateway and the state code of the SAE gateway to be fault in the monitoring period T2, the DNS server isolates the SAE gateway with fault. In the embodiment of the invention, when the number of times that the DNS server continuously receives that the SAE gateway state is in the fault state is greater than the third threshold value, the SAE gateway is determined to be in fault, and the SAE gateway is isolated.
When the DNS server confirms that the SAE gateway fails, the DNS server actively isolates the SAE gateway with failure, the DNS server acquires domain name information and IP address information of the SAE gateway with failure, and a failure 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 obtain, for a DNS server, a resolution record of the faulty SAE gateway, and delete the resolution record of the faulty SAE gateway, including a resolution record of the S-GW and a resolution record of the P-GW; meanwhile, because the DNS analysis cache exists in the existing network DNS server and the MME, the DNS server needs to clear the cache in order to enable the modified analysis record to take effect immediately; meanwhile, the DNS server also informs all MMEs of clearing caches through a Gn interface between the DNS server and the MME, namely, issues a cache clearing instruction to the MME, and clears own caches after the MME receives the cache clearing instruction.
Of course, the DNS may also isolate the faulty SAE gateway by other means, such as the DNS server decreasing the priority of the resolution record of the faulty SAE gateway, so that the DNS resolves preferentially to the non-faulty SAE gateway when performing domain name resolution.
Furthermore, when a certain SAE gateway is isolated and recovered from a fault, the embodiment of the invention also provides a function of automatically removing 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 considers that the isolated SAE gateway has recovered from the fault. The DNS server can consider that the fault SAE gateway is recovered when all the state information received in the monitoring period T2 indicates that the SAE gateway is normal; the faulty SAE gateway may also be considered to recover from the fault when the received status information is that the normal number is greater than the fourth threshold.
When the SAE gateway is determined to recover from the failure, the DNS server obtains domain name and IP address information of the SAE gateway, and de-isolates the SAE gateway. In the embodiment of the present invention, the de-isolation may be that the DNS server increases the resolution record of the SAE gateway according to the domain name information of the SAE gateway, including increasing the resolution record of the S-GW and increasing the resolution record of the P-GW. The faulty SAE gateway can also be de-isolated by increasing the priority of the resolution record of the SAE gateway. Meanwhile, after the fault SAE gateway is removed from isolation, the DNS server clears the self cache, and also informs all MMEs of clearing the cache through a Gn interface between the DNS server and the MME, namely issues a cache clearing instruction to the MME, and after the MME receives the cache clearing instruction, clears the self cache. Of course, the above-mentioned mode of removing SAE from the DNS server can also be through the manual mode, the system can set up the parameter on DNS server, when set up as the manual mode to remove from the isolation, remove from the isolation manually; when set to automatically de-quarantine, then the DNS server can automatically de-quarantine the SAE server recovered from the failure.
In summary, according to the SAE gateway fault processing method provided by the embodiment of the invention, the Gn-DNS interface is set between the DNS server and the SAE gateway, so that communication can be performed between the DNS server and the SAE gateway, and the state information of the DNS server is actively reported to the DNS server through the SAE gateway, so that the DNS server can grasp the state of the SAE gateway, and isolate or de-isolate the SAE gateway according to the state of the SAE gateway, thereby avoiding the problem of resolving a domain name to the faulty SAE gateway, and greatly improving the efficiency of resolving a domain name of a system. Meanwhile, compared with the SAE gateway fault processing method provided in the previous embodiment, the method can refine the fault state of the SAE gateway, can process according to different fault states, and can grasp the state of the SAE gateway more accurately.
Of course, the two SAE gateway fault handling manners provided in the embodiment of the present invention may be implemented separately, or may be implemented in combination, 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, so that the advantages of the two modes can be fully utilized by combining the two modes, the state of the SAE gateway can be known more accurately, and the domain name can be resolved to a proper gateway.
The other embodiment of the present invention also provides an SAE gateway fault handling system, as shown in fig. 6, where 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 used to perform the SAE gateway failure handling method in the above embodiment, respectively.
Specifically, in one embodiment, in the SAE gateway fault handling system, 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 detection 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 faulty.
Further, the DNS server sends a probe message to the SAE gateway in a probe period T1 in a circulating manner, 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 fails.
Further, the determining the SAE gateway failure further comprises isolating the failed SAE gateway; said isolating said 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 said isolating said failed SAE gateway, further comprising:
the DNS server circularly sends a detection message to the isolated SAE gateway in a detection period T1, and if all response messages of the isolated SAE gateway are received, the isolated SAE gateway is isolated;
the de-isolating the isolated SAE gateway comprises:
the DNS server adds a resolution record of the isolated SAE gateway; or, the DNS server increases the resolution record priority of the isolated SAE gateway.
From the above, according to the embodiment of the invention, the Gn-DNS interface is arranged between the DNS server and the SAE gateway, so that the DNS server and the SAE gateway can communicate, 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 fault SAE gateway is avoided, and the domain name resolving efficiency of the system is greatly improved. Meanwhile, the SAE gateway fault processing system provided by the embodiment of the invention can monitor the states of all SAE gateways in aspect without greatly modifying all SAE gateways in a mode of actively detecting by a DNS server, thereby improving the monitoring convenience.
In another embodiment, in the SAE gateway fault handling system provided in the embodiment of the present invention, a DNS server receives, through the Gn-DNS interface, SAE gateway status information sent by the SAE gateway;
and if the SAE gateway state information is a gateway fault, the DNS server determines the SAE gateway fault.
Further, if the number of times that the DNS continuously receives that the SAE gateway status is the failure status is greater than the third threshold in the 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;
said isolating said 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, if all the SAE gateway state information circularly sent by the isolated SAE gateway received by the DNS server in the monitoring period T2 is normal, the isolated SAE gateway is de-isolated;
The de-isolating the isolated SAE gateway comprises:
the DNS server adds a resolution record of the isolated SAE gateway; or, the DNS server increases the resolution record priority of the isolated SAE gateway.
In summary, in the SAE gateway fault handling system provided by the embodiment of the present invention, a Gn-DNS interface is provided between the DNS server and the SAE gateway, so that communication can be performed between the DNS server and the SAE gateway, and the SAE gateway actively reports its own state information to the DNS server, so that the DNS server can grasp the state of the SAE gateway, and isolate or de-isolate the SAE gateway according to the state of the SAE gateway, thereby avoiding the problem of resolving a domain name to the faulty SAE gateway, and greatly improving the efficiency of resolving a domain name of the system. Meanwhile, compared with the SAE gateway fault processing system provided in the previous embodiment, the fault state of the SAE gateway can be further refined, processing can be performed according to different fault states, and the state of the SAE gateway can be more accurately mastered.
Fig. 7 is a schematic structural diagram of a DNS server embodiment according to an embodiment of the present invention, and the specific embodiment of the present invention is not limited to the specific implementation of the DNS server.
As shown in fig. 7, the DNS server may include: a processor 702, a communication interface (Communications Interface), a memory 706, and a communication bus 708.
Wherein: processor 702, communication interface 704, and memory 706 perform communication 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. Processor 702 is configured to execute program 710 and may specifically perform the relevant steps described above for the SAE gateway fault handling method embodiment.
In particular, program 710 may include program code including computer-executable instructions.
The processor 702 may be a Central Processing Unit (CPU), or a specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement embodiments of the present invention. The DNS server includes one or more processors, which may be the same type of processor, such as one or more CPUs; but may also be different types of processors such as one or more CPUs and one or more ASICs.
Memory 706 for storing programs 710. The memory 706 may comprise high-speed RAM memory or may further comprise non-volatile memory (non-volatile memory), such as at least one disk memory.
Program 710 may be specifically invoked by processor 702 to cause a DNS server to:
sending a probing message to the SAE gateway over the Gn-DNS interface;
and if the response message of the SAE gateway is received, determining that the SAE gateway is normal, otherwise, determining that the SAE gateway is faulty.
Further, the DNS server sends a probe message to the SAE gateway in a probe period T1 in a circulating manner, 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 fails.
Further, the DNS server isolates the failed SAE gateway;
said isolating said 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 a detection message to the isolated SAE gateway in a detection period T1, and if all response messages of the isolated SAE gateway are received, the isolated SAE gateway is isolated;
The de-isolating the isolated SAE gateway comprises:
the DNS server adds a resolution record of the isolated SAE gateway; or, the DNS server increases the 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:
receiving SAE gateway state information sent by the SAE gateway through the Gn-DNS interface;
and if the SAE gateway state information is a gateway fault, the DNS server determines the SAE gateway fault.
Further, if the number of times that the DNS continuously receives that the SAE gateway status is the failure status is greater than the third threshold in the monitoring period T2, the DNS server determines that the SAE gateway fails.
Further, said causing a DNS server to isolate said failed SAE gateway;
said isolating said 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, if all the SAE gateway state information circularly sent by the isolated SAE gateway received by the DNS server in the monitoring period T2 is normal, the isolated SAE gateway is de-isolated;
The de-isolating the isolated SAE gateway comprises:
the DNS server adds a resolution record of the isolated SAE gateway; or, the DNS server increases the resolution record priority of the isolated SAE gateway.
From the above, the DNS server provided by 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, so as to avoid the problem of resolving the domain name to the faulty SAE gateway, and greatly improve the efficiency of domain name resolution of the system.
Fig. 8 shows a schematic structural diagram of an SAE gateway embodiment according to an embodiment of the present invention, which is not limited to the specific implementation of the SAE gateway.
As shown in fig. 8, the SAE gateway may include: a processor (processor) 802, a communication interface (Communications Interface) 804, a memory (memory) 806, and a communication bus 808.
Wherein: processor 802, communication interface 804, and memory 806 communicate with each other 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 is configured to execute program 810 and may specifically perform the relevant steps described above for the SAE gateway fault handling method embodiment.
In particular, program 810 may include program code including computer-executable instructions.
The processor 802 may be a central processing unit CPU, or a specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement embodiments of the present invention. The DNS server includes one or more processors, which may be the same type of processor, such as one or more CPUs; but may also be different types of processors such as one or more CPUs and one or more ASICs.
Memory 806 for storing a program 810. The memory 806 may include high-speed RAM memory or may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
Program 810 may be specifically invoked by processor 802 to cause the SAE gateway to:
when receiving the detection message sent by the DNS server, returning a response message to the DNS server through a Gn-DNS interface; or, sending SAE gateway status information to the DNS server through the Gn-DNS interface.
Through the SAE gateway, the system can communicate with the DNS server through the Gn-DNS interface, and the DNS server analyzes the domain name according to the state of the SAE gateway, so that the problem of analyzing the domain name to a fault SAE gateway is avoided, and the domain name analysis efficiency of the system is greatly improved.
An embodiment of the present invention provides a computer readable storage medium storing at least one executable instruction that, when executed on an SAE gateway fault handling system, causes the SAE gateway fault handling system to perform the SAE gateway fault handling method in any of the method embodiments 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 is callable by a processor to cause an SAE gateway fault handling system to perform the SAE gateway fault handling method in any of the method embodiments described above.
An embodiment of the present invention provides a computer program product, which comprises 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 SAE gateway fault handling method in any of the method embodiments described above.
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 a construction of such a system is apparent from the description above. In addition, embodiments of the present invention are not directed to any particular programming language. It will be appreciated that the teachings of the present invention described herein may be implemented in a variety of programming languages, and the above description of specific languages is provided for disclosure of enablement and best mode of the present invention.
In the description provided herein, numerous specific details are set forth. However, it is understood 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 above 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 disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be construed as reflecting the intention that: i.e., the claimed invention 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 apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. 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. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units 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 but not others included in other embodiments, 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 can 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 use of the words first, second, third, etc. do not denote any order. These words may be interpreted as names. The steps in the above embodiments should not be construed as limiting the order of execution unless specifically stated.
Claims (6)
1. An SAE gateway fault handling method, wherein a DNS server establishes a communication connection with the SAE gateway through a Gn-DNS interface, comprising:
The DNS server circularly sends a detection message to the SAE gateway in a detection period T1 through the Gn-DNS interface;
the DNS server receives SAE gateway state information sent by the SAE gateway in a monitoring period T2 through the Gn-DNS interface;
if the DNS server receives the response message of the SAE gateway or the SAE gateway state information is in a normal state, determining that the SAE gateway is normal, otherwise, determining that the SAE gateway is faulty, including: if the number of times of not receiving the response message of the SAE gateway is larger than a first threshold value, determining that the SAE gateway fails; and if the number of times of continuously receiving that the SAE gateway state is in the fault state is larger than a third threshold value, the DNS server determines that the SAE gateway fails.
2. The SAE gateway fault handling method of claim 1, wherein the determining the SAE gateway fault further comprises isolating a faulty SAE gateway;
the SAE gateway with the fault isolation comprises:
the DNS server acquires the analysis record of the faulty SAE gateway and deletes the analysis record of the faulty SAE gateway;
or alternatively, the first and second heat exchangers may be,
the DNS server reduces the priority of resolution records for the failed SAE gateway.
3. The SAE gateway fault handling method as recited in claim 2, wherein after isolating the failed SAE gateway, further comprising:
the DNS server circularly sends a detection message to the isolated SAE gateway in a detection period T1, and if all response messages of the isolated SAE gateway are received, the isolated SAE gateway is isolated;
the de-isolating the isolated SAE gateway comprises:
the DNS server adds a resolution record of the isolated SAE gateway;
or alternatively, the first and second heat exchangers may be,
the DNS server increases the resolution record priority of the isolated SAE gateway.
4. The SAE gateway fault handling method of claim 1 wherein the DNS server determines that the SAE gateway is faulty, further comprising isolating the faulty SAE gateway;
the SAE gateway with the fault isolation comprises:
the DNS server acquires the analysis record of the faulty SAE gateway and deletes the analysis record of the faulty SAE gateway;
or alternatively, the first and second heat exchangers may be,
the DNS server reduces the priority of resolution records for the failed SAE gateway.
5. The SAE gateway fault handling method as set forth in claim 4, wherein after isolating the faulty SAE gateway, further comprising:
The DNS server receives the SAE gateway state information circularly sent by all the isolated SAE gateways in the monitoring period T2 and de-isolates the isolated SAE gateways;
the de-isolating the isolated SAE gateway comprises:
the DNS server adds a resolution record of the isolated SAE gateway;
or alternatively, the first and second heat exchangers may be,
the DNS server increases the resolution record priority of the isolated SAE gateway.
6. An SAE gateway fault handling system, comprising a DNS server and an SAE gateway, wherein the DNS server establishes a communication connection with the SAE gateway via a Gn-DNS interface;
the DNS server is used for sending a detection message to the SAE gateway in a detection period T1 through the Gn-DNS interface;
the SAE gateway is used for sending a response message to the DNS server when receiving the detection message sent by the DNS server;
the SAE gateway is further used for sending the state information of the SAE gateway to the DNS server in a monitoring period T2;
when receiving the response message of the SAE gateway or the SAE gateway state information is in a normal state, the DNS server determines that the SAE gateway is normal, otherwise, determines that the SAE gateway is faulty, including: if the number of times that the DNS server does not receive the response message of the SAE gateway is larger than a first threshold value, determining that the SAE gateway fails; and if the number of times that the DNS continuously receives that the SAE gateway state is the fault state is greater than a third threshold value, the DNS server determines that the SAE gateway fails.
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 CN113497727A (en) | 2021-10-12 |
| CN113497727B true 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 (12)
| 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 |
| 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 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8634346B2 (en) * | 2009-10-27 | 2014-01-21 | Cisco Technology, Inc. | Dynamic gateway selection process |
-
2020
- 2020-04-01 CN CN202010251202.9A patent/CN113497727B/en active Active
Patent Citations (12)
| 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 |
| 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.2009,全文. * |
| NTT DOCOMO. "C4-090068-Discussion on PDN Gateway Identity".3GPP tsg_ct\WG4_protocollars_ex-CN4.2009,全文. * |
| 浅谈EPC核心网络的故障应急;张宗峰;;数码世界(第10期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113497727A (en) | 2021-10-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107276811B (en) | Method, related device and system for realizing terminal called service recovery | |
| US10567216B2 (en) | Fault detection method, gateway, user equipment, and communications system | |
| EP2648466B1 (en) | Method and apparatus for selecting service gateway entity | |
| CN103152374B (en) | Know the method and apparatus of terminal presence | |
| EP3544232B1 (en) | Processing method, device and system for nf component abnormality | |
| WO2011083151A1 (en) | Emergency radio connection setup | |
| US20120124413A1 (en) | Method and system for network element service recovery | |
| KR20130130839A (en) | System and method for session resiliancy at geo-redundant gateways | |
| CN108011737A (en) | A kind of failure switching method, apparatus and system | |
| CN103581351B (en) | The method and apparatus of network access | |
| EP3253090A1 (en) | Service disaster recovery method and related device | |
| CN112423331B (en) | Fault diagnosis method and device | |
| CN107872326B (en) | Method, device and system for releasing session resources | |
| WO2018166328A1 (en) | Information processing method, apparatus, computer readable storage medium and electronic device | |
| CN105814934B (en) | Handle method, mobile management entity and the home subscriber server of called service | |
| US9049562B2 (en) | HSS fault recovery for non-3GPP access | |
| CN106656659A (en) | Network path selection method and network video recorder (NVR) | |
| JP6544835B2 (en) | Message processing method and apparatus | |
| CN103051484B (en) | Session service processing method, system and Session Border Controll | |
| CN113497727B (en) | SAE gateway fault processing method and system | |
| JP2018523381A (en) | Method and system for recovering communication state in which SGW has failed, MME, SGW | |
| US10225191B2 (en) | Service packet distribution method and apparatus | |
| EP3736696A1 (en) | Early gx/rx session failure detection and response | |
| CN114697191A (en) | Resource migration method, device, equipment and storage medium | |
| CN111092966A (en) | Domain name system, domain name access 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 |