A method for forwarding virtual links across domains

By constructing a heterogeneous interconnection network architecture and a global identifier mapping mechanism, cross-domain transparent transmission between different network systems such as IPv4, IPv6, and MPLS in heterogeneous networks is realized, solving the problem of transparent forwarding in cross-domain interconnection in heterogeneous networks, and supporting multi-domain peer-to-peer interconnection and end-to-end service transmission in heterogeneous networks.

CN123074973APending Publication Date: 2026-11-10NANJING UNIV
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611569787.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-10-12
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In heterogeneous networks, existing cross-domain interconnection methods are difficult to achieve end-to-end transparent transmission, especially when maintaining the original network mechanisms of different network domains. How can cross-domain transparent forwarding be achieved between different network systems such as IPv4, IPv6, and MPLS?

Method used

The cross-domain interconnection virtual link forwarding method is adopted. By constructing a heterogeneous interconnection network architecture, a unified global identifier mapping and addressing mechanism for cross-domain gateways is established. Virtual link label stacks are generated and virtual link packet headers are encapsulated. Virtual link label mapping and transparent forwarding are performed to ensure that network domains do not exchange intra-domain routing information.

Benefits of technology

It enables multi-domain peer-to-peer interconnection and end-to-end transparent service transmission in heterogeneous networks, supports various protocol systems such as IPv4, IPv6, and MPLS, and cross-protocol conversion is automatically completed by the border gateway without the network being aware of it, and there is no need to exchange intra-domain routing information between different domains.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123074973A_ABST
    Figure CN123074973A_ABST
Patent Text Reader

Abstract

This invention discloses a cross-domain interconnection virtual link forwarding method. The invention establishes a heterogeneous interconnection network architecture and a unified global identifier mapping and addressing mechanism for cross-domain gateways. For cross-domain communication tasks, the control plane performs path calculation, generating a virtual link label stack composed of global labels from each cross-domain gateway along the communication path. The source gateway encapsulates the virtual link packet header. Each gateway encapsulates and forwards the packet based on the global labels in the virtual link label stack according to the intra-domain forwarding mechanism, forwarding the packet to the next gateway in the cross-domain interconnection. At the destination AGW, the virtual link packet header is removed, the original service packet is restored, and forwarded to the destination CLE. This invention decouples global labels from the intra-domain network mechanism, adapting to the dynamic establishment of gateway links in heterogeneous networks and supporting mixed cross-domain interconnection of different network mechanisms such as IPv4, IPv6, and MPLS.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention belongs to the field of communication network interconnection technology, specifically relating to a cross-domain interconnection virtual link forwarding method, which is particularly suitable for end-to-end transparent service transmission in multi-domain peer-to-peer and heterogeneous protocol system mixed scenarios such as satellite networks. Background Technology

[0002] As network architectures become increasingly complex, the demand for cross-domain interconnection between different network domains continues to grow. Given the differences in protocol systems, address systems, and forwarding mechanisms among network domains, achieving end-to-end transparent transmission while maintaining the original network mechanisms of each domain has become a crucial issue in heterogeneous network interconnection.

[0003] Satellite networks typically consist of multiple isolated network domains. For example, in remote sensing constellation networks, cross-domain data transmission can be achieved through external heterogeneous networks. Compared to general terrestrial networks, satellite network cross-domain interconnection is characterized by relatively closed network domains, unique node organization methods such as orbital plane-orbit position, and the independence and peer-to-peer relationship between network domains. Furthermore, a single end-to-end transmission path may traverse multiple network domains employing different network architectures such as IPv4, IPv6, and MPLS, further increasing the complexity of cross-domain interconnection and transparent forwarding.

[0004] Existing cross-domain interconnection methods typically require the exchange of routing information between domains or reliance on a unified network architecture for forwarding, making it difficult to simultaneously meet the requirements of multi-domain peer-to-peer interconnection, compatibility with heterogeneous network architectures, and isolation of routing information within each domain. Therefore, a forwarding method is needed that can achieve transparent end-to-end cross-domain transmission without exchanging intra-domain routing information and while maintaining the existing network architecture and intra-domain forwarding mechanisms. Summary of the Invention

