WO2012149777A1 - Procédé, appareil et système pour établir un chemin à commutation d'étiquettes - Google Patents

Procédé, appareil et système pour établir un chemin à commutation d'étiquettes Download PDF

Info

Publication number
WO2012149777A1
WO2012149777A1 PCT/CN2011/080305 CN2011080305W WO2012149777A1 WO 2012149777 A1 WO2012149777 A1 WO 2012149777A1 CN 2011080305 W CN2011080305 W CN 2011080305W WO 2012149777 A1 WO2012149777 A1 WO 2012149777A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
path message
session identifier
address information
core node
Prior art date
Application number
PCT/CN2011/080305
Other languages
English (en)
Chinese (zh)
Inventor
林毅
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2011/080305 priority Critical patent/WO2012149777A1/fr
Priority to CN201180002218.5A priority patent/CN102439919B/zh
Publication of WO2012149777A1 publication Critical patent/WO2012149777A1/fr

Links

Classifications

    • 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, and a system for establishing a label switching path. Background technique
  • GMPLS Generalized Multi-Protocol Label Switching
  • RSVP-TE Resource Reservation Protocol-Traffic Engineering
  • the source node assigns a tunnel ID (tunnel identifier) and an LSP ID (label switching path identifier) to the connection;
  • the sink node After receiving the Path message, the sink node starts the sink node, performs label allocation, resource reservation, and cross-connection establishment on a node-by-node basis in the reverse direction of the connection, and returns a Resv (Resource Reservation Message) message to the upstream node.
  • the message carries the assigned tag information;
  • the source node receives the Resv message and the connection is established successfully.
  • Overlay Network establishes a label switched path between the nodes through the Core Network.
  • the routing information between the overlay network and the core network is isolated from each other, that is, in the overlay network.
  • the node cannot obtain the detailed topology information in the core network through the routing protocol.
  • the nodes in the core network cannot obtain the detailed topology information in the overlay network through the routing protocol, and need to establish between the nodes in the two overlay networks.
  • a connection through the core network is required, a UNI (User-Network Interface) between the overlay network and the core network is required to establish a connection.
  • the UNI interfaces that require the source EN (Edge Node), the ingress CN (Core Node), the egress CN, and the sink EN belong to the same addressing space.
  • the source EN is the upstream node of the ingress CN
  • the egress CN is the upstream node of the sink EN.
  • the GMPLS signaling message can start from the source EN, along the node through which the connection passes. The hop is sent to the sink EN to establish the connection.
  • each node uses the source EN address + sink EN address + the source ID assigned by the source EN as the unique identifier of the session.
  • the overlay network and the core network may be deployed independently, when addressing the network node, it is likely that the two networks are not assigned addresses from within the same addressing space. Individually addressed, the address of the node in the overlay network may conflict with the address of the node in the core network, such as the same address. In this case, it may happen that although it belongs to two different sessions, it is due to the nodes in the overlay network. The address and the node in the core network are assigned the same address, resulting in the same situation in which the two session identifiers are the same. As a result, the nodes in the core network cannot correctly distinguish different label switching paths, which causes the signaling protocol processing to be confusing, and finally can not be established. The correct label switching path.
  • the overlay network and the core network adopt different addressing methods, for example, the nodes in the overlay network adopt the IPv4 addressing mode, and the nodes in the core network adopt the IPv6 addressing mode, if the overlay network and the core network If the node in the core network receives the path message sent by the node in the network, the address in the path message cannot be correctly identified because the address space is different. Label switching path.
  • the embodiment of the present invention provides a method, an apparatus, and a system for establishing a label switching path.
  • the technical solution is as follows:
  • a method for establishing a label switched path includes:
  • the ingress core node receives the first path message from the source edge node, where the first path message carries the first session identifier, where the first session identifier includes: address information of the source node, address information of the sink node, and the source node assignment Tunnel identification;
  • the second path message Converting the first path message to a second path message, where the second path message carries the first session identifier and the second session identifier, where the second session identifier includes: address information of the ingress core node, The address information of the egress core node and the tunnel identifier assigned by the ingress core node, so that the core node in the core network uses the second session identifier as the session identifier of the label switching path;
  • an ingress node comprising:
  • a receiving module configured to receive a first path message sent by the source edge node, where the first path message carries a first session identifier, where the first session identifier includes: address information of the source node, address information of the sink node, and Source section Point assigned tunnel identifier;
  • a conversion module configured to convert the first path message into a second path message, where the second path message carries the first session identifier and the second session identifier, where the second session identifier includes: the entry core The address information of the node, the address information of the egress core node, and the tunnel identifier assigned by the ingress core node, so that the core node in the core network uses the second session identifier as the session identifier of the label switching path;
  • a sending module configured to send the second path message to the egress core node hop by hop, so that the egress core node restores the second path message to the first path message according to the first session identifier And sending the first path message to the sink node to establish a label switched path.
  • a method for establishing a label switched path comprising:
  • the user network interface UNI server receives the first path message from the source edge node, where the first path message carries the first session identifier, where the first session identifier includes: address information of the source node, address information of the sink node, and the source The tunnel identifier assigned by the node;
  • the second path message Converting the first path message to a second path message, where the second path message carries the first session identifier and the second session identifier, where the second session identifier includes: address information of the ingress core node, The address information of the egress core node and the tunnel identifier assigned by the ingress core node, so that the core node in the core network uses the second session identifier as the session identifier of the label switching path;
  • the first session identifier restores the second path message to the first path message, and sends the first path message to the sink node to establish a label switching path.
  • a system for label switching path establishment comprising: an ingress core node and an egress core node as described above;
  • the egress core node is configured to receive a second path message sent by the ingress core node hop by hop according to the first session identifier, and restore the second path message to a first path message, where the first path message is sent Sent to the sink node to establish a label switched path.
  • a server comprising:
  • a receiving module configured to receive a first path message from the source edge node, where the first path message carries a first session identifier, where the first session identifier includes: address information of the source node, address information of the sink node, and the source The tunnel identifier assigned by the node;
  • a conversion module configured to convert the first path message into a second path message, where the second path message carries the first session identifier and the second session identifier, where the second session identifier includes: the entry core Node address information, The address information of the egress core node and the tunnel identifier assigned by the ingress core node, so that the core node in the core network uses the second session identifier as the session identifier of the label switching path;
  • a forwarding module configured to send the second path message to the ingress core node, to enable the ingress core node to send the second path message hop by hop to a server at the egress core node, where the egress core
  • the server at the node restores the second path message to the first path message according to the first session identifier, and sends the first path message to the sink node to establish a label switching path.
  • a system for label switched path establishment comprising: a server at the server, an ingress core node, and an egress core node as described above;
  • the ingress core node is configured to receive a second path message sent by the server, and send the second path message hop by hop to a server at the egress core node;
  • the server at the egress core node is configured to restore the second path message to the first path message according to the first session identifier, and send the first path message to the sink node to establish a label switching path.
  • the first session identifier carried in the first path message is converted into the second session identifier at the ingress core node, where the second session identifier includes: address information of the ingress core node And the address information of the egress core node and the tunnel identifier allocated by the ingress core node, where the second session identifier information is unique on the path from the ingress core node to the egress core node, and the core node in the core network is in the second session
  • the session identifier of the label switching path is identified, thereby solving the problem that the nodes in the core network cannot correctly distinguish different label switching paths and cannot establish a correct label switching path because the source node and the ingress core node address are the same.
  • FIG. 1 is a flowchart of a method for establishing a label switching path according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for establishing a label switching path according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for establishing a label switching path according to an embodiment of the present invention
  • 4 is a schematic diagram of a system for deploying a UNI server outside a node of a network according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a UNI_info object format according to an embodiment of the present invention
  • FIG. 6 is a schematic system diagram of a label switching path according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of an ingress core node according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a system for establishing a label switching path according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a server according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a system for establishing a label switching path according to an embodiment of the present invention. detailed description
  • a connection is a pipe established between the first and last node pairs, which can be used to transmit the services of the client layer;
  • a tunnel is a transmission resource provided for a specific service of a client layer between a pair of first and last nodes.
  • a tunnel may contain one or more connections. For example, if the connection fails and re-routing, or the bandwidth of the connection is modified, the re-routed or bandwidth-modified connection and the original connection are two different connections, but belong to the same tunnel; 1+1 or 1: 1 service, the working path and the protection path are two different connections but belong to the same tunnel;
  • the GMPLS signaling protocol uses one Session to establish and control one tunnel.
  • the signaling protocol carries the identifier of the session and the identifier of the connection to indicate the tunnel and the connection corresponding to the signaling message.
  • GMPLS uses the source node address + sink node address + the unique tunnel ID assigned by the source node in the source node as the unique identifier of one session;
  • GMPLS uses the session identifier + the unique LSP ID assigned by the source node in the source node (or within the source node + tunnel ID range) as the unique identifier of one connection.
  • an embodiment of the present invention provides a method for establishing a label switching path, including:
  • the ingress core node receives the first path message sent by the source edge node, where the first path message carries a first session identifier, where the first session identifier includes address information of the source node, address information of the sink node, and the The tunnel identifier assigned by the source node;
  • the first path message is converted into a second path message, where the second path message carries the first session identifier and the second session identifier, where the second session identifier includes: address information of the ingress core node, and an egress core Node ground The address information and the tunnel identifier allocated by the ingress core node, so that the core node in the core network uses the second session identifier as the session identifier of the label switching path;
  • the source edge node, the sink edge node, the source node, and the sink node belong to the overlay network
  • the ingress core node and the egress core node belong to the core network
  • the source edge node is the upstream node of the ingress core node
  • the sink edge node is the egress core.
  • converting the first path message to the second path message includes:
  • the pre-configured UNI information includes: The address information of the source edge node, the address information of the ingress core node corresponding to the source edge node, the address information of the sink edge node, and the address information of the egress core node corresponding to the sink edge node;
  • the first path message further carries a port identifier of the source node or a port identifier of the ingress core node, and is used to indicate a user network interface selected by the source node;
  • the ingress core node After receiving the first path message sent by the source node, further includes:
  • the port identifier of the source node is replaced with the port identifier of the ingress core node.
  • the first path message carries the first label switching path identifier LSP ID
  • the second path message carries the second label switching path identifier and the first label switching path identifier, where
  • the second tag interaction path identifier is that the ingress core node is allocated for the label switching path.
  • the method further includes: the egress core node receiving the second path message;
  • the first path message further carries a network identifier where the source node is located, and is used to indicate the The network where the source node is located.
  • the first session identifier carried in the first path message is converted into the second session identifier at the ingress core node, where the second session identifier includes: address information of the ingress core node, Address information of the egress core node and a tunnel identifier assigned by the ingress core node, where the second session identifier information is unique on the path from the ingress core node to the egress core node, and the core node in the core network is identified by the second session
  • the problem that the nodes in the core network cannot correctly distinguish different label switching paths and cannot establish a correct label switching path due to the same address of the source node and the ingress core node is solved.
  • an embodiment of the present invention provides a method for establishing a label switching path, including:
  • the user network interface UNI server receives the first path message sent by the source edge node, where the first path message carrying message carries the first session identifier, where the first session identifier includes: address information of the source node, and the location information of the sink node Address information and a tunnel identifier assigned by the source node;
  • the second P path message carries the first session identifier and the second session identifier
  • the second session identifier includes: The address information, the address information of the egress core node, and the tunnel identifier assigned by the ingress core node, so that the core node in the core network uses the second session identifier as the session identifier of the label switching path;
  • converting the first path message to the second path message includes:
  • the pre-configured UNI information includes: Address information of the source edge node, address information of the ingress core node corresponding to the source edge node, address information of the sink edge node, and address information of the egress core node corresponding to the sink edge node;
  • the method of the present invention provides the following steps:
  • the UNI server is configured to convert the first session identifier carried in the first path message into a second session identifier, where the second session identifier includes: address information of the ingress core node, Address information of the egress core node and a tunnel identifier assigned by the ingress core node, where the second session identifier information is unique on the path from the ingress core node to the egress core node, and the core node in the core network is identified by the second session
  • the session identifier of the label switching path the problem that the nodes in the core network cannot correctly distinguish different label switching paths and cannot establish a correct label switching path due to the same address of the source node and the ingress core node is solved.
  • an embodiment of the present invention provides a method for establishing a label switching path.
  • a source node and a source edge node are one node
  • a sink node and a sink edge node are one node.
  • the specific method includes:
  • a UNI server in order to solve the problem of the UNI address space limitation, a UNI server is provided, and the UNI server is configured with related information of the UNI link, that is, pre-configured UNI information, such as node addresses at both ends, interfaces at both ends Address, etc.
  • the UNI server can implement the conversion of the address identifier in the path message and the forwarding of the path message.
  • the UNI server may be a server independent of each node in the network, or may be directly deployed on an ingress and/or egress node at the edge of the core network, that is, the edge core node directly functions as a UNI server.
  • a distributed schematic diagram of a system in which a UNI server is deployed outside the nodes of the network is provided.
  • the edge nodes in the overlay network are EN1 and EN2, and the core nodes in the core network are CN1, CN2, and CN3.
  • CN1 is the ingress core node
  • CN2 is the egress core node
  • UNI server A and UNI server B are servers deployed outside CN1 and CN2 respectively.
  • the UNI server is controlled by the operator of the core network, and the overlay network applies to the core network operator to connect to the core network when the network is built; the core network configures the UNI server, thereby providing services for the overlay network.
  • the operator of the core network can configure the information of each UNI link on each UNI server.
  • These UNI link information can be directly configured in the routing table or as separate UNI link information. Table. For example, for the UNI server in Figure 4, the UNI link information shown in Table 1 below can be configured:
  • the port of the UNI link can be configured as an IP address or a unique unnumbered port identifier in only the node.
  • link binding that is, when multiple member links are bound to one UNI link, in addition to configuring the port address or port identifier of the bonded link, you need to further configure the internal link. Member link ID of each member link.
  • both UNI server A and UNI server B are distributed servers. Local UNI link information is deployed on the two servers. That is, the address information of EN1 and CN1 is deployed on UNI server A. The address information of EN2 and CN2 is deployed on the UNI server B.
  • the address information deployed on the UNI server A and the UNI server B is flooded to other UNI servers in the core network through the routing protocol, that is, the UNI server A is deployed.
  • the address information is flooded to the UNI server B, and the address information on the UNI server B is flooded to the UNI server A.
  • the UNI server in order for the UNI server to communicate with the overlay network control plane, the UNI server requires a control plane interface to be connected to the control plane of the overlay network, and the interface needs to be assigned an address that belongs to the same addressing space as the overlay network. If the UNI server is independent of the core network, the UNI server needs another interface to be connected to the control plane of the core network. Similarly, the interface needs to allocate an address that belongs to the same addressing space as the core network.
  • the source EN1 sends a Path message to EN2 via the intermediate node.
  • the source EN1 is the source node of the label switching path.
  • EN1 can be sent to the corresponding UNI server.
  • Send Path The message, in the Path message, carries the source node address information, the sink node address information, and the unique tunnel address information in the range of the source node.
  • EN1 indicates that the connected first and the sink nodes are respectively EN1.
  • the tunnel ID of EN has different tunnel IDs, but the tunnel IDs of tunnels arriving at different sinks EN may be the same.
  • the source node address information, sink node address information, and unique tunnel address information within the source node are the first. Session ID.
  • the message further includes an IF-ID RSVP-HOP object, where the object includes a local port identifier or a peer port identifier of the UNI link, and is used to indicate the UNI link selected by the source node.
  • EN1 may select a UNI link with port identifiers at both ends, Pa and P1.
  • the IF-ID RSVP-HOP object contains the peer port identifier of the UNI link (Pl , ie link ID).
  • the EN node may not be able to fill in the identifier of the peer port of the UNI link in the object due to the addressing space problem (for example, the EN node does not know the peer port identifier of the UNI link, or the signaling processing of the EN node. IPv6 is not supported, and the peer port identifier is in IPv6 format. Therefore, the UNI peer port identifier cannot be filled in the IF-ID RSVP-HOP. In this case, EN1 can be filled in the IF-ID RSVP-HOP object.
  • Local port ID (Pa) Local port ID
  • EN1 encapsulates the Path message as an IP packet, and the destination address of the IP packet is the corresponding UNI server.
  • the Path message can be sent to the UNI server.
  • the UNI server or the ingress core node processes the received Path message.
  • the processing of the Path message by the UNI server or the ingress core node after receiving the Path message specifically includes:
  • the UNI server or the ingress core node obtains the address information of the sink edge node, searches for the configured UNI information according to the address information of the sink edge node, and determines the address information of the egress core node connected to the sink edge node. More preferably, if the sink edge node is connected to multiple egress core nodes at the same time (referred to as multi-homing), the UNI server can select an optimal egress core node according to the network topology and resource conditions, for example, the UNI server can calculate from the source EN to The least cost path between the sinks EN, thus determining the exit core node.
  • the UNI server or the ingress core node replaces the source node address and the sink node address in the Path message with the addresses of the ingress core node and the egress core node, that is, replaces the address of EN1 with the address of CN1, and replaces the address of EN2 with the address of CN2. .
  • the IF-ID RSVP-HOP object in the Path message contains the port identifier of the UNI link on the EN side, it is also required to replace the identifier with the port identifier of the UNI link on the ingress core node side according to the UNI information. That is, replace Pa with P1, so that the ingress core node can know which UNI link the EN selects, and then reserve resources on the selected UNI link for use by the service.
  • the UNI server or the ingress core node allocates a tunnel ID to the label switching path according to the address information of the egress core node, and the tunnel ID is unique within the scope of the ingress core node; or, the tunnel ID and the egress core section
  • the identifier of the address of the point is unique within the scope of the ingress core node (ie, in the ingress core node, all the tunnels that reach the same egress core node have different tunnel ID values, but the tunnel ID of the tunnel reaching the different egress core nodes may be the same).
  • the address of the ingress core node and the egress core node and the ingress core node allocate a tunnel ID to the label switching path as the second session identifier according to the address information of the egress core node.
  • Step 2) -3) Performing is a process of converting the first path message into a second path message.
  • the first session identifier needs to be saved in the Path message, including the node of the source EN and the sink EN. Address, tunnel ID assigned by source EN.
  • a UNI_info object can be newly defined in the Path message to save the information.
  • the UNI server can also save the LSP ID assigned by the source EN. Referring to FIG.
  • an embodiment of the present invention provides a format of a UNI_info object format, where a tunnel source end point address and a tunnel destination end point address are respectively a node address of a source EN and a sink EN (32 bits are respectively occupied by using IPv4,
  • the LSP ID field is optional.
  • the tunnel ID and LSP ID are the tunnel ID and LSP ID assigned by the source node.
  • the LSP ID field is optional.
  • the Path message also carries the LSP ID, and the UNI server or the ingress core node may directly adopt the LSP ID assigned by the source EN, or may re-allocate a new LSP ID. If a new LSP ID is assigned, the LSP ID assigned by the source EN needs to be filled in the UNI_info object.
  • the UNI server or the ingress core node locally saves the pre-conversion session identifier (source EN address + sink EN address + source EN assigned tunnel ID) and the converted session identifier (ingress core node address + egress core node) Address + tunnel ID assigned by the ingress core node).
  • the UNI server or ingress core node can also save the pre- and post-conversion LSP IDs.
  • the UNI server needs to send the processed Path message to the ingress core node.
  • the UNI server may use the RSVP-TE protocol, and may also use other communication protocols for sending, which is not specifically limited in this embodiment. This process is not required if the UNI server is deployed directly in the ingress core node.
  • the ingress core node needs to process the Path message in a normal manner, including creating a control status block on the control plane of the ingress core node, and saving the information in the Path message.
  • the established connection selects the link in the downstream direction of the ingress core node and sends a Path message in the downstream direction.
  • the ingress core node may also perform label allocation on the selected link (the allocated label will be carried in the Path message, sent to the ingress core node) and the resource reservation process.
  • the command may be further sent to the data plane of the ingress core node to establish a cross-connection from the ingress port to the egress port of the ingress core node.
  • Each intermediate core node performs processing on the received Path message.
  • the intermediate core node nodes that are connected to process the Path message in a normal manner including creating a control status block on the control plane of the node, saving the information in the Path message, and selecting the downstream direction for the connection to be established.
  • the link sends the Path message to the downstream direction hop by hop until the core node node is exported.
  • the intermediate node may also perform label allocation on the selected link (the assigned label will be carried in the Path message, sent to the downstream neighbor node) and the resource reservation process, and The command may be further sent to the data plane of the node to establish a cross-connection from the ingress port to the egress port of the intermediate node.
  • the UNI_info object remains unchanged and is always passed along with the Path message to the egress core node.
  • the Path message is processed after the egress core node or the UNI server receives the Path message.
  • the UNI server since the UNI server converts the original Path message sent by the source node at the ingress core node, the UNI server needs to restore the converted Path message at the egress core node, including:
  • the egress core node or the UNI server After receiving the Path message, the egress core node or the UNI server obtains the address information of the source EN and the sink EN from the UNI_info object and the tunnel ID assigned by the source EN. At the same time, the egress core node or the UNI server will be in the Path message. The source node address, the sink node address, and the tunnel ID are restored to the source EN, the address information of the sink EN, and the tunnel ID assigned by the source EN, and the UNI_info object in the Path message is deleted.
  • the egress core node or the UNI server also needs to restore the LSP ID in the Path message to the source EN allocation. LSP ID.
  • the egress core node or UNI server selects the UNI link between the egress core node and the sink EN for connection.
  • the egress core node is at the IF— ID RSVP—The HOP object fills in the port identifier (such as P3) on the egress core node side of the selected UNI link, and the UNI server replaces the local port ID in the IF-ID RSVP-HOP object according to the UNI information table. It is the port identifier (such as Pc) on the side of the sink EN.
  • the egress core node or the UNI server may directly select the The UNI link is filled in the IF-ID RSVP-HOP object with the port identifier (such as Pc) on the sink EN side.
  • the UNI server or the egress core node locally saves the pre-restore session identifier (ingress core node address + egress core node address + tunnel ID assigned by the ingress core node) and the restored session identifier (source EN address + sink EN) Address + tunnel ID assigned by source EN).
  • the UNI server or the egress core node can also save the pre-restore and post-restore LSP IDs.
  • the export core node also needs to process the Path message in the normal way, including in the exit core section.
  • the control plane of the point creates a control status block, which stores the information in the Path message; optionally, after selecting the UNI link between the egress core node and the sink EN, the egress core node can also be on its selected UNI link.
  • the process of performing label allocation (the assigned label will be carried in the Path message and sent to the sink EN node) and resource reservation, and further issuing a command to the data plane of the egress core node to establish an ingress port from the egress core node A cross-connection between the outgoing port (that is, the port on the egress core node side of the UNI link).
  • the UNI server encapsulates the modified Path message into an IP packet, and the destination address of the IP packet is the address of the sink EN. In this way, the Path message can be sent to the sink EN.
  • the sink EN2 processes the Path message after receiving the Path message, and returns a Resv message to the EN1 via the intermediate node.
  • the sink EN processes the Path message in a normal manner, including: creating a control status block on the control plane of the sink EN node, and saving the information in the Path message; if the previous exit core node is not
  • the sinking EN node performs the process of label allocation and resource reservation on the selected UNI link, otherwise the resource is reserved on the selected UNI link according to the label allocated by the egress core node node, and is upstream.
  • the node returns a Resv message carrying the assigned tag information.
  • the source and sink nodes in the Resv message are still source EN and sink EN, and the tunnel ID and LSP ID are still the values assigned to the source EN.
  • the sink EN if the sink EN does not have the port identification information of the UNI link on the egress core node side, the port identification information of the UNI on the EN side is filled in the IF_ID RSVP_HOP object.
  • the sink EN encapsulates the Resv message into an IP packet, and the destination address of the IP packet is the address of the corresponding UNI server, thereby transmitting the Resv message to the corresponding UNI server.
  • the processing of the Resv message by the egress core node and the UNI server is similar to the processing of the Path message by the ingress core node and the UNI server, and specifically includes: the UNI server replaces the source node address and the sink node address in the Resv message with The address of the ingress core node and the egress core node, that is, the address of EN1 is replaced by the address of CN1, and the address of EN2 is replaced by the address of CN2.
  • the UNI server replaces the tunnel ID in the Resv message with the tunnel ID assigned by the ingress core node.
  • the IF-ID RSVP-HOP object in the Resv message contains the port identifier of the UNI link on the EN side, it is also required to replace the identifier with the port identifier of the UNI link on the core node side according to the UNI information table. , that is, replace Pc with P3.
  • the egress core node or the UNI server needs to replace the LSP ID in the Resv message with the LSP ID assigned by the ingress core node.
  • the Resv message contains the UNI_info object, but since the ingress core node or the UNI server holds the information in the UNI_info object, the object may or may not be carried.
  • the egress core node processes the Resv message in the normal manner, including: saving the letter in the Resv message Information, obtain the label allocated by the sink EN node, thereby determining the resource reserved on the UNI link; if the upstream neighbor node of the export core node node is not assigned a label, the exit core node is selected in the upstream direction The process of label allocation and resource reservation is performed on the road. Otherwise, resources are reserved on the selected link according to the label allocated by the upstream neighbor node of the export core node.
  • the egress node If the egress node does not establish a cross-connection before processing the Path message, it is required to further issue a command to the data plane of the node to establish an ingress port to the egress port from the egress core node (that is, the UNI link is in the egress core). Cross-connection between ports on the node side). Finally, the egress core node returns a Resv message to the upstream node, where the message carries the allocated tag information.
  • Each intermediate core node node processes the received Resv message.
  • the intermediate core nodes that are connected to process the Resv message in a normal manner including: saving the information in the Resv message, obtaining the label allocated by the downstream neighbor node, and determining the node and its downstream neighbor node. Resources reserved on the link; if the upstream neighbor node of the intermediate node does not assign a label, the intermediate node performs label allocation and resource reservation on the selected link in the upstream direction; otherwise, the intermediate node The label assigned by the upstream neighbor node reserves resources on the selected link. If the intermediate node does not establish a cross-connection before processing the Path message, it is required to further issue a command to the data plane of the node to establish a cross-connection from the ingress port to the egress port of the intermediate node.
  • each intermediate node sends a Resv message to the upstream direction hop by hop, and the message carries the allocated tag information until the ingress core node. If the Resv message contains a UNI_info object, then in the process, the UNI_info object remains unchanged and is always passed to the ingress core node with the Resv message.
  • the incoming core node or the UNI server processes the received Resv message.
  • the processing of the Resv message by the ingress core node and the UNI server is similar to the processing of the Path message by the egress core node and the UNI server, and specifically includes: After the Ingress core node or the UNI server receives the Resv message, the UNI_info object is received.
  • the source EN, the address information of the sink EN, and the tunnel ID assigned by the source EN are obtained from the locally saved information.
  • the ingress core node or the UNI server restores the source node address, the sink node address, and the tunnel ID in the Resv message to the source EN, the address information of the sink EN, and the tunnel ID assigned by the source EN, and deletes the UNI in the Path message. Info object.
  • the ingress core node is assigned a new LSP ID
  • the ingress core node or the UNI server also needs to restore the LSP ID in the Resv message to the LSP ID assigned by the source EN.
  • the UNI server fills the port identifier (such as Pa) of the previously selected UNI link on the source EN side into the IF-ID RSVP-HOP object; or, the egress core node selects the previously selected UNI chain.
  • the port identifier (such as P1) on the core node side is filled in the IF-ID RSVP-HOP object, and the UNI server converts the identifier into the corresponding port identifier (such as Pa) on the source EN side.
  • the ingress core node node processes the Resv message in a normal manner, including: saving information in the Resv message, obtaining a label allocated by the downstream neighbor node, thereby determining that the ingress core node node and its downstream neighbor node Resources reserved on the link; if the source EN node does not assign a label, the ingress core node performs label allocation and resource reservation on the selected UNI link, otherwise it is allocated by the source EN node.
  • the label reserves resources on the selected UNI link.
  • the ingress core node also contains the assigned tag in the Resv message.
  • the ingress core node node does not establish a cross-connection before processing the Path message, it is further required to issue a command to the data plane of the node to establish an ingress port from the ingress core node node (ie, the UNI link is on the ingress core node side). Port) A cross-connection between the outgoing ports.
  • the UNI server encapsulates the modified Resv message into an IP packet, and the destination address of the IP packet is the address of the source EN. In this way, the Resv message can be sent to the source EN.
  • Source EN1 handles the Resv message.
  • the source EN1 node after receiving the Resv message, saves the information in the Resv message, obtains the label allocated by the ingress core node node, determines the resource reserved on the UNI link, and completes the connection establishment process.
  • the core network provides transmission resources for two mutually independent overlay networks (A and B). Since the core network, the overlay network A, and the overlay network B all allocate node addresses within their respective ranges, it is possible
  • the addresses of EN1, EN3, and CN1 are the same (both 1. 1. 1. 1), and the addresses of EN2, EN4, and CN2 are the same (both 1. 1. 1. 2).
  • the CN1 or UNI server can judge according to which control plane interface the Path message comes from. Which overlay network the source edge node in the Path message belongs to.
  • the node addresses of EN2 and EN4 are the same, CN2 cannot determine which overlay network is the sink edge node of the UNI connection according to the address information of the sink edge node in the UNI_info object after receiving the Path message. To prevent this, the CN1 or UNI server needs to carry additional information in the Path message to indicate which source of the UNI connection and which overlay network the sink edge node belongs to.
  • One method is to carry the port identifier P1 of the source UNI link on the ingress core node side in the Path message, which can be placed in an ERO (Expl icit Route Object) object, such that the egress core node or the UNI
  • the server may determine, according to the configured UNI information table, that the source edge node of the connection is from overlay network A; another method is to add an overlay_network_ID object in the Path, and explicitly indicate that the source edge node is from the overlay. Network A.
  • the session identifier is converted at CN1, although the source and sink node addresses are still 1. 1. 1. 1 and 1. 1. 1. 2, but
  • the Path message also needs to carry the port identifier P2 or the overlay_network_ID object of the source UNI link on the ingress CN side to indicate that the source edge node is from overlay network B.
  • each node in the core network can correctly know that the three connections belong to different sessions, so these three connections can be established correctly.
  • a source node and a source edge node are one node, where the source node and the source edge node may not be one node, and the source edge node is an intermediate node of the entire label switching path, instead of establishing The initiator of the label switching path.
  • the source node sends a Path message to the source edge node hop by hop, in which the source node indicates in a normal manner.
  • First and last sections of the connection The source node and the sink node are respectively assigned, and the unique tunnel ID is allocated in the network where the source node is located.
  • the source edge node After receiving the Path message, the source edge node sends a Path message to the corresponding UNI server or sends the Path message to the UNI server.
  • the UNI server or the ingress core node processes the Path message.
  • the process of processing the Path message is the same as the embodiment in which the source node and the source edge node are one node in the foregoing embodiment.
  • the source node and the sink node are allocated, and the unique tunnel ID in the network domain where the source node is located is replaced with the address information of the ingress core node, the address information of the egress core node, and the tunnel identifier assigned by the ingress core node, except that the source is
  • the sink edge node is the sink node
  • the Path message carries the address information of the sink edge node, and in the scenario where the source node and the source edge node are not one node, if the source node is established Before the connection has determined the various network domains that the connection will go through, then P The ath message carries the ingress node address of each network domain, including the address of the ingress node (ie, the sink edge node) of the sink overlay network.
  • the UNI server may The path calculation server having the global path calculation capability is requested to perform the inter-domain path calculation, thereby determining the sink edge node node address.
  • the process of processing the Path message in the intermediate node in the core network is the same as that in the foregoing embodiment, and details are not described herein again.
  • the sink edge node After receiving the Path message, the sink edge node sends the Path message to the sink node hop by hop after processing the Path message. After receiving the Path message, the sink node returns the Resv message hop by hop, thereby establishing label switching from the source node to the sink node. path.
  • the method provided by the present invention has the beneficial effects of: deploying a UNI server in an overlay network and a core network, or expanding a function of a UNI server on an ingress core node and an egress core node, and configuring a UNI link in the UNI server.
  • the UNI server can implement the conversion of the address identifier in the Path message and the forwarding of the Path message, even in the scenario where the overlay network and the core network belong to different addressing spaces, through the UNI server.
  • an embodiment of the present invention provides an ingress core node, including: a receiving module 401, a converting module 402, and a sending module 403.
  • the receiving module 401 is configured to receive a first path message sent by the source edge node, where the first path message carries a first session identifier, where the first session identifier includes: address information of the source node, address information of the sink node, and a tunnel identifier assigned by the source node;
  • the conversion module 402 is configured to convert the first path message into a second path message, where the second path message carries the first session identifier and the second session identifier, where the second session identifier includes: the portal Core The address information of the node, the address information of the egress core node, and the tunnel identifier assigned by the ingress core node, so that the core node in the core network uses the second session identifier as the session identifier of the label switching path;
  • the sending module 403 is configured to send the second path message hop by hop to the egress core node, so that the egress core node restores the second path message to the first path message according to the first session identifier And sending the first path message to the sink node to establish a label switched path.
  • the conversion module 402 includes:
  • a determining unit configured to obtain address information of the sink edge node, search for pre-configured user network interface UNI information according to the address information of the sink edge node, and determine address information of the egress core node connected to the sink node;
  • the configured UNI information includes: address information of the source edge node, address information of an ingress core node corresponding to the source edge node, address information of the sink edge node, and an egress core node corresponding to the sink edge node. Address information;
  • an allocating unit configured to allocate a tunnel identifier to the label switching path according to the address information of the egress core node determined by the determining unit, to obtain a second session identifier, where the second session identifier includes: address information and an exit of the ingress core node Address information of the core node and a tunnel identifier assigned by the ingress core node;
  • an embodiment of the present invention further provides a system for establishing a label switching path, including: an ingress core node 601 and an egress core node 602 as described above;
  • the egress core node 602 is configured to receive a second path message sent by the ingress core node hop by hop according to the first session identifier, and restore the second path message to a first path message, where the first path is A message is sent to the sink node to establish a label switched path.
  • the device provided by the present invention has the following beneficial effects: the first session identifier carried in the first path message is converted into the second session identifier at the ingress core node, where the second session identifier includes: address information of the ingress core node, Address information of the egress core node and a tunnel identifier assigned by the ingress core node, where the second session identifier information is unique on the path from the ingress core node to the egress core node, and the core node in the core network is identified by the second session
  • the session identifier of the label switching path the problem that the nodes in the core network cannot correctly distinguish different label switching paths and cannot establish a correct label switching path due to the same address of the source node and the ingress core node is solved.
  • an embodiment of the present invention provides a server, including: a receiving module 501, a converting module 502, and a forwarding module 503.
  • the receiving module 501 is configured to receive a first path path message from the source edge node, where the first path message carries a first session identifier, where the first session identifier includes: address information of the source node, address information of the sink node And a tunnel identifier allocated by the source node;
  • the conversion module 502 is configured to convert the first path message into a second path message, where the second path message carries the first session identifier and the second session identifier, where the second session identifier includes: the portal The address information of the core node, the address information of the egress core node, and the tunnel identifier allocated by the ingress core node, so that the core node in the core network uses the second session identifier as the session identifier of the label switching path;
  • the forwarding module 503 is configured to send the second path message to the ingress core node, so that the ingress core node sends the second path message hop by hop to the egress core node, where the egress core node is configured according to The second session identifier restores the second path message to a first path message, and sends the first path message to the sink node to establish a label switching path.
  • the conversion module 502 includes:
  • a determining unit configured to obtain address information of the sink edge node, search for pre-configured user network interface UNI information according to the address information of the sink edge node, and determine an egress core node connected to the sink edge node;
  • the UNI information includes: address information of the source edge node, address information of an ingress core node corresponding to the source edge node, address information of the sink edge node, and an address of an egress core node corresponding to the sink edge node.
  • an allocating unit configured to allocate a tunnel identifier to the label switching path according to the address information of the egress core node, to obtain a second session identifier, where the second session identifier includes: address information of the ingress core node, and an address of the egress core node Information and a tunnel identifier assigned by the ingress core node;
  • a system for label switching path establishment includes: a server 701, an ingress core node 702, and a server 703 at an egress core node as described above;
  • the ingress core node 702 is configured to receive a second path message sent by the server 701, and send the second path The path message is hop by hop to the server 703 at the egress core node;
  • the server 703 at the egress core node is configured to restore the second path message to the first path message according to the first session identifier, and send the first path message to the sink node to establish a label switching path.
  • the system implementation of the present invention has the following advantages: the first session identifier carried in the first path message is converted into the second session identifier at the ingress core node, where the second session identifier includes: address information of the ingress core node, Address information of the egress core node and a tunnel identifier assigned by the ingress core node, where the second session identifier information is unique on the path from the ingress core node to the egress core node, and the core node in the core network is identified by the second session
  • the session identifier of the label switching path the problem that the nodes in the core network cannot correctly distinguish different label switching paths and cannot establish a correct label switching path due to the same address of the source node and the ingress core node is solved.
  • the device and the system provided in this embodiment may be the same as the method embodiment, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.

