Method and equipment for realizing IPv6 segment routing network slice forwarding

Abstract

The invention provides a method and equipment for realizing IPv6 segment routing network slice forwarding. The method comprises the following steps: setting a strict mode in a first SRv6 data message descriptor matched with a strict mode mark table item of a directional access control table; associating the first SRv6 data message matched with the network slice channel mapping table item of the direction access table to the network slice channel of the network slice instance; searching a real next hop out interface in the longest route matching table based on the outer layer destination IP address of the first SRv6 data message; caching the first SRv6 data message in a cache space corresponding to the network slice instance in an outbound buffer; and scheduling the first SRv6 data message to a port queue bound with the network slice channel in the real next hop-out interface.

Description

Technical Field

[0001] This application relates to communication technologies, and more specifically, to a method and device for implementing IPv6 segment routing network slice forwarding. Background Art

[0002] A large number of terminal devices and various types of applications are connected to the network. The needs of home users and industrial users are different, and the demands of users are becoming more and more personalized. Using a single network or a unified policy can no longer meet the needs of emerging new services and new scenarios. Building a separate network for each service scenario is costly and time-consuming.

[0003] Network slicing technology supports partitioning multiple independent virtual networks on a physical network, allocating resources on demand for different services, and providing differentiated queue scheduling capabilities to meet the different needs of various services without affecting the existing network. A network slice instance has a unique network slice identifier (Slice ID), and network slicing supports SRv6 networking.

[0004] Since the switching chips of the existing switch devices in the network were introduced earlier and are not flexibly programmable, for the switching chips that perform queue scheduling in the ingress direction, how to implement network slice forwarding. Summary of the Invention

[0005] The purpose of this application is to provide a method and device for implementing IPv6 segment routing network slice forwarding, which can implement slice forwarding in strict mode within the SRv6 network.

[0006] To achieve the above purpose, a method for implementing IPv6 segment routing network slice forwarding includes setting strict mode in the first SRv6 data packet descriptor that matches the strict mode marking entry of the ingress access control list; associating the first SRv6 data packet that matches the network slice channel mapping entry of the ingress access table with the network slice channel of the network slice instance; finding the actual next-hop egress interface in the longest route matching table based on the outer destination IP address of the first SRv6 data packet; caching the first SRv6 data packet in the cache space corresponding to the network slice instance in the egress buffer cache; and scheduling the first SRv6 data packet to the port queue bound to the network slice channel of the actual next-hop egress interface.

[0007] To achieve the above object, the present application provides a device for implementing SRv6 network slice forwarding. The device includes a processor, a memory, and a switching chip having one or more programmable processors. The programmable processors of the switching chip are configured to perform the following processes: setting strict mode in the first SRv6 data packet descriptor that matches the strict mode marking entry of the ingress access control table; associating the first SRv6 data packet that matches the network slice channel mapping entry of the ingress access table with the network slice channel of the network slice instance; looking up the actual next-hop egress interface in the longest route matching table based on the outer destination IP address of the first SRv6 data packet; caching the first SRv6 data packet in the cache space corresponding to the network slice instance in the egress buffer cache; and scheduling the first SRv6 data packet to the port queue of the port bound to the network slice channel of the actual next-hop egress interface.

[0008] The beneficial effect of the embodiment of the present application is that the mapping of the network slice channel is implemented in the ingress direction, and the SRv6 data packet is mapped to the network slice channel of the network slice instance to achieve network slice forwarding. Description of the Drawings

[0009] Figure 1 It is a schematic diagram of an embodiment of a method for implementing SRv6 network slice forwarding provided by the present application;

[0010] Figure 2 It is a schematic diagram of an SRv6 network with network slice instances;

[0011] Figure 3 It is a schematic diagram of an embodiment of a device for implementing SRv6 network slice forwarding provided by the present application. Detailed Embodiments

[0012] Multiple examples shown in multiple drawings will be described in detail. In the following detailed description, multiple specific details are used to provide a comprehensive understanding of the present application. Known methods, steps, components, and circuits are not described in detail in the examples to avoid making these examples difficult to understand.

[0013] Among the terms used, the term "including" means including but not limited to; the term "containing" means including but not limited to; the terms "above", "within", and "below" include the number; the terms "greater than" and "less than" do not include the number. The term "based on" means at least based on a part of it.

