WO2022042499A1 - 隧道保活方法、网络设备、系统及存储介质 - Google Patents

隧道保活方法、网络设备、系统及存储介质 Download PDF

Info

Publication number
WO2022042499A1
WO2022042499A1 PCT/CN2021/114141 CN2021114141W WO2022042499A1 WO 2022042499 A1 WO2022042499 A1 WO 2022042499A1 CN 2021114141 W CN2021114141 W CN 2021114141W WO 2022042499 A1 WO2022042499 A1 WO 2022042499A1
Authority
WO
WIPO (PCT)
Prior art keywords
tunnel
alive
network device
keep
information
Prior art date
Application number
PCT/CN2021/114141
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 EP21860334.8A priority Critical patent/EP4192085A4/en
Publication of WO2022042499A1 publication Critical patent/WO2022042499A1/zh
Priority to US18/175,274 priority patent/US20230208679A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4641Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/25Maintenance of established connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2801Broadband local area networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/10Active monitoring, e.g. heartbeat, ping or trace-route
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/19Connection re-establishment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16Gateway arrangements

Definitions

  • the embodiments of the present application relate to the field of communications technologies, and in particular, to a tunnel keep-alive method, network device, system, and storage medium.
  • BNG Broadband Network Gateway
  • the traditional BNG equipment couples the control plane (CP) function and the user plane (UP) function.
  • the BNG is called a virtual broadband network gateway (vBNG), and includes a CP device and a UP device.
  • vBNG virtual broadband network gateway
  • L2TP layer 2 tunnel protocol access concentrator
  • LAC layer 2 tunnel protocol access concentrator
  • the related art provides a tunnel keep-alive method.
  • the CP device After the CP device establishes a tunnel between the UP device and the LNS, the CP device and the LNS periodically send a tunnel keep-alive message through the UP device to perform tunneling. Keep alive to ensure that user services are not interrupted. That is, the UP device is responsible for forwarding the tunnel keep-alive message between the CP device and the LNS, so that the CP device and the LNS can communicate with each other, and then perform tunnel keep-alive to ensure that user services are not interrupted.
  • the embodiments of the present application provide a tunnel keep-alive method, network device, system, and storage medium, which can ensure that the network connection of the terminal is not interrupted when a communication failure occurs between the UP device and the CP device.
  • the technical solution is as follows:
  • a first aspect provides a tunnel keep-alive method, wherein a control plane CP device and a user plane UP device are used to interact with a remote network device to ensure that a terminal accesses a network, and the method includes:
  • the UP device receives the first tunnel information sent by the CP device, and the first tunnel information includes the information of one or more tunnels established between the UP device and the remote network device; if the UP device detects that the communication between itself and the CP device occurs If the fault occurs, the UP device performs tunnel keep-alive for the one or more tunnels according to the first tunnel information.
  • the UP device before the communication failure between the UP device and the CP device, the UP device receives the tunnel information synchronized by the CP device, and after the communication between the UP device and the CP device fails, the UP device performs tunnel protection according to the tunnel information. In other words, the UP device maintains the tunnel with the remote network device, so that the tunnel removal will not be triggered due to the communication failure between the CP device and the UP device.
  • This solution can ensure that the network connection between the terminal and the remote device is not Therefore, it will be interrupted, that is, to ensure that user services are not damaged.
  • the CP device before the communication between the UP device and the CP device fails, there are various implementations for the CP device to send the first tunnel information to the UP device. Repeat.
  • the first tunnel information is carried in the packet forwarding control protocol (packet forwarding control protocol, PFCP) update request message
  • the one or more tunnels are L2TP tunnels
  • the information of each tunnel in the one or more tunnels Including the tunnel description information
  • the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv4 address and the tunnel remote IPv4 address
  • the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv6 address, and the tunnel remote IPv6 address. That is, the CP device synchronizes the tunnel information with the UP device by extending the PFCP message.
  • the CP device when the communication between the UP device and the CP device is normal, can also synchronize the first session information with the UP device, and the UP device receives the first session information sent by the CP device, the first session information Include information about sessions carried over the one or more tunnels. It should be noted that since the terminal implements service communication through the session carried on the tunnel, the CP device synchronizes the session information with the UP device, and the subsequent UP device performs the tunnel keep-alive process, according to the session information. communication between sessions.
  • the first session information is carried in the PFCP update request message, and the session information carried on each of the one or more tunnels includes a tunnel local identifier, a session local identifier, and a session remote identifier. That is, by extending the PFCP message, the CP device can synchronize session messages with the UP device.
  • the UP device after receiving the PFCP update request message, the UP device sends a PFCP update response message to the CP device.
  • the UP device communicates with the CP device through the control message redirection interface and the state control interface; the UP device detects that the communication between itself and the CP device fails, including: the UP device monitors the control message redirection interface and The state of the state control interface; if the UP device monitors the abnormal state of the control packet redirection interface and/or the state control interface, the UP device determines to detect that the communication between itself and the CP device is faulty. That is, the UP device perceives the communication status between the UP device and the CP device by detecting the state of the communication interface communicating with the CP device in real time.
  • each tunnel performs tunnel keep-alive independently, that is, each tunnel corresponds to a tunnel keep-alive sequence number, and the UP device or the CP device periodically interacts with the remote network device.
  • the tunnel keep-alive message implements the tunnel keep-alive for each tunnel.
  • the first tunnel information includes identifiers of one or more tunnels, and the tunnel keep-alive message carries the tunnel keep-alive sequence number of the corresponding tunnel.
  • the tunnel is not expected to be dismantled, that is, the user service of the terminal is not expected to be interrupted. Therefore, the UP device continues to keep the tunnel alive.
  • an implementation manner for the UP device to keep the tunnel alive when the UP device detects that the communication between itself and the CP device is faulty is introduced.
  • the UP device performs tunnel keep-alive on the one or more tunnels according to the first tunnel information, including: the UP device monitors the first tunnel keep-alive message sent by the remote network device, and the first tunnel keeps alive
  • the packet carries the identifier of the target tunnel and the tunnel keep-alive sequence number.
  • the UP device sends the second tunnel keep-alive message to the remote network device according to the identifier of the target tunnel, the tunnel keep-alive sequence number, and the identifiers of the one or more tunnels. Arts.
  • the UP device starts to send the second tunnel keep-alive message to the remote network device, that is, starts to periodically exchange the tunnel keep-alive message with the remote network device to realize the tunnel keep-alive.
  • the remote network device does not perceive a communication failure between the CP device and the UP device, but the UP device continues to take over the CP device according to the tunnel currently maintained by the remote network device.
  • the information of the tunnel is kept alive, that is, the seamless and fast tunnel keep alive.
  • the CP device when the communication between the UP device and the CP device is normal, the CP device also sends the first session information to the UP device.
  • the data packets between the terminal and the remote network device are maintained in the session carried by the tunnel to ensure the normal service communication of the terminal.
  • the UP device performs tunnel keep-alive on the one or more tunnels according to the first tunnel information, including: the UP device resets the tunnel keep-alive sequence number of the target tunnel in the first tunnel information, and the target tunnel is the One of one or more tunnels, the UP device instructs the remote network device to reset the tunnel keep-alive sequence number of the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel, and the remote network device resets the target tunnel's keep-alive sequence number. After the tunnel keep-alive sequence number of the tunnel is successfully reset, the UP device performs tunnel keep-alive for the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel and the identifier of the target tunnel.
  • the UP device needs to perform a tunnel failure recovery with the remote network device, that is, perform a data reconciliation with the remote network device and reset the tunnel keep-alive serial number to ensure that the UP device is connected to the remote network device. Tunnel consistency between end network devices.
  • the UP device instructs the remote network device to reset the tunnel keep-alive sequence number of the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel, including: The end network device sends a first control request message, and the first control request message carries the identifier of the target tunnel, the tunnel keep-alive sequence number of the reset target tunnel, and the sequence number reset indication information; the UP device receives the remote network The first control response packet sent by the device is used to indicate that the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel.
  • the method further includes: the UP device creates a data reconciliation tunnel with the remote network device; the UP device sends a data reconciliation tunnel to the remote network device through the data reconciliation tunnel. Send the first tunnel data reconciliation message, where the first tunnel data reconciliation message carries the identifier of the tunnel established between the UP device and the remote network device; the UP device receives the first tunnel pair sent by the remote network device.
  • the first tunnel account reconciliation response message carries the identifier of the tunnel established between the remote network device and the UP device; the UP device compares the tunnel identifier carried in the first tunnel data reconciliation message with the first The intersection of the tunnel identifiers carried in a tunnel reconciliation response packet is determined as the identifiers of one or more tunnels.
  • the UP device before resetting the tunnel keep-alive serial number between the UP device and the remote network device, the UP device first performs data reconciliation with the remote network device to ensure that the UP device and the remote Tunnel consistency between network devices, so that the UP device can more accurately keep the tunnel alive.
  • the CP device when the communication between the UP device and the CP device is normal, the CP device also sends the first session information to the UP device, that is, the UP device sends the information about the one or more tunnels to the UP device according to the first tunnel information.
  • the method further includes: the UP device receives the first session information sent by the CP device, and the first session information includes the information of the sessions carried on the one or more tunnels. In this way, the UP device creates a connection with the remote network device.
  • the UP device After the data reconciliation tunnel between the two, it also includes: the UP device sends a first session data reconciliation message to the remote network device, where the first session data reconciliation message carries one or more identifiers of the first reference session, the one or multiple first reference sessions are sessions carried on the target tunnel stored on the UP device; the UP device receives the first session reconciliation response message sent by the remote network device, and the first session reconciliation response message carries one or more identifiers of the one or more second reference sessions, where the one or more second reference sessions are sessions carried on the target tunnel stored on the remote network device; the UP device associates the identifiers of the one or more first reference sessions with one or more The second reference is the intersection of the identifiers of the sessions, and is determined to be the identifiers of the sessions carried on the target tunnel.
  • the UP device can also update the information of the session carried on the target tunnel in the first session information, so as to perform fault recovery on the session carried on the target tunnel.
  • tunnel failure recovery and session failure recovery are used between the UP device and the remote network device to ensure the consistency of the tunnels and sessions between the UP device and the remote network device, and can more accurately The tunnel established between the UP device and the remote network device is kept alive.
  • the UP device can The tunnel keep-alive is performed according to the same tunnel keep-alive method as that of the target tunnel, which is not repeated in this embodiment of the present application.
  • the method further includes: if the UP device detects that the communication between itself and the CP device is restored, the UP device stops Tunnel keep-alive is performed on the one or more tunnels, and the CP device needs to perform the tunnel keep-alive on the one or more tunnels again.
  • the method further includes: the UP device receives the second tunnel information sent by the CP device, and the second tunnel information includes the information stored on the CP device at the first moment. information about one or more tunnels established between the UP device and the remote network device.
  • the first moment means that after the communication between the UP device and the CP device is restored, the CP device completes the process between the UP device and the remote network device. The moment when the tunnel fault is restored or the session is restored from the fault; the UP device updates the locally stored tunnel information according to the second tunnel information.
  • the tunnel information is synchronized to the UP device again to ensure that the tunnel information stored on the UP device is consistent with the CP device, so as to prepare for subsequent UP devices to communicate with the CP device. Communication between CP devices fails again.
  • the second tunnel information is carried in the PFCP update request message. That is, in the embodiment of the present application, the PFCP update request message carrying the second tunnel information is obtained by extending the PFCP.
  • a tunnel keep-alive method is provided.
  • the control plane CP device and the user plane UP device are used to interact with remote network devices to ensure that terminals access the network.
  • the method includes:
  • the CP device sends the first tunnel information to the UP device, where the first tunnel information includes information about one or more tunnels established between the UP device and the remote network device; if the CP device detects that the communication between itself and the UP device is faulty , the CP device stops the tunnel keep-alive for the one or more tunnels; wherein, the first tunnel information is used by the UP device when detecting that the communication between itself and the CP device is faulty, according to the first tunnel information to the UP device. Tunnel keep-alive with one or more tunnels established between remote network devices.
  • the CP device before the communication between the UP device and the CP device fails, the CP device synchronizes the tunnel information with the UP device, and after the communication between the UP device and the CP device fails, the UP device performs tunnel keep-alive according to the tunnel information , that is, the UP device maintains the tunnel with the remote network device, so that the removal of the tunnel will not be triggered due to the communication failure between the CP device and the UP device.
  • This solution can ensure that the network connection between the terminal and the remote device will not be Therefore, it is interrupted, that is, it is ensured that user services are not damaged.
  • the CP device before the communication between the UP device and the CP device fails, there are multiple implementations for the CP device to send the first tunnel information to the UP device, and two implementations are described below.
  • the CP device synchronizes the first tunnel information to the UP device in an instant manner.
  • each time the CP device creates a tunnel it sends the information of the created tunnel to the UP device, and each time it deletes a tunnel, it sends the information of the deleted tunnel to the UP device.
  • the first tunnel information is carried in the PFCP update request message, the one or more tunnels are L2TP tunnels, and the information of each tunnel in the one or more tunnels includes tunnel description information; if the L2TP tunnel is based on IPv4 If the L2TP tunnel is created according to IPv6, the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv4 address and the tunnel remote IPv4 address; if the L2TP tunnel is created according to IPv6, the tunnel description information includes the tunnel local identifier, the tunnel remote identifier , the local IPv6 address of the tunnel, and the remote IPv6 address of the tunnel.
  • the CP device when the communication between the UP device and the CP device is normal, can also synchronize the first session information with the UP device, and the UP device receives the first session information sent by the CP device, the first session information Include information about sessions carried over the one or more tunnels.
  • the CP device synchronizes information of the created session with the UP device every time a session is created, and synchronizes the information of the deleted session with the UP device every time a session is deleted.
  • the first session information is carried in the PFCP update request message, and the session information carried on each of the one or more tunnels includes a tunnel local identifier, a session local identifier, and a session remote identifier.
  • the first tunnel information and the first session information are respectively carried in different PFCP update request packets, and one PRCP update request packet carries information of a created tunnel , or information about a deleted tunnel, or information about a created session, or information about a deleted session. Synchronizing information in a real-time manner can ensure the timeliness of information and the reliability of tunnel keep-alive.
  • the CP device periodically synchronizes the first tunnel information to the UP device.
  • the CP device synchronizes the information of all established tunnels stored by itself to the UP device every other synchronization period. Or, the CP device synchronizes the updated tunnel information to the CP device every other synchronization period, and the updated tunnel includes the information of the tunnels established and deleted after synchronizing the tunnel information last time.
  • the CP device can also periodically synchronize the first session information to the UP device. That is, in this embodiment of the present application, before the CP device stops keeping the tunnel alive, it further includes: the CP device sends first session information to the UP device, where the first session information includes information about sessions carried on the one or more tunnels. .
  • the first tunnel information and the first session information are carried in the PFCP update request message.
  • the first tunnel information and the first session information may be carried in the same PFCP update request message, or may be carried in different PFCP update request messages.
  • the first session information is carried in the PFCP update request message, and the session information carried on each of the one or more tunnels includes a tunnel local identifier, a session local identifier, and a session remote identifier.
  • the CP device communicates with the UP device through the control message redirection interface and the state control interface; the CP device detects that the communication between itself and the UP device fails, including: the CP device monitors the control message redirection interface and the UP device. The state of the state control interface; if the CP device monitors that the state of the control packet redirection interface and/or the state control interface is abnormal, the CP device determines to detect that the communication between itself and the UP device is faulty.
  • the method further includes: if the CP device detects that the communication between itself and the UP device is faulty When the communication between the UP devices is restored, the CP device performs the tunnel keep-alive for the one or more tunnels again. That is, when the communication between the CP device and the UP device is normal, the CP device still performs tunnel keep-alive, so as to reduce the load pressure of the UP device.
  • the CP device performs tunnel keep-alive again on the one or more tunnels, including: the CP device resets the locally stored tunnel keep-alive sequence number of the target tunnel, where the target tunnel is one of the one or more tunnels. one; the CP device instructs the remote network device to reset the tunnel keep-alive sequence number of the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel; the remote network device resets the tunnel keep-alive sequence number of the target tunnel After the number is reset successfully, the CP device performs tunnel keep-alive on the target tunnel through the UP device according to the reset tunnel keep-alive sequence number of the target tunnel and the identifier of the target tunnel.
  • the CP device instructs the remote network device to reset the tunnel keep-alive sequence number of the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel, including: the CP device sends a message to the remote network device through the UP device. Send a second control request packet, where the second control request packet carries the identifier of the target tunnel, the tunnel keep-alive sequence number of the reset target tunnel, and the sequence number reset indication information; the CP device receives the remote network through the UP device The second control response packet sent by the device is used to indicate that the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel.
  • the remote network device may remove some tunnels.
  • the tunnel between the device and the remote network device performs data reconciliation about the tunnel to clear the removed tunnel stored on the CP, ensure the tunnel consistency between the CP device and the remote network device, and ensure that the UP device performs tunneling. Keep-alive accuracy.
  • the CP device before the CP device resets the tunnel keep-alive sequence number of the target tunnel stored locally, it also includes: the CP device creates a data reconciliation tunnel with the remote network device; The device sends a second data reconciliation message to the remote network device, and the second data reconciliation message carries the identifier of the tunnel established between the UP device and the remote network device stored on the CP device; the CP device receives the remote network device through the UP device.
  • the second reconciliation response message sent by the end network device the second reconciliation response message carries the identifier of the tunnel established between the remote network device and the UP device; the CP device carries the second data reconciliation message
  • the intersection of the identifier of the tunnel and the identifier of the tunnel carried in the second reconciliation response packet is determined as the identifier of one or more tunnels.
  • the CP device after the CP device performs fault recovery on the target tunnel through the UP device, the CP device can also update the information of the session carried on the target tunnel stored by itself through the UP device, so as to perform fault recovery on the session carried on the target tunnel.
  • the process further includes: the CP device sends a second session data reconciliation message to the remote network device through the UP device, and the second session data reconciliation message.
  • the message carries the identifiers of one or more first reference sessions, and the one or more first reference sessions are sessions carried on the target tunnel stored on the CP device; the CP device receives the second data sent by the remote network device through the UP device.
  • Session reconciliation response message the second session reconciliation response message carries the identifiers of one or more third reference sessions, and the one or more third reference sessions are sessions carried on the target tunnel stored on the remote network device ;
  • the CP device determines the intersection of the identifiers of the one or more first reference sessions and the identifiers of the one or more third reference sessions as the identifiers of the sessions carried on the target tunnel. That is, the CP device updates the information of the session carried on the target tunnel stored by itself through the UP device, so as to perform fault recovery on the session carried on the target tunnel.
  • the remote network device may also remove sessions on some tunnels, and the session failure between the CP device and the remote network device may occur. Recovery, reconciling the session data between the UP device and the remote network device, that is, clearing the session that has been removed stored on the CP, to ensure the session consistency between the CP device and the remote network device.
  • the CP device can perform tunnel failure recovery and session failure recovery according to the same failure recovery method as the target tunnel, which is no longer required in this embodiment of the present application. Repeat.
  • the method further includes: the CP device sends the second tunnel information to the UP device, and the second tunnel information is sent to the UP device.
  • the tunnel information includes the information of one or more tunnels established between the UP device and the remote network device stored on the CP device at the first moment.
  • the first moment means that after the communication between the UP device and the CP device is restored, the CP device passes the The time when tunnel failure recovery or session failure recovery is completed between the UP device and the remote network device. That is, the CP device synchronizes the tunnel information with the UP device again, in case the communication between the UP device and the CP device fails again, and the UP device keeps the tunnel alive.
  • the second tunnel information is carried in the PFCP update request message.
  • the method further includes: the CP device sends second session information to the UP device, where the second session information includes the data stored on the CP device at the second moment.
  • Information about sessions carried on one or more tunnels established between the UP device and the remote network device That is, the CP device synchronizes the session information to the UP device again, in case the communication between the UP device and the CP device fails again, the UP device will keep the tunnel alive and realize the session communication of the terminal.
  • the second session information is carried in the PFCP update request message.
  • the second tunnel information and the second session information are carried in one PFCP update request message, or carried in different PFCP update request messages.
  • the CP device after sending the PFCP update request message carrying the second tunnel information and/or the second session information to the UP device, the CP device receives the PFCP update response message sent by the UP device.
  • the CP device and the remote network device perform tunnel failure recovery and session failure sessions, after synchronizing the tunnel information and session information with the UP device once, it continues to send the UP device to the UP device in an instant or periodic manner.
  • the device synchronizes the latest tunnel information and session information in case of another communication failure between the UP device and the CP device.
  • a network device in a third aspect, has a function of implementing the behavior of the tunnel keep-alive method in the first aspect.
  • the network device includes one or more modules, and the one or more modules are used to implement the tunnel keep-alive method provided in the first aspect.
  • a network device is provided, the network device is applied to a network system, the network system includes a CP device and a UP device, and the CP device and the UP device are used to interact with the remote network device to ensure that the terminal accesses the network,
  • the network device is a UP device, and the network device includes:
  • a first receiving module configured to receive first tunnel information sent by the CP device, where the first tunnel information includes information of one or more tunnels established between the UP device and the remote network device;
  • the tunnel keep-alive module is configured to perform tunnel keep-alive for the one or more tunnels according to the first tunnel information if it is detected that the communication between the UP device and the CP device fails.
  • the first tunnel information includes identifiers of one or more tunnels
  • the tunnel keep-alive module includes:
  • a monitoring unit configured to monitor the first tunnel keep-alive message sent by the remote network device, where the first tunnel keep-alive message carries the identifier of the target tunnel and the tunnel keep-alive sequence number;
  • the first sending unit is configured to send the second tunnel keep-alive message to the remote network device according to the tunnel keep-alive sequence number of the target tunnel and the identifiers of the one or more tunnels.
  • the first tunnel information includes identifiers of one or more tunnels
  • the tunnel keep-alive module includes:
  • a reset unit used to reset the tunnel keep-alive sequence number of the target tunnel, where the target tunnel is one of the one or more tunnels;
  • an instruction unit configured to instruct the remote network device to reset the tunnel keep-alive sequence number of the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel;
  • the tunnel keep-alive unit is used to tunnel the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel and the identifier of the target tunnel after the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel. keep alive.
  • the indicating unit is specifically used for:
  • the remote network device sends a first control request message to the remote network device, where the first control request message carries the identifier of the target tunnel, the tunnel keep-alive sequence number of the reset target tunnel, and the sequence number reset indication information;
  • a first control response packet sent by the remote network device is received, where the first control response packet is used to indicate that the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel.
  • the tunnel keep-alive module further includes:
  • a creation unit is used to create a data reconciliation tunnel with a remote network device
  • the second sending unit is configured to send a first tunnel data reconciliation message to the remote network device through the data reconciliation tunnel, where the first tunnel data reconciliation message carries the data stored on the UP device and the remote network device. the identity of the established tunnel;
  • a first receiving unit configured to receive the first tunnel account reconciliation response message sent by the remote network device, where the first tunnel account reconciliation response message carries the identifier of the tunnel established between the remote network device and the UP device;
  • the first determining unit is configured to determine the intersection of the identifier of the tunnel carried in the first tunnel data reconciliation message and the identifier of the tunnel carried in the first tunnel reconciliation response message as the identifier of the one or more tunnels.
  • the network device further includes:
  • a second receiving module configured to receive first session information sent by the CP device, where the first session information includes information about sessions carried on the one or more tunnels;
  • the tunnel keep-alive module also includes:
  • a third sending unit configured to send a first session data reconciliation message to the remote network device, where the first session data reconciliation message carries the identifiers of one or more first reference sessions, the one or more first reference The session is the session carried on the target tunnel stored on the UP device;
  • the second receiving unit is configured to receive the first session reconciliation response message sent by the remote network device, where the first session reconciliation response message carries one or more identifiers of the second reference session, the one or more second The reference session is the session carried on the target tunnel stored on the remote network device;
  • the second determining unit is configured to determine the intersection of the identifiers of the one or more first reference sessions and the identifiers of the one or more second reference sessions as the identifiers of the sessions carried on the target tunnel.
  • the network device further includes:
  • the processing module is configured to stop the tunnel keep-alive for the one or more tunnels if it is detected that the communication between the UP device and the CP device is restored.
  • the network device further includes:
  • the third receiving module is configured to receive the second tunnel information sent by the CP device.
  • the second tunnel information includes the information of one or more tunnels established between the UP device and the remote network device stored on the CP device at the first moment.
  • a moment refers to the moment when the communication between the UP device and the CP device is restored, and the CP device completes the tunnel failure recovery or session failure recovery between the UP device and the remote network device;
  • An update module configured to update the locally stored tunnel information according to the second tunnel information.
  • the UP device communicates with the CP device through the control packet redirection interface and the state control interface;
  • the tunnel keep-alive module includes:
  • the monitoring unit is used to monitor the status of the control packet redirection interface and the status control interface
  • the third determining unit is configured to determine that a failure has been detected in the communication between the UP device and the CP device if it is monitored that the state of the control packet redirection interface and/or the state control interface is abnormal.
  • the first tunnel information is carried in the PFCP update request message, the one or more tunnels are L2TP tunnels, and the information of each tunnel in the one or more tunnels includes tunnel description information;
  • the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv4 address and the tunnel remote IPv4 address;
  • the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv6 address and the tunnel remote IPv6 address.
  • the second tunnel information is carried in the PFCP update request message.
  • the first session information is carried in the PFCP update request message, and the session information carried on each of the one or more tunnels includes a tunnel local identifier, a session local identifier, and a session remote identifier.
  • a network device in a fourth aspect, has a function of implementing the behavior of the tunnel keep-alive method in the second aspect.
  • the network device includes one or more modules, and the one or more modules are used to implement the tunnel keep-alive method provided in the second aspect above.
  • a network device is provided, the network device is applied to a network system, the network system includes a CP device and a UP device, and the CP device and the UP device are used to interact with the remote network device to ensure that the terminal accesses the network,
  • the network device is a CP device, and the network device includes:
  • a first sending module configured to send first tunnel information to the UP device, where the first tunnel information includes information of one or more tunnels established between the UP device and the remote network device;
  • a processing module configured to stop the tunnel keep-alive for the one or more tunnels if it is detected that the communication between the CP device and the UP device fails;
  • the first tunnel information is used to instruct the UP device to keep the tunnels for one or more tunnels established between the UP device and the remote network device when it detects that the communication between itself and the CP device is faulty.
  • the network device further includes:
  • the tunnel keep-alive module is used for re-tunnel keep-alive for one or more tunnels if it is detected that the communication between the CP device and the UP device is restored.
  • the tunnel keep-alive module includes:
  • a reset unit used to reset the tunnel keep-alive sequence number of the locally stored target tunnel, where the target tunnel is one of the one or more tunnels;
  • an instruction unit configured to instruct the remote network device to reset the tunnel keep-alive sequence number of the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel;
  • the tunnel keep-alive unit is used for, after the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel, according to the reset tunnel keep-alive sequence number of the target tunnel and the identifier of the target tunnel, through the UP device to the target tunnel
  • the tunnel performs tunnel keep-alive.
  • the indicating unit is specifically used for:
  • the second control response packet sent by the remote network device is received by the UP device, where the second control response packet is used to indicate that the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel.
  • the tunnel keep-alive module further includes:
  • a creation unit is used to create a data reconciliation tunnel with a remote network device
  • the first sending unit is configured to send a second data reconciliation message to the remote network device through the UP device through the data reconciliation tunnel, and the second data reconciliation message carries the UP device stored on the CP device and the remote network device.
  • the first receiving unit is configured to receive, through the UP device, a second reconciliation response message sent by the remote network device, where the second reconciliation response message carries the identifier of the tunnel established between the remote network device and the UP device. ;
  • the first determining unit is configured to determine the intersection of the identifier of the tunnel carried in the second data reconciliation message and the identifier of the tunnel carried in the second reconciliation response message as the identifier of one or more tunnels.
  • the tunnel keep-alive module further includes:
  • the second sending unit is configured to send a second session data reconciliation message to the remote network device through the UP device, where the second session data reconciliation message carries one or more identifiers of the first reference session, the one or more The first reference session is a session carried on the target tunnel stored on the CP device;
  • the second receiving unit is configured to receive, through the UP device, a second session reconciliation response message sent by the remote network device, where the second session reconciliation response message carries one or more identifiers of the third reference session, the one or more The third reference session is the session carried on the target tunnel stored on the remote network device;
  • the second determining unit is configured to determine the intersection of the identifiers of the one or more first reference sessions and the identifiers of one or more third reference sessions as the identifiers of the sessions carried on the target tunnel.
  • the tunnel keep-alive module further includes:
  • the third sending unit is configured to send the second tunnel information to the UP device, where the second tunnel information includes the information of one or more tunnels established between the UP device and the remote network device stored on the CP device at the first moment, and the first The time refers to the time when the CP device completes the tunnel failure recovery or session failure recovery between the UP device and the remote network device after the communication between the UP device and the CP device is restored.
  • the CP device communicates with the UP device through a control packet redirection interface and a state control interface;
  • Processing modules include:
  • the monitoring unit is used to monitor the status of the control packet redirection interface and the status control interface
  • the third determining unit is configured to determine that a failure occurs in the communication between the CP device and the UP device if it is monitored that the state of the control packet redirection interface and/or the state control interface is abnormal.
  • the first tunnel information is carried in the PFCP update request message, the one or more tunnels are Layer 2 tunneling protocol L2TP tunnels, and the information of each tunnel in the one or more tunnels includes tunnel description information;
  • the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv4 address and the tunnel remote IPv4 address;
  • the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv6 address and the tunnel remote IPv6 address.
  • the second tunnel information is carried in the PFCP update request message.
  • the network device further includes:
  • the fourth sending module is configured to send first session information to the UP device, where the first session information includes information of sessions carried on the one or more tunnels.
  • the first session information is carried in the PFCP update request message, and the session information carried on each of the one or more tunnels includes a tunnel local identifier, a session local identifier, and a session remote identifier.
  • the first sending module includes:
  • the fifth sending unit configured to send the information of the created tunnel to the UP device every time a tunnel is created, and the one or more tunnels include the created tunnel; or,
  • the sixth sending unit is configured to periodically send the information of the tunnel stored by itself to the UP device.
  • a fifth aspect provides a network device, the network device is applied to a network system, the network system includes a UP device and a CP device, and the CP device and the UP device are used to interact with remote network devices to ensure terminal access A network, where the network device is a UP device, and the network device includes a processor and a memory, where the memory is used for storing a program for executing the tunnel keep-alive method provided in the first aspect, and for implementing the first aspect.
  • the processor is configured to execute programs stored in the memory.
  • the operating means of the storage device may further include a communication bus for establishing a connection between the processor and the memory.
  • a sixth aspect provides a network device, the network device is applied to a network system, the network system includes a UP device and a CP device, and the CP device and the UP device are used to interact with remote network devices to ensure terminal access.
  • a network the network device is a CP device, the network device includes a processor and a memory, the memory is used for storing a program for executing the tunnel keep-alive method provided in the second aspect, and for implementing the second aspect. The data involved in the provided tunnel keepalive method.
  • the processor is configured to execute programs stored in the memory.
  • the operating means of the storage device may further include a communication bus for establishing a connection between the processor and the memory.
  • a network system in a seventh aspect, includes a CP device, a UP device, and a remote network device, the CP device and the UP device are used to interact with the remote network device to ensure that the terminal access the network;
  • the UP device is used to implement the tunnel keep-alive method provided by the first aspect
  • the CP device is configured to implement the tunnel keep-alive method provided in the second aspect.
  • a computer-readable storage medium where instructions are stored in the computer-readable storage medium, when the computer-readable storage medium runs on a computer, the computer is made to execute the tunnel protection described in the first aspect or the second aspect. live method.
  • a computer program product containing instructions, which, when executed on a computer, cause the computer to execute the tunnel keep-alive method described in the first aspect or the second aspect.
  • the UP device before the communication failure between the UP device and the CP device, the UP device receives the tunnel information synchronized by the CP device, and after the communication between the UP device and the CP device fails, the UP device performs tunnel protection according to the tunnel information. In other words, the UP device maintains the tunnel with the remote network device, so that the tunnel removal will not be triggered due to the communication failure between the CP device and the UP device.
  • This solution can ensure that the network connection between the terminal and the remote device is not Therefore, it will be interrupted, that is, to ensure that user services are not damaged.
  • FIG. 1 is a system architecture diagram involved in a tunnel keep-alive method provided by an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • FIG. 3 is a flowchart of a method for keeping a tunnel alive according to an embodiment of the present application
  • FIG. 4 is a flowchart of another tunnel keep-alive method provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of communication between modules included in a CP device and a UP device provided by an embodiment of the present application;
  • FIG. 6 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of another network device provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of another network device provided by an embodiment of the present application.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • the evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • FIG. 1 is a system architecture diagram involved in a tunnel keep-alive method provided by an embodiment of the present application.
  • the system architecture includes a terminal 101 , a CP device 102 and a UP device 103 , a remote network device 104 and a remote access point 105 .
  • a communication connection is established between the terminal 101 and the UP device 103, a communication connection is established between the UP device 103 and the remote network device 104, a communication connection is established between the CP device 102 and the UP device 103, and the remote network device 104 is connected to the remote network device 104.
  • a communication connection is established between the end access points 105 .
  • the local CP device 102 and the UP device 103 jointly implement the LAC function
  • the remote network device 104 implements the LNS function
  • the local CP device 102 can communicate between the UP device 103 and the remote network.
  • a tunnel and a session are established between the devices 104 to ensure that the terminal 101 successfully accesses the network provided by the remote access point 105 and implements service communication.
  • the tunnel between the UP device 103 and the remote network device 104 needs to be kept alive.
  • the CP device 102 is used to establish a tunnel between the UP device 103 and the remote network device 104 and a session carried on the tunnel, and then the terminal 101 Access the remote network, and the CP device 102 through the UP device 103 performs tunnel keep-alive on the tunnel established between the UP device 103 and the remote network device 104 to ensure that user services are not interrupted.
  • the UP device 103 is further configured to transmit the data message between the terminal 101 and the remote network device 104 on the session carried by the tunnel, so as to realize the service communication between the terminal 101 and the remote network device 104 .
  • the CP device 102 and the UP device 103 are used to interact with the remote network device 104 to ensure that the terminal 101 accesses the network.
  • the CP device 102 is further configured to synchronize the tunnel information and session information to the UP device 103 according to the tunnel keep-alive method provided by the embodiment of the present application.
  • the CP device 102 cannot continue to interact with the remote network device 104 through the UP device 103 to keep the tunnel alive.
  • Tunnel information the tunnel between the UP device 103 and the remote network device 104 is kept alive to ensure that the tunnel will not be dismantled due to the communication failure between the UP device 103 and the CP device 102, so as to maintain the tunnel and ensure that the Hosted sessions are not interrupted.
  • the UP device 103 stops the tunnel keep-alive, the CP device 102 continues to perform the tunnel keep-alive between the UP device 103 and the remote network device 104, and the CP device 102 saves itself During the process of keeping the tunnel alive with the remote network device 104 , the stored tunnel information is synchronized to the UP device 103 .
  • the system architecture includes multiple terminals, as well as a remote network device and a remote access point corresponding to each terminal.
  • a remote network device and a remote access point corresponding to each terminal.
  • only one terminal and a corresponding remote network device and remote access point are used. Click as an example to introduce.
  • both the CP device and the UP device can implement the above functions.
  • the remote network device 104 is a traditional BNG device, that is, the remote network device 104 is an independent gateway device.
  • the remote network device 104 is also implemented through vBNG, that is, it includes a CP device and a UP device.
  • the CP device 102 and UP device 103 at the local end are referred to as CP-LAC and UP respectively.
  • CP-LAC the remote CP equipment and UP equipment are called CP-LNS and UP-LNS respectively
  • CP-LAC is connected to UP-LAC
  • UP-LAC is connected to UP-LNS
  • UP-LNS is connected to CP-LNS communication connection.
  • a virtual broadband remote access server can also implement the same function as the vBNG, that is, the vBRAS includes a CP device and an UP device, and the CP device and the UP device are used to connect the terminal of the local end.
  • the remote network is accessed, and the tunnel keep-alive method is implemented according to the tunnel keep-alive method provided in the embodiment of the present application.
  • the terminal 101 is a mobile phone, a computer, a home gateway and other devices
  • the UP device 103 is a router, a switch and other devices
  • the CP device 102 is a server, or a server cluster composed of multiple servers, or a cloud
  • the remote network device 104 is an independent device such as a router and a switch, or the remote network device 104 includes a UP device and a CP device
  • the remote access point 105 is a device that provides a broadband network.
  • FIG. 2 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • the network device is the CP device or the UP device shown in FIG. 1 , and the network device includes one or more processors 201, a communication bus 202, a memory 203, and one or more communication interfaces 204.
  • the processor 201 is a general-purpose central processing unit (CPU), a network processor (NP), a microprocessor, or one or more integrated circuits for implementing the solution of the present application, for example, an application-specific integrated circuit ( application-specific integrated cirCPit, ASIC), programmable logic device (programmable logic device, PLD) or a combination thereof.
  • the above-mentioned PLD is a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL) or any of them. combination.
  • the communication bus 202 is used to transfer information between the aforementioned components.
  • the communication bus 202 is divided into an address bus, a data bus, a control bus, and the like.
  • address bus a data bus
  • control bus a control bus
  • only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.
  • the memory 203 is a read-only memory (read-only memory, ROM), a random access memory (random access memory, RAM), an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM) , optical disc (including compact disc read-only memory, CD-ROM, compact disc, laser disc, digital versatile disc, Blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or can be used for portable or any other medium that stores desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory 203 exists independently and is connected to the processor 201 through the communication bus 202, or the memory 203 is integrated with the processor 201.
  • the Communication interface 204 uses any transceiver-like device for communicating with other devices or a communication network.
  • the communication interface 204 includes a wired communication interface and, optionally, a wireless communication interface.
  • the wired communication interface is, for example, an Ethernet interface.
  • the Ethernet interface is an optical interface, an electrical interface or a combination thereof.
  • the wireless communication interface is a wireless local area network (wireless local area network, WLAN) interface, a cellular network communication interface, or a combination thereof.
  • WLAN wireless local area network
  • the network device includes multiple processors, such as processor 201 and processor 205 as shown in FIG. 2 .
  • processors such as processor 201 and processor 205 as shown in FIG. 2 .
  • Each of these processors is a single-core processor, or a multi-core processor.
  • a processor herein refers to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the network device further includes an output device 206 and an input device 207 .
  • the output device 206 is in communication with the processor 201 and can display information in a variety of ways.
  • the output device 206 is a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, a projector, or the like.
  • the input device 207 communicates with the processor 201 and can receive user input in a variety of ways.
  • the input device 207 is a mouse, a keyboard, a touch screen device, a sensor device, or the like.
  • the memory 203 is used to store the program code 210 for executing the solutions of the present application, and the processor 201 can execute the program code 210 stored in the memory 203 .
  • the program code includes one or more software modules, and the network device can implement the tunnel keep-alive method provided in the embodiment of FIG. 3 below through the processor 201 and the program code 210 in the memory 203 .
  • the memory 203 is used to store program code 210
  • the processor 201 is used to execute the program code 210 stored in the memory 203 to implement the corresponding function of the UP device in the tunnel keep-alive method provided by the embodiment of the present application . That is, if the first tunnel information sent by the CP device is received, if it is detected that the communication between the UP device and the CP device fails, the tunnel keep alive according to the first tunnel information.
  • FIG. 3 refer to the detailed introduction in the embodiment of FIG. 3 below, which is not repeated here.
  • the program code 210 may include the first receiving module and the tunnel keep-alive module, the first A receiving module is configured to receive the first tunnel information sent by the CP device, and the tunnel keep-alive module is configured to perform tunnel keep-alive according to the first tunnel information.
  • the memory 203 is used to store the program code 210
  • the processor 201 is used to execute the program code 210 stored in the memory 203, so as to realize the corresponding function of the CP device in the tunnel keep-alive method provided by the embodiment of the present application . That is, the first tunnel information is sent to the UP device, and if it is detected that the communication between the CP device and the UP device fails, the tunnel keep-alive is stopped.
  • FIG. 3 refer to the detailed introduction in the embodiment of FIG. 3 below, which is not repeated here.
  • the program code 210 may include the first sending module, the processing module and the tunnel keep-alive module, the first sending module is used to send the first tunnel information to the UP device, the processing module is used to stop the tunnel keep-alive after detecting that the communication between the CP device and the UP device fails, and the tunnel keep-alive module It is used to restart the tunnel keep alive after detecting that the communication between the CP device and the UP device is restored.
  • FIG. 3 is a flowchart of a method for keeping a tunnel alive according to an embodiment of the present application. Please refer to FIG. 3 , the method includes the following steps.
  • Step 301 The UP device receives the first tunnel information sent by the CP device, where the first tunnel information includes information of one or more tunnels established between the UP device and the remote network device.
  • the CP device and the UP device are used to interact with the remote network device to ensure that the terminal accesses the network.
  • the terminal can establish a communication connection through the channel established between the local CP device and the UP device and the remote network device.
  • a tunnel and a session carried on the tunnel are established between the UP device and the remote network device to ensure that the terminal accesses the remote network and realizes service communication.
  • the terminal can send a connection request to the UP device to request access to the data provided by the remote access point managed by the remote network device under the condition that no communication failure occurs between the UP device and the CP device.
  • the UP device forwards the connection request to the CP device, and the CP device performs user authentication on the connection request to determine the remote network device corresponding to the network the terminal requests to access.
  • a tunnel and a session carried on the tunnel are established between the device and the remote network device, and the terminal is successfully connected to the network through the session on the tunnel, and service communication is realized.
  • a terminal of a lottery point wants to access the network of the lottery center of the corporate headquarters.
  • the terminal sends a connection request to the UP device included in the vBNG of the local operator through broadband dial-up.
  • the CP device performs user authentication according to the connection request and determines For the remote network device corresponding to the network of the lottery center requested by the terminal, after the CP device has passed the user authentication, a tunnel and a session carried on the tunnel are established between the UP device and the remote network device.
  • the terminal is successfully connected to the network of the lottery center through this session.
  • the terminal After the terminal successfully accesses the network, the terminal implements service communication through the session carried on the tunnel maintained between the UP device and the remote network device.
  • the CP device exchanges tunnel keep-alive messages between the UP device and the remote network device to keep the tunnel between the UP device and the remote network device, that is, maintains the connection between the UP device and the remote network device. It ensures that the tunnel and the session carried on the tunnel are not interrupted, that is, the terminal service is not interrupted.
  • the UP device ensures that the service communication of the terminal is maintained on the session carried by the tunnel by forwarding the data packets between the terminal and the remote network device.
  • the CP device can also synchronize the information of the tunnel stored by itself to the UP device. That is, in this embodiment of the present application, the CP device sends the first tunnel information to the UP device, where the first tunnel information includes information of one or more tunnels established between the UP device and the remote network device. It should be noted that there are multiple implementation manners for the CP device to send the first tunnel information to the UP device, and two implementation manners of which are exemplarily described below.
  • the CP device synchronizes the first tunnel information to the UP device in an instant manner.
  • each time the CP device creates a tunnel it sends the information of the created tunnel to the UP device, and each time it deletes a tunnel, it sends the information of the deleted tunnel to the UP device.
  • the first tunnel information is carried in the PFCP update request message
  • the one or more tunnels are L2TP tunnels
  • the information of each tunnel in the one or more tunnels includes tunnel description information. If the L2TP tunnel is created according to IPv4, the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv4 address and the tunnel remote IPv4 address. If the L2TP tunnel is created according to IPv6, the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv6 address and the tunnel remote IPv6 address. The tunnel local identifier and the tunnel remote identifier are the identifiers of the tunnel.
  • the first tunnel information may be carried in any communication protocol packet.
  • the PFCP update request message is obtained by extending the PFCP protocol.
  • a node-level message (node message) specified by PFCP is extended to obtain a PFCP update request message.
  • Table 1 is the node message specified by the extended PFCP, and the PFCP update request message also carries a message type, which can take any value between 16 and 49, and the message type is used to indicate that the corresponding message is a PFCP update.
  • Request message also known as PFCP L2TP Tunnel Update Request.
  • the PFCP update request message includes a group information element (grouped information element, Grouped IE), and a Grouped IE includes one or more embedded information elements Embedded IE. unit, each Embedded IE carries a tunnel description information, and by extending the Grouped IE, a PFCP update request message is obtained.
  • group information element group information element
  • Grouped IE group information element
  • Embedded IE includes one or more embedded information elements Embedded IE. unit, each Embedded IE carries a tunnel description information, and by extending the Grouped IE, a PFCP update request message is obtained.
  • Table 3 is an introduction to the tunnel information carried in the PFCP update request message.
  • the PFCP update request message also carries the device number of the CP device, that is, the node identification (Node ID) of the CP device.
  • the PFCP update request message also carries the tunnel description information of each created tunnel.
  • the PFCP update request message also carries the tunnel description information of each deleted tunnel.
  • the PFCP update request packet also carries the name of the L3VPN instance, that is, the private network name of the L3VPN.
  • Table 4 is the structure description of the PFCP update request message obtained by extending the Grouped IE.
  • the first 2 bytes of the PFCP update request packet (one Octet is 8 bits, that is, one byte) carry the tunnel message type (message type), the third and fourth bytes Carrying the length (length), used to indicate the length of the message, the 5th and 6th bytes carry the enterprise ID (enterprise ID), which indicates which company the message is extended by, starting from the 7th byte, carrying the creation or deletion
  • the tunnel description information of the tunnel optionally, if L2TP traverses L3VPN, also carries the name of the L3VPN instance.
  • Table 5 is a schematic structural diagram of a PFCP update request message carrying tunnel description information obtained by extending the Embedded IE.
  • Ver indicates the version number of the L2TP tunnel.
  • the value is 2, indicating the L2TPV2 version.
  • the tunnel identification (tunnel ID) is a 16-bit unsigned integer.
  • the value is 3, indicating the L2TPV3 version.
  • the tunnel ID is a 32-bit unsigned integer.
  • Bits 7 to 8 of the 7th byte reserved fields, set to 0.
  • Tunnel local IPv4 address (local IPv4 address).
  • the CP device can also send the first session information to the UP device, and the UP device Receive first session information sent by the CP device, where the first session information includes session information carried on the one or more tunnels, that is, the CP device synchronizes the session information to the UP device.
  • the first session information is also carried in the PFCP update request message, and the session information carried on each of the one or more tunnels includes a tunnel local identifier, a session local identifier, and a session remote identifier.
  • the PFCP update request message in the PFCP update request message carrying the first session information, includes a Grouped IE, a Grouped IE includes one or more Embedded IEs, and each Embedded IE carries a session information, and by extending the Grouped IE, a PFCP update request message carrying the first session information is obtained.
  • Table 8 describes the session information carried in the PFCP update request message.
  • the PFCP update request message carries the device number of the CP device, that is, the node identifier of the CP device.
  • the PFCP update request message The message also carries the information of each created session.
  • the PFCP update request message In the case of deleting the L2TP session, the PFCP update request message also carries the information of each deleted session.
  • Table 9 is the structure description of the PFCP update request message obtained by extending the Grouped IE.
  • the first 2 bytes (Octet) carry the session message type
  • the 3rd and 4th bytes carry the length, which are used to indicate the length of the message
  • the 5th and 6th bytes carry the manufacturer number. , indicating which manufacturer extended the packet, starting from the 7th byte, and carrying information about the session created or deleted.
  • Table 10 is a schematic structural diagram of a PFCP update request message carrying information of a session obtained by extending the embedded IE.
  • bits 1 to 4 Ver of the 7th byte indicate the version number of the L2TP tunnel.
  • the value is 2, which indicates the L2TPV2 version.
  • the session ID (session ID) is a 16-bit unsigned integer.
  • the value is 3, indicating the L2TPV3 version.
  • the session ID is a 32-bit unsigned integer.
  • Bits 5 to 8 of the 7th byte reserved fields, set to 0.
  • session remote ID local session ID
  • 32-bit unsigned integer valid for L2TPV2 version 16-bit lower.
  • the first tunnel information and the first session information are respectively carried in different PFCP update request packets, and one PRCP update request packet carries the information of a created tunnel, or deletes it. information about a tunnel, or a created session, or a deleted session.
  • the UP device After receiving the PFCP update request message carrying the information of the created tunnel or session, the UP device locally stores the information of the created tunnel or session, and the UP device receives the PFCP update request message carrying the information of the deleted tunnel or session. After the message is sent, the corresponding tunnel or session information stored locally is deleted.
  • the CP device periodically synchronizes the first tunnel information to the UP device.
  • the CP device synchronizes the information of all established tunnels stored by itself to the UP device every other synchronization period. Or, the CP device synchronizes the updated tunnel information to the CP device every other synchronization period, and the updated tunnel includes the information of the tunnels established and deleted after synchronizing the tunnel information last time.
  • the first tunnel information is carried in the PFCP update request message. If the CP device stores information about multiple established tunnels, then the first tunnel information includes information about multiple established tunnels, and information about each tunnel. Include tunnel description information.
  • the CP device can also periodically synchronize the first session information to the UP device, and the first session information is carried in the PFCP update request message.
  • the PFCP update request message For the relevant description of the PFCP update request message, refer to the foregoing related introduction, and details are not repeated here.
  • the first tunnel information and the first session information may be carried in the same PFCP update request message, or may be carried in different PFCP update request messages.
  • the CP device synchronizes the information of all established tunnels and sessions stored by the CP device to the UP device through a PFCP update request message every other synchronization period. Or, every synchronization period, the CP device synchronizes the information of all established tunnels stored by itself to the UP device through a PFCP update request message, and synchronizes the information of all sessions stored by itself to the UP device through another PFCP update request message.
  • UP equipment
  • the UP device after receiving the PFCP update request message, can send a PFCP update response message to the CP device.
  • the PFCP update response message carries a message type, and the message type can take any value between 16-49 that is different from the message type carried in the PFCP update request message, and the message type is used to indicate
  • the corresponding message is a PFCP update response message, also known as a PFCP L2TP tunnel update response.
  • the PFCP update response message also carries the device number of the UP device, that is, the node identifier of the UP device, and the PFCP update response message also carries the processing result (also called cause), which is used to indicate whether the UP device is successful or not. Parse the PFCP update request message.
  • Step 302 If the communication between the UP device and the CP device fails, the UP device performs tunnel keep-alive on the one or more tunnels according to the first tunnel information, and the CP device stops tunneling on the one or more tunnels. keep alive.
  • the UP device and the CP device communicate through multiple communication interfaces, for example, the CP in the vBNG defined in the Broadband-forum (BBF) WT-459 (also referred to as TR-459)
  • the communication interface between the device and the UP device including the control packet redirection interface (CPRi) and the state control interface (state control interface, SCi).
  • the UP device uses the control packet redirection interface and the state control interface. Communicates with the CP device, and the UP device monitors the status of the control packet redirection interface and the status control interface. If the UP device monitors the abnormal status of the control packet redirection interface and/or the status control interface, the UP device determines that it has detected itself. Communication with the CP device has failed.
  • the CP device communicates with the UP device through the control packet redirection interface and the status control interface.
  • the CP device monitors the status of the control packet redirection interface and the status control interface. If the CP device monitors the control packet redirection interface and the status control interface /or the state of the state control interface is abnormal, the CP device determines to detect that the communication between itself and the UP device is faulty.
  • the UP device if the UP device detects that the communication between itself and the CP device is faulty, the UP device performs tunnel keep-alive for the one or more tunnels according to the first tunnel information. If the CP device detects that it When the communication with the UP device fails, the CP device stops the tunnel keep-alive for the one or more tunnels.
  • each tunnel performs tunnel keep-alive independently, that is, each tunnel corresponds to a tunnel keep-alive sequence number, and the UP device or the CP device interacts with the remote network device to keep the tunnel alive.
  • the tunnel keep-alive sequence number includes a sending sequence number and an expected receiving sequence number. For example, for a tunnel, it is assumed that the UP device sends a tunnel keep-alive message to the remote network device, and the tunnel keep-alive message is Carry the packet with the sending sequence number 0 and the expected receiving sequence number 0. After receiving the tunnel keep-alive packet, the remote network device sends the UP device with the sending sequence number 0 and the expected receiving sequence number 1.
  • the tunnel keep-alive message the UP device continues to send the tunnel keep-alive message carrying the sending sequence number 1 and the expected receiving sequence number 1 to the remote network device, and the remote network device sends the UP device carrying the sending sequence number 1 and 1. It is expected to receive a tunnel keep-alive packet with a sequence number of 2, and so on.
  • the UP device and the remote network device periodically send a tunnel keep-alive message carrying the tunnel keep-alive sequence number to keep the tunnel alive. If the remote network device does not receive the expected tunnel keep-alive message within the timeout period, the remote network device will tear down the tunnel.
  • the CP device removes the tunnel.
  • the tunnel keep-alive message is a Hello (Hel) message or a zero-length body message (ZLB) specified in L2TP.
  • Hel Hello
  • ZLB zero-length body message
  • the tunnel is not expected to be dismantled, that is, the user service of the terminal is not expected to be interrupted. Therefore, the UP device needs to keep the tunnel alive.
  • an implementation manner for the UP device to keep the tunnel alive when the UP device detects that the communication between itself and the CP device is faulty is introduced.
  • the UP device monitors the first tunnel keep-alive message sent by the remote network device.
  • the first tunnel keep-alive message carries the identifier of the target tunnel and the tunnel keep-alive sequence number.
  • the UP device uses the identifier of the target tunnel and the tunnel keep-alive sequence number and the identifier of the one or more tunnels, and send a second tunnel keep-alive message to the remote network device.
  • the UP device stores the first tunnel information synchronized by the CP device, and the first tunnel information includes tunnel description information of one or more tunnels established between the UP device and the remote network device, and the tunnel description information Include the ID of the tunnel.
  • the UP device After monitoring the first tunnel keep-alive message sent by the remote network device, the UP device obtains information from the locally stored first tunnel information according to the identifier of the target tunnel and the tunnel keep-alive sequence number carried in the first tunnel keep-alive message.
  • the identifier of the target tunnel is queried, and after the identifier of the target tunnel is found, the tunnel keep-alive sequence number of the target tunnel is stored locally, and a second tunnel keep-alive message is sent to the remote network device according to the tunnel keep-alive sequence number.
  • the UP device starts to send the second tunnel keep-alive message to the remote network device, that is, it starts to periodically send the tunnel keep-alive message to each other with the remote network device, so that the UP device can perform tunnel keep-alive. .
  • the remote network device does not perceive a communication failure between the CP device and the UP device, but the UP device continues to take over the CP device according to the tunnel currently maintained by the remote network device.
  • the information of the tunnel is kept alive, that is, the tunnel keep alive in a seamless and fast manner.
  • the CP device when the communication between the UP device and the CP device is normal, the CP device also sends the first session information to the UP device.
  • the data packets between the terminal and the remote network device are maintained in the session carried by the tunnel to ensure the normal service communication of the terminal.
  • the terminal sends the data packet to the UP device, the UP device sends the data packet to the remote network device through the session carried by the tunnel created for the terminal, and then the remote network device sends the data packet to the remote network device.
  • the terminal access point realizes the business communication between the terminal and the remote access point.
  • the above only takes the target tunnel in the one or more tunnels as an example to introduce the first implementation of tunnel keep-alive on the UP device.
  • the UP device can learn the tunnel keep-alive sequence number of the corresponding tunnel by monitoring the tunnel keep-alive message sent by the remote network device according to the same tunnel keep-alive method as the target tunnel.
  • the corresponding tunnel performs tunnel keep-alive, which is not repeated in this embodiment of the present application.
  • the UP device resets the tunnel keep-alive sequence number of the target tunnel in the first tunnel information, the target tunnel is one of the one or more tunnels, and the UP device keeps alive according to the reset tunnel of the target tunnel Sequence number, instructing the remote network device to reset the tunnel keep-alive sequence number of the target tunnel.
  • the UP device will follow the reset sequence number of the target tunnel.
  • the tunnel keep-alive sequence number and the identifier of the target tunnel are used to keep the target tunnel alive.
  • the UP device sends a first control request message to the remote network device, where the first control request message carries the identifier of the target tunnel, the reset tunnel keep-alive sequence number of the target tunnel, and the sequence number
  • the UP device receives the first control response packet sent by the remote network device, and the first control response packet is used to indicate that the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel.
  • the UP device needs to perform a tunnel failure recovery with the remote network device, and the tunnel failure recovery includes tunnel data reconciliation and resetting the tunnel keep-alive sequence number, that is, with the remote network device.
  • the device performs a data reconciliation about the tunnel and resets the tunnel keep-alive sequence number to ensure the tunnel consistency between the UP device and the remote network device, and performs tunnel keep-alive according to the reset tunnel keep-alive sequence number.
  • the process of performing data reconciliation between the UP device and the remote network device is as follows: the UP device creates a data reconciliation tunnel with the remote network device, and sends the first tunnel data to the remote network device through the data reconciliation tunnel.
  • the first tunnel data reconciliation message carries the identifier of the tunnel established between the UP device and the remote network device, and the UP device receives the first tunnel reconciliation response message sent by the remote network device,
  • the first tunnel reconciliation response message carries the identifier of the tunnel established between the remote network device and the UP device, and the UP device sends the tunnel identifier carried in the first tunnel data reconciliation message with the first tunnel reconciliation response.
  • the intersection of the tunnel identifiers carried in the packet is determined as the identifiers of one or more tunnels.
  • the UP device first performs data reconciliation, and then resets the tunnel keep-alive sequence number.
  • the UP device may first reset the tunnel keep-alive sequence number of each tunnel included in the locally stored first tunnel information, and then send the data reconciliation tunnel created to the remote network device for tunneling.
  • the data reconciliation and the control request message for resetting the tunnel keep-alive sequence number are used to perform data reconciliation about the tunnel and reset the tunnel keep-alive sequence number with the remote network device through the control request message. That is, the first control request message and the first tunnel data reconciliation message may be the same message, and the first control response message and the first tunnel reconciliation response message may be the same message.
  • the UP device resets the tunnel keep-alive sequence number of each tunnel included in the locally stored first tunnel information, establishes a data reconciliation tunnel (also referred to as a recovery tunnel) with the remote network device, and The first control request message is sent to the remote network device through the data reconciliation tunnel.
  • a data reconciliation tunnel also referred to as a recovery tunnel
  • the remote network device receives the first control request message, if the remote network device stores the information of the target tunnel, it means that the remote network device stores the target tunnel information.
  • the data about the target tunnel between the network device and the UP device is consistent, and the first control response packet that the remote network device replies to the UP device carries the identifier of the target tunnel and an indication to confirm the reset of the tunnel keep-alive sequence number of the target tunnel information, after receiving the first control response packet, the UP device determines that the fault recovery of the target tunnel is successful. If the information of the target tunnel is not stored on the remote network device, it means that the data about the target tunnel is inconsistent between the remote network device and the UP device, and the first control response packet returned by the remote network device to the UP device does not carry the target. The relevant information of the tunnel, or carry the prompt information for indicating that the target tunnel is not successfully established. After receiving the first control response packet, the UP device deletes the locally stored information of the target tunnel.
  • the first control request message sent by the UP to the remote network device carries the identifier of the one or more tunnels, the tunnel keep-alive sequence number after the one or more tunnels are reset, and the sequence number reset.
  • Indication information that is, the UP device performs data reconciliation about the tunnel with the remote network device and resets the tunnel keep-alive sequence number at one time through a control request message.
  • the remote network device After receiving the first control request message, the remote network device sends the identifiers of all the tunnels stored by itself and the indication information for determining to reset the tunnel keep-alive sequence number of the corresponding tunnel to the UP device through the first control response message , after receiving the first control response message, the UP device determines that the UP device and the remote network device jointly store the identifiers of one or more tunnels stored by itself with the identifiers of the tunnels carried in the first control response message. and clear the tunnels that are only stored on the UP but not on the remote network device, so as to complete the data reconciliation with the remote network device about the tunnel and reset the tunnel keep-alive sequence number.
  • the UP device removes the data reconciliation tunnel used for data reconciliation and requesting to reset the tunnel keep-alive sequence number.
  • the UP device After the data reconciliation about the tunnel is performed between the UP device and the remote network device, and the UP device stores the target tunnel information, the UP device tunnels the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel. keep alive.
  • the UP device resets the tunnel keep-alive sequence number according to the communication protocol between the UP device and the remote network device.
  • the communication protocol between the UP device and the remote network device is the L2TP protocol.
  • the L2TP protocol specifies that when a tunnel is created
  • the tunnel keep-alive sequence number is 0 or 1.
  • the CP device and the remote network device send tunnel keep-alive messages to each other to perform tunnel keep-alive
  • the tunnel message sequence number carried in the tunnel keep-alive message increases dynamically.
  • the UP device needs to reset the tunnel keep-alive sequence number to 0 or 1, that is, reset to the initial value.
  • the remote network device After the UP device sends the first control request packet to the remote network device, the remote network device determines, according to the sequence number reset indication information, that the target tunnel currently needs to be recovered from the tunnel failure. The UP device sends a first control response message to the UP device. After receiving the first control response message, the UP device determines that the fault recovery of the target tunnel is successful.
  • the UP device After the UP device successfully recovers from the fault of the target tunnel, it performs tunnel keep-alive on the target tunnel according to the tunnel keep-alive sequence number of the reset target tunnel. That is, the UP device periodically sends a tunnel keep-alive message to the remote network device starting from the reset tunnel keep-alive sequence number of the target tunnel, so as to periodically exchange the tunnel keep-alive message with the remote network device. text to achieve tunnel keep-alive for the target tunnel.
  • the first control request message and the first tunnel data reconciliation message are both start control connection request (start control connection request, SCCRQ) messages in the L2TP protocol
  • the first control response message and the first tunnel The reconciliation response messages are all start control connection reply (SCCRP) messages in the L2TP protocol.
  • the above only takes the target tunnel in the one or more tunnels as an example to introduce the second implementation of tunnel keep-alive on the UP device.
  • the UP device can perform tunnel keep-alive for the corresponding tunnel through tunnel failure recovery according to the same tunnel keep-alive method as that of the target tunnel, which is not repeated in this embodiment of the present application.
  • the CP device when the communication between the UP device and the CP device is normal, the CP device also sends the first session information to the UP device. In this way, the UP device can update the first session information in addition to the failure recovery of the target tunnel. Information about the session carried on the target tunnel in the session information, so as to perform fault recovery on the session carried on the target tunnel.
  • the UP device after creating a data reconciliation tunnel with the remote network device, the UP device sends a first session data reconciliation message to the remote network device, and the first session data reconciliation message carries a identifiers of one or more first reference sessions, where the one or more first reference sessions are sessions carried on the target tunnel stored on the UP device.
  • the UP device receives the first session reconciliation response message sent by the remote network device, and the first session reconciliation response message carries the identifiers of one or more second reference sessions, and the one or more second reference sessions are the remote Sessions hosted on the target tunnel stored on the network device.
  • the UP device determines the intersection of the identifiers of the one or more first reference sessions and the identifiers of the one or more second reference sessions as the identifiers of the sessions carried on the target tunnel. In this way, the sessions carried on the target tunnel can be aligned.
  • the first session data reconciliation message and the first tunnel data reconciliation message are the same message, that is, the UP device reconciles the data stored on the UP device with the remote network through the data reconciliation tunnel.
  • the identifiers of the tunnels established between the devices and the identifiers of the sessions carried on each tunnel are sent to the remote network device at one time for data reconciliation of the tunnel and session data reconciliation.
  • the UP device after the UP device successfully recovers from the failure of the target tunnel, it exchanges session information with the remote network device to perform failure recovery on all sessions carried on the target tunnel, that is, for one or more sessions carried on the target tunnel.
  • the first reference session fails back.
  • the first session data reconciliation packet and the first tunnel data reconciliation packet are different packets.
  • the sessions carried on the target tunnel stored on the UP device include session 1, session 2 and session 3, and the sessions carried on the target tunnel stored on the remote network device include session 1 and session 2, wherein session 1 Session 2 is a successfully connected session, and session 3 is a session in which the connection between the CP device and the remote network device is not completed before the communication failure between the UP device and the CP device, that is, session 3 is a session in a semi-connected state.
  • the information of session 3 is stored on the CP device, and the information of session 3 is synchronized to the UP device, while the information of session 3 is not stored on the remote network device.
  • the UP device sends the first message to the remote network device.
  • the fault recovery session query packet carries the identifiers of session 1, session 2, and session 3, and the first fault recovery session response packet returned by the remote network device to the UP device only carries the identifiers of session 1 and session 2, then the UP After receiving the first fault recovery session response message, the device deletes the locally stored information of session 3, that is, clears the session in the semi-connected state.
  • Session 2 and Session 3 indicate that Session 3 is a session in a semi-connected state created by a remote network device. After the remote network device receives the first fault recovery session query message, it will delete the information of session 3 stored by itself. That is, the remote network device will also clean up the session in the semi-connected state.
  • the first session data reconciliation message is a failure session query (failover session query, FSQ) message in the L2TP protocol
  • the first session data reconciliation response message is a failure session response (failover session response (failover session response, FSQ) message in the L2TP protocol. , FSR) message.
  • the session failure recovery between the UP device and the remote network device deletes the session that has not been established between the UP device and the remote network device, that is, clears the session in the semi-connected state.
  • the UP device can restore the corresponding tunnel through session failure recovery in the same way as restoring the session carried on the target tunnel. Session failure recovery is performed on the session carried on the Internet, which is not repeated in this embodiment of the present application.
  • the tunnel failure recovery and session failure recovery performed in the second implementation manner of tunnel keep-alive performed by the UP device may use the failure recovery (failure recovery) function proposed in the L2TP RFC 4951 specification.
  • the failure recovery function is enabled on the CP device, the UP device and the remote network device, the UP device starts to keep the tunnel alive. , enable the failure recovery function to perform tunnel failure recovery and session failure recovery with the remote network device.
  • the UP device performs tunnel failure recovery and session failure recovery with the remote network device, that is, through data reconciliation between the tunnel and the session, and resetting the tunnel protection.
  • the active serial number can ensure that the UP device can more accurately keep the tunnel established between the UP device and the remote network device.
  • the above only takes the target tunnel in the one or more tunnels as an example to introduce the method for the UP device to keep the tunnel alive.
  • the UP device can follow the
  • the tunnel keep-alive method is the same as that of the target tunnel, and the tunnel keep-alive method is performed, which is not repeated in this embodiment of the present application.
  • Step 303 If the communication between the CP device and the UP device is restored, the CP device performs the tunnel keep-alive on the one or more tunnels again, and the UP device stops the tunnel keep-alive on the one or more tunnels.
  • the CP device after the CP device detects that the communication between itself and the UP device is restored, the CP device needs to re-enable the one or more tunnels, while the UP device detects that the communication between itself and the CP device is restored. Stop the tunnel keep-alive after the communication between them is restored.
  • the CP device communicates with the UP device through the control packet redirection interface and the status control interface.
  • the CP device monitors the status of the control packet redirection interface and the status control interface. If the CP device monitors the control packet redirection interface And/or the state of the state control interface returns to normal, the CP device determines to detect that the communication between itself and the UP device is restored.
  • the UP device communicates with the CP device through the control packet redirection interface and the status control interface.
  • the UP device monitors the status of the control packet redirection interface and the status control interface. If the UP device monitors the control packet redirection interface and the status control interface /or the state of the state control interface returns to normal, the UP device determines to detect that the communication between itself and the CP device is restored.
  • the implementation manner of the CP device re-performing the tunnel keep-alive is: the CP device resets the tunnel keep-alive sequence number of the target tunnel stored locally, the target tunnel is one of the one or more tunnels, and the CP device resets the tunnel keep-alive sequence number of the target tunnel stored locally.
  • the remote network device is instructed to reset the tunnel keep-alive sequence number of the target tunnel.
  • the CP device performs tunnel keep-alive on the target tunnel through the UP device according to the reset tunnel keep-alive sequence number of the target tunnel and the identifier of the target tunnel.
  • the implementation manner of resetting the tunnel keep-alive sequence number of the target tunnel stored locally by the CP device is similar to the foregoing implementation manner of resetting the tunnel keep-alive sequence number of the target tunnel by the UP device.
  • the CP device resets the tunnel keep-alive sequence number of the target tunnel.
  • the keep-alive sequence number is 0 or 1, that is, reset to the initial value specified by the communication protocol.
  • the CP device after the CP device resets the tunnel keep-alive sequence number of the target tunnel, it sends a second control request packet to the remote network device through the UP device. After setting the tunnel keep-alive sequence number of the target tunnel, and the sequence number reset indication information, the CP device receives the second control response packet sent by the remote network device through the UP device, and the second control response packet is used to indicate The remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel.
  • the remote network device After the CP device sends the second control request packet to the remote network device through the UP device, the remote network device determines that the target tunnel needs to be restored from the tunnel fault according to the sequence number reset indication information.
  • the tunnel keep-alive sequence number of the target tunnel, sends a first control response message to the CP device, and the CP device determines that the fault recovery of the target tunnel is successful after receiving the second control response message through the UP device.
  • the process of the CP device performing tunnel fault recovery also includes data reconciliation of the tunnel and resetting of the tunnel keep-alive sequence number.
  • the CP device before the CP device resets the tunnel keep-alive sequence number of the target tunnel stored locally, it creates a data reconciliation tunnel with the remote network device, and through the data reconciliation tunnel, sends the data to the remote network through the UP device.
  • the device sends a second data reconciliation message.
  • the second data reconciliation message carries the identifier of the tunnel established between the UP device and the remote network device stored on the CP device.
  • the CP device receives the data sent by the remote network device through the UP device.
  • the second account reconciliation response packet, the second account reconciliation response packet carries the identifier of the tunnel established between the remote network device and the UP device, and the CP device compares the tunnel identifier carried in the second data reconciliation packet with the UP device.
  • the intersection of the tunnel identifiers carried in the second account reconciliation response packet is determined as the identifiers of one or more tunnels.
  • the remote network device may send a removal request to the UP device to remove a tunnel to actively remove the tunnel, and the UP device receives the message. After the removal request, the corresponding tunnel may or may not be removed. That is, during the tunnel keep alive process of the UP device, the tunnel established between the UP device and the remote network device will be updated. After the communication between the CP device and the UP device is restored, the tunnel between the CP device and the remote network device is restored through the tunnel failure, and the tunnel data reconciliation between the UP device and the remote network device is performed to clear the data on the CP. Stored tunnels that have been removed to ensure tunnel consistency between the CP device and the remote network device.
  • the CP device first performs data reconciliation, and then resets the tunnel keep-alive sequence number.
  • the CP device can first reset the tunnel keep-alive sequence number of each tunnel stored locally, and then send the data reconciliation and reconciliation of the tunnel to the remote network device through the created data reconciliation tunnel.
  • the control request message for setting the tunnel keep-alive sequence number is used to perform data reconciliation with the remote network device about the tunnel and reset the tunnel keep-alive sequence number through the control request message. That is, the second control request message and the second tunnel data reconciliation message may be the same message, and the second control response message and the second tunnel reconciliation response message may be the same message.
  • the CP device resets the tunnel keep-alive sequence number of each tunnel stored locally, establishes a data reconciliation tunnel (also called a recovery tunnel) between the UP device and the remote network device, and passes the UP device to the remote network device.
  • the remote network device receives the second control request message, if the remote network device stores the information of the target tunnel, it means that the remote network device stores the information of the target tunnel.
  • the data about the target tunnel is consistent between the end network device and the CP device, and the second control response packet that the remote network device replies to the CP device carries the identifier of the target tunnel, and a message confirming the reset of the tunnel keep-alive sequence number of the target tunnel.
  • the CP device determines that the fault recovery of the target tunnel is successful. If the information about the target tunnel is not stored on the remote network device, it means that the data about the target tunnel is inconsistent between the remote network device and the CP device, and the second control response packet returned by the remote network device to the CP device does not carry the target. The relevant information of the tunnel, or carry the prompt information indicating that the target tunnel is not successfully established. After receiving the second control response packet through the UP device, the CP device deletes the locally stored information of the target tunnel.
  • the second control request message sent by the CP to the remote network device through the UP device carries the identifier of the one or more tunnels, the tunnel keep-alive sequence number after the one or more tunnels are reset, and the sequence number.
  • Number reset indication information that is, the CP device performs data reconciliation about the tunnel with the remote network device and resets the tunnel keep-alive sequence number through a control request message at one time.
  • the remote network device After receiving the second control request message, the remote network device sends the identifiers of all tunnels stored by itself and the indication information for determining the tunnel keep-alive sequence number of the corresponding tunnel to be reset to the CP device through the second control response message , after the CP device receives the second control response message through the UP device, it determines the relationship between the CP device and the remote network device by comparing the identifiers of one or more tunnels stored by itself with the identifiers of the tunnels carried in the second control response message. and clear the tunnels that are only stored on the CP but not on the remote network device, so as to complete the data reconciliation with the remote network device about the tunnel and reset the tunnel keep-alive sequence number.
  • the tunnel information that the CP device synchronizes to the UP device for the last time includes the information of tunnel 1, tunnel 2 and tunnel 3.
  • a communication failure occurs.
  • tunnel 3 is removed by the remote network device.
  • the CP device performs tunnel failure recovery with the remote network device to restore the tunnel.
  • the tunnel keep-alive sequence numbers of tunnel 1 and tunnel 2 are reset after negotiation with the remote network device, and then tunnel keep-alive is performed on tunnel 1 and tunnel 2.
  • tunnel 3 After the CP device sends a control request packet to reset the tunnel keep-alive sequence number of tunnel 3 to the remote network device, since the information of tunnel 3 has been deleted on the remote network device, the remote network device will send a message to the remote network device.
  • the CP device replies with a control response message that the tunnel 3 is not found. After receiving the control response message, the CP device deletes the information of the tunnel 3.
  • both the second control request message and the second tunnel data reconciliation message are SCCRQ messages in the L2TP protocol, and the second control response message and the second tunnel reconciliation reply message are both in the L2TP protocol.
  • SCCRP message is SCCRQ messages in the L2TP protocol
  • the second control response message and the second tunnel reconciliation reply message are both in the L2TP protocol.
  • the CP device removes the data reconciliation tunnel used for data reconciliation and requesting to reset the tunnel keep-alive sequence number.
  • the CP device After the data reconciliation about the tunnel is performed between the CP device and the remote network device, the CP device stores the information of the target tunnel, then the CP device uses the UP device to verify the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel. The tunnel performs tunnel keep-alive.
  • the above only takes the target tunnel in the one or more tunnels as an example to introduce the implementation method of the CP device to re-enable the tunnel.
  • the CP device For the other tunnels in the one or more tunnels except the target tunnel, the CP device The tunnels can be kept alive for the corresponding tunnels through tunnel failure recovery according to the same tunnel keep-alive method as the target tunnel, which is not repeated in this embodiment of the present application.
  • the CP device in addition to performing fault recovery on the target tunnel through the UP device, can also update the information about the session carried on the target tunnel stored by itself through the UP device, so as to troubleshoot the session carried on the target tunnel. recover.
  • the CP device after creating a data reconciliation tunnel with the remote network device, sends a second session data reconciliation packet to the remote network device through the UP device, and the second session data reconciliation
  • the message carries the identifiers of one or more first reference sessions, where the one or more first reference sessions are sessions carried on the target tunnel stored on the CP device.
  • the CP device receives the second session reconciliation response message sent by the remote network device through the UP device.
  • the second session reconciliation response message carries the identifiers of one or more third reference sessions.
  • the one or more third reference sessions It is a session carried on the target tunnel stored on the remote network device.
  • the CP device determines the intersection of the identifiers of the one or more first reference sessions and the identifiers of the one or more third reference sessions as the identifiers of the sessions carried on the target tunnel. In this way, the sessions carried on the target tunnel can be aligned.
  • the second session data reconciliation message and the second tunnel data reconciliation message are the same message, that is, the CP device uses the data reconciliation tunnel to reconcile the UP device stored on the CP device with the remote device.
  • the identifiers of the tunnels established between the end network devices and the identifiers of the sessions carried on each tunnel are sent to the remote network devices at one time for data reconciliation of the tunnel and session data reconciliation.
  • the tunnel established between the UP device and the remote network device will be removed.
  • the bearer established between the UP device and the remote network device is carried on the tunnel. Based on this, after the communication between the CP device and the UP device is restored, the session failure recovery between the CP device and the remote network device will delete the deleted session stored on the CP device. That is, perform a session data reconciliation with the remote network device to ensure the session consistency between the CP device and the remote network device.
  • the second session data reconciliation message is an FSQ message in the L2TP protocol
  • the second session reconciliation response message is an FSR message in the L2TP protocol.
  • the CP device can restore the corresponding tunnel through session failure recovery in the same method as restoring the session carried on the target tunnel. Session failure recovery is performed on the session carried on the Internet, which is not repeated in this embodiment of the present application.
  • the implementation manner of performing tunnel failure recovery and session failure recovery is similar to the UP device, that is, the CP device re-performs the tunnel keep-alive process.
  • Tunnel failure recovery and session failure recovery can also use the failure Recovery function proposed in the L2TP RFC 4951 specification. It can be seen from the foregoing that the CP device negotiates whether to enable the failure recovery function when establishing a tunnel with the remote network device through the UP device. If the failure recovery function is enabled on the CP device, the UP device, and the remote network device, the CP device starts. When the tunnel keep-alive is performed again, the failure recovery function is enabled to perform tunnel failure recovery and session failure recovery with the remote network device.
  • the CP device can perform tunnel fault recovery and session fault recovery according to the same fault recovery method as the target tunnel. This will not be repeated here.
  • the CP device after the CP device performs tunnel fault recovery through the UP device, it sends the second tunnel information to the UP device, the UP device receives the second tunnel information sent by the CP device, and the UP device updates the local storage according to the second tunnel information.
  • tunnel information includes the information of one or more tunnels established between the UP device and the remote network device stored on the CP device at the first moment, and the first moment refers to after the communication between the UP device and the CP device is restored , the moment when the CP device completes the tunnel failure recovery or session failure recovery between the UP device and the remote network device. That is, the CP device synchronizes the tunnel information to the UP device again.
  • the second tunnel information is carried in the PFCP update request message.
  • the second tunnel information For a detailed introduction of the second tunnel information, reference may be made to the foregoing related introduction to the first tunnel information, which will not be repeated here.
  • the CP device after the CP device recovers the session on the target tunnel through the UP device, it sends the second session information to the UP device, and the UP device receives the second session information sent by the CP device. information to update locally stored session information.
  • the second session information includes session information carried on one or more tunnels established between the UP device and the remote network device stored on the CP device at the second moment. That is, the CP device synchronizes the session information to the UP device again.
  • the second time refers to the time when the CP device completes the session failure recovery through the UP device and the remote network device after the communication between the CP device and the UP device is restored.
  • the second session information is carried in the PFCP update request message.
  • the second session information For a detailed introduction of the second session information, reference may be made to the foregoing related introduction to the first session information, which is not repeated here.
  • the CP device may, after performing tunnel fault recovery on the one or more tunnels, send a second message to the UP device.
  • Tunnel information after session failure recovery is performed on the sessions carried on the one or more tunnels, the second session information is sent to the UP device, or the third tunnel information and the second session information are sent to the UP device, where the third The tunnel information includes information about sessions carried on one or more tunnels established between the UP device and the remote network device stored on the CP device at the second moment.
  • the third tunnel information and the second session information are carried in the same PFCP message, or carried in different PFCP messages.
  • the CP device can perform tunnel failure recovery and session failure recovery on the one or more tunnels After recovery, the second tunnel information and the second session information are sent to the UP device, and the second tunnel information and the second session information are carried in one PFCP update request message, or carried in different PFCP update request messages.
  • the UP device sends the information of the session carried on the tunnel to the remote network device, Synchronize the second session information to the UP device in a manner of sending multiple times.
  • the UP device after receiving the PFCP update request message carrying the second tunnel information and/or the second session information, the UP device sends a PFCP update response message to the CP device.
  • PFCP update response message For the related introduction of the PFCP update response message, refer to the related description in Table 11 above.
  • the CP device and the remote network device perform tunnel failure recovery and session failure sessions, after synchronizing the tunnel information and session information with the UP device once, it continues to send the UP device to the UP device in an instant or periodic manner.
  • the device synchronizes the latest tunnel information and session information in case of another communication failure between the UP device and the CP device.
  • the terminal is a home gateway
  • the home gateway requests access to the network through the point-to-point protocol (PPP)
  • the CP device CP-LAC
  • UP-LAC UP device
  • a tunnel and session are established between end network devices (LNS), and the terminal is connected to the remote network.
  • the CP device sends Hello packets/ZLB packets between the UP device and the remote network device to keep the tunnel alive.
  • the CP device The device synchronizes the L2TP tunnel information and session information to the UP device.
  • the CP device detects the failure and stops the tunnel keep-alive, and the UP device detects the failure and starts the tunnel keep-alive.
  • the UP device and the remote network device synchronize tunnel and session information, and send tunnel keep-alive packets to each other to keep the tunnel alive.
  • the UP device stops the tunnel keep-alive, and the CP device performs the tunnel keep-alive again.
  • the CP device synchronizes the tunnel and session information between the UP device and the remote network device, and sends tunnel keep-alive messages to each other to keep the tunnel alive.
  • the CP device synchronizes the current tunnel and session information to the UP device.
  • the tunnel and session information can be synchronized between the CP device and the UP device through a PFCP update request message.
  • the UP device includes a PFCP protocol module, a PFCP L2TP module and an L2TP proxy module
  • the CP device includes a LAC function module, an LNS function module, a PFCP L2TP module and a PFCP protocol module.
  • the CP device sends a PFCP update request message to the UP device through the SCi interface, the UP device decodes the message header of the PFCP update request message through the PFCP protocol module, and the PFCP protocol module of the UP device decodes the obtained PFCP update request message.
  • the message body is sent to the PFCP L2TP module, and the PFCP L2TP module of the UP device parses the message body, obtains the tunnel information and / session information, and sends the tunnel information and / session information to the L2TP proxy module, and stores the tunnel information and / through the L2TP proxy module.
  • the tunnel keep-alive is performed.
  • the function description of each module on the UP device is detailed in Table 12, and the function description of each module on the CP device is detailed in Table 13.
  • the UP device before the communication failure between the UP device and the CP device, the UP device receives the tunnel information synchronized by the CP device, and after the communication failure between the UP device and the CP device, the UP device according to the The tunnel information is used to keep the tunnel alive, that is, the UP device maintains the tunnel with the remote network device, so that the tunnel removal is not triggered due to the communication failure between the CP device and the UP device.
  • the connection of the network at the end will not be interrupted because of this, that is, to ensure that user services are not damaged.
  • FIG. 6 is a schematic structural diagram of a network device 600 provided by an embodiment of the present application.
  • the network device 600 may be implemented by software, hardware, or a combination of the two to become part or all of a UP device, and the UP device may be any of the above-mentioned embodiments.
  • the CP device and the UP device are used to interact with the remote network device to ensure that the terminal accesses the network.
  • the network device 600 includes: a first receiving module 601 and a tunnel keep-alive module 602 .
  • the first receiving module 601 is configured to receive the first tunnel information sent by the CP device, where the first tunnel information includes information of one or more tunnels established between the UP device and the remote network device; for a specific implementation, please refer to FIG. 3 for implementation. The detailed description of step 301 in the example will not be repeated here.
  • the tunnel keep-alive module 602 is configured to perform tunnel keep-alive for the one or more tunnels according to the first tunnel information if it is detected that the communication between the UP device and the CP device fails.
  • the detailed description of step 302 in the embodiment of FIG. 3 please refer to the detailed description of step 302 in the embodiment of FIG. 3 , which will not be repeated here.
  • the first tunnel information includes identifiers of one or more tunnels
  • the tunnel keep-alive module 602 includes:
  • a monitoring unit configured to monitor the first tunnel keep-alive message sent by the remote network device, where the first tunnel keep-alive message carries the identifier of the target tunnel and the tunnel keep-alive sequence number;
  • the first sending unit is configured to send the second tunnel keep-alive message to the remote network device according to the tunnel keep-alive sequence number of the target tunnel and the identifiers of the one or more tunnels.
  • the second tunnel keep-alive message is sent to the remote network device according to the tunnel keep-alive sequence number of the target tunnel and the identifiers of the one or more tunnels.
  • the first tunnel information includes identifiers of one or more tunnels
  • the tunnel keep-alive module 602 includes:
  • a reset unit used to reset the tunnel keep-alive sequence number of the target tunnel, where the target tunnel is one of the one or more tunnels;
  • an instruction unit configured to instruct the remote network device to reset the tunnel keep-alive sequence number of the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel;
  • the tunnel keep-alive unit is used to tunnel the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel and the identifier of the target tunnel after the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel. keep alive.
  • step 302 in the embodiment of FIG. 3 , which will not be repeated here.
  • the indicating unit is specifically used for:
  • the remote network device sends a first control request message to the remote network device, where the first control request message carries the identifier of the target tunnel, the tunnel keep-alive sequence number of the reset target tunnel, and the sequence number reset indication information;
  • a first control response packet sent by the remote network device is received, where the first control response packet is used to indicate that the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel.
  • the first control response packet is used to indicate that the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel.
  • the tunnel keep-alive module 602 further includes:
  • a creation unit is used to create a data reconciliation tunnel with a remote network device
  • the second sending unit is configured to send a first tunnel data reconciliation message to the remote network device through the data reconciliation tunnel, where the first tunnel data reconciliation message carries the data stored on the UP device and the remote network device. the identity of the established tunnel;
  • the first receiving unit is used to receive the first tunnel account reconciliation response message sent by the remote network device, and the first tunnel account reconciliation response message carries the identifier of the tunnel established between the remote network device and the UP device;
  • the first determining unit is configured to determine the intersection of the identifier of the tunnel carried in the first tunnel data reconciliation message and the identifier of the tunnel carried in the first tunnel reconciliation response message as the identifier of the one or more tunnels.
  • the network device 600 further includes:
  • the second receiving module is configured to receive the first session information sent by the CP device, where the first session information includes information about sessions carried on the one or more tunnels; for the specific implementation method, please refer to the relevant description of step 301 in the embodiment of FIG. 3 , which will not be repeated here.
  • the tunnel keep-alive module 602 also includes:
  • a third sending unit configured to send a first session data reconciliation message to the remote network device, where the first session data reconciliation message carries the identifiers of one or more first reference sessions, the one or more first reference The session is the session carried on the target tunnel stored on the UP device;
  • the second receiving unit is configured to receive the first session reconciliation response message sent by the remote network device, where the first session reconciliation response message carries one or more identifiers of the second reference session, the one or more second The reference session is the session carried on the target tunnel stored on the remote network device;
  • the second determining unit is configured to determine the intersection of the identifiers of the one or more first reference sessions and the identifiers of the one or more second reference sessions as the identifiers of the sessions carried on the target tunnel.
  • the network device 600 further includes:
  • the processing module is configured to stop the tunnel keep-alive for the one or more tunnels if it is detected that the communication between the UP device and the CP device is restored.
  • the network device 600 further includes:
  • the third receiving module is configured to receive the second tunnel information sent by the CP device.
  • the second tunnel information includes the information of one or more tunnels established between the UP device and the remote network device stored on the CP device at the first moment.
  • a moment refers to the moment when the communication between the UP device and the CP device is restored, and the CP device completes the tunnel failure recovery or session failure recovery through the UP device and the remote network device.
  • the specific implementation method please refer to the steps in the embodiment of FIG. 3 The detailed description of 303 will not be repeated here.
  • An update module configured to update the locally stored tunnel information according to the second tunnel information.
  • the UP device communicates with the CP device through the control packet redirection interface and the state control interface;
  • the tunnel keep-alive module 602 includes:
  • the monitoring unit is used to monitor the status of the control packet redirection interface and the status control interface
  • the third determining unit is configured to determine that a failure has been detected in the communication between the UP device and the CP device if it is monitored that the state of the control packet redirection interface and/or the state control interface is abnormal.
  • a failure has been detected in the communication between the UP device and the CP device if it is monitored that the state of the control packet redirection interface and/or the state control interface is abnormal.
  • the first tunnel information is carried in the PFCP update request message, the one or more tunnels are L2TP tunnels, and the information of each tunnel in the one or more tunnels includes tunnel description information;
  • the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv4 address and the tunnel remote IPv4 address;
  • the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv6 address and the tunnel remote IPv6 address.
  • the tunnel local IPv6 address includes the tunnel local IPv6 address.
  • the second tunnel information is carried in the PFCP update request message.
  • the first session information is carried in the PFCP update request message, and the session information carried on each of the one or more tunnels includes a tunnel local identifier, a session local identifier, and a session remote identifier.
  • the session information carried on each of the one or more tunnels includes a tunnel local identifier, a session local identifier, and a session remote identifier.
  • the UP device before the communication failure between the UP device and the CP device, the UP device receives the tunnel information synchronized by the CP device, and after the communication between the UP device and the CP device fails, the UP device performs tunnel protection according to the tunnel information. In other words, the UP device maintains the tunnel with the remote network device, so that the tunnel removal will not be triggered due to the communication failure between the CP device and the UP device.
  • This solution can ensure that the network connection between the terminal and the remote device is not Therefore, it will be interrupted, that is, to ensure that user services are not damaged.
  • the network device provided in the above embodiment performs tunnel keep-alive
  • only the division of the above functional modules is used as an example for illustration.
  • the above functions can be allocated to different functional modules as required. That is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the network equipment provided in the above embodiments and the tunnel keep-alive method embodiments belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be repeated here.
  • FIG. 7 is a schematic structural diagram of a network device 700 provided by an embodiment of the present application.
  • the network device 700 may be implemented by software, hardware, or a combination of the two to become part or all of a CP device, and the CP device may be any of the above-mentioned embodiments.
  • the CP device and the UP device are used to interact with the remote network device to ensure that the terminal accesses the network.
  • the network device 700 includes: a first sending module 701 and a processing module 702 .
  • the first sending module 701 is configured to send first tunnel information to the UP device, where the first tunnel information includes information of one or more tunnels established between the UP device and the remote network device; for a specific implementation, please refer to the embodiment in FIG. 3 The detailed description of step 301 in the above will not be repeated here.
  • the processing module 702 is configured to stop the tunnel keep-alive for the one or more tunnels if it is detected that the communication between the CP device and the UP device fails; for the specific implementation, please refer to the detailed description of step 302 in the embodiment of FIG. 3 , which will not be repeated here.
  • the first tunnel information is used for the UP device to perform tunnel protection for one or more tunnels established between the UP device and the remote network device according to the first tunnel information when it detects that the communication between itself and the CP device fails. live.
  • step 302 in the embodiment of FIG. 3 , which will not be repeated here.
  • the network device 700 further includes:
  • the tunnel keep-alive module 703 is configured to perform tunnel keep-alive on the one or more tunnels again if it is detected that the communication between the CP device and the UP device is restored.
  • the tunnel keep-alive module 703 is configured to perform tunnel keep-alive on the one or more tunnels again if it is detected that the communication between the CP device and the UP device is restored.
  • the tunnel keep-alive module 703 includes:
  • a reset unit configured to reset the locally stored tunnel keep-alive sequence number of each tunnel in the one or more tunnels
  • an instruction unit configured to instruct the remote network device to reset the tunnel keep-alive sequence number of the target tunnel according to the reset tunnel keep-alive sequence number of the target tunnel;
  • the tunnel keep-alive unit is used for, after the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel, according to the reset tunnel keep-alive sequence number of the target tunnel and the identifier of the target tunnel, through the UP device to the target tunnel
  • the tunnel performs tunnel keep-alive.
  • step 3032 in the embodiment of FIG. 3 please refer to the detailed description of step 3032 in the embodiment of FIG. 3 , which will not be repeated here.
  • the indicating unit is specifically used for:
  • the second control response packet sent by the remote network device is received by the UP device, where the second control response packet is used to indicate that the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel.
  • the second control response packet is used to indicate that the remote network device successfully resets the tunnel keep-alive sequence number of the target tunnel.
  • the tunnel keep-alive module 703 further includes:
  • a creation unit is used to create a data reconciliation tunnel with a remote network device
  • the first sending unit is configured to send a second data reconciliation message to the remote network device through the UP device through the data reconciliation tunnel, and the second data reconciliation message carries the UP device stored on the CP device and the remote network device.
  • the first receiving unit is configured to receive, through the UP device, a second reconciliation response message sent by the remote network device, where the second reconciliation response message carries the identifier of the tunnel established between the remote network device and the UP device. ;
  • the first determining unit is configured to determine the intersection of the identifier of the tunnel carried in the second data reconciliation message and the identifier of the tunnel carried in the second reconciliation response message as the identifier of one or more tunnels.
  • the tunnel keep-alive module 703 further includes:
  • the second sending unit is configured to send a second session data reconciliation message to the remote network device through the UP device, where the second session data reconciliation message carries one or more identifiers of the first reference session, the one or more The first reference session is a session carried on the target tunnel stored on the CP device;
  • the second receiving unit is configured to receive, through the UP device, a second session reconciliation response message sent by the remote network device, where the second session reconciliation response message carries one or more identifiers of the third reference session, the one or more The third reference session is the session carried on the target tunnel stored on the remote network device;
  • the second determining unit is configured to determine the intersection of the identifiers of the one or more first reference sessions and the identifiers of one or more third reference sessions as the identifiers of the sessions carried on the target tunnel.
  • the tunnel keep-alive module 703 further includes:
  • the third sending unit is configured to send the second tunnel information to the UP device, where the second tunnel information includes the information of one or more tunnels established between the UP device and the remote network device stored on the CP device at the first moment, and the first
  • the time refers to the time when the CP device completes the tunnel failure recovery or session failure recovery between the UP device and the remote network device after the communication between the UP device and the CP device is restored.
  • the CP device communicates with the UP device through a control packet redirection interface and a state control interface;
  • Processing module 702 includes:
  • the monitoring unit is used to monitor the status of the control packet redirection interface and the status control interface
  • the third determining unit is configured to determine that a failure occurs in the communication between the CP device and the UP device if it is monitored that the state of the control packet redirection interface and/or the state control interface is abnormal.
  • a failure occurs in the communication between the CP device and the UP device if it is monitored that the state of the control packet redirection interface and/or the state control interface is abnormal.
  • the first tunnel information is carried in the PFCP update request message, and the one or more tunnels are Layer 2 tunneling protocol L2TP tunnels, and the information of each tunnel in the one or more tunnels includes tunnel description information;
  • the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv4 address and the tunnel remote IPv4 address;
  • the tunnel description information includes the tunnel local identifier, the tunnel remote identifier, the tunnel local IPv6 address and the tunnel remote IPv6 address.
  • the second tunnel information is carried in the PFCP update request message.
  • the network device 700 further includes:
  • the fourth sending module is configured to send first session information to the UP device, where the first session information includes information of sessions carried on the one or more tunnels.
  • the first session information is carried in the PFCP update request message, and the session information carried on each of the one or more tunnels includes a tunnel local identifier, a session local identifier, and a session remote identifier.
  • the session information carried on each of the one or more tunnels includes a tunnel local identifier, a session local identifier, and a session remote identifier.
  • the first sending module includes:
  • the fifth sending unit configured to send the information of the created tunnel to the UP device every time a tunnel is created, and the one or more tunnels include the created tunnel; or,
  • the sixth sending unit is configured to periodically send the information of the tunnel stored by itself to the UP device.
  • the UP device before the communication failure between the UP device and the CP device, the UP device receives the tunnel information synchronized by the CP device, and after the communication between the UP device and the CP device fails, the UP device performs tunnel protection according to the tunnel information. In other words, the UP device maintains the tunnel with the remote network device, so that the tunnel removal will not be triggered due to the communication failure between the CP device and the UP device.
  • This solution can ensure that the network connection between the terminal and the remote device is not Therefore, it will be interrupted, that is, to ensure that user services are not damaged.
  • the network device provided in the above embodiment performs tunnel keep-alive
  • only the division of the above functional modules is used as an example for illustration.
  • the above functions can be allocated to different functional modules as required. That is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the network equipment provided in the above embodiments and the tunnel keep-alive method embodiments belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be repeated here.
  • An embodiment of the present application provides a network system, which may also be referred to as a tunnel keep-alive system, where the network system includes a CP device, a UP device, and a remote network device.
  • the CP device and the UP device are used to interact with the remote network device. to ensure that the terminal can access the network.
  • the UP device and the CP device have corresponding functions for implementing the tunnel keep-alive method provided by the foregoing embodiments, so as to perform tunnel keep-alive through the system.
  • the network system includes a CP device, a UP device, and a remote network device.
  • the CP device and the UP device are used to interact with the remote network device. to ensure that the terminal can access the network.
  • the UP device and the CP device have corresponding functions for implementing the tunnel keep-alive method provided by the foregoing embodiments, so as to perform tunnel keep-alive through the system.
  • FIG. 3 please refer to the detailed description of the embodiment in FIG. 3 ,
  • the UP device before the communication failure between the UP device and the CP device, the UP device receives the tunnel information synchronized by the CP device, and after the communication between the UP device and the CP device fails, the UP device performs tunnel protection according to the tunnel information. In other words, the UP device maintains the tunnel with the remote network device, so that the tunnel removal will not be triggered due to the communication failure between the CP device and the UP device.
  • This solution can ensure that the network connection between the terminal and the remote device is not Therefore, it will be interrupted, that is, to ensure that user services are not damaged.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general purpose computer, special purpose computer, computer network or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer, or a data storage device such as a server, a data center, etc. that includes one or more available media integrated.
  • the available media may be magnetic media (eg: floppy disk, hard disk, magnetic tape), optical media (eg: digital versatile disc (DVD)) or semiconductor media (eg: solid state disk (SSD)) Wait.
  • the computer-readable storage medium mentioned in the embodiments of the present application may be a non-volatile storage medium, in other words, may be a non-transitory storage medium.
  • references herein to "at least one” refers to one or more, and “plurality” refers to two or more.
  • “/” means or means, for example, A/B can mean A or B;
  • "and/or” in this document is only an association that describes an associated object Relation, it means that there can be three kinds of relations, for example, A and/or B can mean that A exists alone, A and B exist at the same time, and B exists alone.
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect. Those skilled in the art can understand that the words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like are not necessarily different.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例公开了一种隧道保活方法、网络设备、系统及存储介质,属于通信技术领域。在本申请实施例中,在UP设备与CP设备之间通信故障之前,UP设备接收CP设备同步的隧道信息,在UP设备与CP之间的通信故障后,由UP设备根据隧道信息进行隧道保活,也即由UP设备维持与远端网络设备之间的隧道,这样就不会因为CP设备与UP设备之间的通信故障而触发拆除隧道,本方案能够保证终端与远端的网络连接不会因此中断,也即保证用户业务不受损。

Description

隧道保活方法、网络设备、系统及存储介质
本申请实施例要求于2020年8月31日提交的申请号为202010899677.9、发明名称为“隧道保活方法、网络设备、系统及存储介质”的中国专利申请的优先权,其全部内容通过引用结合在本申请实施例中。
技术领域
本申请实施例涉及通信技术领域,特别涉及一种隧道保活方法、网络设备、系统及存储介质。
背景技术
当前,终端能够通过网络中部署的宽带网络网关(broadband network gateway,BNG)设备来接入网络。传统的BNG设备中耦合了控制面(control plane,CP)功能和用户面(user plane,UP)功能,随着通信技术的发展,业界提出了控制面功能和用户面功能分离的BNG,这种BNG称为虚拟宽带网络网关(virtual broadband network gateway,vBNG),且包括CP设备和UP设备。当二层隧道协议接入集中器((layer 2 tunnel protocol,L2TP)access concentrator,LAC)通过vBNG来实现时,CP设备能够在UP设备与远端的L2TP网络服务器(L2TP network server,LNS)之间建立隧道,保证该终端成功接入远端网络。但是,为了保证用户业务不中断,需要对该隧道进行保活处理。
相关技术提供了一种隧道保活方法,在该方法中,CP设备在UP设备与LNS之间建立隧道之后,CP设备与LNS之间通过UP设备周期性地发送隧道保活报文以进行隧道保活,保障用户业务不中断。也即是,UP设备负责转发CP设备与LNS之间的隧道保活报文,以使CP设备与LNS之间能够通信,进而进行隧道保活,来保障用户业务不中断。
然而,如果CP设备与UP设备之间发生通信故障,CP设备与LNS之间无法通过隧道保活报文来进行隧道保活,就会触发拆除隧道,进而使终端与远端网络连接中断,也即用户业务中断。
发明内容
本申请实施例提供了一种隧道保活方法、网络设备、系统及存储介质,能够在UP设备和CP设备之间发生通信故障的情况下,保证终端的网络连接不因此中断。所述技术方案如下:
第一方面,提供了一种隧道保活方法,控制面CP设备和用户面UP设备用于与远端网络设备进行交互来保证终端接入网络,该方法包括:
UP设备接收CP设备发送的第一隧道信息,第一隧道信息包括UP设备与远端网络设备之间建立的一条或多条隧道的信息;如果UP设备检测到自身与CP设备之间的通信发生故障,则UP设备根据第一隧道信息,对该一条或多条隧道进行隧道保活。
在本申请实施例中,在UP设备与CP设备之间通信故障之前,UP设备接收CP设备同步的隧道信息,在UP设备与CP之间的通信故障后,由UP设备根据隧道信息进行隧道保活, 也即由UP设备维持与远端网络设备之间的隧道,这样就不会因为CP设备与UP设备之间的通信故障而触发拆除隧道,本方案能够保证终端与远端的网络连接不会因此中断,也即保证用户业务不受损。
在本申请实施例中,在UP设备与CP设备之间通信故障之前,CP设备向UP设备发送第一隧道信息的实现方式有多种,请按照下述第二方面中相关介绍,这里不再赘述。
可选地,第一隧道信息携带在包转发控制协议(packet forwarding control protocol,PFCP)更新请求报文中,该一条或多条隧道为L2TP隧道,该一条或多条隧道中每条隧道的信息包括隧道描述信息;如果L2TP隧道是根据第四版互联网协议(Internet protocol version4,IPv4)创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv4地址和隧道远端IPv4地址;如果L2TP隧道是根据第六版互联网协议(Internet protocol version6,IPv6)创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv6地址和隧道远端IPv6地址。也即是,通过扩展PFCP报文实现CP设备向UP设备同步隧道信息。
在本申请实施例中,在UP设备与CP设备之间通信正常的情况下,CP设备还能够向UP设备同步第一会话信息,UP设备接收CP设备发送的第一会话信息,第一会话信息包括该一条或多条隧道上承载的会话的信息。需要说明的是,由于终端通过承载在隧道上的会话实现业务通信,因此,CP设备向UP设备同步会话信息,后续UP设备进行隧道保活的过程中,根据会话信息实现终端与远端网络设备之间的会话通信。
可选地,第一会话信息携带在PFCP更新请求报文中,该一条或多条隧道中每条隧道上承载的会话的信息包括隧道本地标识、会话本地标识和会话远端标识。也即是,通过扩展PFCP报文实现CP设备向UP设备同步会话报文。
可选地,在本申请实施例中,UP设备在接收到PFCP更新请求报文之后,向CP设备发送PFCP更新应答报文。
可选地,UP设备通过控制报文重定向接口和状态控制接口与CP设备进行通信;UP设备检测到自身与CP设备之间的通信发生故障,包括:UP设备监控控制报文重定向接口和状态控制接口的状态;如果UP设备监控到控制报文重定向接口和/或状态控制接口的状态异常,则UP设备确定检测到自身与CP设备之间的通信发生故障。也即是,UP设备通过实时检测自身与CP设备通信的通信接口的状态,感知UP设备与CP设备之间的通信状况。
需要说明的是,在本申请实施例中,各个隧道独立进行隧道保活,也即每条隧道对应有隧道保活序列号,UP设备或者CP设备通过与远端网络设备之间周期性地交互隧道保活报文,实现对各个隧道的隧道保活。在本申请实施例中,第一隧道信息包括一条或多条隧道的标识,隧道保活报文携带相应隧道的隧道保活序列号。
而在UP设备与CP设备之间的通信发生故障的情况下,不希望隧道因此被拆除,也即不希望终端的用户业务中断,因此,通过UP设备对隧道继续进行隧道保活。接下来对在UP设备检测到自身与CP设备之间的通信发生故障的情况下,UP设备进行隧道保活的实现方式进行介绍。
第一种实现方式、UP设备根据第一隧道信息,对该一条或多条隧道进行隧道保活,包括:UP设备监听远端网络设备发送的第一隧道保活报文,第一隧道保活报文携带目标隧道的标识和隧道保活序列号,UP设备根据该目标隧道的标识和隧道保活序列号以及该一条或多条隧道的标识,向远端网络设备发送第二隧道保活报文。
需要说明的是,UP设备从向远端网络设备发送第二隧道保活报文开始,即开始周期性地与远端网络设备交互隧道保活报文,实现隧道保活。
在这种实现方式中,对于远端网络设备来说,并不会感知到CP设备与UP设备之间发生通信故障,而是由UP设备继续接替CP设备并根据远端网络设备当前维持的隧道的信息进行隧道保活,也即无缝衔接式的快速进行隧道保活。
由前述可知,在UP设备与CP设备之间的通信正常的情况下,CP设备还向UP设备发送第一会话信息,这样,UP设备在隧道保活的同时,还能够根据第一会话信息,将终端与远端网络设备之间的数据报文维持在隧道承载的会话上,保证终端正常进行业务通信。
第二种实现方式、UP设备根据第一隧道信息,对该一条或多条隧道进行隧道保活,包括:UP设备重置第一隧道信息中目标隧道的隧道保活序列号,目标隧道为该一条或多条隧道中的一条,UP设备根据重置后的目标隧道的隧道保活序列号,指示远端网络设备对目标隧道的隧道保活序列号进行重置,在远端网络设备对目标隧道的隧道保活序列号重置成功后,UP设备按照重置后的目标隧道的隧道保活序列号以及目标隧道的标识,对目标隧道进行隧道保活。
在这种实现方式中,UP设备需要与远端网络设备之间进行一次隧道故障恢复,也即与远端网络设备进行一次数据对账和重置隧道保活序列号,以保证UP设备与远端网络设备之间的隧道一致性。
可选地,UP设备根据重置后的所述目标隧道的隧道保活序列号,指示所述远端网络设备对所述目标隧道的隧道保活序列号进行重置,包括:UP设备向远端网络设备发送第一控制请求报文,第一控制请求报文携带目标隧道的标识、重置后的目标隧道的隧道保活序列号,以及序列号重置指示信息;UP设备接收远端网络设备发送的第一控制应答报文,第一控制应答报文用于指示远端网络设备对目标隧道的隧道保活序列号重置成功。
可选地,UP设备重置目标隧道的隧道保活序列号之前,还包括:UP设备创建与远端网络设备之间的数据对账隧道;UP设备通过数据对账隧道,向远端网络设备发送第一隧道数据对账报文,第一隧道数据对账报文携带UP设备上存储的与远端网络设备之间建立的隧道的标识;UP设备接收远端网络设备发送的第一隧道对账应答报文,第一隧道对账应答报文携带远端网络设备上存储的与UP设备之间建立的隧道的标识;UP设备将第一隧道数据对账报文携带的隧道的标识与第一隧道对账应答报文携带的隧道的标识的交集,确定为一条或多条隧道的标识。
也即是,在UP设备与远端网络设备之间进行重置隧道保活序列号之前,UP设备先与远端网络设备之间进行数据对账,以通过数据对账保证UP设备与远端网络设备之间的隧道一致性,这样,UP设备能更加精确地进行隧道保活。
由前述可知,在UP设备与CP设备之间的通信正常的情况下,CP设备还向UP设备发送第一会话信息,也即是,UP设备根据第一隧道信息,对该一条或多条隧道进行隧道保活之前,还包括:UP设备接收CP设备发送的第一会话信息,第一会话信息包括该一条或多条隧道上承载的会话的信息,这样,UP设备创建与远端网络设备之间的数据对账隧道之后,还包括:UP设备向远端网络设备发送第一会话数据对账报文,第一会话数据对账报文携带一个或多个第一参考会话的标识,该一个或多个第一参考会话为UP设备上存储的目标隧道上承载的会话;UP设备接收远端网络设备发送的第一会话对账应答报文,第一会话对账应答报文携带一个或多个第二参考会话的标识,该一个或多个第二参考会话为远端网络设备上存储的目 标隧道上承载的会话;UP设备将一个或多个第一参考会话的标识与一个或多个第二参考会话的标识的交集,确定为目标隧道上承载的会话的标识。
也即是,在本申请实施例中,UP设备还能够更新第一会话信息中目标隧道上承载的会话的信息,以对目标隧道上承载的会话进行故障恢复。
需要说明的是,UP设备与远端网络设备之间通过会话故障恢复,将UP设备与远端网络设备之间还未完成建立的会话进行删除,也即清理半连接状态的会话。
在上述第二种实现方式中,UP设备与远端网络设备之间通过隧道故障恢复和会话故障恢复,保证UP设备与远端网络设备之间的隧道和会话的一致性,能够更加精确地对UP设备与远端网络设备之间建立的隧道进行隧道保活。
以上仅以该一条或多条隧道中的目标隧道为例,对UP设备进行隧道保活的方法进行了介绍,对于该一条或多条隧道中除目标隧道之外的其他隧道,UP设备均能够按照与目标隧道相同的隧道保活方法,进行隧道保活,本申请实施例对此不再赘述。
在本申请实施例中,UP设备根据第一隧道信息,对该一条或多条隧道进行隧道保活之后,还包括:如果UP设备检测到自身与CP设备之间的通信恢复,则UP设备停止对该一条或多条隧道进行隧道保活,而CP设备需要重新对该一条或多条隧道进行隧道保活。
在本申请实施例中,UP设备停止对该一条或多条隧道进行隧道保活之后,还包括:UP设备接收CP设备发送的第二隧道信息,第二隧道信息包括第一时刻CP设备上存储的UP设备与远端网络设备之间建立的一条或多条隧道的信息,第一时刻是指UP设备与CP设备之间的通信恢复之后,CP设备通过UP设备与远端网络设备之间完成隧道故障恢复或会话故障恢复的时刻;UP设备根据第二隧道信息,更新本地存储的隧道信息。也即是,CP设备与远端网络设备之间完成隧道故障恢复或会话故障恢复之后,再次向UP设备同步隧道信息,保证UP设备上存储的隧道信息与CP设备一致,以备后续UP设备与CP设备之间的通信再次发生故障。
可选地,第二隧道信息携带在PFCP更新请求报文中。也即是,在本申请实施例中,也通过对PFCP进行扩展,得到携带第二隧道信息的PFCP更新请求报文。
第二方面,提供了一种隧道保活方法,控制面CP设备和用户面UP设备用于与远端网络设备进行交互来保证终端接入网络,该方法包括:
CP设备向UP设备发送第一隧道信息,第一隧道信息包括UP设备与远端网络设备之间建立的一条或多条隧道的信息;如果CP设备检测到自身与UP设备之间的通信发生故障,则CP设备停止对该一条或多条隧道进行隧道保活;其中,第一隧道信息用于UP设备在检测到自身与CP设备之间的通信发生故障时,根据第一隧道信息对UP设备与远端网络设备之间建立的一条或多条隧道进行隧道保活。
在本申请实施例中,在UP设备与CP设备之间通信故障之前,CP设备向UP设备同步隧道信息,在UP设备与CP之间的通信故障后,由UP设备根据隧道信息进行隧道保活,也即由UP设备维持与远端网络设备之间的隧道,这样就不会因为CP设备与UP设备之间的通信故障而触发拆除隧道,本方案能够保证终端与远端的网络连接不会因此中断,也即保证用户业务不受损。
需要说明的是,UP设备根据隧道信息进行隧道保活的实现方式参照前述第一方面提供的 隧道保活方法,这里不再赘述。
在本申请实施例中,在UP设备与CP设备之间通信故障之前,CP设备向UP设备发送第一隧道信息的实现方式有多种,接下来介绍其中的两种实现方式。
第一种实现方式、CP设备通过即时的方式将第一隧道信息同步给UP设备。
也即是,CP设备每创建一条隧道,向UP设备发送所创建的隧道的信息,每删除一条隧道,向UP设备发送所删除的隧道的信息。
可选地,第一隧道信息携带在PFCP更新请求报文中,该一条或多条隧道为L2TP隧道,该一条或多条隧道中每条隧道的信息包括隧道描述信息;如果L2TP隧道是根据IPv4创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv4地址和隧道远端IPv4地址;如果L2TP隧道是根据IPv6创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv6地址和隧道远端IPv6地址。
在本申请实施例中,在UP设备与CP设备之间通信正常的情况下,CP设备还能够向UP设备同步第一会话信息,UP设备接收CP设备发送的第一会话信息,第一会话信息包括该一条或多条隧道上承载的会话的信息。
在第一种实现方式中,CP设备每创建一个会话,向UP设备同步所创建的会话的信息,每删除一个会话,向UP设备同步所删除的会话的信息。
可选地,第一会话信息携带在PFCP更新请求报文中,该一条或多条隧道中每个隧道上承载的会话的信息包括隧道本地标识、会话本地标识和会话远端标识。
在CP设备向UP设备同步信息的第一种实现方式中,第一隧道信息和第一会话信息分别携带在不同的PFCP更新请求报文中,一个PRCP更新请求报文携带创建的一条隧道的信息,或者删除的一条隧道的信息,或者一个创建的会话的信息,或者一个删除的会话的信息。通过即时的方式同步信息,能够保证信息的及时性和隧道保活的可靠性。
第二种实现方式、CP设备周期性地将第一隧道信息同步给UP设备。
也即是,CP设备每隔一个同步周期,将自身存储的所有建立的隧道的信息同步给UP设备。或者,CP设备每隔一个同步周期,将更新的隧道的信息同步给CP设备,更新的隧道包括上一次同步隧道的信息之后建立的隧道和删除的隧道的信息。
在第二种实现方式中,CP设备还能够周期性地将第一会话信息同步给UP设备。也即是,在本申请实施例中,CP设备停止隧道保活之前,还包括:CP设备向UP设备发送第一会话信息,第一会话信息包括该一条或多条隧道上承载的会话的信息。
可选地,第一隧道信息和第一会话信息携带在PFCP更新请求报文中。对PFCP更新请求报文的相关描述参照前述相关介绍,这里不再赘述。需要说明的是,在第二种实现方式中,第一隧道信息和第一会话信息可以携带在同一个PFCP更新请求报文中,也可以携带在不同的PFCP更新请求报文中。
可选地,第一会话信息携带在PFCP更新请求报文中,该一条或多条隧道中每条隧道上承载的会话的信息包括隧道本地标识、会话本地标识和会话远端标识。
需要说明的是,第一隧道信息和第一会话信息的详细介绍参照前述第一方面的相关内容,这里不再赘述。
可选地,CP设备通过控制报文重定向接口和状态控制接口与UP设备进行通信;CP设备检测到自身与UP设备之间的通信发生故障,包括:CP设备监控控制报文重定向接口和状 态控制接口的状态;如果CP设备监控到控制报文重定向接口和/或状态控制接口的状态异常,则CP设备确定检测到自身与UP设备之间的通信发生故障。
在本申请实施例中,如果CP设备检测到自身与UP设备之间的通信发生故障,则CP设备停止对该一条或多条隧道进行隧道保活之后,还包括:如果CP设备检测到自身与UP设备之间的通信恢复,则CP设备重新对该一条或多条隧道进行隧道保活。也即是,在CP设备与UP设备之间的通信正常的情况下,仍由CP设备进行隧道保活,以减轻UP设备的负载压力。
在本申请实施例中,CP设备重新对该一条或多条隧道进行隧道保活,包括:CP设备重置本地存储的目标隧道的隧道保活序列号,目标隧道为该一条或多条隧道中的一条;CP设备根据重置后的目标隧道的隧道保活序列号,指示远端网络设备对目标隧道的隧道保活序列号进行重置;在远端网络设备对目标隧道的隧道保活序列号重置成功后,CP设备按照重置后的目标隧道的隧道保活序列号以及目标隧道的标识,通过UP设备对目标隧道进行隧道保活。
可选地,CP设备根据重置后的目标隧道的隧道保活序列号,指示远端网络设备对目标隧道的隧道保活序列号进行重置,包括:CP设备通过UP设备向远端网络设备发送第二控制请求报文,第二控制请求报文携带目标隧道的标识、重置后的目标隧道的隧道保活序列号,以及序列号重置指示信息;CP设备通过UP设备接收远端网络设备发送的第二控制应答报文,第二控制应答报文用于指示远端网络设备对目标隧道的隧道保活序列号重置成功。
需要说明的是,在UP设备与远端网络设备之间进行隧道保活的过程中,远端网络设备可能会拆除某些隧道,CP设备与远端网络设备之间通过隧道故障恢复,将UP设备与远端网络设备之间的隧道进行关于隧道的数据对账,以清理CP上存储的已被拆除的隧道,保证CP设备与远端网络设备之间的隧道一致性,保证UP设备进行隧道保活的精确性。
也即是,CP设备重置本地存储的目标隧道的隧道保活序列号之前,还包括:CP设备创建与远端网络设备之间的数据对账隧道;CP设备通过数据对账隧道,通过UP设备向远端网络设备发送第二数据对账报文,第二数据对账报文携带CP设备上存储的UP设备与远端网络设备之间建立的隧道的标识;CP设备通过UP设备接收远端网络设备发送的第二对账应答报文,第二对账应答报文携带远端网络设备上存储的与UP设备之间建立的隧道的标识;CP设备将第二数据对账报文携带的隧道的标识与第二对账应答报文携带的隧道的标识的交集,确定为一条或多条隧道的标识。
需要说明的是,CP设备进行数据对账以及重置隧道保活序列号的过程参照前述UP设备的相关内容,这里不再赘述。
在本申请实施例中,CP设备通过UP设备对目标隧道进行故障恢复之后,还能够通过UP设备更新自身存储的目标隧道上承载的会话的信息,以对目标隧道上承载的会话进行故障恢复。
也即是,CP设备创建与远端网络设备之间的数据对账隧道之后,还包括:CP设备通过UP设备向远端网络设备发送第二会话数据对账报文,第二会话数据对账报文携带一个或多个第一参考会话的标识,该一个或多个第一参考会话为CP设备上存储的目标隧道上承载的会话;CP设备通过UP设备接收远端网络设备发送的第二会话对账应答报文,第二会话对账应答报文携带一个或多个第三参考会话的标识,该一个或多个第三参考会话为远端网络设备上存储的目标隧道上承载的会话;CP设备将该一个或多个第一参考会话的标识与该一个或多个第三参考会话的标识的交集,确定为目标隧道上承载的会话的标识。也即是,CP设备通过UP 设备更新自身存储的目标隧道上承载的会话的信息,以对目标隧道上承载的会话进行故障恢复。
需要说明的是,在UP设备与远端网络设备之间进行隧道保活的过程中,远端网络设备也可能会拆除某些隧道上的会话,CP设备与远端网络设备之间通过会话故障恢复,将UP设备与远端网络设备之间的会话进行关于会话的数据对账,也即清理CP上存储的已被拆除的会话,保证CP设备与远端网络设备之间的会话一致性。
另外,对于该一条或多条隧道中除目标隧道之外的其他隧道,CP设备均能够按照与目标隧道相同的故障恢复方法,进行隧道故障恢复以及会话故障恢复,本申请实施例对此不再赘述。
在本申请实施例中,CP设备根据重置后的目标隧道的隧道保活序列号,通过UP设备对目标隧道进行故障恢复之后,还包括:CP设备向UP设备发送第二隧道信息,第二隧道信息包括第一时刻CP设备上存储的UP设备与远端网络设备之间建立的一条或多条隧道的信息,第一时刻是指UP设备与CP设备之间的通信恢复之后,CP设备通过UP设备与远端网络设备之间完成隧道故障恢复或会话故障恢复的时刻。也即是,CP设备再次向UP设备同步隧道信息,以备后续UP设备与CP设备之间的通信再次发生故障,由UP设备进行隧道保活。
可选地,第二隧道信息携带在PFCP更新请求报文中。
在本申请实施例中,CP设备通过UP设备对目标隧道上的会话进行故障恢复之后,还包括:CP设备向UP设备发送第二会话信息,第二会话信息包括第二时刻CP设备上存储的UP设备与远端网络设备之间建立的一条或多条隧道上承载的会话的信息。也即是,CP设备再次向UP设备同步会话信息,以备后续UP设备与CP设备之间的通信再次发生故障,由UP设备进行隧道保活以及实现终端的会话通信。
可选地,第二会话信息携带在PFCP更新请求报文中。
可选地,第二隧道信息和第二会话信息携带在一个PFCP更新请求报文中,或者携带在不同的PFCP更新请求报文中。
可选地,在申请实施例中,CP设备在向UP设备发送携带第二隧道信息和/或第二会话信息的PFCP更新请求报文之后,接收UP设备发送的PFCP更新应答报文。
在本申请实施例中,CP设备与远端网络设备进行隧道故障恢复和会话故障会话后,向UP设备同步一次隧道信息和会话信息之后,仍继续通过即时的方式或者周期性的方式,向UP设备同步最新的隧道信息和会话信息,以备后续UP设备与CP设备之间再次发生通信故障。
第三方面,提供了一种网络设备,所述网络设备具有实现上述第一方面中隧道保活方法行为的功能。所述网络设备包括一个或多个模块,该一个或多个模块用于实现上述第一方面所提供的隧道保活方法。
也即是,提供了一种网络设备,该网络设备应用于网络系统,该网络系统包括CP设备和UP设备,CP设备和UP设备用于与远端网络设备进行交互来保证终端接入网络,该网络设备为UP设备,该网络设备包括:
第一接收模块,用于接收CP设备发送的第一隧道信息,第一隧道信息包括UP设备与远端网络设备之间建立的一条或多条隧道的信息;
隧道保活模块,用于如果检测到UP设备与CP设备之间的通信发生故障,则根据第一隧 道信息,对该一条或多条隧道进行隧道保活。
可选地,第一隧道信息包括一条或多条隧道的标识;
隧道保活模块包括:
监听单元,用于监听远端网络设备发送的第一隧道保活报文,第一隧道保活报文携带目标隧道的标识和隧道保活序列号;
第一发送单元,用于根据目标隧道的隧道保活序列号以及该一条或多条隧道的标识,向远端网络设备发送第二隧道保活报文。
可选地,第一隧道信息包括一条或多条隧道的标识;
隧道保活模块包括:
重置单元,用于重置目标隧道的隧道保活序列号,目标隧道为该一条或多条隧道中的一条;
指示单元,用于根据重置后的目标隧道的隧道保活序列号,指示远端网络设备对目标隧道的隧道保活序列号进行重置;
隧道保活单元,用于在远端网络设备对目标隧道的隧道保活序列号重置成功后,按照重置后的目标隧道的隧道保活序列号以及目标隧道的标识,对目标隧道进行隧道保活。
可选地,指示单元具体用于:
向远端网络设备发送第一控制请求报文,第一控制请求报文携带目标隧道的标识、重置后的目标隧道的隧道保活序列号,以及序列号重置指示信息;
接收远端网络设备发送的第一控制应答报文,第一控制应答报文用于指示远端网络设备对目标隧道的隧道保活序列号重置成功。
可选地,隧道保活模块还包括:
创建单元,用于创建与远端网络设备之间的数据对账隧道;
第二发送单元,用于通过该数据对账隧道,向远端网络设备发送第一隧道数据对账报文,第一隧道数据对账报文携带UP设备上存储的与远端网络设备之间建立的隧道的标识;
第一接收单元,用于接收远端网络设备发送的第一隧道对账应答报文,第一隧道对账应答报文携带远端网络设备上存储的与UP设备之间建立的隧道的标识;
第一确定单元,用于将第一隧道数据对账报文携带的隧道的标识与第一隧道对账应答报文携带的隧道的标识的交集,确定为该一条或多条隧道的标识。
可选地,该网络设备还包括:
第二接收模块,用于接收CP设备发送的第一会话信息,第一会话信息包括该一条或多条隧道上承载的会话的信息;
隧道保活模块还包括:
第三发送单元,用于向远端网络设备发送第一会话数据对账报文,第一会话数据对账报文携带一个或多个第一参考会话的标识,该一个或多个第一参考会话为UP设备上存储的目标隧道上承载的会话;
第二接收单元,用于接收远端网络设备发送的第一会话对账应答报文,第一会话对账应答报文携带一个或多个第二参考会话的标识,该一个或多个第二参考会话为远端网络设备上存储的目标隧道上承载的会话;
第二确定单元,用于将该一个或多个第一参考会话的标识与该一个或多个第二参考会话 的标识的交集,确定为目标隧道上承载的会话的标识。
可选地,该网络设备还包括:
处理模块,用于如果检测到UP设备与CP设备之间的通信恢复,则停止对该一条或多条隧道进行隧道保活。
可选地,该网络设备还包括:
第三接收模块,用于接收CP设备发送的第二隧道信息,第二隧道信息包括第一时刻CP设备上存储的UP设备与远端网络设备之间建立的一条或多条隧道的信息,第一时刻是指UP设备与CP设备之间的通信恢复之后,CP设备通过UP设备与远端网络设备之间完成隧道故障恢复或会话故障恢复的时刻;
更新模块,用于根据第二隧道信息,更新本地存储的隧道信息。
可选地,UP设备通过控制报文重定向接口和状态控制接口与CP设备进行通信;
隧道保活模块包括:
监控单元,用于监控控制报文重定向接口和状态控制接口的状态;
第三确定单元,用于如果监控到控制报文重定向接口和/或状态控制接口的状态异常,则确定检测到UP设备与CP设备之间的通信发生故障。
可选地,第一隧道信息携带在PFCP更新请求报文中,该一条或多条隧道为L2TP隧道,该一条或多条隧道中每条隧道的信息包括隧道描述信息;
如果L2TP隧道是根据IPv4创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv4地址和隧道远端IPv4地址;
如果L2TP隧道是根据IPv6创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv6地址和隧道远端IPv6地址。
可选地,第二隧道信息携带在PFCP更新请求报文中。
可选地,第一会话信息携带在PFCP更新请求报文中,该一条或多条隧道中每条隧道上承载的会话的信息包括隧道本地标识、会话本地标识和会话远端标识。
第四方面,提供了一种网络设备,所述网络设备具有实现上述第二方面中隧道保活方法行为的功能。所述网络设备包括一个或多个模块,该一个或多个模块用于实现上述第二方面所提供的隧道保活方法。
也即是,提供了一种网络设备,该网络设备应用于网络系统,该网络系统包括CP设备和UP设备,CP设备和UP设备用于与远端网络设备进行交互来保证终端接入网络,该网络设备为CP设备,该网络设备包括:
第一发送模块,用于向UP设备发送第一隧道信息,第一隧道信息包括UP设备与远端网络设备之间建立的一条或多条隧道的信息;
处理模块,用于如果检测到CP设备与UP设备之间的通信发生故障,则停止对该一条或多条隧道进行隧道保活;
其中,第一隧道信息用于指示UP设备在检测到自身与CP设备之间的通信发生故障时,对UP设备与远端网络设备之间建立的一条或多条隧道进行隧道保活。
可选地,该网络设备还包括:
隧道保活模块,用于如果检测到CP设备与UP设备之间的通信恢复,则重新对一条或多 条隧道进行隧道保活。
可选地,隧道保活模块包括:
重置单元,用于重置本地存储的目标隧道的隧道保活序列号,目标隧道为该一条或多条隧道中的一条;
指示单元,用于根据重置后的目标隧道的隧道保活序列号,指示远端网络设备对目标隧道的隧道保活序列号进行重置;
隧道保活单元,用于在远端网络设备对目标隧道的隧道保活序列号重置成功后,按照重置后的目标隧道的隧道保活序列号以及目标隧道的标识,通过UP设备对目标隧道进行隧道保活。
可选地,指示单元具体用于:
通过UP设备向远端网络设备发送第二控制请求报文,第二控制请求报文携带目标隧道的标识、重置后的目标隧道的隧道保活序列号,以及序列号重置指示信息;
通过UP设备接收远端网络设备发送的第二控制应答报文,第二控制应答报文用于指示远端网络设备对目标隧道的隧道保活序列号重置成功。
可选地,隧道保活模块还包括:
创建单元,用于创建与远端网络设备之间的数据对账隧道;
第一发送单元,用于通过数据对账隧道,通过UP设备向远端网络设备发送第二数据对账报文,第二数据对账报文携带CP设备上存储的UP设备与远端网络设备之间建立的隧道的标识;
第一接收单元,用于通过UP设备接收远端网络设备发送的第二对账应答报文,第二对账应答报文携带远端网络设备上存储的与UP设备之间建立的隧道的标识;
第一确定单元,用于将第二数据对账报文携带的隧道的标识与第二对账应答报文携带的隧道的标识的交集,确定为一条或多条隧道的标识。
可选地,隧道保活模块还包括:
第二发送单元,用于通过UP设备向远端网络设备发送第二会话数据对账报文,第二会话数据对账报文携带一个或多个第一参考会话的标识,该一个或多个第一参考会话为CP设备上存储的目标隧道上承载的会话;
第二接收单元,用于通过UP设备接收远端网络设备发送的第二会话对账应答报文,第二会话对账应答报文携带一个或多个第三参考会话的标识,该一个或多个第三参考会话为远端网络设备上存储的目标隧道上承载的会话;
第二确定单元,用于将该一个或多个第一参考会话的标识和一个或多个第三参考会话的标识的交集,确定为目标隧道上承载的会话的标识。
可选地,隧道保活模块还包括:
第三发送单元,用于向UP设备发送第二隧道信息,第二隧道信息包括第一时刻CP设备上存储的UP设备与远端网络设备之间建立的一条或多条隧道的信息,第一时刻是指UP设备与CP设备之间的通信恢复之后,CP设备通过UP设备与远端网络设备之间完成隧道故障恢复或会话故障恢复的时刻。
可选地,CP设备通过控制报文重定向接口和状态控制接口与UP设备进行通信;
处理模块包括:
监控单元,用于监控控制报文重定向接口和状态控制接口的状态;
第三确定单元,用于如果监控到控制报文重定向接口和/或状态控制接口的状态异常,则确定检测到CP设备与UP设备之间的通信发生故障。
可选地,第一隧道信息携带在PFCP更新请求报文中,该一条或多条隧道为二层隧道协议L2TP隧道,该一条或多条隧道中每条隧道的信息包括隧道描述信息;
如果L2TP隧道是根据IPv4创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv4地址和隧道远端IPv4地址;
如果L2TP隧道是根据IPv6创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv6地址和隧道远端IPv6地址。
可选地,第二隧道信息携带在PFCP更新请求报文中。
可选地,该网络设备还包括:
第四发送模块,用于向UP设备发送第一会话信息,第一会话信息包括该一条或多条隧道上承载的会话的信息。
可选地,第一会话信息携带在PFCP更新请求报文中,该一条或多条隧道中每条隧道上承载的会话的信息包括隧道本地标识、会话本地标识和会话远端标识。
可选地,第一发送模块包括:
第五发送单元,用于每创建一条隧道,向UP设备发送创建的一条隧道的信息,一条或多条隧道包括创建的一条隧道;或者,
第六发送单元,用于周期性地向UP设备发送自身存储的隧道的信息。
第五方面,提供了一种网络设备,所述网络设备应用于网络系统,所述网络系统包括UP设备和CP设备,CP设备和UP设备用于与远端网络设备进行交互来保证终端接入网络,所述网络设备为UP设备,所述网络设备包括处理器和存储器,所述存储器用于存储执行上述第一方面所提供的隧道保活方法的程序,以及存储用于实现上述第一方面所提供的隧道保活方法所涉及的数据。所述处理器被配置为用于执行所述存储器中存储的程序。所述存储设备的操作装置还可以包括通信总线,该通信总线用于该处理器与存储器之间建立连接。
第六方面,提供了一种网络设备,所述网络设备应用于网络系统,所述网络系统包括UP设备和CP设备,CP设备和UP设备用于与远端网络设备进行交互来保证终端接入网络,所述网络设备为CP设备,所述网络设备包括处理器和存储器,所述存储器用于存储执行上述第二方面所提供的隧道保活方法的程序,以及存储用于实现上述第二方面所提供的隧道保活方法所涉及的数据。所述处理器被配置为用于执行所述存储器中存储的程序。所述存储设备的操作装置还可以包括通信总线,该通信总线用于该处理器与存储器之间建立连接。
第七方面,提供了一种网络系统,所述系统包括CP设备和UP设备,以及远端网络设备,所述CP设备和所述UP设备用于与所述远端网络设备进行交互来保证终端接入网络;
所述UP设备,用于实现上述第一方面所提供的隧道保活方法;
所述CP设备,用于实现上述第二方面所提供的隧道保活方法。
第八方面,提供了一种计算机可读存储介质,所述计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机执行上述第一方面或第二方面所述的隧道保活方法。
第九方面,提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述第一方面或第二方面所述的隧道保活方法。
上述第三方面、第四方面、第五方面、第六方面、第七方面、第八方面和第九方面所获得的技术效果与第一方面或第二方面中对应的技术手段获得的技术效果近似,在这里不再赘述。
本申请实施例提供的技术方案至少能够带来以下有益效果:
在本申请实施例中,在UP设备与CP设备之间通信故障之前,UP设备接收CP设备同步的隧道信息,在UP设备与CP之间的通信故障后,由UP设备根据隧道信息进行隧道保活,也即由UP设备维持与远端网络设备之间的隧道,这样就不会因为CP设备与UP设备之间的通信故障而触发拆除隧道,本方案能够保证终端与远端的网络连接不会因此中断,也即保证用户业务不受损。
附图说明
图1是本申请实施例提供的一种隧道保活方法所涉及的系统架构图;
图2是本申请实施例提供的一种网络设备的结构示意图;
图3是本申请实施例提供的一种隧道保活方法的流程图;
图4是本申请实施例提供的另一种隧道保活方法的流程图;
图5是本申请实施例提供的一种CP设备与UP设备包括的模块间通信的示意图;
图6是本申请实施例提供的一种网络设备的结构示意图;
图7是本申请实施例提供的另一种网络设备的结构示意图;
图8是本申请实施例提供的又一种网络设备的结构示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚,下面将结合附图对本申请实施方式作进一步地详细描述。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本申请实施例提供的技术方案对于类似的技术问题,同样适用。
图1是本申请实施例提供的一种隧道保活方法所涉及的系统架构图。参见图1,该系统架构包括终端101、CP设备102和UP设备103、远端网络设备104和远端接入点105。终端101与UP设备103之间建立有通信连接,UP设备103与远端网络设备104之间建立有通信连接,CP设备102与UP设备103之间建立有通信连接,远端网络设备104与远端接入点 105之间建立通信连接。
在本申请实施例中,本端的CP设备102和UP设备103作为vBNG的两部分,共同实现LAC功能,远端网络设备104实现LNS功能,本端的CP设备102能够在UP设备103与远端网络设备104之间建立隧道和会话,保证终端101成功接入远端接入点105提供的网络并实现业务通信。为了保证用户业务不中断,需要对UP设备103与远端网络设备104之间的隧道进行隧道保活。
在UP设备103与CP设备102之间未发生通信故障的情况下,CP设备102用于在UP设备103与远端网络设备104之间建立隧道以及承载在该隧道上的会话,进而将终端101接入远端的网络,并由CP设备102通过UP设备103对UP设备103与远端网络设备104之间建立的隧道进行隧道保活,保障用户业务不中断。UP设备103还用于在该隧道承载的会话上传递终端101与远端网络设备104之间的数据报文,实现终端101与远端网络设备104之间的业务通信。也即是,CP设备102和UP设备103用于与远端网络设备104进行交互保证终端101接入网络。另外,CP设备102还用于根据本申请实施例提供的隧道保活方法,向UP设备103同步隧道信息和会话信息。
在UP设备103与CP设备102之间的通信发生故障的情况下,CP设备102不能继续通过UP设备103与远端网络设备104交互进行隧道保活,这种情况下,UP设备103根据存储的隧道信息,对UP设备103与远端网络设备104之间的隧道进行隧道保活,以保证隧道不会因为UP设备103和CP设备102之间的通信故障而拆除,以维持隧道,保证隧道上承载的会话不中断。
在UP设备103与CP设备102之间的通信恢复之后,UP设备103停止隧道保活,CP设备102继续通过UP设备103与远端网络设备104之间进行隧道保活,并且CP设备102将自身与远端网络设备104之间进行隧道保活的过程中,存储的隧道信息同步给UP设备103。
需要说明的是,该系统架构中包括多个终端,以及与每个终端对应的远端网络设备和远端接入点,以上仅以一个终端和对应的一个远端网络设备和远端接入点为例进行介绍。对于每个终端,CP设备与UP设备均能实现以上功能。
可选地,远端网络设备104为传统的BNG设备,即远端网络设备104为一个独立的网关设备。或者,远端网络设备104也通过vBNG实现,即包括一个CP设备和一个UP设备,在这种情况下,为了便于描述,将本端的CP设备102和UP设备103分别称为CP-LAC和UP-LAC,将远端的CP设备和UP设备分别称为CP-LNS和UP-LNS,CP-LAC与UP-LAC通信连接,UP-LAC与UP-LNS通信连接,UP-LNS与CP-LNS通信连接。
可选地,虚拟宽带远程接入服务器(virtual broadband remote access server,vBRAS)也能实现与vBNG相同的功能,也即vBRAS包括CP设备和UP设备,该CP设备和UP设备用于将本端的终端接入远端网络,并根据本申请实施例提供的隧道保活方法实现隧道保活。
在本申请实施例中,终端101为手机、电脑、家庭网关等设备,UP设备103为路由器、交换机等设备,CP设备102为一台服务器,或者由多台服务器构成的服务器集群,或者一个云计算服务中心,远端网络设备104为路由器、交换机等独立的设备,或者远端网络设备104包括一个UP设备和一个CP设备,远端接入点105为提供宽带网络的设备。
请参考图2,图2是根据本申请实施例示出的一种网络设备的结构示意图。可选地,该 网络设备为图1中所示的CP设备或UP设备,该网络设备包括一个或多个处理器201、通信总线202、存储器203以及一个或多个通信接口204。
处理器201为一个通用中央处理器(central processing unit,CPU)、网络处理器(NP)、微处理器、或者为一个或多个用于实现本申请方案的集成电路,例如,专用集成电路(application-specific integrated cirCPit,ASIC),可编程逻辑器件(programmable logic device,PLD)或其组合。可选地,上述PLD为复杂可编程逻辑器件(complex programmable logic device,CPLD),现场可编程逻辑门阵列(field-programmable gate array,FPGA),通用阵列逻辑(generic array logic,GAL)或其任意组合。
通信总线202用于在上述组件之间传送信息。可选地,通信总线202分为地址总线、数据总线、控制总线等。为便于表示,图中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
可选地,存储器203为只读存储器(read-only memory,ROM)、随机存取存储器(random access memory,RAM)、电可擦可编程只读存储器(electrically erasable programmable read-only memory,EEPROM)、光盘(包括只读光盘(compact disc read-only memory,CD-ROM)、压缩光盘、激光盘、数字通用光盘、蓝光光盘等)、磁盘存储介质或者其它磁存储设备,或者是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其它介质,但不限于此。存储器203独立存在,并通过通信总线202与处理器201相连接,或者,存储器203与处理器201集成在一起。
通信接口204使用任何收发器一类的装置,用于与其它设备或通信网络通信。通信接口204包括有线通信接口,可选地,还包括无线通信接口。其中,有线通信接口例如以太网接口等。可选地,以太网接口为光接口、电接口或其组合。无线通信接口为无线局域网(wireless local area networks,WLAN)接口、蜂窝网络通信接口或其组合等。当该网络设备为CP设备时,通信接口204用于与UP设备通信,当该网络设备为UP设备时,通信接口204用于与CP设备通信。
可选地,在一些实施例中,该网络设备包括多个处理器,如图2中所示的处理器201和处理器205。这些处理器中的每一个为一个单核处理器,或者一个多核处理器。可选地,这里的处理器指一个或多个设备、电路、和/或用于处理数据(如计算机程序指令)的处理核。
在具体实现中,作为一种实施例,该网络设备还包括输出设备206和输入设备207。输出设备206和处理器201通信,能够以多种方式来显示信息。例如,输出设备206为液晶显示器(liquid crystal display,LCD)、发光二级管(light emitting diode,LED)显示设备、阴极射线管(cathode ray tube,CRT)显示设备或投影仪(projector)等。输入设备207和处理器201通信,能够以多种方式接收用户的输入。例如,输入设备207是鼠标、键盘、触摸屏设备或传感设备等。
在一些实施例中,存储器203用于存储执行本申请方案的程序代码210,处理器201能够执行存储器203中存储的程序代码210。该程序代码中包括一个或多个软件模块,该网络设备能够通过处理器201以及存储器203中的程序代码210,来实现下文图3实施例提供的隧道保活方法。
当该网络设备为UP设备时,存储器203用于存储程序代码210,处理器201用于执行存储器203中存储的程序代码210,实现本申请实施例提供的隧道保活方法中UP设备的相应功 能。也即是,接收CP设备发送的第一隧道信息,如果检测到UP设备与CP设备之间的通信发生故障,则根据第一隧道信息,进行隧道保活。具体实现方式参照下述图3实施例中的详细介绍,这里不再赘述。
示例性地,当图6所示实施例中的第一接收模块601和隧道保活模块602是通过软件实施的情况下,该程序代码210中可以包括第一接收模块和隧道保活模块,第一接收模块用于接收CP设备发送的第一隧道信息,隧道保活模块用于根据第一隧道信息进行隧道保活。
当该网络设备为CP设备时,存储器203用于存储程序代码210,处理器201用于执行存储器203中存储的程序代码210,实现本申请实施例提供的隧道保活方法中CP设备的相应功能。也即是,向UP设备发送第一隧道信息,如果检测到CP设备与UP设备之间的通信发生故障,则停止进行隧道保活。具体实现方式参照下述图3实施例中的详细介绍,这里不再赘述。
示例性地,当图8所示实施例中的第一发送模块701、处理模块702和隧道保活模块703是通过软件实施的情况下,该程序代码210中可以包括第一发送模块、处理模块和隧道保活模块,第一发送模块用于向UP设备发送第一隧道信息,处理模块用于在检测到CP设备与UP设备之间的通信发生故障后,停止隧道保活,隧道保活模块用于在检测到CP设备与UP设备之间的通信恢复后,重新进行隧道保活。
图3是本申请实施例提供的一种隧道保活方法的流程图。请参考图3,该方法包括如下步骤。
步骤301:UP设备接收CP设备发送的第一隧道信息,第一隧道信息包括UP设备与远端网络设备之间建立的一条或多条隧道的信息。
在本申请实施例中,CP设备和UP设备用于与远端网络设备进行交互来保证终端接入网络。例如,在终端通过宽带拨号连接接入远端的公司总部内网的场景中,终端能够通过本端的CP设备和UP设备与远端网络设备之间建立的通道建立通信连接,例如,CP设备在UP设备与远端网络设备之间建立隧道和承载在隧道上的会话,保证终端接入远端的网络,以及实现业务通信。
在本申请实施例中,终端能够在UP设备与CP设备之间未发生通信故障的情况下,向UP设备发送连接请求,以请求接入远端网络设备所管理的远端接入点提供的网络,UP设备将该连接请求转发给CP设备,CP设备对该连接请求进行用户认证,确定该终端所请求接入的网络对应的远端网络设备,CP设备在对用户认证通过之后,在UP设备与远端网络设备之间建立一条隧道和一个承载在该隧道上的会话,通过该隧道上会话将终端成功接入网络,并实现业务通信。
例如,一个彩票点的终端想要接入企业总部的彩票中心的网络,该终端通过宽带拨号将连接请求发送到本地运营商的vBNG包括的UP设备,CP设备根据该连接请求进行用户认证,确定该终端所请求接入的彩票中心的网络对应的远端网络设备,CP设备在对用户认证通过之后,在UP设备与远端网络设备之间建立一条隧道和一个承载在该隧道上的会话,通过该会话将终端成功接入彩票中心的网络。
在终端成功接入网络之后,终端通过UP设备与远端网络设备之间所维持的隧道上承载的会话,实现业务通信。同时,CP设备通过UP设备与远端网络设备之间交互隧道保活报文, 对UP设备与远端网络设备之间的隧道进行隧道保活,也即维持UP设备与远端网络设备之间的隧道,并保证隧道以及承载在隧道上的会话不中断,也即保证终端业务不中断。UP设备通过转发终端与远端网络设备之间的数据报文,保证终端的业务通信维持在隧道承载的会话上。
在CP设备与UP设备之间的通信正常的情况下,CP设备还能够向UP设备同步自身存储的隧道的信息。也即是,在本申请实施例中,CP设备向UP设备发送第一隧道信息,第一隧道信息包括UP设备与远端网络设备之间建立的一条或多条隧道的信息。需要说明的是,CP设备向UP设备发送第一隧道信息的实现方式有多种,下面示例性地介绍其中的两种实现方式。
第一种实现方式、CP设备通过即时的方式将第一隧道信息同步给UP设备。
也即是,CP设备每创建一条隧道,向UP设备发送所创建的隧道的信息,每删除一条隧道,向UP设备发送所删除的隧道的信息。
在本申请实施例中,第一隧道信息携带在PFCP更新请求报文中,该一条或多条隧道为L2TP隧道,该一条或多条隧道中每个隧道的信息包括隧道描述信息。如果L2TP隧道是根据IPv4创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv4地址和隧道远端IPv4地址。如果L2TP隧道是根据IPv6创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv6地址和隧道远端IPv6地址。其中,隧道本地标识和隧道远端标识为隧道的标识。
在本申请实施例中,第一隧道信息可以携带在任一种通信协议报文中。可选地,通过对PFCP协议进行扩展,得到PFCP更新请求报文。可选地,对PFCP规定的节点级消息(node message)进行扩展,得到PFCP更新请求报文。
示例性地,表1为扩展PFCP规定的node message,PFCP更新请求报文还携带消息类型,该消息类型可以取16-49之间的任一数值,消息类型用于指示相应报文为PFCP更新请求报文,也称为PFCP L2TP隧道更新请求。
表1
Figure PCTCN2021114141-appb-000001
在PFCP的node message中,PFCP更新请求报文包括一个组信息单元(grouped information element,Grouped IE),一个Grouped IE包括一个或多个嵌入信息单元Embedded IE,Embedded IE为PFCP更新请求报文的最小单元,每个Embedded IE携带一个隧道描述信息,通过扩展Grouped IE,得到PFCP更新请求报文。
在本申请实施例中,参见表2,首先对PFCP更新请求报文中携带的IE的标识符进行解释,其中,M表示必选项,C表示满足条件就需要携带,CO表示满足条件可以选择携带或不携带,O表示可以选择携带或不携带。
表2
IE是否出现在此业务流程的分类 解释
mandatory(M) 必选项
conditional(C) 满足某种条件就需要携带
conditional-optional(CO) 满足某种条件可以选择携带或不携带
optional(O) 可选择携带或不携带
表3为PFCP更新请求报文携带的隧道(tunnel)的信息的介绍,PFCP更新请求报文还携带CP设备的设备号,也即CP设备的节点标识(node identification,Node ID),在创建L2TP隧道的情况下,PFCP更新请求报文还携带所创建的各个隧道的隧道描述信息,在删除L2TP隧道的情况下,PFCP更新请求报文还携带所删除的各个隧道的隧道描述信息。
表3
Figure PCTCN2021114141-appb-000002
可选地,如果L2TP穿越三层虚拟私有网络(layer 3 virtual private network,L3VPN),PFCP更新请求报文还携带L3VPN的实例的名称,也即L3VPN的私网名称。
示例性地,表4为扩展Grouped IE得到的PFCP更新请求报文的结构描述。在创建或者删除L2TP隧道的情况下,PFCP更新请求报文的前2个字节(一个Octet为8比特,也即一个字节)携带隧道消息类型(message type),第3和4个字节携带长度(length),用于指示报文长度,第5和6个字节携带厂家号(enterprise ID),表示该报文是哪个厂家扩展的,从第7个字节开始,携带创建或删除的隧道的隧道描述信息,可选地,如果L2TP穿越L3VPN,还携带L3VPN的实例的名称。
表4
Figure PCTCN2021114141-appb-000003
表5为扩展Embedded IE,得到的一个携带隧道描述信息的PFCP更新请求报文的结构示意图。
表5
Figure PCTCN2021114141-appb-000004
在表5中,从第7字节开始为隧道描述信息,第7字节的比特1(bit 1):V4取值为1,表示L2TP隧道附着(over)在IPv4地址上,也即L2TP隧道是根据IPv4创建的,此时p=16,q=20;
第7字节的bit 2:V6取值为1,表示隧道over在IPv6地址上,也即L2TP隧道是根据IPv6创建的,此时r=16,s=32;
第7字节的bit 3~6:Ver(version)表示L2TP隧道的版本号。取值为2,表示L2TPV2版本,此时隧道标识(tunnel identification,tunnel ID)是16bit无符号整数。取值为3,表示L2TPV3版本,此时tunnel ID的是32bit无符号整数。
第7字节的bit 7~8:保留字段,设置为0。
第8~11字节:隧道本地标识(local tunnel ID),32bit无符号整数,L2TPV2版本低16bit有效。
第12~15字节:隧道远端标识(remote tunnel ID),32bit无符号整数,L2TPV2版本低16bit有效。
第p~p+3字节:隧道本地IPv4地址(local IPv4 address)。
第q~q+3字节:隧道远端IPv4地址(remote IPv4 address)。
第r~r+15字节:隧道本地IPv6地址(local IPv6 address)。
第s~s+15字节:隧道远端IPv6地址(remote IPv6 address)。
示例性地,假设为L2TPV2版本,且采用IPv4地址,PFCP更新请求报文的结构如表6所示。
表6
Figure PCTCN2021114141-appb-000005
示例性地,假设为L2TPV3版本,且采用IPv6地址,PFCP更新请求报文的结构如表7所示。
表7
Figure PCTCN2021114141-appb-000006
以上介绍了在UP设备与CP设备之间通信正常的情况下,CP设备向UP设备同步隧道信息的过程,在本申请实施例中,CP设备还能够向UP设备发送第一会话信息,UP设备接收CP设备发送的第一会话信息,第一会话信息包括该一条或多条隧道上承载的会话的信息,也即CP设备将会话信息同步给UP设备。
可选地,第一会话信息也携带在PFCP更新请求报文中,该一条或多条隧道中每条隧道上承载的会话的信息包括隧道本地标识、会话本地标识和会话远端标识。
在PFCP的node级message中,在携带第一会话信息的PFCP更新请求报文中,PFCP更新请求报文包括一个Grouped IE,一个Grouped IE包括一个或多个Embedded IE,每个Embedded IE携带一个会话的信息,通过扩展Grouped IE,得到携带第一会话信息的PFCP更新请求报文。
表8为PFCP更新请求报文携带的会话的信息介绍,PFCP更新请求报文携带CP设备的设备号,也即CP设备的节点标识,在创建L2TP会话(session)的情况下,PFCP更新请求报文还携带所创建的各个会话的信息,在删除L2TP会话的情况下,PFCP更新请求报文还携带所删除的各个会话的信息。
表8
Figure PCTCN2021114141-appb-000007
示例性地,表9为扩展Grouped IE得到的PFCP更新请求报文的结构描述。在创建或者删除L2TP会话的情况下,前2个字节(Octet)携带会话消息类型,第3和4个字节携带长度,用于指示报文长度,第5和6个字节携带厂家号,表示该报文是哪个厂家扩展的,从第7个字节开始,携带创建或删除的会话的信息。
表9
Figure PCTCN2021114141-appb-000008
表10为扩展embedded IE,得到的携带一个会话的信息的PFCP更新请求报文的结构示意图。
表10
Figure PCTCN2021114141-appb-000009
在表10中,第7字节的bit 1~4:Ver表示L2TP隧道的版本号。取值为2,表示L2TPV2版本,此时会话标识(session ID)的是16bit无符号整数。取值为3,表示L2TPV3版本,此时session ID的是32bit无符号整数。
第7字节的bit 5~8:保留字段,设置为0。
第8~11字节:隧道本地标识(local tunnel ID),32bit无符号整数,L2TPV2版本低16bit有效。表示会话所属的隧道。
第12~15字节:会话本地标识(local session ID),32bit无符号整数,L2TPV2版本低16bit有效。
第16~19字节:会话远端标识(local session ID),32bit无符号整数,L2TPV2版本低16bit有效。
需要说明的是,在第一种实现方式中,第一隧道信息和第一会话信息分别携带在不同的PFCP更新请求报文中,一个PRCP更新请求报文携带创建的一条隧道的信息,或者删除的一条隧道的信息,或者一个创建的会话的信息,或者一个删除的会话的信息。UP设备在接收到携带创建的隧道或会话的信息的PFCP更新请求报文之后,在本地存储所创建的隧道或会话的信息,UP设备在接收到携带删除的隧道或会话的信息的PFCP更新请求报文之后,删除本地存储的相应的隧道或会话的信息。
第二种实现方式、CP设备周期性地将第一隧道信息同步给UP设备。
也即是,CP设备每隔一个同步周期,将自身存储的所有建立的隧道的信息同步给UP设备。或者,CP设备每隔一个同步周期,将更新的隧道的信息同步给CP设备,更新的隧道包括上一次同步隧道的信息之后建立的隧道和删除的隧道的信息。
可选地,第一隧道信息携带在PFCP更新请求报文中,如果CP设备上存储有建立的多条隧道的信息,那么第一隧道信息包括建立的多条隧道的信息,每条隧道的信息包括隧道描述信息。
在第二种实现方式中,CP设备还能够周期性地将第一会话信息同步给UP设备,第一会话信息携带在PFCP更新请求报文中。对PFCP更新请求报文的相关描述参照前述相关介绍,这里不再赘述。
需要说明的是,在本申请实施例中,第一隧道信息和第一会话信息可以携带在同一个PFCP更新请求报文中,也可以携带在不同的PFCP更新请求报文中。
示例性地,假设CP设备每隔一个同步周期,将自身存储的所有建立的隧道和会话的信息通过一个PFCP更新请求报文同步给UP设备。或者,CP设备每隔一个同步周期,将自身存储的所有建立的隧道的信息通过一个PFCP更新请求报文同步给UP设备,将自身存储的所有会话的信息通过另一个PFCP更新请求报文同步给UP设备。
可选地,在本申请实施例中,UP设备在接收到PFCP更新请求报文之后,能够向CP设备发送PFCP更新应答报文。
示例性地,参见表1,PFCP更新应答报文携带消息类型,该消息类型可以取16-49之间的任一与PFCP更新请求报文携带的消息类型不同的数值,该消息类型用于指示相应报文为PFCP更新应答报文,也称为PFCP L2TP隧道更新应答。参见表11,PFCP更新应答报文还携带UP设备的设备号,也即UP设备的节点标识,PFCP更新应答报文还携带处理结果(也称为cause),处理结果用于指示UP设备是否成功解析PFCP更新请求报文。
表11
Embedded IE P 条件/内容 IE类型
Node ID M UP的设备号 节点标识
cause M 处理结果(成功/错误码) cause
步骤302:如果UP设备与CP设备之间的通信发生故障,则UP设备根据第一隧道信息,对该一条或多条隧道进行隧道保活,且CP设备停止对该一条或多条隧道进行隧道保活。
在本申请实施例中,UP设备和CP设备之间通过多个通信接口进行通信,例如宽带论坛(broadband-forum,BBF)WT-459(也称为TR-459)中定义的vBNG中的CP设备与UP设备之间的通信接口,包括控制报文重定向接口(control packet redirection interface,CPRi)和状态控制接口(state control interface,SCi),UP设备通过控制报文重定向接口和状态控制接口与CP设备进行通信,UP设备监控控制报文重定向接口和状态控制接口的状态,如果UP设备监控到控制报文重定向接口和/或状态控制接口的状态异常,则UP设备确定检测到自身与CP设备之间的通信发生故障。
同样地,CP设备通过控制报文重定向接口和状态控制接口与UP设备进行通信,CP设备监控控制报文重定向接口和状态控制接口的状态,如果CP设备监控到控制报文重定向接口和/或状态控制接口的状态异常,则CP设备确定检测到自身与UP设备之间的通信发生故障。
在本申请实施例中,如果UP设备检测到自身与CP设备之间的通信发生故障,则UP设备根据第一隧道信息,对该一条或多条隧道进行隧道保活,如果CP设备检测到自身与UP设备之间的通信发生故障,CP设备停止对该一条或多条隧道进行隧道保活。
需要说明的是,在本申请实施例中,各个隧道独立进行隧道保活,也即每条隧道对应有隧道保活序列号,UP设备或者CP设备通过与远端网络设备之间交互隧道保活报文,实现对各个隧道的隧道保活。隧道保活序列号包括一个发送序列号和一个期望接收序列号,示例性地,对于一条隧道来说,假设UP设备向远端网络设备发送一个隧道保活报文,该隧道保活报文为携带发送序列号为0和期望接收序列号为0的报文,远端网络设备在接收到该隧道保活报文之后,向UP设备发送携带发送序列号为0和期望接收序列号为1的隧道保活报文,UP设备继续向远端网络设备发送携带发送序列号为1和期望接收序列号为1的隧道保活报文,远端网络设备向UP设备发送携带发送序列号为1和期望接收序列号为2的隧道保活报文,以此类推,UP设备与远端网络设备之间通过周期性发送携带隧道保活序列号的隧道保活报文对该隧道进行保活。如果远端网络设备超时未接收到期望的隧道保活报文,则远端网络设备将拆除该隧道。在UP设备与CP设备之间的通信正常的情况下,如果CP设备超时未接收到隧道保活报文,则CP设备拆除该隧道。
可选地,隧道保活报文为L2TP中规定的Hello(Hel)报文或者零长报文(zero-length body message,ZLB)。
而在UP设备与CP设备之间的通信发生故障的情况下,不希望隧道因此被拆除,也即不希望终端的用户业务中断,因此,需要UP设备对隧道继续进行隧道保活。接下来对在UP设备检测到自身与CP设备之间的通信发生故障的情况下,UP设备进行隧道保活的实现方式进行介绍。
第一种实现方式、UP设备监听远端网络设备发送的第一隧道保活报文,第一隧道保活报文携带目标隧道的标识和隧道保活序列号,UP设备根据该目标隧道的标识和隧道保活序列号以及该一条或多条隧道的标识,向远端网络设备发送第二隧道保活报文。
在本申请实施例中,UP设备存储有CP设备同步的第一隧道信息,第一隧道信息包括在 UP设备与远端网络设备之间建立的一条或多条隧道的隧道描述信息,隧道描述信息包括隧道的标识。UP设备在监听到远端网络设备发送的第一隧道保活报文之后,根据第一隧道保活报文携带的目标隧道的标识和隧道保活序列号,从本地存储的第一隧道信息中查询目标隧道的标识,在查找到目标隧道的标识之后,在本地存储目标隧道的隧道保活序列号,并根据该隧道保活序列号,向远端网络设备发送第二隧道保活报文。
需要说明的是,UP设备从向远端网络设备发送第二隧道保活报文开始,即开始与远端网络设备之间周期性地互相发送隧道保活报文,实现UP设备进行隧道保活。
在这种实现方式中,对于远端网络设备来说,并不会感知到CP设备与UP设备之间发生通信故障,而是由UP设备继续接替CP设备并根据远端网络设备当前维持的隧道的信息进行隧道保活,也即无缝衔接式地快速进行隧道保活。
由前述可知,在UP设备与CP设备之间的通信正常的情况下,CP设备还向UP设备发送第一会话信息,这样,UP设备在隧道保活的同时,还能够根据第一会话信息,将终端与远端网络设备之间的数据报文维持在隧道承载的会话上,保证终端正常进行业务通信。
示例性地,终端将数据报文发送给UP设备,UP设备将数据报文通过为该终端创建的隧道承载的会话发送给远端网络设备,再由远端网络设备将数据报文发送给远端接入点,实现终端与远端接入点之间的业务通信。
以上仅以该一条或多条隧道中的目标隧道为例,对UP设备进行隧道保活的第一种实现方式进行了介绍,对于该一条或多条隧道中除目标隧道之外的其他隧道,UP设备均能够按照与目标隧道相同的隧道保活方法,通过监听远端网络设备发送的隧道保活报文,以获知相应隧道的隧道保活序列号,根据监听到的隧道保活序列号对相应隧道进行隧道保活,本申请实施例对此不再赘述。
第二种实现方式、UP设备重置第一隧道信息中目标隧道的隧道保活序列号,目标隧道为该一条或多条隧道中的一条,UP设备根据重置后的目标隧道的隧道保活序列号,指示远端网络设备对目标隧道的隧道保活序列号进行重置,在远端网络设备对目标隧道的隧道保活序列号重置成功后,UP设备按照重置后的目标隧道的隧道保活序列号以及目标隧道的标识,对目标隧道进行隧道保活。
在本申请实施例中,UP设备向远端网络设备发送第一控制请求报文,第一控制请求报文携带目标隧道的标识、重置后的目标隧道的隧道保活序列号,以及序列号重置指示信息,UP设备接收远端网络设备发送的第一控制应答报文,第一控制应答报文用于指示远端网络设备对目标隧道的隧道保活序列号重置成功。
可选地,在这种实现方式中,UP设备需要与远端网络设备之间进行一次隧道故障恢复,隧道故障恢复包括隧道数据对账和重置隧道保活序列号,也即与远端网络设备进行一次关于隧道的数据对账和重置隧道保活序列号,以保证UP设备与远端网络设备之间的隧道一致性,并根据重置后的隧道保活序列号进行隧道保活。
其中,UP设备与远端网络设备进行数据对账的过程为:UP设备创建与远端网络设备之间的数据对账隧道,并通过数据对账隧道,向远端网络设备发送第一隧道数据对账报文,第一隧道数据对账报文携带UP设备上存储的与远端网络设备之间建立的隧道的标识,UP设备接收远端网络设备发送的第一隧道对账应答报文,第一隧道对账应答报文携带远端网络设备上存储的与UP设备之间建立的隧道的标识,UP设备将第一隧道数据对账报文携带的隧道的 标识与第一隧道对账应答报文携带的隧道的标识的交集,确定为一条或多条隧道的标识。
在本申请实施例中,UP设备先进行数据对账,再重置隧道保活序列号。可选地,UP设备也可以先重置本地存储的第一隧道信息包括的每条隧道的隧道保活序列号,之后,通过创建的数据对账隧道,向远端网络设备发送用于进行隧道的数据对账和重置隧道保活序列号的控制请求报文,以通过控制请求报文与远端网络设备进行关于隧道的数据对账以及重置隧道保活序列号。也即是,第一控制请求报文与第一隧道数据对账报文可以为同一个报文,第一控制应答报文与第一隧道对账应答报文可以为同一个报文。
可选地,UP设备重置本地存储的第一隧道信息包括的每条隧道的隧道保活序列号,与远端网络设备之间建立一条数据对账隧道(也可以称为恢复隧道),并通过该数据对账隧道向远端网络设备发送第一控制请求报文,远端网络设备在接收到第一控制请求报文之后,如果远端网络设备上存储有目标隧道的信息,表示远端网络设备与UP设备之间关于目标隧道的数据一致,远端网络设备向UP设备回复的第一控制应答报文中携带目标隧道的标识,以及确认重置目标隧道的隧道保活序列号的指示信息,UP设备在接收到第一控制应答报文之后,确定对目标隧道的故障恢复成功。如果远端网络设备上未存储目标隧道的信息,表示远端网络设备与UP设备之间关于目标隧道的数据存在不一致,远端网络设备向UP设备回复的第一控制应答报文中不携带目标隧道的相关信息,或者携带用于指示目标隧道未成功建立的提示信息,UP设备在接收到第一控制应答报文之后,将本地存储的目标隧道的信息删除。
可选地,UP向远端网络设备发送的第一控制请求报文中携带该一条或多条隧道的标识、该一条或多条隧道重置后的隧道保活序列号,以及序列号重置指示信息,也即是,UP设备一次性通过一个控制请求报文与远端网络设备进行关于隧道的数据对账以及重置隧道保活序列号。远端网络设备在接收到第一控制请求报文之后,将自身存储的所有隧道的标识以及确定重置相应隧道的隧道保活序列号的指示信息,通过第一控制应答报文发送给UP设备,UP设备在接收到第一控制应答报文之后,通过对比自身存储的一条或多条隧道的标识与第一控制应答报文携带的隧道的标识,确定UP设备与远端网络设备中共同存储的隧道,并清理仅在UP上存储,而未在远端网络设备上存储的隧道,以完成与远端网络设备之间关于隧道的数据对账和重置隧道保活序列号。
可选地,UP设备在与远端网络设备之间进行数据对账和重置隧道保活序列号之后,拆除用于数据对账和请求重置隧道保活序列号的数据对账隧道。
UP设备与远端网络设备之间进行关于隧道的数据对账之后,UP设备上存储有目标隧道的信息,则UP设备按照重置后的目标隧道的隧道保活序列号,对目标隧道进行隧道保活。
可选地,UP设备根据与远端网络设备之间的通信协议来重置隧道保活序列号,假设UP设备与远端网络设备之间的通信协议为L2TP协议,L2TP协议规定创建一条隧道时的隧道保活序列号为0或1,随着之前CP设备与远端网络设备之间互相发送隧道保活报文进行隧道保活,隧道保活报文携带的隧道报文序列号动态递增,在UP设备通过隧道故障恢复以进行隧道保活时,UP设备需要重置隧道保活序列号为0或者1等,也即重置为起始值。
UP设备向远端网络设备发送第一控制请求报文之后,远端网络设备根据序列号重置指示信息,确定当前需要对目标隧道进行隧道故障恢复,远端网络设备根据重置后的目标隧道的隧道保活序列号,向UP设备发送第一控制应答报文,UP设备接收到第一控制应答报文后确定对目标隧道故障恢复成功。
UP设备在对目标隧道故障恢复成功之后,按照重置后的目标隧道的隧道保活序列号,对目标隧道进行隧道保活。也即是,UP设备从重置后的目标隧道的隧道保活序列号开始,周期性地向远端网络设备发送隧道保活报文,以与远端网络设备周期性地交互隧道保活报文,实现对目标隧道的隧道保活。
可选地,第一控制请求报文和第一隧道数据对账报文均为L2TP协议中的开始控制连接请求(start control connection request,SCCRQ)报文,第一控制应答报文和第一隧道对账应答报文均为L2TP协议中的开始控制连接应答(start control connection reply,SCCRP)报文。
以上仅以该一条或多条隧道中的目标隧道为例,对UP设备进行隧道保活的第二种实现方式进行了介绍,对于该一条或多条隧道中除目标隧道之外的其他隧道,UP设备均能够按照与目标隧道相同的隧道保活方法,通过隧道故障恢复对相应隧道进行隧道保活,本申请实施例对此不再赘述。
由前述可知,在UP设备与CP设备之间的通信正常的情况下,CP设备还向UP设备发送第一会话信息,这样,UP设备除了对目标隧道进行故障恢复之外,还能够更新第一会话信息中目标隧道上承载的会话的信息,以对目标隧道上承载的会话进行故障恢复。
在本申请实施例中,UP设备在创建与远端网络设备之间的数据对账隧道之后,向远端网络设备发送第一会话数据对账报文,第一会话数据对账报文携带一个或多个第一参考会话的标识,该一个或多个第一参考会话为UP设备上存储的目标隧道上承载的会话。UP设备接收远端网络设备发送的第一会话对账应答报文,第一会话对账应答报文携带一个或多个第二参考会话的标识,该一个或多个第二参考会话为远端网络设备上存储的目标隧道上承载的会话。UP设备将该一个或多个第一参考会话的标识与该一个或多个第二参考会话的标识的交集,确定为目标隧道上承载的会话的标识。这样,即可对目标隧道上承载的会话进行对齐。
可选地,第一会话数据对账报文与第一隧道数据对账报文为同一个报文,也即是,UP设备通过数据对账隧道将UP设备上存储的与所述远端网络设备之间建立的隧道的标识以及每条隧道上承载的会话的标识,一次性地发送给远端网络设备,以进行隧道的数据对账以及会话的数据对账。
可选地,UP设备在对目标隧道故障恢复成功之后,再与远端网络设备交互会话信息,以对目标隧道上承载的所有会话进行故障恢复,也即对目标隧道上承载的一个或多个第一参考会话进行故障恢复。这种情况下,第一会话数据对账报文与第一隧道数据对账报文为不同的报文。
示例性地,假设UP设备上存储的目标隧道上承载的会话包括会话1、会话2和会话3,远端网络设备上存储的目标隧道上承载的会话包括会话1和会话2,其中,会话1和会话2为已成功连接的会话,会话3为UP设备与CP设备之间通信故障之前,CP设备与远端网络设备之间未完成连接的会话,也即会话3为半连接状态的会话。CP设备上存储有会话3的信息,并将会话3的信息同步给了UP设备,而远端网络设备上未存储会话3的信息,这种情况下,UP设备向远端网络设备发送第一故障恢复会话查询报文中,携带会话1、会话2和会话3的标识,而远端网络设备向UP设备回复的第一故障恢复会话应答报文仅携带会话1和会话2的标识,那么UP设备在接收到第一故障恢复会话应答报文之后,将本地存储的会话3的信息删除,也即清理半连接状态的会话。
同理,假设UP设备向远端网络设备发送的第一故障恢复会话查询报文携带会话1和会 话2,而远端网络设备向UP设备回复的第一故障恢复会话应答报文携带会话1、会话2和会话3,表示会话3为远端网络设备创建的半连接状态的会话,远端网络设备在接收到第一故障恢复会话查询报文之后,会将自身存储的会话3的信息删除,也即远端网络设备也会清理半连接状态的会话。
可选地,第一会话数据对账报文为L2TP协议中的故障会话查询(failover session query,FSQ)报文,第一会话对账应答报文为L2TP协议中的故障会话应答(failover session response,FSR)报文。
由上述可知,UP设备与远端网络设备之间通过会话故障恢复,将UP设备与远端网络设备之间还未完成建立的会话进行删除,也即清理半连接状态的会话。
需要说明的是,对于该一条或多条隧道中除目标隧道之外的其他隧道上承载的会话,UP设备均能够按照与恢复目标隧道上承载的会话相同的方法,通过会话故障恢复对相应隧道上承载的会话进行会话故障恢复,本申请实施例对此不再赘述。
可选地,UP设备进行隧道保活的第二种实现方式中进行的隧道故障恢复和会话故障恢复,可以采用L2TP RFC 4951规范中提出的故障恢复(failure recovery)功能。CP设备通过UP设备与远端网络设备在建立隧道时,协商是否开启failure recovery功能,如果CP设备、UP设备和远端网络设备上均开启了failure recovery功能,则在UP设备开始进行隧道保活时,启动failure recovery功能来与远端网络设备进行隧道故障恢复以及会话故障恢复。
需要说明的是,在上述第二种实现方式中,UP设备通过与远端网络设备之间进行隧道故障恢复和会话故障恢复,也即通过对隧道和会话的数据对账,以及重置隧道保活序列号,能够保证UP设备更加精确地对UP设备与远端网络设备之间建立的隧道进行隧道保活。
以上仅以该一条或多条隧道中的目标隧道为例对UP设备进行隧道保活的方法进行了介绍,对于该一条或多条隧道中除目标隧道之外的其他隧道,UP设备均能够按照与目标隧道相同的隧道保活方法,进行隧道保活,本申请实施例对此不再赘述。
步骤303:如果CP设备与UP设备之间的通信恢复,则CP设备重新对该一条或多条隧道进行隧道保活,且UP设备停止对该一条或多条隧道进行隧道保活。
在本申请实施例中,在CP设备检测到自身与UP设备之间的通信恢复之后,CP设备需要重新对该一条或多条隧道进行隧道保活,而UP设备在检测到自身与CP设备之间的通信恢复之后停止隧道保活。
由前述可知,CP设备通过控制报文重定向接口和状态控制接口与UP设备进行通信,CP设备监控控制报文重定向接口和状态控制接口的状态,如果CP设备监控到控制报文重定向接口和/或状态控制接口的状态恢复正常,则CP设备确定检测到自身与UP设备之间的通信恢复。
同样地,UP设备通过控制报文重定向接口和状态控制接口与CP设备进行通信,UP设备监控控制报文重定向接口和状态控制接口的状态,如果UP设备监控到控制报文重定向接口和/或状态控制接口的状态恢复正常,则UP设备确定检测到自身与CP设备之间的通信恢复。
在本申请实施例中,CP设备重新进行隧道保活的实现方式为:CP设备重置本地存储的目标隧道的隧道保活序列号,目标隧道为该一条或多条隧道中的一条,CP设备根据重置后的目标隧道的隧道保活序列号,指示远端网络设备对目标隧道的隧道保活序列号进行重置,在 远端网络设备对目标隧道的隧道保活序列号重置成功后,CP设备按照重置后的目标隧道的隧道保活序列号以及目标隧道的标识,通过UP设备对目标隧道进行隧道保活。
其中,CP设备重置本地存储的目标隧道的隧道保活序列号的实现方式,与前述UP设备重置目标隧道的隧道保活序列号的实现方式类似,例如,CP设备重置目标隧道的隧道保活序列号为0或1等,也即重置为通信协议规定的起始值。
在本申请实施例中,CP设备重置目标隧道的隧道保活序列号之后,通过UP设备向远端网络设备发送第二控制请求报文,第二控制请求报文携带目标隧道的标识、重置后的目标隧道的隧道保活序列号,以及序列号重置指示信息,然后,CP设备通过UP设备接收远端网络设备发送的第二控制应答报文,第二控制应答报文用于指示远端网络设备对目标隧道的隧道保活序列号重置成功。
CP设备通过UP设备向远端网络设备发送第二控制请求报文之后,远端网络设备根据序列号重置指示信息,确定当前需要对目标隧道进行隧道故障恢复,远端网络设备根据重置后的目标隧道的隧道保活序列号,向CP设备发送第一控制应答报文,CP设备通过UP设备接收到第二控制应答报文后确定对目标隧道故障恢复成功。
可选地,在本申请实施例中,CP设备进行隧道故障恢复的过程也包括隧道的数据对账和重置隧道保活序列号。
可选地,CP设备重置本地存储的目标隧道的隧道保活序列号之前,创建与远端网络设备之间的数据对账隧道,并通过该数据对账隧道,通过UP设备向远端网络设备发送第二数据对账报文,第二数据对账报文携带CP设备上存储的UP设备与远端网络设备之间建立的隧道的标识,CP设备通过UP设备接收远端网络设备发送的第二对账应答报文,第二对账应答报文携带远端网络设备上存储的与UP设备之间建立的隧道的标识,CP设备将第二数据对账报文携带的隧道的标识与第二对账应答报文携带的隧道的标识的交集,确定为一条或多条隧道的标识。
由于在UP设备与远端网络设备交互隧道保活报文进行隧道保活的过程中,远端网络设备可能会向UP设备发送拆除一条隧道的拆除请求,以主动拆除隧道,UP设备接收到该拆除请求后,可以拆除相应隧道,也可以不拆除相应隧道,也即是,在UP设备进行隧道保活的过程中,UP设备与远端网络设备之间建立的隧道会更新,基于此,在CP设备与UP设备之间的通信恢复之后,CP设备与远端网络设备之间通过隧道故障恢复,将UP设备与远端网络设备之间的隧道进行关于隧道的数据对账,以清理CP上存储的已被拆除的隧道,保证CP设备与远端网络设备之间的隧道一致性。
在本申请实施例中,CP设备先进行数据对账,再重置隧道保活序列号。可选地,CP设备也可以先重置本地存储的每条隧道的隧道保活序列号,之后,通过创建的数据对账隧道,向远端网络设备发送用于进行隧道的数据对账和重置隧道保活序列号的控制请求报文,以通过控制请求报文与远端网络设备进行关于隧道的数据对账以及重置隧道保活序列号。也即是,第二控制请求报文与第二隧道数据对账报文可以为同一个报文,第二控制应答报文与第二隧道对账应答报文可以为同一个报文。
可选地,CP设备重置本地存储的每条隧道的隧道保活序列号,通过UP设备与远端网络设备之间建立一条数据对账隧道(也可以称为恢复隧道),并通过UP设备将第二控制请求报文通过该数据对账隧道发送给远端网络设备,远端网络设备在接收到第二控制请求报文之后, 如果远端网络设备上存储有目标隧道的信息,表示远端网络设备与CP设备之间关于目标隧道的数据一致,远端网络设备向CP设备回复的第二控制应答报文中携带目标隧道的标识,以及确认重置目标隧道的隧道保活序列号的指示信息,CP设备在通过UP设备接收到第二控制应答报文之后,确定对目标隧道的故障恢复成功。如果远端网络设备上未存储目标隧道的信息,表示远端网络设备与CP设备之间关于目标隧道的数据存在不一致,远端网络设备向CP设备回复的第二控制应答报文中不携带目标隧道的相关信息,或者携带用于指示目标隧道未成功建立的提示信息,CP设备在通过UP设备接收到第二控制应答报文之后,将本地存储的目标隧道的信息删除。
可选地,CP通过UP设备向远端网络设备发送的第二控制请求报文中携带该一条或多条隧道的标识、该一条或多条隧道重置后的隧道保活序列号,以及序列号重置指示信息,也即是,CP设备一次性通过一个控制请求报文与远端网络设备进行关于隧道的数据对账以及重置隧道保活序列号。远端网络设备在接收到第二控制请求报文之后,将自身存储的所有隧道的标识以及确定重置相应隧道的隧道保活序列号的指示信息,通过第二控制应答报文发送给CP设备,CP设备在通过UP设备接收到第二控制应答报文之后,通过对比自身存储的一条或多条隧道的标识与第二控制应答报文携带的隧道的标识,确定CP设备与远端网络设备中共同存储的隧道,并清理仅在CP上存储,而未在远端网络设备上存储的隧道,以完成与远端网络设备之间关于隧道的数据对账和重置隧道保活序列号。
示例性地,假设在CP设备与UP设备之间的通信故障之前,CP设备最后一次同步给UP设备的隧道信息包括隧道1、隧道2和隧道3的信息,在UP设备与CP设备之间的通信发生故障,UP设备进行隧道保活的过程中,隧道3被远端网络设备拆除,那么CP设备与UP设备之间的通信恢复之后,CP设备通过与远端网络设备进行隧道故障恢复,将隧道1和隧道2的隧道保活序列号与远端网络设备协商重置,之后对隧道1和隧道2进行隧道保活。对于隧道3,CP设备向远端网络设备发送重置隧道3的隧道保活序列号的控制请求报文之后,由于远端网络设备上已删除隧道3的信息,因此,远端网络设备会向CP设备回复未找到隧道3的控制应答报文,CP设备接收到该控制应答报文之后,将隧道3的信息删除。
可选地,第二控制请求报文和第二隧道数据对账报文均为L2TP协议中的SCCRQ报文,第二控制应答报文和第二隧道对账应答报文均为L2TP协议中的SCCRP报文。
可选地,CP设备在于远端网络设备之间进行数据对账和重置隧道保活序列号之后,拆除用于数据对账和请求重置隧道保活序列号的数据对账隧道。
CP设备与远端网络设备之间进行关于隧道的数据对账之后,CP设备上存储有目标隧道的信息,则CP设备按照重置后的目标隧道的隧道保活序列号,通过UP设备对目标隧道进行隧道保活。
以上仅以该一条或多条隧道中的目标隧道为例,对CP设备重新进行隧道保活的实现方式进行了介绍,对于该一条或多条隧道中除目标隧道之外的其他隧道,CP设备均能够按照与目标隧道相同的隧道保活方法,通过隧道故障恢复对相应隧道进行隧道保活,本申请实施例对此不再赘述。
在本申请实施例中,CP设备除了通过UP设备对目标隧道进行故障恢复之外,还能够通过UP设备更新自身存储的目标隧道上承载的会话的信息,以对目标隧道上承载的会话进行故障恢复。
在本申请实施例中,CP设备在创建与远端网络设备之间的数据对账隧道之后,通过UP设备向远端网络设备发送第二复会话数据对账报文,第二会话数据对账报文携带一个或多个第一参考会话的标识,该一个或多个第一参考会话为CP设备上存储的目标隧道上承载的会话。CP设备通过UP设备接收远端网络设备发送的第二会话对账应答报文,第二会话对账应答报文携带一个或多个第三参考会话的标识,该一个或多个第三参考会话为远端网络设备上存储的目标隧道上承载的会话。CP设备将该一个或多个第一参考会话的标识与该一个或多个第三参考会话的标识的交集,确定为目标隧道上承载的会话的标识。这样,即可对目标隧道上承载的会话进行对齐。
可选地,第二会话数据对账报文与第二隧道数据对账报文为同一个报文,也即是,CP设备通过数据对账隧道将CP设备上存储的UP设备与所述远端网络设备之间建立的隧道的标识以及每条隧道上承载的会话的标识,一次性地发送给远端网络设备,以进行隧道的数据对账以及会话的数据对账。
由前述可知,在UP设备进行隧道保活的过程中,UP设备与远端网络设备之间建立的隧道会拆除,除此之外,UP设备与远端网络设备之间建立的承载在隧道上的会话也会被拆除,基于此,在CP设备与UP设备之间的通信恢复之后,CP设备与远端网络设备之间通过会话故障恢复,将CP设备上存储的已拆除的会话删除,也即与远端网络设备进行一次关于会话的数据对账,以保证CP设备与远端网络设备之间的会话一致性。
可选地,第二会话数据对账报文为L2TP协议中的FSQ报文,第二会话对账应答报文为L2TP协议中的FSR报文。
需要说明的是,对于该一条或多条隧道中除目标隧道之外的其他隧道上承载的会话,CP设备均能够按照与恢复目标隧道上承载的会话相同的方法,通过会话故障恢复对相应隧道上承载的会话进行会话故障恢复,本申请实施例对此不再赘述。
在本申请实施例中,CP设备重新进行隧道保活的实现方式中,进行隧道故障恢复和会话故障恢复的实现方式,与UP设备相似,也即是,CP设备重新进行隧道保活中进行的隧道故障恢复和会话故障恢复,也可以采用L2TP RFC 4951规范中提出的failure Recovery功能。由前述可知,CP设备通过UP设备与远端网络设备在建立隧道时,协商是否开启failure recovery功能,如果CP设备、UP设备和远端网络设备上均开启了failure recovery功能,则在CP设备开始重新进行隧道保活时,启动failure recovery功能来与远端网络设备进行隧道故障恢复以及会话故障恢复。
需要说明的是,对于该一条或多条隧道中除目标隧道之外的其他隧道,CP设备均能够按照与目标隧道相同的故障恢复方法,进行隧道故障恢复以及会话故障恢复,本申请实施例对此不再赘述。
在本申请实施例中,CP设备通过UP设备进行隧道故障恢复之后,向UP设备发送第二隧道信息,UP设备接收CP设备发送的第二隧道信息,UP设备根据第二隧道信息,更新本地存储的隧道信息。其中,第二隧道信息包括第一时刻CP设备上存储的UP设备与远端网络设备之间建立的一条或多条隧道的信息,第一时刻是指UP设备与CP设备之间的通信恢复之后,CP设备通过UP设备与远端网络设备之间完成隧道故障恢复或会话故障恢复的时刻。也即是,CP设备再次向UP设备同步隧道信息。
可选地,第二隧道信息携带在PFCP更新请求报文中,第二隧道信息的详细介绍可以参 照前述对第一隧道信息的相关介绍,这里不再赘述。
在本申请实施例中,CP设备通过UP设备对目标隧道上的会话进行故障恢复之后,向UP设备发送第二会话信息,UP设备接收CP设备发送的第二会话信息,UP设备根据第二会话信息,更新本地存储的会话信息。其中,第二会话信息包括第二时刻CP设备上存储的UP设备与远端网络设备之间建立的一条或多条隧道上承载的会话的信息。也即是,CP设备再次向UP设备同步会话信息。
可选地,第二时刻是指CP设备与UP设备之间的通信恢复之后,CP设备通过UP设备与远端网络设备之间完成会话故障恢复的时刻。
可选地,第二会话信息携带在PFCP更新请求报文中,第二会话信息的详细介绍可以参照前述对第一会话信息的相关介绍,这里不再赘述。
在第一时刻为CP设备通过UP设备与远端网络设备之间完成隧道故障恢复的时刻的情况下,CP设备可以在对该一条或多条隧道进行隧道故障恢复之后,向UP设备发送第二隧道信息,在对该一条或多条隧道上承载的会话进行会话故障恢复之后,向UP设备发送第二会话信息,或者,向UP设备发送第三隧道信息和第二会话信息,其中,第三隧道信息包括第二时刻CP设备上存储的UP设备与远端网络设备之间建立的一条或多条隧道上承载的会话的信息。可选地,第三隧道信息和第二会话信息携带在同一个PFCP报文中,或者携带在不同的PFCP报文中。
在第一时刻和第二时刻均为CP设备通过UP设备与远端网络设备之间完成会话故障恢复的时刻的情况下,CP设备可以在对该一条或多条隧道进行隧道故障恢复以及会话故障恢复之后,向UP设备发送第二隧道信息和第二会话信息,第二隧道信息和第二会话信息携带在一个PFCP更新请求报文中,或者携带在不同的PFCP更新请求报文中。
可选地,对于该一条或多条隧道中每条隧道上承载的会话,CP设备每恢复一条隧道上承载的会话之后,通过UP设备向远端网络设备发送该隧道上承载的会话的信息,以通过多次发送的方式将第二会话信息同步给UP设备。
可选地,在申请实施例中,UP设备在接收到携带第二隧道信息和/或第二会话信息的PFCP更新请求报文之后,向CP设备发送PFCP更新应答报文。PFCP更新应答报文的相关介绍可以参照前述表11的相关描述。
在本申请实施例中,CP设备与远端网络设备进行隧道故障恢复和会话故障会话后,向UP设备同步一次隧道信息和会话信息之后,仍继续通过即时的方式或者周期性的方式,向UP设备同步最新的隧道信息和会话信息,以备后续UP设备与CP设备之间再次发生通信故障。
接下来参照图4对本申请实施例提供的隧道保活报文结合示例性应用场景再次进行解释说明。参见图4,终端为一个家庭网关,家庭网关通过点到点协议(point-to-point protocol,PPP)请求接入网络,CP设备(CP-LAC)通过在UP设备(UP-LAC)与远端网络设备(LNS)之间建立隧道和会话,将终端接入远端的网络,CP设备通过UP设备与远端网络设备之间发送Hello报文/ZLB报文进行隧道保活,同时,CP设备将L2TP隧道信息和会话信息同步给UP设备。在UP设备与CP设备之间的通信发生故障的情况下,CP设备检测到故障,停止隧道保活,UP设备检测到故障,开始进行隧道保活。UP设备与远端网络设备之间同步隧道和会话信息,并互相发送隧道保活报文进行隧道保活。在UP设备与CP设备之间的通信恢复之后,UP设备停止隧道保活,CP设备重新进行隧道保活。CP设备通过UP设备与远端网络设 备之间同步隧道和会话信息,并互相发送隧道保活报文进行隧道保活,另外,CP设备将此时的隧道和会话信息同步给UP设备。其中,CP设备与UP设备之间可以通过PFCP更新请求报文同步隧道和会话信息。
在本申请实施例中,通过在UP设备上设置一个L2TP代理模块,实现在UP设备上进行隧道保活的功能。示例性地,参见图5、表12和表13,UP设备包括PFCP协议模块、PFCP L2TP模块和L2TP代理模块,CP设备包括LAC功能模块、LNS功能模块、PFCP L2TP模块和PFCP协议模块。其中,CP设备通过SCi接口向UP设备发送PFCP更新请求报文,UP设备通过PFCP协议模块解码PFCP更新请求报文的消息头,UP设备的PFCP协议模块将解码后得到的PFCP更新请求报文的消息体发送给PFCP L2TP模块,UP设备的PFCP L2TP模块解析该消息体,得到隧道信息和/会话信息,并将隧道信息和/会话信息发送给L2TP代理模块,通过L2TP代理模块存储隧道信息和/会话信息,并根据本申请实施例提供的隧道保活方法,在UP设备与CP设备之间的通信发生故障的情况下,进行隧道保活。在本申请实施例中,UP设备上的各个模块的功能描述详见表12,CP设备上各个模块的功能描述详见表13。
表12
Figure PCTCN2021114141-appb-000010
表13
Figure PCTCN2021114141-appb-000011
综上所述,在本申请实施例中,在UP设备与CP设备之间通信故障之前,UP设备接收CP设备同步的隧道信息,在UP设备与CP之间的通信故障后,由UP设备根据隧道信息进行隧道保活,也即由UP设备维持与远端网络设备之间的隧道,这样就不会因为CP设备与UP设备之间的通信故障而触发拆除隧道,本方案能够保证终端与远端的网络的连接不会因此 中断,也即保证用户业务不受损。
图6是本申请实施例提供的一种网络设备600的结构示意图,该网络设备600可以由软件、硬件或者两者的结合实现成为UP设备的部分或者全部,该UP设备可以为前述实施例所示的UP设备。在本申请实施例中,CP设备和UP设备用于与远端网络设备进行交互来保证终端接入网络。参见图6,该网络设备600包括:第一接收模块601和隧道保活模块602。
第一接收模块601,用于接收CP设备发送的第一隧道信息,第一隧道信息包括UP设备与远端网络设备之间建立的一条或多条隧道的信息;具体实现方式请参考图3实施例中步骤301的详细描述,这里不再赘述。
隧道保活模块602,用于如果检测到UP设备与CP设备之间的通信发生故障,则根据第一隧道信息,对该一条或多条隧道进行隧道保活。具体实现方式请参考图3实施例中步骤302的详细描述,这里不再赘述。
可选地,第一隧道信息包括一条或多条隧道的标识;
隧道保活模块602包括:
监听单元,用于监听远端网络设备发送的第一隧道保活报文,第一隧道保活报文携带目标隧道的标识和隧道保活序列号;
第一发送单元,用于根据目标隧道的隧道保活序列号以及该一条或多条隧道的标识,向远端网络设备发送第二隧道保活报文。具体实现方式请参考图3实施例中步骤302的详细描述,这里不再赘述。
可选地,第一隧道信息包括一条或多条隧道的标识;
隧道保活模块602包括:
重置单元,用于重置目标隧道的隧道保活序列号,目标隧道为该一条或多条隧道中的一条;
指示单元,用于根据重置后的目标隧道的隧道保活序列号,指示远端网络设备对目标隧道的隧道保活序列号进行重置;
隧道保活单元,用于在远端网络设备对目标隧道的隧道保活序列号重置成功后,按照重置后的目标隧道的隧道保活序列号以及目标隧道的标识,对目标隧道进行隧道保活。具体实现方式请参考图3实施例中步骤302的详细描述,这里不再赘述。
可选地,指示单元具体用于:
向远端网络设备发送第一控制请求报文,第一控制请求报文携带目标隧道的标识、重置后的目标隧道的隧道保活序列号,以及序列号重置指示信息;
接收远端网络设备发送的第一控制应答报文,第一控制应答报文用于指示远端网络设备对目标隧道的隧道保活序列号重置成功。具体实现方式请参考图3实施例中步骤302的详细描述,这里不再赘述。
可选地,隧道保活模块602还包括:
创建单元,用于创建与远端网络设备之间的数据对账隧道;
第二发送单元,用于通过该数据对账隧道,向远端网络设备发送第一隧道数据对账报文,第一隧道数据对账报文携带UP设备上存储的与远端网络设备之间建立的隧道的标识;
第一接收单元,用于接收远端网络设备发送的第一隧道对账应答报文,第一隧道对账应 答报文携带远端网络设备上存储的与UP设备之间建立的隧道的标识;
第一确定单元,用于将第一隧道数据对账报文携带的隧道的标识与第一隧道对账应答报文携带的隧道的标识的交集,确定为该一条或多条隧道的标识。
可选地,该网络设备600还包括:
第二接收模块,用于接收CP设备发送的第一会话信息,第一会话信息包括该一条或多条隧道上承载的会话的信息;具体实现方式请参考图3实施例中步骤301的相关描述,这里不再赘述。
隧道保活模块602还包括:
第三发送单元,用于向远端网络设备发送第一会话数据对账报文,第一会话数据对账报文携带一个或多个第一参考会话的标识,该一个或多个第一参考会话为UP设备上存储的目标隧道上承载的会话;
第二接收单元,用于接收远端网络设备发送的第一会话对账应答报文,第一会话对账应答报文携带一个或多个第二参考会话的标识,该一个或多个第二参考会话为远端网络设备上存储的目标隧道上承载的会话;
第二确定单元,用于将该一个或多个第一参考会话的标识与该一个或多个第二参考会话的标识的交集,确定为目标隧道上承载的会话的标识。具体实现方式请参考图3实施例中步骤302的详细描述,这里不再赘述。
可选地,该网络设备600还包括:
处理模块,用于如果检测到UP设备与CP设备之间的通信恢复,则停止对该一条或多条隧道进行隧道保活。
可选地,该网络设备600还包括:
第三接收模块,用于接收CP设备发送的第二隧道信息,第二隧道信息包括第一时刻CP设备上存储的UP设备与远端网络设备之间建立的一条或多条隧道的信息,第一时刻是指UP设备与CP设备之间的通信恢复之后,CP设备通过UP设备与远端网络设备之间完成隧道故障恢复或会话故障恢复的时刻;具体实现方式请参考图3实施例中步骤303的详细描述,这里不再赘述。
更新模块,用于根据第二隧道信息,更新本地存储的隧道信息。
可选地,UP设备通过控制报文重定向接口和状态控制接口与CP设备进行通信;
隧道保活模块602包括:
监控单元,用于监控控制报文重定向接口和状态控制接口的状态;
第三确定单元,用于如果监控到控制报文重定向接口和/或状态控制接口的状态异常,则确定检测到UP设备与CP设备之间的通信发生故障。具体实现方式请参考图3实施例中步骤302的详细描述,这里不再赘述。
可选地,第一隧道信息携带在PFCP更新请求报文中,该一条或多条隧道为L2TP隧道,该一条或多条隧道中每条隧道的信息包括隧道描述信息;
如果L2TP隧道是根据IPv4创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv4地址和隧道远端IPv4地址;
如果L2TP隧道是根据IPv6创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv6地址和隧道远端IPv6地址。具体实现方式请参考图3实施例中步骤301的详 细描述,这里不再赘述。
可选地,第二隧道信息携带在PFCP更新请求报文中。
可选地,第一会话信息携带在PFCP更新请求报文中,该一条或多条隧道中每条隧道上承载的会话的信息包括隧道本地标识、会话本地标识和会话远端标识。具体实现方式请参考图3实施例中步骤301的详细描述,这里不再赘述。
在本申请实施例中,在UP设备与CP设备之间通信故障之前,UP设备接收CP设备同步的隧道信息,在UP设备与CP之间的通信故障后,由UP设备根据隧道信息进行隧道保活,也即由UP设备维持与远端网络设备之间的隧道,这样就不会因为CP设备与UP设备之间的通信故障而触发拆除隧道,本方案能够保证终端与远端的网络连接不会因此中断,也即保证用户业务不受损。
需要说明的是:上述实施例提供的网络设备在进行隧道保活时,仅以上述各功能模块的划分进行举例说明,实际应用中,可以根据需要而将上述功能分配由不同的功能模块完成,即将装置的内部结构划分成不同的功能模块,以完成以上描述的全部或者部分功能。另外,上述实施例提供的网络设备与隧道保活方法实施例属于同一构思,其具体实现过程详见方法实施例,这里不再赘述。
图7是本申请实施例提供的一种网络设备700的结构示意图,该网络设备700可以由软件、硬件或者两者的结合实现成为CP设备的部分或者全部,该CP设备可以为前述实施例所示的CP设备。在本申请实施例中,CP设备和UP设备用于与远端网络设备进行交互来保证终端接入网络。参见图7,该网络设备700包括:第一发送模块701和处理模块702。
第一发送模块701,用于向UP设备发送第一隧道信息,第一隧道信息包括UP设备与远端网络设备之间建立的一条或多条隧道的信息;具体实现方式请参考图3实施例中步骤301的详细描述,这里不再赘述。
处理模块702,用于如果检测到CP设备与UP设备之间的通信发生故障,则停止对该一条或多条隧道进行隧道保活;具体实现方式请参考图3实施例中步骤302的详细描述,这里不再赘述。
其中,第一隧道信息用于UP设备在检测到自身与CP设备之间的通信发生故障时,根据第一隧道信息对UP设备与远端网络设备之间建立的一条或多条隧道进行隧道保活。具体实现方式请参考图3实施例中步骤302的详细描述,这里不再赘述。
可选地,参见图8,该网络设备700还包括:
隧道保活模块703,用于如果检测到CP设备与UP设备之间的通信恢复,则重新对该一条或多条隧道进行隧道保活。具体实现方式请参考图3实施例中步骤303的详细描述,这里不再赘述。
可选地,隧道保活模块703包括:
重置单元,用于重置本地存储的该一条或多条隧道中每条隧道的隧道保活序列号;
指示单元,用于根据重置后的目标隧道的隧道保活序列号,指示远端网络设备对目标隧道的隧道保活序列号进行重置;
隧道保活单元,用于在远端网络设备对目标隧道的隧道保活序列号重置成功后,按照重置后的目标隧道的隧道保活序列号以及目标隧道的标识,通过UP设备对目标隧道进行隧道 保活。具体实现方式请参考图3实施例中步骤3032的详细描述,这里不再赘述。
可选地,指示单元具体用于:
通过UP设备向远端网络设备发送第二控制请求报文,第二控制请求报文携带目标隧道的标识、重置后的目标隧道的隧道保活序列号,以及序列号重置指示信息;
通过UP设备接收远端网络设备发送的第二控制应答报文,第二控制应答报文用于指示远端网络设备对目标隧道的隧道保活序列号重置成功。具体实现方式请参考图3实施例中步骤303的详细描述,这里不再赘述。
可选地,隧道保活模块703还包括:
创建单元,用于创建与远端网络设备之间的数据对账隧道;
第一发送单元,用于通过数据对账隧道,通过UP设备向远端网络设备发送第二数据对账报文,第二数据对账报文携带CP设备上存储的UP设备与远端网络设备之间建立的隧道的标识;
第一接收单元,用于通过UP设备接收远端网络设备发送的第二对账应答报文,第二对账应答报文携带远端网络设备上存储的与UP设备之间建立的隧道的标识;
第一确定单元,用于将第二数据对账报文携带的隧道的标识与第二对账应答报文携带的隧道的标识的交集,确定为一条或多条隧道的标识。
可选地,隧道保活模块703还包括:
第二发送单元,用于通过UP设备向远端网络设备发送第二会话数据对账报文,第二会话数据对账报文携带一个或多个第一参考会话的标识,该一个或多个第一参考会话为CP设备上存储的目标隧道上承载的会话;
第二接收单元,用于通过UP设备接收远端网络设备发送的第二会话对账应答报文,第二会话对账应答报文携带一个或多个第三参考会话的标识,该一个或多个第三参考会话为远端网络设备上存储的目标隧道上承载的会话;
第二确定单元,用于将该一个或多个第一参考会话的标识和一个或多个第三参考会话的标识的交集,确定为目标隧道上承载的会话的标识。具体实现方式请参考图3实施例中步骤303的详细描述,这里不再赘述。
可选地,隧道保活模块703还包括:
第三发送单元,用于向UP设备发送第二隧道信息,第二隧道信息包括第一时刻CP设备上存储的UP设备与远端网络设备之间建立的一条或多条隧道的信息,第一时刻是指UP设备与CP设备之间的通信恢复之后,CP设备通过UP设备与远端网络设备之间完成隧道故障恢复或会话故障恢复的时刻。具体实现方式请参考图3实施例中步骤303的详细描述,这里不再赘述。
可选地,CP设备通过控制报文重定向接口和状态控制接口与UP设备进行通信;
处理模块702包括:
监控单元,用于监控控制报文重定向接口和状态控制接口的状态;
第三确定单元,用于如果监控到控制报文重定向接口和/或状态控制接口的状态异常,则确定检测到CP设备与UP设备之间的通信发生故障。具体实现方式请参考图3实施例中步骤302的详细描述,这里不再赘述。
可选地,第一隧道信息携带在PFCP更新请求报文中,该一条或多条隧道为二层隧道协 议L2TP隧道,该一条或多条隧道中每条隧道的信息包括隧道描述信息;
如果L2TP隧道是根据IPv4创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv4地址和隧道远端IPv4地址;
如果L2TP隧道是根据IPv6创建的,则隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv6地址和隧道远端IPv6地址。具体实现方式请参考图3实施例中步骤301的详细描述,这里不再赘述。
可选地,第二隧道信息携带在PFCP更新请求报文中。
可选地,该网络设备700还包括:
第四发送模块,用于向UP设备发送第一会话信息,第一会话信息包括该一条或多条隧道上承载的会话的信息。
可选地,第一会话信息携带在PFCP更新请求报文中,该一条或多条隧道中每条隧道上承载的会话的信息包括隧道本地标识、会话本地标识和会话远端标识。具体实现方式请参考图3实施例中步骤301的详细描述,这里不再赘述。
可选地,第一发送模块包括:
第五发送单元,用于每创建一条隧道,向UP设备发送创建的一条隧道的信息,一条或多条隧道包括创建的一条隧道;或者,
第六发送单元,用于周期性地向UP设备发送自身存储的隧道的信息。
在本申请实施例中,在UP设备与CP设备之间通信故障之前,UP设备接收CP设备同步的隧道信息,在UP设备与CP之间的通信故障后,由UP设备根据隧道信息进行隧道保活,也即由UP设备维持与远端网络设备之间的隧道,这样就不会因为CP设备与UP设备之间的通信故障而触发拆除隧道,本方案能够保证终端与远端的网络连接不会因此中断,也即保证用户业务不受损。
需要说明的是:上述实施例提供的网络设备在进行隧道保活时,仅以上述各功能模块的划分进行举例说明,实际应用中,可以根据需要而将上述功能分配由不同的功能模块完成,即将装置的内部结构划分成不同的功能模块,以完成以上描述的全部或者部分功能。另外,上述实施例提供的网络设备与隧道保活方法实施例属于同一构思,其具体实现过程详见方法实施例,这里不再赘述。
本申请实施例提供了一种网络系统,也可称为隧道保活系统,该网络系统包括CP设备和UP设备,以及远端网络设备,CP设备和UP设备用于与远端网络设备进行交互来保证终端接入网络。其中,UP设备和CP设备具有实现前述实施例提供的隧道保活方法的相应功能,以通过该系统进行隧道保活。具体实现方式请参考图3实施例的详细描述,这里不再赘述。
在本申请实施例中,在UP设备与CP设备之间通信故障之前,UP设备接收CP设备同步的隧道信息,在UP设备与CP之间的通信故障后,由UP设备根据隧道信息进行隧道保活,也即由UP设备维持与远端网络设备之间的隧道,这样就不会因为CP设备与UP设备之间的通信故障而触发拆除隧道,本方案能够保证终端与远端的网络连接不会因此中断,也即保证用户业务不受损。
需要说明的是:上述实施例提供的网络系统与隧道保活方法实施例属于同一构思,其具体实现过程详见方法实施例,这里不再赘述。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意结合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络或其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如:同轴电缆、光纤、数据用户线(digital subscriber line,DSL))或无线(例如:红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质,或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如:软盘、硬盘、磁带)、光介质(例如:数字通用光盘(digital versatile disc,DVD))或半导体介质(例如:固态硬盘(solid state disk,SSD))等。值得注意的是,本申请实施例提到的计算机可读存储介质可以为非易失性存储介质,换句话说,可以是非瞬时性存储介质。
应当理解的是,本文提及的“至少一个”是指一个或多个,“多个”是指两个或两个以上。在本申请实施例的描述中,除非另有说明,“/”表示或的意思,例如,A/B可以表示A或B;本文中的“和/或”仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,为了便于清楚描述本申请实施例的技术方案,在本申请的实施例中,采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定,并且“第一”、“第二”等字样也并不限定一定不同。
以上所述为本申请提供的实施例,并不用以限制本申请,凡在本申请的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本申请的保护范围之内。

