WO2017101085A1 - 确定通用路由封装gre隧道标识的方法、设备和系统 - Google Patents

确定通用路由封装gre隧道标识的方法、设备和系统 Download PDF

Info

Publication number
WO2017101085A1
WO2017101085A1 PCT/CN2015/097757 CN2015097757W WO2017101085A1 WO 2017101085 A1 WO2017101085 A1 WO 2017101085A1 CN 2015097757 W CN2015097757 W CN 2015097757W WO 2017101085 A1 WO2017101085 A1 WO 2017101085A1
Authority
WO
WIPO (PCT)
Prior art keywords
gre
tunnel
gre tunnel
hag
hcpe
Prior art date
Application number
PCT/CN2015/097757
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 CN202010631680.2A priority Critical patent/CN111917650B/zh
Priority to EP15910556.8A priority patent/EP3382952B1/en
Priority to CN201580062767.XA priority patent/CN107113230B/zh
Priority to PCT/CN2015/097757 priority patent/WO2017101085A1/zh
Priority to EP19219742.4A priority patent/EP3691204B1/en
Priority to ES15910556T priority patent/ES2788720T3/es
Publication of WO2017101085A1 publication Critical patent/WO2017101085A1/zh
Priority to US16/010,512 priority patent/US10873478B2/en
Priority to US17/118,507 priority patent/US11817970B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2212/00—Encapsulation of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H04L45/245—Link aggregation, e.g. trunking

