WO2018119559A1 - 一种通信接口故障的处理方法和装置 - Google Patents

一种通信接口故障的处理方法和装置 Download PDF

Info

Publication number
WO2018119559A1
WO2018119559A1 PCT/CN2016/112046 CN2016112046W WO2018119559A1 WO 2018119559 A1 WO2018119559 A1 WO 2018119559A1 CN 2016112046 W CN2016112046 W CN 2016112046W WO 2018119559 A1 WO2018119559 A1 WO 2018119559A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication interface
network device
preset
link
message
Prior art date
Application number
PCT/CN2016/112046
Other languages
English (en)
French (fr)
Inventor
张志龙
龚晓东
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2016/112046 priority Critical patent/WO2018119559A1/zh
Priority to CN201680091484.2A priority patent/CN110050478A/zh
Publication of WO2018119559A1 publication Critical patent/WO2018119559A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • the present application relates to the field of communications and, more particularly, to a method and apparatus for handling communication interface failures.
  • 3GPP Third Generation Partnership Project
  • eNB base station
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • the S1 control plane interface is located between the eNB and the MME, and the transport network layer is transmitted by using an Internet Protocol (IP), and a flow is added to the IP layer in order to reliably transmit signaling messages.
  • IP Internet Protocol
  • SCTP Streaming Control Transmission Protocol
  • S1AP S1 Application Protocol
  • the S1 interface status of the eNB and the MME is inconsistent due to the software problem of the peer network element (for example, the MME) and the anti-flash parameters of the SCTP link at both ends are different, especially when the MME side is flashed and the eNB side is normal. In this case, the MME cannot initiate the reestablishment of the S1 interface, which may cause the communication of the S1 interface to be interrupted.
  • the peer network element for example, the MME
  • the anti-flash parameters of the SCTP link at both ends are different, especially when the MME side is flashed and the eNB side is normal.
  • the MME cannot initiate the reestablishment of the S1 interface, which may cause the communication of the S1 interface to be interrupted.
  • the present application provides a method and device for processing a communication interface failure, and an abnormality of the time-aware interface to improve interface reliability.
  • a method for processing a communication interface failure is provided, the method being applied to a communication system including a first network device and a second network device, the first network device and the second network
  • the network devices are communicatively coupled by a first communication interface, the first communication interface including at least a transport layer link and an application layer link configured between the first network device and the second network device,
  • Methods include:
  • the first network device releases the transport layer link to trigger the reconstruction of the application layer link when determining that the success rate of the service transmitted by the first communication interface of the local end meets the preset condition.
  • the application layer link and the transport layer link share a transport layer and a protocol entity of each layer below the transport layer.
  • the success rate of the service transmitted through the first communication interface is monitored by the first network device, and when an abnormality occurs at the opposite end, the abnormality of the interface can be sensed in time, and the upper link is triggered to release the upper link.
  • Reconstruction enables the communication interface to resume normal communication, thereby improving interface reliability and improving the reliability of the communication system.
  • the preset condition includes: a quantity and a pass of a first message sent by using the first communications interface in a first preset time period The total number of second messages received by the first communication interface is less than a preset first threshold; and,
  • Determining, by the first network device, whether a success rate of the service transmitted by the first communication interface of the local end meets a preset condition including:
  • the preset condition includes: sending, by using the first communication interface, the number of second messages that are received by using the first communications interface The ratio of the number of first messages is less than a preset second threshold, and,
  • Determining, by the first network device, whether a success rate of the service transmitted by the first communication interface of the local end meets a preset condition including:
  • the second message is a message that is sent by the second network device based on the first message. Therefore, the accuracy of the judgment can be improved.
  • the first network device determines, in the second preset time period, the number of the second message received through the first communication interface and the first message sent by using the first communication interface
  • the method further includes: before whether the ratio of the number is less than a preset second threshold, the method further includes:
  • the first network device determines that a success rate of the service transmitted by the first communication interface of the local end meets the Release the transport layer link when the condition is preset, including:
  • the first network device releases the transport layer link when it is determined that the transport layer link state is normal.
  • a communication device failure processing apparatus for performing the method of the first aspect and any possible implementation of the first aspect.
  • the processing means may comprise means for performing the method of the first aspect and any possible implementation of the first aspect.
  • a processing device for communication interface failure comprising a memory and a processor for storing a computer program, the processor for calling and running the computer program from the memory, such that the communication interface is faulty
  • the processing device performs the method of the first aspect above and any possible implementation of the first aspect.
  • a computer program product comprising: computer program code, when the computer program code is processed by a processing unit, a transceiver unit or a processor, a transceiver of a first device in the first aspect
  • the first device is caused to perform the method of the first aspect and any possible implementation of the first aspect.
  • a fifth aspect a computer readable storage medium for storing a computer program, the computer program comprising: in any of the possible implementations of the first aspect and the first aspect Method of instruction.
  • the first communication interface is an S1 interface
  • the first network device is an access network device
  • the second network device is a core network device
  • the first message includes: an initial UE message, and the second message includes an initial context setup request message.
  • the first communication interface is an S1 interface
  • the first network device is a core network device
  • the second network device is an access network device
  • the first message includes: an E-RAB setup request message
  • the second message includes: an E-RAB setup response message
  • the first message includes an E-RAB modification request message
  • the second message includes an E-RAB modification response message.
  • the first communication interface is an S1 interface
  • the transport layer link is an SCTP link
  • the application layer link is an S1AP link.
  • the first communication interface is an X2 interface
  • the first network device is a first access network device
  • the second network device is a second access network device
  • the first message includes a Handover Request message
  • the second message includes a Handover Request acknowledge message.
  • the first communication interface is an X2 interface
  • the transport layer link is an SCTP link
  • the application layer link is an X2AP link.
  • the first network device monitors the service success rate of the local end, and in the case of an abnormality at the opposite end, the abnormality of the interface can be sensed in time, and the communication interface is reconstructed, thereby It can improve the reliability of the interface and improve the reliability of the communication system.
  • FIG. 1 shows a schematic diagram of a protocol stack of an MME and an eNB.
  • FIG. 2 shows a schematic flow chart of S1AP link setup.
  • FIG. 3 is a schematic flowchart of a method for processing a communication interface failure according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram showing a method of processing a communication interface failure according to another embodiment of the present application. flow chart.
  • FIG. 5 is a schematic flowchart of a method for processing a communication interface failure according to still another embodiment of the present application.
  • FIG. 6 shows a schematic block diagram of a processing device for a communication interface failure in accordance with an embodiment of the present application.
  • FIG. 7 shows a schematic block diagram of a processing device for a communication interface failure in accordance with an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Longterm evolution
  • LTE-A Advanced long term evolution
  • UMTS Universal Mobile Telecommunication System
  • 5G fifth-generation
  • E-UTRAN Evolved UMTS Terrestrial Radio Access Network
  • FIG. 1 shows a schematic diagram of a protocol stack of an MME and an eNB. It can be seen from FIG. 1 that in the current LTE network, the user signaling transmission between the MME device and the eNB device uses the S1-AP protocol, which guarantees the transmission of user signaling, and the transport layer protocol uses SCTP protocol.
  • the MME and the eNB communicate normally, it is necessary to ensure that the links of the layers shown in FIG. 1 are in a normal state. For example, if the SCTP link is abnormal, the MME and the eNB cannot communicate normally. If the SCTP link is normal and the S1AP link is abnormal, the MME and the eNB cannot communicate normally.
  • the S1 interface includes links formed by peer-to-peer protocol entities, such as at least: an SCTP link, an S1AP link, and the like.
  • the user signaling transmission uses the X2-AP protocol
  • the transport layer protocol uses the SCTP protocol.
  • the X2 interface includes links formed by peer-to-peer protocol entities, such as at least: an SCTP link, an X2AP link, and the like.
  • the S1AP link may be abnormal in the following situations:
  • any one of the above three situations may cause normal communication between the MME and the eNB.
  • the eNB side may trigger the S1AP setup process when the SCTP link is abnormal. If the eNB side cannot send the message to the MME, the eNB may actively release the SCTP link to notify the peer. If the MME link is abnormal, the MME releases the S1AP link, and then the eNB actively initiates the S1AP Setup procedure. If the situation a occurs, the eNB side may send a message to the MME, and the MME does not perform any processing due to its own abnormality, and the eNB does not Knowing the MME side failure, it will not initiate the S1 Setup process. Therefore, the embodiment of the present application is directed to the scenario, and a method for processing a communication interface failure is proposed.
  • FIG. Figure 2 shows a schematic flow diagram of S1 setup from the perspective of device interaction.
  • the S1 establishment process specifically includes the following steps:
  • the eNB sends an SCTP link initialization (SCTP Init) message to the MME.
  • SCTP Init SCTP link initialization
  • the MME sends an SCTP Link Initialization Response (SCTP Init Ack) message to the eNB, where the SCTP Init Ack message carries a cache (Cookie);
  • SCTP Init Ack SCTP Link Initialization Response
  • the eNB sends an SCTP Cookie Echo message to the MME.
  • the MME sends an SCTP Cookie Echo Ack message to the eNB.
  • the SCTP link establishment (Established) is completed;
  • the eNB sends an S1 setup (S1Setup) message to the MME.
  • the MME sends an S1 Setup Response (S1Setup Response) message to the eNB.
  • S1Setup Response S1 Setup Response
  • the foregoing steps 201 to 204 are processes for establishing an SCTP link.
  • the S1AP link is further established through steps 205 and 206.
  • the release of the S1AP link can be understood as the release of the link information of the S1AP layer and its lower layer (for example, including the SCTP layer, the IP layer, and the like, specifically referring to FIG. 1).
  • Establishing an S1AP link can be understood as establishing all the links between the S1AP layer and its lower layers. In other words, the S1AP link and the SCTP link share the protocol entities of the SCTP layer and its underlying layers.
  • the reestablishment of the S1AP link can only be initiated by the eNB. That is to say, in the case a, if the MME is abnormal and the eNB is unknown, the eNB does not actively initiate the S1AP link reestablishment. Therefore, it is required to provide a method for triggering an eNB to actively initiate an S1AP link reestablishment in case of an MME abnormality.
  • FIG. 3 to 5 are schematic flow charts showing a method of processing a communication interface failure according to an embodiment of the present application. It should be understood that FIG. 3 to FIG. 5 show the communication steps or operations of the processing method for the communication interface failure in the embodiment of the present application, but the steps or operations are only examples, and the other embodiments of the present application may perform other operations or Deformation of various operations. In addition, the various steps in the figures may be performed in a different order than that presented in the figures, and it is not possible to perform all of the operations in the figures.
  • each step in the processing method for the communication interface failure shown in each figure may be performed by the first network device.
  • the first network device is the S1 interface
  • the first network device and the second The network device is connected by using an S1 interface
  • the first network device may be an access network device
  • the second network device may be a core network device
  • the transport layer link may be an SCTP link
  • the application layer link may be an S1AP link.
  • the first network device may be a core network device
  • the second network device may be an access network device
  • the transport layer link may be an SCTP link
  • the application layer link may be An S1AP link (in the second case, corresponding to FIG.
  • the first communication interface is an X2 interface
  • the first network device and the second network device are communicatively connected through an X2 interface
  • the first network device and the second network The device may be an access network device
  • the transport layer link may be an SCTP link
  • the application layer link may be an X2AP link (case 3, corresponding to FIG. 5).
  • an SCTP link can be understood as a link that provides stable and orderly data transmission services between two endpoints (eg, MME and eNB, or first eNB and second eNB). It is a reliable data messaging protocol based on protocols (eg, IP) that provide unreliable transport services. It is used to provide reliable connection-oriented datagram transmission.
  • the endpoint is the basic logical concept of SCTP. It is the logical sender and receiver of data packets and is a typical logical entity.
  • the sending end may be an MME
  • the receiving end may be an eNB.
  • the sending end MME the local end is its own, the opposite end is an eNB, and the receiving end eNB is itself On its own, the peer is the MME.
  • An SCTP endpoint is identified by a set of transport addresses with the same SCTP port number, and the SCTP protocol specifies that only one connection can be established between two endpoints. Therefore, an SCTP endpoint may have multiple transport addresses, but these transport addresses have unique port numbers.
  • the access network device may be an Access Point (AP) in a Wireless Local Area Networks (WLAN), and a Base Transceiver in GSM or CDMA.
  • BTS Base Transceiver
  • AP Access Point
  • WLAN Wireless Local Area Networks
  • BTS Base Transceiver
  • NB base station
  • eNode B Evolutionary Node B
  • gNB gNode B
  • 5G network a network device in a future public network mobile network
  • PLMN Public Land Mobile Network
  • the core network device may be an MME
  • the MME is a control plane network element, and is mainly responsible for control plane functions such as mobility management and session management of the user equipment.
  • FIG. 3 is a schematic flowchart of a method 300 for processing a communication interface failure according to an embodiment of the present application.
  • the first network device may be an eNB
  • the second network device may be an MME.
  • the examples are merely examples and should not be construed as limiting the application.
  • the method 300 includes:
  • the eNB determines whether a success rate of the service transmitted through the S1 interface meets a preset condition.
  • the success rate of the service transmitted through the S1 interface can be understood as an indicator for indicating normal communication through the S1 interface.
  • the communication link since the communication link involves a service level, it may be referred to as a service success rate, or may also be referred to as a communication success rate, a message response rate, and the like.
  • Ben The application is not specifically limited. Specifically, when the link is in a normal communication state, the interaction between the local end and the opposite end is normal, and the probability of failure such as communication interruption and service loss is small, that is, the success rate is high; when the link is in an abnormal state, The abnormal interaction between the local end and the peer end may cause a large number of failures such as communication interruption and service loss, that is, the success rate is low.
  • the service success rate may be determined by monitoring whether certain messages sent by the eNB are responded. For example, in the user equipment (User Equipment (“UE") boot attach process, or in the Tracking Area Update (TAU) process, or the active network initiated paging (Paging) In the process, the eNB may send an Initial UE message to the MME. If the link is normal, the MME may send an Initial context setup request message to the eNB.
  • UE User Equipment
  • TAU Tracking Area Update
  • Paging active network initiated paging
  • a message sent by the first network device is recorded as a first message
  • the second network device eg, MME
  • the message sent is recorded as the second message.
  • S310 may specifically include:
  • the eNB may preset a time period (recorded as a first preset time period for convenience of distinction and description), and monitor the total number of messages sent and received through the S1 interface during the first preset time period.
  • the first preset time period may be from 8:00 to 20:00.
  • the success rate of the service transmitted by the eNB through the S1 interface is determined to meet a preset condition, and then the status is abnormal.
  • the traffic volume is different because the area covered by the eNB is different.
  • the traffic volume between the mountain and the city is very different. Therefore, the corresponding first threshold may also be different.
  • the first threshold corresponding to the eNB covering the mountain area may be small, and the first threshold corresponding to the eNB covering the city may be large.
  • S310 may specifically include:
  • the eNB determines whether the ratio of the number of second messages received through the S1 interface to the number of first messages sent through the S1 interface in the second preset time period is less than a preset second threshold.
  • the eNB may preset a time period (recorded as a second preset time period for convenience of distinction and description), and monitor the number of second messages received by the eNB through the S1 interface in the second preset time period.
  • the ratio of the number of sent first messages, if the second preset time period is monitored The ratio of the number of the second message received by the eNB to the number of the first message sent by the eNB is less than a preset second threshold, and determines that the success rate of the service transmitted by the eNB through the S1 interface meets a preset condition, and then determines The status is abnormal.
  • the ratio is also related to the traffic volume of the eNB to some extent, that is, related to the area covered by the eNB.
  • the S1 interface of the local end is abnormal according to the total number of the first message sent by the eNB through the S1 interface and the second message received through the S1 interface.
  • the method further include:
  • the eNB determines that the total number of the first message sent through the S1 interface and the second message received through the S1 interface in the second preset time period is greater than or equal to a preset third threshold.
  • the preset third threshold can be understood as a sample size, that is, when the eNB determines that the number of messages sent and received through the S1 interface meets the threshold of the sample size within the second preset time period, the second message received is further determined. Whether the ratio of the number of first messages sent is less than a preset second threshold. For example, when the eNB determines that the number of messages sent and received through the S1 interface meets the threshold of the sample size (for example, 100 messages) in the second preset period, it is further determined whether the S1 interface is only in the second preset period. 100 messages were sent without receiving any messages, or the number of messages sent was much larger than the number of messages received. That is to monitor whether the S1 interface is "only going out”.
  • the preset third threshold is also related to the traffic volume of the eNB.
  • the first preset time period and the second preset time period listed in the foregoing are only distinguishing two different determination methods, and the first preset time period and the second preset time period may be the same or different durations.
  • the application is not particularly limited thereto.
  • the two methods for determining whether the service success rate satisfies the preset condition may be used in combination.
  • the preset first threshold and the preset The third threshold is the same. That is, it is first determined whether the number of messages sent and received through the S1 interface in the first preset time period is greater than or equal to a preset first threshold.
  • determining that the S1 interface of the eNB is abnormal; if yes, determining whether the ratio of the number of the second messages received through the S1 interface to the number of the first messages sent is greater than The preset second threshold, if not, determines that the S1 interface on the eNB side is abnormal, and if so, determines that the S1 interface on the eNB side is normal, and does not need to be processed temporarily.
  • the MME may reply or not reply. If all the first messages in the collected samples do not need to be returned by the MME, even if it is detected that the number of the first message sent by the eNB is all of the samples, and the number of the second messages is zero, it is not necessarily It can be determined that the S1 interface on the eNB side is abnormal.
  • the eNB may further improve the accuracy of the judgment, and may pre-define the second message that the monitored first message includes at least a part of the peers must reply. That is, if the eNB sends the first message to the MME through the S1 interface, the MME must reply to the eNB with the second message if the communication is normal. In this way, the service success rate can be more accurately determined according to whether the MME replies to the second message for the received first message. In this case, the success rate of the service can be understood as the message response rate.
  • the first message may be an initial UE message
  • the second message is an initial context setup request message
  • the eNB can determine that the local S1 interface is faulty.
  • the eNB releases the SCTP link (that is, an example of a transport layer link) when determining that the success rate of the service transmitted through the S1 interface meets a preset condition.
  • the eNB After determining that the local S1 interface is faulty, the eNB needs to reestablish the S1 interface. However, since the MME does not know that the S1 interface on the eNB side is faulty, the S1 interface is normal to the MME. Therefore, the eNB can notify the MME S1 interface of the opposite end of the fault by releasing the SCTP link. After the eNB releases the SCTP link, the peer (ie, the MME) can release the S1AP link by using a handshake mechanism between the SCTP entities. Specifically, the eNB releases the SCTP link, which can be understood as releasing the SCTP link information and the entity.
  • the information of the SCTP link includes: the IP address of the local end and the peer end, the port number of the local end and the opposite end, the entity number (or the instance number) of the SCTP layer and the following layers, and the link number.
  • the MME releases the S1AP link, which can be understood as whether the S1AP link information and the entity.
  • the S1AP link information includes: an entity number (or an instance number) of the S1AP layer and the following layers.
  • S320 may specifically include:
  • the eNB determines whether the SCTP link is normal
  • the eNB releases the SCTP link when it determines that the SCTP link is normal.
  • the eNB Since the eNB determines that the S1 interface is faulty, it is not determined that only the S1AP layer link is faulty, or the SCTP layer link is faulty, or even the lower layer link is faulty. Therefore, the eNB can determine whether the SCTP layer link is normal before reconstructing the S1 link. If the link of the SCTP layer is normal, the link from the SCTP layer is normal, and only the link of the S1AP layer is abnormal. If the SCTP link is abnormal, you need to further determine the cause of the abnormal link in the SCTP layer.
  • the eNB can directly initiate the reconstruction of the S1 link. If the link of the SCTP layer is abnormal, the eNB can detect and repair the SCTP link by using the prior art. The S1 interface is abnormal, and the S1AP link can be reconstructed by using the communication interface failure processing method of the embodiment of the present application.
  • the eNB reestablishes an S1AP link (that is, an example of an application layer link).
  • the process of the eNB re-establishing the S1AP link includes the process of reestablishing the SCTP link.
  • the specific process of the eNB re-establishing the S1AP link has been described above in detail with reference to FIG. 2, and is not described herein for brevity.
  • the eNB can monitor the S1 interface of the local end in real time.
  • the foregoing method 300 can be performed to repair the S1 interface, so that the communication can quickly return to normal.
  • the method for processing a communication interface fault in the embodiment of the present application determines the success rate of the service transmitted through the S1 interface by using the eNB, and actively initiates the reconstruction of the S1 link if the preset condition is met. Therefore, in the case that an abnormality occurs on the MME side, the link fault is detected in time, and the link repair is performed in a timely manner, thereby improving the self-healing capability of the S1 interface and avoiding the service success rate caused by the inconsistent interface status of the two ends. The problem of falling has improved the reliability of the S1 interface.
  • FIG. 4 shows a schematic flow chart of a method 400 of processing a communication interface failure in accordance with another embodiment of the present application.
  • the first network device may be an MME
  • the second The network device may be an eNB
  • the transport layer link may be an SCTP link
  • the application layer link may be an S1AP link.
  • the examples are merely examples and should not be construed as limiting the application.
  • the method 400 includes:
  • the MME determines whether a success rate of the service transmitted through the S1 interface meets a preset condition.
  • the service success rate may be determined by monitoring, by the MME, whether some of the messages sent are responsive. For example, in the process of establishing a bearer by the MME, the MME may send a bearer setup/modification request to the eNB. If the link is normal, the eNB may send a bearer setup/modification response to the MME.
  • S410 may specifically include:
  • S410 may specifically include:
  • the MME determines whether the ratio of the number of second messages received through the S1 interface to the number of first messages sent through the S1 interface in the second preset time period is less than a preset second threshold.
  • the method further include:
  • the MME determines that the total number of the first message sent through the S1 interface and the second message received through the S1 interface in the second preset time period is greater than or equal to a preset third threshold.
  • the second message is a response message that is sent by the eNB based on the first message sent by the MME.
  • the first message may be an Evolved Radio Access Bearer (E-RAB) setup request (E-RAB setup request) message
  • the second message may be a E-RAB setup response (E- RAB setup response) message
  • the first message may include an E-RAB modification request message
  • the second message may include an E-RAB modification response message
  • the MME releases the SCTP link (that is, another instance of the transport layer link) when determining that the success rate of the service transmitted through the S1 interface meets a preset condition.
  • S420 specifically includes:
  • the MME determines whether the SCTP link is normal.
  • the MME releases the SCTP link when it determines that the SCTP link is normal.
  • the eNB is triggered to re-establish the S1AP link (ie, another instance of the application layer link).
  • the method for processing a communication interface failure in the embodiment of the present application determines the success rate of the service transmitted through the S1 interface by using the MME, and actively initiates the reconstruction of the S1 link if the preset condition is met. Therefore, in the case that an abnormality occurs on the eNB side, the link fault is detected in time, and the eNB is quickly triggered to perform link repair, thereby improving the self-healing capability of the S1 interface and avoiding the service caused by the inconsistent interface status of the two ends.
  • the problem of a drop in success rate has improved the reliability of the S1 interface.
  • first communication interface is the S1 interface
  • first communication interface is the X2 interface
  • FIG. 5 shows a schematic flowchart of a method 500 for processing a communication interface failure according to still another embodiment of the present application.
  • the first network device may be a first eNB
  • the second network device may be a second eNB
  • the transport layer link may be an SCTP link
  • the application layer link may be an X2AP link.
  • the examples are merely examples and should not be construed as limiting the application.
  • the first eNB and the second eNB are two peers, and the S1 interface is abnormal at any one of the first eNB and the second eNB, and the communication interface fault processing method in the embodiment of the present application can be used. Detection and repair.
  • FIG. 5 is only described by taking the case where the first eNB end detects the abnormality of the second eNB end as an example.
  • the action performed by the second eNB is shown in FIG. 5 .
  • the steps are the same and will not be described here.
  • the method 500 includes:
  • the first eNB determines that a success rate of the service transmitted through the S1 interface meets a preset condition.
  • the service success rate may be determined by the first eNB monitoring whether certain messages sent are responded.
  • the first eNB may be understood as a source base station
  • the second eNB may be understood as a target base station
  • the first eNB may send a handover request to the second eNB.
  • the second eNB may send a handover request response to the first eNB.
  • S510 may specifically include:
  • the total number of the first message sent by the eNB through the X2 interface and the second message received through the X2 interface in the first preset time period is less than a preset first threshold.
  • the S510 may include: determining, by the first eNB, that the ratio of the number of the second message received through the X2 interface to the number of the first message sent by using the X2 interface is less than the preset second. Threshold.
  • the method also includes:
  • the first eNB determines that the total number of the first message sent through the X2 interface and the second message received through the X2 interface in the second preset time period is greater than or equal to a preset third threshold.
  • the second message is a response message that is sent by the second eNB based on the first message sent by the first eNB.
  • the first message may include a handover request (Handover request) message
  • the second message may include a handover request acknowledge message.
  • the first eNB releases the SCTP link (ie, another example of the transport layer link) when determining that the success rate of the service transmitted through the S1 interface meets a preset condition.
  • S520 may specifically include:
  • the first eNB determines that the SCTP link is normal
  • the first eNB releases the SCTP link when it determines that the SCTP link is normal.
  • the first eNB reestablishes an S1AP link (ie, another example of an application layer link).
  • the method for processing a communication interface failure in the embodiment of the present application determines the success rate of the service transmitted through the X2 interface by using the first eNB, and actively initiates the reconstruction of the X2 link if the preset condition is met. Therefore, in the case that an abnormality occurs on the second eNB side, the link fault is detected in time, and the link repair is performed quickly, thereby improving the self-healing capability of the X2 interface and avoiding the service caused by the inconsistent interface status of the two ends.
  • the problem of a drop in success rate has improved the reliability of the X2 interface.
  • the specific contents of the first message and the second message listed above are merely exemplary descriptions, and should not be construed as limiting the application.
  • the first message and the second information for determining whether the service success rate satisfies the preset condition Messages can be the same message or different messages, respectively.
  • the first message may be a different message, and the second message as a response to the first message may also be different.
  • FIG. 6 shows a schematic block diagram of a processing device 10 for communication interface failure in an embodiment of the present application.
  • the apparatus 10 includes a determining unit 11 and a processing unit 12.
  • the device 10 may correspond to (for example, may be configured or be itself) the first network device described in the foregoing method 300 to method 500, and each module or unit in the device 10 is used to perform the above method 200, respectively.
  • the details of the operations or processes performed by the transmitting device are omitted here.
  • FIG. 7 shows a schematic block diagram of a processing device 20 for a communication interface failure in accordance with an embodiment of the present application.
  • the device 20 includes a transceiver 21, a processor 22, and a memory 23.
  • the transceiver 21, the processor 22 and the memory 23 communicate with each other through an internal connection path to transfer control and/or data signals.
  • the device 20 may correspond to (for example, may be configured or itself) the first network device described in the foregoing method 300 to method 500.
  • the processor 22 can be used to perform the method of the embodiment shown in Figures 3, 4 or 5 and to implement the functionality of the embodiment of the device 20 shown in Figures 3, 4 or 5.
  • the embodiments of the present application may be applied to a processor or implemented by a processor.
  • the processor can be an integrated circuit chip with signal processing capabilities.
  • each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the processor may be a central processing unit ("CPU"), and may be other general-purpose processors, digital signal processors ("DSP"), and application-specific integrated circuits ( Application Specific Integrated Circuit (“ASIC”), Field Programmable Gate Array (“FPGA”) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software in the decoding processor.
  • Software device It is located in a storage medium mature in the field of random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (Read-Only Memory (ROM), a programmable read only memory (PROM), or an erasable programmable read only memory (Erasable PROM). , referred to as "EPROM”), electrically erasable programmable read only memory (“EEPROM”) or flash memory.
  • the volatile memory may be a Random Access Memory (“RAM”), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM Enhanced SDRAM
  • DR RAM direct memory bus random access memory
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
  • the implementation process constitutes any limitation.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the steps of the method for processing a communication interface failure disclosed in the embodiment of the present application may be directly implemented as completion of the hardware processor, or may be performed by a combination of hardware and software in the processor.
  • the software can be located in a random storage medium, such as a flash memory, a read only memory, a programmable read only memory or an electrically erasable programmable memory, a register, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种通信接口故障的处理方法和装置，能够提高接口可靠性。该方法应用于包括第一网络设备和第二网络设备的通信***中，该第一网络设备与该第二网络设备之间通过第一通信接口通信连接，该第一通信接口至少包括配置于该第一网络设备和该第二网络设备之间的传输层链路和应用层链路，该方法包括：该第一网络设备确定通过第一通信接口传输的业务的成功率是否满足预设条件；该第一网络设备在确定通过本端的第一通信接口传输的业务的成功率满足该预设条件时，释放该传输层链路，以触发该应用层链路的重建。

Description

一种通信接口故障的处理方法和装置 技术领域
本申请涉及通信领域，并且更具体地，涉及一种通信接口故障的处理方法和装置。
背景技术
第三代合作伙伴项目(3rd Generation Partnership Project，简称“3GPP”)长期演进(Long Term Evolution，简称“LTE”)中，接入网设备(例如，基站(eNode B，简称“eNB”))与核心网设备(例如，移动性管理实体(Mobility Management Entity，简称“MME”)、服务网关(Serving Gateway，简称“SGW”))之间通过S1接口通信连接，接入网设备之间通过X2接口通信连接。因此，接口的可靠性直接影响着通信的可靠性。
以S1接口为例，S1控制面接口位于eNB和MME之间，传输网络层是利用网际协议(Internet Protocol，简称“IP”)传输，为了可靠地传输信令消息，在IP层上添加了流控制传输协议(Streaming Control Transmission Protocol，简称“SCTP”)，应用层的信令协议为S1应用层协议(S1-Application Protocol，简称“S1AP”)。
但是，由于对端网元(例如，MME)软件问题、两端SCTP链路防闪参数不同等原因造成eNB和MME两端的S1接口状态不一致时，尤其是在MME侧闪断而eNB侧正常的情况下，MME不能主动发起S1接口的重建，进而可能导致S1接口通信中断。
因此，需要提供一种技术，能够在两端的接口状态不一致时，及时地感知到接口的异常，并能够快速地修复通信接口，提高接口可靠性，进而提高通信可靠性。
发明内容
本申请提供一种通信接口故障的处理方法和装置，以及时感知接口的异常，提高接口可靠性。
一方面，提供了一种通信接口故障的处理方法，所述方法应用于包括第一网络设备和第二网络设备的通信***中，所述第一网络设备与所述第二网 络设备之间通过第一通信接口通信连接，所述第一通信接口至少包括配置于所述第一网络设备和所述第二网络设备之间的传输层链路和应用层链路，所述方法包括：
所述第一网络设备确定通过第一通信接口传输的业务的成功率是否满足预设条件；
所述第一网络设备在确定通过本端的第一通信接口传输的业务的成功率满足所述预设条件时，释放所述传输层链路，以触发所述应用层链路的重建。
其中，应用层链路和传输层链路共用传输层及所述传输层以下各层的协议实体。
因此，通过第一网络设备监控通过第一通信接口传输的业务的成功率，在对端出现异常的情况下，能及时地感知到接口的异常，并通过释放下层链路以触发上层链路的重建，使通信接口恢复正常通信，从而能够提高接口可靠性，提高通信***的可靠性。
结合第一方面，在第一方面的第一种可能的实现方式中，所述预设条件包括：在第一预设时段内通过所述第一通信接口发送的第一消息的数量和通过所述第一通信接口接收到的第二消息的总数量小于预设的第一门限；以及，
所述第一网络设备确定通过本端的第一通信接口传输的业务的成功率是否满足预设条件，包括：
所述第一网络设备确定在第一预设时段内通过所述第一通信接口发送的所述第一消息和通过所述第一通信接口接收到的所述第二消息的总数量是否小于所述预设的第一门限。
结合第一方面，在第一方面的第二中可能的实现方式中，所述预设条件包括：通过所述第一通信接口接收到的第二消息的数量与通过所述第一通信接口发送的第一消息的数量的比值小于预设的第二门限，以及，
所述第一网络设备确定通过本端的第一通信接口传输的业务的成功率是否满足预设条件，包括：
所述第一网络设备确定在第二预设时段内通过所述第一通信接口接收到的所述第二消息的数量与通过所述第一通信接口发送的所述第一消息的数量的比值是否小于预设的第二门限。
可选地，所述第二消息为所述第二网络设备基于所述第一消息发送的消息。因此，可以提高判断的准确性。
进一步地，在所述第一网络设备确定在第二预设时段内通过所述第一通信接口接收到的所述第二消息的数量与通过所述第一通信接口发送的所述第一消息的数量的比值是否小于预设的第二门限之前，所述方法还包括：
所述第一网络设备确定在所述第二预设时段内通过所述第一通信接口发送的所述第一消息和通过所述第一通信接口接收到的所述第二消息的总数量大于或等于预设的第三门限。
结合第一方面及其上述可能的实现方式，在第一方面的第三种可能的实现方式中，所述第一网络设备在确定通过本端的第一通信接口传输的业务的成功率满足所述预设条件时，释放所述传输层链路，包括：
所述第一网络设备在确定通过本端的第一通信接口传输的业务的成功率满足所述预设条件时，确定所述传输层链路状态是否正常；
所述第一网络设备在确定所述传输层链路状态正常时释放所述传输层链路。
因此，可以在释放下层链路之前确定下层链路是否正常，在下层链路有故障的情况下，首先排除下层链路的故障再进行S1接口的重建，从而可以准确及时地修复S1接口，提高接口可靠性。
第二方面，提供了一种通信接口故障的处理装置，用于执行第一方面及第一方面的任意可能的实现方式中的方法。具体地，该处理装置可以包括用于执行第一方面及第一方面的任意可能的实现方式中的方法的单元。
第三方面，提供了一种通信接口故障的处理设备，包括存储器和处理器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得所述通信接口故障的处理设备执行上述第一方面及第一方面的任意可能的实现方式中的方法。
第四方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被第一方面中的第一设备的处理单元、收发单元或处理器、收发器运行时，使得所述第一设备执行第一方面及第一方面的任意可能的实现方式中的方法。
第五方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序包括用于执行第一方面及第一方面的任意可能的实现方式中的 方法的指令。
在上述某些可能的实现方式中，所述第一通信接口为S1接口，所述第一网络设备为接入网设备，所述第二网络设备为核心网设备，
所述第一消息包括：初始用户设备消息(Initial UE message)，所述第二消息包括初始上下文建立请求(Initial context setup request)消息。
在上述某些可能的实现方式中，所述第一通信接口为S1接口，所述第一网络设备为核心网设备，所述第二网络设备为接入网设备，
所述第一消息包括：演进的无线接入承载建立请求(E-RAB setup request)消息，所述第二消息包括：E-RAB建立响应(E-RAB setup response)消息；或者，
所述第一消息包括：E-RAB修改请求(E-RAB modification request)消息，所述第二消息包括：E-RAB修改响应(E-RAB modification response)消息。
在上述某些可能的实现方式中，所述第一通信接口为S1接口，所述传输层链路为SCTP链路，所述应用层链路为S1AP链路。
在上述某些可能的实现方式中，所述第一通信接口为X2接口，所述第一网络设备为第一接入网设备，所述第二网络设备为第二接入网设备，
所述第一消息包括：切换请求(Handover request)消息，所述第二消息包括：切换请求响应(Handover request acknowledge)消息。
在上述某些可能的实现方式中，所述第一通信接口为X2接口，所述传输层链路为SCTP链路，所述应用层链路为X2AP链路。
本申请实施例的通信接口故障的处理方法和装置，通过第一网络设备监控本端的业务成功率，在对端出现异常的情况下，能及时地感知到接口的异常，并重建通信接口，从而能够提高接口可靠性，提高通信***的可靠性。
附图说明
图1示出了MME和eNB的协议栈的示意图。
图2示出了S1AP链路建立的示意性流程图。
图3示出了根据本申请一实施例的通信接口故障的处理方法的示意性流程图。
图4示出了根据本申请另一实施例的通信接口故障的处理方法的示意性 流程图。
图5示出了根据本申请又一实施例的通信接口故障的处理方法的示意性流程图。
图6示出了根据本申请实施例的通信接口故障的处理装置的示意性框图。
图7示出了根据本申请实施例的通信接口故障的处理设备的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚地描述。
应理解，本申请的技术方案可以应用于各种通信***，例如：全球移动通讯(Global System of Mobile communication，简称“GSM”)***、码分多址(Code Division Multiple Access，简称“CDMA”)***、宽带码分多址(Wideband Code Division Multiple Access，简称“WCDMA”)***、通用分组无线业务(General Packet Radio Service，简称“GPRS”)、LTE***、先进的长期演进(Advanced long term evolution，简称“LTE-A”)***、Universal Mobile Telecommunication System，简称“UMTS”)或下一代通信***，例如，第五代通信(fifth-generation，简称“5G”)等。
为便于理解，首先结合图1简要介绍演进型UMTS陆地无线接入网(Evolved UMTS Terrestrial Radio Access Network，简称“E-UTRAN”)接口的协议栈。
图1示出了MME和eNB的协议栈的示意图。由图1可以看到，在目前的LTE网络中，MME设备和eNB设备之间的用户信令传输使用的是S1-AP协议，该协议保证用户信令的传送，其传输层协议使用的是SCTP协议。
因此，若MME与eNB之间正常地通信，需要保证图1中示出的各层的链路都处于正常状态。例如，若SCTP链路异常，则会导致MME和eNB之间不能正常通信；若SCTP链路正常，而S1AP链路异常，也会导致MME和eNB之间不能正常通信。
换句话说，S1接口包括各层对等的协议实体构成的链路，例如至少包括：SCTP链路、S1AP链路等。
与之相似地，在基站间的X2接口，例如，在eNB和eNB之间，用户信令传输使用的是X2-AP协议，传输层协议使用的是SCTP协议。X2接口包括各层对等的协议实体构成的链路，例如至少包括：SCTP链路、X2AP链路等。
以下，为方便理解和说明，以S1接口的链路为例，详细说明本申请实施例。
如上所述，在SCTP链路正常，而S1AP链路异常的情况下，会导致MME和eNB之间不能正常通信。但是，S1AP链路的异常有可能出现以下几种情况：
情况a、eNB侧正常，MME侧异常；
情况b、eNB侧异常，MME侧正常；
情况c、eNB侧和MME侧都出现异常。
可以理解，以上三种情况中任意一种情况出现都会导致MME和eNB之间不能正常通信。若出现情况c，则eNB侧在SCTP链路异常时可以触发S1AP建立(Setup)流程；若出现情况b，因eNB侧无法将消息发送给MME，eNB可以主动释放SCTP链路，以通知对端的MME链路异常，MME释放S1AP链路，接着eNB主动发起S1AP Setup流程；若出现情况a，因eNB侧可以将消息发送到MME，而MME因自身异常而不会作出任何处理，eNB因并不知道MME侧故障，故不会主动发起S1建立(Setup)流程。因此，本申请实施例主要针对该场景，提出一种通信接口故障的处理方法。
为了便于理解本申请实施例，首先结合图2说明S1建立的具体过程。图2从设备交互的角度示出了S1建立的示意性流程图。如图2所示，S1建立流程具体包括以下步骤：
201、在传输层，eNB向MME发送SCTP链路初始化(SCTP Init)消息；
202、MME向eNB发送SCTP链路初始化响应(SCTP Init Ack)消息，该SCTP Init Ack消息中携带缓存(Cookie)；
203、eNB向MME发送SCTP缓存响应(SCTP Cookie Echo)消息；
204、MME向eNB发送SCTP缓存响应反馈(SCTP Cookie Echo Ack)消息。此时，SCTP链路建立(Established)完成；
205、在协议层，eNB向MME发送S1建立(S1Setup)消息；
206、MME向eNB发送S1建立响应(S1Setup Response)消息。此时，S1AP链路建立完成。
由上述过程可以看到，上述步骤201至204即为SCTP链路建立的过程，在建立起SCTP链路后，进一步通过步骤205和206建立S1AP链路。需要说明的是，图2中虽然仅示出了SCTP链路和S1AP链路的建立，但这不应对本申请构成任何限定。本领域的技术人员可以理解，释放S1AP链路，可以理解为将S1AP层以及其下层(例如，包括SCTP层、IP层等，具体可以参看图1)的链路信息全部释放掉。建立S1AP链路，可以理解为将S1AP层以及其下层之间的链路全部建立起来。换句话说，S1AP链路和SCTP链路共用SCTP层及其以下各层的协议实体。
需要注意的是，S1AP链路的重建只能由eNB发起，也就是说，在上述情况a下，MME异常而eNB未知的情况下，eNB是不会主动发起S1AP链路重建的。因此，需要提供一种方法，能够在MME异常的情况下，触发eNB主动发起S1AP链路重建。
图3至图5示出了根据本申请实施例的通信接口故障的处理方法的示意性流程图。应理解，图3至图5示出了本申请实施例的通信接口故障的处理方法的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图中的各种操作的变形。此外，图中的各个步骤可以按照与图中呈现的不同的顺序来执行，并且有可能并非要执行图中的全部操作。
需要说明的是，各图中示出的通信接口故障的处理方法中的各步骤可以由第一网络设备来执行，在第一通信接口为S1接口的场景下，该第一网络设备与第二网络设备通过S1接口通信连接，该第一网络设备可以为接入网设备，该第二网络设备可以为核心网设备，传输层链路可以为SCTP链路，应用层链路可以为S1AP链路(情况一，对应图3)，或者，该第一网络设备可以为核心网设备，该第二网络设备可以为接入网设备，传输层链路可以为SCTP链路，应用层链路可以为S1AP链路(情况二，对应图4)；在第一通信接口为X2接口的场景下，该第一网络设备与第二网络设备通过X2接口通信连接，该第一网络设备和该第二网络设备可以为接入网设备，传输层链路可以为SCTP链路，应用层链路可以为X2AP链路(情况三，对应图5)。
需要说明的是，SCTP链路可以理解为在两个端点(例如，MME和eNB，或者，第一eNB和第二eNB)之间提供稳定、有序的数据传输服务的链路。 它是一种基于提供不可靠传输业务的协议(例如，IP)之上的可靠的数据报文传输协议。它用于提供面向连接的可靠的数据报文传输。端点是SCTP的基本逻辑概念，是数据报文的逻辑发送端和接收端，是一个典型的逻辑实体。例如，在本申请实施例中，发送端可以为MME，接收端可以为eNB，对于发送端MME而言，本端为其自身，对端为eNB，而对于接收端eNB而言，本身为其自身，对端为MME。
SCTP端点由一组具有相同SCTP端口号的传输地址标识，且SCTP协议规定两个端点之间能且仅能建立一条连接。所以，SCTP端点可能有多个传输地址，但这些传输地址有唯一的端口号。
在本申请实施例中，接入网设备可以为无线局域网(Wireless Local Area Networks，简称“WLAN”)中的接入点(Access Point，简称“AP”)，GSM或CDMA中的基站(Base Transceiver Station，简称“BTS”)，也可以是WCDMA中的基站(NodeB，简称“NB”)，还可以是LTE中的演进型基站(Evolutional Node B，简称“eNode B”或“eNB”)，或者中继站或接入点，或者车载设备、可穿戴设备以及未来5G网络中的gNB或者未来演进的公共陆地移动网络(Public Land Mobile Network，简称“PLMN”)网络中的网络设备等。
在本申请实施例中，核心网设备可以为MME，MME是控制面网元，主要负责用户设备的移动性管理和会话管理等控制面功能。
以下结合图3至图5，以及上文描述的三种情况，详细说明根据本申请实施例的通信接口故障的处理方法。
情况一：
图3示出了根据本申请一实施例的通信接口故障的处理方法300的示意性流程图。在图3示出的方法300中，第一网络设备可以为eNB，第二网络设备可以为MME。但应理解，这里仅为示例，而不应对本申请构成任何限定。
如图3所示，该方法300包括：
S310，eNB确定通过S1接口传输的业务的成功率是否满足预设条件。
通过S1接口传输的业务的成功率，可以理解用于指示通过S1接口正常通信的一个指标。在本申请实施例中，由于该通信链路涉及业务层面，因此，可以称为业务成功率，或者，也可以称为通信的成功率，消息响应率等。本 申请对此并未特别限定。具体地，当链路处于正常通信状态，本端与对端之间的交互正常，可能遭受通信中断、业务丢失等故障的几率较小，即，成功率较高；当链路处于异常状态，本端与对端之间的交互异常，可能造成通信中断、业务丢失等故障的几率较大，即，成功率较低。
作为一个可能的实施例，该业务成功率可以通过eNB端监测发出的某些消息是否得到响应来确定。例如，在用户设备(User Equipment，简称“UE”)开机附着流程中，或者，在跟踪区域更新(Tracking Area Update，简称“TAU”)流程中，或者，在核心网主动发起的寻呼(Paging)流程中，eNB可以向MME发送初始UE消息(Initial UE message)，在链路正常的情况下，MME可以向eNB发送初始上下文建立请求(Initial context setup request)消息。
这里，为便于区分和说明，将第一网络设备(例如，该eNB)发送的消息记作第一消息，将第一网络设备(例如，该eNB)接收到的第二网络设备(例如，MME)发送的消息记作第二消息。
可选地，S310可以具体包括：
该eNB在第一预设时段内通过S1接口发送的第一消息和通过S1接口接收到的第二消息的总数量是否小于预设的第一门限。
具体地，该eNB可以预先设定一个时段(为便于区分和说明，记作第一预设时段)，在该第一预设时段内监测通过该S1接口发送和接收消息的总数量。例如，该第一预设时段可以为8:00至20:00。在监测到该第一预设时段内通过该S1接口收发消息的总数量小于预设的第一门限时，确定该eNB通过S1接口传输的业务的成功率满足预设条件，进而判定状态异常。
可以理解的是，由于eNB所覆盖的区域不同，话务量也不相同，例如，山区与城市的话务量就有着非常大的差别，因此，所对应的第一门限也可能是不同的，覆盖山区的eNB所对应的第一门限可能较小，覆盖城市的eNB所对应的第一门限可能较大。
可选地，S310可以具体包括：
该eNB确定在第二预设时段内通过S1接口接收到第二消息的数量与通过S1接口发送的第一消息的数量的比值是否小于预设的第二门限。
具体地，该eNB可以预先设定一个时段(为便于区分和说明，记作第二预设时段)，在该第二预设时段内监测该eNB通过S1接口接收到的第二消息的数量与发送的第一消息的数量的比值，若监测到该第二预设时段内该 eNB通过该S1接口接收到的第二消息的数量与发送的第一消息的数量的比值小于预设的第二门限，确定该eNB通过S1接口传输的业务的成功率满足预设条件，进而判定状态异常。
进一步地，由于该比值在一定程度上也与该eNB的话务量相关，即与eNB所覆盖的区域相关。可以结合该eNB在该第二预设时段内通过S1接口发送的第一消息和通过S1接口接收到的第二消息的总数量来判定本端的S1接口是否异常。
可选地，在该eNB确定在第二预设时段内通过S1接口接收到第二消息的数量与通过S1接口发送的第一消息的数量的比值小于预设的第二门限之前，该方法还包括：
该eNB确定在第二预设时段内通过S1接口发送的第一消息和通过S1接口接收到的第二消息的总数量大于或等于预设的第三门限。
其中，预设的第三门限可以理解为一个样本大小，即，当eNB确定在第二预设时段内通过S1接口收发消息的数量满足样本大小的门限时，才进一步确定接收到的第二消息与发送的第一消息的数量之比是否小于预设的第二门限。举例来说，eNB确定在第二预设时段内通过S1接口收发消息的数量满足样本大小的门限(例如，100条消息)时，便进一步确定该S1接口在该第二预设时段内是否只是发送了100条消息，而未收到任何消息，或者，发送的消息数量远远大于接收到的消息的数量。也就是监测该S1接口是否“只出不进”。
可以理解的是，该预设的第三门限同样与该eNB的话务量相关。
需要说明的是，上文中所列举的第一预设时段和第二预设时段仅为区分两种不同的判定方法，该第一预设时段和第二预设时段可以为时长相同或不同的时段，本申请对此并未特别限定。在第一预设时段与第二预设时段为相同时长的情况下，上述两种判定业务成功率是否满足预设条件的方法可以结合使用，此时，预设的第一门限与预设的第三门限相同。即，先判断在第一预设时段内通过S1接口收发消息的数量是否大于或等于预设的第一门限。若否，则直接确定该eNB侧的S1接口异常；若是，则进一步确定在该第一预设时段内通过S1接口接收到的第二消息的数量与发送的第一消息的数量的比值是否大于预设的第二门限，若否，则确定该eNB侧的S1接口异常，若是，则确定该eNB侧的S1接口正常，暂时不需要处理。
由于上文所描述的方法中，所监测的eNB发送的第一消息，MME可以进行回复或者不回复。若所采集的样本中的所有的第一消息都是不需要MME回复的，则，即便检测到eNB发送的第一消息的数量为样本的全部，而第二消息的数量为零，也不一定能确定该eNB侧的S1接口异常。
因此，为了提高鲁棒性，该eNB可以进一步提高判断的准确率，可以预定义所监测的第一消息中至少包括部分对端必须回复的第二消息。即，若eNB通过S1接口向MME发送该第一消息，MME在通信正常情况下，必须要向该eNB回复第二消息。这样，可以根据MME是否针对接收到的第一消息回复第二消息来更准确地确定业务成功率。在这种情况下，该业务的成功率可以理解为消息响应率。
在本申请实施例中，作为示例而非限定，该第一消息可以为初始用户设备消息(Initial UE message)，该第二消息为初始上下文建立请求(Initial context setup request)消息。
由上述方法，eNB可以确定本端的S1接口故障。
S320，eNB在确定通过S1接口传输的业务的成功率满足预设条件时，释放SCTP链路(即，传输层链路的一例)。
eNB在确定本端的S1接口故障后，需要重建S1接口。但是由于MME并不知道eNB侧的S1接口故障，在MME看来，S1接口是正常的。因此，eNB可以通过释放SCTP链路的方式通知对端的MME S1接口故障。当eNB释放SCTP链路后，可以通过SCTP实体之间的握手机制，使对端(即，MME)释放S1AP链路。具体地，eNB释放SCTP链路，可以理解为释放SCTP链路信息和实体。其中，SCTP链路信息包括：本端及对端的IP地址、本端及对端的端口号，SCTP层及以下各层的实体编号(或者说，实例号)，以及链路号等信息。MME释放S1AP链路，可以理解为是否S1AP链路信息和实体。其中，S1AP链路信息包括：S1AP层及以下各层的实体编号(或者说，实例号)。
应理解，以上列举的SCTP链路信息、S1AP链路信息的具体内容、释放SCTP链路以及释放S1AP链路的具体内容仅为示例性说明，而不应对本申请构成任何限定。
可选地，S320可以具体包括：
eNB确定SCTP链路是否正常；
eNB在确定SCTP链路正常时释放SCTP链路。
由于eNB在确定S1接口故障的时候，并不确定只是S1AP层链路故障，还是SCTP层链路故障，甚至更底层的链路故障。因此，eNB可以在重建S1链路前，确定SCTP层链路是否正常。若SCTP层链路正常，则说明从SCTP层往下的链路都是正常的，而仅仅是S1AP层链路出现异常，只要直接发起S1AP链路重建即可。若SCTP链路异常，则还需要进一步确定SCTP层链路异常的原因。
若SCTP层链路正常，则eNB可以直接发起S1链路的重建；若SCTP层链路异常，则eNB可以通过现有技术来检测并修复SCTP链路，若在修复SCTP链路后仍检测到S1接口异常，可以使用本申请实施例的通信接口故障的处理方法来重建S1AP链路。
应理解，SCTP链路故障的检测与修复可以通过现有技术中的方法来实现，而这也并非本申请的核心所在，为了简洁，这里省略对其具体过程的详细说明。
S330，eNB重建S1AP链路(即，应用层链路的一例)。
可以理解的是，eNB重建S1AP链路的过程包括了重建SCTP链路的过程，eNB重建S1AP链路的具体过程在上文中已经结合图2详细说明，为了简洁，这里不再赘述。
由此，S1接口恢复正常工作。
在本申请实施例中，eNB可以实时监测本端的S1接口，在检测到业务成功率满足预设条件时，可以执行上述方法300来修复S1接口，以便于通信快速恢复正常。
本申请实施例的通信接口故障的处理方法，通过eNB确定通过S1接口传输业务的成功率，在满足预设条件的情况下，主动发起S1链路的重建。因此，能够在MME侧出现异常的情况下，及时地检测到链路故障，并快速进行链路修复，从而提高了S1接口的自愈能力，避免了由于两端接口状态不一致造成的业务成功率下降的问题，提高了S1接口的可靠性。
情况二：
可以理解，上述方法同样适用于在eNB侧异常，MME侧正常的情况下。
图4示出了根据本申请另一实施例的通信接口故障的处理方法400的示意性流程图。在图4示出的方法400中，第一网络设备可以为MME，第二 网络设备可以为eNB，传输层链路可以为SCTP链路，应用层链路可以为S1AP链路。但应理解，这里仅为示例，而不应对本申请构成任何限定。
如图4所示，该方法400包括：
S410，MME确定通过S1接口传输的业务的成功率是否满足预设条件。
作为一个可能的实施例，该业务成功率可以通过MME端监测发出的某些消息是否得到响应来确定。例如，在MME建立承载的流程中，MME可以向eNB发送承载建立/修改请求，在链路正常的情况下，eNB可以向MME发哦送承载建立/修改响应。
可选地，S410可以具体包括：
该MME在第一预设时段内通过S1接口发送的第一消息和通过S1接口接收到的第二消息的总数量是否小于预设的第一门限。
可选地，S410可以具体包括：
该MME确定在第二预设时段内通过S1接口接收到第二消息的数量与通过S1接口发送的第一消息的数量的比值是否小于预设的第二门限。
可选地，在该MME确定在第二预设时段内通过S1接口接收到第二消息的数量与通过S1接口发送的第一消息的数量的比值小于预设的第二门限之前，该方法还包括：
该MME确定在第二预设时段内通过S1接口发送的第一消息和通过S1接口接收到的第二消息的总数量大于或等于预设的第三门限。
可选地，该第二消息为eNB基于该MME发送的第一消息回复的响应消息。
在本申请实施例中，作为示例而非限定。该第一消息可以为演进的无线接入承载(Evolved Radio Access Bearer，简称“E-RAB”)建立请求(E-RAB setup request)消息，该第二消息可以为E-RAB建立响应(E-RAB setup response)消息；或者，
该第一消息可以包括E-RAB修改请求(E-RAB modification request)消息，该第二消息可以包括E-RAB修改响应(E-RAB modification response)消息。
S420，MME在确定通过S1接口传输的业务的成功率满足预设条件时，释放SCTP链路(即，传输层链路的另一例)。
可选地，S420具体包括：
MME确定SCTP链路是否正常；
MME在确定SCTP链路正常时，释放SCTP链路。
应理解，S420的具体过程与方法300中的S320的具体过程基本相似，为了简洁，这里不再赘述。
可以理解的是，MME释放SCTP链路后，会触发eNB重建S1AP链路(即，应用层链路的另一例)。
本申请实施例的通信接口故障的处理方法，通过MME确定通过S1接口传输业务的成功率，在满足预设条件的情况下，主动发起S1链路的重建。因此，能够在eNB侧出现异常的情况下，及时地检测到链路故障，并快速触发eNB进行链路修复，从而提高了S1接口的自愈能力，避免了由于两端接口状态不一致造成的业务成功率下降的问题，提高了S1接口的可靠性。
以上，结合图3和图4详细说明了第一通信接口为S1接口的情形。以下，结合图5详细说明第一通信接口为X2接口的情形。
情况三：
图5示出了根据本申请又一实施例的通信接口故障的处理方法500的示意性流程图。在图5示出的方法500中，第一网络设备可以为第一eNB，第二网络设备可以为第二eNB，传输层链路可以为SCTP链路，应用层链路可以为X2AP链路。但应理解，这里仅为示例，而不应对本申请构成任何限定。可以理解，第一eNB和第二eNB为对等的两个实体，在第一eNB和第二eNB中的任意一端发生S1接口异常，都可以使用本申请实施例的通信接口故障的处理方法进行检测和修复。为了简洁，图5仅以第一eNB端监测到第二eNB端异常的情况为例进行说明，第二eNB端监测到第一eNB端异常的情况下，第二eNB执行的动作与图5示出的步骤相同，这里不再赘述。
如图5所示，该方法500包括：
S510，第一eNB确定通过S1接口传输的业务的成功率满足预设条件。
作为一个可能的实施例，该业务成功率可以通过第一eNB监测发出的某些消息是否得到响应来确定。例如，在UE切换由第一eNB的小区切换至第二eNB的小区场景下，第一eNB可以理解为源基站，第二eNB可以理解为目标基站，第一eNB可以向第二eNB发送切换请求，在链路正常的情况下，第二eNB可以向第一eNB发送切换请求响应。
可选地，S510可以具体包括：
该eNB在第一预设时段内通过X2接口发送的第一消息和通过X2接口接收到的第二消息的总数量小于预设的第一门限。
可选地，S510可以具体包括：该第一eNB确定在第二预设时段内通过X2接口接收到第二消息的数量与通过X2接口发送的第一消息的数量的比值小于预设的第二门限。
可选地，在该第一eNB确定在第二预设时段内通过X2接口接收到第二消息的数量与通过X2接口发送的第一消息的数量的比值小于预设的第二门限之前，该方法还包括：
该第一eNB确定在第二预设时段内通过X2接口发送的第一消息和通过X2接口接收到的第二消息的总数量大于或等于预设的第三门限。
可选地，该第二消息为第二eNB基于该第一eNB发送的第一消息回复的响应消息。
在本申请实施例中，作为示例而非限定该第一消息可以包括切换请求(Handover request)消息，该第二消息可以包括切换请求响应(Handover request acknowledge)消息。
S520，第一eNB在确定通过S1接口传输的业务的成功率满足预设条件时，释放SCTP链路(即，传输层链路的又一例)。
可选地，S520可以具体包括：
第一eNB确定SCTP链路正常；
该第一eNB在确定SCTP链路正常时，释放SCTP链路。
S530，第一eNB重建S1AP链路(即，应用层链路的又一例)。
应理解，S520、S530的具体过程与方法300中的S320、S330的具体过程基本相似，为了简洁，这里不再赘述。
本申请实施例的通信接口故障的处理方法，通过第一eNB确定通过X2接口传输业务的成功率，在满足预设条件的情况下，主动发起X2链路的重建。因此，能够在第二eNB侧出现异常的情况下，及时地检测到链路故障，并快速进行链路修复，从而提高了X2接口的自愈能力，避免了由于两端接口状态不一致造成的业务成功率下降的问题，提高了X2接口的可靠性。
需要说明的是，上文中列举的第一消息和第二消息的具体内容仅为示例性说明，而不应对本申请构成任何限定。并且，还需要注意的是，在以上示例的各种情况下，用于判断业务成功率是否满足预设条件的第一消息和第二 消息分别可以为相同的消息或者不同的消息。例如，在采集的样本中，第一消息可以为不同的消息，作为对第一消息的响应的第二消息也可以不同。
以上，结合图3至图5详细说明了根据本申请实施例的通信接口故障的处理方法。以下，结合图6和图7详细说明根据本申请实施例的通信接口故障的处理装置。
图6示出了本申请实施例的通信接口故障的处理装置10的示意性框图。如图6所示，该装置10包括：确定单元11和处理单元12。
应理解，该装置10可以对应(例如，可以配置于或本身即为)上述方法300至方法500中描述的第一网络设备，并且，该装置10中各模块或单元分别用于执行上述方法200中发送设备所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
图7示出了根据本申请实施例的通信接口故障的处理设备20的示意性框图。如图7所示，该设备20包括：收发器21、处理器22和存储器23。其中，收发器21、处理器22和存储器23之间通过内部连接通路互相通信，传递控制和/或数据信号。
具体地，该设备20可以对应(例如，可以配置于或本身即为)上述方法300至方法500中描述的第一网络设备。在该设备20中，处理器22可用于执行图3、图4或图5中所示实施例的方法，并实现该设备20在图3、图4或图5中所示实施例的功能。
本申请实施例可以应用于处理器中，或者由处理器实现。处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是中央处理单元(Central Processing Unit，简称“CPU”)、该处理器还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，简称“DSP”)、专用集成电路(Application Specific Integrated Circuit，简称“ASIC“)、现成可编程门阵列(Field Programmable Gate Array，简称“FPGA”)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件器组合执行完成。软件器可 以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，简称“ROM”)、可编程只读存储器(Programmable ROM，简称“PROM”)、可擦除可编程只读存储器(Erasable PROM，简称“EPROM”)、电可擦除可编程只读存储器(Electrically EPROM，简称“EEPROM”)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，简称“RAM”)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，简称“SRAM”)、动态随机存取存储器(Dynamic RAM，简称“DRAM”)、同步动态随机存取存储器(Synchronous DRAM，简称“SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，简称“DDR SDRAM”)、增强型同步动态随机存取存储器(Enhanced SDRAM，简称“ESDRAM”)、同步连接动态随机存取存储器(Synchlink DRAM，简称“SLDRAM”)和直接内存总线随机存取存储器(Direct Rambus RAM，简称“DR RAM”)。应注意，本文描述的***和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的通信接口故障的处理方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件器组合执行完成。软件器可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结 合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易 想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (12)

  1. 一种通信接口故障的处理方法，其特征在于，所述方法应用于包括第一网络设备和第二网络设备的通信***中，所述第一网络设备与所述第二网络设备之间通过第一通信接口通信连接，所述第一通信接口至少包括配置于所述第一网络设备和所述第二网络设备之间的传输层链路和应用层链路，所述方法包括：
    所述第一网络设备确定通过所述第一通信接口传输的业务的成功率是否满足预设条件；
    所述第一网络设备在确定通过所述第一通信接口传输的业务的成功率满足所述预设条件时，释放所述传输层链路，以触发所述应用层链路的重建。
  2. 根据权利要求1所述的方法，其特征在于，所述预设条件包括：在第一预设时段内通过所述第一通信接口发送的第一消息的数量和通过所述第一通信接口接收到的第二消息的总数量小于预设的第一门限；以及，
    所述第一网络设备确定通过所述第一通信接口传输的业务的成功率是否满足预设条件，包括：
    所述第一网络设备确定在第一预设时段内通过所述第一通信接口发送的所述第一消息和通过所述第一通信接口接收到的所述第二消息的总数量是否小于所述预设的第一门限。
  3. 根据权利要求1所述的方法，其特征在于，所述预设条件包括：通过所述第一通信接口接收到的第二消息的数量与通过所述第一通信接口发送的第一消息的数量的比值小于预设的第二门限，以及，
    所述第一网络设备确定通过所述第一通信接口传输的业务的成功率是否满足预设条件，包括：
    所述第一网络设备确定在第二预设时段内通过所述第一通信接口接收到的所述第二消息的数量与通过所述第一通信接口发送的所述第一消息的数量的比值是否小于预设的第二门限。
  4. 根据权利要求3所述的方法，其特征在于，所述第二消息为所述第二网络设备基于所述第一消息发送的消息。
  5. 根据权利要求3或4所述的方法，其特征在于，在所述第一网络设备确定在第二预设时段内通过所述第一通信接口接收到的所述第二消息的数量与通过所述第一通信接口发送的所述第一消息的数量的比值是否小于 预设的第二门限之前，所述方法还包括：
    所述第一网络设备确定在所述第二预设时段内通过所述第一通信接口发送的所述第一消息和通过所述第一通信接口接收到的所述第二消息的总数量大于或等于预设的第三门限。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第一网络设备在确定通过所述第一通信接口传输的业务的成功率满足所述预设条件时，释放所述传输层链路，包括：
    所述第一网络设备在确定通过所述第一通信接口传输的业务的成功率满足所述预设条件时，确定所述传输层链路状态是否正常；
    所述第一网络设备在确定所述传输层链路状态正常时释放所述传输层链路。
  7. 一种通信接口故障的处理装置，其特征在于，所述装置与第二网络设备之间通过第一通信接口通信连接，所述第一通信接口至少包括配置于所述装置与所述第二网络设备之间的传输层链路和应用层链路，所述装置包括：
    确定单元，用于确定通过所述第一通信接口传输的业务的成功率是否满足预设条件；
    处理单元，用于所述确定单元确定通过所述第一通信接口传输的业务的成功率满足所述预设条件时，释放所述传输层链路，以触发所述应用层链路的重建。
  8. 根据权利要求7所述的装置，其特征在于，所述确定单元具体用于确定在第一预设时段内通过所述第一通信接口发送的第一消息和通过所述第一通信接口接收到的第二消息的总数量是否小于预设的第一门限。
  9. 根据权利要求7所述的装置，其特征在于，所述确定单元具体用于确定在第二预设时段内通过所述第一通信接口接收到第二消息的数量与通过所述第一通信接口发送的第一消息的数量的比值是否小于预设的第二门限。
  10. 根据权利要求9所述的装置，其特征在于，所述第二消息为所述第二网络设备基于所述第一消息发送的消息。
  11. 根据权利要求9或10所述的装置，其特征在于，所述确定单元还用于确定在所述第二预设时段内通过所述第一通信接口发送的所述第一消 息和通过所述第一通信接口接收到的所述第二消息的总数量大于或等于预设的第三门限。
  12. 根据权利要求7至11中任一项所述的装置，其特征在于，所述确定单元还用于确定所述传输层链路状态是否正常；
    所述处理单元具体用于在确定所述传输层链路状态正常时释放所述传输层链路。