[0014] Figure 1 The following shows an embodiment of a method for implementing IPv6 segment routing network slice forwarding provided by the present application. The embodiment includes:

[0015] Step 101: Set the strict mode in the first SRv6 data packet descriptor of the strict mode marking entry that matches the incoming direction access control table.

[0016] Step 102: Associate the first SRv6 data packet of the network slice channel mapping entry that matches the incoming direction access table with the network slice channel of the network slice instance.

[0017] Step 103: Search for the actual next-hop egress interface in the longest route matching table based on the outer destination IP address of the first SRv6 data packet.

[0018] Step 104: Cache the first SRv6 data packet in the cache space corresponding to the network slice instance in the egress direction buffer cache.

[0019] Step 105: Schedule the first SRv6 data packet to the port queue of the port bound to the network slice channel in the actual next-hop egress interface.

[0020] The beneficial effect of this application is that the mapping of the network slice channel is realized in the incoming direction, and the SRv6 data packet is mapped to the network slice channel of the network slice instance to realize network slice forwarding.

[0021] Figure 2 It is a schematic diagram of the SRv6 network with network slice instances;

[0022] CE device 21 sends 210, 220, 230, 240 from the terminal device ( Figure 2 not shown) to the terminal device accessed by CE device 22 ( Figure 2 not shown).

[0023] PE device 23 receives the Ethernet data packets 210, 220, 230, 240 from the private network on the bound VPN interface. The destination MAC addresses of the Ethernet data packets 210, 220, 230, 240 correspond to the SRv6 three-layer attributes; strip the outer Ethernet header of the Ethernet data packets 210, 220, 240, 240 to obtain the IP data packets 210', 220', 230', 240'; search for the SID of PE device 25 corresponding to the matching route in the routing table based on the destination IP addresses of the IP data packets 210', 220', 230', 240'; the type of this SID is End.DT4 SID.

[0024] PE device 23 encapsulates the IP data packets 210', 220', 230', 240' into SRv6 data packets 211, 221, 231, 241 according to the encapsulation information of the SID of the tail-end PE device 25.

[0025] The PE device 23 uses the SID encapsulation information of the tail-end node PE24 device as the loopback port of the outgoing interface, and loops back the SRv6 data packets 211, 221, 231, and 241.

[0026] In the incoming direction access control table of the PE device 23, the strict mode flag entry and the network slice channel mapping entry are stored in storage spaces with different search priorities; the strict mode flag entry is stored in the storage space with a higher search priority.

[0027] The first bit of the lower 32 bits of the outer source IPv6 source address of the SRv6 data packet is the Strict-Flag (strict) flag bit, and the remaining 31 bits carry the identifier of the slice channel.

[0028] Based on the IPv6 source addresses of the looped-back SRv6 data packets 211, 221, and 231, the PE device 23 matches the strict mode flag entry and sets the strict mode in the SRv6 data packet descriptors of 211, 221, and 231.

[0029] If the PE device 23 does not match the strict mode flag entry based on the looped-back SRv6 data packet 241 in the storage space with a high search priority, the strict mode is not set in the SRv6 data packet 241 descriptor.

[0030] The PE device 23 finds the network slice channel mapping entries that match Slice ID1 for the SRv6 data packets 211 and 221, and maps the SRv6 data packets 211 and 221 to the network slice channel of Slice ID1.

[0031] The PE device 23 finds the network slice channel mapping entries that match Slice ID2 for the SRv6 data packets 231 and 241, and maps the SRv6 data packets 231 and 241 to the network slice channel of Slice ID2.

[0032] Based on the outer destination IP addresses of the SRv6 data packets 211, 221, and 231, the PE device 23 searches in the longest route matching table within the VPN to find that the actual next-hop outgoing interface is the interface (not shown in the figure, Interface 0 / 1) where the PE device 23 is connected to the P device 24.

[0033] Based on the outer destination IP address of the SRv6 data packet 241, the PE device 23 finds in the longest route matching table that the next-hop outgoing interface of the default route is Interface 0 / 1.

[0034] The PE device 23 caches the SRv6 data packets 211 and 221 in the cache space corresponding to the network slice instance Slice ID1 in the egress direction buffer cache, and caches the SRv6 data packets 231 and 241 in the cache space corresponding to the network slice instance Slice ID2.