Definitions

  • Embodiments of the present invention relate to the field of communications, and, more particularly, to a method, device, and system for determining a generic route encapsulation GRE tunnel identity.
  • Hybrid Access is an access technology that binds heterogeneous networks. Users can access two or more access networks at the same time to access the network side, for example, in home broadband. In the network, users can access a fixed access network (for example, Digital Subscriber Line (DSL)) and a mobile access network (for example, Long Time Evolution (LTE). )), able to provide users with faster service provisioning services, more reliable WAN connectivity, and greater bandwidth.
  • DSL Digital Subscriber Line
  • LTE Long Time Evolution
  • the HA technology is implemented by using Generic Routing Encapsulation (GRE) tunnel binding.
  • GRE Generic Routing Encapsulation
  • the hybrid terminal access device Hybrid Customer Premises Equipment, referred to as "HCPE"
  • HOG Hybrid Access Gateway
  • the first GRE tunnel based on the DSL access network and the second GRE tunnel based on the LTE access network are created.
  • the packets of the same service on the HCPE can pass through at the same time.
  • the first GRE tunnel and the second GRE tunnel are transmitted to the HAG.
  • the bandwidth of the DSL access network is 1G
  • the bandwidth of the LTE access network is 1G.
  • the user can provide 2G access network bandwidth.
  • the present invention provides a method, a device, and a system for determining a GRE tunnel identity, which can flexibly distinguish which GRE tunnel a received service message is from after the binding of at least two GRE tunnels.
  • the first aspect provides a method for determining a generic route encapsulation GRE tunnel identifier, where the method is applied to a scenario where there are at least two GRE tunnels between a hybrid access gateway HAG and a hybrid access terminal device HCPE, and the at least two GRE tunnel binding, the method includes:
  • the HAG receives the service packet sent by the HCPE through the first GRE tunnel, where the service packet includes the source IP address of the first GRE tunnel that carries the service packet, where the first GRE tunnel is the at least two a GRE tunnel in the GRE tunnel;
  • the HAG searches for a correspondence relationship table according to the source IP address of the first GRE tunnel that carries the service packet, and determines a tunnel identifier of the first GRE tunnel that carries the service packet, where the correspondence relationship table includes the first GRE tunnel.
  • the tunnel identifier of the tunnel is used to uniquely indicate the first GRE tunnel.
  • the first GRE tunnel indicates any one of the at least two GRE tunnels.
  • the above steps for the first GRE tunnel are performed on each of the at least two GRE tunnels.
  • the source IP address of the first GRE tunnel refers to the IP address of the tunnel port of the first GRE tunnel on the HCPE. Specifically, as shown in FIG. 1 , the source IP address of the first GRE tunnel refers to the DSL of the HCPE. IP address of the interface. The source IP address of the second GRE tunnel refers to the IP address of the LTE interface of the HCPE.
  • the tunnel identifier of the first GRE tunnel is used to uniquely indicate the first GRE tunnel.
  • the tunnel identifier is a tunnel number of the first GRE tunnel, and it is assumed that at least two GRE tunnels include five GRE tunnels, where The tunnel identifiers of the five GRE tunnels are 1, 2, 3, 4, and 5, respectively.
  • the tunnel identifier of the first GRE tunnel may also adopt other presentation forms that can uniquely indicate the first GRE tunnel, such as a letter or a Roman numeral, which is not limited by the present invention.
  • the HAG can flexibly and efficiently distinguish which service packet is received according to the correspondence between the source IP address of the GRE tunnel and the tunnel identifier.
  • the GRE tunnel can meet the requirements of the current operator for the operation, management, and maintenance (OAM) of the GRE tunnel.
  • the HAG may obtain the correspondence between the source IP address of the first GRE tunnel and the tunnel identifier of the first GRE tunnel from the HCPE, or obtain the corresponding relationship from the upper layer device (for example, the network management device or the controller).
  • the upper layer device for example, the network management device or the controller.
  • the method before the HAG receives the service packet sent by the HCPE by using the first GRE tunnel, the method further includes:
  • the HAG Receiving, by the HAG, a GRE control message sent by the HCPE, where the GRE control message includes information indicating a correspondence between a source IP address of the first GRE tunnel and a tunnel identifier of the first GRE tunnel;
  • the HAG obtains the correspondence according to the GRE control packet.
  • the HAG After the HAG obtains the correspondence between the source IP address of the first GRE tunnel and the tunnel identifier of the first GRE tunnel, the HAG stores the corresponding relationship in the local correspondence table. It should also be understood that the correspondence table includes a correspondence between a source IP address and a tunnel identifier of each GRE tunnel in the at least two GRE tunnels.
  • the HCPE can notify the HAG of the correspondence between the source IP address of the GRE tunnel and the tunnel identifier based on the existing GRE control message, so that the HAG can flexibly distinguish and receive a service packet according to the corresponding relationship.
  • GRE tunnel there is no additional signaling overhead compared to the existing process.
  • the HCPE can notify the HAG of the correspondence between the source IP address of the at least two GRE tunnels and the tunnel identifier, so that the HAG can flexibly distinguish and receive a service packet according to the corresponding relationship.
  • the HAG receives the GRE control packet sent by the HCPE, including:
  • the HAG receives the GRE Tunnel Setup Request message sent by the HCPE, and the attribute field of the GRE Tunnel Setup Request message includes information indicating the correspondence.
  • the HAG receives the GRE control packet sent by the HCPE, including:
  • the HAG After the first GRE tunnel is established, the HAG receives the first GRE Tunnel Notify message sent by the HCPE, and the attribute field of the first GRE Tunnel Notify message includes information for indicating the correspondence.
  • the method further includes:
  • the HAG sends a GRE Tunnel to the HCPE.
  • a Setup Accept message where the GRE Tunnel Setup Accept message includes request information for requesting the correspondence;
  • the HAG receives the first GRE Tunnel Notify message sent by the HCPE, including:
  • the HAG receives the first GRE Tunnel Notify message sent by the HCPE according to the request information.
  • the HAG receives the first GRE Tunnel Notify message sent by the HCPE, including:
  • the HAG receives the first GRE Tunnel Notify message sent by the HCPE according to the second GRE Tunnel Notify message.
  • the method provided by the present invention can flexibly and efficiently distinguish which GRE tunnel a received service packet is from in a GRE tunnel binding scenario, thereby satisfying the current OAM requirement of the operator for the GRE tunnel. .
  • the second aspect provides a method for determining a generic route encapsulation GRE tunnel identifier, where the method is applied to a scenario where there are at least two GRE tunnels between a hybrid access gateway HAG and a hybrid access terminal device HCPE, and the at least two GREs Tunnel binding, the method includes:
  • the HCPE sends a service packet to the HAG through the first GRE tunnel, where the service packet includes a source IP address of the first GRE tunnel that carries the service packet, so that the HAG is configured according to the service carrying the service packet.
  • the source IP address of the first GRE tunnel is searched for the corresponding relationship table, and the tunnel identifier of the first GRE tunnel that carries the service packet is determined, where the correspondence relationship table includes the source IP address of the first GRE tunnel and the first GRE tunnel.
  • a mapping between the tunnel identifiers, where the source IP address of the first GRE tunnel is an IP address of the tunnel port of the first GRE tunnel, and the tunnel identifier of the first GRE tunnel is used to uniquely indicate the A GRE tunnel.
  • the HAG can flexibly and efficiently distinguish which service packet is received according to the correspondence between the source IP address of the GRE tunnel and the tunnel identifier.
  • the GRE tunnel can meet the current OAM requirements of the GRE tunnel.
  • the method further includes:
  • the HCPE sends a GRE control message to the HAG, where the GRE control message includes information indicating a correspondence between a source IP address of the first GRE tunnel and a tunnel identifier of the first GRE tunnel.
  • the HCPE can notify the HAG of the correspondence between the source IP address of the GRE tunnel and the tunnel identifier based on the existing GRE control message, so that the HAG can flexibly distinguish and receive a service packet according to the corresponding relationship.
  • GRE tunnel there is no additional signaling overhead compared to the existing process.
  • the HCPE sends a GRE control message to the HAG, including:
  • the HCPE sends a GRE Tunnel Setup Request message to the HAG, and the attribute field of the GRE Tunnel Setup Request message includes information indicating the correspondence.
  • the HCPE sends a GRE control message to the HAG, including:
  • the HCPE After the first GRE tunnel is established, the HCPE sends a first GRE Tunnel Notify message to the HAG, where the attribute field of the first GRE Tunnel Notify message includes information indicating the correspondence.
  • the method further includes:
  • the HCPE receives the GRE Tunnel Setup Accept message sent by the HAG, where the GRE Tunnel Setup Accept message includes request information for requesting the corresponding relationship;
  • the HCPE sends the first GRE Tunnel Notify message to the HAG, including:
  • the HCPE sends the first GRE Tunnel Notify message to the HAG according to the request information.
  • the HCPE sends the first GRE Tunnel Notify message to the HAG, including:
  • the HCPE sends the first to the HAG according to the second GRE Tunnel Notify message.
  • GRE Tunnel Notify message The HCPE sends the first to the HAG according to the second GRE Tunnel Notify message.
  • the HAG can flexibly and efficiently distinguish which service packet is received according to the correspondence between the source IP address of the GRE tunnel and the tunnel identifier.
  • the GRE tunnel can meet the current OAM requirements of the GRE tunnel.
  • a third aspect provides a network device for performing the method of a first aspect or a possible implementation of any of the aspects of the first aspect.
  • the network device may comprise means for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • the network device corresponds to the hybrid access gateway HAG in the method of the first aspect.
  • a fourth aspect provides a network device for performing the method of a possible implementation of the second aspect or the second aspect.
  • the network device may comprise means for performing the method of any of the possible implementations of the second aspect or the second aspect.
  • the network device corresponds to the hybrid access terminal device HCPE in the method of the second aspect.
  • a fifth aspect provides a system for determining a GRE tunnel identity, the system comprising the network device provided by the third aspect and the network device provided by the fourth aspect.
  • the system includes the HAG and HCPE in the method of determining the GRE tunnel identity provided by the first aspect or the second aspect.
  • a sixth aspect provides a network device including a memory and a processor for storing instructions for executing instructions stored by the memory, and performing execution of the instructions stored in the memory such that the processing The method of the first aspect or the possible implementation of any of the aspects of the first aspect is performed.
  • a seventh aspect provides a network device including a memory and a processor for storing instructions for executing instructions stored by the memory, and performing execution of the instructions stored in the memory such that the processing The method of the second aspect or a possible implementation of any of the aspects of the second aspect is performed.
  • the tunnel identifier of the first GRE tunnel mentioned in the present invention may directly be the access network where the first GRE tunnel is located.
  • Type also known as tunnel type
  • the access network types of the different GRE tunnels in the at least two GRE tunnels are different, and the tunnel identifier of the first GRE tunnel indicates the type of the access network where the first GRE tunnel is located.
  • the access network type in which the GRE tunnel is located includes a fixed access network and a mobile access network, where a fixed access network, such as a Digital Subscriber Line (DSL) access network, and the mobile access network, for example, 3G or LTE network.
  • a fixed access network such as a Digital Subscriber Line (DSL) access network
  • DSL Digital Subscriber Line
  • the HAG obtains the corresponding relationship between the source IP address and the access network type of the at least two GRE tunnels, and when the service packet is received, the HAG can flexibly determine the bearer according to the correspondence.
  • the access network type of the GRE tunnel in the text so that in the GRE tunnel binding scenario, it is possible to flexibly and efficiently distinguish which GRE tunnel the received service packet is from, which can meet the urgent needs of the current operator. demand.
  • the Hybrid Customer Premises Equipment (HCPE) and the Hybrid Access Gateway (HAG) are devices at both ends of the hybrid access tunnel, where the HCPE is the access device on the client side.
  • the HCPE includes multiple access network interfaces, and establishes GRE tunnels of different access networks with the HAG through different access network interfaces.
  • the HAG is an access device on the provider network side.
  • the binding of the at least two GRE tunnels refers to that the packets of the same service can be simultaneously transmitted on the at least two GRE tunnels.
  • the first GRE tunnel based on the access network DSL established between the HCPE and the HAG is bound to the second GRE tunnel based on the LTE, and the HCPE can use the two GRE tunnels to transmit the same service to the HAG. Text.
  • the format of the GRE control packet is as shown in FIG. 4(a), and the GRE control packet includes an attribute type (Attr Type) field, and the value is an attribute type 55 (Attr Type 55), which is used for Indicates the learning of the correspondence between the source IP address of the GRE tunnel and the tunnel identifier.
  • the Attribute Value field of the GRE control message includes a tunnel ID (Tunnel ID) field, a Tunnel Source IP Address field, and a Delivery Protocol (Delivery Protl) field. That is, the GRE control message includes information indicating a correspondence between a source IP address of the GRE tunnel and a tunnel identifier of the GRE tunnel.
  • the message type (MsgType) field of the GRE control message is used to indicate the message type of the GRE control message, and the MsgType field is assigned a different value to indicate different types of GRE control messages, as shown in Table 1, for example, when MsgType When the field is set to 1, it indicates the GRE control report.
  • the GRE Tunnel Setup Request message is sent to the GRE Tunnel Setup Accept message.
  • the MsgType field is set to 2
  • the GRE control message is GRE Tunnel Setup Accept message.
  • the MsgType field is set to 6
  • the GRE control message is GRE Tunnel Notify. Text.
  • the format of the GRE Tunnel Setup Request message sent by the HCPE to the HAG is as shown in Figure 4(b).
  • the format of the GRE Tunnel Notify message sent by the HCPE to the HAG is as shown in FIG. 4(c).
  • the HAG in a GRE tunnel binding scenario, can flexibly and efficiently distinguish which service packet is received according to the correspondence between the source IP address of the GRE tunnel and the tunnel identifier.
  • the GRE tunnel can meet the current OAM requirements of the GRE tunnel.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a method for determining a GRE tunnel identifier according to an embodiment of the present invention.
  • FIG. 3 is another schematic flowchart of a method for determining a GRE tunnel identifier according to an embodiment of the present invention.
  • 4(a), 4(b) and 4(c) are diagrams showing a GRE control message according to an embodiment of the present invention.
  • FIG. 5 is still another schematic flowchart of a method for determining a GRE tunnel identifier according to an embodiment of the present invention.
  • FIG. 6 is still another schematic flowchart of a method for determining a GRE tunnel identifier according to an embodiment of the present invention.
  • FIG. 7 is still another schematic flowchart of a method for determining a GRE tunnel identifier according to an embodiment of the present invention.
  • FIG. 8 shows still another method for determining a GRE tunnel identifier according to an embodiment of the present invention. Schematic flow chart.
  • FIG. 9 is still another schematic flowchart of a method for determining a GRE tunnel identifier according to an embodiment of the present invention.
  • FIG. 10 shows a schematic block diagram of a network device according to an embodiment of the present invention.
  • FIG. 11 is a schematic block diagram of a system for determining a GRE tunnel identity according to an embodiment of the present invention.
  • FIG. 12 shows a schematic block diagram of a network device according to another embodiment of the present invention.
  • FIG. 13 shows another schematic block diagram of a network device according to another embodiment of the present invention.
  • the hybrid access terminal device HCPE includes a DSL interface and an LTE interface.
  • the HCPE establishes a GRE tunnel (recorded as the first GRE tunnel) of the DSL access network with the hybrid access gateway HAG through the DSL interface, and through the LTE interface.
  • the HAG establishes a GRE tunnel (referred to as a second GRE tunnel) of the LTE access network, and the first GRE tunnel is bonded to the second GRE tunnel to form a hybrid access tunnel.
  • the Generic Routing Encapsulation (GRE) protocol is an encapsulation protocol, which provides a mechanism for encapsulating a protocol packet in another protocol packet, so that the packet can be Transmission in heterogeneous networks.
  • the GRE encapsulates data packets of certain network protocols (such as IP, IPx, Apple Talk, etc.) so that the encapsulated data packets can be transmitted in another network layer protocol.
  • the service packets of the same service on the HCPE can be transmitted to the HAG through the first GRE tunnel and the second GRE tunnel respectively, assuming that the bandwidth of the DSL access network (ie, the first GRE tunnel) is 1 G, and the LTE access network The bandwidth of the second GRE tunnel is 1 G.
  • the two GRE tunnels can provide the user with 2G access network bandwidth.
  • the HCPE sends a service packet to the HAG through the hybrid access tunnel.
  • a GRE When the transmission amount of the tunnel exceeds the bandwidth of the first GRE tunnel, the excess transmission amount is transferred to the second GRE tunnel for transmission. Therefore, the first GRE tunnel and the second GRE tunnel are tied to each GRE tunnel separately.
  • the hybrid access tunnel formed after the determination can increase the bandwidth of the access network for the user and improve the reliability of packet transmission.
  • the first GRE tunnel and the second GRE tunnel are bonded together at the HCPE end and the HAG end, and the HCPE hides the first GRE tunnel from the user and
  • the second GRE tunnel in other words, appears to the user to utilize a separate access network connection tunnel between the HCPE and the HAG to transmit data.
  • the GRE tunnel of the access network from which the specific service packet received from the HCPE is received cannot be distinguished on the HAG.
  • operators have put forward urgent needs for this.
  • the embodiment of the present invention provides a method, a device, and a system for determining a GRE tunnel identity.
  • the HAG can independently and flexibly receive a certain The service packet is from which GRE tunnel in the bound GRE tunnel.
  • FIG. 2 illustrates a method 100 for determining a generic route encapsulation GRE tunnel identity, which is applied to a scenario where there are at least two GRE tunnels between a hybrid access gateway HAG and a hybrid access terminal device HCPE, according to an embodiment of the present invention. And binding the at least two GRE tunnels, the method 100 includes:
  • the HAG receives the service packet sent by the HCPE through the first GRE tunnel, where the service packet includes a source IP address of the first GRE tunnel that carries the service packet, where the first GRE tunnel is the at least one One of the two GRE tunnels;
  • the HAG searches for a correspondence relationship table according to the source IP address of the first GRE tunnel that carries the service packet, and determines a tunnel identifier of the first GRE tunnel that carries the service packet, where the correspondence relationship table includes the first GRE.
  • the tunnel identifier of a GRE tunnel is used to uniquely indicate the first GRE tunnel.
  • the HAG in a GRE tunnel binding scenario, can flexibly and efficiently distinguish a received service packet from the corresponding relationship between the source IP address of the GRE tunnel and the tunnel identifier.
  • Which GRE tunnel can meet the current carrier's GRE The requirements for Operation, Administration, and Maintenance (OAM).
  • the GRE tunnel is determined by the source IP address of the tunnel and the destination IP address of the tunnel.
  • the direction of the GRE tunnel is from the HCPE to the HAG.
  • the source IP address of the GRE tunnel refers to the GRE tunnel on the HCPE. IP address of the tunnel port.
  • the destination IP address refers to the IP address of the tunnel port of the GRE tunnel on the HAG.
  • the source IP address of the first GRE tunnel refers to the IP address of the DSL interface of the HCPE
  • the destination IP address of the first GRE tunnel refers to the tunnel port of the first GRE tunnel on the HAG.
  • the IP address of the second GRE tunnel refers to the IP address of the LTE interface of the HCPE.
  • the destination IP address of the second GRE tunnel refers to the IP address of the tunnel port of the second GRE tunnel on the HAG. It should be understood that the destination IP address of the first GRE tunnel may be different from the destination IP address of the second GRE tunnel, and may be the same.
  • the HCPE has at least two access network interfaces, and the at least two access network interfaces are in one-to-one correspondence with the at least two GRE tunnels.
  • the HAG and the HCPE may establish the at least two GRE tunnels by using the following process:
  • the HCPE sends a GRE Tunnel Setup Request message for requesting the first GRE tunnel to the HAG by using the first interface of the at least two access network interfaces;
  • the HAG sends a GRE Tunnel Setup Accept message to the HCPE in response to the GRE Tunnel Setup Request message, so that the HCPE and the HAG complete the establishment of the first GRE tunnel.
  • the HCPE performs the above steps 1) and 2) in sequence on each of the at least two access network interfaces except the first interface, thereby completing the establishment of at least two GRE tunnels between the HCPE and the HAG.
  • the types of access networks in which the at least two GRE tunnels are located may be different from each other, or may be partially the same, which is not limited in this embodiment of the present invention.
  • the at least two GRE tunnels include a first GRE tunnel based on a DSL access network, a second GRE tunnel based on an LTE access network, and a third GRE tunnel based on a 3G access network.
  • the at least two GRE tunnels include a first GRE tunnel based on a DSL access network, a second GRE tunnel based on an LTE access network, and a third GRE tunnel based on a DSL access network.
  • the binding of the at least two GRE tunnels refers to that the packets of the same service can be simultaneously transmitted on the at least two GRE tunnels.
  • two GRE tunnels based on access network DSL and LTE established between HCPE and HAG are bound together.
  • HCPE can use these two GRE tunnels to simultaneously transmit packets of the same service to the HAG.
  • the tunnel identifier of the GRE tunnel mentioned in the present invention may be directly the type of the access network where the GRE tunnel is located (also Can be called tunnel type).
  • the access network types of the different GRE tunnels in the at least two GRE tunnels are different, and the tunnel identifier of the first GRE tunnel indicates the access network where the first GRE tunnel is located. Types of.
  • the tunnel identifier of the first GRE tunnel is, for example, a DSL
  • the tunnel identifier of the second GRE tunnel is, for example, LTE.
  • the access network type in which the GRE tunnel is located includes a fixed access network and a mobile access network, where a fixed access network, such as a Digital Subscriber Line (DSL) access,
  • a fixed access network such as a Digital Subscriber Line (DSL) access
  • DSL Digital Subscriber Line
  • the network, the mobile access network is, for example, a 3G network, an LTE network, or other mobile access network.
  • the HAG obtains the corresponding relationship between the source IP address and the access network type of the at least two GRE tunnels, and when the service packet is received, the HAG can flexibly determine the bearer according to the corresponding relationship.
  • the access network type of the GRE tunnel of the packet so that in the GRE tunnel binding scenario, the GRE tunnel can be flexibly and efficiently separated from the GRE tunnel, so that the current carrier can be satisfied. Urgent need.
  • the HAG can obtain the correspondence between the source IP address and the tunnel identifier of the at least two GRE tunnels from the upper-layer device (for example, the network management device or the controller), for example, the HCPE real-time upper-layer device reports each of the current HAG-established Corresponding relationship between the source IP address of the GRE tunnel and the tunnel identifier, and then the upper device notifies the HAG of the corresponding relationship; the HAG can also obtain the corresponding relationship directly from the HCPE.
  • the upper-layer device for example, the network management device or the controller
  • the method 100 before the HAG receives the service packet sent by the HCPE through the first GRE tunnel, the method 100 further includes:
  • the HAG receives the GRE control message sent by the HCPE, where the GRE control message includes information indicating a correspondence between a source IP address of the first GRE tunnel and a tunnel identifier of the first GRE tunnel;
  • the HAG obtains the correspondence according to the GRE control packet.
  • the GRE control message is a message used for the establishment, binding, teardown, and OAM management of the GRE tunnel.
  • the Attribute field of the GRE control packet may carry the correspondence between the source IP address of the GRE tunnel and the tunnel identifier.
  • FIG. 4(a) is a schematic diagram showing a format of a message of a GRE control message in the embodiment of the present invention, where the GRE control message includes a message type (MsgType) field, and a reserved bit 1 (Rsvd1) field and an attribute ( Attributes) field.
  • the MsgType field is used to indicate the message type of the GRE control message, and the MsgType field is assigned a different value to indicate the GRE control message of the different message type, as shown in Table 1. For example, when the MsgType field is set to 1, the GRE control is indicated.
  • the message is a GRE Tunnel Setup Request message.
  • the MsgType field is set to 2
  • the GRE control message is GRE Tunnel Setup Accept message.
  • the GRE control message is GRE Tunnel Notify.
  • the reserved bit 1 (Rsvd1) field can be assigned a value of zero.
  • the Attributes field indicates the attributes of the GRE control message. As shown in FIG. 4(a), the Attribute field specifically includes an Attribute Type field, an Attribute Length field, and an attribute value. An Attribute Value field, where the Attribute Type indicates the type of the attribute of the GRE control message.
  • the Attribute Type is assigned to the attribute type 55 (Attri Type 55), indicating that the Attribute type of the GRE control message is the tunnel source. Learning the correspondence between the IP address and the tunnel identifier.
  • This attribute type Attri Type 55 can also be called a Learning Attribute.
  • the Attribute Length field indicates the length of the Attribute Value.
  • the Attribute Value field includes a tunnel ID (Tunnel ID) field, a Transport Protocol (Delivery Prot1) field, and a Tunnel Source IP Address field.
  • the tunnel ID (Tunnel ID) indicates different GRE tunnels by assigning different values.
  • the transport protocol (Delivery Prot1) represents the transport protocol of the GRE tunnel. For example, when the Delivery Prot1 is 0, it indicates that the transport protocol is IPv4; when the Delivery Prot1 is set to 1, it indicates that the transport protocol is IPv6.
  • the Tunnel Source IP Address field indicates the tunnel source IP address of the GRE tunnel. When the transport protocol is IPv4, the Tunnel Source IP Address field is 4 bytes. When the transport protocol is IPv6, the Tunnel Source IP Address field is 16 bytes.
  • the version number (Ver) indicates the protocol version number of the GRE control message; the protocol type (Protocol Type) is used to indicate the protocol type of the GRE control message; the keyword (key)
  • the field is used as a security parameter and is used as a multiplexer for the GRE tunnel on the HAG.
  • the "key” field is assigned by the HAG and is communicated to the HCPE.
  • the tunnel identifier of each GRE tunnel is directly, for example, the GRE tunnel.
  • the access network type also referred to as a tunnel type
  • the tunnel identifier (Tunnel ID) field of the GRE control packet shown in FIG. 4(a) may also be a tunnel type field, which is implemented by the present invention. This example does not limit this.
  • the GRE control message shown in Figure 4(a) is set to 1
  • the GRE control message is a GRE Tunnel Setup Request message
  • the GRE is The tunnel setup request carries the mapping between the tunnel ID and the source IP address of the tunnel.
  • the MsgType in the GRE control packet shown in FIG. 4(a) is set to 6
  • the GRE control packet is a GRE Tunnel Notify packet
  • the GRE Tunnel Notify is carried in the GRE Tunnel Notify. Correspondence between the tunnel ID and the source IP address of the tunnel.
  • the HCPE can notify the HAG of the correspondence between the source IP address of the GRE tunnel and the tunnel identifier based on the existing GRE control message, so that the HAG can flexibly distinguish and receive a service report according to the corresponding relationship.
  • the HCPE may send the corresponding relationship to the HAG through the GRE Tunnel Setup Request message during the GRE establishment process, or after the GRE tunnel is established, the GRE Tunnel Setup Request message sends the corresponding relationship to the HAG.
  • control messages including:
  • the HAG receives the GRE Tunnel Setup Request message sent by the HCPE, and the attribute field of the GRE Tunnel Setup Request message includes information indicating the correspondence.
  • FIG. 5 is a schematic flowchart of a scheme for the HCPE to notify the HAG of the correspondence between the source IP address of the GRE tunnel and the tunnel identifier by using the GRE Tunnel Setup Request message.
  • the HCPE sends a GRE Tunnel Setup Request message to the HAG to request to establish a first GRE tunnel with the HAG, where the GRE Tunnel Setup Request message includes the tunnel source IP address of the first GRE tunnel.
  • the format of the GRE Tunnel Setup Request message is as shown in Figure 4(b).
  • the HAG obtains a correspondence between the tunnel source IP address of the first GRE tunnel and the tunnel identifier according to the GRE Tunnel Setup Request; in S23, the HAG sends a GRE Tunnel Setup Accept to the HCPE, in response to establishing the first GRE. Tunnel.
  • the HCPE sends a service packet to the HAG by using the established first GRE tunnel, for example, "GRE Tunnel Hello", where the service packet carries the source IP address of the GRE tunnel that carries the service packet; in S25, The HAG obtains the source IP address of the GRE tunnel that carries the service packet according to the received service packet, and obtains the tunnel identifier of the GRE tunnel that carries the service packet according to the correspondence obtained in S22, so as to obtain the service identifier.
  • the message is from which of the first GRE tunnels.
  • the foregoing steps S21 to S25 are performed separately for each GRE tunnel of at least two GRE tunnels.
  • the HCPE sends a source carrying the first GRE tunnel to the HAG through the DSL interface.
  • the GRE Tunnel Setup Request message of the IP address and the tunnel identifier (for example, the access network type DSL where the first GRE tunnel is located) is used to request to establish a first DSL-based GRE tunnel with the HAG.
  • the HAG receives the GRE Tunnel Setup Request. After the packet is received, the mapping between the source IP address of the first GRE tunnel and the tunnel identifier is obtained.
  • the HAG sends a GRE Tunnel Setup Accept message to the HCPE in response to establishing the first GRE tunnel.
  • the GPE sends a GRE Tunnel Setup Request message carrying the source IP address of the second GRE tunnel and the tunnel identifier (for example, the access network type LTE where the second GRE tunnel is located) to the HAG through the LTE interface, and is used to request to establish a basis with the HAG.
  • the HAG After receiving the GRE Tunnel Setup Request message, the HAG obtains the correspondence between the source IP address of the second GRE tunnel and the tunnel identifier, and then the HAG sends a GRE Tunnel Setup Accept message to the HCPE. In response to establishing the second GRE tunnel.
  • the HCPE utilizes bound The first GRE tunnel and the second GRE tunnel send service packets to the HAG.
  • the HAG determines, according to the source IP address of the tunnel that the service packet is received, and the obtained correspondence, which GRE tunnel is received from the first GRE tunnel and the second GRE tunnel.
  • the correspondence relationship acquired by the HAG in S22 is IP Address 1 - DSL, IP Address 2 - LTE.
  • the source IP address of the bearer tunnel in which the HAG receives the service packet is IP Address 2
  • the HAG may determine that the GRE tunnel carrying the service packet is the second GRE tunnel based on the access network LTE.
  • the HCPE can notify the HAG of the mapping between the source IP address of the at least two GRE tunnels and the tunnel identifier based on the existing GRE control message, so that the HAG can be flexible according to the corresponding relationship.
  • the region receives a GRE tunnel from a traffic message from the at least two GRE tunnels, and there is no additional signaling overhead compared to the existing process.
  • the S130 receives the GRE control packet sent by the HCPE, and the method includes:
  • the HAG After the first GRE tunnel is established, the HAG receives the first GRE Tunnel Notify message sent by the HCPE, and the attribute field of the first GRE Tunnel Notify message includes information for indicating the correspondence.
  • FIG. 6 is a schematic flowchart of a scheme for the HCPE to actively notify the HAG of the correspondence between the source IP address of the GRE tunnel and the tunnel identifier by using the GRE Tunnel Notify packet.
  • the HCPE sends a GRE Tunnel Setup Request to the HAG to request to establish a first GRE tunnel with the HAG.
  • the GRE Tunnel Setup Request does not carry the correspondence between the tunnel source IP address and the tunnel identifier.
  • the HAG sends a GRE Tunnel Setup Accept message to the HCPE in response to establishing the first GRE tunnel.
  • the HCPE sends a GRE Tunnel Notify message to the HAG through the first GRE tunnel, where the GRE Tunnel Notify message carries the correspondence between the source IP address of the tunnel and the tunnel identifier of the first GRE tunnel, specifically, the GRE The format of the Tunnel Notify packet is as shown in Figure 4(c).
  • the HAG learns the correspondence between the tunnel type and the source IP address of the tunnel through the received GRE Tunnel Notify packet.
  • the HAG is sent to the HCPE.
  • the GRE Tunnel Setup Accept message is sent as a response, and the tunnel information is updated, that is, the correspondence between the tunnel source IP address and the tunnel identifier of the first GRE tunnel is saved.
  • the HCPE uses the established first GRE tunnel to the HAG.
  • the source IP address of the GRE tunnel carrying the service packet is carried.
  • the HAG obtains the source IP address of the GRE tunnel that carries the service packet according to the received service packet, and obtains the corresponding IP address according to the information obtained in S34.
  • the relationship is obtained by obtaining the tunnel identifier of the GRE tunnel that carries the service packet, so as to know which of the at least two GRE tunnels the service packet is from.
  • steps S31 to S37 are performed separately for each GRE tunnel of at least two GRE tunnels.
  • the HCPE can notify the HAG of the mapping between the source IP address of the at least two GRE tunnels and the tunnel identifier based on the existing GRE control message, so that the HAG can be flexible according to the corresponding relationship.
  • the region receives a GRE tunnel from a traffic message from the at least two GRE tunnels, and there is no additional signaling overhead compared to the existing process.
  • the correspondence between the source IP address of the HCPE and the tunnel identifier of the at least two GRE tunnels of the HAG is described above with reference to FIG. 5 and FIG. Alternatively, it may be notified after the HAG sends a request message to the HCPE, which is not limited by the embodiment of the present invention.
  • the method 300 further includes:
  • the HAG sends a GRE Tunnel Setup Accept message to the HCPE, where the GRE Tunnel Setup Accept message includes request information for requesting the correspondence.
  • the HAG receives the first GRE Tunnel Notify message sent by the HCPE, including:
  • the HAG receives the first GRE Tunnel Notify message sent by the HCPE according to the request information.
  • FIG. 7 is a schematic flowchart of a scheme for the HAG to request a correspondence between a source IP address of a GRE tunnel and a tunnel identifier by using a GRE Tunnel Setup Accept message by the HAG according to the embodiment of the present invention.
  • the HCPE sends a GRE Tunnel Setup Request to the HAG to request to establish a first GRE tunnel with the HAG.
  • the GRE Tunnel Setup Request does not carry the mapping between the tunnel source IP address and the tunnel identifier.
  • the HAG sends a GRE Tunnel Setup Accept message to the HCPE, in response to establishing the first GRE tunnel, and the GRE Tunnel Setup Accept message is further used to request the source IP address of the first GRE tunnel and the tunnel identifier.
  • the GRE Tunnel Setup Accept message carries the source IP address of the first GRE tunnel.
  • the format of the GRE Tunnel Setup Accept message may be: "MsgType" shown in Figure 4 (a) is set to "2", Tunnel Source IP Address The field carries the GRE tunnel source IP address, and the Tunnel ID field is empty.
  • the HCPE sends a GRE Tunnel Notify message to the HAG through the first GRE tunnel, where the GRE Tunnel Notify message carries the correspondence between the source IP address of the tunnel and the tunnel identifier of the first GRE tunnel.
  • the GRE Tunnel The format of the Notify message is shown in Figure 4(c).
  • the HAG learns the correspondence between the tunnel type and the source IP address of the tunnel through the received GRE Tunnel Notify message.
  • the HAG sends a GRE Tunnel Setup Accept message to the HCPE as a response, and updates the tunnel information.
  • the HCPE sends a service packet, such as "GRE Tunnel Hello", to the HAG by using the established first GRE tunnel.
  • the source IP address of the GRE tunnel carrying the service packet is carried in the packet.
  • the HAG obtains the source IP address of the GRE tunnel that carries the service packet according to the received service packet, and obtains the tunnel identifier of the GRE tunnel that carries the service packet according to the correspondence obtained in S44. Therefore, it is learned which one of the at least two GRE tunnels the service message is from.
  • steps S41 to S47 are performed separately for each GRE tunnel of at least two GRE tunnels.
  • the HCPE can notify the HAG of the mapping between the source IP address of the at least two GRE tunnels and the tunnel identifier based on the existing GRE control message, so that the HAG can be flexible according to the corresponding relationship.
  • the region receives a GRE tunnel from a traffic message from the at least two GRE tunnels, and there is no additional signaling overhead compared to the existing process.
  • the HAG receives the first GRE Tunnel Notify message sent by the HCPE, including:
  • the HAG receives the first GRE Tunnel Notify message sent by the HCPE according to the second GRE Tunnel Notify message.
  • FIG. 8 is a schematic flowchart of a scheme in which a HAG uses a GRE Tunnel Notify message to request a correspondence between a source IP address and a tunnel type of a GRE tunnel by a HAG according to an embodiment of the present invention.
  • the HCPE sends a GRE Tunnel Setup Request to the HAG to request to establish a first GRE tunnel with the HAG.
  • the GRE Tunnel Setup Request does not carry the mapping between the tunnel source IP address and the tunnel identifier.
  • the HAG sends to the HCPE GRE Tunnel Setup Accept message in response to establishing the first GRE tunnel.
  • the HAG sends a GRE Tunnel Notify message to the HCPE to request a correspondence between the source IP address of the first GRE tunnel and the tunnel identifier, and optionally, the GRE Tunnel Notify packet carries the first The source IP address of the GRE tunnel.
  • the format of the GRE Tunnel Notify packet is as shown in Figure 4 (c).
  • the Attribute Type of the GRE Tunnel Notify packet is 55.
  • the source of the GRE tunnel is carried in the Tunnel Source IP Address field.
  • the IP address, but the tunnel ID field is empty.
  • the HCPE sends a GRE Tunnel Notify message to the HAG through the first GRE tunnel.
  • the GRE Tunnel Notify packet carries the tunnel source IP address and tunnel of the first GRE tunnel.
  • the HAG learns the correspondence between the tunnel type and the tunnel source IP address through the received GRE Tunnel Notify message.
  • the HAG sends a GRE Tunnel Setup Accept message to the HCPE as a response, and updates the tunnel information, that is, the learned correspondence is saved.
  • the HCPE sends a service packet to the HAG by using the established first GRE tunnel, for example, GRE tunnel Hello.
  • the service packet carries the source IP address of the GRE tunnel that carries the service packet.
  • the HAG obtains the source IP address of the GRE tunnel that carries the service packet according to the received service packet, and obtains the tunnel identifier of the GRE tunnel that carries the service packet according to the correspondence obtained in S55. Therefore, it is learned which one of the at least two GRE tunnels the service message is from.
  • steps S51 to S58 are performed separately for each GRE tunnel of at least two GRE tunnels.
  • the HCPE can notify the HAG of the mapping between the source IP address of the at least two GRE tunnels and the tunnel identifier based on the existing GRE control message, so that the HAG can be flexible according to the corresponding relationship.
  • the region receives a GRE tunnel from a traffic message from the at least two GRE tunnels, and there is no additional signaling overhead compared to the existing process.
  • the HAG obtains the correspondence between the source IP address and the tunnel identifier of the at least two GRE tunnels, and can receive a certain service packet from the flexible relationship according to the corresponding relationship. Which of the at least two GRE tunnels is the GRE tunnel. Therefore, the method provided by the present invention can flexibly and efficiently distinguish and connect in the GRE tunnel binding scenario.
  • the GRE tunnel is received from a certain service packet, which can meet the current OAM requirements of the GRE tunnel.
  • GRE control message Attribute Type has other rich Attributes Type types in addition to the Attribute Type 55 shown in Figure 4 to complete the operations of the GRE control plane. This is a prior art and will not be described in detail herein. Said.
  • FIG. 9 is a schematic flowchart of a method 200 for determining a GRE tunnel identifier according to an embodiment of the present invention. The method is described from the perspective of an HCPE, and the method is applied to a hybrid access gateway HAG and a hybrid access terminal device HCPE. There are at least two scenarios of GRE tunnels, and the at least two GRE tunnels are bound. As shown in FIG. 9, the method 200 includes:
  • the HCPE determines a first GRE tunnel, where the first GRE tunnel is one of the at least two GRE tunnels;
  • the HCPE sends a service packet to the HAG by using the first GRE tunnel, where the service packet includes a source IP address of the first GRE tunnel that carries the service packet, so that the HAG carries the service packet according to the bearer.
  • the source IP address of the first GRE tunnel is searched for the corresponding relationship table, and the tunnel identifier of the first GRE tunnel that carries the service packet is determined.
  • the correspondence table includes the source IP address of the first GRE tunnel and the first GRE.
  • the mapping between the tunnel IDs of the tunnels, where the source IP address of the first GRE tunnel is the IP address of the tunnel port of the first GRE tunnel, and the tunnel identifier of the first GRE tunnel is used for the unique indication.
  • the first GRE tunnel is used for the unique indication.
  • the HAG can flexibly and efficiently distinguish which service packet is received according to the correspondence between the source IP address of the GRE tunnel and the tunnel identifier.
  • the GRE tunnel can meet the current OAM requirements of the GRE tunnel.
  • the tunnel identifier of the first GRE tunnel mentioned in the present invention may be directly connected to the first GRE tunnel.
  • Incoming network type also known as tunnel type.
  • the access network types of the different GRE tunnels in the at least two GRE tunnels are different, and the tunnel identifier of the first GRE tunnel indicates the access network where the first GRE tunnel is located. Types of.
  • the tunnel identifier of the first GRE tunnel is, for example, a DSL
  • the tunnel identifier of the second GRE tunnel is, for example, LTE.
  • FIG. 1 is only an example and not a limitation, and the type of access network where the GRE tunnel is located includes solid A fixed access network and a mobile access network, wherein a fixed access network, such as a Digital Subscriber Line (DSL) access network, such as a 3G network, an LTE network, or other mobile access network.
  • a fixed access network such as a Digital Subscriber Line (DSL) access network, such as a 3G network, an LTE network, or other mobile access network.
  • DSL Digital Subscriber Line
  • the HAG obtains the corresponding relationship between the source IP address and the access network type of the at least two GRE tunnels, and when the service packet is received, the HAG can flexibly determine the bearer according to the corresponding relationship.
  • the access network type of the GRE tunnel of the packet so that in the GRE tunnel binding scenario, the GRE tunnel can be flexibly and efficiently separated from the GRE tunnel, so that the current carrier can be satisfied. Urgent need.
  • the method 200 before the sending, by the first GRE tunnel, the service message to the HAG, the method 200 further includes:
  • the HCPE sends a GRE control message to the HAG, where the GRE control message includes information indicating a correspondence between a source IP address of the first GRE tunnel and a tunnel identifier of the first GRE tunnel.
  • the HCPE can notify the HAG of the correspondence between the source IP address of the GRE tunnel and the tunnel identifier based on the existing GRE control message, so that the HAG can flexibly distinguish and receive a service packet according to the corresponding relationship.
  • GRE tunnel there is no additional signaling overhead compared to the existing process.
  • the HCPE can notify the HAG of the correspondence between the source IP address of the at least two GRE tunnels and the tunnel identifier, so that the HAG can flexibly distinguish and receive a service packet according to the corresponding relationship.
  • the S3300 sends the GRE control message to the HAG, including:
  • the HCPE sends a GRE Tunnel Setup Request message to the HAG, and the attribute field of the GRE Tunnel Setup Request message includes information indicating the correspondence.
  • the S3300 sends the GRE control message to the HAG, including:
  • the HCPE After the first GRE tunnel is established, the HCPE sends a first GRE Tunnel Notify message to the HAG, where the attribute field of the first GRE Tunnel Notify message includes information indicating the correspondence.
  • the method 200 further includes:
  • the HCPE receives the GRE Tunnel Setup Accept message sent by the HAG, where the GRE Tunnel Setup Accept message includes request information for requesting the corresponding relationship;
  • the HCPE sends the first GRE Tunnel Notify message to the HAG, including:
  • the HCPE sends the first GRE Tunnel Notify message to the HAG according to the request information.
  • the HCPE sends the first GRE Tunnel Notify message to the HAG, including:
  • the HCPE sends the first GRE Tunnel Notify message to the HAG according to the second GRE Tunnel Notify message.
  • the HCPE can notify the HAG of the mapping between the source IP address of the at least two GRE tunnels and the tunnel identifier based on the existing GRE control message, so that the HAG can be flexible according to the corresponding relationship.
  • the region receives a GRE tunnel from a traffic message from the at least two GRE tunnels, and there is no additional signaling overhead compared to the existing process.
  • the HAG in a GRE tunnel binding scenario, can flexibly and efficiently distinguish a received service packet from the corresponding relationship between the source IP address of the GRE tunnel and the tunnel identifier. Which GRE tunnel can meet the current OAM requirements of the operator for the GRE tunnel.
  • FIG. 10 is a schematic block diagram of a network device 300 provided with a scenario of at least two GRE tunnels between the network device 300 and the hybrid access terminal device HCPE, and the at least two GRE tunnels are tied
  • the network device 300 includes:
  • the receiving module 310 is configured to receive a service packet that is sent by the HCPE by using the first GRE tunnel, where the service packet includes a source IP address of the first GRE tunnel that carries the service packet, where the first GRE tunnel is One of the at least two GRE tunnels;
  • the determining module 320 is configured to search the correspondence table according to the source IP address of the first GRE tunnel that is used by the receiving module to determine the tunnel identifier of the first GRE tunnel that carries the service packet, and the corresponding
  • the relationship table includes a mapping between a source IP address of the first GRE tunnel and a tunnel identifier of the first GRE tunnel, where the source IP address of the first GRE tunnel is a tunnel of the first GRE tunnel on the HCPE The IP address of the port, the tunnel identifier of the first GRE tunnel is used to uniquely indicate the first GRE tunnel.
  • the network device 300 may correspond to the HAG in the method for determining the GRE tunnel identity of the embodiment of the present invention.
  • the HAG in a GRE tunnel binding scenario, can flexibly and efficiently distinguish a received service packet from the corresponding relationship between the source IP address of the GRE tunnel and the tunnel identifier. Which GRE tunnel can meet the current OAM requirements of the operator for the GRE tunnel.
  • the receiving module 310 is further configured to: before receiving the service packet sent by the HCPE by using the first GRE tunnel, receive the GRE control packet sent by the HCPE, where the GRE control packet is received. And including information indicating a correspondence between a source IP address of the first GRE tunnel and a tunnel identifier of the first GRE tunnel;
  • the network device 300 further includes:
  • the obtaining module 330 is configured to obtain the correspondence according to the GRE control packet received by the receiving module.
  • the HAG obtains a correspondence between the source IP address of the at least two GRE tunnels and the tunnel identifier, and can receive a certain service packet flexibly according to the corresponding relationship. Which GRE tunnel is in at least two GRE tunnels. Therefore, the method provided by the present invention can flexibly and efficiently distinguish which GRE tunnel a received service packet is from in a GRE tunnel binding scenario, thereby satisfying the current OAM requirement of the operator for the GRE tunnel. .
  • the receiving module 310 is configured to receive, in the process of establishing the first GRE tunnel, a GRE Tunnel Setup Request message sent by the HCPE, and an attribute of the GRE Tunnel Setup Request message.
  • the field includes information indicating the correspondence.
  • the receiving module 310 is configured to: after the first GRE tunnel is established, receive the first GRE Tunnel Notify packet sent by the HCPE, and the attribute of the first GRE Tunnel Notify packet
  • the field includes information indicating the correspondence.
  • the network device 300 further includes:
  • the sending module 340 is configured to send a GRE Tunnel Setup Accept message to the HCPE in the process of establishing the first GRE tunnel, where the GRE Tunnel Setup Accept message includes request information for requesting the corresponding relationship;
  • the receiving module 310 is configured to receive the first GRE Tunnel Notify message sent by the HCPE according to the request information.
  • the receiving module 310 includes:
  • a sending unit configured to send, to the HCPE, a second GRE Tunnel Notify message for requesting the corresponding relationship
  • the receiving unit is configured to receive the first GRE Tunnel Notify message sent by the HCPE according to the second GRE Tunnel Notify message sent by the sending unit.
  • the access network types of the different GRE tunnels in the at least two GRE tunnels are different, and the tunnel identifier of the first GRE tunnel indicates the access network where the first GRE tunnel is located. Types of.
  • the network device 300 may correspond to the HAG in the method for determining the GRE tunnel identity of the embodiment of the present invention, and the foregoing and other operations and/or functions of the respective modules in the network device 300 are respectively implemented.
  • the corresponding processes of the respective methods in FIG. 1 to FIG. 9 are not described herein again for the sake of brevity.
  • the HAG obtains a correspondence between the source IP address of the at least two GRE tunnels and the tunnel identifier, and can receive a certain service packet flexibly according to the corresponding relationship. Which GRE tunnel is in at least two GRE tunnels. Therefore, the method provided by the present invention can flexibly and efficiently distinguish which GRE tunnel a received service packet is from in a GRE tunnel binding scenario, thereby satisfying the current OAM requirement of the operator for the GRE tunnel. .
  • FIG. 10 also shows a schematic block diagram of a network device 400 provided with at least two GRE tunnels between the network device 400 and the hybrid access gateway HAG, and the at least two GRE tunnels are tied.
  • the network device 400 includes:
  • a determining module 410 configured to determine a first GRE tunnel, where the first GRE tunnel is the at least two a GRE tunnel in a GRE tunnel;
  • the sending module 420 is configured to send a service packet to the HAG by using the first GRE tunnel determined by the determining module, where the service packet includes a source IP address of the first GRE tunnel that carries the service packet, to facilitate the
  • the HAG searches for the corresponding relationship table according to the source IP address of the first GRE tunnel that carries the service packet, and determines the tunnel identifier of the first GRE tunnel that carries the service packet, where the correspondence relationship table includes the source of the first GRE tunnel.
  • the tunnel identifier is used to uniquely indicate the first GRE tunnel.
  • the network device 400 corresponds to the HCPE in the method for determining the GRE tunnel identifier provided by the embodiment of the present invention.
  • the HAG in a GRE tunnel binding scenario, can flexibly and efficiently distinguish a received service packet from the corresponding relationship between the source IP address of the GRE tunnel and the tunnel identifier. Which GRE tunnel can meet the current OAM requirements of the operator for the GRE tunnel.
  • the sending module 420 is further configured to: before sending the service packet to the HAG by using the first GRE tunnel, send a GRE control packet to the HAG, where the GRE control packet includes Information for indicating a correspondence between a source IP address of the first GRE tunnel and a tunnel identifier of the first GRE tunnel.
  • the HCPE can notify the HAG of the correspondence between the source IP address and the tunnel identifier of the at least two GRE tunnels, so that the HAG can flexibly distinguish and receive a service packet according to the corresponding relationship.
  • the sending module 420 is configured to send a GRE Tunnel Setup Request message to the HAG in the process of establishing the first GRE tunnel, and the attribute field of the GRE Tunnel Setup Request message Information for indicating the correspondence is included.
  • the sending module 420 is configured to: after the first GRE tunnel is established, send a first GRE Tunnel Notify message to the HAG, and the attribute field of the first GRE Tunnel Notify message Information for indicating the correspondence is included.
  • the network device 400 further includes:
  • the receiving module 430 is configured to receive, in the process of establishing the first GRE tunnel, a GRE Tunnel Setup Accept message sent by the HAG, where the GRE Tunnel Setup Accept message includes request information for requesting the corresponding relationship;
  • the sending module 420 is configured to send the first GRE Tunnel Notify message to the HAG according to the request information.
  • the sending module 420 includes:
  • a receiving unit configured to receive a second GRE Tunnel Notify message sent by the HAG to request the corresponding relationship
  • the sending unit is configured to send the first GRE Tunnel Notify message to the HAG according to the second GRE Tunnel Notify message received by the receiving unit.
  • the access network types of the different GRE tunnels in the at least two GRE tunnels are different, and the tunnel identifier of the first GRE tunnel indicates the access network where the first GRE tunnel is located. Types of.
  • the network device 400 may correspond to the HCPE in the method for determining the GRE tunnel identity of the embodiment of the present invention, and the foregoing and other operations and/or functions of the respective modules in the network device 400 are respectively implemented.
  • the corresponding processes of the respective methods in FIG. 1 to FIG. 9 are not described herein again for the sake of brevity.
  • the HCPE can notify the HAG of the correspondence between the source IP address and the tunnel identifier of the at least two GRE tunnels, so that the HAG can flexibly distinguish and receive a service packet according to the corresponding relationship.
  • FIG. 11 shows a system 500 for determining a generic route encapsulation GRE tunnel identifier according to an embodiment of the present invention.
  • the system 500 includes a network device 300 according to an embodiment of the present invention, and a network device 400 according to an embodiment of the present invention.
  • the network device 300 corresponds to the HAG in the method for determining the GRE tunnel identifier according to the embodiment of the present invention
  • the network device 400 corresponds to the HCPE in the method for determining the GRE tunnel identifier according to the embodiment of the present invention
  • each of the systems 500 The above and other operations and/or functions of the modules are respectively implemented in order to implement the respective processes of the respective methods in FIG. 1 to FIG. 9, and are not described herein again for brevity.
  • the HAG in a GRE tunnel binding scenario, can flexibly and efficiently distinguish a received service packet from the corresponding relationship between the source IP address of the GRE tunnel and the tunnel identifier. Which GRE tunnel can meet the current OAM requirements of the operator for the GRE tunnel.
  • the embodiment of the present invention further provides a network device 600, where there are at least two GRE tunnels between the network device 600 and the hybrid access terminal device HCPE, and the at least two GRE tunnels are bound.
  • the network device 600 includes a processor 610, a memory 620, a bus system 630, a receiver 640, and a transmitter 650.
  • the processor 610, the memory 620, the receiver 640, and the transmitter 650 are connected by a bus system 630.
  • the memory 620 is configured to store instructions for executing the instructions stored in the memory 620 to control the receiver 640 to receive. Signal and control transmitter 650 to send a signal.
  • the receiver 640 is configured to receive a service packet that is sent by the HCPE through the first GRE tunnel, where the service packet includes a source IP address of the first GRE tunnel that carries the service packet, where the first GRE The tunnel is one of the at least two GRE tunnels;
  • the processor 610 is configured to: search, according to the source IP address of the first GRE tunnel that carries the service packet, a mapping table, and determine a tunnel identifier of the first GRE tunnel that carries the service packet, where the correspondence table includes the first Corresponding relationship between the source IP address of the GRE tunnel and the tunnel identifier of the first GRE tunnel, where the source IP address of the first GRE tunnel is the IP address of the tunnel port of the first GRE tunnel on the HCPE.
  • the tunnel identifier of the first GRE tunnel is used to uniquely indicate the first GRE tunnel.
  • the network device 600 may correspond to the HAG in the method for determining the GRE tunnel identity of the embodiment of the present invention.
  • the HAG in a GRE tunnel binding scenario, can flexibly and efficiently distinguish a received service packet from the corresponding relationship between the source IP address of the GRE tunnel and the tunnel identifier. Which GRE tunnel can meet the current OAM requirements of the operator for the GRE tunnel.
  • the receiver 640 is configured to: before receiving the service packet sent by the HCPE by using the first GRE tunnel, receive the GRE control packet sent by the HCPE, where the GRE control packet includes Information indicating a correspondence between a source IP address of the first GRE tunnel and a tunnel identifier of the first GRE tunnel;
  • the processor 610 is configured to obtain the correspondence according to the GRE control packet.
  • the HAG obtains a correspondence between the source IP address of the at least two GRE tunnels and the tunnel identifier, and can receive a certain service packet flexibly according to the corresponding relationship. Which GRE tunnel is in at least two GRE tunnels. Therefore, the method provided by the present invention can flexibly and efficiently distinguish which GRE tunnel a received service packet is from in a GRE tunnel binding scenario, thereby satisfying the current OAM requirement of the operator for the GRE tunnel. .
  • the receiver 640 is configured to receive, in the process of establishing the first GRE tunnel, a GRE Tunnel Setup Request message sent by the HCPE, and an attribute field of the GRE Tunnel Setup Request message. Information for indicating the correspondence is included.
  • the receiver 640 is configured to: after the first GRE tunnel is established, receive the first GRE Tunnel Notify message sent by the HCPE, and the attribute field of the first GRE Tunnel Notify message Information for indicating the correspondence is included.
  • the transmitter 650 is configured to send a GRE Tunnel Setup Accept message to the HCPE in the process of establishing the first GRE tunnel, where the GRE Tunnel Setup Accept message is included in the GRE Tunnel Setup Accept message. Requesting the request information of the corresponding relationship;
  • the receiver 640 is configured to receive the first GRE Tunnel Notify message sent by the HCPE according to the request information.
  • the transmitter 650 is configured to send, to the HCPE, a second GRE Tunnel Notify message for requesting the corresponding relationship;
  • the receiver 640 is configured to receive the first GRE Tunnel Notify message sent by the HCPE according to the second GRE Tunnel Notify message.
  • the access network types of the different GRE tunnels in the at least two GRE tunnels are different, and the tunnel identifier of the first GRE tunnel indicates the access network where the first GRE tunnel is located. Types of.
  • the processor 610 may be a central processing unit ("CPU"), and the processor 610 may also be other general-purpose processors, digital signal processors (DSPs). , an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, and the like.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 620 can include read only memory and random access memory and provides instructions and data to the processor 610. A portion of the memory 620 can also include a non-volatile random access memory. For example, the memory 620 can also store information of the device type.
  • the bus system 630 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 630 in the figure.
  • each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 610 or an instruction in a form of software.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 620, and the processor 610 reads the information in the memory 620 and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • the network device 600 may correspond to the HAG in the method for determining the GRE tunnel identifier of the embodiment of the present invention, and also corresponds to the network device 300 of the embodiment of the present invention, and each module in the network device 600.
  • the above and other operations and/or functions are respectively implemented in order to implement the respective processes of the respective methods in FIG. 1 to FIG. 9, and are not described herein again for brevity.
  • the HAG obtains a correspondence between the source IP address of the at least two GRE tunnels and the tunnel identifier, and can receive a certain service packet flexibly according to the corresponding relationship. Which GRE tunnel is in at least two GRE tunnels. Therefore, the method provided by the present invention can flexibly and efficiently distinguish which GRE tunnel a received service packet is from in a GRE tunnel binding scenario, thereby satisfying the current OAM requirement of the operator for the GRE tunnel. .
  • the embodiment of the present invention further provides a network device 700, where the network device 700 and the hybrid access gateway HAG have at least two GRE tunnels, and the at least two GRE tunnels are bound.
  • the network device 700 includes a processor 710, a memory 720, a bus system 730, a receiver 740, and a transmitter 750.
  • the processor 710, the memory 720, the receiver 740 and the transmitter 750 are connected by a bus system 730 for storing instructions for executing instructions stored in the memory 720 to control the receiver 740 to receive. Signal and control transmitter 750 to send a signal.
  • the processor 710 is configured to determine a first GRE tunnel, where the first GRE tunnel is one of the at least two GRE tunnels, and the transmitter 750 is configured to send a service report to the HAG by using the first GRE tunnel.
  • the service packet includes the source IP address of the first GRE tunnel that carries the service packet, so that the HAG is based on the bearer.
  • the mapping table Determining, by the source IP address of the first GRE tunnel, the mapping table, the tunnel identifier of the first GRE tunnel that carries the service packet, where the correspondence relationship table includes the source IP address of the first GRE tunnel and Corresponding relationship between the tunnel identifiers of the first GRE tunnel, where the source IP address of the first GRE tunnel is the IP address of the tunnel port of the first GRE tunnel on the HCPE, and the tunnel identifier of the first GRE tunnel Used to uniquely indicate the first GRE tunnel.
  • the network device 700 corresponds to the HCPE in the method for determining the GRE tunnel identifier provided by the embodiment of the present invention.
  • the HAG in a GRE tunnel binding scenario, can flexibly and efficiently distinguish a received service packet from the corresponding relationship between the source IP address of the GRE tunnel and the tunnel identifier. Which GRE tunnel can meet the current OAM requirements of the operator for the GRE tunnel.
  • the transmitter 750 is configured to send a GRE control packet to the HAG before sending the service packet to the HAG by using the first GRE tunnel, where the GRE control packet includes Information indicating a correspondence between a source IP address of the first GRE tunnel and a tunnel identifier of the first GRE tunnel.
  • the HCPE can notify the HAG of the correspondence between the source IP address and the tunnel identifier of the at least two GRE tunnels, so that the HAG can flexibly distinguish and receive a service packet according to the corresponding relationship.
  • the transmitter 750 is configured to send a GRE Tunnel Setup Request message to the HAG in the process of establishing the first GRE tunnel, where the GRE Tunnel Setup Request message is in an attribute field. Information for indicating the correspondence is included.
  • the transmitter 750 is configured to: after the first GRE tunnel is established, send a first GRE Tunnel Notify message to the HAG, where the first GRE Tunnel Notify message is in an attribute field. Information for indicating the correspondence is included.
  • the receiver 740 is configured to receive the GRE Tunnel Setup Accept message sent by the HAG in the process of establishing the first GRE tunnel, where the GRE Tunnel Setup Accept message is included in the GRE Tunnel Setup Accept message. Request information for requesting the correspondence;
  • the transmitter 750 is configured to send the first GRE Tunnel to the HAG according to the request information. Notify message.
  • the receiver 740 is configured to receive a second GRE Tunnel Notify message that is sent by the HAG to request the corresponding relationship;
  • the sender 750 is configured to send the first GRE Tunnel Notify message to the HAG according to the second GRE Tunnel Notify message.
  • the access network types of the different GRE tunnels in the at least two GRE tunnels are different, and the tunnel identifier of the first GRE tunnel indicates the access network where the first GRE tunnel is located. Types of.
  • the processor 710 may be a central processing unit (“CPU"), and the processor 710 may also be other general-purpose processors, digital signal processors (DSPs). , an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, and the like.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 720 can include read only memory and random access memory and provides instructions and data to the processor 710. A portion of the memory 720 can also include a non-volatile random access memory. For example, the memory 720 can also store information of the device type.
  • the bus system 730 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 730 in the figure.
  • each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 710 or an instruction in a form of software.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in memory 720, and processor 710 reads the information in memory 720 and, in conjunction with its hardware, performs the steps of the above method. To avoid repetition, it will not be described in detail here.
  • the network device 700 according to the embodiment of the present invention may correspond to the HCPE in the method for determining the GRE tunnel identifier of the embodiment of the present invention, and also corresponds to the network device 400 according to the embodiment of the present invention, and each of the network devices 700
  • the above and other operations and/or functions of the modules are respectively implemented in order to implement the respective processes of the respective methods in FIG. 1 to FIG. 9, and are not described herein again for brevity.
  • the HCPE notifies the HAG of the binding of at least two GRE tunnels.
  • the HAG can flexibly distinguish which GRE tunnel of the at least two GRE tunnels a service packet receives from the service. Therefore, the method provided by the present invention can flexibly and efficiently distinguish which GRE tunnel a received service packet is from in a GRE tunnel binding scenario, thereby satisfying the current OAM requirement of the operator for the GRE tunnel. .
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated in one unit. In the unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提供一种确定GRE隧道标识的方法、设备和系统，应用于HAG与HCPE之间有至少两条GRE隧道的场景，该至少两条GRE隧道绑定，该方法包括：HAG接收HCPE经由第一GRE隧道发送的业务报文，该业务报文中包括承载该业务报文的第一GRE隧道的源IP地址，第一GRE隧道为至少两条GRE隧道中的一条；该HAG根据第一GRE隧道的源IP地址查找对应关系表，确定承载该业务报文的该第一GRE隧道的隧道标识，该对应关系表包括第一GRE隧道的源IP地址与第一GRE隧道的隧道标识之间的对应关系。因此，在本发明实施例中，在GRE隧道绑定场景下，能够灵活高效地区分出接收到的业务报文来自于哪个GRE隧道。

Description

确定通用路由封装GRE隧道标识的方法、设备和系统 技术领域
本发明实施例涉及通信领域，并且更具体地，涉及一种确定通用路由封装GRE隧道标识的方法、设备和系统。
背景技术
混合接入(Hybrid Access，简称为“HA”)是一种绑定异构网络的接入技术，用户可以同时接入两种或两种以上的接入网络来访问网络侧，例如在家庭宽带网络中，用户可同时接入固定接入网络(例如，数字用户线路(Digital Subscriber Line，简称为“DSL”))和移动接入网络(例如，长期演进(Long time Evolution,简称为“LTE”))，能够为用户提供更快的业务开通服务、更可靠的WAN连接、以及更大的带宽。
当前技术中，采用通用路由封装(Generation Routing Encapsulation，简称为“GRE”)隧道绑定实现HA技术。如图1所示，用户侧的混合终端接入设备(Hybrid Customer Premises Equipment，简称为“HCPE”)利用DSL接口和LTE接口分别与网络侧的混合接入网关(Hybrid Access Gateway，简称为“HAG”)创建基于DSL接入网络的第一GRE隧道和基于LTE接入网络的第二GRE隧道，该第一GRE隧道和该第二GRE隧道绑定之后，HCPE上同一业务的报文可以同时通过第一GRE隧道和第二GRE隧道传输到HAG。假设DSL接入网络的带宽为1G，LTE接入网络的带宽为1G，则该第一GRE隧道和该第二GRE隧道绑定之后可为用户提供2G的接入网络带宽。
但在两条GRE隧道绑定之后，在HAG上无法区分接收到的某个业务报文来自哪条GRE隧道，目前运营商对此提出迫切需要。
发明内容
本发明提供一种确定GRE隧道标识的方法、设备和系统，能够在至少两条GRE隧道进行绑定后，灵活地区分接收到的某个业务报文来自哪个GRE隧道。
第一方面，提供了一种确定通用路由封装GRE隧道标识的方法，该方法应用于混合接入网关HAG与混合接入终端设备HCPE之间有至少两条GRE隧道的场景，且该至少两条GRE隧道绑定，该方法包括：
该HAG接收该HCPE经由第一GRE隧道发送的业务报文，该业务报文中包括承载该业务报文的该第一GRE隧道的源IP地址，其中，该第一GRE隧道为该至少两条GRE隧道中的一条GRE隧道；
该HAG根据承载该业务报文的该第一GRE隧道的源IP地址查找对应关系表，确定承载该业务报文的该第一GRE隧道的隧道标识，该对应关系表包括该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系，其中，该第一GRE隧道的源IP地址为该第一GRE隧道在该HCPE上的隧道端口的IP地址，该第一GRE隧道的隧道标识用于唯一指示该第一GRE隧道。
应理解，在本发明中，该第一GRE隧道指示该至少两条GRE隧道中的任一条GRE隧道。例如，上述针对第一GRE隧道的各个步骤在该至少两条GRE隧道中的每条GRE隧道上都执行。
该第一GRE隧道的源IP地址指的是该第一GRE隧道在HCPE上的隧道端口的IP地址，具体地，如图1所示，第一GRE隧道的源IP地址指的是HCPE的DSL接口的IP地址，第二GRE隧道的源IP地址指的是HCPE的LTE接口的IP地址。
该第一GRE隧道的隧道标识用于唯一指示该第一GRE隧道，具体地，例如，该隧道标识为第一GRE隧道的隧道编号，假设至少两条GRE隧道包括5条GRE隧道，其中，这5条GRE隧道的隧道标识分别为1、2、3、4、5。应理解，第一GRE隧道的隧道标识还可以采用其他能够唯一指示第一GRE隧道的呈现形式，例如字母或者罗马数字等，本发明对此不作限定。
因此，在本发明中，在GRE隧道绑定场景下，HAG能够根据GRE隧道的源IP地址与隧道标识之间的对应关系，灵活、高效地区分接收到的某个业务报文来自于哪条GRE隧道，从而能够满足当前运营商对GRE隧道操作、管理和维护(Operation Administration and Maintenance，简称为“OAM”)的需求。
具体地，HAG可以从HCPE处获取第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系，也可以从上层设备(例如网管设备或者控制器)获取该对应关系。
结合第一方面，在第一方面的第一种可能的实现方式中，在该HAG接收该HCPE经由该第一GRE隧道发送的业务报文之前，该方法还包括：
该HAG接收该HCPE发送的GRE控制报文，该GRE控制报文包括用于指示该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系的信息；
该HAG根据该GRE控制报文，获取该对应关系。
应理解，HAG获取了第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系之后，将该对应关系存储到本地的对应关系表中。还应理解，该对应关系表中包括该至少两条GRE隧道中每条GRE隧道各自的源IP地址与隧道标识之间的对应关系。
在本发明中，HCPE可以基于现有的GRE控制报文向HAG通知GRE隧道的源IP地址与隧道标识的对应关系，使得HAG可以根据该对应关系，灵活地区分接收到某个业务报文来自于哪条GRE隧道，与现有流程相比，并没有额外的信令开销。
在本发明中，HCPE通过向HAG通知绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，使得HAG能够根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道。因此，本发明提供的方法，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
结合第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，该HAG接收该HCPE发送的GRE控制报文，包括：
在建立该第一GRE隧道的过程中，该HAG接收该HCPE发送的GRE Tunnel Setup Request报文，该GRE Tunnel Setup Request报文的属性字段中包括用于指示该对应关系的信息。
结合第一方面的第一种可能的实现方式，在第一方面的第三种可能的实现方式中，该HAG接收该HCPE发送的GRE控制报文，包括：
在建立该第一GRE隧道之后，该HAG接收该HCPE发送的第一GRE Tunnel Notify报文，该第一GRE Tunnel Notify报文的属性字段中包括用于指示该对应关系的信息。
结合第一方面的第三种可能的实现方式，在第一方面的第四种可能的实现方式中，该方法还包括：
在建立该第一GRE隧道的过程中，该HAG向该HCPE发送GRE Tunnel  Setup Accept报文，该GRE Tunnel Setup Accept报文中包括用于请求该对应关系的请求信息；
其中，该HAG接收该HCPE发送的第一GRE Tunnel Notify报文，包括：
该HAG接收该HCPE根据该请求信息发送的该第一GRE Tunnel Notify报文。
结合第一方面的第三种可能的实现方式，在第一方面的第五种可能的实现方式中，该HAG接收该HCPE发送的第一GRE Tunnel Notify报文，包括：
该HAG向该HCPE发送用于请求该对应关系的第二GRE Tunnel Notify报文；
该HAG接收该HCPE根据该第二GRE Tunnel Notify报文发送的该第一GRE Tunnel Notify报文。
因此，本发明提供的方法，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
第二方面提供了一种确定通用路由封装GRE隧道标识的方法，该方法应用于混合接入网关HAG与混合接入终端设备HCPE之间有至少两条GRE隧道的场景，且该至少两条GRE隧道绑定，该方法包括：
该HCPE确定第一GRE隧道，该第一GRE隧道为该至少两条GRE隧道中的一条GRE隧道；
该HCPE经由该第一GRE隧道向该HAG发送业务报文，该业务报文中包括承载该业务报文的该第一GRE隧道的源IP地址，以便于该HAG根据承载该业务报文的该第一GRE隧道的源IP地址查找对应关系表，确定承载该业务报文的该第一GRE隧道的隧道标识，该对应关系表包括该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系，其中，该第一GRE隧道的源IP地址为该第一GRE隧道在该HCPE上的隧道端口的IP地址，该第一GRE隧道的隧道标识用于唯一指示该第一GRE隧道。
因此，在本发明中，在GRE隧道绑定场景下，HAG能够根据GRE隧道的源IP地址与隧道标识之间的对应关系，灵活、高效地区分接收到的某个业务报文来自于哪条GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
结合第二方面，在第二方面的第一种可能的实现方式中，在该HCPE经 由该第一GRE隧道向该HAG发送业务报文之前，该方法还包括：
该HCPE向该HAG发送GRE控制报文，该GRE控制报文包括用于指示该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系的信息。
在本发明中，HCPE可以基于现有的GRE控制报文向HAG通知GRE隧道的源IP地址与隧道标识的对应关系，使得HAG可以根据该对应关系，灵活地区分接收到某个业务报文来自于哪条GRE隧道，与现有流程相比，并没有额外的信令开销。
结合第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，该HCPE向该HAG发送GRE控制报文，包括：
在建立该第一GRE隧道的过程中，该HCPE向该HAG发送GRE Tunnel Setup Request报文，该GRE Tunnel Setup Request报文的属性字段中包括用于指示该对应关系的信息。
结合第二方面的第一种可能的实现方式，在第二方面的第三种可能的实现方式中，该HCPE向该HAG发送GRE控制报文，包括：
在建立该第一GRE隧道之后，该HCPE向该HAG发送第一GRE Tunnel Notify报文，该第一GRE Tunnel Notify报文的属性字段中包括用于指示该对应关系的信息。
结合第二方面的第三种可能的实现方式，在第二方面的第四种可能的实现方式中，该方法还包括：
在建立该第一GRE隧道的过程中，该HCPE接收该HAG发送的GRE Tunnel Setup Accept报文，该GRE Tunnel Setup Accept报文中包括用于请求该对应关系的请求信息；
其中，该HCPE向该HAG发送第一GRE Tunnel Notify报文，包括：
该HCPE根据该请求信息，向该HAG发送该第一GRE Tunnel Notify报文。
结合第二方面的第三种可能的实现方式，在第二方面的第五种可能的实现方式中，该HCPE向该HAG发送第一GRE Tunnel Notify报文，包括：
该HCPE接收该HAG发送的用于请求该对应关系的第二GRE Tunnel Notify报文；
该HCPE根据该第二GRE Tunnel Notify报文，向该HAG发送该第一 GRE Tunnel Notify报文。
因此，在本发明中，在GRE隧道绑定场景下，HAG能够根据GRE隧道的源IP地址与隧道标识之间的对应关系，灵活、高效地区分接收到的某个业务报文来自于哪条GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
第三方面提供了一种网络设备，该网络设备用于执行第一方面或第一方面的任一方面的可能实现方式中的方法。
具体地，该网络设备可以包括用于执行第一方面或第一方面的任一可能的实现方式中的方法的模块。
应理解，该网络设备对应于第一方面的方法中的混合接入网关HAG。
第四方面提供了一种网络设备，该网络设备用于执行第二方面或第二方面的任一方面的可能实现方式中的方法。
具体地，该网络设备可以包括用于执行第二方面或第二方面的任一可能的实现方式中的方法的模块。
应理解，该网络设备对应于第二方面的方法中的混合接入终端设备HCPE。
第五方面提供了一种确定GRE隧道标识的系统，该系统包括第三方面提供的网络设备和第四方面提供的网络设备。
还应理解，该系统包括第一方面或第二方面提供的确定GRE隧道标识的方法中的HAG和HCPE。
第六方面提供了一种网络设备，该网络设备包括存储器和处理器，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，并且对该存储器中存储的指令的执行使得该处理器执行第一方面或第一方面的任一方面的可能实现方式中的方法。
第七方面提供了一种网络设备，该网络设备包括存储器和处理器，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，并且对该存储器中存储的指令的执行使得该处理器执行第二方面或第二方面的任一方面的可能实现方式中的方法。
在本发明中，当绑定的该至少两条GRE隧道所在的接入网络类型不同时，本发明中提及的第一GRE隧道的隧道标识可以直接为该第一GRE隧道所在的接入网络类型(也可称之为隧道类型)。
在上述各个实现方式中，该至少两条GRE隧道中不同GRE隧道所在的接入网络类型不同，其中，该第一GRE隧道的隧道标识指示该第一GRE隧道所在的接入网络类型。
具体地，GRE隧道所在的接入网络类型包括固定接入网络和移动接入网络，其中，固定接入网络例如数字用户线路(Digital Subscriber Line，DSL)接入网络，移动接入网路例如为3G或LTE网络。
在本发明中，HAG通过获取绑定的至少两条GRE隧道的源IP地址与接入网络类型的对应关系，在接收到某个业务报文时，能够根据该对应关系灵活地确定承载该报文的GRE隧道所在的接入网络类型，从而，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商的迫切需求。
在上述各个实现方式中，混合接入终端设备(Hybrid Customer Premises Equipment，HCPE)与混合接入网关(Hybrid Access Gateway，HAG)为混合接入隧道两端的设备，其中HCPE为客户侧的接入设备，HCPE包括多了接入网接口，通过不同的接入网接口与HAG建立不同接入网的GRE Tunnel。HAG为供应商网络侧的接入设备。
在上述各个实现方式中，该至少两条GRE隧道绑定指的是，在该至少两条GRE隧道上可以同时传输同一业务的报文。例如图1所示的，HCPE与HAG之间建立的基于接入网络DSL的第一GRE隧道和基于LTE的第二GRE隧道绑定，HCPE可以利用这两条GRE隧道向HAG传输同一业务的报文。
在上述某些实现方式中，GRE控制报文的格式如图4(a)所示，该GRE控制报文中包括属性类型(Attr Type)字段，赋值为属性类型55(Attr Type55)，用于表示对GRE隧道的源IP地址与隧道标识之间的对应关系的学习。该GRE控制报文的属性值(Attribute Value)字段包括：隧道标识(Tunnel ID)字段、隧道源IP地址(Tunnel Source IP Address)字段和传输协议(Delivery Protl)字段。即该GRE控制报文中包括用于指示GRE隧道的源IP地址与GRE隧道的隧道标识之间的对应关系的信息。
应理解，该GRE控制报文的消息类型(MsgType)字段用于指示GRE控制报文的消息类型，MsgType字段赋不同的值表示不同类型的GRE控制报文，如表1所示，例如当MsgType字段赋值为1时，表示该GRE控制报 文为GRE Tunnel Setup Request报文；当MsgType字段赋值为2时，表示该GRE控制报文为GRE Tunnel Setup Accept报文；当MsgType字段赋值为6时，表示该GRE控制报文为GRE Tunnel Notify报文。
在上述某些实现方式中，HCPE向HAG发送的GRE Tunnel Setup Request报文的格式如图4(b)所示。
在上述某些实现方式中，HCPE向HAG发送的GRE Tunnel Notify报文的格式如图4(c)所示。
基于本发明上述技术方案，在GRE隧道绑定场景下，HAG能够根据GRE隧道的源IP地址与隧道标识之间的对应关系，灵活、高效地区分接收到的某个业务报文来自于哪条GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1示出了本发明实施例的应用场景的示意图。
图2示出了根据本发明实施例提供的确定GRE隧道标识的方法的示意性流程图。
图3示出了根据本发明实施例提供的确定GRE隧道标识的方法的另一示意性流程图。
图4(a)，图4(b)和图4(c)示出了根据本发明实施例提供的GRE控制报文的示意图。
图5示出了根据本发明实施例提供的确定GRE隧道标识的方法的再一示意性流程图。
图6示出了根据本发明实施例提供的确定GRE隧道标识的方法的再一示意性流程图。
图7示出了根据本发明实施例提供的确定GRE隧道标识的方法的再一示意性流程图。
图8示出了根据本发明实施例提供的确定GRE隧道标识的方法的再一 示意性流程图。
图9示出了根据本发明实施例提供的确定GRE隧道标识的方法的再一示意性流程图。
图10示出了根据本发明实施例提供的网络设备的示意性框图。
图11示出了根据本发明实施例提供的确定GRE隧道标识的系统的示意性框图。
图12示出了根据本发明另一实施例提供的网络设备的示意性框图。
图13示出了根据本发明另一实施例提供的网络设备的另一示意性框图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
为了便于理解和描述本发明实施例提出的方法，首先结合图1描述本发明实施例提出的确定GRE隧道标识的方法的应用场景。
如图1所示，混合接入终端设备HCPE包括DSL接口和LTE接口，HCPE通过DSL接口与混合接入网关HAG建立DSL接入网络的GRE tunnel(记为第一GRE tunnel)，通过LTE接口与HAG建立LTE接入网络的GRE tunnel(记为第二GRE tunnel)，该第一GRE tunnel与第二GRE tunnel进行绑定(bonding)形成一个混合接入隧道。
应理解，通用路由封装(Generation Routing Encapsulation，简称为“GRE”)协议为一种封装协议，它提供了一种协议的报文封装在另一种协议报文中的机制，使得报文能够在异种网络中传输。具体地，GRE是对某些网络协议(如IP、IPx、Apple Talk等)的数据报文进行封装，使这些被封装的数据报文能够在另一个网络层协议中传输。
还应理解，HCPE上的同一业务的业务报文可以分别通过第一GRE tunnel和第二GRE tunnel传输到HAG，假设DSL接入网络(即第一GRE tunnel)的带宽为1G，LTE接入网络(即第二GRE tunnel)的带宽为1G，这两个GRE tunnel bonding之后可为用户提供2G的接入网络带宽，例如HCPE通过该混合接入隧道向HAG发送一个业务的业务报文，当第一GRE  tunnel的传输量超过该第一GRE tunnel的带宽时，超出的传输量迁移到第二GRE tunnel上进行传输，因此，相比于单独的每个GRE tunnel，第一GRE tunnel和第二GRE tunnel绑定之后形成的混合接入隧道能够为用户提高较大的接入网带宽，也能够提高报文传输的可靠性。
还应理解，在如图1所示的GRE tunnel bonding的场景中，第一GRE tunnel和第二GRE tunnel在HCPE端和HAG端是粘结在一起的，HCPE向用户隐藏了第一GRE tunnel和第二GRE tunnel，换句话说，在用户看来，是利用HCPE与HAG之间的单独一条接入网连接隧道在传输数据。
在图1所示的场景中，当第一GRE tunnel和第二GRE tunnel进行绑定后，在HAG上无法区分从HCPE接收到的具体某个业务报文来自哪种接入网络的GRE tunnel，而目前运营商对此提出了迫切的需求。
针对上述技术问题，本发明实施例提出一种确定GRE隧道标识的方法、设备和系统，在GRE隧道绑定(GRE tunnel bonding)的场景下，能够使得HAG自主地、灵活地区分接收到某个业务报文来自于绑定的GRE隧道中的哪条GRE隧道。
图2示出了根据本发明实施例提供的确定通用路由封装GRE隧道标识的方法100，该方法应用于混合接入网关HAG与混合接入终端设备HCPE之间有至少两条GRE隧道的场景，且该至少两条GRE隧道绑定，该方法100包括：
S110，该HAG接收该HCPE经由第一GRE隧道发送的业务报文，该业务报文中包括承载该业务报文的该第一GRE隧道的源IP地址，其中，该第一GRE隧道为该至少两条GRE隧道中的一条GRE隧道；
S120，该HAG根据承载该业务报文的该第一GRE隧道的源IP地址查找对应关系表，确定承载该业务报文的该第一GRE隧道的隧道标识，该对应关系表包括该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系，其中，该第一GRE隧道的源IP地址为该第一GRE隧道在该HCPE上的隧道端口的IP地址，该第一GRE隧道的隧道标识用于唯一指示该第一GRE隧道。
因此，在本发明实施例中，在GRE隧道绑定场景下，HAG能够根据GRE隧道的源IP地址与隧道标识之间的对应关系，灵活、高效地区分接收到的某个业务报文来自于哪条GRE隧道，从而能够满足当前运营商对GRE 隧道操作、管理和维护(Operation Administration and Maintenance，简称为“OAM”)的需求。
应理解，GRE隧道是由该隧道源IP地址与隧道目的IP地址确定，GRE隧道的方向是从HCPE到HAG，其中，该条GRE隧道的源IP地址指的是该条GRE隧道在HCPE上的隧道端口的IP地址，目的IP地址指的是该条GRE隧道在HAG上的隧道端口的IP地址。具体地，如图1所示，第一GRE隧道的源IP地址指的是HCPE的DSL接口的IP地址，第一GRE隧道的目的IP地址指的是该第一GRE隧道在HAG上的隧道端口的IP地址；第二GRE隧道的源IP地址指的是HCPE的LTE接口的IP地址，第二GRE隧道的目的IP地址指的是该第二GRE隧道在HAG上的隧道端口的IP地址。应理解，第一GRE隧道的目的IP地址与第二GRE隧道的目的IP地址可能不同，也可能相同，本发明实施例对此不作限定。
具体地，HCPE具有至少两个接入网接口，该至少两个接入网接口与该至少两条GRE隧道一一对应，HAG与HCPE可以通过以下流程建立该至少两条GRE隧道：
1)HCPE利用至少两个接入网接口中的第一接口，向HAG发送用于请求第一GRE隧道的GRE Tunnel Setup Request报文；
2)HAG向HCPE发送GRE Tunnel Setup Accept报文，以响应GRE Tunnel Setup Request报文，这样，HCPE与HAG完成第一GRE隧道的建立。
3)HCPE在该至少两个接入网接口中除第一接口之外的其他每个接口依次执行上述步骤1)和2)，从而在HCPE与HAG之间完成至少两条GRE隧道的建立。
应理解，该至少两条GRE隧道所在的接入网络类型可以互不相同，也可以部分相同，本发明实施例对此不做限定。例如，该至少两条GRE隧道包括基于DSL接入网络的第一GRE隧道、基于LTE接入网络的第二GRE隧道，和基于3G接入网络的第三GRE隧道。或者，该至少两条GRE隧道包括基于DSL接入网络的第一GRE隧道、基于LTE接入网络的第二GRE隧道，以及基于DSL接入网络的第三GRE隧道。
还应理解，在本发明实施例中，该至少两条GRE隧道绑定指的是，在该至少两条GRE隧道上可以同时传输同一业务的报文。如图1所示，HCPE与HAG之间建立的基于接入网络DSL和LTE的两条GRE隧道绑定在一起， HCPE可以利用这两条GRE隧道同时向HAG传输同一业务的报文。
在本发明实施例中，当绑定的该至少两条GRE隧道所在的接入网络类型不同时，本发明中提及的GRE隧道的隧道标识可以直接为GRE隧道所在的接入网络类型(也可称之为隧道类型)。
可选地，在本发明实施例中，该至少两条GRE隧道中不同GRE隧道所在的接入网络类型不同，其中，该第一GRE隧道的隧道标识指示该第一GRE隧道所在的接入网络类型。
具体地，例如在图1所示场景中，第一GRE隧道的隧道标识例如为DSL，第二GRE隧道的隧道标识例如为LTE。
应理解，图1仅为示例而非限定，GRE隧道所在的接入网络类型包括固定接入网络和移动接入网络，其中，固定接入网络例如数字用户线路(Digital Subscriber Line，DSL)接入网络，移动接入网路例如为3G网络、LTE网络或其他移动接入网络。
在本发明实施例中，HAG通过获取绑定的至少两条GRE隧道的源IP地址与接入网络类型的对应关系，在接收到某个业务报文时，能够根据该对应关系灵活地确定承载该报文的GRE隧道所在的接入网络类型，从而，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商的迫切需求。
具体地，HAG可以从上层设备(例如网管设备或者控制器)获取该至少两条GRE隧道的源IP地址与隧道标识之间的对应关系，例如，HCPE实时向上层设备上报当前与HAG建立的各条GRE隧道的源IP地址和隧道标识之间的对应关系，然后该上层设备向该HAG通知该对应关系；HAG也可以直接从HCPE处获取该对应关系。
可选地，如图3所示，在本发明实施例中，在S110该HAG接收该HCPE经由该第一GRE隧道发送的业务报文之前，该方法100还包括：
S130，该HAG接收该HCPE发送的GRE控制报文，该GRE控制报文包括用于指示该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系的信息；
S140，该HAG根据该GRE控制报文，获取该对应关系。
应理解，GRE控制报文是用于GRE隧道的建立、绑定、拆除和OAM管理等操作的报文。
例如，可以在该GRE控制报文的属性(Attribute)字段携带GRE隧道的源IP地址与隧道标识之间的对应关系。
具体地，图4(a)示出了本发明实施例中GRE控制报文的报文格式的示意图，该GRE控制报文包括消息类型(MsgType)字段，保留位1(Rsvd1)字段和属性(Attributes)字段。其中，MsgType字段用于指示GRE控制报文的消息类型，MsgType字段赋不同的值表示不同消息类型的GRE控制报文，如表1所示，例如当MsgType字段赋值为1时，表示该GRE控制报文为GRE Tunnel Setup Request报文；当MsgType字段赋值为2时，表示该GRE控制报文为GRE Tunnel Setup Accept报文；当MsgType字段赋值为6时，表示该GRE控制报文为GRE Tunnel Notify报文，其他赋值的意义参见表1所示信息，这里不再详述。保留位1(Rsvd1)字段可以赋值为0。属性(Attributes)字段指示GRE控制报文的属性，如图4(a)中所示，该属性(Attribute)字段具体地包括属性类型(Attribute Type)字段、属性长度(Attribute Length)字段、属性值(Attribute Value)字段，其中，Attribute Type指示GRE控制报文的属性的类型，在本发明实施例中，Attribute Type赋值为属性类型55(Attri Type55)，表示GRE控制报文的Attribute类型为隧道源IP地址与隧道标识之间对应关系的学习，这个属性类型Attri Type55也可称之为Learning Attribute。属性长度(Attribute Length)字段表示属性值(Attribute Value)的长度。在本发明实施例中，属性值(Attribute Value)字段包括隧道标识(Tunnel ID)字段、传输协议(Delivery Prot1)字段和隧道源IP地址(Tunnel Source IP Address)字段。隧道标识(Tunnel ID)通过赋不同的值来指示不同的GRE隧道。传输协议(Delivery Prot1)表示GRE隧道的传输协议，例如，Delivery Prot1赋值为0时，表示传输协议为IPv4；Delivery Prot1赋值为1时，表示传输协议为IPv6。隧道源IP地址(Tunnel Source IP Address)字段表示GRE隧道的隧道源IP地址，当传输协议为IPv4时，Tunnel Source IP Address字段为4bytes，当传输协议为IPv6时，Tunnel Source IP Address字段为16bytes。
应理解，如图4(a)所示，在GRE控制报文的报文头中，C指示Checksum Present，赋值为0；k指示Key Present，赋值为1；S指示Sequence Number Present，赋值为0；版本号(Ver)指示GRE控制报文的协议版本号；协议类型(Protocol Type)用于指示GRE控制报文的协议类型；关键字(key) 字段作为安全参数，用作GRE隧道在HAG上的多路复用分配器，“key”字段由HAG赋值，并告知给HCPE。
在本发明实施例中，当HCPE与HAG之间建立的至少两条GRE隧道中不同GRE隧道所在的接入网类型互不相同时，每条GRE隧道的隧道标识例如直接为该每条GRE隧道所在的接入网类型(也可称之为隧道类型)，图4(a)中所示GRE控制报文的隧道标识(Tunnel ID)字段也可以为隧道类型(Tunnel Type)字段，本发明实施例对此不做限定。
应理解，当图4(a)所示的GRE控制报文中的MsgType赋值为1时，如图4(b)所示，表示该GRE控制报文为GRE Tunnel Setup Request报文，且该GRE Tunnel Setup Request中携带隧道标识与隧道源IP地址之间的对应关系。当图4(a)所示的GRE控制报文中的MsgType赋值为6时，如图4(c)所示，表示该GRE控制报文为GRE Tunnel Notify报文，且该GRE Tunnel Notify中携带隧道标识与隧道源IP地址之间的对应关系。
表1
MsgType GRE控制报文类型
1 GRE Tunnel Setup Request
2 GRE Tunnel Setup Accept
3 GRE Tunnel Setup Deny
4 GRE Tunnel Hello
5 GRE Tunnel Tear Down
6 GRE Tunnel Notify
0,7-15 Reserved
在本发明实施例中，HCPE可以基于现有的GRE控制报文向HAG通知GRE隧道的源IP地址与隧道标识的对应关系，使得HAG可以根据该对应关系，灵活地区分接收到某个业务报文来自于哪条GRE隧道，与现有流程相比，并没有额外的信令开销。
在S130中，具体地，HCPE可以在建立GRE过程中通过GRE Tunnel Setup Request报文向HAG发送该对应关系，也可以在建立GRE隧道之后，GRE Tunnel Setup Request报文向HAG发送该对应关系。
可选地，在本发明实施例中，S130该HAG接收该HCPE发送的GRE 控制报文，包括：
在建立该第一GRE隧道的过程中，该HAG接收该HCPE发送的GRE Tunnel Setup Request报文，该GRE Tunnel Setup Request报文的属性字段中包括用于指示该对应关系的信息。
具体地，图5示出了本发明实施例提供的HCPE利用GRE Tunnel Setup Request报文向HAG告知GRE隧道的源IP地址与隧道标识之间的对应关系的方案的示意性流程图。如图5所示，在S21中，HCPE向HAG发送GRE Tunnel Setup Request报文，用于请求与HAG建立第一GRE tunnel，该GRE Tunnel Setup Request报文中包括第一GRE tunnel的隧道源IP地址与隧道标识的对应关系，具体地，该GRE Tunnel Setup Request报文的格式如图4(b)所示。在S22中，HAG根据GRE Tunnel Setup Request获取该第一GRE tunnel的隧道源IP地址与隧道标识之间的对应关系；在S23中，HAG向HCPE发送GRE Tunnel Setup Accept，以响应建立该第一GRE tunnel。在S24中，HCPE利用建立的第一GRE tunnel向HAG发送业务报文，例如“GRE Tunnel Hello”，该业务报文中携带有承载该业务报文的GRE tunnel的源IP地址；在S25中，HAG根据接收到的业务报文，获取承载该业务报文的GRE Tunnel的源IP地址，并根据在S22中获取的对应关系，获取承载该业务报文的GRE Tunnel的隧道标识，从而获知该业务报文来自于该第一GRE隧道中的哪条。
应理解，上述步骤S21至S25是针对至少两条GRE隧道的各条GRE隧道分别进行的，例如，以图1所示场景为例，HCPE通过DSL接口向HAG发送携带有第一GRE隧道的源IP地址和隧道标识(例如为第一GRE隧道所在的接入网类型DSL)的GRE Tunnel Setup Request报文，用于请求与HAG建立基于DSL的第一GRE隧道，HAG接收到该GRE Tunnel Setup Request报文后，就获得了第一GRE隧道的源IP地址和隧道标识之间的对应关系，然后，HAG向HCPE发送GRE Tunnel Setup Accept报文，以响应建立该第一GRE隧道。HCPE通过LTE接口向HAG发送携带有第二GRE隧道的源IP地址和隧道标识(例如为第二GRE隧道所在的接入网类型LTE)的GRE Tunnel Setup Request报文，用于请求与HAG建立基于LTE的第二GRE隧道，HAG接收到该GRE Tunnel Setup Request报文后，就获得了第二GRE隧道的源IP地址和隧道标识之间对应关系，然后，HAG向HCPE发送GRE Tunnel Setup Accept报文，以响应建立该第二GRE隧道。HCPE利用绑定的 该第一GRE隧道和第二GRE隧道向HAG发送业务报文。HAG根据接收到业务报文携带的隧道源IP地址，以及获取的对应关系，确定该接收到的业务报文来自于第一GRE隧道和第二GRE隧道中的哪条GRE隧道。具体地，例如HAG在S22中获取的对应关系为IP Address 1—DSL，IP Address2—LTE。假设在S24中，HAG接收到业务报文的承载隧道的源IP地址为IP Address 2，则HAG可以确定承载该业务报文的GRE隧道为基于接入网LTE的第二GRE隧道。
因此，在本发明实施例中，HCPE可以基于现有的GRE控制报文向HAG通知绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，使得HAG可以根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道，与现有流程相比，并没有额外的信令开销。
可选地，在本发明实施例中，S130该HAG接收该HCPE发送的GRE控制报文，包括：
在建立该第一GRE隧道之后，该HAG接收该HCPE发送的第一GRE Tunnel Notify报文，该第一GRE Tunnel Notify报文的属性字段中包括用于指示该对应关系的信息。
具体地，图6示出了本发明实施例提供的HCPE利用GRE Tunnel Notify报文主动向HAG告知GRE隧道的源IP地址与隧道标识之间的对应关系的方案的示意性流程图。在S31中，HCPE向HAG发送GRE Tunnel Setup Request，用于请求与HAG建立第一GRE tunnel，该GRE Tunnel Setup Request中不携带隧道源IP地址和隧道标识的对应关系。在S32中，HAG向HCPE发送GRE Tunnel Setup Accept报文，以响应建立该第一GRE tunnel。在S33中，HCPE通过该第一GRE Tunnel向HAG发送GRE Tunnel Notify报文，该GRE Tunnel Notify报文中携带该第一GRE tunnel的隧道源IP地址与隧道标识的对应关系，具体地，该GRE Tunnel Notify报文格式为图4(c)所示；在S34中，HAG通过接收到的GRE Tunnel Notify报文学习到隧道类型和隧道源IP地址之间的对应关系；在S35中，HAG向HCPE发送GRE Tunnel Setup Accept报文作为响应，并更新隧道信息，即保存学习到该第一GRE tunnel的隧道源IP地址与隧道标识的对应关系；在S36中，HCPE利用建立的第一GRE tunnel向HAG发送业务报文，例如“GRE Tunnel Hello”，该业务报文中 携带有承载该业务报文的GRE tunnel的源IP地址；在S37中，HAG根据接收到的业务报文，获取承载该业务报文的GRE Tunnel的源IP地址，并根据在S34中获取的对应关系，获取承载该业务报文的GRE Tunnel的隧道标识，从而获知该业务报文来自于该至少两条GRE隧道中的哪条。
应理解，上述步骤S31至S37是针对至少两条GRE隧道的各条GRE隧道分别进行的。
因此，在本发明实施例中，HCPE可以基于现有的GRE控制报文向HAG通知绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，使得HAG可以根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道，与现有流程相比，并没有额外的信令开销。
上文结合图5和图6描述了HCPE告知HAG至少两条GRE隧道的源IP地址与隧道标识之间的对应关系。可选地，也可以是在HAG向HCPE发送请求消息之后告知，本发明实施例对此不作限定。
可选地，在本发明实施例中，该方法300还包括：
在建立该第一GRE隧道的过程中，该HAG向该HCPE发送GRE Tunnel Setup Accept报文，该GRE Tunnel Setup Accept报文中包括用于请求该对应关系的请求信息；
其中，该HAG接收该HCPE发送的第一GRE Tunnel Notify报文，包括：
该HAG接收该HCPE根据该请求信息发送的该第一GRE Tunnel Notify报文。
具体地，图7示出了本发明实施例提供的HAG利用GRE Tunnel Setup Accept报文向HCPE请求GRE隧道的源IP地址与隧道标识之间的对应关系的方案的示意性流程图。在S41中，HCPE向HAG发送GRE Tunnel Setup Request，用于请求与HAG建立第一GRE tunnel，该GRE Tunnel Setup Request中不携带隧道源IP地址和隧道标识的对应关系。在S42中，HAG向HCPE发送GRE Tunnel Setup Accept报文，以响应建立该第一GRE tunnel，并且该GRE Tunnel Setup Accept报文还用于请求该第一GRE隧道的源IP地址与隧道标识之间的对应关系，可选地，该GRE Tunnel Setup Accept报文中携带该第一GRE隧道的源IP地址。具体地，GRE Tunnel Setup Accept报文的格式可以为：将图4(a)中所示的“MsgType”赋值为“2”，Tunnel Source IP Address 字段中携带GRE隧道源IP地址，Tunnel ID字段为空。S43中，HCPE通过该第一GRE Tunnel向HAG发送GRE Tunnel Notify报文，该GRE Tunnel Notify报文中携带该第一GRE tunnel的隧道源IP地址与隧道标识的对应关系，具体地，该GRE Tunnel Notify报文格式为图4(c)所示。在S44中，HAG通过接收到的GRE Tunnel Notify报文学习到隧道类型和隧道源IP地址之间的对应关系；在S45中，HAG向HCPE发送GRE Tunnel Setup Accept报文作为响应，并更新隧道信息，即保存学习到该第一GRE tunnel的隧道源IP地址与隧道标识的对应关系；在S46中，HCPE利用建立的第一GRE tunnel向HAG发送业务报文，例如“GRE Tunnel Hello”，该业务报文中携带有承载该业务报文的GRE tunnel的源IP地址。在S47中，HAG根据接收到的业务报文，获取承载该业务报文的GRE Tunnel的源IP地址，并根据在S44中获取的对应关系，获取承载该业务报文的GRE Tunnel的隧道标识，从而获知该业务报文来自于该至少两条GRE隧道中的哪条。
应理解，上述步骤S41至S47是针对至少两条GRE隧道的各条GRE隧道分别进行的。
因此，在本发明实施例中，HCPE可以基于现有的GRE控制报文向HAG通知绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，使得HAG可以根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道，与现有流程相比，并没有额外的信令开销。
可选地，在本发明实施例中，该HAG接收该HCPE发送的第一GRE Tunnel Notify报文，包括：
该HAG向该HCPE发送用于请求该对应关系的第二GRE Tunnel Notify报文；
该HAG接收该HCPE根据该第二GRE Tunnel Notify报文发送的该第一GRE Tunnel Notify报文。
具体地，图8示出了本发明实施例提供的HAG利用GRE Tunnel Notify报文向HCPE请求GRE隧道的源IP地址与隧道类型之间的对应关系的方案的示意性流程图。在S51中，HCPE向HAG发送GRE Tunnel Setup Request，用于请求与HAG建立第一GRE tunnel，该GRE Tunnel Setup Request中不携带隧道源IP地址和隧道标识的对应关系。在S52中，HAG向HCPE发送 GRE Tunnel Setup Accept报文，以响应建立该第一GRE tunnel。在S53中，HAG向HCPE发送用于请求该第一GRE隧道的源IP地址与隧道标识之间的对应关系的GRE Tunnel Notify报文，可选地，该GRE Tunnel Notify报文中携带该第一GRE隧道的源IP地址，具体地，GRE Tunnel Notify报文的格式如图4(c)所示，即该GRE Tunnel Notify报文的Attribute Type为55，Tunnel Source IP Address字段中携带GRE隧道的源IP地址，但是Tunnel ID字段为空；在S54中，HCPE通过该第一GRE Tunnel向HAG发送GRE Tunnel Notify报文，该GRE Tunnel Notify报文中携带该第一GRE tunnel的隧道源IP地址与隧道标识的对应关系，具体地，该GRE Tunnel Notify报文格式为图4(c)所示，Attribute Type为55，Tunnel Source IP Address字段中携带GRE隧道的源IP地址，Tunnel ID字段中携带GRE隧道的隧道类型。在S55中，HAG通过接收到的GRE Tunnel Notify报文学习到隧道类型和隧道源IP地址之间的对应关系。在S56中，HAG向HCPE发送GRE Tunnel Setup Accept报文作为响应，并更新隧道信息，即保存学习到的对应关系；在S57中，HCPE利用建立的第一GRE tunnel向HAG发送业务报文，例如“GRE Tunnel Hello”，该业务报文中携带有承载该业务报文的GRE tunnel的源IP地址。在S58中，HAG根据接收到的业务报文，获取承载该业务报文的GRE Tunnel的源IP地址，并根据在S55中获取的对应关系，获取承载该业务报文的GRE Tunnel的隧道标识，从而获知该业务报文来自于该至少两条GRE隧道中的哪条。
应理解，上述步骤S51至S58是针对至少两条GRE隧道的各条GRE隧道分别进行的。
因此，在本发明实施例中，HCPE可以基于现有的GRE控制报文向HAG通知绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，使得HAG可以根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道，与现有流程相比，并没有额外的信令开销。
在本发明实施例提供的方法中，HAG通过获取绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，能够根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道。因此，本发明提供的方法，在GRE隧道绑定场景下，能够灵活、高效地区分出接 收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
还应理解，GRE控制报文Attribute Type除了图4所示的Attribute Type 55之外，还有其他丰富的Attributes Type类型，以完成GRE控制平面的各项操作，此为现有技术，本文不作详述。
图9示出了根据本发明实施例提供的确定GRE隧道标识的方法200的示意性流程图，是从HCPE的角度描述本方案，该方法应用于混合接入网关HAG与混合接入终端设备HCPE之间有至少两条GRE隧道的场景，且该至少两条GRE隧道绑定，如图9所示，该方法200包括：
S210，该HCPE确定第一GRE隧道，该第一GRE隧道为该至少两条GRE隧道中的一条GRE隧道；
S220，该HCPE经由该第一GRE隧道向该HAG发送业务报文，该业务报文中包括承载该业务报文的该第一GRE隧道的源IP地址，以便于该HAG根据承载该业务报文的该第一GRE隧道的源IP地址查找对应关系表，确定承载该业务报文的该第一GRE隧道的隧道标识，该对应关系表包括该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系，其中，该第一GRE隧道的源IP地址为该第一GRE隧道在该HCPE上的隧道端口的IP地址，该第一GRE隧道的隧道标识用于唯一指示该第一GRE隧道。
因此，在本发明中，在GRE隧道绑定场景下，HAG能够根据GRE隧道的源IP地址与隧道标识之间的对应关系，灵活、高效地区分接收到的某个业务报文来自于哪条GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
在本发明实施例中，当绑定的该至少两条GRE隧道所在的接入网络类型不同时，本发明中提及的第一GRE隧道的隧道标识可以直接为该第一GRE隧道所在的接入网络类型(也可称之为隧道类型)。
可选地，在本发明实施例中，该至少两条GRE隧道中不同GRE隧道所在的接入网络类型不同，其中，该第一GRE隧道的隧道标识指示该第一GRE隧道所在的接入网络类型。
具体地，例如在图1所示场景中，第一GRE隧道的隧道标识例如为DSL，第二GRE隧道的隧道标识例如为LTE。
应理解，图1仅为示例而非限定，GRE隧道所在的接入网络类型包括固 定接入网络和移动接入网络，其中，固定接入网络例如数字用户线路(Digital Subscriber Line，DSL)接入网络，移动接入网路例如为3G网络、LTE网络或其他移动接入网络。
在本发明实施例中，HAG通过获取绑定的至少两条GRE隧道的源IP地址与接入网络类型的对应关系，在接收到某个业务报文时，能够根据该对应关系灵活地确定承载该报文的GRE隧道所在的接入网络类型，从而，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商的迫切需求。
可选地，在本发明实施例中，在S220该HCPE经由该第一GRE隧道向该HAG发送业务报文之前，该方法200还包括：
S230，该HCPE向该HAG发送GRE控制报文，该GRE控制报文包括用于指示该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系的信息。
在本发明中，HCPE可以基于现有的GRE控制报文向HAG通知GRE隧道的源IP地址与隧道标识的对应关系，使得HAG可以根据该对应关系，灵活地区分接收到某个业务报文来自于哪条GRE隧道，与现有流程相比，并没有额外的信令开销。
在本发明中，HCPE通过向HAG通知绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，使得HAG能够根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道。因此，本发明提供的方法，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
可选地，在本发明实施例中，S230该HCPE向该HAG发送GRE控制报文，包括：
在建立该第一GRE隧道的过程中，该HCPE向该HAG发送GRE Tunnel Setup Request报文，该GRE Tunnel Setup Request报文的属性字段中包括用于指示该对应关系的信息。
具体地，详见上文结合图5的描述，这里不再赘述。
可选地，在本发明实施例中，S230该HCPE向该HAG发送GRE控制报文，包括：
在建立该第一GRE隧道之后，该HCPE向该HAG发送第一GRE Tunnel Notify报文，该第一GRE Tunnel Notify报文的属性字段中包括用于指示该对应关系的信息。
具体地，详见上文结合图6的描述，这里不再赘述。
可选地，在本发明实施例中，该方法200还包括：
在建立该第一GRE隧道的过程中，该HCPE接收该HAG发送的GRE Tunnel Setup Accept报文，该GRE Tunnel Setup Accept报文中包括用于请求该对应关系的请求信息；
其中，该HCPE向该HAG发送第一GRE Tunnel Notify报文，包括：
该HCPE根据该请求信息，向该HAG发送该第一GRE Tunnel Notify报文。
具体地，详见上文结合图7的描述，这里不再赘述。
可选地，在本发明实施例中，该HCPE向该HAG发送第一GRE Tunnel Notify报文，包括：
该HCPE接收该HAG发送的用于请求该对应关系的第二GRE Tunnel Notify报文；
该HCPE根据该第二GRE Tunnel Notify报文，向该HAG发送该第一GRE Tunnel Notify报文。
具体地，详见上文结合图8的描述，这里不再赘述。
因此，在本发明实施例中，HCPE可以基于现有的GRE控制报文向HAG通知绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，使得HAG可以根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道，与现有流程相比，并没有额外的信令开销。
因此，在本发明实施例中，在GRE隧道绑定场景下，HAG能够根据GRE隧道的源IP地址与隧道标识之间的对应关系，灵活、高效地区分接收到的某个业务报文来自于哪条GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
图10示出了根据本发明实施例提供的网络设备300的示意性框图，该网络设备300与混合接入终端设备HCPE之间有至少两条GRE隧道的场景，且该至少两条GRE隧道绑定，该网络设备300包括：
接收模块310，用于接收该HCPE经由第一GRE隧道发送的业务报文，该业务报文中包括承载该业务报文的该第一GRE隧道的源IP地址，其中，该第一GRE隧道为该至少两条GRE隧道中的一条GRE隧道；
确定模块320，用于根据承载该接收模块接收的该业务报文的该第一GRE隧道的源IP地址查找对应关系表，确定承载该业务报文的该第一GRE隧道的隧道标识，该对应关系表包括该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系，其中，该第一GRE隧道的源IP地址为该第一GRE隧道在该HCPE上的隧道端口的IP地址，该第一GRE隧道的隧道标识用于唯一指示该第一GRE隧道。
应理解，根据本发明实施例的网络设备300可对应于本发明实施例的确定GRE隧道标识的方法中的HAG。
因此，在本发明实施例中，在GRE隧道绑定场景下，HAG能够根据GRE隧道的源IP地址与隧道标识之间的对应关系，灵活、高效地区分接收到的某个业务报文来自于哪条GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
可选地，在本发明实施例中，该接收模块310还用于，接收该HCPE经由该第一GRE隧道发送的业务报文之前，接收该HCPE发送的GRE控制报文，该GRE控制报文包括用于指示该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系的信息；
该网络设备300还包括：
获取模块330，用于根据该接收模块接收的该GRE控制报文，获取该对应关系。
因此，在本发明实施例中，HAG通过获取绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，能够根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道。因此，本发明提供的方法，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
可选地，在本发明实施例中，该接收模块310用于，在建立该第一GRE隧道的过程中，接收该HCPE发送的GRE Tunnel Setup Request报文，该GRE Tunnel Setup Request报文的属性字段中包括用于指示该对应关系的信息。
可选地，在本发明实施例中，该接收模块310用于，在建立该第一GRE隧道之后，接收该HCPE发送的第一GRE Tunnel Notify报文，该第一GRE Tunnel Notify报文的属性字段中包括用于指示该对应关系的信息。
可选地，在本发明实施例中，该网络设备300还包括：
发送模块340，用于在建立该第一GRE隧道的过程中，向该HCPE发送GRE Tunnel Setup Accept报文，该GRE Tunnel Setup Accept报文中包括用于请求该对应关系的请求信息；
其中，该接收模块310用于，接收该HCPE根据该请求信息发送的该第一GRE Tunnel Notify报文。
可选地，在本发明实施例中，该接收模块310包括：
发送单元，用于向该HCPE发送用于请求该对应关系的第二GRE Tunnel Notify报文；
接收单元，用于接收该HCPE根据该发送单元发送的该第二GRE Tunnel Notify报文发送的该第一GRE Tunnel Notify报文。
可选地，在本发明实施例中，该至少两条GRE隧道中不同GRE隧道所在的接入网络类型不同，其中，该第一GRE隧道的隧道标识指示该第一GRE隧道所在的接入网络类型。
应理解，根据本发明实施例的网络设备300可对应于本发明实施例的确定GRE隧道标识的方法中的HAG，并且网络设备300中的各个模块的上述和其它操作和/或功能分别为了实现图1至图9中的各个方法的相应流程，为了简洁，在此不再赘述。
因此，在本发明实施例中，HAG通过获取绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，能够根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道。因此，本发明提供的方法，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
图10还示出了根据本发明实施例提供的网络设备400的示意性框图，该网络设备400与混合接入网关HAG之间有至少两条GRE隧道的场景，且该至少两条GRE隧道绑定，该网络设备400包括：
确定模块410，用于确定第一GRE隧道，该第一GRE隧道为该至少两 条GRE隧道中的一条GRE隧道；
发送模块420，用于经由该确定模块确定的该第一GRE隧道向该HAG发送业务报文，该业务报文中包括承载该业务报文的该第一GRE隧道的源IP地址，以便于该HAG根据承载该业务报文的该第一GRE隧道的源IP地址查找对应关系表，确定承载该业务报文的该第一GRE隧道的隧道标识，该对应关系表包括该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系，其中，该第一GRE隧道的源IP地址为该第一GRE隧道在该HCPE上的隧道端口的IP地址，该第一GRE隧道的隧道标识用于唯一指示该第一GRE隧道。
应理解，该网络设备400对应于本发明实施例提供的确定GRE隧道标识的方法中的HCPE。
因此，在本发明实施例中，在GRE隧道绑定场景下，HAG能够根据GRE隧道的源IP地址与隧道标识之间的对应关系，灵活、高效地区分接收到的某个业务报文来自于哪条GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
可选地，在本发明实施例中，该发送模块420还用于，在经由该第一GRE隧道向该HAG发送业务报文之前，向该HAG发送GRE控制报文，该GRE控制报文包括用于指示该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系的信息。
在本发明实施例中，HCPE通过向HAG通知绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，使得HAG能够根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道。因此，本发明提供的方法，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
可选地，在本发明实施例中，该发送模块420用于，在建立该第一GRE隧道的过程中，向该HAG发送GRE Tunnel Setup Request报文，该GRE Tunnel Setup Request报文的属性字段中包括用于指示该对应关系的信息。
可选地，在本发明实施例中，该发送模块420用于，在建立该第一GRE隧道之后，向该HAG发送第一GRE Tunnel Notify报文，该第一GRE Tunnel Notify报文的属性字段中包括用于指示该对应关系的信息。
可选地，在本发明实施例中，该网络设备400还包括：
接收模块430，用于在建立该第一GRE隧道的过程中，接收该HAG发送的GRE Tunnel Setup Accept报文，该GRE Tunnel Setup Accept报文中包括用于请求该对应关系的请求信息；
其中，该发送模块420用于根据该请求信息，向该HAG发送该第一GRE Tunnel Notify报文。
可选地，在本发明实施例中，该发送模块420包括：
接收单元，用于接收该HAG发送的用于请求该对应关系的第二GRE Tunnel Notify报文；
发送单元，用于根据该接收单元接收的该第二GRE Tunnel Notify报文，向该HAG发送该第一GRE Tunnel Notify报文。
可选地，在本发明实施例中，该至少两条GRE隧道中不同GRE隧道所在的接入网络类型不同，其中，该第一GRE隧道的隧道标识指示该第一GRE隧道所在的接入网络类型。
应理解，根据本发明实施例的网络设备400可对应于本发明实施例的确定GRE隧道标识的方法中的HCPE，并且网络设备400中的各个模块的上述和其它操作和/或功能分别为了实现图1至图9中的各个方法的相应流程，为了简洁，在此不再赘述。
在本发明实施例中，HCPE通过向HAG通知绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，使得HAG能够根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道。因此，本发明提供的方法，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
图11示出了本发明实施例提供的确定通用路由封装GRE隧道标识的系统500，该系统500包括根据本发明实施例提供的网络设备300，和根据本发明实施例提供的网络设备400。
应理解，该网络设备300对应于本发明实施例的确定GRE隧道标识的方法中的HAG，网络设备400对应于本发明实施例的确定GRE隧道标识的方法中的HCPE，并且系统500中的各个模块的上述和其它操作和/或功能分别为了实现图1至图9中的各个方法的相应流程，为了简洁，在此不再赘述。
因此，在本发明实施例中，在GRE隧道绑定场景下，HAG能够根据GRE隧道的源IP地址与隧道标识之间的对应关系，灵活、高效地区分接收到的某个业务报文来自于哪条GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
如图12所示，本发明实施例还提供了一种网络设备600，该网络设备600与混合接入终端设备HCPE之间有至少两条GRE隧道的场景，且该至少两条GRE隧道绑定。该网络设备600包括处理器610、存储器620、总线系统630、接收器640和发送器650。其中，处理器610、存储器620、接收器640和发送器650通过总线系统630相连，该存储器620用于存储指令，该处理器610用于执行该存储器620存储的指令，以控制接收器640接收信号，并控制发送器650发送信号。其中，接收器640用于，接收该HCPE经由第一GRE隧道发送的业务报文，该业务报文中包括承载该业务报文的该第一GRE隧道的源IP地址，其中，该第一GRE隧道为该至少两条GRE隧道中的一条GRE隧道；
处理器610用于，根据承载该业务报文的该第一GRE隧道的源IP地址查找对应关系表，确定承载该业务报文的该第一GRE隧道的隧道标识，该对应关系表包括该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系，其中，该第一GRE隧道的源IP地址为该第一GRE隧道在该HCPE上的隧道端口的IP地址，该第一GRE隧道的隧道标识用于唯一指示该第一GRE隧道。
应理解，根据本发明实施例的网络设备600可对应于本发明实施例的确定GRE隧道标识的方法中的HAG。
因此，在本发明实施例中，在GRE隧道绑定场景下，HAG能够根据GRE隧道的源IP地址与隧道标识之间的对应关系，灵活、高效地区分接收到的某个业务报文来自于哪条GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
可选地，在本发明实施例中，接收器640用于，在接收该HCPE经由该第一GRE隧道发送的业务报文之前，接收该HCPE发送的GRE控制报文，该GRE控制报文包括用于指示该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系的信息；
处理器610用于，根据该GRE控制报文，获取该对应关系。
因此，在本发明实施例中，HAG通过获取绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，能够根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道。因此，本发明提供的方法，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
可选地，在本发明实施例中，接收器640用于，在建立该第一GRE隧道的过程中，接收该HCPE发送的GRE Tunnel Setup Request报文，该GRE Tunnel Setup Request报文的属性字段中包括用于指示该对应关系的信息。
可选地，在本发明实施例中，接收器640用于，在建立该第一GRE隧道之后，接收该HCPE发送的第一GRE Tunnel Notify报文，该第一GRE Tunnel Notify报文的属性字段中包括用于指示该对应关系的信息。
可选地，在本发明实施例中，发送器650用于，在建立该第一GRE隧道的过程中，向该HCPE发送GRE Tunnel Setup Accept报文，该GRE Tunnel Setup Accept报文中包括用于请求该对应关系的请求信息；
接收器640用于，接收该HCPE根据该请求信息发送的该第一GRE Tunnel Notify报文。
可选地，在本发明实施例中，发送器650用于，向该HCPE发送用于请求该对应关系的第二GRE Tunnel Notify报文；
接收器640用于，接收该HCPE根据该第二GRE Tunnel Notify报文发送的该第一GRE Tunnel Notify报文。
可选地，在本发明实施例中，该至少两条GRE隧道中不同GRE隧道所在的接入网络类型不同，其中，该第一GRE隧道的隧道标识指示该第一GRE隧道所在的接入网络类型。
应理解，在本发明实施例中，该处理器610可以是中央处理单元(Central Processing Unit，简称为“CPU”)，该处理器610还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器620可以包括只读存储器和随机存取存储器，并向处理器610提供指令和数据。存储器620的一部分还可以包括非易失性随机存取存储器。 例如，存储器620还可以存储设备类型的信息。
该总线系统630除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图中将各种总线都标为总线系统630。
在实现过程中，上述方法的各步骤可以通过处理器610中的硬件的集成逻辑电路或者软件形式的指令完成。结合本发明实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器620，处理器610读取存储器620中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应理解，根据本发明实施例的网络设备600可对应于本发明实施例的确定GRE隧道标识的方法中的HAG，也对应于本发明实施例的网络设备300，并且网络设备600中的各个模块的上述和其它操作和/或功能分别为了实现图1至图9中的各个方法的相应流程，为了简洁，在此不再赘述。
因此，在本发明实施例中，HAG通过获取绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，能够根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道。因此，本发明提供的方法，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
如图13所示，本发明实施例还提出一种网络设备700，该网络设备700与混合接入网关HAG之间有至少两条GRE隧道的场景，且该至少两条GRE隧道绑定。该网络设备700包括处理器710、存储器720、总线系统730、接收器740和发送器750。其中，处理器710、存储器720、接收器740和发送器750通过总线系统730相连，该存储器720用于存储指令，该处理器710用于执行该存储器720存储的指令，以控制接收器740接收信号，并控制发送器750发送信号。其中，处理器710用于，确定第一GRE隧道，该第一GRE隧道为该至少两条GRE隧道中的一条GRE隧道；发送器750用于，经由该第一GRE隧道向该HAG发送业务报文，该业务报文中包括承载该业务报文的该第一GRE隧道的源IP地址，以便于该HAG根据承载 该业务报文的该第一GRE隧道的源IP地址查找对应关系表，确定承载该业务报文的该第一GRE隧道的隧道标识，该对应关系表包括该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系，其中，该第一GRE隧道的源IP地址为该第一GRE隧道在该HCPE上的隧道端口的IP地址，该第一GRE隧道的隧道标识用于唯一指示该第一GRE隧道。
应理解，该网络设备700对应于本发明实施例提供的确定GRE隧道标识的方法中的HCPE。
因此，在本发明实施例中，在GRE隧道绑定场景下，HAG能够根据GRE隧道的源IP地址与隧道标识之间的对应关系，灵活、高效地区分接收到的某个业务报文来自于哪条GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
可选地，在本发明实施例中，发送器750用于，在经由该第一GRE隧道向该HAG发送业务报文之前，向该HAG发送GRE控制报文，该GRE控制报文包括用于指示该第一GRE隧道的源IP地址与该第一GRE隧道的隧道标识之间的对应关系的信息。
在本发明实施例中，HCPE通过向HAG通知绑定的至少两条GRE隧道的源IP地址与隧道标识的对应关系，使得HAG能够根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道。因此，本发明提供的方法，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
可选地，在本发明实施例中，发送器750用于，在建立该第一GRE隧道的过程中，向该HAG发送GRE Tunnel Setup Request报文，该GRE Tunnel Setup Request报文的属性字段中包括用于指示该对应关系的信息。
可选地，在本发明实施例中，发送器750用于，在建立该第一GRE隧道之后，向该HAG发送第一GRE Tunnel Notify报文，该第一GRE Tunnel Notify报文的属性字段中包括用于指示该对应关系的信息。
可选地，在本发明实施例中，接收器740用于，在建立该第一GRE隧道的过程中，接收该HAG发送的GRE Tunnel Setup Accept报文，该GRE Tunnel Setup Accept报文中包括用于请求该对应关系的请求信息；
发送器750用于，根据该请求信息，向该HAG发送该第一GRE Tunnel  Notify报文。
可选地，在本发明实施例中，接收器740用于，接收该HAG发送的用于请求该对应关系的第二GRE Tunnel Notify报文；
发送器750用于，根据该第二GRE Tunnel Notify报文，向该HAG发送该第一GRE Tunnel Notify报文。
可选地，在本发明实施例中，该至少两条GRE隧道中不同GRE隧道所在的接入网络类型不同，其中，该第一GRE隧道的隧道标识指示该第一GRE隧道所在的接入网络类型。
应理解，在本发明实施例中，该处理器710可以是中央处理单元(Central Processing Unit，简称为“CPU”)，该处理器710还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器720可以包括只读存储器和随机存取存储器，并向处理器710提供指令和数据。存储器720的一部分还可以包括非易失性随机存取存储器。例如，存储器720还可以存储设备类型的信息。
该总线系统730除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图中将各种总线都标为总线系统730。
在实现过程中，上述方法的各步骤可以通过处理器710中的硬件的集成逻辑电路或者软件形式的指令完成。结合本发明实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器720，处理器710读取存储器720中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应理解，根据本发明实施例的网络设备700可对应于本发明实施例的确定GRE隧道标识的方法中的HCPE，也对应于根据本发明实施例的网络设备400，并且网络设备700中的各个模块的上述和其它操作和/或功能分别为了实现图1至图9中的各个方法的相应流程，为了简洁，在此不再赘述。
在本发明实施例中，HCPE通过向HAG通知绑定的至少两条GRE隧道 的源IP地址与隧道标识的对应关系，使得HAG能够根据该对应关系，灵活地区分接收到某个业务报文来自于该至少两条GRE隧道中的哪条GRE隧道。因此，本发明提供的方法，在GRE隧道绑定场景下，能够灵活、高效地区分出接收到的某个业务报文来自于哪个GRE隧道，从而能够满足当前运营商对GRE隧道进行OAM的需求。
还应理解，本文中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本发明实施例的范围。
应理解，在本发明的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一 个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (29)

  1. 一种确定通用路由封装GRE隧道标识的方法，其特征在于，所述方法应用于混合接入网关HAG与混合接入终端设备HCPE之间有至少两条GRE隧道的场景，且所述至少两条GRE隧道绑定，所述方法包括：
    所述HAG接收所述HCPE经由第一GRE隧道发送的业务报文，所述业务报文中包括承载所述业务报文的所述第一GRE隧道的源IP地址，其中，所述第一GRE隧道为所述至少两条GRE隧道中的一条GRE隧道；
    所述HAG根据承载所述业务报文的所述第一GRE隧道的源IP地址查找对应关系表，确定承载所述业务报文的所述第一GRE隧道的隧道标识，所述对应关系表包括所述第一GRE隧道的源IP地址与所述第一GRE隧道的隧道标识之间的对应关系，其中，所述第一GRE隧道的源IP地址为所述第一GRE隧道在所述HCPE上的隧道端口的IP地址，所述第一GRE隧道的隧道标识用于唯一指示所述第一GRE隧道。
  2. 根据权利要求1所述的方法，其特征在于，在所述HAG接收所述HCPE经由所述第一GRE隧道发送的业务报文之前，所述方法还包括：
    所述HAG接收所述HCPE发送的GRE控制报文，所述GRE控制报文包括用于指示所述第一GRE隧道的源IP地址与所述第一GRE隧道的隧道标识之间的对应关系的信息；
    所述HAG根据所述GRE控制报文，获取所述对应关系。
  3. 根据权利要求2所述的方法，其特征在于，所述HAG接收所述HCPE发送的GRE控制报文，包括：
    在建立所述第一GRE隧道的过程中，所述HAG接收所述HCPE发送的GRE Tunnel Setup Request报文，所述GRE Tunnel Setup Request报文的属性字段中包括用于指示所述对应关系的信息。
  4. 根据权利要求2所述的方法，其特征在于，所述HAG接收所述HCPE发送的GRE控制报文，包括：
    在建立所述第一GRE隧道之后，所述HAG接收所述HCPE发送的第一GRE Tunnel Notify报文，所述第一GRE Tunnel Notify报文的属性字段中包括用于指示所述对应关系的信息。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    在建立所述第一GRE隧道的过程中，所述HAG向所述HCPE发送GRE  Tunnel Setup Accept报文，所述GRE Tunnel Setup Accept报文中包括用于请求所述对应关系的请求信息；
    其中，所述HAG接收所述HCPE发送的第一GRE Tunnel Notify报文，包括：
    所述HAG接收所述HCPE根据所述请求信息发送的所述第一GRE Tunnel Notify报文。
  6. 根据权利要求4所述的方法，其特征在于，所述HAG接收所述HCPE发送的第一GRE Tunnel Notify报文，包括：
    所述HAG向所述HCPE发送用于请求所述对应关系的第二GRE Tunnel Notify报文；
    所述HAG接收所述HCPE根据所述第二GRE Tunnel Notify报文发送的所述第一GRE Tunnel Notify报文。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述至少两条GRE隧道中不同GRE隧道所在的接入网络类型不同，其中，所述第一GRE隧道的隧道标识指示所述第一GRE隧道所在的接入网络类型。
  8. 一种确定通用路由封装GRE隧道标识的方法，其特征在于，所述方法应用于混合接入网关HAG与混合接入终端设备HCPE之间有至少两条GRE隧道的场景，且所述至少两条GRE隧道绑定，所述方法包括：
    所述HCPE确定第一GRE隧道，所述第一GRE隧道为所述至少两条GRE隧道中的一条GRE隧道；
    所述HCPE经由所述第一GRE隧道向所述HAG发送业务报文，所述业务报文中包括承载所述业务报文的所述第一GRE隧道的源IP地址，以便于所述HAG根据承载所述业务报文的所述第一GRE隧道的源IP地址查找对应关系表，确定承载所述业务报文的所述第一GRE隧道的隧道标识，所述对应关系表包括所述第一GRE隧道的源IP地址与所述第一GRE隧道的隧道标识之间的对应关系，其中，所述第一GRE隧道的源IP地址为所述第一GRE隧道在所述HCPE上的隧道端口的IP地址，所述第一GRE隧道的隧道标识用于唯一指示所述第一GRE隧道。
  9. 根据权利要求8所述的方法，其特征在于，在所述HCPE经由所述第一GRE隧道向所述HAG发送业务报文之前，所述方法还包括：
    所述HCPE向所述HAG发送GRE控制报文，所述GRE控制报文包括 用于指示所述第一GRE隧道的源IP地址与所述第一GRE隧道的隧道标识之间的对应关系的信息。
  10. 根据权利要求9所述的方法，其特征在于，所述HCPE向所述HAG发送GRE控制报文，包括：
    在建立所述第一GRE隧道的过程中，所述HCPE向所述HAG发送GRE Tunnel Setup Request报文，所述GRE Tunnel Setup Request报文的属性字段中包括用于指示所述对应关系的信息。
  11. 根据权利要求9所述的方法，其特征在于，所述HCPE向所述HAG发送GRE控制报文，包括：
    在建立所述第一GRE隧道之后，所述HCPE向所述HAG发送第一GRE Tunnel Notify报文，所述第一GRE Tunnel Notify报文的属性字段中包括用于指示所述对应关系的信息。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    在建立所述第一GRE隧道的过程中，所述HCPE接收所述HAG发送的GRE Tunnel Setup Accept报文，所述GRE Tunnel Setup Accept报文中包括用于请求所述对应关系的请求信息；
    其中，所述HCPE向所述HAG发送第一GRE Tunnel Notify报文，包括：
    所述HCPE根据所述请求信息，向所述HAG发送所述第一GRE Tunnel Notify报文。
  13. 根据权利要求11所述的方法，其特征在于，所述HCPE向所述HAG发送第一GRE Tunnel Notify报文，包括：
    所述HCPE接收所述HAG发送的用于请求所述对应关系的第二GRE Tunnel Notify报文；
    所述HCPE根据所述第二GRE Tunnel Notify报文，向所述HAG发送所述第一GRE Tunnel Notify报文。
  14. 根据权利要求8至13中任一项所述的方法，其特征在于，所述至少两条GRE隧道中不同GRE隧道所在的接入网络类型不同，其中，所述第一GRE隧道的隧道标识指示所述第一GRE隧道所在的接入网络类型。
  15. 一种网络设备，其特征在于，所述网络设备与混合接入终端设备HCPE之间有至少两条GRE隧道的场景，且所述至少两条GRE隧道绑定，所述网络设备包括：
    接收模块，用于接收所述HCPE经由第一GRE隧道发送的业务报文，所述业务报文中包括承载所述业务报文的所述第一GRE隧道的源IP地址，其中，所述第一GRE隧道为所述至少两条GRE隧道中的一条GRE隧道；
    确定模块，用于根据承载所述接收模块接收的所述业务报文的所述第一GRE隧道的源IP地址查找对应关系表，确定承载所述业务报文的所述第一GRE隧道的隧道标识，所述对应关系表包括所述第一GRE隧道的源IP地址与所述第一GRE隧道的隧道标识之间的对应关系，其中，所述第一GRE隧道的源IP地址为所述第一GRE隧道在所述HCPE上的隧道端口的IP地址，所述第一GRE隧道的隧道标识用于唯一指示所述第一GRE隧道。
  16. 根据权利要求15所述的网络设备，其特征在于，所述接收模块还用于，接收所述HCPE经由所述第一GRE隧道发送的业务报文之前，接收所述HCPE发送的GRE控制报文，所述GRE控制报文包括用于指示所述第一GRE隧道的源IP地址与所述第一GRE隧道的隧道标识之间的对应关系的信息；
    所述网络设备还包括：
    获取模块，用于根据所述接收模块接收的所述GRE控制报文，获取所述对应关系。
  17. 根据权利要求16所述的网络设备，其特征在于，所述接收模块用于，在建立所述第一GRE隧道的过程中，接收所述HCPE发送的GRE Tunnel Setup Request报文，所述GRE Tunnel Setup Request报文的属性字段中包括用于指示所述对应关系的信息。
  18. 根据权利要求16所述的网络设备，其特征在于，所述接收模块用于，在建立所述第一GRE隧道之后，接收所述HCPE发送的第一GRE Tunnel Notify报文，所述第一GRE Tunnel Notify报文的属性字段中包括用于指示所述对应关系的信息。
  19. 根据权利要求18所述的网络设备，其特征在于，所述网络设备还包括：
    发送模块，用于在建立所述第一GRE隧道的过程中，向所述HCPE发送GRE Tunnel Setup Accept报文，所述GRE Tunnel Setup Accept报文中包括用于请求所述对应关系的请求信息；
    其中，所述接收模块用于，接收所述HCPE根据所述请求信息发送的所 述第一GRE Tunnel Notify报文。
  20. 根据权利要求18所述的网络设备，其特征在于，所述接收模块包括：
    发送单元，用于向所述HCPE发送用于请求所述对应关系的第二GRE Tunnel Notify报文；
    接收单元，用于接收所述HCPE根据所述发送单元发送的所述第二GRE Tunnel Notify报文发送的所述第一GRE Tunnel Notify报文。
  21. 根据权利要求15至20中任一项所述的网络设备，其特征在于，所述至少两条GRE隧道中不同GRE隧道所在的接入网络类型不同，其中，所述第一GRE隧道的隧道标识指示所述第一GRE隧道所在的接入网络类型。
  22. 一种网络设备，其特征在于，所述网络设备与混合接入网关HAG之间有至少两条GRE隧道的场景，且所述至少两条GRE隧道绑定，所述网络设备包括：
    确定模块，用于确定第一GRE隧道，所述第一GRE隧道为所述至少两条GRE隧道中的一条GRE隧道；
    发送模块，用于经由所述确定模块确定的所述第一GRE隧道向所述HAG发送业务报文，所述业务报文中包括承载所述业务报文的所述第一GRE隧道的源IP地址，以便于所述HAG根据承载所述业务报文的所述第一GRE隧道的源IP地址查找对应关系表，确定承载所述业务报文的所述第一GRE隧道的隧道标识，所述对应关系表包括所述第一GRE隧道的源IP地址与所述第一GRE隧道的隧道标识之间的对应关系，其中，所述第一GRE隧道的源IP地址为所述第一GRE隧道在所述HCPE上的隧道端口的IP地址，所述第一GRE隧道的隧道标识用于唯一指示所述第一GRE隧道。
  23. 根据权利要求22所述的网络设备，其特征在于，所述发送模块还用于，在经由所述第一GRE隧道向所述HAG发送业务报文之前，向所述HAG发送GRE控制报文，所述GRE控制报文包括用于指示所述第一GRE隧道的源IP地址与所述第一GRE隧道的隧道标识之间的对应关系的信息。
  24. 根据权利要求23所述的网络设备，其特征在于，所述发送模块用于，在建立所述第一GRE隧道的过程中，向所述HAG发送GRE Tunnel Setup Request报文，所述GRE Tunnel Setup Request报文的属性字段中包括用于指 示所述对应关系的信息。
  25. 根据权利要求23所述的网络设备，其特征在于，所述发送模块用于，在建立所述第一GRE隧道之后，向所述HAG发送第一GRE Tunnel Notify报文，所述第一GRE Tunnel Notify报文的属性字段中包括用于指示所述对应关系的信息。
  26. 根据权利要求25所述的网络设备，其特征在于，所述网络设备还包括：
    接收模块，用于在建立所述第一GRE隧道的过程中，接收所述HAG发送的GRE Tunnel Setup Accept报文，所述GRE Tunnel Setup Accept报文中包括用于请求所述对应关系的请求信息；
    其中，所述发送模块用于根据所述请求信息，向所述HAG发送所述第一GRE Tunnel Notify报文。
  27. 根据权利要求25所述的网络设备，其特征在于，所述发送模块包括：
    接收单元，用于接收所述HAG发送的用于请求所述对应关系的第二GRE Tunnel Notify报文；
    发送单元，用于根据所述接收单元接收的所述第二GRE Tunnel Notify报文，向所述HAG发送所述第一GRE Tunnel Notify报文。
  28. 根据权利要求22至27中任一项所述的网络设备，其特征在于，所述至少两条GRE隧道中不同GRE隧道所在的接入网络类型不同，其中，所述第一GRE隧道的隧道标识指示所述第一GRE隧道所在的接入网络类型。
  29. 一种确定通用路由封装GRE隧道标识的系统，其特征在于，所述系统包括如权利要求15-21中任一项所述的网络设备，和如权利要求22-28中任一项所述的网络设备。