[0005] Purpose of the invention:

[0006] This invention aims to provide a cross-domain interconnection virtual link forwarding method, establishing a unified global identifier mapping and addressing mechanism for cross-domain gateways. Under the conditions of not exchanging intra-domain routing information between network domains and maintaining the existing network architecture and intra-domain forwarding mechanism unchanged, end-to-end transparent transmission is achieved. Cross-domain virtual link paths are represented by virtual link label stacks, with each gateway handling label processing and outer layer bearer conversion. This enables continuous forwarding of packets between different network architectures such as IPv4, IPv6, and MPLS, thereby meeting the needs of multi-domain peer-to-peer interconnection and end-to-end service transmission in heterogeneous networks.

[0007] To achieve the above objectives, the present invention adopts the following technical solution: a cross-domain interconnection virtual link forwarding method, applied to a cross-domain interconnection scenario of heterogeneous networks with multiple network architectures, the method comprising:

[0008] S1. Construct a heterogeneous interconnection network architecture: The heterogeneous interconnection network architecture includes user link devices (CLE), access links (AL), access gateways (AGW), border gateways (BGW), intra-domain subnets, the heterogeneous hybrid network (HetNet), inter-domain links (IDL), and virtual links (PL).

[0009] S2. Establish a unified global identifier mapping and addressing mechanism for cross-domain gateways:

[0010] The control plane assigns global labels to gateway nodes participating in cross-domain interconnection. The global label includes programmable forwarding action (PFA) and establishes an intra-domain information table (LIB) for the global label. The global label is independent of the IPv4 forwarding system, IPv6 forwarding system, and MPLS forwarding system used within each network domain, and serves as a unified node identifier across heterogeneous network domains.

[0011] The global label is 32 bits and includes a Label field, a Programmable Forwarding Action (PFA) field, a Domain field, and an extension field. The Label field is used to identify the gateway node participating in cross-domain virtual link forwarding. The PFA field is used to indicate the forwarding operation that the node needs to perform. The Domain field is used to record the network domain number to which the node corresponding to the global label belongs. The extension field is a reserved field. The intra-domain information table (LIB) uses the Label field as the key and the network domain number, network architecture, and intra-domain forwarding information of the corresponding node as the value. The intra-domain forwarding information includes at least one of IPv4 address, IPv6 address, and MPLS label value.

[0012] S3. Generate a virtual link label stack and encapsulate a virtual link header: The control plane performs path calculation for the cross-domain communication task between the source user link device (CLE) and the destination user link device (CLE), generates a virtual link label stack, and sends the virtual link label stack to the data plane, where the source access gateway (AGW) encapsulates the virtual link header according to the virtual link label stack.

[0013] The control plane generates a virtual link PL ID (PLID) for the cross-domain communication task and determines a list of gateways traversed by the cross-domain communication task. The gateway list includes the source access gateway (AGW), at least one border gateway (BGW), and the destination access gateway (AGW). The control plane converts the gateway list into a virtual link tag stack and forms a virtual link referral table. The virtual link referral table uses the PLID as the key and the global tag count, service category (TC), flag, and virtual link tag stack as values. The source access gateway (AGW) queries the virtual link referral table using the PLID to obtain the virtual link tag stack. The virtual link header includes a tag pointer and the virtual link tag stack. The tag pointer indicates the current global tag position that needs to be processed. When the source access gateway (AGW) encapsulates the virtual link header, it initializes the tag pointer to the global tag count.

[0014] S4. Perform virtual link label mapping and transparent forwarding: The gateway node performs label mapping and transparent forwarding on packets carrying the virtual link header according to the programmable forwarding action (PFA) in the global label and the domain information table (LIB), and converts the protocol system at the domain boundary.