Landscapes

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

Abstract

Des modes de réalisation de la présente invention portent sur un procédé, un appareil et un système pour établir un chemin à commutation d'étiquettes, et concernent le domaine technique des communications. Le procédé comprend les opérations suivantes : un nœud de cœur d'entrée reçoit un premier message de chemin envoyé par un nœud de périphérie source, le premier message de chemin contenant un premier identificateur de session ; conversion du premier message de chemin en un second message de chemin, le second message de chemin contenant le premier identificateur de session et un second identificateur de session, et le second identificateur de session comprenant : des informations d'adresse du nœud de cœur d'entrée, des informations d'adresse d'un nœud de cœur de sortie, et un identificateur de tunnel attribué par le nœud de cœur d'entrée, de manière à ce qu'un nœud de cœur dans un cœur de réseau utilise le second identificateur de session comme identificateur de session pour le chemin à commutation d'étiquettes ; envoi du second message de chemin au nœud de cœur de sortie saut par saut, de manière à ce que le nœud de cœur de sortie récupère le premier message de chemin à partir du second message de chemin conformément au premier identificateur de session, et envoie le premier message de chemin à un nœud collecteur afin d'établir le chemin à commutation d'étiquettes.
PCT/CN2011/080305 2011-09-28 2011-09-28 Procédé, appareil et système pour établir un chemin à commutation d'étiquettes WO2012149777A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2011/080305 WO2012149777A1 (fr) 2011-09-28 2011-09-28 Procédé, appareil et système pour établir un chemin à commutation d'étiquettes
CN201180002218.5A CN102439919B (zh) 2011-09-28 2011-09-28 标签交换路径建立的方法、装置和系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/080305 WO2012149777A1 (fr) 2011-09-28 2011-09-28 Procédé, appareil et système pour établir un chemin à commutation d'étiquettes