PCT/CN2016/112046 2016-12-26 2016-12-26 一种通信接口故障的处理方法和装置 WO2018119559A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2016/112046 WO2018119559A1 (zh) 2016-12-26 2016-12-26 一种通信接口故障的处理方法和装置
CN201680091484.2A CN110050478A (zh) 2016-12-26 2016-12-26 一种通信接口故障的处理方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/112046 WO2018119559A1 (zh) 2016-12-26 2016-12-26 一种通信接口故障的处理方法和装置

Publications (1)

Publication Number Publication Date
WO2018119559A1 true WO2018119559A1 (zh) 2018-07-05

Family

ID=62706625

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/112046 WO2018119559A1 (zh) 2016-12-26 2016-12-26 一种通信接口故障的处理方法和装置

Country Status (2)

Country Link
CN (1) CN110050478A (zh)
WO (1) WO2018119559A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113225762B (zh) * 2020-02-04 2022-11-22 大唐移动通信设备有限公司 一种流控制传输协议链路的建立方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008116378A1 (fr) * 2007-03-23 2008-10-02 Huawei Technologies Co., Ltd. Procédé et dispositif correspondant pour le rétablissement d'un support de transmission
CN101848554A (zh) * 2010-05-19 2010-09-29 新邮通信设备有限公司 一种无线接口恢复方法和一种施主基站
CN103428742A (zh) * 2013-08-07 2013-12-04 大唐移动通信设备有限公司 一种s1接口sctp链路故障的处理方法和装置
CN104754628A (zh) * 2013-12-31 2015-07-01 ***通信集团山西有限公司 一种基于lte s1接口的数据采集关联分析方法和装置
CN105517195A (zh) * 2015-11-27 2016-04-20 上海华为技术有限公司 一种状态检测的方法及无线网络节点

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101136801B (zh) * 2007-03-06 2010-07-14 中兴通讯股份有限公司 网络故障检测方法
JP6151073B2 (ja) * 2013-04-15 2017-06-21 株式会社 日立産業制御ソリューションズ 基地局無線通信装置、無線通信システム、無線通信方法およびマルチホップ無線通信システム
US20150327156A1 (en) * 2014-05-06 2015-11-12 Qualcomm Incorporated Optimization of mbsfn decoding on scells when the pcell and scells belong to same mbsfn area
CN105554107B (zh) * 2015-12-14 2018-07-03 中南大学 高动态车载自组网络中基于tdma协议的最优合作点选择方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008116378A1 (fr) * 2007-03-23 2008-10-02 Huawei Technologies Co., Ltd. Procédé et dispositif correspondant pour le rétablissement d'un support de transmission
CN101848554A (zh) * 2010-05-19 2010-09-29 新邮通信设备有限公司 一种无线接口恢复方法和一种施主基站
CN103428742A (zh) * 2013-08-07 2013-12-04 大唐移动通信设备有限公司 一种s1接口sctp链路故障的处理方法和装置
CN104754628A (zh) * 2013-12-31 2015-07-01 ***通信集团山西有限公司 一种基于lte s1接口的数据采集关联分析方法和装置
CN105517195A (zh) * 2015-11-27 2016-04-20 上海华为技术有限公司 一种状态检测的方法及无线网络节点

Also Published As

Publication number Publication date
CN110050478A (zh) 2019-07-23

Similar Documents

Publication Publication Date Title
US10050827B2 (en) Method and apparatus for monitoring connectivity in a long term evolution network
TWI540928B (zh) 處理無線鏈路失敗的方法
EP2955962B1 (en) Handover failure detection device, handover parameter adjustment device, and handover optimization system
US20080076405A1 (en) Method of handling radio link failure in wireless communications system and related device
JP2020502873A (ja) パケット送信方法および装置、チップ、ならびに端末
US20170311371A1 (en) Method and nodes for handling connections in a communications system
EP3373520B1 (en) Status detection method and wireless network node
MX2011003311A (es) Estacion movil.
US9167614B2 (en) Tunneled direct link setup systems and methods with consistent link information maintenance
US20170289942A1 (en) Radio terminal, network apparatus, and method therefor
WO2016101575A1 (zh) 一种语音业务切换方法及设备
JP2017098666A (ja) 通信装置，及び暗号化通信の異常検出方法
US20230337066A1 (en) Managing multicast and broadcast services interest information
TW202123767A (zh) 用於在通訊網路中管理無線電承載相容性之系統和方法
WO2018082623A1 (zh) 一种连接重建立方法及装置、电子设备、计算机存储介质
RU2640573C1 (ru) Способ устранения отказа, сеть пакетной передачи данных, узел управления мобильностью и сетевая система
CN113661774A (zh) 双连接中的辅小区组失败
US10085191B2 (en) Control device and method therefor
US20230171648A1 (en) Method Network Optimization in Handover Failure Scenarios
WO2018119559A1 (zh) 一种通信接口故障的处理方法和装置
US20240163746A1 (en) Enhancements to self-organizing network reports for radio link failure after a dual active protocol stack fallback
US20240073771A1 (en) Managing ue configurations when a conditional procedure fails
WO2020200136A1 (zh) 一种网关选择***及方法
CN111279642B (zh) 信令可靠度增强方法及其装置
WO2022206485A1 (zh) 网关故障恢复方法、***及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16925147

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16925147

Country of ref document: EP

Kind code of ref document: A1