[0035] The PE device 23 schedules the SRv6 data packets 211 and 221 to the port queue of the network slice channel of Interface 0 / 1 bound to Slice1, such as queue 0.

[0036] The PE device 23 schedules the SRv6 data packet 231 to the port queue of the network slice channel of Interface 0 / 1 bound to Slice2, such as queue 1.

[0037] The PE device 23 schedules the SRv6 data packet 241 to the port queue of the network slice channel of Slice2 bound to the default route egress interface Interface 0 / 1, such as queue 1.

[0038] The PE device 23 assigns weights to queues 0 - 7 of Interface 0 / 1 based on the SDWRR (Shaped Deficit Weighted Round Robin) scheduling algorithm; the weights of queues 0 and 1 are greater than those of the queues not bound to any network slice channels, so as to ensure that the SRv6 data packets 211, 221, 231, and 241 in queues 0 and 1 are preferentially forwarded in each polling cycle. The weights of queues 0 and 1 of Interface 0 / 1 can be the same or different according to the different priority levels of the cache.

[0039] The P device 24 receives the SRv6 data packets 211, 221, 231, and 241.

[0040] The P device 24 first matches the outer IPv6 source addresses of the SRv6 data packets 211, 221, and 231 to the strict mode marking entries, and sets the strict mode in the packet descriptors of the SRv6 data packets 211, 221, and 231.

[0041] The P device 24 searches for a storage space with a high priority. Since the loopback-based SRv6 data packet 241 does not match the strict mode marking entry, the strict mode is not set in the packet descriptor of the SRv6 data packet 241.

[0042] The P device 24 finds the network slice channel mapping entries in the network slice channel mapping table that match the SRv6 data packets 211 and 221 for Slice ID1, and maps the SRv6 data packets 211 and 221 to the network slice channel of Slice ID1.

[0043] The P device 24 finds the network slice channel mapping entries in the network slice channel mapping table that match the SRv6 data packets 231 and 241 for Slice ID2, and maps the SRv6 data packets 231 and 241 to the network slice channel of Slice ID2.

[0044] Based on the outer destination IP address of the SRv6 data packets 211 and 221, the P device 24 searches in the longest route matching table within the VPN and finds that the actual next-hop egress interface is the interface (not shown in the figure, Interface 1 / 1) through which the P device 24 is connected to the PE device 25.

[0045] Based on the outer destination IP address of the SRv6 data packet 231, the P device 24 does not find the actual next-hop egress interface in the longest route matching table within the VPN, and discards the SRv6 data packet 231.

[0046] Based on the outer destination IP address of the SRv6 data packet 241, the P device 24 finds in the longest route matching table that the next-hop egress interface of the default route is the egress interface Interface 1 / 1.

[0047] The P device 24 caches the SRv6 data packets 211 and 221 in the cache space corresponding to the network slice instance Slice ID1 in the egress direction buffer cache, and caches the SRv6 data packet 241 in the cache space corresponding to the network slice instance Slice ID2.

[0048] The P device 24 schedules the SRv6 data packets 211 and 221 to the port queue of the network slice channel of Slice1 bound to the egress interface Interface 1 / 1, such as queue 0.

[0049] The P device 24 schedules the SRv6 data packet 241 to the port queue of the network slice channel of Slice2 bound to the default route egress interface Interface 1 / 1, such as queue 1.

[0050] The P device 24, based on the SDWRR scheduling algorithm, assigns weights to queue 0 and queue 1 of interface Interface 1 / 1 that are greater than those of other queues not bound to any network slice channels. This ensures that the SRv6 data packets 211, 221, and 241 in queue 0 and queue 1 of Interface 1 / 1 are preferentially forwarded. The weights of queue 0 and queue 1 of Interface 1 / 1 can be the same or different according to the priority levels of the caches.

[0051] The PE device 25 receives the SRv6 data packets 211, 221, and 241.

[0052] The PE device 25, based on the outer IPv6 source addresses of the SRv6 data packets 211 and 22, first matches a strict mode marking entry and sets the strict mode in the packet descriptors of the SRv6 data packets 211 and 221.

[0053] When the PE device 25 searches for a storage space with a high priority and the loopback-based SRv6 data packet 241 does not match the strict mode marking entry, the strict mode is not set in the packet descriptor of the SRv6 data packet 241.