PCT/CN2015/097757 2015-12-17 2015-12-17 确定通用路由封装gre隧道标识的方法、设备和系统 WO2017101085A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
CN202010631680.2A CN111917650B (zh) 2015-12-17 2015-12-17 确定通用路由封装gre隧道标识的方法、设备和系统
EP15910556.8A EP3382952B1 (en) 2015-12-17 2015-12-17 Method, device and system for determining generic routing encapsulation (gre) tunnel identifier
CN201580062767.XA CN107113230B (zh) 2015-12-17 2015-12-17 确定通用路由封装gre隧道标识的方法、设备和系统
PCT/CN2015/097757 WO2017101085A1 (zh) 2015-12-17 2015-12-17 确定通用路由封装gre隧道标识的方法、设备和系统
EP19219742.4A EP3691204B1 (en) 2015-12-17 2015-12-17 Method, device, and system for determining generic routing encapsulation gre tunnel identifier
ES15910556T ES2788720T3 (es) 2015-12-17 2015-12-17 Método, dispositivo y sistema para determinar un identificador de túnel para encapsulación de enrutamiento genérico (GRE)
US16/010,512 US10873478B2 (en) 2015-12-17 2018-06-17 Method, device, and system for determining generic routing encapsulation GRE tunnel identifier
US17/118,507 US11817970B2 (en) 2015-12-17 2020-12-10 Method, device, and system for determining generic routing encapsulation GRE tunnel identifier

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/097757 WO2017101085A1 (zh) 2015-12-17 2015-12-17 确定通用路由封装gre隧道标识的方法、设备和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/010,512 Continuation US10873478B2 (en) 2015-12-17 2018-06-17 Method, device, and system for determining generic routing encapsulation GRE tunnel identifier