[0015] The gateway node locates the current global label based on the label pointer, reads the Label field and Programmable Forwarding Action (PFA) field from the current global label, and queries the Intra-Domain Information Table (LIB) based on the Label field to obtain the intra-domain forwarding information of the node corresponding to the current global label. The gateway node updates the label pointer based on the forwarding action indicated by the PFA field in the current global label. When the forwarding action needs to continue forwarding, the gateway node locates the next-hop global label based on the updated label pointer, queries the Intra-Domain Information Table (LIB) based on the Label field of the next-hop global label to obtain the next-hop intra-domain forwarding information, determines the outer bearer information of the next forwarding segment according to the conversion rules, and executes the forwarding action indicated by the PFA field in the current global label after completing the outer encapsulation. The Border Gateway (BGW) strips the outer bearer information used by the current forwarding segment at the domain boundary and encapsulates the outer bearer information used by the next forwarding segment.

[0016] S5. Perform virtual link packet decapsulation: After receiving the packet, the destination access gateway AGW removes the virtual link packet header, restores the original service packet, and sends the original service packet to the destination user link device CLE.

[0017] Furthermore, different network domains do not exchange intra-domain routing information, and each network domain maintains its existing network architecture and intra-domain forwarding mechanism.

[0018] Beneficial effects:

[0019] 1. This invention establishes a cross-domain interconnection network architecture that integrates multiple heterogeneous network systems;

[0020] 2. This invention establishes a unified global identifier mapping and addressing mechanism for cross-domain gateways;

[0021] 3. This invention enables cross-domain interconnection of various heterogeneous network systems, as well as end-to-end transparent service transmission between multiple peer autonomous domains, supporting various protocol systems such as IPv4, IPv6, and MPLS.

[0022] 4. The cross-protocol family conversion of this invention is automatically completed by BGW at the domain boundary, without the awareness of the network within the domain, and there is no need for different domains to exchange their respective intra-domain routing information, thus minimizing the impact on the existing network. Attached Figure Description

[0023] Figure 1 This is a typical networking scenario for heterogeneous interconnection;

[0024] Figure 2 It is a heterogeneous interconnection network architecture;

[0025] Figure 3 This is a global tag structure;

[0026] Figure 4 This is a virtual link message header structure;

[0027] Figure 5 This refers to the message encapsulation structure during the forwarding process. Detailed Implementation

[0028] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0029] In the process of remote sensing constellation landing and transmission, cross-domain data transmission is sometimes required through external heterogeneous networks. This invention can be applied to, for example... Figure 1 In the application scenarios shown.

[0030] Example 1:

[0031] Cross-domain interconnection virtual link forwarding method:

[0032] S1. Establish a heterogeneous interconnection network architecture.

[0033] The forwarding method of the present invention is applied to, for example Figure 2The heterogeneous interconnection network architecture shown above uses virtual link multiplexing for packet forwarding. This architecture mainly includes User Link Equipment (CLE), Access Link (AL), Access Gateway (AGW), Border Gateway (BGW), intra-domain subnets, Heterogeneous Hybrid Network (HetNet), inter-domain links (IDL) between two network domains, Domain1 and Domain2, and virtual links (PL).

[0034] User Link Device (CLE): A user-side link device where one end of a service initiates and / or terminates. The CLE is unaware of whether it is using a virtual link service or a native service.

[0035] AL: The physical link between CLE and AGW, which can take the form of laser link, microwave link, Ethernet port, AOS port, etc.

[0036] Access Gateway (AGW): The access device for CLE, which provides virtual links for CLE;

[0037] Border Gateway (BGW): A gateway device located between network domains that enables inter-domain forwarding;

[0038] Intra-domain subnets: Networks operating on a single protocol.

[0039] HetNet: A heterogeneous hybrid network with multiple protocol schemes, consisting of multiple networks with a single protocol scheme.

[0040] Virtual Link (PL): A mechanism that carries necessary service information through HetNet to enable service transmission between AGWs.