[0054] The PE device 25 finds the network slice channel mapping entries of Slice ID1 that match the SRv6 data packets 211 and 221 and maps the SRv6 data packets 211 and 221 to the network slice channel of Slice ID1.

[0055] The PE device 25 finds the network slice channel mapping entries of Slice ID2 that match the SRv6 data packet 241 and maps the SRv6 data packet 241 to the network slice channel of Slice ID2.

[0056] The PE device 25 determines that the outer destination IP address of the SRv6 data packets 211, 221, and 241 is the local SID; strips off the outer Ethernet header, outer IP header, and SRH header of the SRv6 data packets 211, 221, and 241 to obtain the IPv6 data packets 211', 221', and 241'.

[0057] The PE device 25 finds the next-hop egress interface Interface 2 / 1 in the forwarding information table according to the destination IP address of the IPv6 data packet 211'; caches the IPv6 data packet 211' in the cache space corresponding to Slice ID1 in the egress direction buffer cache.

[0058] The PE device 25 does not find the next-hop egress interface in the forwarding information table according to the destination IP address of the IPv6 data packet 221' and discards the IPv6 packet 221'.

[0059] The PE device 25 looks up the next-hop egress interface Interface 2 / 1 in the forwarding information table according to the destination IP address of the IPv6 data packet 241'; and caches the IPv6 data packet 241' in the cache space corresponding to Slice ID2 in the egress direction buffer cache.

[0060] The PE device 25 schedules the IPv6 data packet 211' to port queue 0 of the network slice channel bound to sliceID1 in the next-hop egress interface Interface 2 / 1.

[0061] The PE device 25 schedules the IPv6 data packet 241' to port queue 1 of the network slice channel bound to sliceID2 in the next-hop egress interface Interface 2 / 1.

[0062] Based on the SDWRR scheduling algorithm, the PE device 25 encapsulates the IPv6 data packets 211' and 241' in queues 0 and 1 into Ethernet data packets 212 and 242 based on the egress interface Interface 2 / 1, and preferentially forwards the Ethernet data packets 212 and 242 in queues 0 and 1 of the egress interface Interface 2 / 1.

[0063] In this application, for SRv6 that supports the strict mode, it is forwarded according to the slice channel of the slice instance bound to the egress interface; for SRv6 packets that support the strict mode and no egress interface is found, the SRv6 packet is discarded; for SRv6 that does not support the strict mode, it is forwarded through the slice channel of the slice instance bound to the egress interface of the matching default route.

[0064] Figure 3 This is a schematic diagram of an apparatus embodiment for implementing SRv6 network slice forwarding provided by this application. The apparatus includes a processor 31, a memory 32, and more than one switching chip 33.

[0065] The programmable processor of the switching chip 33 is configured to perform the following processing: set the strict mode in the first SRv6 data packet descriptor that matches the strict mode flag entry of the ingress access control table; associate the first SRv6 data packet that matches the network slice channel mapping entry of the ingress access table with the network slice channel of the network slice instance; look up the actual next-hop egress interface in the longest route matching table based on the outer destination IP address of the first SRv6 data packet; cache the first SRv6 data packet in the cache space corresponding to the network slice instance in the egress direction buffer cache; schedule the first SRv6 data packet to the port queue bound to the network slice channel in the actual next-hop egress interface.

[0066] The programmable processor of the switching chip 33 is configured to perform the following processes: set strict mode in the second SRv6 data packet descriptor that matches the strict mode label entry; associate the second SRv6 data packet that matches the network slice channel mapping entry with the network slice channel; discard the second SRv6 data packet if the real next-hop egress interface is not found in the longest route matching table based on the outer destination IP address of the second SRv6 data packet.

[0067] The programmable processor of the switching chip 33 is configured to perform the following processes: set non-strict mode in the third SRv6 data packet descriptor that does not match the strict mode label entry; associate the third SRv6 data packet that matches the network slice channel mapping entry with the network slice channel; if the real next-hop egress interface of the outer destination IP address of the third SRv6 data packet is not found in the longest route matching table; if the next-hop egress interface of the default route that matches the outer destination IP address of the third SRv6 data packet is found in the longest route matching table; cache the third SRv6 data packet in the cache space corresponding to the network slice instance in the egress direction buffer cache; schedule the third SRv6 data packet to the port queue of the port bound to the network slice channel of the next-hop egress interface of the default route.