Publications (1)

Publication Number Publication Date
WO2012149777A1 true WO2012149777A1 (fr) 2012-11-08

Family

ID=45986272

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/080305 WO2012149777A1 (fr) 2011-09-28 2011-09-28 Procédé, appareil et système pour établir un chemin à commutation d'étiquettes

Country Status (2)

Country Link
CN (1) CN102439919B (fr)
WO (1) WO2012149777A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103238299B (zh) * 2012-10-15 2015-04-01 华为技术有限公司 建立标签交换路径的方法、设备和系统
CN104144122B (zh) * 2013-05-10 2019-06-21 华为技术有限公司 建立标签交换路径的方法、设备及系统
CN103841022B (zh) * 2014-03-12 2017-04-05 华为技术有限公司 用于建立隧道的方法及装置
CN108377495B (zh) 2016-10-31 2021-10-15 华为技术有限公司 一种数据传输方法、相关设备及系统
CN106656802B (zh) * 2016-12-21 2019-06-21 北京格林伟迪科技股份有限公司 一种端到端隧道生成方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101030914A (zh) * 2007-03-31 2007-09-05 华为技术有限公司 一种保证二级运营商公网带宽的方法、路由器和系统
CN101163110A (zh) * 2007-11-30 2008-04-16 华为技术有限公司 部署流量工程隧道的方法及装置
US20090323698A1 (en) * 2008-06-26 2009-12-31 Cisco Technology, Inc. Pure control-plane approach for on-path connection admission control operations in multiprotocol label switching virtual private networks
CN101984595A (zh) * 2010-11-03 2011-03-09 北京星网锐捷网络技术有限公司 跨区域流量工程隧道建立方法、系统及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ITMI20051570A1 (it) * 2005-08-12 2007-02-13 Alcatel Italia Metodo di monitoraggio di una connessione tandem in una rete di telecomunicazioni di tipo mpls
CN101771577B (zh) * 2008-12-31 2012-10-17 华为技术有限公司 一种为双向lsp建立双向转发检测的方法、系统及设备
CN102136991B (zh) * 2010-07-02 2013-10-09 华为技术有限公司 在标签交换路径上配置隧道的方法和节点
CN102130829B (zh) * 2010-12-28 2013-06-05 华为技术有限公司 一种lsp的建立方法、装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101030914A (zh) * 2007-03-31 2007-09-05 华为技术有限公司 一种保证二级运营商公网带宽的方法、路由器和系统
CN101163110A (zh) * 2007-11-30 2008-04-16 华为技术有限公司 部署流量工程隧道的方法及装置
US20090323698A1 (en) * 2008-06-26 2009-12-31 Cisco Technology, Inc. Pure control-plane approach for on-path connection admission control operations in multiprotocol label switching virtual private networks
CN101984595A (zh) * 2010-11-03 2011-03-09 北京星网锐捷网络技术有限公司 跨区域流量工程隧道建立方法、系统及装置

Also Published As

Publication number Publication date
CN102439919A (zh) 2012-05-02
CN102439919B (zh) 2014-04-16

Similar Documents

Publication Publication Date Title
EP3731474B1 (fr) Contrôleurs centralisés d'éléments de calcul de chemin (pcecc) pour services de réseau
JP4328478B2 (ja) ラベル転送ネットワークにおける経路変更方法並びにラベルスイッチングノード及び管理ノード
CN111385165A (zh) 配置无缝双向转发检测sbfd机制的方法和装置
WO2016115823A1 (fr) Procédé et appareil pour transférer une construction d'étiquette et paquet d'étiquettes
WO2015042824A1 (fr) Procédé et dispositif d'établissement de chemin inter-domaine
JP2009512287A (ja) イーサネットのｇｍｐｌｓ制御
JP2006211661A (ja) Ｍｐｌｓ基盤のｖｐｎ提供装置及びｖｐｎ提供方法
WO2011103781A2 (fr) Procédé, dispositif pour la mise en oeuvre de la séparation d'identificateur et de localisateur et procédé d'encapsulation de données
WO2015054904A1 (fr) Procédé, contrôleur, dispositif de transmission, et système de réseau pour la transmission de paquets
WO2005006670A1 (fr) Procede pour etablir une session dans un reseau a commutation par etiquette et noeud a commutation par etiquette
WO2012149777A1 (fr) Procédé, appareil et système pour établir un chemin à commutation d'étiquettes
JP2003032280A (ja) コネクション型通信ネットワークにおけるリンク識別子の割当システム
US7463580B2 (en) Resource sharing among network tunnels
JP2005295551A (ja) 移動ネットワーク通信におけるハンドオーバー時のパス形成方法
US20140185607A1 (en) Communication system, communication path establishing method and management server
US8902909B2 (en) Method, system, and device for implementing service forwarding
WO2011147341A1 (fr) Procédé et dispositif de réseau pour distribuer des étiquettes de commutation multi-protocole par étiquette
US20090010201A1 (en) Mobile Communication Access System, Packet Transfer Device, and Path Re-Establishing Method
WO2015024440A1 (fr) Procédé et système d'obtention de la valeur de surdébit de liaison d'une liaison ip
JP2004159112A (ja) 通信制御システム、通信制御方法、これらに用いて好適なルーティング制御装置及びルータ装置
CN101656740A (zh) 控制标签发送的方法和路由设备
WO2008011771A1 (fr) Procédé, équipement de réseau et système permettant d'établir une voie de commutation dans un réseau internet optique
JPWO2005079022A1 (ja) パケット通信ネットワーク、経路制御サーバ、経路制御方法、パケット転送装置、アドミッション制御サーバ、光波長パス設定方法、プログラム、および記録媒体
WO2004102904A1 (fr) Procede pour mettre en place un canal dans un reseau de communication, la communication etant etablie a travers des couches, et dispositif de communication
WO2022142932A1 (fr) Procédé de traitement d'itinéraire et appareil associé et système de réseau

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180002218.5

Country of ref document: CN

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

Ref document number: 11864813

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11864813

Country of ref document: EP

Kind code of ref document: A1