Publications (1)

Publication Number Publication Date
WO2017101085A1 true WO2017101085A1 (zh) 2017-06-22

Family

ID=59055470

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/097757 WO2017101085A1 (zh) 2015-12-17 2015-12-17 确定通用路由封装gre隧道标识的方法、设备和系统

Country Status (5)

Country Link
US (2) US10873478B2 (zh)
EP (2) EP3382952B1 (zh)
CN (2) CN107113230B (zh)
ES (1) ES2788720T3 (zh)
WO (1) WO2017101085A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3382952B1 (en) * 2015-12-17 2020-02-26 Huawei Technologies Co., Ltd. Method, device and system for determining generic routing encapsulation (gre) tunnel identifier
CN108712348A (zh) * 2018-05-18 2018-10-26 王逸人 流量控制方法、系统、设备及计算机可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009132530A1 (zh) * 2008-04-30 2009-11-05 华为技术有限公司 报文错误检测方法、报文错误处理方法、设备及系统
CN103905284A (zh) * 2012-12-27 2014-07-02 杭州华三通信技术有限公司 一种基于evi网络的流量负载分担方法和设备
CN104601483A (zh) * 2013-10-31 2015-05-06 华为技术有限公司 报文转发方法、装置及转发设备

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101272340B (zh) * 2008-04-30 2012-09-26 中兴通讯股份有限公司 一种racs支持移动ip的系统及方法
US8897139B2 (en) * 2008-12-05 2014-11-25 Hewlett-Packard Development Company, L.P. Packet processing indication
US8687631B2 (en) * 2009-10-16 2014-04-01 Cisco Technology, Inc. System and method for providing a translation mechanism in a network environment
US8787303B2 (en) * 2010-10-05 2014-07-22 Cisco Technology, Inc. Methods and apparatus for data traffic offloading at a router
EP2728802B1 (en) * 2012-11-02 2020-08-12 Deutsche Telekom AG Method and system for network and service controlled hybrid access
CN104052666B (zh) * 2013-03-14 2018-05-11 新华三技术有限公司 实现主机路由可达的方法和装置
CN104869042B (zh) * 2014-02-20 2018-07-13 华为技术有限公司 报文转发方法和装置
CN103986637B (zh) * 2014-05-15 2018-11-27 新华三技术有限公司 一种差错报文处理方法及隧道设备
US20170005830A1 (en) * 2015-06-30 2017-01-05 Futurewei Technologies, Inc. Demultiplexing Bonded GRE Tunnels
EP3382952B1 (en) * 2015-12-17 2020-02-26 Huawei Technologies Co., Ltd. Method, device and system for determining generic routing encapsulation (gre) tunnel identifier

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009132530A1 (zh) * 2008-04-30 2009-11-05 华为技术有限公司 报文错误检测方法、报文错误处理方法、设备及系统
CN103905284A (zh) * 2012-12-27 2014-07-02 杭州华三通信技术有限公司 一种基于evi网络的流量负载分担方法和设备
CN104601483A (zh) * 2013-10-31 2015-05-06 华为技术有限公司 报文转发方法、装置及转发设备

