CN114221891B - Binding segment identification splicing method, routing reflector, autonomous domain and cross-domain network - Google Patents
Binding segment identification splicing method, routing reflector, autonomous domain and cross-domain network Download PDFInfo
- Publication number
- CN114221891B CN114221891B CN202111515529.3A CN202111515529A CN114221891B CN 114221891 B CN114221891 B CN 114221891B CN 202111515529 A CN202111515529 A CN 202111515529A CN 114221891 B CN114221891 B CN 114221891B
- Authority
- CN
- China
- Prior art keywords
- service
- autonomous domain
- border gateway
- gateway protocol
- autonomous
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
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/34—Source routing
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The disclosure relates to a binding segment identification splicing method, a routing reflector, an autonomous domain and a cross-domain network. The binding segment identification splicing method comprises the following steps: the routing reflector acquires the autonomous domain path attribute in a first border gateway protocol message sent by the service terminal equipment and determines the sequence among autonomous domains; the routing reflector receives a second border gateway protocol message carrying a binding segment identification type length value, an autonomous domain subtype length value connected with service starting point equipment and an autonomous domain subtype length value connected with service end point equipment, reads corresponding fields of the second border gateway protocol message, and determines a connection relation between autonomous domains involved in service; and the route reflector completes the splicing of the binding section identifiers according to the sequence and the connection relation. The BSID splicing work can be carried out by the RR equipment by carrying out function enhancement on the RR equipment.
Description
Technical Field
The disclosure relates to the technical field of communication, and in particular relates to a binding segment identification splicing method, a routing reflector, an autonomous domain and a cross-domain network.
Background
In the Option C cross-domain scenario, BSID (Binding Segment ID, binding segment identifier) in the related art technical solution is spliced by the controller and then sent to the headend node of the service (i.e. service origin device).
Disclosure of Invention
The inventors found through research that: related art uses controllers to make BSID splice, and one of the two controllers needs to be selected to complete the work, which involves a multi-domain management problem. The related art network device cannot complete BSID splicing work.
In view of at least one of the above technical problems, the present disclosure provides a binding segment identification splicing method, a routing Reflector, an autonomous domain, and a cross-domain network, which perform functional enhancement on RR (Router Reflector) devices, and may perform BSID splicing work by the routing Reflector.
According to one aspect of the present disclosure, there is provided a binding segment identification splicing method, including:
the routing reflector acquires the autonomous domain path attribute in a first border gateway protocol message sent by the service terminal equipment and determines the sequence among autonomous domains;
the routing reflector receives a second border gateway protocol message carrying a binding segment identification type length value, an autonomous domain subtype length value connected with service starting point equipment and an autonomous domain subtype length value connected with service end point equipment, reads corresponding fields of the second border gateway protocol message, and determines a connection relation between autonomous domains involved in service;
And the route reflector completes the splicing of the binding section identifiers according to the sequence and the connection relation.
In some embodiments of the present disclosure, the route reflector obtaining an autonomous domain path attribute in a first border gateway protocol packet of a service endpoint device, and determining a sequence between autonomous domains includes:
under the condition that a virtual private network segment identifier sent by service end point equipment is received, extracting service start point information in a first border gateway protocol message by a routing reflector, and storing the service start point information as identifier information;
the routing reflector extracts autonomous domain path attributes from a first border gateway protocol message carrying a virtual private network segment identifier, and determines the sequence among autonomous domains from the autonomous domain path attributes.
In some embodiments of the present disclosure, the routing reflector completing the splicing of the binding segment identifiers according to the connection relationship and the sequencing includes:
after the routing reflector determines that the message is a message sent to the same network equipment according to the segment identifiers, the routing reflector determines the sequence of binding the segment identifiers according to the autonomous domain path attributes of the received first border gateway protocol message and the second border gateway protocol message, and completes the splicing work.
In some embodiments of the present disclosure, the reading the corresponding field of the second border gateway protocol packet, and determining the connection relationship between the autonomous domains involved in the service includes:
the routing reflector determines an autonomous domain from which the second border gateway protocol message comes from the second border gateway protocol message through the autonomous domain path attribute;
the route reflector determines the section identifiers of the service starting point device and the service end point device of the service path related to the autonomous domain where the service corresponding to the binding section identifier is located from the coded content of the length value of the binding section identifier type;
the routing reflector determines the autonomous domain connected by the service starting point device and the service end point device of the autonomous domain according to the autonomous domain subtype length value connected by the service starting point device and the autonomous domain subtype length value connected by the service end point device.
In some embodiments of the present disclosure, the binding segment identification splicing method further includes:
and the routing reflector sends the spliced binding segment identification to corresponding equipment according to the identification information.
In some embodiments of the present disclosure, the route reflector obtaining an autonomous domain path attribute in a first border gateway protocol message of a service endpoint device, determining a precedence order between autonomous domains includes:
The route reflector receives a first border gateway protocol message carrying a virtual private network segment identifier, which is sent to the service starting point equipment by the service ending point equipment;
the routing reflector acquires an autonomous domain number passing through when the message is transmitted from an autonomous domain path attribute of the first border gateway protocol message;
the routing reflector acquires first service type information related to the virtual private network segment identifier from a first border gateway protocol message;
the route reflector acquires the section identification of the service terminal equipment from the first border gateway protocol message;
the router reflector takes the virtual private network segment identifier as a stack bottom segment identifier spliced by the binding segment identifiers;
the routing reflector determines that the destination to which the private network segment identification information is sent is a service origin device.
In some embodiments of the present disclosure, the reading the corresponding field of the second border gateway protocol packet, and determining the connection relationship between the autonomous domains involved in the service includes:
the routing reflector acquires an autonomous domain number where the binding section identifier is located from an autonomous domain path attribute of the second border gateway protocol message;
the routing reflector obtains second service type information related to the binding segment identification from the binding segment identification type length value.
In some embodiments of the present disclosure, the completing the splicing of the binding segment identifiers by the routing reflector according to the sequence and the connection relationship includes:
comparing the autonomous domain number acquired from the first border gateway protocol message with the autonomous domain number acquired from the second border gateway protocol message, and comparing the first service type information with the second service type information;
determining a binding segment identifier corresponding to each autonomous domain passed by the message transmission;
and sequencing the binding segment identifiers of each autonomous domain according to the path attribute of the autonomous domain coordinated by the first border gateway, pressing the binding segment identifiers into the stack bottom according to the transmission sequence, and completing the binding segment identifier splicing.
In some embodiments of the present disclosure, the determining, for each autonomous domain that passes through when the message is transmitted, the binding segment identifier corresponding to the autonomous domain includes:
if the autonomous domain acquired from the second border gateway protocol message is the autonomous domain where the service starting point device is located, and the first service type information and the second service type information are the same, judging whether the first condition and the second condition are met, wherein the first condition is that the service starting point device section identifier acquired from the binding section identifier type length value is consistent with the virtual private network section identifier of the routing reflector, and the second condition is that the autonomous domain where the service starting point device is connected acquired from the autonomous domain subtype length value connected with the service starting point device contains the autonomous domain where the service end point device is located;
And if the first condition and the second condition are met, extracting the binding segment identifier corresponding to the autonomous domain from the length value of the binding segment identifier type.
In some embodiments of the present disclosure, the determining, for each autonomous domain that passes through when the message is transmitted, the binding segment identifier corresponding to the autonomous domain includes:
if the autonomous domain acquired from the second border gateway protocol message is the autonomous domain where the service end point device is located, and the first service type information and the second service type information are the same, judging whether a third condition and a fourth condition are met, wherein the third condition is that the service end point device section identifier acquired from the binding section identifier type length value is consistent with the virtual private network section identifier of the routing reflector, and the fourth condition is that the autonomous domain where the service end point device is connected acquired from the autonomous domain subtype length value connected with the service start point device contains the autonomous domain where the service start point device is located;
and if the third condition and the fourth condition are met, extracting the binding segment identifier corresponding to the autonomous domain from the length value of the binding segment identifier type.
According to another aspect of the present disclosure, there is provided a routing reflector comprising:
the first message reading module is used for acquiring the autonomous domain path attribute in the first border gateway protocol message sent by the service terminal equipment and determining the sequence among the autonomous domains;
The second message reading module is used for receiving a second border gateway protocol message carrying a binding section identification type length value, an autonomous domain subtype length value connected with service starting point equipment and an autonomous domain subtype length value connected with service end point equipment, reading corresponding fields of the second border gateway protocol message and determining a connection relation between autonomous domains related to the service;
and the segment identifier splicing module is used for finishing splicing the binding segment identifiers according to the sequence and the connection relation.
In some embodiments of the present disclosure, the routing reflector is configured to perform operations for implementing the binding segment identification stitching method described in any of the embodiments above.
According to another aspect of the present disclosure, there is provided a routing reflector comprising:
a memory for storing instructions;
and the processor is used for executing the instructions to enable the routing reflector to execute the operation of realizing the binding segment identification splicing method according to any embodiment.
According to another aspect of the present disclosure, there is provided an autonomous domain comprising a routing reflector as described in any of the embodiments above.
According to another aspect of the present disclosure, there is provided a cross-domain network comprising a plurality of autonomous domains as described in any of the embodiments above.
According to another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium storing computer instructions which, when executed by a processor, implement a binding segment identification splicing method as described in any of the embodiments above.
According to the method and the system, the RR equipment is subjected to function enhancement, and BSID splicing work can be performed by the RR equipment, so that the deployment efficiency of a cross-domain networking scheme is greatly improved, and the cost brought by upgrading a large amount of equipment is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings may be obtained according to these drawings without inventive effort to a person of ordinary skill in the art.
Fig. 1 is a schematic diagram of some embodiments of a binding segment identification stitching method of the present disclosure.
Fig. 2 is a schematic diagram of some embodiments of a cross-domain network of the present disclosure.
Fig. 3 is a schematic diagram of some embodiments of a routing reflector of the present disclosure.
Fig. 4 is a schematic structural view of yet other embodiments of the routing reflector of the present disclosure.
Detailed Description
The following description of the technical solutions in the embodiments of the present disclosure will be made clearly and completely with reference to the accompanying drawings in the embodiments of the present disclosure, and it is apparent that the described embodiments are only some embodiments of the present disclosure, not all embodiments. The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. Based on the embodiments in this disclosure, all other embodiments that a person of ordinary skill in the art would obtain without making any inventive effort are within the scope of protection of this disclosure.
The relative arrangement of the components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless it is specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective parts shown in the drawings are not drawn in actual scale for convenience of description.
Techniques, methods, and apparatus known to one of ordinary skill in the relevant art may not be discussed in detail, but should be considered part of the specification where appropriate.
In all examples shown and discussed herein, any specific values should be construed as merely illustrative, and not a limitation. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further discussion thereof is necessary in subsequent figures.
The inventors noted that: related art, by using controllers to perform BSID splicing, one of the two controllers must be selected to complete the task, which involves a multi-domain management problem. In addition, the related art controllers do not define standardized interfaces for coordinating and transmitting BSIDs, and only point-to-point development is used.
The inventors also noted that: the reason why the related art network device cannot complete BSID splicing operation is mainly as follows:
first, there is currently no mechanism to transmit BSID separately across domains, which needs to be transmitted with SID-List (segment identification List).
Second, network devices within a certain autonomous domain cannot learn the topology of the entire network, and cannot learn in which order the BSIDs of the autonomous domains should be spliced.
In view of at least one of the above technical problems, the present disclosure provides a binding segment identification splicing method, a routing reflector, an autonomous domain, and a cross-domain network. The present disclosure is illustrated by the following specific examples.
Fig. 1 is a schematic diagram of some embodiments of a binding segment identification stitching method of the present disclosure. Preferably, the present embodiment may be performed by the routing reflector of the present disclosure. The method may comprise at least one of steps 11 to 13, wherein:
and 11, acquiring an autonomous domain path attribute in a first BGP (Border Gateway Protocol ) message sent by service end point equipment by RR (Router Reflector), and determining the sequence among all autonomous domains.
In some embodiments of the present disclosure, step 11 may include: when the RR device receives a VPN (Virtual Private Network ) SID sent by the service end device, it extracts service start information in the message and stores the service start information AS an identification information, and extracts an as_path attribute from a BGP message carrying the VPN SID, and learns the connection order between ases (Head Connected Autonomous System, autonomous domains) from the as_path attribute.
In some embodiments of the present disclosure, step 11 may include: under the condition that a virtual private network segment identifier sent by service end point equipment is received, extracting service start point information in a first border gateway protocol message by a routing reflector, and storing the service start point information as identifier information; the routing reflector extracts autonomous domain path attributes from a first border gateway protocol message carrying a virtual private network segment identifier, and determines the sequence among autonomous domains from the autonomous domain path attributes.
In some embodiments of the present disclosure, step 11 may include: at least one of steps 111 to 116, wherein:
step 111, the route reflector receives a first border gateway protocol packet carrying a virtual private network segment identifier sent by the service end point device to the service start point device.
Step 112, the routing reflector obtains the autonomous domain number passed by the message when transmitting from the autonomous domain path attribute of the first border gateway protocol message.
In step 113, the routing reflector obtains first service type information related to the virtual private network segment identifier from the first border gateway protocol message.
Step 114, the route reflector obtains the segment identifier of the service end point device from the first border gateway protocol message.
In step 115, the router reflector uses the virtual private network segment identifier as a stack bottom segment identifier for binding segment identifier concatenation.
The routing reflector determines the destination to which the private network segment identification information is sent as the origin of service device, step 116.
Step 12, the route reflector receives a second border gateway protocol message carrying a binding segment identification type length value, an autonomous domain subtype length value connected with the service starting point equipment and an autonomous domain subtype length value connected with the service end point equipment; and reading the corresponding fields of the second border gateway protocol message, and determining the connection relation between the autonomous domains involved in the service.
In some embodiments of the present disclosure, a BSID transmission mechanism based on BGP SRv6 (Segment Routing IPv, segment routing based on IPv6 forwarding plane) is provided, where a BGP update message is enabled to carry a BSID, and the problem that the BSID lacks a cross-domain transmission mechanism is solved by newly defining two Sub-TLVs, namely a Binding-SID (Type Length Value ) and a Head Connected AS Sub-TLV (Head Connected Autonomous System TLV Sub-TLV for service origin device connection), and a Tail Connected AS Sub-TLV (autonomous domain subtype length value for service end device connection), where the update message is used to exchange routing information between peers.
In some embodiments of the present disclosure, table 1 is the encoded format of the Binding-SID TLV. As shown in table 1, the Binding-SID TLV includes an 8-bit Type field, a 16-bit Length field, an 8-bit RESERVED field, a 128-bit BSID field, a 128-bit Head End SID (service start device segment identification) field, a 128-bit Tail End SID (service End device segment identification) field, and a 32-bit Color field, wherein Color is used to identify the service Type of the BSID.
TABLE 1
In some embodiments of the present disclosure, table 2 is the encoded format of the Head Connected AS Sub-TLV. As shown in table 2, the Head Connected AS Sub-TLV includes an 8-bit Type field, a 16-bit Length field, and a capacity-optional Head Connected AS (autonomous domain for service origin connection) field.
TABLE 2
In some embodiments of the present disclosure, table 3 is the encoded format of the Tail Connected AS Sub-TLV. As shown in table 2, the Tail Connected AS Sub-TLV includes an 8-bit Type field, a 16-bit Length field, and a capacity-optional Tail Connected AS (autonomous domain for service end point connection) field.
TABLE 3 Table 3
In some embodiments of the present disclosure, step 12 may include: the routing reflector determines an autonomous domain from which the second border gateway protocol message comes from the second border gateway protocol message through the autonomous domain path attribute; the route reflector determines the section identifiers of the service starting point device and the service end point device of the service path related to the autonomous domain where the service corresponding to the binding section identifier is located from the coded content of the length value of the binding section identifier type; the routing reflector determines the autonomous domain connected by the service starting point device and the service end point device of the autonomous domain according to the autonomous domain subtype length value connected by the service starting point device and the autonomous domain subtype length value connected by the service end point device.
In some embodiments of the present disclosure, step 12 may include: when RR equipment receives BGP message with Binding-SID TLV, knowing from which AS the message comes through AS_PATH attribute; the service corresponding to the BSID, the SIDs of the head and tail endpoints of the related service paths in the AS are known from the encoded content of the Binding-SID TLV, and which ASs the head and tail endpoints of the AS are connected to are known from the Head Connected AS Sub-TLV and the Tail Connected AS Sub-TLV.
In some embodiments of the present disclosure, step 12 may include: the routing reflector acquires an autonomous domain number where the binding section identifier is located from an autonomous domain path attribute of the second border gateway protocol message; the routing reflector obtains second service type information related to the binding segment identification from the binding segment identification type length value.
And 13, the route reflector completes the splicing of the binding section identifiers according to the sequence and the connection relation.
In some embodiments of the present disclosure, after step 13, the binding segment identification splicing method may further include: and the routing reflector sends the spliced binding segment identification to corresponding equipment according to the identification information.
In some embodiments of the present disclosure, step 13 may include: after the routing reflector determines that the message is a message sent to the same network equipment according to the segment identifiers, the routing reflector determines the sequence of binding the segment identifiers according to the autonomous domain path attributes of the received first border gateway protocol message and the second border gateway protocol message, and completes the splicing work.
In some embodiments of the present disclosure, step 13 may include: after the RR device determines that the message is sent to the same network device according to the identifier, the sequence of the BSIDs can be determined and the splicing work can be completed according to the AS_PATH attribute of the received BGP message carrying the VPN SID and the received BGP message carrying the Binding-SID TLV.
In some embodiments of the present disclosure, in step 13, the step of completing the splicing of the binding section identifier by the routing reflector according to the sequence and the connection relationship may include at least one of steps 131 to 133, wherein:
step 131, comparing the autonomous domain number obtained from the first border gateway protocol message with the autonomous domain number obtained from the second border gateway protocol message, and comparing the first service type information with the second service type information.
Step 132, for each autonomous domain passed during message transmission, determining the binding segment identifier corresponding to the autonomous domain.
In some embodiments of the present disclosure, step 132 may include: if the autonomous domain acquired from the second border gateway protocol message is the autonomous domain where the service starting point device is located, and the first service type information and the second service type information are the same, judging whether the first condition and the second condition are met, wherein the first condition is that the service starting point device section identifier acquired from the binding section identifier type length value is consistent with the virtual private network section identifier of the routing reflector, and the second condition is that the autonomous domain where the service starting point device is connected acquired from the autonomous domain subtype length value connected with the service starting point device contains the autonomous domain where the service end point device is located; and if the first condition and the second condition are met, extracting the binding segment identifier corresponding to the autonomous domain from the length value of the binding segment identifier type.
In other embodiments of the present disclosure, step 132 may include: if the autonomous domain acquired from the second border gateway protocol message is the autonomous domain where the service end point device is located, and the first service type information and the second service type information are the same, judging whether a third condition and a fourth condition are met, wherein the third condition is that the service end point device section identifier acquired from the binding section identifier type length value is consistent with the virtual private network section identifier of the routing reflector, and the fourth condition is that the autonomous domain where the service end point device is connected acquired from the autonomous domain subtype length value connected with the service start point device contains the autonomous domain where the service start point device is located; and if the third condition and the fourth condition are met, extracting the binding segment identifier corresponding to the autonomous domain from the length value of the binding segment identifier type.
And step 133, sorting the binding segment identifiers of each autonomous domain according to the autonomous domain path attribute cooperated with the first border gateway, pressing the binding segment identifiers into the stack bottom according to the transmission sequence, and completing the binding segment identifier splicing.
According to the embodiment of the disclosure, the RR equipment can carry out BSID splicing work by carrying out function enhancement on the RR equipment, so that the deployment efficiency of a cross-domain networking scheme is greatly improved, and the cost brought by upgrading a large amount of equipment is reduced.
The above embodiments of the present disclosure provide a functional enhanced RR device capable of receiving and reading corresponding fields in a Binding-SID TLV, a Head Connected AS Sub-TLV and a Tail Connected AS Sub-TLV, so that a network device in a certain autonomous domain can learn a connection relationship of an AS related to a service, identify a network device from which the service starts, and directly complete a splicing requirement of a BSID on the RR device, and transfer the spliced BSID to a corresponding destination device according to identification information.
According to another aspect of the present disclosure, there is provided an autonomous domain comprising a routing reflector as described in any of the embodiments of the present disclosure (e.g., the embodiment of fig. 3 or fig. 4).
According to another aspect of the present disclosure, there is provided a cross-domain network comprising a plurality of autonomous domains as described in any embodiment of the present disclosure.
Fig. 2 is a schematic diagram of some embodiments of a cross-domain network of the present disclosure. Fig. 2 presents a schematic view of a SRv6 cross-domain networking scenario. Fig. 2 is also a schematic diagram of some embodiments of the autonomous domain of the present disclosure. AS shown in fig. 2, there are two autonomous domains AS1 and AS2 in the network, they cross domains by means of Option C, ASBRs (Autonomous System Boundary Router, autonomous domain border Router) of AS1 and AS2 are ASBR1 and ASBR2, respectively, and the user accesses through network devices R1 and R2, where R1 and R2 are routers. The present disclosure assumes that the traffic flow direction to be opened is shown by solid arrows R1 to R2 in fig. 2, i.e., R1 is a service start device, R2 is a service end device, RR1 is a device with BSID splicing capability, and CE device is a Customer Edge device.
Next, the binding segment identification splicing method of the embodiment of fig. 1 of the present disclosure is adopted to perform binding segment identification splicing on the cross-domain network of the embodiment of fig. 2. Particular embodiments may include at least one of steps 1 through 3, wherein:
step 1, when a service is opened, R2 sends a BGP message carrying a VPN SID to R1, where the message passes through RR1, and after RR1 receives the message, at least one step from step 1.1 to step 1.5 is performed, where:
step 1.1, the AS number passed by the message in transmission is obtained from the AS_PATH attribute of the BGP message, in this example, the AS_PATH should include AS1 and AS2.
Step 1.2, obtain Color (used for identifying the service type of VPN SID) related to VPN SID from it.
Step 1.3, obtaining the SID of the service tail-end node.
At step 1.4, RR1 will use VPN SID as the stack bottom SID for BSID concatenation.
In step 1.5, RR1 marks that the VPN SID information is sent to R1, and can ensure that the VPN SID information is also sent to R1 after being spliced.
Step 2, after receiving the BGP message carrying the Binding-SID TLV, the rr1 performs at least one step of steps 2.1 to 2.3, where:
step 2.1, extracting the AS number where the BSID is located from the AS_PATH attribute of the BGP message.
And 2.2, acquiring Color from the Binding-SID TLV.
Step 2.3, comparing the AS number obtained in step 2.1 with the AS number passed by the VPN SID of R1 marked above, and comparing the Color obtained from step 2.2 with the Color of the VPN SID of R1 marked above:
if as=as1 and Color value is the same, the Head End SID obtained from the Binding-SID TLV is compared with the VPN SID of R1 to see if the two are identical. And Head Connected AS is also retrieved from the Head Connected AS Sub-TLV to see if AS2 is contained therein. If both conditions are met, acquiring the BSID from the Binding-SID TLV; if different, no operation is performed.
If as=as2 and Color values are the same, then the Tail End SID is obtained from the Binding-SID TLV and compared with the VPN SID to see if they are the same. And Tail Connected AS is also retrieved from the Tail Connected AS Sub-TLV to see if AS1 is contained therein. If both conditions are met, acquiring the BSID from the Binding-SID TLV; if different, no operation is performed.
And 3, the RR1 sorts the BSID1 and the BSID2 according to the AS_PATH attribute in the BGP message carrying the VPN SID, presses the BSID1 and the BSID2 into the stack bottom according to the transmission sequence, and completes BSID splicing. Then RR1 confirms that the spliced BSID should be transmitted to R1 according to the previous identification information, and finally transmits the BSID to R1.
The RR device of the above embodiment of the present disclosure can read the corresponding field of the Binding-SID TLV from the BGP message, and obtain the BSID of each AS, the service corresponding to the BSID, the SID of the head and tail end points of the related service paths in the AS, and which AS the tail end is connected to according to the content in the field.
The controller of the above embodiment of the present disclosure does not need to participate in the splicing work of BSIDs any more, and the above embodiment of the present disclosure simplifies the functions of the controller.
When related services are opened, the embodiment of the disclosure can directly complete BSID splicing and issuing by the RR equipment, and the controller only needs to issue the generated BSID to the RR equipment of the management domain.
Fig. 3 is a schematic diagram of some embodiments of a routing reflector of the present disclosure. As shown in fig. 3, the routing reflector of the present disclosure may include a first message reading module 31, a second message Wen Douqu module 32, and a segment identification concatenation module 33, where:
the first message reading module 31 is configured to obtain an autonomous domain path attribute in a first border gateway protocol message sent by the service end point device, and determine a sequence between the autonomous domains.
In some embodiments of the present disclosure, the first message reading module 31 may be configured to extract, when receiving the vpn segment identifier sent by the service end device, service start point information in the first border gateway protocol message, and store the service start point information as one identifier information; extracting autonomous domain path attributes from a first border gateway protocol message carrying a virtual private network segment identifier, and determining the sequence among autonomous domains from the autonomous domain path attributes.
In some embodiments of the present disclosure, the first message reading module 31 may be configured to receive a first border gateway protocol message carrying a virtual private network segment identifier, where the first border gateway protocol message is sent by a service end point device to a service start point device; acquiring an autonomous domain number passing through when the message is transmitted from an autonomous domain path attribute of a first border gateway protocol message; acquiring first service type information related to the virtual private network segment identifier from a first border gateway protocol message; acquiring a section identifier of service terminal equipment from a first border gateway protocol message; taking the virtual private network segment identifier as a stack bottom segment identifier spliced by the binding segment identifiers; and determining the destination of the private network segment identification information as the service starting point equipment.
The second message Wen Douqu module 32 is configured to receive a second border gateway protocol message carrying a binding segment identifier type length value, an autonomous domain subtype length value connected to a service start point device, and an autonomous domain subtype length value connected to a service end point device, read a corresponding field of the second border gateway protocol message, and determine a connection relationship between autonomous domains involved in the service.
In some embodiments of the present disclosure, the second packet Wen Douqu module 32 may be configured to determine, from the second border gateway protocol packet, an autonomous domain from which the second border gateway protocol packet originates, by an autonomous domain path attribute; determining the section identifiers of the service starting point device and the service end point device of the service path related to the autonomous domain where the service corresponding to the binding section identifier is located from the coded content of the length value of the binding section identifier type; and determining the autonomous domain connected with the service starting point equipment and the service end point equipment of the autonomous domain according to the autonomous domain subtype length value connected with the service starting point equipment and the autonomous domain subtype length value connected with the service end point equipment.
In some embodiments of the present disclosure, the second packet Wen Douqu module 32 may be configured to obtain, from the autonomous domain path attribute of the second border gateway protocol packet, an autonomous domain number where the binding segment identifier is located; and acquiring second service type information related to the binding segment identifier from the length value of the binding segment identifier type.
And the segment identifier splicing module 33 is configured to complete splicing of the binding segment identifiers according to the sequence and the connection relationship.
In some embodiments of the present disclosure, the segment identifier splicing module 33 may be configured to determine, after determining that the message is a message sent to the same network device according to the segment identifier, an order of binding segment identifiers according to the autonomous domain path attributes of the received first border gateway protocol message and the second border gateway protocol message, and complete the splicing operation.
In some embodiments of the present disclosure, the segment identification concatenation module 33 may be configured to compare the autonomous domain number acquired from the first border gateway protocol packet with the autonomous domain number acquired from the second border gateway protocol packet, and compare the first service type information with the second service type information; determining a binding segment identifier corresponding to each autonomous domain passed by the message transmission; and sequencing the binding segment identifiers of each autonomous domain according to the path attribute of the autonomous domain coordinated by the first border gateway, pressing the binding segment identifiers into the stack bottom according to the transmission sequence, and completing the binding segment identifier splicing.
In some embodiments of the present disclosure, the segment identification splicing module 33 may be configured to determine whether a first condition and a second condition are met if an autonomous domain acquired from the second border gateway protocol packet is an autonomous domain where a service start device is located, and the first service type information and the second service type information are the same, where the first condition is that a service start device segment identifier acquired from the binding segment identification type length value is consistent with a virtual private network segment identifier of the route reflector, and the second condition is that an autonomous domain where a service start device acquired from an autonomous domain subtype length value connected with the service start device is located includes an autonomous domain where a service end device is located; and if the first condition and the second condition are met, extracting the binding segment identifier corresponding to the autonomous domain from the length value of the binding segment identifier type.
In other embodiments of the present disclosure, the segment identification splicing module 33 may be configured to determine whether a third condition and a fourth condition are met if the autonomous domain acquired from the second border gateway protocol packet is the autonomous domain where the service end device is located, and the first service type information and the second service type information are the same, where the third condition is that the service end device segment identification acquired from the binding segment identification type length value is consistent with the virtual private network segment identification of the routing reflector, and the fourth condition is that the autonomous domain where the service end device is connected acquired from the autonomous domain subtype length value connected with the service start device includes the autonomous domain where the service start device is located; and if the third condition and the fourth condition are met, extracting the binding segment identifier corresponding to the autonomous domain from the length value of the binding segment identifier type.
In some embodiments of the present disclosure, the routing reflector may be further configured to send the spliced binding segment identification to a corresponding device according to the identification information.
In some embodiments of the present disclosure, the routing reflector is configured to perform operations to implement the binding segment identification stitching method described in any of the embodiments above (e.g., the embodiment of fig. 1).
The above embodiments of the present disclosure provide an RR device with enhanced functionality, which can identify a destination device for BGP packet sending, and extract the contents in BSID, head End SID, tail End SID, color field from the Binding-SID TLV of BGP packet.
The RR device of the foregoing embodiment of the present disclosure can match received messages, and when the matched message is a BGP message sent to the same network device, the RR device will match the BSID and VPN SID according to the as_path and Color, determine the BSID sequence, and perform BSID splicing.
The RR device of the above embodiment of the present disclosure may send the spliced BSID to the corresponding network device according to the destination device identified by the BGP message.
Fig. 4 is a schematic structural view of yet other embodiments of the routing reflector of the present disclosure. As shown in fig. 4, the routing reflector includes a memory 41 and a processor 42.
The memory 41 is for storing instructions and the processor 42 is coupled to the memory 41, the processor 42 being configured to implement the binding segment identification concatenation method described in any of the embodiments described above (e.g. the embodiment of fig. 1) based on the instructions stored by the memory.
As shown in fig. 4, the routing reflector further comprises a communication interface 43 for information interaction with other devices. Meanwhile, the routing reflector further comprises a bus 44, and the processor 42, the communication interface 43 and the memory 41 are in communication with each other through the bus 44.
The memory 41 may comprise a high-speed RAM memory or may further comprise a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 41 may also be a memory array. The memory 41 may also be partitioned and the blocks may be combined into virtual volumes according to certain rules.
Further, the processor 42 may be a central processing unit CPU, or may be an application specific integrated circuit ASIC, or one or more integrated circuits configured to implement embodiments of the present disclosure.
The above embodiments of the present disclosure propose a functionally enhanced RR device that can understand the connection relationship between autonomous domains by extracting the corresponding fields therein after receiving BGP messages containing a Binding-SID TLV, a Head Connected AS Sub-TLV and a Tail Connected AS Sub-TLV.
On the basis, the RR device of the embodiment of the disclosure can combine AS_PATH attribute carried in SID transfer message of service terminal device to determine the sequence among autonomous domains, complete the splicing of BSIDs, and send the spliced BSIDs to corresponding devices according to the identification information.
According to another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium storing computer instructions which, when executed by a processor, implement a binding segment identification splicing method as described in any of the embodiments (e.g., the embodiment of fig. 1).
It will be apparent to those skilled in the art that embodiments of the present disclosure may be provided as a method, apparatus, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The routing reflectors described above may be implemented to include general purpose processors, programmable Logic Controllers (PLCs), digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof, for performing the functions described herein.
Thus far, the present disclosure has been described in detail. In order to avoid obscuring the concepts of the present disclosure, some details known in the art are not described. How to implement the solutions disclosed herein will be fully apparent to those skilled in the art from the above description.
Those of ordinary skill in the art will appreciate that all or a portion of the steps implementing the above embodiments may be implemented by hardware, or may be implemented by a program indicating that the relevant hardware is implemented, where the program may be stored on a non-transitory computer readable storage medium, where the storage medium may be a read-only memory, a magnetic disk or optical disk, etc.
The description of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments were chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.
Claims (13)
1. The binding segment identification splicing method is characterized by comprising the following steps of:
the routing reflector acquires the autonomous domain path attribute in a first border gateway protocol message sent by the service terminal equipment and determines the sequence among autonomous domains;
the routing reflector receives a second border gateway protocol message carrying a binding segment identification type length value, an autonomous domain subtype length value connected with service starting point equipment and an autonomous domain subtype length value connected with service end point equipment, reads corresponding fields of the second border gateway protocol message, and determines a connection relation between autonomous domains involved in service, wherein the binding segment identification type length value comprises a type field, a length field, a reserved field, a binding segment identification field, a service starting point equipment segment identification field, a service end point equipment segment identification field and a service type field;
The route reflector completes the splicing of the binding section identifiers according to the sequence and the connection relation;
wherein, the reading the corresponding field of the second border gateway protocol message, and determining the connection relationship between the autonomous domains involved in the service includes:
the routing reflector determines an autonomous domain from which the second border gateway protocol message comes from the second border gateway protocol message through the autonomous domain path attribute;
the route reflector determines the section identifiers of the service starting point device and the service end point device of the service path related to the autonomous domain where the service corresponding to the binding section identifier is located from the coded content of the length value of the binding section identifier type;
the routing reflector determines an autonomous domain connected with the service starting point equipment and the service end point equipment of the autonomous domain according to the autonomous domain subtype length value connected with the service starting point equipment and the autonomous domain subtype length value connected with the service end point equipment;
the routing reflector acquires an autonomous domain number where the binding section identifier is located from an autonomous domain path attribute of the second border gateway protocol message;
the routing reflector acquires second service type information related to the binding segment identifier from the length value of the binding segment identifier type;
The routing reflector completes splicing of the binding section identifiers according to the sequence and the connection relation, and the splicing comprises the following steps:
comparing the autonomous domain number acquired from the first border gateway protocol message with the autonomous domain number acquired from the second border gateway protocol message, and comparing the first service type information with the second service type information, wherein the first service type information is first service type information which is acquired from the first border gateway protocol message by the routing reflector and is related to a virtual private network segment identifier sent by the service end point device;
determining a binding segment identifier corresponding to each autonomous domain passed by the message transmission;
and sequencing the binding segment identifiers of each autonomous domain according to the autonomous domain path attribute of the first border gateway protocol, pressing the binding segment identifiers into the stack bottom according to the transmission sequence, and completing the binding segment identifier splicing.
2. The binding segment identification splicing method according to claim 1, wherein the routing reflector obtains an autonomous domain path attribute in a first border gateway protocol message sent by a service endpoint device, and determining a sequence between autonomous domains includes:
Under the condition that a virtual private network segment identifier sent by service end point equipment is received, extracting service start point information in a first border gateway protocol message by a routing reflector, and storing the service start point information as identifier information;
the routing reflector extracts autonomous domain path attributes from a first border gateway protocol message carrying a virtual private network segment identifier, and determines the sequence among autonomous domains from the autonomous domain path attributes.
3. The binding segment identification splicing method according to claim 2, wherein the routing reflector completes the splicing of the binding segment identification according to the connection relation and the sequence, comprising:
and determining the sequence of the binding segment identifiers according to the autonomous domain path attributes of the received first border gateway protocol message and the second border gateway protocol message.
4. A binding segment identification splicing method according to claim 2 or 3, further comprising:
and the routing reflector sends the spliced binding segment identification to corresponding equipment according to the identification information.
5. A binding segment identification splicing method according to any of claims 1-3, wherein the routing reflector obtains an autonomous domain path attribute in a first border gateway protocol message sent by a service endpoint device, and determining a sequence between autonomous domains comprises:
The route reflector receives a first border gateway protocol message carrying a virtual private network segment identifier, which is sent to the service starting point equipment by the service ending point equipment;
the routing reflector acquires an autonomous domain number passing through when the message is transmitted from an autonomous domain path attribute of the first border gateway protocol message;
the routing reflector acquires first service type information related to the virtual private network segment identifier from a first border gateway protocol message;
the route reflector acquires the section identification of the service terminal equipment from the first border gateway protocol message;
the router reflector takes the virtual private network segment identifier as a stack bottom segment identifier spliced by the binding segment identifiers;
the route reflector determines that the destination of the virtual private network segment identification information is the service starting point equipment.
6. A binding segment identification splicing method according to any one of claims 1 to 3, wherein, for each autonomous domain passed during message transmission, determining the binding segment identification corresponding to the autonomous domain includes:
if the autonomous domain acquired from the second border gateway protocol message is the autonomous domain where the service starting point device is located, and the first service type information and the second service type information are the same, judging whether the first condition and the second condition are met, wherein the first condition is that the service starting point device section identifier acquired from the binding section identifier type length value is consistent with the virtual private network section identifier of the routing reflector, and the second condition is that the autonomous domain where the service starting point device is connected acquired from the autonomous domain subtype length value connected with the service starting point device contains the autonomous domain where the service end point device is located;
And if the first condition and the second condition are met, extracting the binding segment identifier corresponding to the autonomous domain from the length value of the binding segment identifier type.
7. A binding segment identification splicing method according to any one of claims 1 to 3, wherein, for each autonomous domain passed during message transmission, determining the binding segment identification corresponding to the autonomous domain includes:
if the autonomous domain acquired from the second border gateway protocol message is the autonomous domain where the service end point device is located, and the first service type information and the second service type information are the same, judging whether a third condition and a fourth condition are met, wherein the third condition is that the service end point device section identifier acquired from the binding section identifier type length value is consistent with the virtual private network section identifier of the routing reflector, and the fourth condition is that the autonomous domain where the service end point device is connected acquired from the autonomous domain subtype length value connected with the service start point device contains the autonomous domain where the service start point device is located;
and if the third condition and the fourth condition are met, extracting the binding segment identifier corresponding to the autonomous domain from the length value of the binding segment identifier type.
8. A routing reflector, comprising:
The first message reading module is used for acquiring the autonomous domain path attribute in the first border gateway protocol message sent by the service terminal equipment and determining the sequence among the autonomous domains;
the second message reading module is used for receiving a second border gateway protocol message carrying a binding segment identification type length value, an autonomous domain subtype length value connected with service starting point equipment and an autonomous domain subtype length value connected with service end point equipment, reading corresponding fields of the second border gateway protocol message and determining a connection relationship between autonomous domains involved in service, wherein the binding segment identification type length value comprises a type field, a length field, a reserved field, a binding segment identification field, a service starting point equipment segment identification field, a service end point equipment segment identification field and a service type field;
the segment identifier splicing module is used for finishing splicing of the binding segment identifiers according to the sequence and the connection relation;
the second message reading module is used for determining an autonomous domain from which the second border gateway protocol message comes from the second border gateway protocol message through the autonomous domain path attribute; determining the section identifiers of the service starting point device and the service end point device of the service path related to the autonomous domain where the service corresponding to the binding section identifier is located from the coded content of the length value of the binding section identifier type; determining the autonomous domain connected with the service starting point equipment and the service end point equipment of the autonomous domain according to the autonomous domain subtype length value connected with the service starting point equipment and the autonomous domain subtype length value connected with the service end point equipment; acquiring an autonomous domain number where the binding segment identification is located from an autonomous domain path attribute of the second border gateway protocol message; acquiring second service type information related to the binding segment identifier from the length value of the binding segment identifier type;
The segment identification splicing module is used for comparing the autonomous domain number acquired from the first border gateway protocol message with the autonomous domain number acquired from the second border gateway protocol message and comparing the first service type information with the second service type information, wherein the first service type information is first service type information which is acquired from the first border gateway protocol message by the routing reflector and is related to a virtual private network segment identification sent by the service terminal equipment; determining a binding segment identifier corresponding to each autonomous domain passed by the message transmission; and sequencing the binding segment identifiers of each autonomous domain according to the autonomous domain path attribute of the first border gateway protocol, pressing the binding segment identifiers into the stack bottom according to the transmission sequence, and completing the binding segment identifier splicing.
9. The routing reflector of claim 8, wherein the routing reflector is configured to perform operations to implement the binding segment identification stitching method of any of claims 2-7.
10. A routing reflector, comprising:
a memory for storing instructions;
a processor configured to execute the instructions to cause the routing reflector to perform operations implementing the binding segment identification stitching method of any one of claims 1-7.
11. An autonomous domain comprising a routing reflector as claimed in any of claims 8-10.
12. A cross-domain network comprising a plurality of autonomous domains as claimed in claim 11.
13. A non-transitory computer readable storage medium storing computer instructions which, when executed by a processor, implement the binding segment identification stitching method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111515529.3A CN114221891B (en) | 2021-12-13 | 2021-12-13 | Binding segment identification splicing method, routing reflector, autonomous domain and cross-domain network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111515529.3A CN114221891B (en) | 2021-12-13 | 2021-12-13 | Binding segment identification splicing method, routing reflector, autonomous domain and cross-domain network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114221891A CN114221891A (en) | 2022-03-22 |
| CN114221891B true CN114221891B (en) | 2023-08-29 |
Family
ID=80701163
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111515529.3A Active CN114221891B (en) | 2021-12-13 | 2021-12-13 | Binding segment identification splicing method, routing reflector, autonomous domain and cross-domain network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114221891B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115987803A (en) * | 2022-12-23 | 2023-04-18 | 天翼安全科技有限公司 | Organization mechanism determination method of autonomous system and related device |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9660897B1 (en) * | 2013-12-04 | 2017-05-23 | Juniper Networks, Inc. | BGP link-state extensions for segment routing |
| WO2020136660A1 (en) * | 2018-12-26 | 2020-07-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and system to extend segment routing based traceroute in a multiprotocol label switching network |
| CN111713079A (en) * | 2018-10-22 | 2020-09-25 | 思科技术公司 | Packet network interworking including segment routing |
| CN112187649A (en) * | 2019-07-01 | 2021-01-05 | 华为技术有限公司 | Message forwarding method, message processing method and device |
| CN112217719A (en) * | 2019-07-12 | 2021-01-12 | 华为技术有限公司 | Data transmission method, network node and storage medium |
| US10938717B1 (en) * | 2019-09-04 | 2021-03-02 | Cisco Technology, Inc. | Policy plane integration across multiple domains |
| CN113328949A (en) * | 2020-02-28 | 2021-08-31 | 华为技术有限公司 | Method, network device and system for updating routing attribute |
| CN113395206A (en) * | 2020-03-13 | 2021-09-14 | 华为技术有限公司 | Route determining method, device and network equipment |
| CN113746729A (en) * | 2020-05-28 | 2021-12-03 | 华为技术有限公司 | Method and device for processing binding segment identifier |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP5276177B2 (en) * | 2009-09-04 | 2013-08-28 | 株式会社日立製作所 | Route selection apparatus and mobile radio communication system |
| CN110971433B (en) * | 2018-09-29 | 2022-02-22 | 华为技术有限公司 | Method, device and system for acquiring SRv6 tunnel information |
| US11336569B2 (en) * | 2020-02-11 | 2022-05-17 | Juniper Networks, Inc. | Ping and traceroute in inter-autonomous system (AS) segment routing (SR) networks without requiring headend router or path monitoring system (PMS) controller knowledge of topology outside of origin as |
-
2021
- 2021-12-13 CN CN202111515529.3A patent/CN114221891B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9660897B1 (en) * | 2013-12-04 | 2017-05-23 | Juniper Networks, Inc. | BGP link-state extensions for segment routing |
| CN111713079A (en) * | 2018-10-22 | 2020-09-25 | 思科技术公司 | Packet network interworking including segment routing |
| WO2020136660A1 (en) * | 2018-12-26 | 2020-07-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and system to extend segment routing based traceroute in a multiprotocol label switching network |
| CN112187649A (en) * | 2019-07-01 | 2021-01-05 | 华为技术有限公司 | Message forwarding method, message processing method and device |
| CN112217719A (en) * | 2019-07-12 | 2021-01-12 | 华为技术有限公司 | Data transmission method, network node and storage medium |
| US10938717B1 (en) * | 2019-09-04 | 2021-03-02 | Cisco Technology, Inc. | Policy plane integration across multiple domains |
| CN113328949A (en) * | 2020-02-28 | 2021-08-31 | 华为技术有限公司 | Method, network device and system for updating routing attribute |
| CN113395206A (en) * | 2020-03-13 | 2021-09-14 | 华为技术有限公司 | Route determining method, device and network equipment |
| CN113746729A (en) * | 2020-05-28 | 2021-12-03 | 华为技术有限公司 | Method and device for processing binding segment identifier |
Non-Patent Citations (1)
| Title |
|---|
| G-SID: SRv6 Header Compression Solution;Weiqiang Cheng等;2020 IEEE 20th International Conference on Communication Technology (ICCT);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114221891A (en) | 2022-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105337881B (en) | A kind of processing method of data message, service node and drainage point | |
| EP3863240A1 (en) | Method for forwarding packet in hybrid network, device, and system | |
| WO2016197344A1 (en) | Method, device and system for realizing service link | |
| CN109729019B (en) | Speed limiting method and device for special line service in EVPN (Ethernet virtual private network) networking | |
| US20200153728A1 (en) | Multicast Forwarding Method and Related Device | |
| US9692716B2 (en) | Interoperation of switch line card and programmable line card | |
| CN105591868B (en) | A kind of cut-in method and device of Virtual Private Network VPN | |
| CN109818858B (en) | Method, device and system for realizing automatic splicing of inter-domain topological relation | |
| CN105991435B (en) | For obtaining the method and device of port path | |
| WO2017124709A1 (en) | Method of establishing traffic engineering tunnel and device | |
| CN112511444A (en) | Multicast traffic transmission method, device, communication node and storage medium | |
| CN105340217A (en) | Packet processing method, apparatus and system | |
| CN114221891B (en) | Binding segment identification splicing method, routing reflector, autonomous domain and cross-domain network | |
| CN107026796A (en) | A kind of VPN route advertising methods, stream compression forwarding method and relevant device | |
| JP2022537296A (en) | EVPN message transfer method, system, storage medium and terminal | |
| CN103684959A (en) | VPN realization method and PE device | |
| CN101355487A (en) | Method and apparatus for distributing label | |
| CN112511988A (en) | Message forwarding method, device, system, network device and storage medium | |
| CN107959611A (en) | A kind of method to E-Packet, apparatus and system | |
| CN106713130B (en) | A kind of routing table update method, EVPN control equipment and EVPN system | |
| CN109756419B (en) | Routing information distribution method and device and RR | |
| CN115065637A (en) | Method and device for transmitting computing power resource information and electronic equipment | |
| KR102547681B1 (en) | Service flow processing method and device | |
| CN114205282B (en) | SRv6 Policy scheduling method, system, router and controller | |
| CN103209125A (en) | Label information transmission method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |