A two-tier operator networking optimization method and system based on a new SID

Abstract

The present invention discloses a two-level operator networking optimization method and system based on a new SID. When using the End.CSC SID, the first-level operator can provide network programming services to the second-level operator and provide network quality assurance services based on the End.CSC SID. The second-level operator uses the End.CSC SID to establish its own SRv6 technology system network with the help of the first-level operator's backbone network, realize flexible business management and scheduling, and provide users with richer network services.

Description

Technical Field

[0001] The present invention belongs to the technical field of operator networking, and in particular relates to a two-level operator networking optimization method and system based on a novel SID. Background Art

[0002] In the operator networking scenario, there is a two-tier operator networking scenario, that is, the second-tier operator lacks the conditions to build a national backbone network and needs to use the backbone network of the first-tier operator to build a nationwide network to provide services to users. The first-tier operator provides channels to interconnect the scattered networks of the second-tier operators, but the first-tier operator does not perceive the routing information in the user network served by the second-tier operator. In this scenario, the relationship between the two-tier operators in the industry is another form of relationship between a large network covering the whole country or within the scope of industry requirements and the private networks of various organizations. The network diagram is shown below. Figure 1 shown. Figure 1 In the SRv6 technology system, because SRv6 packets are IPv6 packets, classic IPv6 technology can be used to achieve interoperability in a two-tier operator scenario. However, if both tiers of operators adopt the SRv6 technology system, using classic IPv6 technology will not allow end-to-end scheduling using SRv6 TE technology.

[0003] Currently, some solutions exist in the industry for Tier 2 carrier users to traverse Tier 1 carriers, but these solutions are complex and lack scalability. For example, to achieve end-to-end route calculation, Tier 2 carrier controllers need to build a topology that spans the Tier 1 carrier network and collect the corresponding TE information for traversing the Tier 1 carrier network. Currently, the industry uses a combination of BGP EPE and BGP virtual link technologies to address this issue, but these solutions suffer from the following drawbacks:

[0004] Shortcoming 1: The secondary operator controller cannot perceive the relationship between the regional network and the primary operator access point. The current solution uses BGP EPE to allocate peer-Node SID and peer-Adj SID. These two SIDs cannot be transmitted to the secondary operator. The secondary operator controller cannot perceive the information and automatically associate the regional network with the VPN channel access point provided by the primary operator. If you want to achieve this business goal, you need to collect the peer-NodeSID and peer-Adj SID data of the secondary operator to establish and maintain a mapping relationship with the VPN channel access point of the primary operator. Figure 2 As shown, Figure 2The second-tier carrier and the first-tier carrier have four access points: ASBR1, ASBR2, ASBR3, and ASBR4. To establish the entire network topology, the second-tier carrier needs to use BGP EPE and BGP virtual link technology to establish a fully interconnected relationship between the four ASBRs. This requires a total of n*(n-1) / 2 virtual links (the dotted arrows indicate the relationship between ASBR1 and the other three ASBRs). Each additional ASBR requires configuring the corresponding interconnection relationship on the existing ASBRs, making deployment and maintenance difficult.

[0005] The second shortcoming is that during the data forwarding process of the first-tier operator VPN channel, two layers of IPv6 headers will be encapsulated, which reduces the load efficiency of the communication data. Figure 3 shown. Figure 3 When user data packets enter the SRv6 backbone network of the second-tier operator, an SRv6 header is added. When entering the SRv6 backbone network of the first-tier operator through the access point, an SRv6 header is added, which makes the header too long and reduces the load transmission efficiency. Summary of the Invention

[0006] The technical problem to be solved by the present invention is to address the deficiencies of the above-mentioned prior art and provide a two-level carrier (Carrier Support Carrier) networking optimization method and system based on a new SID (End.CSC SID).

[0007] In order to achieve the above technical objectives, the technical solution adopted by the present invention is:

[0008] A two-tier operator networking optimization method based on a new SID includes:

[0009] 1) Define a new SID, End.CSC SID, to identify a Tier 1 operator's access point as capable of SRv6VPN services.

[0010] 2) Extend IGP / BGP, with Tier 1 carriers notifying Tier 2 carriers that access nodes have SRv6 VPN capabilities.

[0011] 3) Extending IGP / BGP, by advertising routes to the End.CSC SID or its corresponding locator, allows the primary carrier to notify the secondary carrier controller of SRv6 routes. The secondary carrier controller then adds the primary carrier access point when calculating the path, enabling the primary carrier to provide network programming services to the secondary carrier.

[0012] 4) The secondary carrier controller receives notification from the primary carrier through IGP that the access point has SRv6 VPN functionality and the End.CSC SID generated by the point, and identifies the point as the primary carrier's CSC SRv6 VPN access node.

[0013] 5) The secondary operator controller establishes a fully interconnected topology relationship between the SRv6 VPN access nodes identified as the primary operator CSC, obtaining a continuous and complete SRv6 network topology for the secondary operator.

[0014] 6) The first-tier operator performs performance quality management based on the End.CSC SID and synchronizes the performance quality management data with the second-tier operator;

[0015] 7) The secondary carrier receives the performance quality management data from the primary carrier based on the End.CSC SID, correlates and integrates it, and obtains the quality of the primary carrier's VPN channel in the SRv6 TE Policy.

[0016] To optimize the above technical solutions, specific measures taken also include:

[0017] The format of the End.CSC SID defined in 1) above is |Locator|Function(Arguments)|, which is generated by the IGP / BGP protocol extension using a global locator or a custom locator.

[0018] The above 2) specifically includes: extending the function of the IGP / BGP protocol within the VPN instance, and notifying the secondary operator access device provided by the primary operator PE device that the secondary operator SRv6VPN capability is activated when configuring the protocol on the interface bound to the VPN instance.

[0019] The above 3) specifically includes: the PE device of the first-level operator generates an End.CSC SID for the tunnel VPN, and then publishes and spreads the End.CSC SID or its corresponding Locator route to the PE devices of other first-level operators through MP-iBGP; the first-level operator establishes a dynamic routing protocol with the second-level operator, and the PE device of the first-level operator introduces the End.CSC SID or its corresponding Locator route into the dynamic routing protocol established with the second-level operator for publication. The routers of the second-level operator's local network learn the first-level operator's export route in the local area and add the first-level operator's access point when calculating the path to realize forwarding of forwarding plane messages.

[0020] The above 5) specifically includes: the SRv6 controller of the secondary operator establishes a BGP Linkstate address cluster peer relationship with each border ASBR router, collects SRv6 functional device information in the area by redistributing it to the BGP Linkstate address cluster through IGP, and the SRv6 controller of the secondary operator establishes a global interconnected topology relationship between all the CSC SRv6 VPN access nodes of the primary operator for SRv6 path calculation.

[0021] The above 6) specifically includes: the first-tier operator monitors the data forwarding performance indicators between End.CSC SIDs and synchronizes the monitoring data to users through the interface of the operation system.

[0022] The above 7) specifically includes: the second-tier operator obtains point-to-point performance data based on the End.CSC SID from the first-tier operator, then restores and integrates the monitoring data of the local system based on the End.CSC SID to obtain the quality of the first-tier operator's VPN channel in SRv6 TEPolicy, realizing end-to-end performance quality management.

[0023] A two-tier operator networking optimization system based on a new SID. The system's IGP routing control plane composition, MP-iBGP routing control plane composition, SRv6 routing control plane composition, and SRv6 controller networking structure are as follows:

[0024] The IGP routing control plane consists of the following: 1) OSPF is used to establish IGP routing in the customer network of the second-tier carrier; 2) ISIS IPv6 is used within the second-tier carrier to establish IGP routing in the regional backbone network; 3) eBGP is used to exchange routes between the VPN interfaces of the second-tier carrier and the first-tier carrier; 4) ISIS IPv6 is used to establish IGP routing within the first-tier carrier.

[0025] The routing control plane of MP-iBGP consists of the following: 1) A Tier 2 operator provides VPN services to users by using MP-iBGP to establish peers between the Tier 2 operator's PEs and transfer user routes within the VPN; 2) A Tier 1 operator provides VPN services to a Tier 2 operator by using MP-iBGP to establish peers between the Tier 1 operator's PEs and transfer routes from the Tier 2 operator's backbone SRv6 locator to establish the Tier 2 operator's SRv6 tunnel.

[0026] SRv6 routing control plane composition: 1) The secondary operator activates the ISIS for SRv6 function, publishes the locator route in ISIS, uses eBGP between the secondary operator and the primary operator to publish it to the primary operator's VPN, and then publishes it to other areas by the primary operator's MP-iBGP; 2) The secondary operator's ISIS generates an End SID for each node, and the secondary operator's PE1, PE2, PE3, and PE4 generate End SIDs respectively; 3) The secondary operator uses the global locator parameter through BGP to generate a DT4 SID for the VPN; the secondary operator's PE generates a DT4 SID; 4) The primary operator activates the ISIS for SRv6 function, publishes the locator route in ISIS, and the primary operator's MP-iBGP publishes the secondary operator's locator route; 5) The primary operator's ISIS generates an End SID for each node, and the primary operator generates the End SID for the PE; 6) The primary operator generates an End.CSC SID for the VPN through the CSC SRv6VPNSID generation module, and the primary operator's PE generates an End.CSC SID; 7) The primary operator generates an End.CSC SID in the CSC SRv6 The VPN publishing module publishes the End.CSC SID generated by the PE router;

[0027] SRv6 controller networking structure: 1) The Tier 2 operator's SRv6 controller establishes BGP Linkstate and BGPSR-Policy peer relationships with the Tier 2 operator's PE devices and ASBR devices to collect topology and TE information and issue SRv6 TE policies. 2) The Tier 1 operator uses eBGP to notify the Tier 2 operator's ASBR of the CSC SRv6 VPN function of the Tier 1 operator's PE devices. The ASBR then republishes the information via eBGP to BGP Linkstate, which is then sent to the Tier 2 operator's SRv6 controller. 3) The Tier 1 operator uses current industry solutions to establish the path calculation topology and issue SRv6 TE policies.

[0028] The above system includes header nesting scenarios and header merging scenarios when forwarding data;

[0029] The data forwarding process of the header nesting scenario is as follows:

[0030] 1) A user connected to CE1 accesses a service connected to CE2 and sends a DST, IPv4 / IPv6 message.

[0031] 2) The user's IPv4 / IPv6 packet arrives at the Tier 2 carrier PE1. Based on the SRv6 TEPolicy policy issued by the controller, the user packet is encapsulated into an SRv6 VPN packet and forwarded to the Tier 2 carrier ASBR1. The packet contains the IPv6 header, SRH header, and payload.

[0032] 3) After the packet reaches the Tier 2 carrier's ASBR, the destination address is replaced with the Tier 1 carrier's End.CSC SID based on the SRH header, and the packet is then forwarded to Tier 1 carrier access PE1.

[0033] 4) The message arrives at the Tier 1 carrier access PE1, undergoes programming operations based on the End.CSC SID requirements, and is then sent to the Tier 1 carrier backbone P. The programming operations include: extracting the next hop from the SRH to replace the destination address in the IPv6 header of the Tier 2 carrier message; and placing the Tier 2 carrier's SRv6 message as the payload into the Tier 1 carrier's SRv6 message, including the IPv6 header, SRH header, and payload.

[0034] 5) When the message reaches the Tier 1 carrier backbone P, the packet is forwarded to the Tier 1 carrier access PE2 using the current standard SRv6 message forwarding operation. The next hop of the SRH is removed and replaced with the destination address of the IPv6 message.

[0035] 6) After the message arrives at the Tier 1 carrier access PE2, it follows the current conventional SRv6 message forwarding operation to retrieve the next hop from the SRH. It finds that the next hop is the local End.CSC SID, pops the Tier 1 carrier's SRv6 header, and then queries the IPv6 destination address in the Tier 2 carrier's SRv6 message header. It then performs the End.CSC SID programming operation in the VPN, retrieves the next hop from the SRH, replaces it with the IPv6 destination address in the Tier 2 carrier's SRv6 message, and forwards it to Tier 2 carrier ASBR2.

[0036] 7) After the message reaches the secondary operator ASBR2, it is forwarded to the secondary operator access PE2 according to the normal SRv6 message forwarding operation, replacing the IPv6 destination address in the SRv6 message header with the SRH next hop;

[0037] 8) After the message arrives at the secondary operator access PE2, it extracts the SRH next-hop DT4 SID according to the normal SRv6 message operation, pops the SRv6 message header according to the DT4 SID operation, and queries the route of the user's original IPv4 message header in the VPN. It forwards it to the user access CE2 and then continues to forward it to the corresponding server in the user network.

[0038] The data forwarding process in the above header merging scenario is as follows:

[0039] 1) A user connected to CE1 accesses a service connected to CE2 and sends a DST, IPv4 / IPv6 message.

[0040] 2) The user's IPv4 / IPv6 packet arrives at the Tier 2 carrier PE1. Based on the SRv6 TEPolicy policy issued by the controller, the user packet is encapsulated into an SRv6 VPN packet and forwarded to the Tier 2 carrier ASBR1. The packet contains the IPv6 header, SRH header, and payload.

[0041] 3) After the packet reaches the Tier 2 carrier's ASBR, the destination address is replaced with the Tier 1 carrier's End.CSC SID based on the SRH header, and the packet is then forwarded to Tier 1 carrier access PE1.

[0042] 4) The message arrives at the Tier 1 carrier access PE1, is programmed according to the End.CSC SID requirements, and then sent to the Tier 1 carrier backbone P. The programming operations are as follows: the next hop is extracted from the SRH to replace the destination address in the IPv6 header of the Tier 2 carrier message; the IPv6 header in the Tier 2 carrier's SRv6 message is removed, the node before the local End.CSCSID in the SRH list is deleted, the Tier 1 carrier's SRv6 TE Policy node is inserted into the front end to form a new SRH list, a new IPv6 header is generated, and a new SRv6 message is assembled, including the IPv6 header, SRH header, and payload.

[0043] 5) When the message reaches the Tier 1 carrier backbone P, the packet is forwarded to the Tier 1 carrier access PE2 using the current standard SRv6 message forwarding operation. The next hop of the SRH is removed and replaced with the destination address of the IPv6 message.

[0044] 6) After the message arrives at the Tier 1 carrier access PE2, it follows the current conventional SRv6 message forwarding operation to retrieve the next hop from the SRH. It finds that the next hop is the local End.CSC SID. After performing the End.CSC SID programming operation, it further retrieves the next hop from the SRH and replaces it with the IPv6 destination address in the Tier 2 carrier's SRv6 message. The message is then forwarded to Tier 2 carrier ASBR2.

[0045] 7) After the message arrives at the secondary operator ASBR2, it follows the normal SRv6 message forwarding operation to replace the IPv6 destination address in the SRv6 message header with the SRH next hop and forward it to the secondary operator access PE2. After the message arrives at the secondary operator access PE2, it follows the normal SRv6 message operation to extract the SRH next hop DT4 SID, and according to the DT4 SID operation, pops the SRv6 message header, queries the route of the user's original IPv4 message header in the VPN, forwards it to the user access CE2, and then continues to forward it to the corresponding server in the user network.

[0046] The present invention has the following beneficial effects:

[0047] The present invention designs an End.CSC SID and its transmission for a two-tier operator scenario:

[0048] When using End.CSC SID, Tier 1 operators can provide Tier 2 operators with network programming services based on End.CSC SID, as well as value-added network quality assurance services based on End.CSC SID. Tier 2 operators can use End.CSC SID to establish their own SRv6 technology-based networks with the help of Tier 1 operator backbone networks, enabling flexible business management and scheduling, and providing users with richer network services.

[0049] The End.CSC SID of the present invention can be used to identify that the access point of the first-tier operator provides SRv6 VPN services.

[0050] The present invention extends IGP / BGP, and a first-level operator can notify a second-level operator that an access node has the function of CSC SRv6 VPN.

[0051] The present invention extends IGP / BGP and can introduce End.CSC SID or its corresponding Locator for route publishing, so that the first-level operator notifies the SRv6 route to the second-level operator controller. The second-level operator controller adds the first-level operator access node when calculating the path, thereby realizing the network programming service provided by the first-level operator.

[0052] The secondary operator controller of the present invention receives the access point notified by the primary operator through IGP, which has the function of CSC SRv6VPN and the End.CSC SID generated by the node, and identifies the node as a CSC SRv6 VPN access node of the primary operator.

[0053] The secondary operator controller of the present invention establishes a fully interconnected topology relationship between the identified primary operator CSC SRv6 VPN access nodes, thereby constructing a continuous and complete SRv6 network topology of the secondary operator.

[0054] The present invention provides a programming operation mode for End.CSC SID.

[0055] The present invention performs performance quality management on the first-level operator based on End.CSC SID and synchronizes data to the second-level operator.

[0056] The second-level operator of the present invention receives the performance management data based on the End.CSC SID of the first-level operator, and obtains the quality of the VPN channel of the first-level operator in the SRv6 TE Policy through correlation and integration. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 This is a schematic diagram of traditional network configuration;

[0058] Figure 2 Schematic diagram of the mapping relationship between the VPN channel access points of the second-tier operator and the first-tier operator in the traditional network;

[0059] Figure 3 Schematic diagram of the data forwarding process for a Tier 1 operator VPN channel in a traditional network;

[0060] Figure 4 Schematic diagram of the module for generating and issuing End.CSC SID for the PE device of the first-tier operator of the present invention;

[0061] Figure 5 This is a schematic diagram of End.CSC SID routing diffusion in a secondary operator according to the present invention;

[0062] Figure 6 The second-tier operator of the present invention builds a global topology diagram based on End.CSC SID or corresponding Locator information;

[0063] Figure 7 The PE equipment forwarding module relationship of the first-tier operator of the present invention;

[0064] Figure 8 Provide customized performance management services and display schematic diagrams for the first-tier operator of the present invention to the second-tier operator;

[0065] Figure 9 This is a schematic diagram of a first-tier operator providing programmable network services to a second-tier operator according to the present invention;

[0066] Figure 10 are the topology and Locator parameters of the present invention;

[0067] Figure 11 The control plane establishment process for the first-tier operator and the second-tier operator of the present invention;

[0068] Figure 12 This is a schematic diagram of data forwarding in a header-nested scenario according to the present invention;

[0069] Figure 13 This is a schematic diagram of data forwarding in the header merging scenario of the present invention. DETAILED DESCRIPTION

[0070] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0071] Although the steps in the present invention are arranged with numbers, they are not intended to limit the order of the steps. Unless the order of the steps is clearly stated or the execution of a step requires other steps as a basis, the relative order of the steps can be adjusted. It is understood that the term "and / or" used herein refers to and covers any and all possible combinations of one or more of the associated listed items.

[0072] The present invention provides a two-level operator networking optimization method based on a novel SID, comprising:

[0073] 1) Define a new SID, End.CSC SID, to identify a Tier 1 operator's access point as having SRv6VPN service.

[0074] 2) Extend IGP / BGP, with Tier 1 carriers notifying Tier 2 carriers that access nodes have SRv6 VPN capabilities.

[0075] 3) Extending IGP / BGP, by advertising routes to the End.CSC SID or its corresponding locator, allows the primary carrier to notify the secondary carrier controller of SRv6 routes. The secondary carrier controller then adds the primary carrier access point when calculating the path, enabling the primary carrier to provide network programming services to the secondary carrier.

[0076] 4) The secondary carrier controller receives notification from the primary carrier through IGP that the access point has SRv6 VPN functionality and the End.CSC SID generated by the point, and identifies the point as the primary carrier's CSC SRv6 VPN access node.

[0077] 5) The secondary operator controller establishes a fully interconnected topology relationship between the SRv6 VPN access nodes identified as the primary operator CSC, obtaining a continuous and complete SRv6 network topology for the secondary operator.

[0078] 6) The first-tier operator performs performance quality management based on the End.CSC SID and synchronizes the performance quality management data with the second-tier operator;

[0079] 7) The secondary carrier receives the performance quality management data from the primary carrier based on the End.CSC SID, correlates and integrates it, and obtains the quality of the primary carrier's VPN channel in the SRv6 TE Policy.

[0080] In the embodiment, this patent includes content such as End.CSC SID and End.CSC SID propagation.

[0081] End.CSC SID defines a new SID in the format of |Locator|Function(Arguments)|, indicating that the locator can be configured to use a globally configured locator or an independent custom locator. Function(Arguments) is used to identify the VPN deployed on the PE device for accessing the secondary carrier network or private network backbone network. The corresponding forwarding actions include VPN decapsulation, VPN instance routing table lookup, SRv6 header merging, and other programming actions, which can be further expanded based on the services provided.

[0082] The End.CSC SID is generated by the PE device of the Tier 1 carrier (connected to the Tier 2 carrier) and then propagated to the Tier 2 carrier's backbone network. This can be achieved by extending BGP functionality to generate the End.CSC SID. BGP or IGP extensions can introduce End.CSC SID routes and then advertise them for propagation.

[0083] The schematic diagram of the module for generating and issuing End.CSC SID on the PE equipment of the first-tier operator is as follows: Figure 4 shown.

[0084] CSC SRv6 VPN SID Generation Module: This module extends dynamic routing protocols (BGP / ISIS / OSPF) to generate End.CSC SIDs. This can be generated using a global locator or a user-defined locator for the CSC SRv6 VPN SID. The advantage of using a global locator is that it simplifies planning, design, configuration, deployment, and operation and maintenance. However, this exposes the global locator to tier-2 operators. The advantage of using a customized locator is that it hides the tier-1 operator's locator and allows different locators to be planned for different tier-2 operators. This allows for differentiated services not only by using VPNs to identify users but also by using locators to identify tunnels.

[0085] The VPN dynamic protocol extension module extends the IGP protocol functionality within a VPN instance. When protocols such as OSPFv3, ISIS IPv6, and BGP are configured on the interface bound to the VPN instance, the module notifies the Tier 2 carrier access device provided by the Tier 1 carrier PE device that the Tier 2 carrier SRv6 VPN capability has been activated.

[0086] CSC SRv6 VPN SID advertisement module: The End.CSC SID needs to be advertised between the PEs of the first-tier carrier through MP-iBGP. The advertised routes can be either the Locator or the End.CSC SID. The End.CSC SID also needs to be advertised on the interface connecting the first-tier carrier's PE router to the second-tier carrier, notifying the second-tier carrier of the End.CSC SID.

[0087] End.CSC SID route diffusion diagram is as follows Figure 5 shown.

[0088] After the Tier 1 carrier access PE1 generates an End.CSC SID for the CSC SRv6 VPN through BGP, it can choose to advertise and propagate the End.CSC SID or its corresponding locator route to other Tier 1 carrier PEs through MP-iBGP.

[0089] The Tier 1 carrier and Tier 2 carrier establish a dynamic routing protocol using ISIS IPv6 / OSPFv3 / eBGP. The Tier 1 carrier's PE device can import the End.CSC SID or its corresponding locator route into the dynamic routing protocol established with the Tier 2 carrier and advertise it. Routers in the Tier 2 carrier's local network can then learn the Tier 1 carrier's egress routes, enabling forwarding of packets on the forwarding plane.

[0090] The secondary operator builds a global topology diagram based on the End.CSC SID or the corresponding locator information. Figure 6 shown.

[0091] The Tier 2 carrier's SRv6 controller establishes BGP Linkstate address cluster peer relationships with each border ASBR router. It collects information about SRv6-capable devices in the area by redistributing information to the BGP Linkstate address cluster via IGP. Because the Tier 1 carrier has announced through IGP / eBGP that the corresponding access PE router has activated the Tier 2 carrier's SRv6 VPN capability, the Tier 2 carrier's SRv6 controller can establish a fully interconnected topology between all Tier 2 carrier's SRv6 VPN-enabled access points for SRv6 path calculation.

[0092] The relationship between the forwarding modules of the PE equipment of the first-tier operator is as follows: Figure 7 shown.

[0093] Message receiving module: receives messages, determines message processing, and identifies SRv6 messages;

[0094] SRv6 processing module: processes received SRv6 packets, such as extracting and identifying SIDs;

[0095] End.CSC SID processing submodule: This module processes messages whose SID is identified as the local End.CSC SID, performs network programming and corresponding message processing and message encapsulation.

[0096] Routing query module: performs routing query according to the destination address in the message header and sends the message to the message forwarding module for forwarding.

[0097] Packet forwarding module: forwards packets according to packet QoS requirements.

[0098] Tier 1 operators provide customized performance management services to Tier 2 operators and display schematic diagrams such as Figure 8 shown.

[0099] Tier-1 operators can use iFIT to monitor data forwarding performance indicators between End.CSC SIDs and synchronize monitoring data to users through the interface of the operation system. After obtaining the data, Tier-2 operators can restore it based on the End.CSC SID and associate and integrate it with the iFIT monitoring data of the local system to achieve end-to-end performance quality management.

[0100] A diagram of a Tier 1 operator providing programmable network services to a Tier 2 operator is shown below. Figure 9 shown.

[0101] After the primary carrier publishes the End.CSC SID to the secondary carrier, the secondary carrier carries this End.CSC SID in the SRH header of the forwarded message. After the message reaches the primary carrier's PE router, the PE router can be programmed based on the End.CSC SID. For example, the problem of the two-layer IPv6 header mentioned in the background technology can be programmed into a single IPv6 header containing only one SRH header, which can at least save space for one basic IPv6 header. It can also be achieved by trimming the already used nodes in the list of the secondary carrier's SRH header. The disadvantage of this is that the SRH list is incomplete after reaching the tail end, which may affect some tracing and fault handling functions.

[0102] The present invention also proposes a two-level operator networking optimization system based on a new SID, and the specific embodiments are as follows:

[0103] Topology and Locator parameters such as Figure 10 shown.

[0104] User 1.1.1.1 / 24 on the intranet of user CE1 of the secondary carrier's VPN named 1000 accesses service 2.2.2.2 / 24 on the intranet of user CE2 of the secondary carrier's VPN named 1000 through the backbone network of the secondary carrier and the primary carrier (bearing VPN named 100).

[0105] The global locators of the Level 2 operator PE1, ASBR1, ASBR2, and PE2 start with 2000 and are 2000::1 / 64, 2000::2 / 64, 2000::3 / 64, and 2000::4 / 64, respectively.

[0106] The global locators for the Tier 1 carrier accessing PE1, P, and PE2 start with 3000 and are 3000::1 / 64, 3000::2 / 64, and 3000::3 / 64, respectively.

[0107] The locators for generating End.CSC SIDs for PE1 and PE2 connected to the first-tier carrier do not use global parameters. Instead, they are customized and start with 4000, namely 4000::1 / 64 and 4000::2 / 64.

[0108] The control plane establishment process of the first-tier and second-tier operators is as follows: Figure 11 shown.

[0109] IGP routing control plane composition:

[0110] 1) The secondary carrier user network uses OSPF to establish IGP routing.

[0111] 2) The secondary carrier uses ISIS IPv6 internally to establish IGP routing for the regional backbone network.

[0112] 3) eBGP is used for route exchange between the VPN interfaces of the second-tier carrier and the first-tier carrier.

[0113] 4) Use ISIS IPv6 to establish IGP routing within the first-tier carrier.

[0114] The routing control plane of MP-iBGP is composed of the following (MP-iBGP can use a multi-level RR structure, which will not be elaborated here):

[0115] 1) The secondary operator provides VPN (1000) services to users, uses MP-iBGP to establish peers between the PEs of the secondary operator, and performs user route transmission within the VPN (1000).

[0116] 2) The first-tier operator provides VPN (100) services to the second-tier operator, establishes peers between the first-tier operator's PEs using MP-iBGP, and transmits the routes of the second-tier operator's backbone SRv6 Locator to establish the second-tier operator's SRv6 tunnel.

[0117] SRv6 routing control plane composition:

[0118] 1) The secondary operator activates the ISIS for SRv6 function, publishes the locator route in ISIS, uses eBGP between the secondary operator and the primary operator to publish it to the VPN (100) of the primary operator, and then publishes it to other areas by MP-iBGP of the primary operator.

[0119] 2) The secondary operator ISIS generates an End SID for each node. The End SIDs for PE1, PE2, PE3, and PE4 are 2000::1:0000:0000:0000:1000, 2000::2:0000:0000:0000:1000, 2000::3:0000:0000:0000:1000, and 2000::4:0000:0000:0000:1000, respectively.

[0120] 3) The secondary carrier uses the global locator parameter through BGP to generate a DT4 SID for VPN (1000). The secondary carrier's PE1 and PE2 generate the DT4 SIDs: 2000::1:0000:0000:0001:1000 and 2000::4:0000:0000:0001:1000.

[0121] 4) The first-tier carrier activates the ISIS for SRv6 function, publishes the locator route in ISIS, and publishes the second-tier carrier's locator route using MP-iBGP.

[0122] 5) The first-tier operator ISIS generates an End SID for each node. The first-tier operator generates the EndSIDs 3000::1:0000:0000:0000:0100 for PE1, 3000::2:0000:0000:0000:0100 for PE2, and 3000::3:0000:0000:0000:0100 for PE1, P, and PE2.

[0123] 6) The first-level operator generates End.CSCSID for VPN (100) through the CSC SRv6 VPN SID generation module. In the embodiment, the generation is performed using a specified locator. The first-level operator PE1 and PE2 generate End.CSC SIDs: 4000::1:0000:0000:0003:0100 and 4000::2:0000:0000:0003:0100.

[0124] 7) The Tier 1 carrier publishes the End.CSC SID (4000::1:0000:0000:0003:0100 and 4000::2:0000:0000:0003:0100) or its locator (4000::1 / 64 and 4000::2 / 64) generated by the PE router in the CSC SRv6 VPN SID advertisement module. In the embodiment, the publishing module of CSC SRv6 VPN SID introduces the route into eBGP and publishes it to the secondary operator in this area. In the embodiment, the primary operator PE1 introduces 4000::1:0000:0000:0003:0100 or 4000::1 / 64 into eBGP and publishes it to the secondary operator ASBR1, and then introduces ISIS IPv6 and publishes it in the secondary operator left area of ​​the embodiment; the primary operator PE1 introduces 4000::1:0000:0000:0003:0100 or 4000::1 / 64 into MP-iBGP and publishes it to the VPN (100) of the primary operator PE2, and then introduces eBGP and publishes it to the secondary operator ASBR2, thereby realizing the publication of the CSC SRv6VPN access point route in the left area to the right area.

[0125] SRv6 controller network structure:

[0126] 1) The Tier 2 operator's SRv6 controller establishes BGPLinkstate and BGPSR-Policy peer relationships with the Tier 2 operator's PE devices and ASBR devices, respectively, to collect topology and TE information and distribute SRv6 TE policies. BGP RR can be used to establish a networking structure. A two-tier structure is recommended, with an independent primary RR. The ASBR establishes a primary reflection relationship with the primary RR. The ASBR device acts as the secondary RR for the region, establishing a secondary reflection relationship with the PE routers within the region.

[0127] 2) The Tier 2 carrier's SR router information is completed through ISIS and republished via BGP Linkstate. The Tier 1 carrier uses eBGP to advertise the CSC SRv6 VPN functionality of the Tier 1 carrier's PE equipment to the Tier 2 carrier's ASBR. The ASBR then republishes the information via eBGP via BGP Linkstate. Finally, BGP Linkstate is distributed to the SRv6 controller. This allows the Tier 2 carrier controller to gather topology information for all SRv6 routers and access points equipped with CSC SRv6 VPN functionality provided by the Tier 1 carrier. Fullmesh links are established between Tier 1 carrier access points to connect the topologies of each region and map the entire network.

[0128] 3) Tier 1 operators use current industry solutions to establish a path calculation topology and deliver SRv6 TE Policy structures.

[0129] The embodiment assumes that a user uses 1.1.1.1 / 24 in the network connected to the left user CE1 to access the service 2.2.2.2 / 24 in the network connected to the right user CE2. In the secondary operator, the controller issues an SRv6 TE Policy for VPN (1000). Accessing the VPN (1000) network under the secondary operator PE1 from the VPN (1000) network under the secondary operator PE2 requires passing through the secondary operator access PE1, the secondary operator ASBR1, the primary operator access PE1, the primary operator access PE2, the secondary operator ASBR2, and the secondary operator access PE2. In the primary operator, the controller issues an SRv6 TE Policy for VPN (100). Accessing the VPN (100) network under the primary operator access PE1 from the VPN (100) network under the primary operator access PE2 requires passing through nodes such as the primary operator access PE1, the primary operator backbone P, and the primary operator access PE2. The data forwarding layer includes header nesting scenarios and header merging scenarios. In the header merging scenario, the End.CSCSID generated by the first-level operation access PE1 and PE2 is 4000::2:0000:0000:0003:0200 and 4000::2:0000:0000:0003:0200.

[0130] Header nested scene data forwarding such as Figure 12 shown.

[0131] 1) User 1.1.1.1 / 24 connected to user CE1 accesses service 2.2.2.2 / 24 connected to user CE2, sending an IPv4 packet with DST: 2.2.2.2 and SRC: 1.1.1.1.

[0132] 2) The user's IPv4 packet reaches the Tier 2 operator's PE1. Based on the SRv6 TEPolicy policy issued by the controller, the user packet is encapsulated into an SRv6 VPN packet and forwarded to the Tier 2 operator's ASBR1. The packet includes the IPv6 header (dst:2000::2:0000:0000:0000:1000, src:2000::1 / 128) and the SRH header (2000::2:0000:0000:0000:1000, 4000::1:0000:0000:0003:0100, 4000::2:0000:0000:0003:0100, 2000::3:0000:0000:0000:1000). , 2000::4:0000:0000:0000:1000, 2000::4:0000:0000:0001:1000), payload (original user IPv4 message).

[0133] 3) After the packet reaches the Tier 2 operator's ASBR, the destination address is changed to the Tier 1 operator's End.CSC SID: 4000::1:0000:0000:0003:0100 based on the SRH header, and then the packet is forwarded to Tier 1 operator's access PE1.

[0134] 4) The message arrives at the first-tier operator access PE1, is programmed according to the requirements of the End.CSC SID, and then sent to the first-tier operator backbone P. The End.CSC SID programming operations assumed in this embodiment are as follows: 1. The next hop 4000::2:0000:0000:0003:0100 is extracted from the SRH and replaced with the destination address in the IPv6 header of the secondary operator's message. 2. The secondary operator's SRv6 message is placed as a payload in the primary operator's SRv6 message, including the IPv6 header (dst:3000::2:0000:0000:0003:0100, src:3000::1 / 128), SRH header (3000::2:0000:0000:0003:0100, 3000::3:0000:0000:0003:0100, 4000::2:0000:0000:0003:0100), and payload (secondary operator's SRv6 message).

[0135] 5) When the packet reaches the Tier 1 carrier backbone P, the packet is forwarded to the Tier 1 carrier access PE2 using the current standard SRv6 packet forwarding operation. The next hop of the SRH (3000::3:0000:0000:0003:0100) is replaced with the destination address of the IPv6 packet.

[0136] 6) After the packet arrives at the Tier 1 carrier access PE2, it follows the current conventional SRv6 packet forwarding operation, extracting the next hop (4000::2:0000:0000:0003:0100) from the SRH. It finds that the next hop is the local End.CSC SID, pops the Tier 1 carrier's SRv6 header, and then queries the IPv6 destination address (4000::2:0000:0000:0003:0100) in the Tier 2 carrier's SRv6 packet header. It then performs the End.CSC SID programming operation in the VPN, extracts the next hop (2000::3:0000:0000:0000:1000) from the SRH, replaces it with the IPv6 destination address in the Tier 2 carrier's SRv6 packet, and forwards the packet to Tier 2 carrier ASBR2.

[0137] 7) After the message reaches the secondary operator ASBR2, according to the normal SRv6 message forwarding operation, the SRH next hop (2000::4:0000:0000:0000:1000) is replaced with the IPv6 destination address in the SRv6 message header and forwarded to the secondary operator access PE2.

[0138] 8) After the message arrives at the secondary operator access PE2, it extracts the SRH next hop DT4SID according to the conventional SRv6 message operation, pops up the SRv6 message header according to the DT4 SID operation, and queries the route of the user's original IPv4 message header 2.2.2.2 in VPN (1000), forwards it to the user access CE2, and then continues to forward it to the corresponding server in the user network.

[0139] Header merge scene data forwarding Figure 13 shown.

[0140] 1) User 1.1.1.1 / 24 connected to user CE1 accesses service 2.2.2.2 / 24 connected to user CE2, sending an IPv4 packet with DST: 2.2.2.2 and SRC: 1.1.1.1.

[0141] 2) The user's IPv4 packet reaches the Tier 2 operator's PE1. Based on the SRv6 TEPolicy policy issued by the controller, the user packet is encapsulated into an SRv6 VPN packet and forwarded to the Tier 2 operator's ASBR1. The packet contains the IPv6 header (dst:2000::2:0000:0000:0000:1000, src:2000::1 / 128) and the SRH header (2000::2:0000:0000:0000:1000, 4000::1:0000:0000:0003:0200, 4000::2:0000:0000:0003:0200, 2000::3:0000:0000:0000:1000). , 2000::4:0000:0000:0000:1000, 2000::4:0000:0000:0001:1000), payload (original user IPv4 message).

[0142] 3) After the packet reaches the Tier 2 operator's ASBR, the destination address is changed to the Tier 1 operator's End.CSC SID: 4000::1:0000:0000:0003:0200 based on the SRH header, and then the packet is forwarded to the Tier 1 operator's access PE1.

[0143] 4) The message arrives at the first-tier operator access PE1, is programmed according to the requirements of the End.CSC SID, and then sent to the first-tier operator backbone P. The End.CSC SID programming operation assumed in this embodiment is as follows: 1. The next hop 4000::2:0000:0000:0003:0200 is extracted from the SRH and replaced with the destination address in the IPv6 header of the secondary operator's message. 2. The IPv6 header in the secondary operator's SRv6 message is removed, and the node before the local End.CSC SID in the SRH list is deleted. The node of the primary operator's SRv6 TE Policy is inserted into the front end to form a new SRH list. A new IPv6 header is generated and a new SRv6 message is assembled, including the IPv6 header (dst: 3000::2:0000:0000:0003:0100, src: 3000::1 / 128), the SRH header (3000::2:0000:0000:0003:0100, 3000::3:0000:0000:0003:0100 , 4000::2:0000:0000:0003:0200 , 2000::3:0000:0000:0000:1000 , 2000::4:0000:0000:0000:1000 , 2000::4:0000:0000:0001:1000 ), payload (user IPv4 packet);

[0144] 5) When the packet reaches the Tier 1 carrier backbone P, the packet is forwarded to the Tier 1 carrier access PE2 using the current standard SRv6 packet forwarding operation. The next hop of the SRH (3000::3:0000:0000:0003:0100) is replaced with the destination address of the IPv6 packet.

[0145] 6) After the message arrives at the Tier 1 carrier access PE2, it follows the current conventional SRv6 message forwarding operation, extracts the next hop (4000::2:0000:0000:0003:0200) from the SRH, finds that the next hop is the local End.CSC SID, performs the End.CSC SID programming operation, and then extracts the next hop (2000::3:0000:0000:0000:1000) from the SRH to replace the IPv6 destination address in the Tier 2 carrier SRv6 message. The message is then forwarded to Tier 2 carrier ASBR2.

[0146] 7) After the message reaches the secondary operator ASBR2, according to the normal SRv6 message forwarding operation, the SRH next hop (2000::4:0000:0000:0000:1000) is replaced with the IPv6 destination address in the SRv6 message header and forwarded to the secondary operator access PE2.

[0147] After the message arrives at the secondary operator access PE2, it extracts the SRH next hop DT4 SID according to the conventional SRv6 message operation, pops up the SRv6 message header according to the DT4SID operation, and queries the route of the user's original IPv4 message header 2.2.2.2 in VPN (1000), forwards it to the user access CE2, and then continues to forward it to the corresponding server in the user network.

[0148] The first-tier operator can monitor the tunnel quality between 4000::1:0000:0000:0003:0100 (or 4000::1:0000:0000:0003:0200) and 4000::2:0000:0000:0003:0100 (or 4000::2:0000:0000:0003:0200) through iFIT and provide feedback to the second-tier operator. By associating 4000::1:0000:0000:0003:0100 (or 4000::1:0000:0000:0003:0200) and 4000::2:0000:0000:0003:0100 (or 4000::2:0000:0000:0003:0200) with the entire TE trail, segment-by-segment performance indicators are displayed, supporting network maintenance and management.

[0149] The glossary of terms in this article is explained as follows:

[0150] IPv6: Internet Protocol Version 6, is the second-generation standard protocol of the network layer protocol. It is a set of specifications designed by the Internet Engineering Task Force (IETF).

[0151] SRv6: Segment Routing IPv6, a protocol designed based on source routing that uses segment routing on the IPv6 forwarding plane on the network.

[0152] SRv6 Segment Identifier (SRv6 SID) is an IPv6 address. It consists of two parts: Locator and Function. The format is Locator:Function. The Locator part occupies the high-order bits of the IPv6 address, and the Function part occupies the rest of the IPv6 address.

[0153] Locator: A locator is a component of the SRv6 SID and provides location information. After a node is configured with a locator, the system generates a locator segment route and propagates it within the SR domain via IGP. Other nodes in the network can locate the node using the locator segment route. All SRv6 SIDs advertised by the node can also be reached using this locator segment route.

[0154] CSC: Carrier Support Carrier, a business scenario in which small operators interconnect their own regional networks through the backbone network of large operators to support the independent development of VPN users.

[0155] SRv6 VPN: A virtual private network solution that uses Segment Routing IPv6 tunneling technology to interconnect virtual private networks.

[0156] CSC SRv6 VPN: A solution for Tier 1 carriers to provide regional network interconnection services to Tier 2 carriers using the SRv6 VPN solution.

[0157] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above and that the invention can be embodied in other specific forms without departing from the spirit or essential characteristics of the invention. Therefore, the embodiments should be considered in all respects as illustrative and non-restrictive, and the scope of the invention is defined by the appended claims, not the foregoing description, and all variations within the meaning and range of equivalents of the claims are intended to be included therein. Any reference sign in a claim should not be construed as limiting the claim to which it relates.

[0158] In addition, it should be understood that although this specification is described in terms of implementation methods, not every implementation method contains only one independent technical solution. This narrative method of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment can also be appropriately combined to form other implementation methods that can be understood by those skilled in the art.

Claims

1. A two-level operator networking optimization method based on a new SID, characterized in that: include: 1) Define a new SID, the End.CSC SID, to identify Tier 1 carrier access points as capable of SRv6 VPN services. 2) Extending IGP / BGP, with Tier 1 carriers notifying Tier 2 carriers that access nodes are SRv6 VPN-capable; 3) Extending IGP / BGP, by advertising routes to the End.CSC SID or its corresponding locator, allows the Tier 1 carrier to advertise SRv6 routes to the Tier 2 carrier controller. The Tier 2 carrier controller then adds the Tier 1 carrier access point when calculating the path, enabling the Tier 1 carrier to provide network programming services to the Tier 2 carrier. 4) The secondary carrier controller receives notification from the primary carrier through IGP that the access point has SRv6 VPN functionality and the End.CSC SID generated by the access point, and identifies the access point as a CSC SRv6 VPN access node of the primary carrier. 5) The secondary carrier controller establishes a fully interconnected topology between the primary carrier CSC SRv6 VPN access nodes, obtaining a continuous and complete SRv6 network topology for the secondary carrier. 6) The Tier 1 operator performs performance quality management based on the End.CSC SID and synchronizes the performance quality management data with the Tier 2 operator; 7) The second-tier carrier receives the performance quality management data from the first-tier carrier based on the End.CSC SID, correlates and integrates it, and obtains the quality of the first-tier carrier's VPN channel in the SRv6 TE Policy.

2. The two-tier operator network optimization method based on a new SID according to claim 1, characterized in that: The format of the End.CSC SID defined in 1) is |Locator|Function(Arguments)|, which is generated by the IGP / BGP protocol extension using a global locator or a custom locator.

3. The two-tier operator network optimization method based on a new SID according to claim 1, characterized in that: The above 2) specifically includes: extending the function of the IGP / BGP protocol in the VPN instance, and notifying the secondary carrier access device provided by the primary carrier PE device that the secondary carrier SRv6 VPN capability is activated when configuring the protocol on the interface bound to the VPN instance.

4. The two-tier operator network optimization method based on a novel SID according to claim 1, characterized in that: The above 3) specifically includes: the PE device of the first-level operator generates an End.CSC SID for the tunnel VPN, and then advertises and spreads the End.CSC SID or its corresponding Locator route to the PE devices of other first-level operators through MP-iBGP; the first-level operator establishes a dynamic routing protocol with the second-level operator, and the PE device of the first-level operator introduces the End.CSC SID or its corresponding Locator route into the dynamic routing protocol established with the second-level operator for advertisement. The routers of the second-level operator's local network learn the first-level operator's local export route and add the first-level operator's access point when calculating the path, thereby realizing forwarding of forwarding plane messages.

5. The two-tier operator network optimization method based on a new SID according to claim 1, characterized in that: 5) specifically includes: the SRv6 controller of the secondary operator establishes a BGP Linkstate address cluster peer relationship with each border ASBR router, collects SRv6 functional device information in the area by redistributing it to the BGP Linkstate address cluster through IGP, and the SRv6 controller of the secondary operator establishes a global interconnected topology relationship between all the CSC SRv6 VPN access nodes of the primary operator for SRv6 path calculation.

6. The two-tier operator network optimization method based on a new SID according to claim 1, characterized in that: The above 6) specifically includes: the first-tier operator monitors the data forwarding performance indicators between End.CSC SIDs and synchronizes the monitoring data to users through the interface of the operation system.

7. The two-tier operator network optimization method based on a new SID according to claim 1, characterized in that: 7) specifically includes: the second-tier operator obtains point-to-point performance data based on the End.CSC SID from the first-tier operator, then restores and correlates the data with the monitoring data from the local system based on the End.CSC SID to obtain the quality of the first-tier operator's VPN channel in the SRv6 TE Policy, thereby implementing end-to-end performance quality management.

8. A two-level operator networking optimization system based on a new SID, characterized by: The IGP routing control plane composition, MP-iBGP routing control plane composition, SRv6 routing control plane composition and SRv6 controller networking structure of the system are as follows: The IGP routing control plane consists of the following: 1) OSPF is used to establish IGP routing in the Tier 2 carrier's user network; 2) ISIS IPv6 is used within the Tier 2 carrier to establish IGP routing for the regional backbone network; 3) eBGP is used for route exchange between the Tier 2 carrier and Tier 1 carrier's VPN interface; 4) ISIS IPv6 is used within the Tier 1 carrier to establish IGP routing. The MP-iBGP routing control plane consists of the following: 1) A Tier 2 carrier provides VPN services to users by using MP-iBGP to establish peering relationships between the Tier 2 carrier's PEs and transfer user routes within the VPN. 2) A Tier 1 carrier provides VPN services to a Tier 2 carrier by using MP-iBGP to establish peering relationships between the Tier 1 carrier's PEs and transfer routes from the Tier 2 carrier's backbone SRv6 locator to establish the Tier 2 carrier's SRv6 tunnel. The SRv6 routing control plane consists of the following: 1) The Tier 2 carrier activates ISIS for SRv6. Locator routes are published within ISIS, then distributed to the Tier 1 carrier's VPN using eBGP between the Tier 2 carrier and the Tier 1 carrier. These routes are then distributed to other areas using MP-iBGP within the Tier 1 carrier. 2) The secondary carrier's ISIS generates an End SID for each node. PE1, PE2, PE3, and PE4 of the secondary carrier each generate an End SID. 3) The secondary carrier uses the global locator parameter through BGP to generate a DT4 SID for the VPN. The secondary carrier's PE generates a DT4 SID. 4) The primary carrier activates ISIS for SRv6, publishes locator routes within ISIS, and publishes the secondary carrier's locator routes through MP-iBGP. 5) The Tier 1 operator's ISIS generates an End SID for each node, and the Tier 1 operator generates an End SID for the PE. 6) The Tier 1 operator generates an End.CSC SID for the VPN through the CSC VPN SID generation module, and the Tier 1 operator's PE generates an End.CSC SID. The End.CSC SID is a new type of SID used to identify the Tier 1 operator's access point as capable of SRv6 VPN services. 7) The Tier 1 operator publishes the End.CSC SID generated by the PE router through the CSC VPN SID publication module. SRv6 controller networking structure: 1) The Tier 2 carrier's SRv6 controller establishes BGP linkstate address clusters and BGP SR-Policy peer relationships with the Tier 2 carrier's PE devices and ASBR devices to collect topology and TE information and deliver SRv6 TE policies. 2) The Tier 2 carrier's SR router information is completed through ISIS and redistributed by ISIS to the BGP Linkstate address cluster. The Tier 1 carrier notifies the Tier 2 carrier's ASBR of the CSC SRv6 VPN function of its PE equipment through eBGP. The ASBR redistributes the information through eBGP to the BGP Linkstate address cluster, which is then distributed to the Tier 2 carrier's SRv6 controller. 3) The Tier 1 carrier establishes the path calculation topology and distributes the SRv6 TE Policy structure.

9. A two-level operator networking optimization system based on a new SID according to claim 8, characterized in that: The system includes header nesting scenarios and header merging scenarios when forwarding data; The data forwarding process of the header nesting scenario is as follows: 1) A user connected to CE1 accesses a service connected to CE2 and sends a DST, IPv4 / IPv6 packet. 2) The user's IPv4 / IPv6 packet arrives at the Tier 2 carrier's PE1. Based on the SRv6 TEPolicy policy issued by the controller, the user packet is encapsulated into an SRv6 VPN packet and forwarded to the Tier 2 carrier's ASBR1. The packet contains the IPv6 header, SRH header, and payload. 3) After the packet reaches the Tier 2 carrier's ASBR, the destination address is changed to the Tier 1 carrier's End.CSCSID according to the SRH header, and the packet is then forwarded to the Tier 1 carrier's access PE1. 4) The message arrives at the Tier 1 carrier access PE1, undergoes programming operations based on the End.CSC SID requirements, and is then sent to the Tier 1 carrier backbone P. The programming operations include: extracting the next hop from the SRH to replace the destination address in the IPv6 header of the Tier 2 carrier message; and placing the Tier 2 carrier's SRv6 message as the payload into the Tier 1 carrier's SRv6 message, including the IPv6 header, SRH header, and payload. 5) When the packet reaches the Tier 1 carrier backbone P, the packet is forwarded to the Tier 1 carrier access PE2 using the current standard SRv6 packet forwarding operation. The next hop address of the SRH is replaced with the destination address of the IPv6 packet. 6) After the packet reaches the Tier 1 carrier access PE2, it follows the current standard SRv6 packet forwarding operation, extracts the next hop from the SRH, finds the next hop is the local End.CSC SID, pops the Tier 1 carrier's SRv6 header, queries the Tier 2 carrier's SRv6 packet header for the IPv6 destination address, performs the End.CSC SID programming operation in the VPN, extracts the next hop from the SRH, replaces it with the IPv6 destination address in the Tier 2 carrier's SRv6 packet, and forwards it to Tier 2 carrier ASBR2. 7) After the packet reaches the Tier 2 carrier ASBR2, it is forwarded to the Tier 2 carrier access PE2 using standard SRv6 packet forwarding operations. The SRH next hop is replaced with the IPv6 destination address in the SRv6 packet header. 8) After the message arrives at the secondary operator access PE2, it extracts the SRH next-hop DT4 SID according to the normal SRv6 message operation. According to the DT4 SID operation, it pops the SRv6 message header, queries the route of the user's original IPv4 message header in the VPN, forwards it to the user access CE2, and then continues to forward it to the corresponding server in the user network.

10. A two-level operator networking optimization system based on a new SID according to claim 9, characterized in that: The data forwarding process in the header merging scenario is as follows: 1) A user connected to CE1 accesses a service connected to CE2 and sends a DST, IPv4 / IPv6 packet. 2) The user's IPv4 / IPv6 packet arrives at the Tier 2 carrier's PE1. Based on the SRv6 TEPolicy policy issued by the controller, the user packet is encapsulated into an SRv6 VPN packet and forwarded to the Tier 2 carrier's ASBR1. The packet contains the IPv6 header, SRH header, and payload. 3) After the packet reaches the Tier 2 carrier's ASBR, the destination address is changed to the Tier 1 carrier's End.CSCSID according to the SRH header, and the packet is then forwarded to the Tier 1 carrier's access PE1. 4) The message arrives at the Tier 1 carrier access PE1, where it is programmed according to the End.CSC SID requirements and then sent to the Tier 1 carrier backbone P. The programming operations are as follows: the next hop is extracted from the SRH to replace the destination address in the IPv6 header of the Tier 2 carrier message; the IPv6 header in the Tier 2 carrier's SRv6 message is removed, the node before the local End.CSC SID in the SRH list is deleted, the Tier 1 carrier's SRv6 TE Policy node is inserted into the front-end to form a new SRH list, a new IPv6 header is generated, and a new SRv6 message is assembled, including the IPv6 header, SRH header, and payload. 5) When the packet reaches the Tier 1 carrier backbone P, the packet is forwarded to the Tier 1 carrier access PE2 using the current standard SRv6 packet forwarding operation. The next hop address of the SRH is replaced with the destination address of the IPv6 packet. 6) After the packet arrives at the Tier 1 carrier access PE2, it follows the current standard SRv6 packet forwarding operation to retrieve the next hop from the SRH. It finds that the next hop is the local End.CSC SID. After programming the End.CSC SID, it retrieves the next hop from the SRH and replaces it with the IPv6 destination address in the Tier 2 carrier's SRv6 packet. The packet is then forwarded to Tier 2 carrier ASBR2. 7) After the packet reaches the Tier 2 operator ASBR2, it uses standard SRv6 packet forwarding operations to replace the IPv6 destination address in the SRv6 packet header with the SRH next hop and forwards it to the Tier 2 operator access PE2. After the packet reaches the Tier 2 operator access PE2, it uses standard SRv6 packet operations to extract the SRH next hop DT4 SID, and uses the DT4 SID operation to pop out the SRv6 packet header. It then queries the VPN for the route of the user's original IPv4 packet header and forwards it to the user access CE2. The packet is then forwarded to the corresponding server in the user network.

Images