Also Published As

Publication number Publication date
US20180302240A1 (en) 2018-10-18
CN107113230B (zh) 2020-07-24
EP3382952A4 (en) 2018-11-21
US11817970B2 (en) 2023-11-14
US20210167993A1 (en) 2021-06-03
CN111917650A (zh) 2020-11-10
EP3382952B1 (en) 2020-02-26
EP3691204B1 (en) 2022-08-31
US10873478B2 (en) 2020-12-22
EP3382952A1 (en) 2018-10-03
ES2788720T3 (es) 2020-10-22
CN107113230A (zh) 2017-08-29
EP3691204A1 (en) 2020-08-05
CN111917650B (zh) 2023-04-18

Similar Documents

Publication Publication Date Title
US10091304B2 (en) SGC and PGC and SGU and PGU allocation procedure
CN105657748B (zh) 基于隧道绑定的通信方法和网络设备
US20220377819A1 (en) Method and apparatus for establishing data transmission link and computer-readable storage medium
CN102724118B (zh) 标签分发方法及设备
WO2013182059A1 (zh) 多协议标签交换流量工程隧道建立方法及设备
US11153207B2 (en) Data link layer-based communication method, device, and system
CN114124618B (zh) 一种报文传输方法及电子设备
WO2012079527A1 (zh) 公共路径的建立和使用方法、m2m的通信方法及系统
CN106899500B (zh) 一种跨虚拟可扩展局域网的报文处理方法及装置
WO2017211164A1 (zh) 一种确定跨域标签交换路径隧道的方法、设备和系统
CN110752979B (zh) 报文的隧道传输方法、装置及网络设备
US20170005830A1 (en) Demultiplexing Bonded GRE Tunnels
CN109936492A (zh) 一种通过隧道传输报文的方法、装置和系统
WO2015000384A1 (zh) 一种标签处理的方法及装置
CN104993993A (zh) 一种报文处理方法、设备和系统
US11817970B2 (en) Method, device, and system for determining generic routing encapsulation GRE tunnel identifier
US11323410B2 (en) Method and system for secure distribution of mobile data traffic to closer network endpoints
US8817648B2 (en) Pseudowire extended group messaging in a packet switched network
US20130259057A1 (en) Pseudowire groups in a packet switched network
CN112804129A (zh) 报文传输方法及系统，发送端vpn设备及gre拼接设备
CN113300998A (zh) 实现数据加密传输的方法及装置、通信系统
WO2015096008A1 (en) Method and network node for routing backhaul packets
CN115913820A (zh) 网络传输方法和设备
CN114915519A (zh) 通信方法和通信装置
CN117354223A (zh) 流量传输方法、装置、系统、通信设备和存储介质

Legal Events

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

Ref document number: 15910556

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2015910556

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2015910556

Country of ref document: EP

Effective date: 20180627