[0041] Inter-Domain Link (IDL): A cross-domain link connecting the BGW.

[0042] S2. Establish a unified global identifier mapping and addressing mechanism for cross-domain gateways.

[0043] First, global labels are assigned to the AGW and BGW participating in the cross-domain interconnection. The global label is used to represent the identity of the node in the cross-domain virtual link. It does not directly indicate the IPv4, IPv6 or MPLS network system adopted by the node, nor does it depend on the intra-domain forwarding equivalence class (FEC) for assignment.

[0044] S2.1 Global Tag Format Definition.

[0045] like Figure 3 As shown, each global tag is 32 bits long and includes:

[0046] bits [31:24]: Label field (8 bits), label value, used to identify the gateway node participating in cross-domain virtual link forwarding. Since only the gateway needs to be configured with a global label, and the Label is not related to the domain information, the 8-bit Label field can identify up to 256 cross-domain gateways. It can be used for cross-domain forwarding in large-scale heterogeneous networks. In other implementations, the length of the Label field can be adjusted according to the scale of the gateways participating in cross-domain interconnection.

[0047] bits [23:12]: PFA field (12 bits), programmable forwarding action, used to indicate the forwarding operation that the node needs to perform, including the following actions:

[0048] The FWD.TABLE action forwards data according to the specified forwarding table.

[0049] The FWD.XCON action forwards directly based on the specified local outgoing interface.

[0050] The FWD.DECAP and XCON actions decapsulate the data and forward it from the specified local outgoing interface.

[0051] In the virtual link, the destination AGW global label is bound to PFA as FWD.DECAP and XCON, which means that the PL instance is mapped on the destination AGW according to the PFA, the PL message is decapsulated, and the message is forwarded to the destination CLE through the specified outgoing interface.

[0052] bits [11:8]: Domain field (4 bits), which records the network domain number to which the global label node belongs during forwarding, for use in cross-domain explicit path tracing.

[0053] bits [7:0]: Extended field (8 bits), reserved for future expansion.

[0054] S3, cross-domain virtual link calculation, traffic redirection and message encapsulation.

[0055] S3.1 Cross-domain virtual link establishment and calculation.

[0056] Assume the source user link device is CLE-S and the destination user link device is CLE-D. CLE-S connects to the source AGW, and CLE-D connects to the destination AGW. The control plane performs centralized path calculation for cross-domain communication tasks of the {source CLE, destination CLE} pair, forming corresponding cross-domain virtual links: {source AGW, BGW1, BGW2, ..., BGWn, destination AGW}, and determines PLID for each virtual link.

[0057] When a cross-domain path traverses multiple network domains, adjacent network domains are connected via Border Gateways (BGWs) and inter-domain links. Depending on the actual network deployment, a network domain can have different BGWs handling inbound and outbound functions, or the same BGW can handle the corresponding inter-domain forwarding functions. The control plane assembles the global labels corresponding to each gateway into a virtual link label stack {Ls, L1, L2, ..., Ln, Ld}, and distributes it to the data plane through the virtual link routing table.

[0058] After receiving the corresponding cross-domain service, the source AGW directly obtains the complete virtual link tag stack by querying the virtual link referral table through PLID and encapsulates the virtual link message header.

[0059] S3.2 Virtual Link Header Format.

[0060] A virtual link packet is logically represented as "local link layer information + local forwarding segment outer layer bearer information + virtual link packet header + original service packet". The local forwarding segment outer layer bearer information can be an IPv4 packet header, an IPv6 packet header, or an MPLS label. For IP bearers, a new IP upper layer protocol type 254 is defined.

[0061] The virtual link header is used to carry control information and the virtual link label stack for cross-domain virtual links. It is encapsulated between the outer bearer information of the current forwarding segment and the original service message. The virtual link header structure is as follows: Figure 4 As shown in the figure, B represents a byte.

[0062] The virtual link header includes a label pointer, a TC field, a Last Entry field, a Flag field, and a virtual link label stack.

[0063] Tag pointer: The current global tag position that needs to be processed;

[0064] Last Entry: Used to record information related to the length of the virtual link label stack;

[0065] TC: Business category or priority;

[0066] Flag: Control flag.

[0067] Virtual link label stack: It consists of global labels from the source AGW, each BGW along the way, and the destination AGW, arranged in the order of cross-domain virtual link forwarding.

[0068] After the source AGW completes the virtual link packet header encapsulation, it initializes the tag pointer to the global tag count. Each time the packet passes through an AGW or BGW that needs to process virtual link tags, the gateway locates the current tag according to the tag pointer and performs corresponding processing based on the PFA field in the current tag.

[0069] The S3.3 Virtual Link Referral Table is shown in Table 1, which is used to directly obtain the corresponding virtual link tag stack based on the cross-domain communication task.

[0070] Table 1 Virtual Link Referral Table

[0071] Its logical entries are:

[0072] - Key: PLID, which can be obtained from the IP address of the source or destination CLE or the MPLS label corresponding to the service, or from the access link interface of the source CLE.

[0073] - Values: Global tag count, TC, Flag, and virtual link tag stack.

[0074] The global tag count is used to initialize the tag pointer and Last Entry in the virtual link packet header. The tag pointer is updated gradually as each gateway processes the packet during forwarding.

[0075] S4, Virtual Link Label Mapping and Transparent Forwarding.

[0076] S4.1 Definition of LIB format for intra-domain information table.

[0077] Table 2 Intra-Domain Information Table (LIB)

[0078] The Intradomain Information Table (LIB), as shown in Table 2, is used to establish the mapping relationship between global labels and forwarding information within a specific network domain.

[0079] Its logical entries are:

[0080] Key: The 8-bit Label field in the global label;

[0081] Values: The network domain number, network regime, and intra-domain forwarding information that the node can use for different forwarding regimes. The intra-domain forwarding information includes IPv4 address, IPv6 address, and / or MPLS label value.

[0082] S4.2 Mapping of intra-domain information for global labels.

[0083] The global label 8-bit Label field is used as a key to query the LIB and obtain the network domain number, network system, and intra-domain forwarding information of the node corresponding to the label.

[0084] Before encapsulating the next forwarding segment, the obtained network domain number is written to the Domain field of the global label. Since the processed labels are still retained in the virtual link header, the network domain information traversed during cross-domain forwarding can be recorded based on the Domain field of each label for explicit cross-domain path tracing.

[0085] S4.3 Transparent forwarding of virtual links.

[0086] S4.3.1 Transparent forwarding of the source access gateway AGW.

[0087] The source access gateway (AGW) obtains the complete virtual link label stack based on the virtual link routing table and initializes the label pointers to the global label count. The source AGW locates its own current global label based on the label pointers, reads its Label and PFA fields, and queries the LIB based on the Label field to obtain its own network domain number, network architecture, and intra-domain forwarding information.

[0088] When the PFA field indicates an FWD.TABLE or FWD.XCON action, the source AGW continues virtual link forwarding, decrements the label pointer by 1, locates the global label corresponding to the next-hop node, queries the LIB based on its Label field to obtain the network architecture and intra-domain forwarding information of the next-hop node, and determines the outer bearer architecture and encapsulation information for the next forwarding segment according to the conversion rules. After completing the outer encapsulation, the source AGW executes the PFA action in its own global label: when the action is FWD.TABLE, it performs a table lookup and forwarding according to the specified forwarding table bound to the PFA; when the action is FWD.XCON, it forwards directly from the specified local outgoing interface bound to the PFA.

[0089] S4.3.2 Transparent forwarding of Border Gateway (BGW).

[0090] After the message arrives at the Border Gateway (BGW), the outer IP header or MPLS label used by the current network domain is removed. The global label corresponding to the current node is located according to the label pointer, and its Label field and PFA field are read. The LIB is then queried based on the Label field to obtain the network domain number, network system, and intra-domain forwarding information of the current node.

[0091] When the PFA field indicates an FWD.TABLE or FWD.XCON action, the label pointer is updated and the global label corresponding to the next-hop node is located. The LIB is queried to obtain the network domain number, network architecture, and intra-domain forwarding information of the next node. Then, cross-domain protocol architecture conversion is performed based on the conversion rules. After the gateway completes the encapsulation of the outer layer bearer information of the next forwarding segment, it executes the PFA action in the current global label for forwarding.

[0092] S4.3.3 Transition rules in transparent forwarding.

[0093] Table 3 shows the conversion rules corresponding to the system of the domain where the current node and the next node are located:

[0094] Table 3. Transition Rules in Transparent Forwarding

[0095] S5. Virtual link message decapsulation.

[0096] When the message arrives at the destination access gateway (AGW), the destination AGW first removes the outer bearer information used by the current network domain, locates the last global label corresponding to the destination AGW according to the label pointer, reads its Label field and PFA field, and queries the LIB according to the Label field to obtain the network domain number of the corresponding node, and writes it into the Domain field of the current global label.

[0097] The destination AGW identifies the actions bound to the PFA in the current global tag as FWD.DECAP and XCON, and obtains the specified local outgoing interface. After completing the processing of the current tag, the tag pointer is decremented by 1 and becomes 0, and no further tags are read; the destination AGW decapsulates the virtual link packet header, restores the original service packet, and outputs it from the specified local outgoing interface bound to the PFA to the destination CLE.

[0098] Example 2:

[0099] Virtual link forwarding method between two heterogeneous network domains:

[0100] like Figure 5 As shown, the following example illustrates the virtual link forwarding process using cross-domain communication between two network domains, Domain1 and Domain2. CLE1, AGW1, and BGW1 are located in Domain1, which uses IPv6 forwarding. BGW2, AGW2, and CLE2 are located in Domain2, which uses MPLS forwarding, and the link layer uses the AOS frame format. The original service packets sent from CLE1 to CLE2 are IPv4 packets, which remain unchanged during cross-domain transmission.

[0101] Let the global labels corresponding to AGW1, BGW1, BGW2, and AGW2 be Ls, L1, L2, and Ld, respectively. Then the virtual link label stack is:

[0102] L[3] = Ls = AGW1,

[0103] L[2] = L1 = BGW1,

[0104] L[1] = L2 = BGW2,

[0105] L[0] = Ld = AGW2,

[0106] The initial value of the tag pointer is 4, and the currently processed tag is L[tag pointer - 1].

[0107] In this embodiment, the PFA binding action of Ls and L1 is FWD.XCON, L2 is FWD.TABLE, and Ld is FWD.DECAP and XCON.

[0108] 1. Processing of source access gateway AGW1.

[0109] AGW1 obtains the complete label stack by querying the virtual link routing table through PLID and initializes the label pointer to 4. Based on the label pointer, it locates the current label Ls, queries the LIB using the Label field of Ls to obtain the network domain number, network architecture, and intra-domain forwarding information of AGW1, and writes the network domain number into the Domain field of Ls.

[0110] The PFA action of Ls is FWD.XCON, indicating that forwarding needs to continue. AGW1 updates the label pointer from 4 to 3, locates the next label L1, and queries the LIB using the Label field of L1 to obtain the intra-domain forwarding information of BGW1. Since both AGW1 and BGW1 are located in the IPv6 domain Domain1, AGW1 encapsulates the IPv6 outer header and executes the FWD.XCON action in Ls, sending it from the specified local outgoing interface to BGW1.

[0111] After being processed by AGW1, the message is:

[0112] [AOS | IPv4 header | Payload], where Payload is the upper-layer payload located after the IPv4 header in the IPv4 message carried by the AOS frame.

[0113] Convert to:

[0114] [AOS | IPv6 outer header | Virtual link header | AOS | IPv4 header | Payload].

[0115] The source address of the original IPv4 header is the IPv4 address of CLE1, and the destination address is the IPv4 address of CLE2, which remains unchanged during virtual link forwarding; the source address of the outer IPv6 header is the IPv6 address of AGW1 in Domain1, and the destination address is the IPv6 address of the next node BGW1 in Domain1.

[0116] 2. Processing of border gateway BGW1.

[0117] BGW1 removes the IPv6 outer header of the previous forwarding segment, locates the current label L1 according to the label pointer, queries the LIB using the Label field of L1 to obtain its own information, and writes it into the Domain field.

[0118] The PFA action for L1 is FWD.XCON. BGW1 updates the label pointer from 3 to 2, locates the next label L2, and queries the LIB to obtain the intra-domain forwarding information of BGW2. Since the current node is in the IPv6 domain and the next node is in the MPLS domain, BGW1 encapsulates the MPLS outer bearer information according to the conversion rules, executes the FWD.XCON action in L1, and sends the packet to BGW2.

[0119] After processing by BGW1, the message is:

[0120] [AOS | IPv6 Outer Header | Virtual Link Header | AOS | IPv4 Header | Payload]

[0121] Convert to:

[0122] [AOS | MPLS tag | Virtual link header | AOS | IPv4 header | Payload].

[0123] 3. Border Gateway BGW2 processing.

[0124] BGW2 processes the MPLS outer layer bearer information of the previous forwarding segment, locates the current label L2 according to the label pointer, queries the LIB with the Label field of L2 to obtain its own information and writes it to the Domain field.

[0125] The PFA action in L2 is FWD.TABLE. BGW2 updates the label pointer from 2 to 1, locates the next label Ld, and queries LIB to obtain AGW2's intra-domain forwarding information. Since both BGW2 and AGW2 are located in MPLS Domain2, no network architecture conversion is required. BGW2 updates or encapsulates the MPLS outer label based on the intra-domain forwarding information and completes the forwarding to AGW2 according to the MPLS forwarding table specified in the PFA in L2.

[0126] After processing by BGW2, the message is still represented in logical format as follows:

[0127] [AOS | MPLS outer tag | Virtual link header | AOS | IPv4 header | Payload]

[0128] The MPLS outer layer forwarding information is updated based on the forwarding segments from BGW2 to AGW2.

[0129] 4. Destination access gateway AGW2 processing.

[0130] AGW2 removes the MPLS outer layer bearer information used by Domain2, locates the last label Ld according to the label pointer, queries the LIB using the Label field of Ld to obtain its own network domain number, and writes it into the Domain field.

[0131] The PFA binding action of Ld is FWD.DECAP and XCON, specifying the local outgoing interface for connecting to CLE2. AGW2 does not need to read the next tag, updates the tag pointer from 1 to 0, removes the virtual link header, restores the original IPv4 service packet, and sends it to CLE2 from the specified local outgoing interface.

[0132] After being processed by AGW2, the message is:

[0133] [AOS | MPLS Outer Label | Virtual Link Header | AOS | IPv4 Header | Payload]

[0134] Restored to:

[0135] [AOS | IPv4 header | Payload].

[0136] Therefore, the original IPv4 service packets remain unchanged throughout the forwarding process, with only the virtual link outer layer bearer information being converted according to different network domains.

Claims

1. A cross-domain interconnection virtual link forwarding method, characterized in that, This method is applied to cross-domain interconnection of HetNet, a heterogeneous hybrid network with multiple protocol systems. It achieves cross-domain interconnection of heterogeneous hybrid networks based on a virtual link forwarding mechanism with global labels. The method includes: S1. Construct a heterogeneous interconnection network architecture: The heterogeneous interconnection network architecture includes user link devices (CLE), access links (AL), access gateways (AGW), border gateways (BGW), intra-domain subnets, the heterogeneous hybrid network (HetNet), inter-domain links (IDL), and virtual links (PL). S2. Establish a unified global identifier mapping and addressing mechanism for cross-domain gateways: The control plane assigns global labels to gateway nodes participating in cross-domain interconnection. The global label includes programmable forwarding action (PFA) and establishes an intra-domain information table (LIB) for the global label. The global label is independent of the IPv4 forwarding system, IPv6 forwarding system, and MPLS forwarding system used within each network domain, and serves as a unified node identifier across heterogeneous network domains. S3. Generate a virtual link label stack and encapsulate a virtual link header: The control plane performs path calculation for the cross-domain communication task between the source user link device (CLE) and the destination user link device (CLE), generates a virtual link label stack, and sends the virtual link label stack to the data plane, where the source access gateway (AGW) encapsulates the virtual link header according to the virtual link label stack. S4. Perform virtual link label mapping and transparent forwarding: The gateway node performs label mapping and transparent forwarding on packets carrying the virtual link header according to the programmable forwarding action (PFA) in the global label and the domain information table (LIB), and converts the protocol system at the domain boundary. S5. Perform virtual link packet decapsulation: After receiving the packet, the destination access gateway AGW removes the virtual link packet header, restores the original service packet, and sends the original service packet to the destination user link device CLE.

2. The cross-domain interconnection virtual link forwarding method according to claim 1, characterized in that, In step S2, the global label is 32 bits and includes a Label field, a Programmable Forwarding Action (PFA) field, a Domain field, and an extension field. The Label field is used to identify the gateway node participating in cross-domain virtual link forwarding. The PFA field is used to indicate the forwarding operation that the node needs to perform. The Domain field is used to record the network domain number to which the node corresponding to the global label belongs. The extension field is a reserved field. The intra-domain information table LIB uses the Label field as the key and the network domain number, network architecture, and intra-domain forwarding information of the corresponding node as the value. The intra-domain forwarding information includes at least one of IPv4 address, IPv6 address, and MPLS label value.

3. The cross-domain interconnection virtual link forwarding method according to claim 1, characterized in that, In step S3, the control plane generates a virtual link PL ID (PLID) for the cross-domain communication task and determines a list of gateways traversed by the cross-domain communication task. The gateway list includes the source access gateway (AGW), at least one border gateway (BGW), and the destination access gateway (AGW). The control plane converts the gateway list into a virtual link tag stack and forms a virtual link referral table. The virtual link referral table uses the PLID as the key and the global tag count, service category (TC), flag, and virtual link tag stack as values. The source access gateway (AGW) queries the virtual link referral table using the PLID to obtain the virtual link tag stack. The virtual link header includes a tag pointer and the virtual link tag stack. The tag pointer indicates the current global tag position that needs to be processed. When the source access gateway (AGW) encapsulates the virtual link header, it initializes the tag pointer to the global tag count.

4. The cross-domain interconnection virtual link forwarding method according to claim 3, characterized in that, In step S4, the gateway node locates the current global label according to the label pointer, reads the Label field and the Programmable Forwarding Action (PFA) field in the current global label, and queries the Intra-Domain Information Table (LIB) according to the Label field to obtain the intra-domain forwarding information of the node corresponding to the current global label. The gateway node updates the label pointer according to the forwarding action indicated by the PFA field in the current global label. When the forwarding action needs to continue forwarding, it locates the next-hop global label according to the updated label pointer, queries the domain information table LIB according to the Label field of the next-hop global label to obtain the next-hop intra-domain forwarding information, determines the outer bearer information of the next forwarding segment according to the conversion rules, and executes the forwarding action indicated by the PFA field in the current global label after completing the outer encapsulation. The border gateway (BGW) strips the outer bearer information used by the current forwarding segment at the domain boundary and encapsulates the outer bearer information used by the next forwarding segment.

5. The cross-domain interconnection virtual link forwarding method according to claim 1, characterized in that, Different network domains do not exchange intra-domain routing information, and each network domain maintains its existing network architecture and intra-domain forwarding mechanism.