[0068] The programmable processor of the switching chip 33 is configured to perform the following processes: loopback the first, second, and third SRv6 data packets. The process of loopback the first, second, and third SRv6 data packets includes determining that the received first, second, and third Ethernet data packets perform SRv6 encapsulation; stripping the outer Ethernet header of the first, second, and third Ethernet data packets to obtain the first, second, and third IP data packets; finding the tail node SID based on the destination IP address of the first, second, and third IP packets; encapsulating the first, second, and third IP packets into the first, second, and third SRv6 data packets according to the encapsulation information of the tail node SID; sending the first, second, and third SRv6 data packets through the loopback port of the egress interface using the encapsulation information of the tail node SID.

[0069] The programmable processor of the switching chip 33 is configured to perform the following processes: set the strict mode in the fourth SRv6 data packet descriptor that matches the strict mode tag entry; associate the fourth SRv6 data packet that matches the network slice channel mapping entry with the network slice channel; determine that the outer destination IP address of the fourth SRv6 data packet is a local SID; strip off the outer Ethernet header, outer IP header, and SRH header of the fourth SRv6 data packet to obtain the fourth IPv6 data packet; find the next-hop egress interface in the forwarding information table according to the destination IP address of the fourth IP data packet; cache the fourth IPv6 data packet in the cache space corresponding to the network slice instance in the egress direction buffer cache; schedule the fourth IPv6 packet to the port queue of the next-hop egress interface bound to the network slice channel.

[0070] The programmable processor of the switching chip 33 is configured to perform the following processes: set the strict mode in the fifth SRv6 data packet descriptor that matches the strict mode tag entry; associate the fifth SRv6 data packet that matches the network slice channel mapping entry with the network slice channel; determine that the outer destination IP address of the fifth SRv6 data packet is a local SID; strip off the outer Ethernet header, outer IP header, and SRH header of the fifth SRv6 data packet to obtain the fifth IPv6 data packet; in the forwarding information table, fail to find the next-hop egress interface for the destination IP address of the fifth IPv6 data packet; discard the fifth IPv6 packet.

[0071] The programmable processor of the switching chip 33 is configured to perform the following processes: set the non-strict mode in the sixth SRv6 data packet descriptor that does not match the strict mode tag entry; associate the sixth SRv6 data packet that matches the network slice channel mapping entry with the network slice channel; determine that the outer destination IP address of the sixth SRv6 data packet is a local SID; strip off the outer Ethernet header, outer IP header, and SRH header of the sixth SRv6 data packet to obtain the sixth IPv6 data packet; in the forwarding information table, fail to find the next-hop egress interface for the destination IP address of the sixth IPv6 data packet; in the forwarding information table, find the next-hop egress interface of the default route that matches the outer destination IP address of the sixth IPv6 packet; cache the sixth IPv6 data packet in the cache space corresponding to the network slice instance in the egress direction buffer cache; schedule the sixth IPv6 packet to the port queue of the next-hop egress interface of the default route bound to the network slice channel. The search and match priority of the storage space of the strict mode tag entry is higher than that of the storage space of the network slice channel mapping entry.

[0072] In this application, the machine-readable storage medium can be any electronic, magnetic, optical, or other physical storage device used to store or contain information (such as executable instructions, data, etc.). For example, any machine-readable storage medium described herein can be any type of random access memory (RAM), volatile memory, non-volatile memory, flash memory, storage drive (such as a hard disk drive), solid-state drive, any type of storage optical disc (such as a CD, DVD, etc.), and similar devices, or a combination thereof. In addition, any machine-readable storage medium described herein can be a non-transitory machine-readable storage medium.

[0073] The foregoing are only preferred embodiments of this application and are not intended to limit this application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this application shall be included within the scope of protection of this application.

Claims

1. A method for implementing IPv6 segment routing network slice forwarding, characterized in that, The method includes, setting strict mode in the first SRv6 data packet descriptor that matches the strict mode flag entry of the ingress direction access control table; associating the first SRv6 data packet that matches the network slice channel mapping entry of the ingress access table with the network slice channel of the network slice instance; looking up the actual next-hop egress interface in the longest route matching table based on the outer destination IP address of the first SRv6 data packet; caching the first SRv6 data packet in the cache space corresponding to the network slice instance in the egress direction buffer cache; scheduling the first SRv6 data packet to the port queue bound to the network slice channel in the actual next-hop egress interface.