Claims (51)

  1. 一种隧道保活方法,其特征在于,控制面CP设备和用户面UP设备用于与远端网络设备进行交互来保证终端接入网络,所述方法包括:
    所述UP设备接收所述CP设备发送的第一隧道信息,所述第一隧道信息包括所述UP设备与所述远端网络设备之间建立的一条或多条隧道的信息;
    如果所述UP设备检测到自身与所述CP设备之间的通信发生故障,则所述UP设备根据所述第一隧道信息,对所述一条或多条隧道进行隧道保活。
  2. 如权利要求1所述的方法,其特征在于,所述第一隧道信息包括所述一条或多条隧道的标识;
    所述UP设备根据所述第一隧道信息,对所述一条或多条隧道进行隧道保活,包括:
    所述UP设备监听所述远端网络设备发送的第一隧道保活报文,所述第一隧道保活报文携带目标隧道的标识和隧道保活序列号;
    所述UP设备根据所述目标隧道的标识和隧道保活序列号,以及所述一条或多条隧道的标识,向所述远端网络设备发送第二隧道保活报文。
  3. 如权利要求1所述的方法,其特征在于,所述第一隧道信息包括所述一条或多条隧道的标识;
    所述UP设备根据所述第一隧道信息,对所述一条或多条隧道进行隧道保活,包括:
    所述UP设备重置目标隧道的隧道保活序列号,所述目标隧道为所述一条或多条隧道中的一条;
    所述UP设备根据重置后的所述目标隧道的隧道保活序列号,指示所述远端网络设备对所述目标隧道的隧道保活序列号进行重置;
    在所述远端网络设备对所述目标隧道的隧道保活序列号重置成功后,所述UP设备按照重置后的所述目标隧道的隧道保活序列号以及所述目标隧道的标识,对所述目标隧道进行隧道保活。
  4. 如权利要求3所述的方法,其特征在于,所述UP设备根据重置后的所述目标隧道的隧道保活序列号,指示所述远端网络设备对所述目标隧道的隧道保活序列号进行重置,包括:
    所述UP设备向所述远端网络设备发送第一控制请求报文,所述第一控制请求报文携带所述目标隧道的标识、所述重置后的所述目标隧道的隧道保活序列号,以及序列号重置指示信息;
    所述UP设备接收所述远端网络设备发送的第一控制应答报文,所述第一控制应答报文用于指示所述远端网络设备对所述目标隧道的隧道保活序列号重置成功。
  5. 如权利要求3或4所述的方法,其特征在于,所述UP设备重置目标隧道的隧道保活序列号之前,还包括:
    所述UP设备创建与所述远端网络设备之间的数据对账隧道;
    所述UP设备通过所述数据对账隧道,向所述远端网络设备发送第一隧道数据对账报文,所述第一隧道数据对账报文携带所述UP设备上存储的与所述远端网络设备之间建立的隧道的标识;
    所述UP设备接收所述远端网络设备发送的第一隧道对账应答报文,所述第一隧道对账应答报文携带所述远端网络设备上存储的与所述UP设备之间建立的隧道的标识;
    所述UP设备将所述第一隧道数据对账报文携带的隧道的标识与所述第一隧道对账应答报文携带的隧道的标识的交集,确定为所述一条或多条隧道的标识。
  6. 如权利要求5所述的方法,其特征在于,所述UP设备根据所述第一隧道信息,对所述一条或多条隧道进行隧道保活之前,还包括:
    所述UP设备接收所述CP设备发送的第一会话信息,所述第一会话信息包括所述一条或多条隧道上承载的会话的信息;
    所述UP设备创建与所述远端网络设备之间的数据对账隧道之后,还包括:
    所述UP设备向所述远端网络设备发送第一会话数据对账报文,所述第一会话数据对账报文携带一个或多个第一参考会话的标识,所述一个或多个第一参考会话为所述UP设备上存储的所述目标隧道上承载的会话;
    所述UP设备接收所述远端网络设备发送的第一会话对账应答报文,所述第一会话对账应答报文携带一个或多个第二参考会话的标识,所述一个或多个第二参考会话为所述远端网络设备上存储的所述目标隧道上承载的会话;
    所述UP设备将所述一个或多个第一参考会话的标识与所述一个或多个第二参考会话的标识的交集,确定为所述目标隧道上承载的会话的标识。
  7. 如权利要求1-6任一所述的方法,其特征在于,所述UP设备根据所述第一隧道信息,对所述一条或多条隧道进行隧道保活之后,还包括:
    如果所述UP设备检测到自身与所述CP设备之间的通信恢复,则所述UP设备停止对所述一条或多条隧道进行隧道保活。
  8. 如权利要求7所述的方法,其特征在于,所述UP设备停止对所述一条或多条隧道进行隧道保活之后,还包括:
    所述UP设备接收所述CP设备发送的第二隧道信息,所述第二隧道信息包括第一时刻所述CP设备上存储的所述UP设备与所述远端网络设备之间建立的一条或多条隧道的信息,所述第一时刻是指所述UP设备与所述CP设备之间的通信恢复之后,所述CP设备通过所述UP设备与所述远端网络设备之间完成隧道故障恢复或会话故障恢复的时刻;
    所述UP设备根据所述第二隧道信息,更新本地存储的隧道信息。
  9. 如权利要求1-8任一所述的方法,其特征在于,所述UP设备通过控制报文重定向接口和状态控制接口与所述CP设备进行通信;
    所述UP设备检测到自身与所述CP设备之间的通信发生故障,包括:
    所述UP设备监控所述控制报文重定向接口和所述状态控制接口的状态;
    如果所述UP设备监控到所述控制报文重定向接口和/或所述状态控制接口的状态异常,则所述UP设备确定检测到自身与所述CP设备之间的通信发生故障。
  10. 如权利要求1-9任一所述的方法,其特征在于,所述第一隧道信息携带在包转发控制协议PFCP更新请求报文中,所述一条或多条隧道为二层隧道协议L2TP隧道,所述一条或多条隧道中每条隧道的信息包括隧道描述信息;
    如果所述L2TP隧道是根据第四版互联网协议IPv4创建的,则所述隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv4地址和隧道远端IPv4地址;
    如果所述L2TP隧道是根据第六版互联网协议IPv6创建的,则所述隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv6地址和隧道远端IPv6地址。
  11. 如权利要求8所述的方法,其特征在于,所述第二隧道信息携带在PFCP更新请求报文中。
  12. 如权利要求6所述的方法,其特征在于,所述第一会话信息携带在PFCP更新请求报文中,所述一条或多条隧道中每条隧道上承载的会话的信息包括隧道本地标识、会话本地标识和会话远端标识。
  13. 一种隧道保活方法,其特征在于,控制面CP设备和用户面UP设备用于与远端网络设备进行交互来保证终端接入网络,所述方法包括:
    所述CP设备向所述UP设备发送第一隧道信息,所述第一隧道信息包括所述UP设备与所述远端网络设备之间建立的一条或多条隧道的信息;
    如果所述CP设备检测到自身与所述UP设备之间的通信发生故障,则所述CP设备停止对所述一条或多条隧道进行隧道保活;
    其中,所述第一隧道信息用于所述UP设备在检测到自身与所述CP设备之间的通信发生故障时,根据所述第一隧道信息对所述UP设备与所述远端网络设备之间建立的一条或多条隧道进行隧道保活。
  14. 如权利要求13所述的方法,其特征在于,所述如果所述CP设备检测到自身与所述UP设备之间的通信发生故障,则所述CP设备停止对所述一条或多条隧道进行隧道保活之后,还包括:
    如果所述CP设备检测到自身与所述UP设备之间的通信恢复,则所述CP设备重新对所述一条或多条隧道进行隧道保活。
  15. 如权利要求14所述的方法,其特征在于,所述CP设备重新对所述一条或多条隧道进行隧道保活,包括:
    所述CP设备重置本地存储的目标隧道的隧道保活序列号,所述目标隧道为所述一条或多条隧道中的一条;
    所述CP设备根据重置后的所述目标隧道的隧道保活序列号,指示所述远端网络设备对所述目标隧道的隧道保活序列号进行重置;
    在所述远端网络设备对所述目标隧道的隧道保活序列号重置成功后,所述CP设备按照重置后的所述目标隧道的隧道保活序列号以及所述目标隧道的标识,通过所述UP设备对所述目标隧道进行隧道保活。
  16. 如权利要求15所述的方法,其特征在于,所述CP设备根据重置后的所述目标隧道的隧道保活序列号,指示所述远端网络设备对所述目标隧道的隧道保活序列号进行重置,包括:
    所述CP设备通过所述UP设备向所述远端网络设备发送第二控制请求报文,所述第二控制请求报文携带所述目标隧道的标识、所述重置后的所述目标隧道的隧道保活序列号,以及序列号重置指示信息;
    所述CP设备通过所述UP设备接收所述远端网络设备发送的第二控制应答报文,所述第二控制应答报文用于指示所述远端网络设备对所述目标隧道的隧道保活序列号重置成功。
  17. 如权利要求15或16所述的方法,其特征在于,所述CP设备重置本地存储的目标隧道的隧道保活序列号之前,还包括:
    所述CP设备创建与所述远端网络设备之间的数据对账隧道;
    所述CP设备通过所述数据对账隧道,通过UP设备向所述远端网络设备发送第二数据对账报文,所述第二数据对账报文携带所述CP设备上存储的所述UP设备与所述远端网络设备之间建立的隧道的标识;
    所述CP设备通过所述UP设备接收所述远端网络设备发送的第二对账应答报文,所述第二对账应答报文携带所述远端网络设备上存储的与所述UP设备之间建立的隧道的标识;
    所述CP设备将所述第二数据对账报文携带的隧道的标识与所述第二对账应答报文携带的隧道的标识的交集,确定为所述一条或多条隧道的标识。
  18. 如权利要求17所述的方法,其特征在于,所述CP设备创建与所述远端网络设备之间的数据对账隧道之后,还包括:
    所述CP设备通过所述UP设备向所述远端网络设备发送第二会话数据对账报文,所述第二会话数据对账报文携带一个或多个第一参考会话的标识,所述一个或多个第一参考会话为所述CP设备上存储的所述目标隧道上承载的会话;
    所述CP设备通过所述UP设备接收所述远端网络设备发送的第二会话对账应答报文,所述第二会话对账应答报文携带一个或多个第三参考会话的标识,所述一个或多个第三参考会话为所述远端网络设备上存储的所述目标隧道上承载的会话;
    所述CP设备将所述一个或多个第一参考会话的标识与所述一个或多个第三参考会话的标识的交集,确定为所述目标隧道上承载的会话的标识。
  19. 如权利要求15-18任一所述的方法,其特征在于,所述远端网络设备对所述目标隧道的隧道保活序列号重置成功之后,还包括:
    所述CP设备向所述UP设备发送第二隧道信息,所述第二隧道信息包括第一时刻所述 CP设备上存储的所述UP设备与所述远端网络设备之间建立的一条或多条隧道的信息,所述第一时刻是指所述UP设备与所述CP设备之间的通信恢复之后,所述CP设备通过UP设备与所述远端网络设备之间完成隧道故障恢复或会话故障恢复的时刻。
  20. 如权利要求13-19任一所述的方法,其特征在于,所述CP设备通过控制报文重定向接口和状态控制接口与所述UP设备进行通信;
    所述CP设备检测到自身与所述UP设备之间的通信发生故障,包括:
    所述CP设备监控所述控制报文重定向接口和所述状态控制接口的状态;
    如果所述CP设备监控到所述控制报文重定向接口和/或所述状态控制接口的状态异常,则所述CP设备确定检测到自身与所述UP设备之间的通信发生故障。
  21. 如权利要求13-20任一所述的方法,其特征在于,所述第一隧道信息携带在包转发控制协议PFCP更新请求报文中,所述一条或多条隧道为二层隧道协议L2TP隧道,所述一条或多条隧道中每条隧道的信息包括隧道描述信息;
    如果所述L2TP隧道是根据第四版互联网协议IPv4创建的,则所述隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv4地址和隧道远端IPv4地址;
    如果所述L2TP隧道是根据第六版互联网协议IPv6创建的,则所述隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv6地址和隧道远端IPv6地址。
  22. 如权利要求19所述的方法,其特征在于,所述第二隧道信息携带在PFCP更新请求报文中。
  23. 如权利要求13-22任一所述的方法,其特征在于,所述CP设备停止隧道保活之前,还包括:
    所述CP设备向所述UP设备发送第一会话信息,所述第一会话信息包括所述一条或多条隧道上承载的会话的信息。
  24. 如权利要求23所述的方法,其特征在于,所述第一会话信息携带在PFCP更新请求报文中,所述一条或多条隧道中每条隧道上承载的会话的信息包括隧道本地标识、会话本地标识和会话远端标识。
  25. 如权利要求13-24任一所述的方法,其特征在于,所述CP设备向所述UP设备发送第一隧道信息,包括:
    所述CP设备每创建一条隧道,向所述UP设备发送创建的一条隧道的信息,所述一条或多条隧道包括所述创建的一条隧道;或者,
    所述CP设备周期性地向所述UP设备发送自身存储的隧道的信息。
  26. 一种网络设备,其特征在于,所述网络设备应用于网络系统,所述网络系统包括控制面CP设备和用户面UP设备,所述CP设备和所述UP设备用于与远端网络设备进行交互来 保证终端接入网络,所述网络设备为所述UP设备,所述网络设备包括:
    第一接收模块,用于接收所述CP设备发送的第一隧道信息,所述第一隧道信息包括所述UP设备与所述远端网络设备之间建立的一条或多条隧道的信息;
    隧道保活模块,用于如果检测到所述UP设备与所述CP设备之间的通信发生故障,则根据所述第一隧道信息,对所述一条或多条隧道进行隧道保活。
  27. 如权利要求26所述的网络设备,其特征在于,所述第一隧道信息包括所述一条或多条隧道的标识;
    所述隧道保活模块包括:
    监听单元,用于监听所述远端网络设备发送的第一隧道保活报文,所述第一隧道保活报文携带目标隧道的标识和隧道保活序列号;
    第一发送单元,用于根据所述目标隧道的标识和隧道保活序列号,以及所述一条或多条隧道的标识,向所述远端网络设备发送第二隧道保活报文。
  28. 如权利要求26所述的网络设备,其特征在于,所述第一隧道信息包括所述一条或多条隧道的标识;
    所述隧道保活模块包括:
    重置单元,用于重置目标隧道的隧道保活序列号,所述目标隧道为所述一条或多条隧道中的一条;
    指示单元,用于根据重置后的所述目标隧道的隧道保活序列号,指示所述远端网络设备对所述目标隧道的隧道保活序列号进行重置;
    隧道保活单元,用于在所述远端网络设备对所述目标隧道的隧道保活序列号重置成功后,按照重置后的所述目标隧道的隧道保活序列号以及所述目标隧道的标识,对所述目标隧道进行隧道保活。
  29. 如权利要求28所述的网络设备,其特征在于,所述指示单元具体用于:
    向所述远端网络设备发送第一控制请求报文,所述第一控制请求报文携带所述目标隧道的标识、所述重置后的所述目标隧道的隧道保活序列号,以及序列号重置指示信息;
    接收所述远端网络设备发送的第一控制应答报文,所述第一控制应答报文用于指示所述远端网络设备对所述目标隧道的隧道保活序列号重置成功。
  30. 如权利要求28或29所述的网络设备,其特征在于,所述隧道保活模块还包括:
    创建单元,用于创建与所述远端网络设备之间的数据对账隧道;
    第二发送单元,用于通过所述数据对账隧道,向所述远端网络设备发送第一隧道数据对账报文,所述第一隧道数据对账报文携带所述UP设备上存储的与所述远端网络设备之间建立的隧道的标识;
    第一接收单元,用于接收所述远端网络设备发送的第一隧道对账应答报文,所述第一隧道对账应答报文携带所述远端网络设备上存储的与所述UP设备之间建立的隧道的标识;
    第一确定单元,用于将所述第一隧道数据对账报文携带的隧道的标识与所述第一隧道对 账应答报文携带的隧道的标识的交集,确定为所述一条或多条隧道的标识。
  31. 如权利要求30所述的网络设备,其特征在于,所述网络设备还包括:
    第二接收模块,用于接收所述CP设备发送的第一会话信息,所述第一会话信息包括所述一条或多条隧道上承载的会话的信息;
    所述隧道保活模块还包括:
    第三发送单元,用于向所述远端网络设备发送第一会话数据对账报文,所述第一会话数据对账报文携带一个或多个第一参考会话的标识,所述一个或多个第一参考会话为所述UP设备上存储的所述目标隧道上承载的会话;
    第二接收单元,用于接收所述远端网络设备发送的第一会话对账应答报文,所述第一会话对账应答报文携带一个或多个第二参考会话的标识,所述一个或多个第二参考会话为所述远端网络设备上存储的所述目标隧道上承载的会话;
    第二确定单元,用于将所述一个或多个第一参考会话的标识与所述一个或多个第二参考会话的标识的交集,确定为所述目标隧道上承载的会话的标识。
  32. 如权利要求26-31任一所述的网络设备,其特征在于,所述网络设备还包括:
    处理模块,用于如果检测到所述UP设备与所述CP设备之间的通信恢复,则停止对所述一条或多条隧道进行隧道保活。
  33. 如权利要求32所述的网络设备,其特征在于,所述网络设备还包括:
    第三接收模块,用于接收所述CP设备发送的第二隧道信息,所述第二隧道信息包括第一时刻所述CP设备上存储的所述UP设备与所述远端网络设备之间建立的一条或多条隧道的信息,所述第一时刻是指所述UP设备与所述CP设备之间的通信恢复之后,所述CP设备通过所述UP设备与所述远端网络设备之间完成隧道故障恢复或会话故障恢复的时刻;
    更新模块,用于根据所述第二隧道信息,更新本地存储的隧道信息。
  34. 如权利要求26-33任一所述的网络设备,其特征在于,所述UP设备通过控制报文重定向接口和状态控制接口与所述CP设备进行通信;
    所述隧道保活模块包括:
    监控单元,用于监控所述控制报文重定向接口和所述状态控制接口的状态;
    第三确定单元,用于如果监控到所述控制报文重定向接口和/或所述状态控制接口的状态异常,则确定检测到所述UP设备与所述CP设备之间的通信发生故障。
  35. 如权利要求26-34任一所述的网络设备,其特征在于,所述第一隧道信息携带在包转发控制协议PFCP更新请求报文中,所述一条或多条隧道为二层隧道协议L2TP隧道,所述一条或多条隧道中每条隧道的信息包括隧道描述信息;
    如果所述L2TP隧道是根据第四版互联网协议IPv4创建的,则所述隧道描述信息包括隧道本地标识、隧道远端标识、隧道本地IPv4地址和隧道远端IPv4地址;
    如果所述L2TP隧道是根据第六版互联网协议IPv6创建的,则所述隧道描述信息包括隧 道本地标识、隧道远端标识、隧道本地IPv6地址和隧道远端IPv6地址。
  36. 如权利要求33所述的网络设备,其特征在于,所述第二隧道信息携带在PFCP更新请求报文中。
  37. 如权利要求31所述的网络设备,其特征在于,所述第一会话信息携带在PFCP更新请求报文中,所述一条或多条隧道中每条隧道上承载的会话的信息包括隧道本地标识、会话本地标识和会话远端标识。
  38. 一种网络设备,其特征在于,所述网络设备应用于网络系统,所述网络系统包括控制面CP设备和用户面UP设备,所述CP设备和所述UP设备用于与远端网络设备进行交互来保证终端接入网络,所述网络设备为所述CP设备,所述网络设备包括:
    第一发送模块,用于向所述UP设备发送第一隧道信息,所述第一隧道信息包括所述UP设备与所述远端网络设备之间建立的一条或多条隧道的信息;
    处理模块,用于如果检测到所述CP设备与所述UP设备之间的通信发生故障,则停止对所述一条或多条隧道进行隧道保活;
    其中,所述第一隧道信息用于所述UP设备在检测到自身与所述CP设备之间的通信发生故障时,根据所述第一隧道信息对所述UP设备与所述远端网络设备之间建立的一条或多条隧道进行隧道保活。
  39. 如权利要求38所述的网络设备,其特征在于,所述网络设备还包括:
    隧道保活模块,用于如果检测到所述CP设备与所述UP设备之间的通信恢复,则重新对所述一条或多条隧道进行隧道保活。
  40. 如权利要求39所述的网络设备,其特征在于,所述隧道保活模块包括:
    重置单元,用于重置本地存储的目标隧道的隧道保活序列号,所述目标隧道为所述一条或多条隧道中的一条;
    指示单元,用于根据重置后的所述目标隧道的隧道保活序列号,指示所述远端网络设备对所述目标隧道的隧道保活序列号进行重置;
    隧道保活单元,用于在所述远端网络设备对所述目标隧道的隧道保活序列号重置成功后,按照重置后的所述目标隧道的隧道保活序列号以及所述目标隧道的标识,通过所述UP设备对所述目标隧道进行隧道保活。
  41. 如权利要求40所述的网络设备,其特征在于,所述指示具体用于:
    通过所述UP设备向所述远端网络设备发送第二控制请求报文,所述第二控制请求报文携带所述目标隧道的标识、所述重置后的所述目标隧道的隧道保活序列号,以及序列号重置指示信息;
    通过所述UP设备接收所述远端网络设备发送的第二控制应答报文,所述第二控制应答报文用于指示所述远端网络设备对所述目标隧道的隧道保活序列号重置成功。
  42. 如权利要求40或41所述的网络设备,其特征在于,所述隧道保活模块还包括:
    创建单元,用于创建与所述远端网络设备之间的数据对账隧道;
    第一发送单元,用于通过所述数据对账隧道,通过UP设备向所述远端网络设备发送第二数据对账报文,所述第二数据对账报文携带所述CP设备上存储的所述UP设备与所述远端网络设备之间建立的隧道的标识;
    第一接收单元,用于通过所述UP设备接收所述远端网络设备发送的第二对账应答报文,所述第二对账应答报文携带所述远端网络设备上存储的与所述UP设备之间建立的隧道的标识;
    第一确定单元,用于将所述第二数据对账报文携带的隧道的标识与所述第二对账应答报文携带的隧道的标识的交集,确定为所述一条或多条隧道的标识。
  43. 如权利要求42所述的网络设备,其特征在于,所述隧道保活模块还包括:
    第二发送单元,用于通过所述UP设备向所述远端网络设备发送第二会话数据对账报文,所述第二会话数据对账报文携带一个或多个第一参考会话的标识,所述一个或多个第一参考会话为所述CP设备上存储的所述目标隧道上承载的会话;
    第二接收单元,用于通过所述UP设备接收所述远端网络设备发送的第二会话对账应答报文,所述第二会话对账应答报文携带一个或多个第三参考会话的标识,所述一个或多个第三参考会话为所述远端网络设备上存储的所述目标隧道上承载的会话;
    第二确定单元,用于将所述一个或多个第一参考会话的标识与所述一个或多个第三参考会话的标识的交集,确定为所述目标隧道上承载的会话的标识。
  44. 如权利要求40-43任一所述的网络设备,其特征在于,所述隧道保活模块还包括:
    第三发送单元,用于向所述UP设备发送第二隧道信息,所述第二隧道信息包括第一时刻所述CP设备上存储的所述UP设备与所述远端网络设备之间建立的一条或多条隧道的信息,所述第一时刻是指所述UP设备与所述CP设备之间的通信恢复之后,所述CP设备通过UP设备与所述远端网络设备之间完成隧道故障恢复或会话故障恢复的时刻。
  45. 如权利要求38-44任一所述的网络设备,其特征在于,所述CP设备通过控制报文重定向接口和状态控制接口与所述UP设备进行通信;
    所述处理模块包括:
    监控单元,用于监控所述控制报文重定向接口和所述状态控制接口的状态;
    第三确定单元,用于如果监控到所述控制报文重定向接口和/或所述状态控制接口的状态异常,则确定检测到所述CP设备与所述UP设备之间的通信发生故障。
  46. 如权利要求38-45任一所述的网络设备,其特征在于,所述网络设备还包括:
    第四发送模块,用于向所述UP设备发送第一会话信息,所述第一会话信息包括所述一条或多条隧道上承载的会话的信息。
  47. 如权利要求38-46任一所述的网络设备,其特征在于,所述第一发送模块包括:
    第五发送单元,用于每创建一条隧道,向所述UP设备发送创建的一条隧道的信息,所述一条或多条隧道包括所述创建的一条隧道;或者,
    第六发送单元,用于周期性地向所述UP设备发送自身存储的隧道的信息。
  48. 一种网络设备,其特征在于,所述网络设备应用于网络系统,所述网络系统包括控制面CP设备和用户面UP设备,所述CP设备和所述UP设备用于与远端网络设备进行交互来保证终端接入网络,所述网络设备为所述UP设备,所述网络设备包括存储器和处理器;
    所述存储器,用于存储权利要求1-12任一所述的方法所涉及的程序代码;
    所述处理器,用于执行所述程序代码实现权利要求1-12任一所述的方法。
  49. 一种网络设备,其特征在于,所述网络设备应用于网络系统,所述网络系统包括控制面CP设备和用户面UP设备,所述CP设备和所述UP设备用于与远端网络设备进行交互来保证终端接入网络,所述网络设备为所述CP设备,所述网络设备包括存储器和处理器;
    所述存储器,用于存储权利要求13-25任一所述的方法所涉及的程序代码;
    所述处理器,用于执行所述程序代码实现权利要求13-25任一所述的方法。
  50. 一种网络系统,其特征在于,所述系统包括控制面CP设备和用户面UP设备,以及远端网络设备,所述CP设备和所述UP设备用于与所述远端网络设备进行交互来保证终端接入网络;
    所述UP设备,用于实现权利要求1-12任一所述的方法;
    所述CP设备,用于实现权利要求13-25任一所述的方法。
  51. 一种计算机可读存储介质,其特征在于,所述存储介质内存储有计算机程序,所述计算机程序被处理器执行时实现权利要求1-12任一所述的方法的步骤,或者实现权利要求13-25任一所述的方法的步骤。
