Message forwarding method and ASBR
By obtaining and encapsulating Slice ID in ASBR, the end-to-end slice guarantee problem caused by naked IPv6 between ASBRs is solved, and the SliceID slice guarantee in the cross-domain scenario of L3VPN optionA is realized.
Patent Information
- Application Number
- CN202510097479.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-21
- Publication Date
- 2025-05-06
AI Technical Summary
In the cross-domain scenario of L3VPN optionA, since the ASBRs are naked IPv6, the packet does not carry the SliceID field, resulting in the inability to achieve end-to-end slice guarantee.
By receiving the target message in the ASBR, obtaining the Slice ID, and decapsulating it and encapsulating it in the inter-board communication header, ensuring that the message carries the Slice ID during the forwarding process between the ASBRs, thus achieving end-to-end SliceID slices.
It realizes end-to-end SliceID slicing guarantee between ASBRs in the L3VPN optionA cross-domain scenario, ensuring the integrity and reliability of network slicing.
Smart Images
Figure CN119945977A_ABST
Abstract
Description
Technical Field
[0001] The present specification relates to the field of communication technology, and in particular to a message forwarding method and an ASBR. Background Art
[0002] Slice ID-based network slicing is a network slicing technology used in SRv6 networking scenarios. Slice ID is a globally unique identifier in the network, which is used to identify virtual logical networks and physical bandwidth and other resources used by logical networks. At the same time, Slice ID information is encapsulated in IPv6 data packets, and the device forwards the packets carrying Slice ID through the corresponding logical network.
[0003] The current SliceID slicing technology adds the SliceID slicing identifier to the message after it enters the PE device; when it leaves the PE, the SliceID identifier is removed. In the L3VPN optionA cross-domain scenario, since IPv6 is nakedly transferred between ASBRs, the message does not carry the SliceID field, resulting in the inability to achieve end-to-end slicing guarantee when L3VPN optionA cross-domain. Summary of the invention
[0004] In order to overcome the problems existing in the related art, this specification provides a message forwarding method and an ASBR.
[0005] According to a first aspect of an embodiment of this specification, a method for forwarding a message is provided, the method being applied to a first border router ASBR, the method comprising:
[0006] Receive a target message, and obtain a Slice ID from the target message;
[0007] Decapsulate the target message and remove the SRv6 message header and Slice ID carried in the target message;
[0008] The Slice ID is encapsulated in the inter-board communication header, and the target message is forwarded to the switching network.
[0009] A slice channel is deployed on the interface between the first ASBR and the second ASBR.
[0010] The step of encapsulating the Slice ID in the inter-board communication header includes:
[0011] Encapsulate the Slice ID in the corresponding field in the inter-board communication header.
[0012] The step of forwarding the target message to the switching network includes:
[0013] Based on the Slice ID field in the inter-board communication header, the target message is forwarded to the switching network through the outbound interface corresponding to the Slice ID field.
[0014] Among them, the downstream board forwards the target message from the corresponding Slice ID slice to the switching network according to the Slice ID in the inter-board communication header.
[0015] It can be seen from the above embodiments that in order to solve the problem of naked forwarding of IPv6 messages between ASBRs, by recording the Slice ID of the target message and encapsulating the Slice ID in the inter-board communication header, the target message is forwarded from the corresponding Slice ID slice on the outbound interface to achieve end-to-end SliceID slicing.
[0016] According to a second aspect of an embodiment of this specification, a border router ASBR is provided, the ASBR comprising:
[0017] A receiving module, used for receiving a target message and obtaining a Slice ID from the target message;
[0018] A processing module, used for decapsulating the target message and removing the SRv6 message header and Slice ID carried in the target message;
[0019] The sending module is used to encapsulate the Slice ID in the inter-board communication header and forward the target message to the switching network.
[0020] Wherein, a slice channel is deployed on the interface between the ASBR and other ASBRs.
[0021] The processing module is specifically used to encapsulate the Slice ID in a corresponding field in the inter-board communication header.
[0022] The sending module is specifically configured to forward the target message to the switching network through an outbound interface corresponding to the Slice ID field based on the Slice ID field in the inter-board communication header.
[0023] The target message includes: a message with an IPv6 address of End.DT4 SID. The sending module is specifically used for the downlink board to forward the target message from the corresponding Slice ID slice to the switching network according to the Slice ID in the inter-board communication header.
[0024] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present specification. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and, together with the description, serve to explain the principles of the specification.
[0026] Figure 1 It is a schematic diagram of a message structure shown in this specification according to an exemplary embodiment.
[0027] Figure 2 It is a schematic diagram of a message structure shown in this specification according to an exemplary embodiment.
[0028] Figure 3 It is a schematic diagram of a network architecture shown in this specification according to an exemplary embodiment.
[0029] Figure 4 It is a schematic diagram of a network architecture shown in this specification according to an exemplary embodiment.
[0030] Figure 5 It is a flowchart of a message forwarding method shown in this specification according to an exemplary embodiment.
[0031] Figure 6 This is a flow chart of message forwarding according to an exemplary embodiment of the present specification. DETAILED DESCRIPTION
[0032] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this specification. Instead, they are merely examples of devices and methods consistent with some aspects of this specification as detailed in the appended claims.
[0033] The terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit this specification. The singular forms "a", "the" and "the" used in this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.
[0034] It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".
[0035] Currently, on the data forwarding plane, there are two types of Slice ID slicing methods based on the difference in the Slice ID encapsulation method in the IPv6 message.
[0036] One of the methods is: HBH slicing method:
[0037] like Figure 1 As shown in the figure, the Slice ID information is carried by using the option field of the IPv6 Hop-by-Hop Extension Header. When using this method, the device needs to parse the IPv6 Hop-by-Hop Extension Header to obtain the Slice ID information, and the length of the IPv6 message needs to be increased. The efficiency of the device parsing and forwarding messages is slightly lower, but the scalability is good. By default, the SRv6 source node uses the HBH slicing method to encapsulate the Slice ID, that is, the carried Slice ID is encapsulated in the IPv6 Hop-by-Hop Extension Header.
[0038] Another way is: source address slicing:
[0039] like Figure 2 As shown in the figure, the lower 32 bits of the IPv6 message source address are used to carry the Slice ID information. When using this method, the network administrator needs to plan the 128-bit source address reasonably. The advantage is that the device only needs to parse the IPv6 basic header to obtain the Slice ID information, and there is no need to increase the length of the IPv6 message. The message header overhead is small, and the device is more efficient in parsing and forwarding messages. The disadvantage is that if the address is not planned properly, it will cause abnormal message forwarding. For example, if the source address prefix of the IPv6 message carrying the SliceID is the same as the IPv6 source address prefix of a certain service or the source address prefix of the SRv6 VPN encapsulation, these messages will be forwarded through the network slice channel of the source address slice.
[0040] In the current SliceID slicing technology, a SliceID slicing identifier is added to a message after it enters a PE device; when it exits the PE, the SliceID identifier is removed.
[0041] like Figure 3As shown in the figure, the message is marked with SliceID at the head node PE1. When forwarded by the intermediate device P, it is forwarded in the corresponding slice according to the SliceID carried in the message. When forwarded at the tail node PE2, the SliceID is removed and then forwarded to CE2.
[0042] like Figure 4 As shown in the figure, in the L3VPN optionA cross-domain scenario, since IPv6 is nakedly transferred between ASBRs, the message does not carry the SliceID field, resulting in the inability to implement end-to-end slicing guarantee when L3VPN optionA crosses domains.
[0043] In order to solve the above technical problems, the embodiment of the present disclosure provides a message forwarding method, which is applied to a first border router ASBR, such as Figure 5 As shown, the method includes:
[0044] S501 receives a target message and obtains a Slice ID from the target message;
[0045] S502 decapsulates the target message and removes the SRv6 message header and Slice ID carried in the target message;
[0046] S503 encapsulates the Slice ID in the inter-board communication header and forwards the target message to the switching network.
[0047] In this embodiment, when L3VPN optionA is cross-domain, SliceID slice channels are deployed on the interfaces between ASBRs.
[0048] Among them, L3VPN Option A is an interconnection option for implementing virtual private networks (VPNs) in multiprotocol label switching (MPLS) networks. Option A is one of the three main methods for L3VPN connections between different autonomous systems (ASs) (the other two are Option B and Option C). In Option A, the border routers (ASBRs) of each autonomous system are connected through traditional IP routing.
[0049] like Figure 4 As shown, when the first ASBR (ASBR1) forwards a message across the domain to the opposite second ASBR (ASBR2), the first ASBR strips the SliceID of the target message (the target message is a message sent across the domain from the first ASBR to the second ASBR), and obtains and records the Slice ID.
[0050] And in executing step S503, when forwarding the target message to the switching network, it can be forwarded from the corresponding SliceID slice.
[0051] That is, the downstream board forwards the target message from the corresponding Slice ID slice to the switching network according to the Slice ID in the inter-board communication header.
[0052] Specifically, in the ASBR forwarding process, Figure 6 As shown:
[0053] In the upstream direction:
[0054] 1. After receiving the packet with the destination IPv6 address of End.DT4 SID, the first ASBR first reads and records the SliceID, and then decapsulates and removes the SRv6 packet header and SliceID.
[0055] 2. ASBR encapsulates the SliceID in the inter-board communication header and then forwards the message to the switching network.
[0056] In the downlink direction:
[0057] 3. According to the SliceID carried in the inter-board communication header of the message, the message is forwarded from the corresponding SliceID slice on the outbound interface.
[0058] It can be seen from the above embodiments that by recording the Slice ID of the target message and encapsulating the Slice ID in the inter-board communication header, the target message is sliced and forwarded from the corresponding Slice ID on the outbound interface, thereby realizing end-to-end SliceID slicing.
[0059] Based on the above method embodiments, the embodiment of the present disclosure further provides a border router ASBR, which includes:
[0060] A receiving module, used for receiving a target message and obtaining a Slice ID from the target message;
[0061] A processing module, used for decapsulating the target message and removing the SRv6 message header and Slice ID carried in the target message;
[0062] The sending module is used to encapsulate the Slice ID in the inter-board communication header and forward the target message to the switching network.
[0063] Wherein, a slice channel is deployed on the interface between the ASBR and other ASBRs.
[0064] The processing module is specifically used to encapsulate the Slice ID in a corresponding field in the inter-board communication header.
[0065] The sending module is specifically configured to forward the target message to the switching network through an outbound interface corresponding to the Slice ID field based on the Slice ID field in the inter-board communication header.
[0066] The target message includes: a message whose IPv6 address is End.DT4 SID.
[0067] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying creative labor.
[0068] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0069] Those skilled in the art will readily appreciate other embodiments of the specification after considering the specification and practicing the invention claimed herein. The specification is intended to cover any variations, uses or adaptations of the specification that follow the general principles of the specification and include common knowledge or customary techniques in the art that are not claimed in the specification. The specification and examples are to be considered exemplary only, and the true scope and spirit of the specification are indicated by the following claims.
[0070] It should be understood that the present description is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.
[0071] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.
Claims
1. A message forwarding method, characterized in that: The method is applied to a first border router ASBR, and the method comprises: Receive a target message, and obtain a Slice ID from the target message; Decapsulate the target message and remove the SRv6 message header and Slice ID carried in the target message; The Slice ID is encapsulated in the inter-board communication header, and the target message is forwarded to the switching network.
2. The method according to claim 1, characterized in that The method further comprises: A slice channel is deployed on the interface between the first ASBR and the second ASBR.
3. The method according to claim 1, characterized in that The step of encapsulating the Slice ID in the inter-board communication header includes: Encapsulate the Slice ID in the corresponding field in the inter-board communication header.
4. The method according to claim 3, characterized in that: The step of forwarding the target message to the switching network includes: Based on the Slice ID field in the inter-board communication header, the target message is forwarded to the switching network through the outbound interface corresponding to the Slice ID field.
5. The method according to claim 1, characterized in that The step of encapsulating the Slice ID in the inter-board communication header and forwarding the target message to the switching network includes: The downstream board forwards the target message from the corresponding Slice ID slice to the switching network according to the Slice ID in the inter-board communication header.
6. A border router ASBR, characterized in that: The ASBR comprises: A receiving module, used for receiving a target message and obtaining a Slice ID from the target message; A processing module, used for decapsulating the target message and removing the SRv6 message header and SliceID carried in the target message; The sending module is used to encapsulate the SliceID in the inter-board communication header and forward the target message to the switching network.
7. The ASBR according to claim 6, characterized in that: A slice channel is deployed on the interface between the ASBR and other ASBRs.
8. The ASBR according to claim 6, characterized in that: The processing module is specifically used to encapsulate the Slice ID in a corresponding field in the inter-board communication header.
9. The ASBR according to claim 6, characterized in that: The sending module is specifically configured to forward the target message to the switching network through an outbound interface corresponding to the Slice ID field based on the Slice ID field in the inter-board communication header.
10. The ASBR according to claim 6, characterized in that: The sending module is specifically used for the downlink board to forward the target message from the corresponding Slice ID slice to the switching network according to the Slice ID in the inter-board communication header.