2. The method according to claim 1, wherein The method includes, setting strict mode in the second SRv6 data packet descriptor that matches the strict mode flag entry; associating the second SRv6 data packet that matches the network slice channel mapping entry with the network slice channel; if the actual next-hop egress interface is not found in the longest route matching table based on the outer destination IP address of the second SRv6 data packet, discarding the second SRv6 data packet.

3. The method according to claim 1, characterized in that The method includes, setting non-strict mode in the third SRv6 data packet descriptor that does not match the strict mode flag entry; associating the third SRv6 data packet that matches the network slice channel mapping entry with the network slice channel; in the longest route matching table, the actual next-hop egress interface of the outer destination IP address of the third SRv6 data packet is not found; in the longest route matching table, the next-hop egress interface of the default route that matches the outer destination IP address of the third SRv6 data packet is found; caching the third SRv6 data packet in the cache space corresponding to the network slice instance in the egress direction buffer cache; scheduling the third SRv6 data packet to the port queue bound to the network slice channel in the next-hop egress interface of the default route.

4. The method according to claim 3, characterized in that, The first, second, and third Rv6 data packets are looped-back SRv6 data packets; Looping back the first, second, and third SRv6 data packets includes: determining that the received first, second, and third Ethernet data packets perform SRv6 encapsulation; stripping the outer Ethernet header of the first, second, and third Ethernet data packets to obtain the first, second, and third IP data packets; finding the tail node SID based on the destination IP address of the first, second, and third IP packets; encapsulating the first, second, and third IP packets into the first, second, and third SRv6 data packets according to the encapsulation information of the tail node SID; sending the first, second, and third SRv6 data packets through the loopback port of the egress interface using the encapsulation information of the tail node SID.

5. The method according to claim 1, characterized in that, The method includes, setting strict mode in the fourth SRv6 data packet descriptor that matches the strict mode flag entry; associating the fourth SRv6 data packet that matches the network slice channel mapping entry with the network slice channel; Determine that the outer destination IP address of the fourth SRv6 data packet is a local SID; Strip the outer Ethernet header, outer IP header, and SRH header of the fourth SRv6 data packet to obtain a fourth IPv6 data packet; Find the next-hop egress interface in the forwarding information table according to the destination IP address of the fourth IP data packet; Cache the fourth IPv6 data packet in the cache space corresponding to the network slice instance in the egress direction buffer cache; Schedule the fourth IPv6 packet to the port queue bound to the network slice channel in the next-hop egress interface; 6. The method according to claim 1, wherein The method includes, Set the strict mode in the fifth SRv6 data packet descriptor that matches the strict mode marking entry; Associate the fifth SRv6 data packet that matches the network slice channel mapping entry with the network slice channel; Determine that the outer destination IP address of the fifth SRv6 data packet is a local SID; Strip the outer Ethernet header, outer IP header, and SRH header of the fifth SRv6 data packet to obtain a fifth IPv6 data packet; In the forwarding information table, the next-hop egress interface for the destination IP address of the fifth IPv6 data packet is not found; Discard the fifth IPv6 packet; 7. The method according to claim 1, characterized in that, The method includes, Set the non-strict mode in the sixth SRv6 data packet descriptor that does not match the strict mode marking entry; Associate the sixth SRv6 data packet that matches the network slice channel mapping entry with the network slice channel; Determine that the outer destination IP address of the sixth SRv6 data packet is a local SID; Strip the outer Ethernet header, outer IP header, and SRH header of the sixth SRv6 data packet to obtain a sixth IPv6 data packet; In the forwarding information table, the next-hop egress interface for the destination IP address of the sixth IPv6 data packet is not found; In the forwarding information table, find the next-hop egress interface of the default route whose outer destination IP address of the sixth IPv6 packet matches; Cache the sixth IPv6 data packet in the cache space corresponding to the network slice instance in the egress direction buffer cache; Schedule the sixth IPv6 packet to the port queue bound to the network slice channel in the next-hop egress interface of the default route; 8. The method according to claim 1, wherein The search and match priority of the storage space of the strict mode marking entry is higher than the search and match priority of the storage space of the network slice channel mapping entry; 9. A device for implementing SRv6 network slice forwarding, characterized in that The device includes a processor, a memory, and more than one switching chip; the programmable processor of the switching chip is configured to execute any one of the methods of claims 1-8.

Images