PCT/CN2021/114141 2020-08-31 2021-08-23 隧道保活方法、网络设备、系统及存储介质 WO2022042499A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21860334.8A EP4192085A4 (en) 2020-08-31 2021-08-23 TUNNEL KEEPALIVE METHOD, NETWORK DEVICE, SYSTEM AND STORAGE MEDIUM
US18/175,274 US20230208679A1 (en) 2020-08-31 2023-02-27 Tunnel Keepalive Method, Network Device, System, and Storage Medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010899677.9 2020-08-31
CN202010899677.9A CN114125910A (zh) 2020-08-31 2020-08-31 隧道保活方法、网络设备、系统及存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/175,274 Continuation US20230208679A1 (en) 2020-08-31 2023-02-27 Tunnel Keepalive Method, Network Device, System, and Storage Medium

Publications (1)

Publication Number Publication Date
WO2022042499A1 true WO2022042499A1 (zh) 2022-03-03

Family

ID=80352654

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/114141 WO2022042499A1 (zh) 2020-08-31 2021-08-23 隧道保活方法、网络设备、系统及存储介质

Country Status (4)

Country Link
US (1) US20230208679A1 (zh)
EP (1) EP4192085A4 (zh)
CN (1) CN114125910A (zh)
WO (1) WO2022042499A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230239359A1 (en) * 2022-01-26 2023-07-27 Juniper Networks, Inc. Integrated broadband network gateway (bng) device for providing a bng control plane for one or more distributed bng user plane devices
CN117675427A (zh) * 2022-09-07 2024-03-08 华为技术有限公司 客户端设备的接入方法、装置及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006058106A2 (en) * 2004-11-24 2006-06-01 Starent Networks Corporation Redundant l2tp end points
CN108512703A (zh) * 2018-03-28 2018-09-07 新华三技术有限公司 Bras转控分离的备份方法、装置、设备及机器可读存储介质
CN110113825A (zh) * 2012-06-30 2019-08-09 华为技术有限公司 一种控制和转发解耦架构下的转发面隧道资源的管理方法
CN110636535A (zh) * 2018-06-25 2019-12-31 华为技术有限公司 一种数据传输方法及装置
CN111431787A (zh) * 2019-01-10 2020-07-17 中国移动通信有限公司研究院 一种隧道建立方法、装置及计算机可读存储介质

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108075991B (zh) * 2016-11-18 2020-09-08 新华三技术有限公司 报文转发方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006058106A2 (en) * 2004-11-24 2006-06-01 Starent Networks Corporation Redundant l2tp end points
CN110113825A (zh) * 2012-06-30 2019-08-09 华为技术有限公司 一种控制和转发解耦架构下的转发面隧道资源的管理方法
CN108512703A (zh) * 2018-03-28 2018-09-07 新华三技术有限公司 Bras转控分离的备份方法、装置、设备及机器可读存储介质
CN110636535A (zh) * 2018-06-25 2019-12-31 华为技术有限公司 一种数据传输方法及装置
CN111431787A (zh) * 2019-01-10 2020-07-17 中国移动通信有限公司研究院 一种隧道建立方法、装置及计算机可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4192085A4

Also Published As

Publication number Publication date
US20230208679A1 (en) 2023-06-29
EP4192085A4 (en) 2024-02-21
CN114125910A (zh) 2022-03-01
EP4192085A1 (en) 2023-06-07

Similar Documents

Publication Publication Date Title
US11729615B2 (en) Internet of things communication method, apparatus, and system
US7995483B1 (en) Simultaneously testing connectivity to multiple remote maintenance endpoints of the same maintenance association
KR101099382B1 (ko) 패킷 네트워크에서의 종단점 어드레스 변경
WO2022042499A1 (zh) 隧道保活方法、网络设备、系统及存储介质
WO2016155300A1 (zh) 无线终端设备的远程控制系统及远程控制方法
US11419171B2 (en) Method for establishing subflow of multipath connection, apparatus, and system
US20110173344A1 (en) System and method of reducing intranet traffic on bottleneck links in a telecommunications network
US10581669B2 (en) Restoring control-plane connectivity with a network management entity
EP3806404A1 (en) Communication method, device and system for avoiding loop
CN116711445A (zh) 用于提供被配置为经由网络暴露功能支持不频繁的数据通信的统一接口的方法、系统和计算机可读介质
JP7448597B2 (ja) メッセージ生成方法および装置ならびにメッセージ処理方法および装置
TWI740210B (zh) 終端設備管理方法及伺服器
US11552926B2 (en) Method related to sending management IP address and system
CN112995027B (zh) 路由发布方法及vtep节点
CN112887312B (zh) 一种慢协议报文处理方法及相关装置
US20220217093A1 (en) Sequence Number Synchronization Method and Apparatus
WO2023284231A1 (zh) 报文处理方法和报文处理系统
CN113472912B (zh) 一种arp缓存表项的更新方法、vtep、vm及装置
US11363103B2 (en) Dynamic user plane function (UPF) selection based on supported protocol type
CN114765589A (zh) 网络测试方法、装置及存储介质
WO2016206299A1 (zh) 一种会话保活方法及装置
US20230353421A1 (en) Remote connection resumption with previous secure tunnel ip address
WO2018018897A1 (zh) 设备通信方法、装置及系统
CN112153087B (zh) 一种第三方网络终端跨Net通讯方法
EP4391495A1 (en) Message transceiving method, information acquisition and transceiving method, and related device

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: 21860334

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021860334

Country of ref document: EP

Effective date: 20230303

NENP Non-entry into the national phase

Ref country code: DE